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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

isdn back up working but not in both ways

Hi all,

I need your input on this case.

I have two router configured with isdn back up:

RouterA: (Main site)

controller E1 3/0

pri-group timeslots 1-31

description ISDN# +41227828361

interface Dialer13

description ***backup to SiteB ***

ip address 192.168.240.61 255.255.255.252

encapsulation ppp

dialer pool 1

dialer remote-name siteB

dialer idle-timeout 180

dialer enable-timeout 5

dialer string 005714269405

dialer hold-queue 10

dialer-group 1

no snmp trap link-status

no cdp enable

ppp authentication chap

ppp multilink

!

RouterB (remote site)

interface BRI0/0

no ip address

dialer pool-member 2

no snmp trap link-status

isdn switch-type basic-net3

isdn T310 60000

no fair-queue

!

interface Dialer2

description BackUp link to SiteA

ip address 192.168.240.62 255.255.255.252

encapsulation ppp

dialer pool 2

dialer remote-name siteA

dialer idle-timeout 60

dialer string 00741227828361

dialer-group 1

no snmp trap link-status

no fair-queue

pulse-time 0

ppp authentication chap

ppp multilink

I can bring up the isdn back up from siteB to siteA. But not from siteA to siteB.

of cource, It is working fine with other remote sites (SiteC, ..)

(same config and same ios)

a debug isdn q931 on siteB:

SiteB#

Apr 22 08:12:46.915: ISDN BR0/0: RX <- SETUP pd = 8 callref = 0x01

Apr 22 08:12:46.919: Sending Complete

Apr 22 08:12:46.919: Bearer Capability i = 0x8890

Apr 22 08:12:46.919: Channel ID i = 0x89

Apr 22 08:12:46.923: Called Party Number i = 0x81, '5', Plan:ISDN, Type:

Unknown

Apr 22 08:12:46.927: CCBRI_Go Fr L3 pkt (Len=16) :

Apr 22 08:12:46.927: 5 1 81 90 A1 4 2 88 90 18 1 89 70 2 81 35

Apr 22 08:12:46.931:

Apr 22 08:12:46.931: ISDN BR0/0: Incoming call id = 0x0049, dsl 0

Apr 22 08:12:46.931: ISDN BR0/0: LIF_EVENT: ces/callid 1/0x49 HOST_INCOMING_CALL

Apr 22 08:12:46.935: ISDN BR0/0: HOST_INCOMING_CALL: (non-POTS) DATA

Apr 22 08:12:46.935: ISDN BR0/0: HOST_INCOMING_CALL: (1) call_type = DATA

Apr 22 08:12:46.935: ISDN BR0/0: HOST_INCOMING_CALL: voice_answer_data = FALSE c

all type is DATA

Apr 22 08:12:46.935: ISDN BR0/0: Event: Received a DATA call from <unknown> on B

1 at 64 Kb/s

Apr 22 08:12:46.935: ISDN BR0/0: Event: Accepting the call id 0x49

Apr 22 08:12:46: %DIALER-6-BIND: Interface BR0/0:1 bound to profile Di2

Apr 22 08:12:46.939: ISDN BR0/0: RM returned call_type 0 resource type 0 respons

e 1

Apr 22 08:12:46.939: CCBRI_Go Fr Host InPkgInfo (Len=9) :

Apr 22 08:12:46.943: 7 0 1 0 49 3 18 1 89

Apr 22 08:12:46.943:

Apr 22 08:12:46.947: ISDN BR0/0: isdn_send_connect(): msg 4, call id 0x49, ces 1

bchan 0, call type DATA

Apr 22 08:12:46: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up

Apr 22 08:12:46.951: ISDN: get_isdn_service_state(): idb 0x81C28E94 bchan 2 is_i

sdn 1 Not a Pri

Apr 22 08:12:46.951: CCBRI_Go Fr Host InPkgInfo (Len=6) :

Apr 22 08:12:46.951: 4 0 1 0 49 0

Apr 22 08:12:46.951:

Apr 22 08:12:46.955: ISDN BR0/0: TX -> CALL_PROC pd = 8 callref = 0x81

Apr 22 08:12:46.959: Channel ID i = 0x89

Apr 22 08:12:46.979: ISDN BR0/0: TX -> CONNECT pd = 8 callref = 0x81

Apr 22 08:12:47.067: ISDN BR0/0: RX <- CONNECT_ACK pd = 8 callref = 0x01

Apr 22 08:12:47.071: CCBRI_Go Fr L3 pkt (Len=4) :

Apr 22 08:12:47.071: F 1 81 92

Apr 22 08:12:47.075:

Apr 22 08:12:47.075: ISDN BR0/0: LIF_EVENT: ces/callid 1/0x49 HOST_CONNECT

Apr 22 08:12:47.075: ISDN BR0/0: Event: Connected to <unknown> on B1 at 64 Kb/s

Apr 22 08:12:47.075: ISDN BR0/0: RX <- RELEASE pd = 8 callref = 0x01

Apr 22 08:12:47.079: Cause i = 0x829A - Non-selected user clearing

Apr 22 08:12:52: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to 0074122

7828361 SiteA

Apr 22 08:13:07.569: ISDN BR0/0: Event: Hangup call to call id 0x49

Apr 22 08:13:07.569: ISDN BR0/0: process_disconnect(): call id 0x49, call type i

s DATA, b_idb 0x81C28E94, ces 1, cause Normal call clearing(0x10)

Apr 22 08:13:07: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected from 00741227828361 SiteA, call lasted 20 seconds

Apr 22 08:13:07.573: ISDN: get_isdn_service_state(): idb 0x81C28E94 bchan 2 is_i

sdn 1 Not a Pri

Apr 22 08:13:07.573: CCBRI_Go Fr Host InPkgInfo (Len=13) :

Apr 22 08:13:07.573: 5 0 1 0 49 3 8 1 90 8 2 80 90

Apr 22 08:13:07.573:

Apr 22 08:13:07.577: ISDN BR0/0: TX -> DISCONNECT pd = 8 callref = 0x81

Apr 22 08:13:07.581: Cause i = 0x8090 - Normal call clearing

Apr 22 08:13:07.689: ISDN BR0/0: RX <- RELEASE pd = 8 callref = 0x01

Can someone advise me what does this mean?

Cause i = 0x829A - Non-selected user clearing

I found I small explanation on the cisco website but it was not clear enough for me.

siteA is running ios 12.2.12a and site me 12.2.6c.

Thanks in advance

2 REPLIES
Cisco Employee

Re: isdn back up working but not in both ways

Here is the link which explains how to decode that isdn q931 disconnect cause codes and what are the meaning of those codes

http://www.cisco.com/warp/public/129/isdn_disc_code.html

Now from the debug, we can see that siteB have received RELEASE very quickly after CONNECT_ACK

Apr 22 08:12:47.075: ISDN BR0/0: RX <- RELEASE

I think that release is from the isdn network which forced siteB to send DISCONNECT

Apr 22 08:13:07.577: ISDN BR0/0: TX -> DISCONNECT

So need to see the debug on siteA as well about what is going on at isdn layer.

So now the question is

1)Was it working fine in the past?

2)Does that happen for all the calls?

That looks to me a local telco issue but needs to see if we see any ppp debug with that. So lets see following debug on both the sites.

debug isdn q931

debug ppp nego

New Member

Re: isdn back up working but not in both ways

hi,

1)This isdn back up is new and never worked proprely before.

2) Yes, it happens all the time

I will put a "debug isdn q931 and debug ppp nego" soon.

Thanks,

203
Views
0
Helpful
2
Replies
CreatePlease login to create content