cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
277
Views
0
Helpful
3
Replies

DDR issue with CS2621 chasis and 12.2(6c) IOS

mgrigore
Level 1
Level 1

I have IOS c2600-js-mz.122-6c on a 2621 chasis and I am trying to make it dial out on the BRI interface. I have set 2 BRIs together to back the leased line.

The dial does NOT work and what is puzzling me is the foll line:

Jan 27 16:53:12 UTC: ISDN: get_isdn_service_state(): idb 0x8217E990 bchan 2 is_isdn 1 Not a Pri

The complete debug looks like foll :

Jan 27 16:53:12 UTC: BR1/1 DDR: Dialing cause ip (s=xx.xx.xx.xx, d=yy.yy.yy.yy)

Jan 27 16:53:12 UTC: BR1/1 DDR: Attempting to dial 2883752

Jan 27 16:53:12 UTC: ISDN BR1/1: Outgoing call id = 0x8070, dsl 9

Jan 27 16:53:12 UTC: ISDN BR1/1: Event: Call to 2883752 at 64 Kb/s

Jan 27 16:53:12 UTC: ISDN BR1/1: process_bri_call(): call id 0x8070, called_number 2883752, speed 64, call type DATA

Jan 27 16:53:12 UTC: CCBRI_Go Fr Host InPkgInfo (Len=22) :

Jan 27 16:53:12 UTC: 1 9 1 80 70 0 4 2 88 90 18 1 83 2C 7 32 38 38 33 37 35 32

Jan 27 16:53:12 UTC:

Jan 27 16:53:12 UTC: CC_CHAN_GetIdleChanbri: dsl 9

Jan 27 16:53:12 UTC: Found idle channel B1

Jan 27 16:53:12 UTC: ISDN BR1/1: trigger_calling_called_debug, dsl 9, callref 0x41, outgoing TRUE

Jan 27 16:53:12 UTC: CCBRI_Go Fr L3 pkt (Len=32) :

Jan 27 16:53:12 UTC: 2 1 41 98 18 1 89 95 2A 16 80 88 7 32 38 38 33 37 35 32 80 1 D 80 1 14 80 1 14 80 1 14

Jan 27 16:53:12 UTC:

Jan 27 16:53:12 UTC: ISDN BR1/1: LIF_EVENT: ces/callid 1/0x8070 HOST_PROCEEDING

Jan 27 16:53:12 UTC: ISDN BR1/1: HOST_PROCEEDING

Jan 27 16:53:12 UTC: ISDN BR1/1: HOST_MORE_INFO

Jan 27 16:53:12 UTC: CCBRI_Go Fr L3 pkt (Len=8) :

Jan 27 16:53:12 UTC: 45 1 41 96 8 2 82 EF

Jan 27 16:53:12 UTC:

Jan 27 16:53:12 UTC: ISDN BR1/1: LIF_EVENT: ces/callid 1/0x8070 HOST_DISCONNECT

Jan 27 16:53:12 UTC: ISDN BR1/1: Event: Call to 2883752 was hung up.

Jan 27 16:53:12 UTC: ISDN BR1/1: process_disc_ack(): call id 0x8070, ces 1, call type DATA cause 0x0

Jan 27 16:53:12 UTC: ISDN: get_isdn_service_state(): idb 0x8217E990 bchan 2 is_isdn 1 Not a Pri

Jan 27 16:53:12 UTC: BRI1/1: wait for isdn carrier timeout, call id=0x8070

Can you please help me understand what could be wrong???

To mention something: I cannot see any Q931 messages, which seems very odd to me. Could I face a switch which is not configured properly???

Please advise me.

3 Replies 3

tepatel
Cisco Employee
Cisco Employee

Try to bounce the bri line using "shut and no shut" or "clear interface bri x/y"

and see if that makes any difference..I assume "sh isdn status" reports good layer 2 status and no calls at layer 3.

You can also try "isdn call interface bri x/y " command from the router to dialout avoiding the DDR stack to test the outgoing call.

I have changed the switch type WITHOUT reloading router, as it was not possible at the time.

I have just reloaded the router and now I can see Q921 an Q931 messages when doing a debug. So, it looks like the reload has cleared the issue. It seems that the ISDN switch type change MUST be done with a router reload... I know CISCO recommends clear int bri and shut/no shut when reload is not an option, but I now think reload is the best solution...

Thanx, Mihai

You can get away with realod as well. When you mis-configure the switch-type and if you want to change it, just "shutdown" the bri line and change the swith-type, After that "no shut" under the bri intrface should do the job..

Reload is the last weapon..

Review Cisco Networking for a $25 gift card