cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
419
Views
0
Helpful
2
Replies

ISDN Woes

philblack
Level 1
Level 1

I have a Cisco 2620 with IOS 12.0(7)XK1 with a NM-2W, 2 WIC-1B-U ISDN interfaces and the serial 0/0

is active on a frame-relay network. The ISDN blades are to serve as a backup in the event of a frame-relay outage. Initially, I had the 2 ISDN blades in the NM-2W. I was unsuccessful in receiving/placing any ISDN calls. I moved one ISDN WIC to 0/0 (off of the NM-2W) and was unsuccessful in receiving/placing

an ISDN call. I am now down to one ISDN WIC in the router (0/0) and still cannot receive/place an ISDN

call. Sho ISDN Stat returns:

Global ISDN Switchtype = basic-ni

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtype = basic-ni

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 72, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

TEI 72, ces = 1, state = 8(established)

spid1 configured, no LDN, spid1 sent, spid1 valid

Endpoint ID Info: epsf = 0, usid = 1, tid = 1

TEI Not Assigned, ces = 2, state = 3(await establishment)

spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid

Layer 3 Status:

0 Active Layer 3 Call(s)

Activated dsl 0 CCBs = 1

CCB:callid=0, sapi=0, ces=2, B-chan=0, calltype=INTERNAL

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 1

The spid 2 not sent/not valid MAY be a caveat with the 2620 and IOS 12.0(7) as I have another 2620 with the same config reporting the same issue with SPID2 and it works. In any case, I cannot

receive a call (the remote router is configured DDR), nor can I place a call.

Debug ISDN events reveals the following when trying to place a call:

*Mar 1 01:26:53.455: ISDN BR0/0: Outgoing call id = 0x8005, dsl 0

*Mar 1 01:26:53.455: ISDN BR0/0: Event: Call to 11235551212 at 64 Kb/s

*Mar 1 01:26:53.459: ISDN BR0/0: process_bri_call(): call id 0x8005, called_num

ber 11235551212, speed 64, call type DATA

*Mar 1 01:26:53.459: CC_CHAN_GetIdleChanbri: dsl 0

*Mar 1 01:26:53.459: Found idle channel B1

*Mar 1 01:26:53.463: ISDN BR0/0: TX -> SETUP pd = 8 callref = 0x05

*Mar 1 01:26:53.463: Bearer Capability i = 0x8890

*Mar 1 01:26:53.463: Channel ID i = 0x83

*Mar 1 01:26:53.463: Keypad Facility i = '13019374504'

*Mar 1 01:26:54.087: ISDN BR0/0: RX <- CALL_PROC pd = 8 callref = 0x85

*Mar 1 01:26:54.087: Channel ID i = 0x89

*Mar 1 01:26:54.091: ISDN BR0/0: received HOST_PROCEEDING call_id 0x8005

*Mar 1 01:26:54.295: ISDN BR0/0: RX <- DISCONNECT pd = 8 callref = 0x85

*Mar 1 01:26:54.295: Cause i = 0x84C1 - Bearer capability not implement

ed

*Mar 1 01:26:54.295: Signal i = 0x03 - Network congestion tone on

*Mar 1 01:26:54.299: ISDN BR0/0: TX -> RELEASE pd = 8 callref = 0x05

*Mar 1 01:26:54.299: ISDN BR0/0: received HOST_DISCONNECT call_id 0x8005

*Mar 1 01:26:54.303: ISDN BR0/0: Event: Call to 13019374504 was hung up.

*Mar 1 01:26:54.303: ISDN BR0/0: process_disc_ack(): call id 0x8005, ces 1, cal

l type DATA

*Mar 1 01:26:54.499: ISDN BR0/0: RX <- RELEASE_COMP pd = 8 callref = 0x85

*Mar 1 01:26:54.499: CC: dsl 0 No CCB Src->L3 cid 0x8005, ev 0x99 ces 1

The Telco has been out twice and both times the circuit tested good. The SPIDS are correct as is the

switch type (basic-ni). The dialer number is also correct.

HELP!

2 Replies 2

j.early
Level 1
Level 1

If you cannot make a call, I would try checking the spids. I had a router set up similarly and found that if the area code is included in the spids, it may not work. For example, if the spids are 301-555-1212-0101 and 301-555-1213-0101, I would input the spid as follows:

isdn spid1 30155512120101 5551212

isdn spid2 30155512130101 5551213

Try this and see what happens.

Tried that - no go.

Review Cisco Networking for a $25 gift card