Problem with ISDN backup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2006 11:04 AM - edited 03-03-2019 03:00 PM
Hi,
Cisco 1721 Router
IOS: c1700-ipbasek9-mz.124-5a.bin
Config:
interface Dialer0
no description
ip address 192.168.225.238 255.255.255.252
no ip redirects
no ip unreachables
no ip proxy-arp
encapsulation ppp
no ip split-horizon
dialer pool 1
dialer remote-name cr1
dialer idle-timeout 180
dialer string <number removed>
dialer-group 1
fair-queue
no cdp enable
ppp authentication pap callin
ppp chap refuse
ppp pap sent-username <removed>
password 7 <removed>
ppp multilink bap
ppp multilink links maximum 2
ppp multilink links minimum 2
ppp multilink endpoint string client-backup
end
interface BRI0
description 6750
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
isdn point-to-point-setup
isdn calling-number 6750
fair-queue
ppp authentication chap pap
ppp multilink
end
----------------------
sh debu
The following ISDN debugs are enabled on all DSLs:
debug isdn error is ON.
debug isdn event is ON.
debug isdn silent errors is ON.
isd test call int br0 <number removed>
client-cr1#
001122: Dec 11 20:59:00.634 SAST: ISDN BR0 EVENT: UserIdle: callid 0x803C received ISDN_CALL (0x0)
001123: Dec 11 20:59:00.638 SAST: ISDN BR0 SERROR: isdn_get_guid: Cannot allocate a GUID (5)
001124: Dec 11 20:59:00.638 SAST: ISDN BR0 EVENT: process_bri_call: call id 0x803C, called_number <removed>, Guid 006243AC8262 speed 64, call type DATA, bchan -1 clng_num none
001125: Dec 11 20:59:00.638 SAST: ISDN BR0 SERROR: isdn_get_display_text_from_gtd: false ret
001126: Dec 11 20:59:00.638 SAST: ISDN BR0 SERROR: isdn_get_mlpp_from_gtd: MLPP from GTD failed
001127: Dec 11 20:59:00.666 SAST: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 89 changed to up
001128: Dec 11 20:59:00.826 SAST: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x803C calltype 1 HOST_INFORMATION
001129: Dec 11 20:59:02.542 SAST: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x803C calltype 1 HOST_PROCEEDING
001130: Dec 11 20:59:02.710 SAST: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x803C calltype 1 HOST_ALERTING
001131: Dec 11 20:59:02.734 SAST: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x803C calltype 1 HOST_CONNECT
001132: Dec 11 20:59:02.734 SAST: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
001133: Dec 11 20:59:02.734 SAST: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 00216572700 N/A
001134: Dec 11 20:59:03.550 SAST: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x803C calltype 1 HOST_DISCONNECT
001135: Dec 11 20:59:03.550 SAST: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
001136: Dec 11 20:59:03.602 SAST: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x803C calltype 1 HOST_DISCONNECT_ACK
001137: Dec 11 20:59:05.534 SAST: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 89 changed to down
What's wrong with this picture? The config looks correct to me but the darn thing wont dial.
Ideas anyone?
thanks
- Labels:
-
Other Routing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2006 11:49 AM
It looks like it is connecting, but dropping immediately.
001133: Dec 11 20:59:02.734 SAST: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 00216572700
Perhaps an authentication problem? debug ppp authentication
Please rate helpful posts.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2006 11:59 AM
Another thought is that the original post shows dialer-group 1 but does not show dialer-list 1. It would help to know if dialer-list is configured and if so what it has.
HTH
Rick
Rick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2006 12:39 PM
rick,
dialer list is configured.
dialer-list 1 protocol ip permit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2006 12:38 PM
ok ... get auth failure but username and passowrd is correct on both client router and the one they dial into.
What else can it be?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2006 04:12 AM
check out the multilink string used on either sides.
It would help if debug q931 and q921 outputs are taken.
