RE: (ASCEND) Max 6096 frequent reboots and c=185 p=31

["Reece, Mark" <Mark.Reece@gte.com>]

We are working the EXACT same errors with Lucent right now.  We have
upgraded to 7.0.26, but this hasn't helped either.  We have setup a coredump
server, and we are forwarding our coredumps to them to have them determine
where the problem is (code, software, hardware, etc...).

We have been having these outages for the last two weeks.  We have a 4th
level engineer (a coder/engineer) working directly with us.  As soon as we
get a "fix" I'll send it out on this list.

Mark Reece

-----Original Message-----
From: Jerry O'Brien [mailto:jobrien@cuttingedge.net]
Sent: Friday, March 03, 2000 12:02 PM
To: ascend
Cc: Staff
Subject: (ASCEND) Max 6096 frequent reboots and c=185 p=31


I have a Max 6096 running 7.0.22 with frequent reboots (as often as 2-3 per
day, and then sometimes none for a week) and 59% of all calls terminate with
c=185, mostly with p=31or p=2. It has all four PRI connected and does fill
up occasionally in the evening, but the errors happen all the time.

Any ideas? Should I choose another version? Which one?

Sound Business Systems (the reseller) opened a ticket with Ascend for me on
the reboots, but I haven't heard anything yet. They suggested I call Lucent
for status myself, but what the heck is the number???  Their new web page
appears to be a very secure site (no Ascend owners can get in...)

Thanks,


Jerry O'Brien
Cutting Edge Systems


++ 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>