A Core Competence Product Evaluation
Ok, So What’s Wrong: Diagnostics and Monitoring
The WaveRunner's ISDN Port Monitor can be used to observe ISDN line activity. If SPID or TEI negotiation fails, you may have assigned the same SPID and/or ISDN telephone number to both the Extended NT-1 and WaveRunner -- use the ISDN Configuration window to modify the current configuration settings as needed. Note that you can't allocate a SPID to an analog device and use ISDN multilink for data in the same configuration.
The Port Monitor creates a log file to assist with problem diagnosis. The sample log excerpt shown below, illustrates a successful ISDN call, followed by PPP negotiation failure (remote disconnect). As is often the case, this log file can be handy to debug ISDN call setup problems, but provides little insight into problems occurring after the ISDN call has been connected (in this case, our negotiation failure).
ISDN Port Monitor Log
Time/Date Port Monitor Entry
18:45:18 12/10/96 ISDN D-Channel code loaded
18:45:18 12/10/96 IN50: Line Active
18:45:21 12/10/96 IN01: TEI Initialized DN1: 89
18:45:22 12/10/96 IN03: SPID Initialized DN1
18:48:37 12/10/96 IN22: Call ID 2, Outgoing Call (Data)
18:48:37 12/10/96 IN24: Outgoing Call To:
18:48:37 12/10/96 18005551212
18:48:38 12/10/96 IN25: Call ID 2, Network Acknowledged Call
18:48:39 12/10/96 IN27: Call ID 2, Call Accepted
18:50:51 12/10/96 WN31: Call ID 2, Call Release Sent
18:50:51 12/10/96 IN31: Call ID 2, Call Disconnect Received
18:50:51 12/10/96 Cause = 16, Diag = 0
IBM’s WaveRunner product web page provides a good starting point for additional information, hints, and updated software drivers.
Tell me about ISDN Internet Access Providers