Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Callback process chat script fail on NM-16AM modem

I have problem for configuring callback from NM-16AM modem module that attached in router.

Below the configuration for the router :

aaa new-model

aaa authentication login default local group radius

aaa authentication ppp default local group radius

aaa authorization exec default local group radius

aaa authorization network default local group radius

!

aaa session-id common

ip cef

!

voice-card 0

no dspfarm

!

chat-script offhook "" "ATH1" OK

chat-script callback ABORT ERROR ABORT BUSY "" "ATZ" OK "AT" OK "ATDT \T" TIMEOUT 60 CONNECT \c

chat-script rtp ABORT ERROR ABORT BUSY "" "AT" OK "ATDT \T" TIMEOUT 45 CONNECT \c

!

username admin password 0 admin

username lili callback-dialstring "" password 0 lili

!

interface Group-Async1

ip unnumbered GigabitEthernet0/0

encapsulation ppp

ip tcp header-compression

async mode interactive

peer default ip address pool async

ppp callback accept

ppp authentication chap pap

group-range 1 1/15

!

ip local pool async 192.168.0.250 192.168.0.254

!

radius-server host 192.168.0.220 auth-port 1645 acct-port 1646

radius-server key cisco

!

line 1/0 1/14

line 1/15

session-timeout 20

exec-timeout 120 0

script modem-off-hook offhook

script callback callback

modem InOut

modem autoconfigure discovery

transport input all

autoselect during-login

autoselect ppp

callback forced-wait 5

flowcontrol hardware

I have 2 phone line that 1 one of them connected to router modem, 1 for my computer. From my computer, I can make successful dialin with/without radius server as an authentication server. But if I dialin with callback process, It stop until message "waiting callback" from my computer.

This is debug in the router :

*Mar 31 09:11:19.405: Modem 1/15 ACF: State: Init

*Mar 31 09:11:20.669: Modem 1/15 ACF: State: Idle

*Mar 31 09:11:21.029: Modem 1/15 ACF: Event: Hook state: Off Hook Dialing

*Mar 31 09:11:21.029: Modem 1/15 ACF: State: Dialing

*Mar 31 09:11:21.185: CHAT1/15: Asserting DTR

*Mar 31 09:11:21.185: Modem 1/15 ACF: CMD DTR set high

*Mar 31 09:11:21.237: Modem 1/15 ACF: Event: Hook state: On Hook

*Mar 31 09:11:21.237: Modem 1/15 ACF: Event: DISCONNECT

*Mar 31 09:11:21.237: Modem 1/15 ACF: State: Idle

*Mar 31 09:11:21.237: TTY1/15: dropping DTR, hanging up

*Mar 31 09:11:21.237: tty1/15: Modem: HANGUP->IDLE

*Mar 31 09:11:21.237: Modem 1/15 ACF: CMD DTR set low

*Mar 31 09:11:23.237: TTY1/15: restoring DTR

*Mar 31 09:11:23.237: Modem 1/15 ACF: CMD DTR set high

*Mar 31 09:11:23.237: Modem 1/15 ACF: State: Endcall

*Mar 31 09:11:23.373: Modem 1/15 ACF: Event: ENDCALL: No Previous Call

*Mar 31 09:11:23.373: Modem 1/15 ACF: State: Init

*Mar 31 09:11:24.737: Modem 1/15 ACF: State: Idle

%This command has no effect on this line; use modem AT commands instead

*Mar 31 09:11:26.185: TTY1/15 Callback process chat script fail status=Connection timed out; remote host not responding

*Mar 31 09:11:26.185: TTY1/15: Line reset by "Callback Process"

*Mar 31 09:11:26.185: TTY1/15: Modem: IDLE->HANGUP

*Mar 31 09:11:26.185: TTY1/15: no timer type 0 to destroy

*Mar 31 09:11:26.185: TTY1/15: no timer type 1 to destroy

*Mar 31 09:11:26.185: TTY1/15: no timer type 3 to destroy

*Mar 31 09:11:26.185: TTY1/15: no timer type 4 to destroy

*Mar 31 09:11:26.185: TTY1/15: destroy timer type 10

*Mar 31 09:11:26.185: TTY1/15: destroy timer type 2

*Mar 31 09:11:26.237: TTY1/15: dropping DTR, hanging up

*Mar 31 09:11:26.237: tty1/15: Modem: HANGUP->IDLE

*Mar 31 09:11:26.237: Modem 1/15 ACF: CMD DTR set low

*Mar 31 09:11:27.237: TTY1/15: restoring DTR

*Mar 31 09:11:27.237: Modem 1/15 ACF: CMD DTR set high

*Mar 31 09:11:27.237: Modem 1/15 ACF: State: Init

*Mar 31 09:11:28.501: Modem 1/15 ACF: State: Idle

*Mar 31 09:11:35.237: TTY1/15: autoconfigure probe started

Can anyone help me, what should I add or reconfigure?

Thx,

BR,

msi

1 REPLY
Silver

Re: Callback process chat script fail on NM-16AM modem

Designates a string whose presence in the input indicates that the chat script has failed.

Sets the time to wait for input, in seconds. The default is 5 seconds, and a timeout of 60 seconds is recommended for V.90 modems. If a modem reports BUSY when the number dialed is busy, you can indicate that you want the attempt stopped at this point by including ABORT BUSY in your chat script.

258
Views
0
Helpful
1
Replies
CreatePlease to create content