The modem autoconfigure code is ALMOST platform independent (except
that the 5800 [and maybe the 5850?] does some task queueing for
scalability's sake.) We have seen some autoconfig failures on
the high-end platforms (5800, 5850) for very long config strings,
which we believe we can work around by boosting autoconfigure's
read timeout (CSCdy00247).
However none of this would seem to be relevant to the issue raised
below, since it's talking about a 5300, not a 58xx, and about a
short modemcap (e.g. &F&D2S63=3), not a long one. So I believe
that this is not a modemcap issue but a modem AT syntax issue -
so let's zoom into the particulars.
Chris has an AS5300 running 12.2(2)XA5 and MICA portware 2.9.2.0.
He's trying to send a modemcap of:
&F&D2S62=8S63=3S21=15S29=12S34=18000S40=10S54=456S10=50S71=4, but this is
(I presume) being rejected by the MICA AT parser.
I think I'll spare everyone an exegesis of these S registers
(I suspect that the cisco-nsp folk in particular would find the
topic sub-fascinating).
Here are the modemcaps I'm currently recommending for MICA 2.9.2.0:
Recommended modemcap for 2.9.2.0 in a V.92/V.44 application:
&F&D2S54=16584S0=0S29=12S21=15S62=8S63=3S34=18000S40=10S10=50
S54=16584 Enable V.92 (16384) + 200 (default)
S0=0 Do not delay answerback tone (CSCdw05174)
S29=12 Enable V.92
S21=15 Enable V.44, V.42bis, MNP5 compression
S62=8 Maximum MoH time 4 minutes (or whatever the customer wants)
S63=3 Enable V.92 QC ANSpcm at -12dBm
S34=18000 Upshift after 3 good minutes (default: 2000 [20 seconds])
S40=10 Disconnect after 10 consecutive retrains (default: 4)
S10=50 Disconnect after a 5-second loss of carrier (default: 14 [1.4 seconds])
Recommended modemcap for 2.9.2.0 in a non-V.92 application:
&F&D2S0=0S29=6S21=3S34=18000S40=10S10=50
I'm sorry that we haven't yet updated the CCO page
http://www.cisco.com/warp/public/471/recc_modemcaps.html#12 with this information. We decided to hold off on the update
because we're about to post 2.9.4.0 there (at any rate, I
*think* we are ... I'll check.)
Regards,
Aaron
---
> im decently sure that the modem autoconfig code is independent of
> platform/modems.
> hopefully someone smarter then me will comment.
> joshd
> ====
> Hey Josh:
> I can't find this above-referenced DDT.
> What is the workaround? V.92 doesn't work at all, this condition occurs
> for every modem on multiple chassis (I tried another one already).
> >dup'd to:
> >
> >CSCdw78376 R UP324 - modem configuration failing for some ports
> >Version:12.2(02)XB03 Integrated:12.2(11.05)GLD 12.2(11.05)T 12.2(10.07)T04
> >12.2(02)XB06
> This says it is a 5850, I'm using 53xx stuff:
> ---
> · CSCdw78376
> Symptoms A modem configuration (using deb confmodem) may fail.
> Conditions This symptom is observed on a Cisco AS5850 access server when
> using modemcap to modify the nextport register configuration.
> Workaround Apply the same modemcap from a reverse telnet to the nextport.
> ---
> Chris
> >adding in cisco-nas just in case im wrong.
> >
> >joshd
> >
> >----- Original Message -----
> >From: "Cisco Geek Rotation" <cisco@peakpeak.com>
> >To: "Charles Sprickman" <spork@inch.com>; <cisco-nsp@puck.nether.net>
> >Sent: Sunday, August 18, 2002 10:56 PM
> >Subject: Re: [nsp] AS53xx V.92 configuration not working
> >
> >
> > > At 06:32 PM 8/18/2002 -0400, Charles Sprickman wrote:
> > > >I'm out of my league here, but it does seem to be barfing on the init
> > > >string. Does it do the same with something simple like "&F"?
> > > >
> > > >Charles
> > >
> > > Good idea.
> > >
> > > No it doesn't, here are some experiments I tried:
> > >
> > > Original string (FAILS):
> > > modemcap edit cisco misc
> > >
> &F&D2S62=8S63=3S21=15S29=12S34=18000S40=10S54=456S10=50debugthismodemS71=4
> > >
> > >
> > > These work:
> > >
> > > modemcap edit cisco misc &F WORKS
> > >
> > > modemcap edit cisco misc &F&D2 WORKS
> > >
> > > These all fail:
> > >
> > > modemcap edit cisco misc &F&D2S62=8 FAILS
> > >
> > > modemcap edit cisco misc &F&D2S63=3 FAILS
> > >
> > > modemcap edit cisco misc &F&D2S21=15 FAILS
> > >
> > > So it seems to have something to do with any of the S-register commands
> > > that do something with V.92 as documented here:
> > >
> > > http://www.cisco.com/warp/public/471/v92_21360.html
> > >
> > > Here's what's in flash, according to all the documentation this is the
> >code
> > > to run, so I'm puzzled as to what the problem could be.
> > >
> > > #show flash
> > >
> > > System flash directory:
> > > File Length Name/status
> > > 1 9807020 c5300-ds-mz.122-2.XA5.bin
> > > 2 465726 mica-modem-pw.2.9.2.0.bin
> > > [10272876 bytes used, 6504340 available, 16777216 total]
> > > 16384K bytes of processor board System flash (Read/Write)
> > >
> > > And the code is loading into the modems (SPEs):
> > >
> > > #show modem ver
> > >
> > > Codes:
> > > d - DSP software download is required for achieving K56flex
> connections
> > >
> > > Modem module Firmware Boot DSP
> > > Mdm Number Rev Rev Rev
> > > 1/0 0 2.9.2.0
> > > <snip>
> > >
> > >
> > > Chris
> > >
> > >
> > >
> > > >--
> > > >Charles Sprickman
> > > >spork@inch.com
> > > >
> > > >
> > > >On Sun, 18 Aug 2002, Cisco Geek Rotation wrote:
> > > >
> > > > > At 02:03 PM 8/18/2002 -0400, you wrote:
> > > > > >On Sun, 18 Aug 2002, Cisco Geek Rotation wrote:
> > > > > >
> > > > > > >
> > > >
> >&F&D2S62=8S63=3S21=15S29=12S34=18000S40=10S54=456S10=50debugthismodemS71=4
> > > > > >
> >^^^^^^^^^^^^^^
> > > > > >
> > > > > >I'm no cisco modem expert, but what happens if you remove the above
> > > > > >portion of the init string?
> > > > >
> > > > > Pretty much the same thing:
> > > > >
> > > > > Aug 18 18:43:57.846: TTY89: Modem
> > > > > command:
> > > >
> > > --AT&F&D2S62=8S63=3S21=15S29=12S40=10S54=456S10=50debugthismodemS71=4--
> > > > > Aug 18 12:44:00: %TTY-3-AUTOCONFIG: TTY89: Modem auto-configuration
> >failed
> > > > >
> > > > >
> > > > > >Also try to debug this with "debug confmodem".
> > > > >
> > > > >
> > > > > Here is what I get:
> > > > >
> > > > > Aug 18 18:30:49.446: TTY160: detection speed (115200)
> >response ---OK---
> > > > > Aug 18 18:30:49.446: TTY160: Modem
> > > > >
> > > >
> >ommand: --AT&F&D2S62=8S63=3S21=15S29=12S34=18000S40=10S54=456S10=50S71=4--
> > > > > Aug 18 12:30:51: %TTY-3-AUTOCONFIG: TTY160: Modem auto-configuration
> >failed
> > > > >
> > > > > Not the treasure trove of info I was expecting! :)
> > > > >
> > > > > Chris
> > > > >
> > > > >
> > > > > >Charles
> > > > > >
> > > > > > > line 1 192
> > > > > > > exec-timeout 0 0
> > > > > > > no flush-at-activation
> > > > > > > modem Dialin
> > > > > > > modem autoconfigure type cisco
> > > > > > > transport input all
> > > > > > > autoselect during-login
> > > > > > > autoselect ppp
> > > > > > > ----
> > > > > > >
> > > > > > > So why is it that the modems are failing to initialize with this
> > > > > > > modemcap? Thanks for any hints.
> > > > > > >
> > > > > > > Chris
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > cisco-nsp mailing list real_name)s@puck.nether.net
> > > > > > > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > > > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > > > > > >
> > > > >
> > > > >
> > >
> > >
> > > _______________________________________________
> > > cisco-nsp mailing list real_name)s@puck.nether.net
> > > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > >