The diagnostic tools supplied in this directory are being supplied to facilitate
Digi International Technical Support assistance to the customer in troubleshooting
and verifying ISDN board and line configurations. These tools are to be used
on a "AS IS" basis may not function on all PC platforms.
Digi International Windows 98 ISDN Diagnostics. (05/2000)
(c) Copyright 2000 by Digi International
Digi ISDN BRI Trace Utility - dgtrcbri.exe
The dgtrcbri.exe is utility used to decode ISDN D channel protocols. The
D channel carries both call set-up and user packets across the network.
This trace utility (dgtrcbri.exe) can be used for troubleshooting outgoing
calls, incoming calls and line problems by decoding this D channel traffic.
The output from this utility is very cryptic and the following information
provides only a brief example of its use.
First, you must bring up Windows and then select DOS prompt icon, since
this command must be execute from a DOS prompt.
Options for dgtrcbri.exe diagnostic:
Usage - trace -a -p -l2 -l3 -raw -?
-a - trace all lines
-p - show decode for all ISDN Protocols
-l2 - show decode for ISDN Layer 2 (Q.921) Protocol (minus letter L number 2)
-l3 - show decode for ISDN Layer 3 (Q.931) Protocol (minus letter L number 3)
-raw - show raw hex dump of all ISDN Protocols
-? - show this screen
* Typically you will only need to use trace with the -L3 option.
* If using a Datafire4 ST or PC/IMAC4 you will need to use -a option.
The following is an example of running dgtrcbri.exe.
1. c:\dgtrcbri -l3 (letter L number 3)
Below is example output from dgtrcbri. (This was from a successful call)
To capture output you need to redirect it to a file. Example
dgtrcbri -l3 > testlog. Then use alt-tab to switch back to windows
session and place call. When you are done gathering information, then
go back to DOS session and type ctrl-c to end trace. Information after #
is text added for clarification. Don't worry if your results vary,
especially if call is successful, various switch types will display
information differently.
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (T) # (T) indicates this is information
# from Digi (T)erminal Adapter side
# (N) indicates this is information
# from ISDN switch (N)etwork side
Q.931 Decode
Crv=001(T) SETUP # BearerCap entry will show call type
[BearerCap ] 04 (02) 88 90 # 88 90 is a Digital 64k
# 88 90 21 8f is a Digital 56k
# 88 90 a2 is a Voice 56k
[ChanIdent ] 18 (01) 83
[KeypadFac ] 2C (07) 39 38 38 36 39 # KeypadFac indicates phone number
34 36 # that is being called. This is in
# hexidecimal. Just remove first 3
# from pair to get the phone number
# Example calling number is 9886946
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (N)
Q.931 Decode
Crv=001(O) CALL PROCEEDING
[ChanIdent ] 18 (01) 89
# CALL PROCEEDING - The switch is
# indicating which B channel will
# be used for call
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (N)
Q.931 Decode
Crv=001(O) ALERTING
[Signal ] 34 (01) 01
# ALERTING - The switch is ringing the
# remote adapter
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (N)
Q.931 Decode
Crv=001(O) CONNECT
[Signal ] 34 (01) 3f
# CONNECT - The switch indicates that the
# call setup was successful, and the
# remote device has answered
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (T)
Q.931 Decode
Crv=001(T) CONNECT ACKNOWLEDGE
# CONNECT ACKNOWLEDGE - The adapter
# signals the switch that it
# acknowledges that the call setup
# is complete
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (N)
Q.931 Decode
Crv=001(O) STATUS ENQUIRY
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (T)
Q.931 Decode
Crv=001(T) STATUS
[Cause ] 08 (02) 80 9e
User
Normal Event
Response To Status Enquiry
[CallState ] 14 (01) 0a
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (T)
Q.931 Decode # DISCONNECT - From the (T) Digi side
Crv=001(T) DISCONNECT # indicates an adapter request for
[Cause ] 08 (02) 80 90 # "CALL REQUEST DISCONNECTION"
User # From the (N) Network-ISDN switch side
Normal Event # indicates the network request for
Normal Clearing # "CALL DISCONNECTION"
# You may need to run a trace on the
# remote side to discover which side
# either the ISDN switch or the remote
# device has requested the disconnect
# In this example a cause of 90 is a
# Normal Call Disconnect caused by
# hanging up from Digi side in RAS
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (N)
Q.931 Decode
Crv=001(O) RELEASE
# RELEASE - Indicates that the network
# has initiated the "REQUEST RELEASE"
# of the call
1188:02:47:296 DATAFIRE - ISA1ST-Line0 (T)
Q.931 Decode
Crv=001(T) RELEASE COMPLETE
# RELEASE COMPLETE - Indicates that the adapter
# has acknowledged the RELEASE of call
Digi ISDN BRI Line Utility - dginfbri.exe
ISDN diag dginfbri.exe is a utility used to find out if there is
proper communication to your ISDN provider. It will show which layers
are passing or failing to determine where or if a problem exists.
This text file provides enough information for troubleshooting.
Testing of ISDN Layers 1-3:
Layer 1 - This is a test to see if we are communicating to the physical
layer correctly. With the PC/IMAC, this may mean a proper connection to
the NT1 device. With the Datafire, is it properly seeing the ISDN line.
Run diagnostic: dginfbri -a1
Example output:
Line: Pcimac2-LINE0
Area: 01 - Layer 1 (S/T)
--------------------------------------------------------------
Tx_Info_Pattern INFO 3
Rx_Info_Pattern INFO 4
Tx_Frames 0
Tx_Collisions 0
Tx_Errors 0
Rx_Frames 0
Rx_Errors 0
Layer 1 passes if: Tx_Info_Pattern is INFO3 & Rx_Info_Pattern is INFO4
You should then go to layer 2 and test with dginfbri.
If Layer 1 fails : Did Digi driver load correctly, any errors on bootup?
Check cabling. Use cables that came with the Digi adapter
or try another. Standard RJ11 phone cable will work. Unplug
all cabling, wait few seconds, plug in, and retest.
Check NT1. Any error lights. Try another NT1 if possible.
If still having problems call Digi Tech Support.
Layer 2 - This is a test to see if the requested TEI (terminal
endpoint identifier) assignment from the switch was successful.
The TEI is assigned dynamically, and if passes will assign a number
from 64-126. If you reboot or lose the ISDN connection to the switch
the TEI will be reassigned.
Run diagnostic: dginfbri -a2
Example output:
Line: Pcimac2-LINE0
Area: 02 - Layer 2 (Q.921)
--------------------------------------------------------------
State Tei Assigned
Sapi 0
Tei 96
Lap_State Multiframe Established
Lap_V(S) 1
Lap_V(A) 1
Lap_V(R) 46
I_Queue_Frames 0
Ack_Queue_Frames 0
State Tei Assigned
Sapi 0
Tei 105
Lap_State Multiframe Established
Lap_V(S) 1
Lap_V(A) 1
Lap_V(R) 46
I_Queue_Frames 0
Ack_Queue_Frames 0
Layer 2 passes if: State = Tei Assigned
Tei = Number from 64-126
Lap_State = Multiframe Established
If you have 2 logical terminals, you will see the above fields shown twice.
The first time for the 1st logical terminal, then again for the 2nd one.
Check both because you can have a problem with 1 B channel.
You should then go to layer 3 and test with dginfbri.
If layer 2 fails :
A TEI of 127 (127 is reserved for the switch) means we are requesting a TEI
from the Switch and have not received that yet. Without the TEI, calls are
not possible.
Causes for waiting TEI assignment:
- Switch busy, needed resources
- Connection not available yet (customer's switch programming not done yet)
Unplug the RJ cables from wall, NT1, and Digi ISDN board, wait a few
seconds, plug back in, and retest. If still having problems call Digi Tech
Support.
Layer 3 - This is a test to see if we are getting full service from the
ISDN switch. It will check to see if switch type entered during Digi driver
configuration is correct. It will also check the SPIDs (typically, only
used in the U.S.) against the values setup at the ISDN service provider.
These values must match exactly. It is just like a password being approved.
Run diagnostic: dginfbri -a3
Example output:
Line: Pcimac2-LINE0
Area: 03 - Layer 3 (Q.931)
--------------------------------------------------------------
State Active
Tei 96
Style National ISDN 1
Spid 61298858901111
Usid 0
Tid 11
Service Full
Style_Flags 0
State Active
Tei 105
Style National ISDN 1
Spid 61298858911111
Usid 1
Tid 11
Service Full
Style_Flags 0
Layer 3 passes if: State = Active or Established, Awaiting Restart
Service = Full, Non Initializing, or Not Determined
If you have 2 logical terminal you will see the above fields shown twice.
The first time for the 1st logical terminal, then again for the 2nd one.
Check both because you can have a problem with 1 B channel.
If layer 3 fails :
Is the switch type entered during driver configuration correct?
ISDN Switch Types
NI-1 - Pick National ISDN 1 if your switch is National ISDN or the
protocol running on it is National ISDN
NTI - Pick Northern Telecom ISDN if your switch is a DMS100 running
their Functional protocol) pick NI-1 if running National
AT&T - Pick this is switch is AT&T running their Custom protocol pick
NI-1 if switch is running National
NET3 - Standard international switch type
EuroISDN - Identical to NET3
VN4 - Identical to NET3
1TR6 - ITR6 (Germany)
VN3 - VN3 (France)
INS64 - INS64 (Japan)
AUSTEL - Australian
SIGNAPORE - Singapore
GENERIC - Generic CCITT/ANSI switch
Are the SPIDs (typically, only used in the U.S.) you entered during
Digi driver configuration correct? (no spaces, no dashes, just one long
number)
Otherwise, you must reconfirm this information with the ISDN service
provider. If still having problems call Digi Tech Support.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.