ISDN DDR Troubleshooting

Unanswered Question
Jul 14th, 2007
User Badges:

Hi,


I have a point to point link with ISDN DDR on both sides. DDR seems to be working, at least it attempts the call. The remote site is able to connect just fine. But the H.O. side can not connect.


debug isdn events gives the following:


ISDN BR1/6: received HOST_DISCONNECT call_id 0xB56A

3w2d: ISDN BR1/6: Event: Call to 065323276 was hung up.

3w2d: ISDN BR1/6: process_disc_ack(): call id 0xB56A, ces 1, call type DATA

3w2d: ISDN BR1/6: Outgoing call id = 0xB56B, dsl 14

3w2d: ISDN BR1/6: Event: Call to 065323276 at 64 Kb/s

3w2d: ISDN BR1/6: process_bri_call(): call id 0xB56B, called_number 065323276, speed 64, call type DATA

3w2d: ISDN BR1/6: received HOST_PROCEEDING call_id 0xB56B....

3w2d: ISDN BR1/6: received HOST_DISCONNECT_ACK call_id 0x80D6A71C

3w2d: ISDN BR1/6: HOST_DISCONNECT_ACK: call type is DATA.

Success rate is 0 percent (0/5)

bhemain#

3w2d: ISDN BR1/6: received HOST_DISCONNECT call_id 0xB56B

3w2d: ISDN BR1/6: Event: Call to 065323276 was hung up.

3w2d: ISDN BR1/6: process_disc_ack(): call id 0xB56B, ces 1, call type DATA

3w2d: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR1/5, TEI 105 changed to down

3w2d: ISDN BR1/6: received HOST_DISCONNECT_ACK call_id 0x80D6A71C

3w2d: ISDN BR1/6: HOST_DISCONNECT_ACK: call type is DATA

3w2d: L3: L3_GetUser_NLCB failed, message ignored cid 0x0 cr 0x27 ev 0x4D ces 1 dsl 14

3w2d: L3: L3_GetUser_NLCB failed, message ignored cid 0x0 cr 0x28 ev 0x4D ces


I also sometimes get a 'no user responding' error. Line noise? Thanks for the help in advance.


Thanks,

Prasenjit

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
spremkumar Sun, 07/15/2007 - 20:13
User Badges:
  • Red, 2250 points or more

Hi


Can you post the configurations here ?


regds


prasenjitmedhi Sun, 07/15/2007 - 21:45
User Badges:

H.O.:


hostname

ip subnet zero

isdn switch-type basic-net3

username password 0


interface bri 1/6

ip address 191.x.x.30 255.255.255.0

no ip directed-broadcast

encapsulation ppp

dialer idle-timeout 300

dialer map ip 191.10.30.29 name broadcast

dialer map ip 191.10.30.60 name broadcast

dialer-group 1

isdn switch-type basic-net3

ppp authentication chap

hold-queue 75 in


ip route 200.x.x.0 255.255.255.0 191.10.30.29



Remote Site


hostname

isdn switch-type basic-net3

username password 0

ip subnet zero


interface BRI0

ip address 191.x.x.29 255.255.255.0

ip directed-broadcast

encapsulation ppp

dialer idle-timeout 300

dialer map ip 191.10.30.30 name broadcast

dialer hold-queue 30

dialer-group 1

isdn switch-type basic-net3

no fair-queue

ppp authentication chap


ip route 200.1.x.x.255.255.0 191.10.30.30



-------


Thanks for your suggestions in advance,


Regards,

Prasenjit

spremkumar Sun, 07/15/2007 - 21:57
User Badges:
  • Red, 2250 points or more

hi


can you revert on the reason behind addressing the bri interface with a whole /24 mask ?


Are you using this link as a primary link or using this as backup for redundancy ?


regds



prasenjitmedhi Sun, 07/15/2007 - 22:08
User Badges:

Hi,


I just joined this company about 2 months ago. The last network admin used a network addressing scheme where he used Public IP's, behind a NAT with great liberty. _Terrible!!!!_networking practice, I know, but, I have not gotten approval yet to overhaul addressing in the system in entirety, yet. I'll change over to a private addressing scheme as quickly as I can. Its a bit like a SOHO network grown overly large .. But its a family owned SME .. and things move slowly .. Its not Wipro :)


This is the primary link, sir.


Thanks and regards,

Prasenjit







spremkumar Sun, 07/15/2007 - 22:41
User Badges:
  • Red, 2250 points or more

Hi


Can you post the output of debug isdn q931 ?


regds


prasenjitmedhi Sun, 07/15/2007 - 22:53
User Badges:

When H.O. dials remote:


3w3d: ISDN BR1/6: Outgoing call id = 0xB615, dsl 14

3w3d: ISDN BR1/6: Event: Call to 065323276 at 64 Kb/s

3w3d: ISDN BR1/6: process_bri_call(): call id 0xB615, called_number 065323276, s

peed 64, call type DATA

3w3d: %ISDN-6-LAYER2UP: Layer 2 for Interface BR1/6, TEI 91 changed to up

3w3d: ISDN BR1/6: TX -> SETUP pd = 8 callref = 0x53

3w3d: Bearer Capability i = 0x8890

3w3d: Channel ID i = 0x83

3w3d: Called Party Number i = 0x80, '065323276'

3w3d: ISDN BR1/6: RX <- CALL_PROC pd = 8 callref = 0xD3

3w3d: Channel ID i = 0x89

3w3d: ISDN BR1/6: received HOST_PROCEEDING call_id 0xB615.....

3w3d: ISDN BR1/6: RX <- DISCONNECT pd = 8 callref = 0xD3

3w3d: Cause i = 0x8292 - No user responding

3w3d: ISDN BR1/6: received HOST_DISCONNECT call_id 0xB615

3w3d: ISDN BR1/6: Event: Call to 065323276 was hung up.

3w3d: ISDN BR1/6: process_disc_ack(): call id 0xB615, ces 1, call type DATA

3w3d: ISDN BR1/6: TX -> RELEASE pd = 8 callref = 0x53

3w3d: Cause i = 0x60 -

3w3d: Cause i = Decode Error: len -1 overflows frame -

Decode Error: IE Length Error (0xC8)


3w3d: ISDN BR1/6: TX -> RELEASE pd = 8 callref = 0x53

3w3d: Cause i = 0x60 -

3w3d: Cause i = Decode Error: len -1 overflows frame - Service/option no

t available, unspecified

Decode Error: IE Length Error (0xF1)

3w3d: ISDN BR1/6: received HOST_DISCONNECT_ACK call_id 0x80D7B410

3w3d: ISDN BR1/6: HOST_DISCONNECT_ACK: call type is DATA

3w3d: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR1/5, TEI 105 changed to down

3w3d: ISDN BR1/6: RX <- RELEASE pd = 8 callref = 0xD3

3w3d: Cause i = 0x8292 - No user responding

3w3d: L3: L3_GetUser_NLCB failed, message ignored cid 0x0 cr 0x53 ev 0x4D ces 1

dsl 14

3w3d: ISDN BR1/6: TX -> RELEASE_COMP pd = 8 callref = 0x53

3w3d: Cause i = 0x80D1 - Invalid call reference value


Remote is able to dial into H.O. just fine.


spremkumar Mon, 07/16/2007 - 00:05
User Badges:
  • Red, 2250 points or more

Hi


Based on the disconnection code 0X8292 following are the possible reasons for the connectivity issue..


82?the public network near the local user (local telco switch)


92 - No user response


The connection fails because the destination does not respond to the call.


This cause indicates that a user does not respond to a call establishment message within the prescribed period.


The user must respond with either an alert or connect indication according to ITU-T Q.931, when either timer T303 or T310 expires.


regds


prasenjitmedhi Mon, 07/16/2007 - 00:41
User Badges:

Thanks for all the assistance Prem Kumar sir!


Could line noise be a factor? Would it hurt to ask the Telco to take a look at the remote line?


Or is it more likely some kind of funky memory/ modem chipset problem with the BRI port on the remote site or at the H.O. side, that only crops up on LCP/NCP negotiation?


The two solutions that occur to me are:


1. Try using a different router at the remote site.


2. Get the remote line checked.


Thank you for all the help and suggestions. Look forward to further feedback.

Actions

This Discussion