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

ISDN Call not getting disconnected after IDLE-Timeout Expires

fmatrine
Level 1
Level 1

Dear Sir,

We have a hub and spoke WAN with all the major locations connected over leased line with isdn backup

One of our remote location has only ISDN dialup as primary connectivity.

At central location we have a citrix server which is being accessed by clients from remote locations.

Under the router configuration we have set the idel-timeout to 180 seconds.

Problem we are facing is that even after Idle-timeout setting expires call is not getting disconnected.

ISDN call is on forever.

Pls advice

-------------------------------------------------

Config for central and remote location is as below:-

-------------------------------------------------

Central#

hostname central

!

username xxxx password xxxx

isdn switch-type basic-net3

interface Loopback0

description *** Local Loopback Address ***

ip address 172.18.254.7 255.255.255.255

no ip directed-broadcast

!

interface Ethernet0

description *** CONNECTED TO LOCAL LAN ***

ip address 172.18.5.1 255.255.255.0

no ip directed-broadcast

!

interface BRI0

ip unnumbered Loopback0

no ip directed-broadcast

encapsulation ppp

dialer idle-timeout 240

dialer string XXXXXXXX

dialer-group 1

isdn switch-type basic-net3

isdn caller ISDN Number1

isdn caller ISDN Number1

isdn caller ISDN Number1

priority-group 1

ppp authentication chap

!

router eigrp 100

network 172.18.0.0

no auto-summary

!

ip route 0.0.0.0 0.0.0.0 BRI0

!

access-list 102 permit tcp any any eq 1494

priority-list 1 protocol ip high tcp 1494

dialer-list 1 protocol ip permit

-------------------------------------------

Config for remote location router:-

--------------------------------------------Remote#

hostname Remote

username central password 7 14141B180F0B

isdn switch-type basic-net3

interface Loopback0

description *** Local Loopback Address ***

ip address 172.18.254.5 255.255.255.255

!

interface BRI0

description *** 64Kbps CONNECTED TO Central***

ip unnumbered Loopback0

encapsulation ppp

dialer idle-timeout 180

dialer-group 1

isdn switch-type basic-net3

isdn caller ISDn Number 1

isdn caller ISDN Number 2

isdn caller ISDN Number 3

priority-group 1

!

interface FastEthernet0

description *** CONNECTED TO LOCAL LAN ***

ip address 172.18.4.1 255.255.255.0

speed auto

!

router eigrp 100

network 172.18.0.0

no auto-summary

no eigrp log-neighbor-changes

!

priority-list 1 protocol ip high tcp 1494

dialer-list 1 protocol ip permit

Regards

Deepak

4 Replies 4

deilert
Level 6
Level 6

your dialer list needs to be more granular. add this

access-list 101 permit ip any any log

dialer-list 1 protocol ip list 101

this will allow you to identify the traffic that is keeping the line active

Put Both ends ( Central and remote ) dialer idle-timeout 180 and check, if its not working then it might be router IOS problem.

Your problem is right here:

!

dialer-list 1 protocol ip permit

!

This makes EIGRP hellos "interesting" and will keep the link up forever. The following is the access list I use when running EIGRP:

access-list 102 deny eigrp any any

access-list 102 permit ip any any

dialer-list 1 protocol ip list 102

Note that this ONLY makes EIGRP uninteresting from the viewpoint of bringing up and keeping up calls. It has NO impact on the functioning of EIGRP on the dial link.

Good luck and have fun!

Vincent C Jones

www.networkingunlimited.com

Dear Sir,

Thanks for the prompt support

will try the listed options and get back to u

Regards

Deepak

Review Cisco Networking for a $25 gift card