opt11c ISDN w/ cisco router

[gewt]

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 34 08 02 00 FE 05
BCAP:04 03 80 90 A2
CHID:18 03 A9 83 17
PROG:1E 02 81 83
DISP:28 0A B1 4D 61 69 6E 20 44 65 73 6B
CLNG:6C 0C 80 01 04 01 05 06 01 06 09 05 04 02
CLED:70 05 C1 07 0A 0A 05

DCH 10 OMSG CONNECT REF 000080FE CH 1 23 TOD 14:33:56 CK 269A9AC8
HEADER:01 01 00 0B 08 02 80 FE 07
CHID:18 04 E9 80 83 17

DCH 10 IMSG STATUS REF 000080FE CH 1 23 TOD 14:33:56 CK 269A9B3D
HEADER:2F 01 00 0D 08 02 00 FE 7D
CSE :08 03 80 E2 07
CAST:14 01 01

DCH 10 OMSG RELEASE REF 000080FE CH 1 23 TOD 14:33:56 CK 269A9B43
HEADER:01 01 00 09 08 02 80 FE 4D
CSE :08 02 81 E2

DCH 10 IMSG REL COMP REF 000080FE CH 1 23 TOD 14:33:56 CK 269A9B6F
HEADER:2F 01 00 05 08 02 00 FE 5A

DCH 10 IMSG SETUP REF 000080FC CH 1 23 TOD 14:32:00
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:14156169542 NUM PLAN: NUM UNKNOWN
CALLED #:7005 NUM PLAN: E164

DCH 10 OMSG CONNECT REF 000080FC CH 1 23 TOD 14:32:00

DCH 10 IMSG STATUS REF 000080FC CH 1 23 TOD 14:32:00
CAUSE :MSG NOT COMPATIBLE WITH STATE
STATE : CALL INIT ST

DCH 10 OMSG RELEASE REF 000080FC CH 1 23 TOD 14:32:00
CAUSE :MSG NOT COMPATIBLE WITH STATE

DCH 10 IMSG REL COMP REF 000080FC CH 1 23 TOD 14:32:00

If what I googled around and found is correct, a STATUS-ENQUIRY message should proceed the STATUS message and that's why the Meridian is sending back a cause code, correct?

Is there a way to work around this? I'm using the SL100/DMS100 type between the Cisco and opt11c for caller name display - is QSIG likely to not have this odd problem? Using NI2 had no issues in this situation, but I am not licensed for NI2 name display.

Here's the DCH ADAN entry:
ADAN DCH 10
CTYP MSDL
CARD 01
PORT 1
DES CiscoIADPRI
USR PRI
DCHL 1
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC S100
SIDE NET
CNEG 1
RLS ID 26
RCAP ND2
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7

And the cisco's idea of the d-channel:
interface Serial0/0/1:23
no ip address
encapsulation hdlc
no logging event link-status
logging event nfas-status
logging event subif-link-status
isdn switch-type primary-dms100
isdn timer T310 120000
isdn incoming-voice voice
isdn guard-timer 20000
isdn supp-service name calling
isdn send-alerting
isdn channel-id invert extend-bit
no cdp enable

 

[bignose21]

The Meridian receives the setup message and replies back with a Connect, the far end says "Message not compatible with call state or message type no-existant" so the Meridian releases the call for the same reason.

What is this connecting to in the Meridian that there is no Alerting etc. just setup then connect?

Most the Cisco I have connected to I usually use ISGF.

 

[gewt]

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?

 

[gewt]

There we go.

Now I'm just not getting name display...

(of note: I do NOT have a license for NI-2 name display....which is rather annoying)

ADAN DCH 10
CTYP MSDL
CARD 01
PORT 1
DES Cisco_2851_PRI
USR PRI
DCHL 1
OTBF 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 2
OUT_T306 30
T200 3
T203 10
N200 3
N201 260
K 7

interface Serial0/0/1:23
no ip address
encapsulation hdlc
no logging event link-status
logging event nfas-status
logging event subif-link-status
isdn switch-type primary-qsig
isdn timer T310 120000
isdn overlap-receiving
isdn protocol-emulate network
isdn incoming-voice voice
isdn guard-timer 20000
isdn supp-service name calling profile Network-Extension operation-value-tag local
isdn send-alerting
no cdp enable

fixed my prior issue at least...

 

[gewt]

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

 

[bignose21]

Could see that you already had RCAP NDO so I guess it was just the Cisco end you needed to alter.

Good stuff that you are sorted.

 

[gewt]

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.

 

[bignose21]

Would it be any different if you used RCAP ND1?

I just set it up on NI2 to a Sonus UX1000 and RCAP was NDS which needs package 385, that worked ok.

 

[gewt]

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