Search results for query: *

Hi all, Continuing my "oddities for my Meridian lab" project I snagged an M3000 touchphone off ebay for a reasonable price. Mint condition, only missing a stylus and one other important item. (Did it ship with one?) The other important item I am missing is...a power supply for it. Does anyone...

Turns out it was strange digit modification plan left over from previous configs. Now the issue is: absorb one digit: dialled number: 517 absorb 0 digits: dialled number: 90517 That's 2 digits, ICP.

...a digital trunk group of "2" which contains every B-channel in descending order. Inbound calls work just fine: 15:43:31 RI601 DPN 2A ISRM_I ;10;*3#*19*Z#*58*Ca*1*Z#*233*`IBb#*58*CI*W5# 15:43:31 RI601 DPN 13 SSRM_C *50*4156169542#134 15:43:31 RO601 DPN...

It wasn't behaving with RCAP of NDI; it wanted NDO.

Yep; the Cisco was being a little silly about things - ISO QSIG on meridian with RCAP NDO wants ECMA-style calling party for some reason.

Fixed with: RCAP: NDO cisco side: isdn supp-service name calling profile Network-Extension operation-value-tag ecma GFFAC: 37 24 13 00 9F 00 AA 06 80 01 00 82 01 00 01 00 A1 14 02 01 10 06 04 2B 0C 09 00 80 09 4D 61 69 6E 20 44 65 73 6B

...32 PARM RS422 DTE DRAT 64KC CLOK EXT IFC ISGF PINX_CUST 0 ISDN_MCNT 300 CLID OPT0 CO_TYPE STD SIDE USR CNEG 1 RLS ID ** RCAP COLP NDO CCBI CCNI PRI PR_TRIGS DIV 2 3 CNG 2 3 PR_RTN NO MBGA NO OVLR NO OVLS YES OVLT 0 T310 120 INC_T306...

This is to either a non-working number or the T105 test line. I can easily switch to ISGF - thanks. Could there also be some weirdness with my trunk type being set to DID as opposed to say, TIE?

Hi all, On calls to invalid numbers or the 105-type test extension over a PRI, the Meridian sends a cause code back (MSG not compatible with state) instead of the expected cause code. Here's the raw hex trace: DCH 10 IMSG SETUP REF 000080FE CH 1 23 TOD 14:33:56 CK 269A9ABC HEADER:2F 01 00...

Hi all, Is it possible to do conferee display on an M3903 hanging off an 11c? The M3903 manual mentions it but I can't find it in any Input/Output docs. Thanks!

Fixed it. LDN_DATA didn't have the right digit length.

...NUM PLAN: E164 CALLED #:4730621 NUM PLAN: E164 DCH 10 OMSG REL COMP REF 00008091 CH 1 23 TOD 19:58:44 CAUSE :CALL REJECTED DCH000 .*** OVL000 >ld 10 PBX000 MEM AVAIL: (U/P): 1171207 USED U P: 178646 26402 TOT: 1376255 SCH5066 TNS AVAIL: 449 USED: 51 TOT: 500...

I stumbled across a copy of CallPilot 5.0 discs on archive dot org when looking for some documentation very recently, if you can't find those physical copies.

I have, yes. Mine is a much older MICB so the webui isn't the greatest, CLI was mainly used for the error logs.

I have no remote cabinets...wonder what the hell is going on.

Option 11C running 24.x...forget the exact subversion.

That has not changed anything, even after a reset of the card. :( Something is spamming ERR5098 in console so I think something weird is going on with my bus...removing the CallPilot and MICB does not result in this error going away... Does anyone know what pins are the voltage rails? I'd...

Hi all, I've got an old MICB I've been trying to set up and I just absolutely cannot get any of the ports to log in...starting with just one as a test. 0006:SW DSPS 275 ln06860 ch00 11-17 15:33:26:516 LOG IN FAIL is the message repeatedly logged in telnet Here's the ACD: TYPE ACD CUST 0 ACDN...

Thanks. Now for the endless difficulty of tracking down that client...

It's actually 1.07...that'd explain none of the docs I was reading applying ;)