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

[maxed_out_user@hotmail.com]

One other suggestion would be to try plugging the Max into some other
power source since the Max needs sufficient power to bring up its
expansion slot cards.  This can cause the card failing to come up and
display those types of messages.

Getting back to our prior discussion about when a call is determined
'bad', I went ahead and did some testing and the outcome is...what I
mentioned before still stands.  If modems don't finish handshaking
(carrier detect is not reached as I previously wrote), "avm" will
register a bad call.  If modems DO finish handshaking, but the user
fails PPP authentication (bad password for instance), the Max will NOT
register a bad call.  I tested this on 7.0.4.  I don't know why the
documentation you found mentioned something contradictive.  Maybe they
changed this behavior in 8.0, but that's definitely not the case in
7.0.x.


> We are getting the following from one card in a max 6000
>
> MODEMDRV-3/0: _postTask: expected response not received
> MODEMDRV-3/15: _postTask: expected response not received
>
> What causes this? Do I need to send the card back (I think this is the
case)?
> If I reset the box it works for a while then this happens again?

If I had to guess, and it's a guess, it looks like your entire card has
stopped responding since all of the ports on that card have the same
error.
If you feel like experimenting, you might try putting the card in
another
slot to see if it's card specific or slot specific and if it's slot
specific
there may be a heating issue or perhaps the slot itself is just bad.

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