Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) 5.0Ap16 woes!
Ok, we all know how horrible v.34 connections to p16 are ;-) But heres
a good one:
After a while, ISDN calls start failing with cause code 2 (unknown) progress
10 (Call Up) Joy, eh? Oh, and then it's a 10 minute boot cycle... and
has to be sheparded, because only 1 in 4 tries gets the PRIs to come up
in a stable state. The PRIs work fine on i13, but that has the old DSP code!
AARRGGH!
Once it's up it "works" for quite a while... but I don't want to have
to shut it down for everyone so that ISDN calls can go through again!
Just a bit peeved here.
Also, When do we get transmit speed reporting?
I would be happy if another 5.0 incremental was released, since
A) that didn't have the PRI problems that I am seeing with p16
B) I could get useful connection information out of it.
Please please PLEASE release another incremental! I can't run without
the new DSP code (too many modems upgraded to it to "fix" their problems)
and I can't run with it in p16!
Subtract 50% of the venom of this rant and apply it to USR, Rockwell, Lucient
and Motorola for trying to pump more bits down corroded copper wires then
god intended, and convincing the end users that it's the ISPs fault if
it dosn't work!
Arrggh! (Really bad support day.)
Hey: How do you convince a user with a 14.4 that they REALLY won't see
a speed increase by calling the (overloaded) 56k lines?
--Dan
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>