cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
279
Views
0
Helpful
2
Replies

Problem with callback

PistuPAPP
Level 1
Level 1

Hi

I have a problem with RAS on my router.

When there is an unsuccessful callback from the router, the router is not able to answer the client's call on the same line again for a long time (approx.6 hours).

Has anybody a good idea to solve this problem?

Here is the configuraton of my router.

Thank you.

Building configuration...

Current configuration:

!

version 12.0

service exec-callback

service timestamps debug uptime

service timestamps log uptime

service password-encryption

service udp-small-servers

service tcp-small-servers

!

hostname router1

!

aaa new-model

aaa authentication login default local

aaa authentication ppp default local

aaa authorization exec default local if-authenticated

aaa authorization network default local

enable secret 5 xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.

!

username xxxxxxx callback-dialstring "" password xxxxxxxxxxxxxxxxxxxx

username xxxxxxx autocommand exit

ip subnet-zero

isdn switch-type basic-net3

chat-script reset "" "ATZ" OK "AT&FS0=1&C1&D3&B1&H1&R2&M4&K1&W" OK

chat-script cb ABORT ERROR ABORT BUSY "" "ATZ" OK "ATDT\T" TIMEOUT 30 CONNECT \c

!

!

!

interface Ethernet0/0

ip address y.z.1.2 255.255.255.0

no ip directed-broadcast

!

interface BRI0/0

ip unnumbered Ethernet0/0

no ip directed-broadcast

encapsulation ppp

dialer idle-timeout 1800 either

dialer enable-timeout 20

dialer-group 1

isdn switch-type basic-net3

peer default ip address pool isdn

ppp callback accept

ppp authentication chap

ppp multilink

ppp timeout retry 20

!

interface Group-Async1

ip unnumbered Ethernet0/0

no ip directed-broadcast

encapsulation ppp

no ip route-cache

ip tcp header-compression passive

no ip mroute-cache

dialer in-band

dialer idle-timeout 1800 either

dialer enable-timeout 20

dialer hold-queue 5

dialer-group 1

async mode interactive

peer default ip address pool modem

no fair-queue

ppp callback accept

ppp authentication chap

group-range 33 48

!

interface Dialer37

no ip address

no ip directed-broadcast

no cdp enable

!

ip local pool modem y.z.2.1 y.z.2.16

ip local pool isdn y.z.2.20 y.z.2.30

ip classless

ip route 0.0.0.0 0.0.0.0 y.z.1.1

!

access-list 99 permit y.z.1.1

access-list 110 permit ip host y.z.1.1 host y.z.1.2

access-list 110 permit tcp host y.z.1.1 any eq telnet

dialer-list 1 protocol ip permit

snmp-server community public RO 99

!

line con 0

transport input none

line 33 48

session-timeout 600

exec-timeout 0 30

timeout login response 60

autoselect during-login

autoselect ppp

script startup reset

script reset atz

script callback cb

modem InOut

no history

transport input all

autohangup

callback forced-wait 20

stopbits 1

speed 38400

flowcontrol hardware

line aux 0

line vty 0 4

access-class 110 in

password 7 xxxxxxxxxxxxxxxxxx

!

no scheduler allocate

end

2 Replies 2

tepatel
Cisco Employee
Cisco Employee

We need to see the state of the line after unsuccessful callback from router. So issue "show line x" (where x is the line number on which the call was just unsuccessful) and also "show modem" just after unsuccessful callback. Looks to me that modem and line both are stuck in active state.

Once you collect those show command, issue "clear line x" and see it makes line/modem to accept new connection faster.

Looking on the config, 30 secs is little low to get connect on modem layer. So modify cb callback script to have 60 secs to get connect.

Unfortunately - or fortunately? - this malfunction is rare. I can't send the requested list at present, because the router and modem work right now.

Thank you for your suggestion of cb callback script.

I will set it.

Review Cisco Networking for a $25 gift card