Magic decoder ring for PM3 isdn debugging

R.D. Thrush (rd@thrush.com)
Wed, 28 May 1997 16:22:16 -0400 (EDT)

I have a win95 customer with a 3ComImpact IQ 230K device that hasn't
been able to connect to a pm3 since Monday. The pm3 has 2 PRIs and is
running ComOS 3.5.1b8. By only changing the phone no. in DUN, the
customer can, however, connect successfully with an Ascend P400 on
another PRI.

The customer had no connection problems with the IQ before Tuesday.
And since no other ISDN customers have reported problems, I am looking
for help understanding why he now has problems with the pm3 yet can
connect via the Ascend?

I have enabled isdn debug (set debug isdn on;set debug isdn-d on)
and have the following snippet associated with one of his failures.
It doesn't appear to get far enough to begin the PPP protocol
negotiation.

Although it all looks mostly like noise, I was able to find the
incoming phone no. in the 5th line so I believe I have the associated
info. Where can I find out how to decode this information?

Presumably, the lines prefixed with D0: or D1: refer to the D
channel for the appropriate PRI. What does the rest of the Dx: lines
mean?

D0: send 00 01 01 eb
D0: recv 00 01 01 b7
D1: send 00 01 01 8b
D1: recv 00 01 01 3f
D0: recv 02 01 ea b6 08 02 05 f5 05 04 02 88 90 18 03 a9 83 81 6c 0c 21 83 34 30 37 33 32 37 30 31 33 38 70 08 c1 39 37 35 35 36 30 30
D0: send 02 01 01 ec
S0: Sending Request Connect - 64Kbps / Data (B1 ID:6c70)
D0: send 00 01 b6 ec 08 02 85 f5 07 18 03 a9 83 81
D0: recv 00 01 01 b8
D0: recv 02 01 ec b8 08 02 05 f5 0f
D0: send 02 01 01 ee
S0: Received Connect - B1
D1: send 00 01 01 8b
D1: recv 00 01 01 3f
D0: send 00 01 01 ef
D0: recv 00 01 01 b9
S0: Sending Disconnect Request
D0: send 00 01 b8 ee 08 02 85 f5 45 08 02 80 90
D0: recv 00 01 01 ba
D0: recv 02 01 ee ba 08 02 05 f5 4d
D0: send 02 01 01 f0
S0: Received Clear Conf (B1 ID:6c70)
D0: send 00 01 ba f0 08 02 85 f5 5a
D0: recv 00 01 01 bc
S0: Session Terminated - Login Timeout