>The driver set for USR Sportster 128K includes a protocol analyzer that
>shows control messages passing between the TA and the telco. It's very
>arcae but if you stare at it long enough it actually provides some useful
>info that makes some sense -- for example if you watch it while you are
>dialing out you can clearly make out the call initiation and negotiation
>sequence as the TA requests call setup and the isdn net replies, etc.
The protocol analyzer included with the USR is just like the rest of
the Sportster ISDN NT setup- not flashy, but effective. I was having
trouble initiating voice calls *at all*(e.g. no dial tone) when I
originally got my ISDN line set up, and played the part of a pinball
between USR and Ameritech, each blaming the other for the problems I
was experiencing. I piped a long session of fxshow.exe to a file and
analyzed it- my problems were related to only having one B channel
configured for voice. Even though it was the first channel, for some
reason the Sporster freaked out when it saw that both of them weren't
configured for voice, in spite of the fact that on 2-2 of the USR user
manual, B2 can/should be data-only. Regardless, I just told NT that I
only had one B channel, and it was configured for data and voice.
Thereafter it behaved normally, and used both channels anyway.
Sometimes I think USR makes good products in spite of themselves.
Rumor has it that they stole the Sporster ISDN. I believe it.
The output of the protocol analyzer isn't something to curl up next to
a fire with, but if you dig stuff like that, it's a great way to learn
about ISDN. And save your sanity dealing with USR and the telco.
I'm eager to hear how the ACO turns out.
My opinions are my own, not TW's, etc.