1. Home
  2. Cisco Systems
  3. Isdn error Cause i = 0x8792 - No user responding

Isdn error Cause i = 0x8792 - No user responding

Helo,

I have a probleme with an interconnexion between two routeurs with isdn BRI interfaces (Cisco 2600 and a Cisco 1700).

The probleme arrive at layer 2 during the isdn connexion initialisation.

It is strange because when i launch the connexion from sig-part-b to sab-801-03 that work, but in the other sens, when i launch the connexion from sab-801-03 to sig-part-b i have an error Cause i =

0x8792 - No user responding

I tryed to use "isdn send-alerting" but without result.

Result of "show ver" :

sab-801-03#show version Cisco Internetwork Operating System Software IOS (tm) C1700 Software (C1700-Y-M), Version 12.3(18a), RELEASE SOFTWARE (fc1) Copyright (c) 1986-2007 by cisco Systems, Inc. Compiled Mon 30-Jul-07 20:42 by dchih Image text-base: 0x8000816C, data-base: 0x80A6EF38

ROM: System Bootstrap, Version 12.2(7r)XM1, RELEASE SOFTWARE (fc1)

sab-801-03 uptime is 0 minutes System returned to ROM by power-on System image file is "flash:c1700-y-mz.123-18a.bin"

cisco 1721 (MPC860P) processor (revision 0x100) with 28215K/4553K bytes of memory. Processor board ID FOC06220TGY (34635014), with hardware revision 0000 MPC860P processor: part number 0, mask 32 Bridging software. X.25 software, Version 3.0.0. Basic Rate ISDN software, Version 1.1.

1 FastEthernet/IEEE 802.3 interface(s) 1 Serial(sync/async) network interface(s) 1 ISDN Basic Rate interface(s) 32K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102

sig-part-b#show version Cisco Internetwork Operating System Software IOS (tm) C2600 Software (C2600-IS-M), Version 12.2(12c), RELEASE SOFTWARE (fc1) Copyright (c) 1986-2003 by cisco Systems, Inc. Compiled Wed 05-Feb-03 18:25 by kellythw Image text-base: 0x8000808C, data-base: 0x810CEFC0

ROM: System Bootstrap, Version 12.2(7r) [cmong 7r], RELEASE SOFTWARE (fc1)

sig-part-b uptime is 0 minutes System returned to ROM by power-on System image file is "flash:c2600-is-mz.122-12c.bin"

cisco 2610XM (MPC860P) processor (revision 0x100) with 61440K/4096K bytes of memory. Processor board ID JAD07070UKX (3688141591) M860 processor: part number 5, mask 2 Bridging software. X.25 software, Version 3.0.0. Basic Rate ISDN software, Version 1.1.

1 FastEthernet/IEEE 802.3 interface(s) 1 ISDN Basic Rate interface(s) 32K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102

Interface Configuration on sab-801-03 :

interface BRI0 ip address 10.255.255.246 255.255.255.252 encapsulation ppp dialer idle-timeout 300 dialer map ip 10.255.255.245 name sig-part-b broadcast 0159670857 dialer hold-queue 10 dialer-group 1 isdn switch-type vn3 no cdp enable ppp authentication chap

dialer-list 1 protocol ip permit

Interface Configuration on sig-part-b :

interface BRI0/0 description *** RNIS #0159670857 *** no ip address encapsulation ppp dialer pool-member 6 isdn switch-type vn3 no cdp enable ppp authentication chap ! interface Dialer2 description *** Lien sab2i *** ip address 10.255.255.245 255.255.255.252 ip nat outside encapsulation ppp dialer pool 6 dialer remote-name sab-801-03 dialer idle-timeout 300 dialer string 0159670856 dialer hold-queue 15 dialer-group 2 ppp authentication chap

I tryed a "debug isdn q931" form a connexion from sab-801-03 to sig- part-b :

sab-801-03#

*Mar 1 00:39:43.135: ISDN BR0 Q931: TX -> SETUP pd = 8 callref = 0x12 Bearer Capability i = 0x8890 Standard = CCITT Transfer Capability = Unrestricted Digital Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0x83 Shift to Codeset 6 Codeset 6 IE 0x24 i = 0x80 Called Party Number i = 0x80, '0159670857' Plan:Unknown, Type:Unknown High Layer Compat i = 0x9181 Sending Complete *Mar 1 00:39:43.507: ISDN BR0 Q931: RX
Reply to
analyne
Loading thread data ...

You don't have any SPIDs defined on the BRI adapters. These are used to determine if the call is to be answered by that device. Remember that a BRI line is like an Ethernet network, you have have multiple ISDN adapters all on the same line and the telephone number is the address. When a call comes in, it checks to see if that number is assigned to it, and if it is it accepts the call. SPIDs are only needed to receive incoming calls, not to place them. It is common not to assign SPIDs on outgoing only lines to prevent them from answering any calls, just as you are experiencing now.

Reply to
Thrill5

What are you talking about? SPID is only a crap concept of the US ISDN network. If you had noticed:

isdn switch-type vn3

You would realize that this is not being used in the US on a broken ISDN implementation that requires "SPIDs". I think "No user responding" is pretty clear and it probably means the remote end is not picking up the call properly for some reason. I'll leave the rest up to the OP to figure out.

Reply to
B. Wright

Reply to
Thrill5

Please see what one of the others who followed up stated. SPIDs are irrelevant in this situation because they are not used outside of the US (or North America). In most other countries there are notions of "MSN" or similiar, "Multiple Subscriber Number". Most equipment, especially that which is usually not on a shared line, will pick up on the "Broadcast MSN" regardless. They really don't care, or need to know, their own number to answer a call.

My main point was this, if you tell him "check the SPIDs" and he listens, you are just wasting time and confusing the issue, so, it's bad advice.

I don't think the OP posted enough to really know what was going on anyway but the caller ID on the receiving end looked screwy/truncated and maybe that was a symptom of his actual problem (wrong switch type).

PS: basic-net3 switch type doesn't use SPIDs either.

Reply to
B. Wright

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.