cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
626
Views
0
Helpful
4
Replies

isdn connection problem

nenadivan
Level 1
Level 1

Hi , I configured a 1841 router for dial backup with two dialers using a single isdn line. when the main tunnels fail, dialer1 dials and connects to remote router, but dialer2 dials but drops the connection immediately.tried everything but it just wont work. here is the debug isdn from the remote router, so please help me.

debug isdn error:

0w21474836480d: ISDN Se1/0:15 SERROR: isdn_get_guid: Cannot allocate a GUID (5)

0w21474836480d: %LINK-3-UPDOWN: Interface Serial1/0:21, changed state to up

0w21474836480d: %ISDN-6-CONNECT: Interface Serial1/0:21 is now connected to 2310

9839 Sileks

0w21474836480d: %LINK-3-UPDOWN: Interface Serial1/0:21, changed state to down

0w21474836480d: ISDN Se1/0:15 SERROR: isdn_get_guid: Cannot allocate a GUID (5)

0w21474836480d: %LINK-3-UPDOWN: Interface Serial1/0:22, changed state to up

0w21474836480d: %ISDN-6-CONNECT: Interface Serial1/0:22 is now connected to 2310

9839 Sileks

0w21474836480d: %LINK-3-UPDOWN: Interface Serial1/0:22, changed state to down

0w21474836480d: ISDN Se1/0:15 SERROR: isdn_get_guid: Cannot allocate a GUID (5)

also

event:

0w21474836480d: %ISDN-6-CONNECT: Interface Serial1/0:17 is now connected to 2310

9839 Sileks

0w21474836480d: ISDN Se1/0:15 EVENT: process_rxstate: ces/callid 1/0x207 calltyp

e 1 CALL_CLEARED

0w21474836480d: %LINK-3-UPDOWN: Interface Serial1/0:17, changed state to down

0w21474836480d: ISDN Se1/0:15 EVENT: process_rxstate: ces/callid 1/0x208 calltyp

e 1 CALL_INCOMING

0w21474836480d: ISDN Se1/0:15 EVENT: call_incoming: call_id 0x0208, Guid = Se1/0

:15

0w21474836480d: ISDN Se1/0:15 EVENT: UserIdle: callid 0x208 received ACCEPT_CALL

(0x13)

0w21474836480d: %LINK-3-UPDOWN: Interface Serial1/0:18, changed state to up

0w21474836480d: ISDN Se1/0:15 EVENT: process_rxstate: ces/callid 1/0x208 calltyp

e 1 CALL_PROGRESS

0w21474836480d: ISDN Se1/0:15 EVENT: UserIdle: callid 0x208 received ISDN_HANGUP

(0x1)

0w21474836480d: %ISDN-6-CONNECT: Interface Serial1/0:18 is now connected to 2310

9839 Sileks

0w21474836480d: ISDN Se1/0:15 EVENT: process_rxstate: ces/callid 1/0x208 calltyp

e 1 CALL_CLEARED

0w21474836480d: %LINK-3-UPDOWN: Interface Serial1/0:18, changed state to down

4 Replies 4

paolo bevilacqua
Hall of Fame
Hall of Fame

Hi,

when the same isdn line is used to reach two different destination, you must use virtual-templates and pool members. Legacy dialer configuration won't work in this case.

Also, the idea of calling for backup to two different numbers is complicating things, because although possible, it is a special configuration to have the router to call one number first, then another if the first doesn't work.

I suggest you go with a single number and try to add the second, if necessary, later once the first part is working ok.

I used pool members. If the main tunnel fails, then the router must dial to two different routers (two different isdn numbers) and connect to them at the same time. The problem was with the wrong ppp chap hostname configured on the remote end router. Thanks for help

spremkumar
Level 9
Level 9

Hi

can you post the config of the main serial interface/dialer interface and the routes configured over there ??

regds

Problem solved. The ppp chap hostname was wrong on the remote end router. Thanks anyway

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card