Re: (ASCEND) A follow up on 'bad' calls...

["Peter Rocca" <rocca@multiboard.com>]

> I don't think the second part is true.  If the user finished modem
> handshaking and got a chance to try and authenticate (be it that the
> user failed authentication), the call should not be flagged as bad since

Version 8.x even words it stronger:

  "Note: A call that has been categorized as bad does not necessarily
indicate a
   modem problem with the MAX. Poor line quality, software problems with the
   calling modem, wrong numbers and __forgotten passwords__ all can generate
calls
   that appear as bad calls but that have nothing to do with modems on the
MAX."

...and the only two times I've had a dramatic increase in bad calls were the
only two times that there was massive failure to authenticate. So,
documentation or not, my experience is that authentication does cause the
bad flags - at least on my system. Yours may differ, though it would be an
interesting test for you to try perhaps -- log in 100 or so times failing to
authenticate and check your results...

> modem handshaking was completed.  The "avm" counters can only tell the
> state of the modem, not anything beyond it (i.e. the PPP level where the
> authentication phase occurs).  I don't think the manual is correct in
> this case.

I don't see why they couldn't be updated after the authentication process
prior to before? I guess we'll have to agree to disagree on this one. :-)

Have a good day!

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