Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) 185's and 11's?

    What percentage do you consider high ?
When I have people bitching and threatening to switch to a mom & pop shop down
the road, its way too high! My average is around 2%. Meaning one in fifty users
will get dropped and be cussing at me. Now the CEO is receiving threatening
letters from customers wanting to take their business elsewhere....elsewhere
being other companies in town who aren't using Ascend mind you...(and also not
having all these problems).
    If it were the users' phone lines, or the telco, the users would have the
same problems elsewhere at the other ISP's. I get disturbing chills down my
back when a user tells me he bought a second account from another ISP and warns
that he is having "no" disconnects whatsoever. How do I compete with that ?
    Maybe I'm pissing and moaning... maybe I made a mistake way back when thats
causing all these problems now...  but then again maybe not, I don't seem to be
the only one making this mistake.
    Could Ascend at least split the 185's into as many pieces as possible,
like...
186  - lots of retrains before sudden loss of carrier
187  - this guys modem sucks, must be USR
188  - PAD too high on user's line
189  - some jerk-off at Telco just hit the reset button on the users' remote
switch....(that would be stretching it a little)

anyway.. something is better than nothing! Like 'ol J.M. said, "Help us, help
you"... By giving us a few extra cause codes, by giving us that SNMP OID (pools
-v) we've been begging for, you would be helping yourselves.

    Today I called my salesman telling him all the problems we have been having
with 6.x. He quickly snagged a engineer next door. The engineer sent me the
reasons I might get a cause code 185. All of which were blamed on the end
users' equipment or lines. How can I be so arrogant (as one customer
questioned) to suggest that its his equipment when a few of his buddies are
getting the same disconnects?

Mike Hughes wrote:

> On 19 May 98 at 20:35, Jason Nealis wrote:
>
> >
> >  I've been off looking at cable modems and doing all types of crazy
> > items and haven't really been paying attention to my NAS's. Well, I
> > took a short trip to my local user newsgroups when I start to see
> > titles like DISCONNECTED AGAIN!, What's HAPPENING TO MY PPP
> > CONNECTION.
>
> Jason
>
> I've been thinking (and occasionallty saying) this about code
> carrying K56Flex 1.160T code since it was released.
>
> The last good release, as far as the K56 code goes, is 5.0Ap36 with
> 1.140N Rockwell code - however, this had been plagued by memory
> leaks.
>
> Also, when running 1.160T based codes, many V34 users only get 31200
> connects, which has also caused some bitching in my usergroups too.
>
> At one point, I was doing the maths on the disconnects on a regular
> basis, and I'll agree that percentage-wise, they were about the same
> as you.
>
> Mike
> --
> Mike Hughes - Network Services         mike@dircon.net
> Tel: 0181 297 0300                     http://www.dircon.net/
> Fax: 0181 463 9820
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd:   <http://www.nealis.net/ascend/faq>



-- Tim Connolly tec@mountain.net     MountainNet, Inc.
-- (304) 594-9075 ext. 37            2816 Cranberry Square
-- fax (304) 594-9088                Morgantown, WV 26505

-- If you sit down at a poker game and don't see a sucker,
-- get up.  You're the sucker. (Story of my life)


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