Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

ISDN Q.931

I am troubleshooting a second B channel of an ISDN connection with the following debug...complaining about an "invalid call reference".

A "show isdn status" shows "MULTIPLE_FRAME_ESTABLISHED" on both channels and everything looks good with the spids,etc.

I've checked the debug on the calling party, and it never receives the "CONNECT" message sent by the called party, but rather it gets the message that the called party is not responding. I assume this is the ISDN switch telling me something.

The first B channel connects, so I don't think it's my router...any thoughts?

*Feb 28 17:10:28 MST: ISDN BR2/0 Q931: RX <- SETUP pd = 8 callref = 0x41

Bearer Capability i = 0x8890

Standard = CCITT

Transer Capability = Unrestricted Digital

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x89

Signal i = 0x40 - Alerting on - pattern 0

Calling Party Number i = 0x2183, '403xxxxxxx'

Plan:ISDN, Type:National

Called Party Number i = 0xC1, '5551234'

Plan:ISDN, Type:Subscriber(local)

Locking Shift to Codeset 5

Codeset 5 IE 0x2A i = 0x808B0A, '403xxxxxxx', 0x80010A80011480011480011

4

*Feb 28 17:10:28 MST: %LINK-3-UPDOWN: Interface BRI2/0:1, changed state to up

*Feb 28 17:10:28 MST: ISDN BR2/0 Q931: TX -> CALL_PROC pd = 8 callref = 0xC1

Channel ID i = 0x89

*Feb 28 17:10:28 MST: ISDN BR2/0 Q931: TX -> CONNECT pd = 8 callref = 0xC1

Channel ID i = 0x89

*Feb 28 17:10:28 MST: ISDN BR2/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x41

Cause i = 0x82D102 - Invalid call reference value

*Feb 28 17:10:28 MST: %ISDN-6-CONNECT: Interface BRI2/0:1 is now connected to 40

3xxxxxxx

*Feb 28 17:10:28 MST: %LINK-3-UPDOWN: Interface BRI2/0:1, changed state to down

*Feb 28 17:10:28 MST: ISDN BR2/0 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x41

Cause i = 0x82D107 - Invalid call reference value

*Feb 28 17:10:28 MST: ISDN BR2/0 Q931: L3_Go: L3_GetUser_NLCB returned NULL cid

0x0 cr 0xC1 ev 0x5A ces 1 -- Message ignored

2 REPLIES
VIP Purple

Re: ISDN Q.931

Hello,

is it possible to post the configs of both routers (local and remote sides) ?

So far I could only find the document that describes the cause codes:

ISDN Switch Types, Codes, and Values

http://www.cisco.com/univercd/cc/td/doc/product/software/ssr921/dcr/24014.htm#xtocid201370

Regards,

Georg

New Member

Re: ISDN Q.931

remote_router receiving the error message on connection attempt...(this router isn't configured to dial-out at this point)

interface BRI2/0

description ISDN Backup

ip unnumbered Loopback0

encapsulation ppp

dialer idle-timeout 300

dialer-group 1

isdn switch-type basic-ni

isdn spid1 403xxxxxxx01

isdn spid2 403xxxxxxx01

ppp authentication chap callin oxioixoixoix

ppp multilink

Router making the call...using a PRI/DialerPool. I can dial and connect fine using the first ISDN Channel/SPID,. but the second one refuses to connect either as a multilink bundle, nor as a direct dial.

interface Dialer2

description Test ISDN Call

ip unnumbered FastEthernet1/0

encapsulation ppp

dialer pool 1

dialer remote-name remote_router

dialer string 403xxxxxxx

dialer caller 403xxxxxxx

dialer caller 403xxxxxxx

dialer hold-queue 10

dialer load-threshold 10 either

dialer-group 2

no peer default ip address

ppp authentication chap callin

ppp chap password 7 oxioixoixoix

ppp multilink

!

interface Serial1/0:23

ip unnumbered Loopback1

encapsulation ppp

dialer pool-member 1

isdn switch-type primary-dms100

isdn incoming-voice modem

ppp multilink

ppp timeout idle 300

multilink max-links 2

I just got off the phone with our carrier folks, and they confirm everything seems fine with the facility. Could be our PRI I'm testing from which apparently is located behind our PBX...I'll try and find a native ISDN to confirm this.

157
Views
0
Helpful
2
Replies
CreatePlease to create content