ISDN problems with 2516 routers

[Solarstone]

We have a 3660 with PRI , with a number of hub sites with a mixture of 1600 and 2516's with BRI's. For some reason the 2516's all refuse to dial IN to HQ automatically, where all the 1600's do. Even if I dialup HQ from a 2516 manually and drop the HQ incoming connection, the 3660 will then dial back into it within a minute or so.

The 2516's are running 12.1(8).

 

[rburke]

Have you defined access-lists on the 2516's to define what the "interesting traffic" is? Can you post a config from one of the 2516's so we can see if there are any config problems? Let us know...

Burke

 

[Solarstone]

Sure, here you go. Note this 2516 has 12.0(7) which is bug-ridden, but the other 3 we have causing the problem don't.

version 12.0
service timestamps debug datetime
service timestamps log datetime
service password-encryption
!
hostname xxxxxxxxx
!
no logging console
enable secret 5 xxxxx
enable password 7 xxxxx
!
username xxxxx password 7 xxxxx
!
!
!
!
ip subnet-zero
ip domain-list xxxxx.xxx
no ip domain-lookup
ip host cheam xx.xx.xx.xx
no ip dhcp conflict logging
ip dhcp excluded-address 10.xx.xx.xx 10.xx.xx.xx
!
ip dhcp pool localsubnet
network 10.xx.0.0 255.255.0.0
domain-name xxxx.xxx
dns-server xx.xx.xx.xx
default-router 10.xx.xx.xx
lease 3
!
isdn switch-type basic-net3
isdn voice-call-failure 0
!
!
!
hub ether 0 1
link-test
auto-polarity
!
hub ether 0 2
link-test
auto-polarity
!
hub ether 0 3
link-test
auto-polarity
!
hub ether 0 4
link-test
auto-polarity
!
hub ether 0 5
link-test
auto-polarity
!
hub ether 0 6
link-test
auto-polarity
!
hub ether 0 7
link-test
auto-polarity
!
hub ether 0 8
link-test
auto-polarity
!
hub ether 0 9
link-test
auto-polarity
!
hub ether 0 10
link-test
auto-polarity
!
hub ether 0 11
link-test
auto-polarity
!
hub ether 0 12
link-test
auto-polarity
!
hub ether 0 13
link-test
auto-polarity
!
hub ether 0 14
link-test
auto-polarity
!
interface Ethernet0
ip address 10.xx.xx.xx 255.255.0.0
no ip directed-broadcast
no ip route-cache
no ip mroute-cache
!
interface Serial0
no ip address
no ip directed-broadcast
no ip route-cache
no ip mroute-cache
shutdown
!
interface Serial1
no ip address
no ip directed-broadcast
no ip route-cache
no ip mroute-cache
shutdown
!
interface BRI0
ip address xxx.xxx.xxx.xx 255.255.255.0
no ip directed-broadcast
encapsulation ppp
no ip route-cache
no ip mroute-cache
dialer idle-timeout 240
dialer enable-timeout 8
dialer map ip xxx.xxx.xxx.xxx name xxx xxxxxxxxxx
dialer map ip xxx.xxx.xxx.xxx name xxx xxxxxxxxxx
dialer-group 1
isdn switch-type basic-net3
ppp authentication chap
!
ip classless
ip route 0.0.0.0 0.0.0.0 xxx.xxx.xxx.xxx
no ip http server
!
dialer-list 1 protocol ip permit
!
line con 0
exec-timeout 0 0
password 7 xxxxxxxxxx
login
transport input none
line aux 0
transport input all
line vty 0 4
password 7 xxxxxxxxxx
login
!
end

 

[marks66]

Is your IP route comand correct ?

This would have to be the IP Address of your PRI interface on the 3660.

Also why are there 2 dialer maps?

ISDN Debug is very useful, it generally tells you what the problems is. You will at least see if the "interesting traffic" is making a call.

Cheers
MARK
PS I Have found ISDN Dial on Demand very bug ridden with various versons of the IOS. My 2600s runs 12.1(4) this works clean with most ISDN features.

 

[Solarstone]

Yes the ip route does point to the PRI on the 3660. The 2 dialer maps are an error with my cutting and pasting, it must have overlapped in Hyperterminal !

I will try the ISDN debug and see what it throws up, thanks.