Re: (ASCEND) Ticket #802135 - Disconnect Problems on 4048 with 7.0.1

["Steven T. Pierce" <stp@Dynasty.Net>]

I know about compatibility issues with "winmodems", particularly with
the Lucent (LT Winmodem) variety, we recommend the older rockwell zooms,
and diamond supra express as replacement modems, we don't see alot of
"getting connected" problems, those get worked out pretty easy with
firmware updates and tweaks from 56k.com and Microsoft.

The true problem seems to be a "hidden" disconnect setting of 15 minutes
(I have it set to 3600 (60 minutes) instead of 900 (which would be 15))
... others complain of a 2 minute disconnect.

Do the 100 cause codes indicate that the Max is timing out the
connection ?  Our radius profiles are also set to 3600 (60 minutes).
After we get the 120 second and 900 second bugs worked out, we are going
to implement a 1800 second (30 minute) idle timeout, but not until I can
prove that someone with out activity on a phone line with call waiting
disabled can stay connected for over 8 hours (again no activity).

Steve
stp@dynasty.net

"R. P. McCormick" wrote:

> >> I have seen problems with 33.6K modems
> >> or 56K modems that can not get a good
> >> 56K connection for what ever reason.
> >> I believe this is a problem with Ascend's
> >> V.90/K56Flex support.  These same users
> >> are able to dial into my Ascend 4000 with
> >> V.34 modems with out any problems.
> >> As soon as they attempt to dial one of the 56K
> >> servers running even just 6.1.0 or 7.0.0,
> >> they will train for ever and then hang up...
> >> Or they will connect but nothing will work.
>
> Yup.  Seen the same thing - actually first hand,
> at one of our folks residence.
>
> Situation: new telephone line, new Micron computer
> with USR Sportster modem in it.  Modem upgraded
> to v.90 (it previously was X2 only).
>
> Dialing into our 4048 boxes (we're fed with ISDN PRI's)
> the Max would answer, modem respond, tones forever
> until the line hung up.
>
> Same setup - but dial an ISP that's connected to the
> same switch and exchange our Max equipment is
> (they're using USR / 3Com) and the modem connects fine,
> in fact, with connections in excess of 33.6 kbps
> (i.e., either X2 or v.90 modulations).
>
> Disabling v.90 capabilities in the modem:
> it connects to our Max just fine ... albeit at low rates
> (24 kbps and below).
>
> Other modems (including Hayes and Zoom) were
> brought over and tested ... bit better with connects
> (at least they'd negotiate and make a connection)
> but the bit rate and throughput was poor ...
> these other modems worked fine connecting
> to the "other guys" with 3Com / USR.
>
> Upgrading the USR Sportster to the latest (stable?!)
> v.90 code made a world of difference: the modem
> would then connect when it previously had not ...
> and the connect rates were pretty similar between
> our Max'en and the other guys 3Com stuff ...
>
> But the connection quality still was extremely poor:
> lots of retrains and disconnections.  This was fixed,
> no - make that reduced/improved, by having the
> telephone company come out three times (at this
> residence) to re-engineer the line.
>
> Our experience has been that we've gotten the
> best connections with 3Com USR Courier
> v.everything modems ... followed by those units
> based on the Rockwell chipset (like the earlier Zooms).
>
> The remedy to problems like you mention above
> seems to be a combination of ensuring that the
> modem has the latest firmware in it, and ensuring
> that the phone line's quality is as best as it could be.
>
> Regards,
> Bob McCormick
>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd:   <http://www.nealis.net/ascend/faq>

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>