Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) BRI Debugging
>From: Kevin A Smith <kevin@ascend.com>
>Date: Fri, 16 Oct 1998 09:41:42 -0700
>Subject: Re: (ASCEND) NFAS and DNIS reporting
>
>
>IF no one else has seen this either way, then you could get some debug output
>from the MAX - I think it was 'pridisplay' that will dump a hex output of the
>d-channel messages for incoming calls. You could then bounce that off TAC, or
>maybe someone here could decode it...I think the decoder that I have will,
>but
>I've only tried BRI traces so far.
Well it looks like you have done something I need to do -- But for
different reasons!
Ironically, our pipeline is behaving very well these days but I have it
sharing the BRI line with an isdn pabx which is not. I was just about to
start writing a decoder for the d-channel call setup messages to make it
easier to debug. (I am using the pipeline to snoop on the pabx) Any code
would be greatfully appreciated, in any form. I was going to write this
to run on a Mac since thats what we do, but I'll take anything. The
thought of wading through the protocol specs to decode all the messages
is daunting & I am not too proud to borrow ;-)
Finally, whats a TAC?
Ken FitzGerald-smith <kfs@foreshadowlogic.com>
++ 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: