ISDN Backup Problem

Unanswered Question
Jul 2nd, 2008

I have a problem with one of our ISDN backup lines. The primary connection to the remote site is a serial interface which we shut down periodically to test the isdn comes up using a floating static route. An engineer has tested the line and reported no problems so we know its operational. I've done some debugging which is below.

*Apr 5 02:30:46.676: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, c

hanged state to down

*Apr 5 02:30:49.464: ISDN BR0: RX <- RRp sapi = 0 tei = 116 nr = 29

*Apr 5 02:30:49.472: ISDN BR0: TX -> RRf sapi = 0 tei = 116 nr = 107

*Apr 5 02:30:52.484: ISDN BR0: Outgoing call id = 0x88E8

*Apr 5 02:30:52.488: ISDN BR0: Event: Call to 801756793780 at 64 Kb/s

*Apr 5 02:30:52.500: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 29 nr =

107 i = 0x0801790504028890180183700D80383031373536373933373830

*Apr 5 02:30:52.504: SETUP pd = 8 callref = 0x79

*Apr 5 02:30:52.508: Bearer Capability i = 0x8890

*Apr 5 02:30:52.512: Channel ID i = 0x83

*Apr 5 02:30:52.512: Called Party Number i = 0x80, '801756793780'

*Apr 5 02:30:52.556: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 30

*Apr 5 02:30:52.716: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 107 nr =

30 i = 0x0801F90218018A

*Apr 5 02:30:52.720: CALL_PROC pd = 8 callref = 0xF9

*Apr 5 02:30:52.720: Channel ID i = 0x8A

*Apr 5 02:30:52.732: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 108

*Apr 5 02:30:52.736: ISDN BR0: received HOST_PROCEEDING call_id 0x88E8

*Apr 5 02:30:52.896: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 108 nr =

30 i = 0x0801F94508028AD8

*Apr 5 02:30:52.896: DISCONNECT pd = 8 callref = 0xF9

*Apr 5 02:30:52.900: Cause i = 0x8AD8 - Incompatible destination

*Apr 5 02:30:52.912: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 109

*Apr 5 02:30:52.920: ISDN BR0: received HOST_DISCONNECT call_id 0x88E8

*Apr 5 02:30:52.920: ISDN BR0: Event: Call to 801756793780 was hung up.

*Apr 5 02:30:52.932: BR0:2 LCP: State is Closed

*Apr 5 02:30:52.936: BR0:2 PPP: Phase is DOWN

*Apr 5 02:30:52.940: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 30 nr =

109 i = 0x0801794D080380E408

*Apr 5 02:30:52.944: RELEASE pd = 8 callref = 0x79

*Apr 5 02:30:52.948: Cause i = 0x80E408 - Invalid IE contents

*Apr 5 02:30:52.984: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 31

*Apr 5 02:30:53.016: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 109 nr =

31 i = 0x0801F95A

*Apr 5 02:30:53.020: RELEASE_COMP pd = 8 callref = 0xF9

*Apr 5 02:30:53.028: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 110

*Apr 5 02:30:53.985: ISDN BR0: Outgoing call id = 0x88E9

*Apr 5 02:30:53.989: ISDN BR0: Event: Call to 801756793780 at 64 Kb/s

*Apr 5 02:30:54.001: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 31 nr =

110 i = 0x08017A0504028890180183700D80383031373536373933373830

*Apr 5 02:30:54.009: SETUP pd = 8 callref = 0x7A

*Apr 5 02:30:54.009: Bearer Capability i = 0x8890

*Apr 5 02:30:54.013: Channel ID i = 0x83

*Apr 5 02:30:54.017: Called Party Number i = 0x80, '801756793780'

*Apr 5 02:30:54.065: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 32

*Apr 5 02:30:54.217: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 110 nr =

32 i = 0x0801FA0218018A

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Pravin Phadte Wed, 07/02/2008 - 03:58

Hi,

I am soory but still its not clear what u are looking for.

1. The logs are from remote router ?

2. what output are u looking for?

3 Can you have the test again with below outputs ?

show isdn status

debug isdn q921

and

debug isdn q931 ( both debug seperately)

also if you can paste the configs of the remote and primary router would be helpful.

Regrads,

Pravin

darrenriley5 Wed, 07/02/2008 - 05:44

Sorry the logs are from the remote router. Having not dealt with ISDN before I'm just trying to establish exactly why the isdn line won't come up. This has been working fine and no changes have been. Dialing from the headoffice router to remote router works fine. Also we can dial from the remote router to a test router we have set up at head office.The number is correct. I have attached the configs as requested. Any help is much appreciated.

spremkumar Wed, 07/02/2008 - 04:53

Hi Darren

from the logs posted out here this is the possible reason for the disconnection.

D8

Incompatible destination

This cause indicates an attempt to connect to non-ISDN equipment. For example, an analog line.

This cause indicates that the equipment receives a request to establish a call that has a low layer compatibility, high layer compatibility, or other compatibility attributes (for example, data rate) that the equipment cannot accommodate.

This code often appears when the calling device dials the wrong number, and reaches a non-ISDN device. Therefore, ensure that you dial the correct number.

This cause can also occur when a a data call is made to a voice number, or a voice call is made to a number that only supports data. If the number is correct, check whether the telco has configured their switch incorrectly.

regds

nagatayoshio Thu, 07/03/2008 - 17:13

Calling-line id notice isn't made of Cisco813 to a center router at present,

so it's in the state which can't be connected.

When there is a command you notify of a caller ID in Cisco813, please tell me.

Actions

This Discussion