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

Help: Digital Modem Problem

I have a 3725 with 6 internal Digital modems.

These are accessed via 3 BRIs' assigned to an Async Interface.

The problem I am experiencing is when I use a PC/Laptop to connect to the network using a US Robotics modem the initial connection works fine, But if I hang up and dial again the digital modems assigned to the Async Interface are locked.

Issuing the "clear modem all" resets then for use again.

I have tried different O/S on the PCs' same problem, any other modem type I have tried is fine.

I have seen "web-posts" regarding firmware to recognize certain modems.

Can anybody help me, I'm going nuts

7 REPLIES
Bronze

Re: Help: Digital Modem Problem

When a digital modem is locked/stuck, do you continue to see the existence of the last call if you do a "show user" or "show caller"? Could you post the IOS version, MICA portware version and your tty lines config? What does debug modem/debug csm modem show when you intiate the next call?

~Zulfi

Community Member

Re: Help: Digital Modem Problem

To answer your questions:

When a modem is stuck/locked the user or caller doesnt show.

The IOS version is 12.3-1a

This the output of "show modem version"

Slot 1:MICA-6DM Firmware, Source - IOS

CP ver 2940 - 7/24/2002, CheckSum BB345F13.

SP ver 2940 - 7/24/2002.

MICA 0: HW Version 1.0, Serial Number 30387330.

Config:

interface Group-Async7

ip unnumbered Loopback0

encapsulation ppp

async mode interactive

peer default ip address pool XXXXXXXX

no keepalive

no fair-queue

ppp authentication pap

group-range 33 34

interface Dialer7

ip unnumbered Loopback0

encapsulation ppp

no ip mroute-cache

dialer in-band

dialer-group 1

peer default ip address pool XXXXXXXX

no fair-queue

ppp authentication chap

line 33 38

flush-at-activation

modem InOut

transport input all

transport output none

autoselect ppp

flowcontrol hardware

I dont have a firmware for the modems, hence my curiousity

Here is the result of the debug modem on the second call.

The modem should not reach Modem1/2 Mica

Mar 2 01:14:11: Modem 1/2 Mica: in modem state LINK

*Mar 2 01:14:14: Modem 1/2 Mica: in modem state RANGING

*Mar 2 01:14:16: Modem 1/2 Mica: in modem state HALF_DUPLEX_TRAIN

*Mar 2 01:14:23: Modem 1/2 Mica: in modem state TRAINUP

*Mar 2 01:14:32: Modem 1/2 Mica: in modem state EC_NEGOTIATING

*Mar 2 01:14:33: Modem 1/2 Mica: in modem state STEADY

*Mar 2 01:14:33: Modem 1/2 Mica: received ConnectInfo

*Mar 2 01:14:33: Modem 1/2 Mica: CONNECT at 42666/28800 (Tx/Rx), V90/92, LAPM,s

*Mar 2 01:14:33: TTY35: DSR came up

*Mar 2 01:14:33: tty35: Modem: IDLE->(unknown)

*Mar 2 01:14:33: TTY35: Autoselect started

*Mar 2 01:14:33: TTY35: create timer type 0, 120 seconds

*Mar 2 01:14:35: TTY35: Autoselect sample 7E

*Mar 2 01:14:35: TTY35: Autoselect sample 7EFF

*Mar 2 01:14:35: TTY35: Autoselect sample 7EFF7D

*Mar 2 01:14:35: TTY35: Autoselect sample 7EFF7D23

.

.

*Mar 2 01:14:35: TTY35: Autoselect failed

*Mar 2 01:14:35: TTY35: Line reset by "AutoSelect"

*Mar 2 01:14:35: TTY35: Modem: (unknown)->HANGUP

*Mar 2 01:14:35: TTY35: destroy timer type 0

*Mar 2 01:14:35: TTY35: no timer type 1 to destroy

*Mar 2 01:14:35: TTY35: no timer type 3 to destroy

*Mar 2 01:14:35: TTY35: no timer type 4 to destroy

*Mar 2 01:14:35: TTY35: no timer type 10 to destroy

*Mar 2 01:14:35: TTY35: no timer type 2 to destroy

*Mar 2 01:14:35: TTY35: dropping DTR, hanging up

*Mar 2 01:14:35: tty35: Modem: HANGUP->IDLE

*Mar 2 01:14:35: Modem 1/2 Mica: in modem state TERMINATING

*Mar 2 01:14:35: Modem 1/2 Mica: received TerminateInfo

*Mar 2 01:14:35: Modem 1/2 Mica: in modem state IDLE

What am I doing wrong, I know its something stupid

Bronze

Re: Help: Digital Modem Problem

Under the tty lines, put "no flush-at-activation". If this does not fix it, I would change async mode to dedicated instead of interactive under group-ascyn 7.

Last, I would move away from 12.3.1 .

FYI: Dialer 7 is not relevant here.

~Zulfi

Community Member

Re: Help: Digital Modem Problem

Still no good Zulfi.

Does my 3725 need portware version 2.9.4.0 in the flash prior to booting.

I have doen further testing and the behaviour repeats itself for Xircom modems.

All the user modems are V92 56K

Bronze

Re: Help: Digital Modem Problem

You need the 2940 portware file in flash/bootflash if you are not using the MICA code bundled in the IOS. Your SPE firmware location command is then set accordingly. So you may or may not need to have that portware in flash/bootflash prior to booting.

So this problem is only specific to Xircom modems? All other modems are not exhibiting this behaviour? If thats the case then I ll make sure you have the latest firmware from Xircom on those modems. This now sounds more like a client modem issue.

~Zulfi

Community Member

Re: Help: Digital Modem Problem

Hi again,

I've tested on more modems and the problem repeats itself.

The only working model is an Agere (Lucent) modem built into a HP laptop.

The only thing I can think of is that the modem is sending something to terminate the connection correctly.

With the other modems when I re-dial after the inital successful connection, it tries each modem in the card despite the fact they are not assigned to the Async Interface.

I'm truely puzzled

Bronze

Re: Help: Digital Modem Problem

Did you enable ppp debugs along with modem debugs? If not, please capture debug ppp nego, debug ppp chap also along with debug modem. Turn on timestamps with "service timestamps debug datetime msec".

~Zulfi

162
Views
0
Helpful
7
Replies
CreatePlease to create content