Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) RE: c=185's [Fwd: Ticket # 200300]
At 05:28 AM 5/20/98 -0400, Cyril Jaouich wrote:
> Also, while running the packet analyser on our Pri we saw bizzare
>stuff from the ascend. Usually a disconnect is has follow:
>
>> From: User Status: Ok
>> Type: DISConnect <45>
>> From: Network Status: Ok
>> Type: RELease <4D>
>> From: User Status: Ok
>> Type: RELease COMplete <5A>
This is still not "usual" as the REL COM is complaining of invalid data in
one of the Information Elements received in the previous message (presumably
the Network REL). Cause code 100 (5A).
>> Disconnect from user (Ascend)
>
> According to what I could find on the net on ISDN sig this is
>correct (it is missing acks, but you at least get the picture).
>
>> From: User Status: Ok
>> Type: DISConnect <45>
>> From: User Status: Ok
>> Type: RELease COMplete <5A>
>> From: Network Status: Ok
>> Type: RELease <4D>
>> ----------------------
>> Disconnect from User (Ascend)
>
> This is where it gets confusing why did the ascend say Release
>completed before the network said release?
It does look weird. Especially as it is still complaining about the IE
contents (cause code 100). Are we sure this is the exact sequence?
> We are still working on this problem, but I think we get 185 maybe
>because of broken ISDN code in the max... I'll update the list as we get
>more data collected.
This is an intriguing avenue. Is anyone running on a 5ESS PRI also seeing a
lot
of disconnect code 185s?
Kevin Smith Ascend Communications...
Customer Satisfaction ...where Network Solutions never end.
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups:
References: