[nsp] AS53xx V.92 configuration not working
Cisco Geek Rotation
cisco@peakpeak.com
Sun, 18 Aug 2002 21:56:01 -0600
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
> >
> command: --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/
> > > >
> >
> >