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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

AS5300 call drop problem

I am doing some testing with an application programmer who has an app that dials in from a PC to an AS5300. The PC is using a USR_Sportster modem, and the access server has a single ISDN PRI circuit. Here is the line config for the modem pool we are using:

line 4 8

no motd-banner

no exec-banner

no flush-at-activation

no vacant-message

modem Dialin

modem autoconfigure type usr_sportster

autocommand telnet HOSTNAME /quiet /noecho

transport preferred none

transport input all

transport output pad telnet rlogin udptn

escape-character NONE

telnet transparent

autohangup

dispatch-timeout 250

I can watch his PC connect (debug isdn q931) and then disconnect with the following messages:

ISDN Se0:23: TX -> DISCONNECT pd = 8 callref = 0x9DD9

Cause i = 0x8090 - Normal call clearing

ISDN Se0:23: RX <- RELEASE pd = 8 callref = 0x1DD9

ISDN Se0:23: TX -> RELEASE_COMP pd = 8 callref = 0x9DD9

He then gets a fast busy signal - like all circuits busy. Any suggestions?

Also, when I run "debug modem" I can see the access server saying "autoconfigure probe started" on each TTY line. I assume this is normal since I am using "modem autoconfigure type " in my config?

Dan

3 REPLIES
New Member

Re: AS5300 call drop problem

Wanted to include the call setup as well . . .

ISDN Se0:23: RX <- SETUP pd = 8 callref = 0x1DD9

Bearer Capability i = 0x9090A2

Channel ID i = 0xA98381

Net Specific Fac i = 0x00E2

Called Party Number i = 0xA1, '200', Plan:ISDN, Type:National

ISDN Se0:23: TX -> CALL_PROC pd = 8 callref = 0x9DD9

Channel ID i = 0xA98381

ISDN Se0:23: TX -> ALERTING pd = 8 callref = 0x9DD9

When watching the modem pool, the modem appears to connect, then the call drops and the dialing party gets a fast busy signal. Any suggestions would be greatly appreciated.

Dan

Bronze

Re: AS5300 call drop problem

Hi Dan,

I think I may have misinterpreted something in a previous message. You now mention the remote modem is a USR sportster, but what modems do you have locally (I thought the local modems were USR)?

If you do have external USR modems attached to the 5300, than the config is OK.

But if they are built-in modems (NM-xDM modules) then the modem type should be mica.

Don't know if this solves the disconnect though.

If it doesn't, try debug confmodem.

regards

Herbert

New Member

Re: AS5300 call drop problem

They are internal Mica modems. I was able to find information on CCO that helped me resolve the issue: I modified the line config to read "modem InOut" instead of just "modem In". That seemed to do the trick.

Thanks again for your input.

dk

127
Views
0
Helpful
3
Replies
CreatePlease login to create content