10-06-2004 05:50 AM
Hi,
I have cisco 2610xm as access server with external analog modem (hayes accura 336 message modem) in aux ports but i can dial. When i debug i have the following :
10-06-2004 07:43 AM
Do you mean you CANNOT dial? The configs look ok, can you capture outputs for the following debugs:
deb dialer event/ deb chat / deb modem / deb ppp nego.
Thanks, Mak
10-06-2004 09:38 AM
10-06-2004 06:02 PM
From the debugs we see that the remote modem is not responsing, the router is initiating a callout:
*Mar 1 00:36:19.848: As65 DDR: Attempting to dial 0805010143
*Mar 1 00:36:19.848: CHAT65: Attempting async line dialer script
*Mar 1 00:36:19.848: CHAT65: Dialing using Modem script: dialout & System scrip
t: none
*Mar 1 00:36:19.848: CHAT65: process started
*Mar 1 00:36:19.848: CHAT65: Asserting DTR
*Mar 1 00:36:19.848: CHAT65: Chat script dialout started
*Mar 1 00:36:19.852: CHAT65: Sending string: AT
*Mar 1 00:36:19.852: CHAT65: Expecting string: OK
*Mar 1 00:36:24.852: CHAT65: Timeout expecting: OK
*Mar 1 00:36:24.852: CHAT65: Chat script dialout finished, status = Connection timed out; remote host not responding <====
*Mar 1 00:36:24.852: As65 DDR: disconnecting call
Ensure the number you are calling is correct.
Try calling your cell phone or a phone near by & see if you hear the phone ring.
Thanks, Mak
10-07-2004 12:56 AM
Thanks,Mak.Please help.I change the phone number but still no dial.
I have the following now :
router3#telnet 172.16.0.7
Trying 172.16.0.7 ...
*Mar 1 15:53:00.121: As65 DDR: rotor dialout [priority]
*Mar 1 15:53:00.121: As65 DDR: Dialing cause ip (s=172.16.0.244, d=172.16.0.7)
*Mar 1 15:53:00.121: As65 DDR: Attempting to dial 0633729567
*Mar 1 15:53:00.121: CHAT65: Attempting async line dialer script
*Mar 1 15:53:00.121: CHAT65: Dialing using Modem script: dialout & System scrip
t: none
*Mar 1 15:53:00.125: CHAT65: process started
*Mar 1 15:53:00.125: CHAT65: Asserting DTR
*Mar 1 15:53:00.125: TTY65: Set DTR to 1
*Mar 1 15:53:00.125: CHAT65: Chat script dialout started
*Mar 1 15:53:00.125: CHAT65: Sending string: AT
*Mar 1 15:53:00.125: CHAT65: Expecting string: OK
*Mar 1 15:53:05.125: CHAT65: Timeout expecting: OK
*Mar 1 15:53:05.125: CHAT65: Chat script dialout finished, status = Connection
timed out; remote host not responding
*Mar 1 15:53:05.125: TTY65: Line reset by "Async dialer"
*Mar 1 15:53:05.125: As65 DDR: disconnecting call
*Mar 1 15:53:05.125: TTY65: Modem: (unknown)->HANGUP
*Mar 1 15:53:05.125: TTY65: no timer type 0 to destroy
*Mar 1 15:53:05.125: TTY65: no timer type 1 to destroy
*Mar 1 15:53:05.125: TTY65: no timer type 3 to destroy
*Mar 1 15:53:05.125: TTY65: no timer type 4 to destroy
*Mar 1 15:53:05.125: TTY65: no timer type 2 to destroy
*Mar 1 15:53:05.486: TTY65: dropping DTR, hanging up
*Mar 1 15:53:05.486: TTY65: Set DTR to 0
*Mar 1 15:53:05.486: tty65: Modem: HANGUP->IDLE
*Mar 1 15:53:07.497: TTY65: restoring DTR
*Mar 1 15:53:07.497: TTY65: Set DTR to 1
*Mar 1 15:53:09.127: Di65: No free dialer - starting fast idle timer
*Mar 1 15:53:20.126: As65 DDR: re-enable timeout
*Mar 1 15:53:20.126: As65 DDR: Attempting to dial 0033320273825
*Mar 1 15:53:20.126: CHAT65: Attempting async line dialer script
*Mar 1 15:53:20.126: CHAT65: Dialing using Modem script: dialout & System scrip
t: none
*Mar 1 15:53:20.126: CHAT65: process started
*Mar 1 15:53:20.126: CHAT65: Asserting DTR
*Mar 1 15:53:20.126: TTY65: Set DTR to 1
*Mar 1 15:53:20.126: CHAT65: Chat script dialout started
*Mar 1 15:53:20.126: CHAT65: Sending string: AT
*Mar 1 15:53:20.130: CHAT65: Expecting string: OK
*Mar 1 15:53:21.127: Di65: No free dialer - starting fast idle timer
*Mar 1 15:53:25.130: CHAT65: Timeout expecting: OK
*Mar 1 15:53:25.130: CHAT65: Chat script dialout finished, status = Connection
timed out; remote host not responding
*Mar 1 15:53:25.130: TTY65: Line reset by "Async dialer"
*Mar 1 15:53:25.130: As65 DDR: disconnecting call
*Mar 1 15:53:25.130: TTY65: Modem: (unknown)->HANGUP
*Mar 1 15:53:25.130: TTY65: no timer type 0 to destroy
*Mar 1 15:53:25.130: TTY65: no timer type 1 to destroy
*Mar 1 15:53:25.130: TTY65: no timer type 3 to destroy
*Mar 1 15:53:25.130: TTY65: no timer type 4 to destroy
*Mar 1 15:53:25.130: TTY65: no timer type 2 to destroy
*Mar 1 15:53:25.530: TTY65: dropping DTR, hanging up
*Mar 1 15:53:25.530: TTY65: Set DTR to 0
*Mar 1 15:53:25.530: tty65: Modem: HANGUP->IDLE
*Mar 1 15:53:27.542: TTY65: restoring DTR
*Mar 1 15:53:27.542: TTY65: Set DTR to 1
*Mar 1 15:53:40.130: As65 DDR: re-enable timeout
% Connection timed out; remote host not responding
what means "No free dialer - starting fast idle timer"?
Thanks.
10-08-2004 07:59 AM
Actually, the router is not able to talk to modem. so whe it sends AT command, its not getting OK from modem.
Now remove "dialer pool-mem 20" from the async65 and remove "interface dialer 65". Now configure the interface async 65 like following
interface Async65
ip unnumbered FastEthernet0/0
encapsulation ppp
dialer in-band
dialer idle-timeout 900
dialer string 0805010143
dialer string 0320281282
dialer-group 1
no cdp enable
async default routing
async mode interactive
!
ip classless
ip route 0.0.0.0 0.0.0.0 Async65
ip route 172.16.0.6 255.255.255.255 Async65
ip route 172.16.0.7 255.255.255.255 Async65
Also enter following command under the line 65
line 65
modem autoconfigure discovery
After that issue "clear line 65". That will force router to detect a modem. After that try to dialout and see the results,
10-08-2004 04:06 PM
Reverse telnet into the modem (telnet 172.16.0.244 2065) and see if you get an OK back from your Hayes when you type in AT. If you do , go ahead and initiate a manual dial by doing an "atdt 0633729567". If you do not see your modem connecting to the other side, its probably that modem which is at fault. While in the reverse telnet mode it may also help to provide your Hayes modem a good init string like : &FS0=1&Q9&C1&D3 .
Check the following for more on that :
ASYNCHRONOUS SERIAL AND MODEM COMMUNICATIONS
Modem-Router Connection Guide
http://www.cisco.com/en/US/tech/tk801/tk36/technologies_tech_note09186a008009428b.shtml
~Zulfi
11-04-2004 02:14 AM
Thanks Zulfi.I changed my modem.Now i have a WIC-2AM.Here is my new config :
router3#sh run
Building configuration...
Current configuration : 1553 bytes
!
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname router3
!
logging buffered 48000 debugging
!
ip subnet-zero
no ip source-route
!
!
no ip domain-lookup
!
isdn switch-type basic-net3
chat-script dialout "" "AT" OK "ATDT\T" TIMEOUT 30 CONNECT \C
!
interface FastEthernet0/0
ip address 172.16.0.244 255.255.255.0
no ip mroute-cache
no keepalive
shutdown
duplex auto
speed auto
no cdp enable
!
interface BRI1/0
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/1
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/2
no ip address
shutdown
isdn switch-type basic-net3
!
interface BRI1/3
no ip address
shutdown
isdn switch-type basic-net3
!
interface Async1
ip unnumbered FastEthernet0/0
encapsulation ppp
dialer in-band
dialer idle-timeout 900
dialer string 00805010142
dialer-group 1
async default routing
async mode interactive
no peer default ip address
no fair-queue
!
interface Async2
no ip address
!
ip classless
ip route 172.16.0.0 255.255.255.0 Async1
no ip http server
ip pim bidir-enable
!
!
access-list 1 permit 172.16.0.0 0.0.0.255
dialer-list 1 protocol ip permit
!
line con 0
line 1
script dialer dialout
modem InOut
transport input all
transport output pad v120 telnet rlogin udptn
autoselect ppp
stopbits 1
speed 115200
flowcontrol hardware
line 2
stopbits 1
speed 115200
line aux 0
line vty 0 4
login
!
!
end
When i debug i have :
router3#telnet 172.16.0.171
Trying 172.16.0.171 ... Modem Registers - IMR:0x0 LED:0x0 RstCntrl:0x0 MSR:0xFF
*Mar 15 23:25:56.404: As1 DDR: place call
*Mar 15 23:25:56.404: As1 DDR: Dialing cause ip (s=172.16.0.244, d=172.16.0.171)
*Mar 15 23:25:56.404: As1 DDR: Attempting to dial 00805010142
*Mar 15 23:25:56.404: CHAT1: Attempting async line dialer script
*Mar 15 23:25:56.408: CHAT1: Dialing using Modem script: dialout & System script
: none
*Mar 15 23:25:56.408: CHAT1: process started
*Mar 15 23:25:56.408: CHAT1: Asserting DTR
*Mar 15 23:25:56.408: CHAT1: Chat script dialout started
*Mar 15 23:25:56.408: CHAT1: Sending string: AT
*Mar 15 23:25:56.408: CHAT1: Expecting string: OK
*Mar 15 23:25:56.412: CHAT1: Completed match for expect: OK
*Mar 15 23:25:56.412: CHAT1: Sending string: ATDT\T<00805010142>
*Mar 15 23:25:56.412: CHAT1: Expecting string: CONNECT
*Mar 15 23:26:26.414: CHAT1: Chat script dialout finished, status = Connection t
imed out; remote host not responding
*Mar 15 23:26:26.414: TTY1: Line reset by "Async dialer"
*Mar 15 23:26:26.414: As1 DDR: disconnecting call
*Mar 15 23:26:26.414: TTY1: Modem: (unknown)->HANGUP
*Mar 15 23:26:26.414: TTY1: no timer type 0 to destroy
*Mar 15 23:26:26.414: TTY1: no timer type 1 to destroy
*Mar 15 23:26:26.414: TTY1: no timer type 3 to destroy
*Mar 15 23:26:26.414: TTY1: no timer type 4 to destroy
*Mar 15 23:26:26.414: TTY1: no timer type 2 to destroy
*Mar 15 23:26:27.191: TTY1: dropping DTR, hanging up
*Mar 15 23:26:27.191: tty1: Modem: HANGUP->IDLE
*Mar 15 23:26:27.203: Modem (0/0) DCD UnAsserted
*Mar 15 23:26:27.203: Modem (0/0) CTS UnAsserted
*Mar 15 23:26:27.387: Modem (0/0) DCD Asserted
*Mar 15 23:26:27.387: Modem (0/0) CTS UnAsserted
*Mar 15 23:26:29.202: TTY1: restoring DTR
*Mar 15 23:26:30.208: TTY1: DSR was dropped
*Mar 15 23:26:30.208: TTY1: Quickly dropping DTR
*Mar 15 23:26:30.208: tty1: Modem: READY->HASPROC
*Mar 15 23:26:31.209: TTY1: restoring DTR
I dial well but still have message : Connection t
imed out; remote host not responding
What wrong ?
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide