Frequently Asked Questions (FAQ)Digi ISDN BRI ISA products under DOS Last Update: (2/8/99) ---------------------------------------------------------------------------How can I find out what Digi DOS client version I gave installed?To determine your current installed DOS client version, at DOS prompt type:Use appropriate show version command:clsh show version, pppsh show version, or pcimac show versionLatest released driver version is: 1.4.0Digi FTP ftp.dgii.com/support/drivers/dos/released/isdn/4001182E.exe  ---------------------------------------------------------------------------Does Digi have any ISDN test numbers I can call?6129886928 (USA) - Netware 4.1 server 1st B channel (ODI connections)6129886938 (USA) - Netware 4.1 server 2nd B channel (ODI connections)Login: guest Password: guest6129888328 (USA) - Win NT 4.0 server 1st B channel (PPP connections)6129889011 (USA) - Win NT 4.0 server 2nd B channel (PPP connections)Login: guest Password: guest Domain: No domain leave field blank---------------------------------------------------------------------------How do I test the Digi ISDN board connection to the ISDN switch? ISDN diag "sh idp/l1-3" is a utility used to find out if there isproper communication to your ISDN provider. It will show which layersare passing or failing to determine where or if a problem exists. Testing of ISDN Layers 1-3:Layer 1 - This is a test to see if we are communicating to the physicallayer correctly. With the PC/IMAC, this may mean a proper connection tothe NT1 device. With the Datafire, is it properly seeing the ISDN line.Command : sh idp /l1 Layer 1 passes if: Tx_Info_Pattern is INFO3 & Rx_Info_Pattern is INFO4                   You should then go to layer 2 and test.If Layer 1 fails : Did the Digi driver load correctly, where there
                   any errors on bootup?		   Check cabling. Use cables that came with Digi or try		   another. Standard RJ11 phone cable will work. Unplug		   all cabling, wait few seconds, plugin, 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 numberfrom 64-126. If you reboot or lose the ISDN connection to the switchthe TEI will be reassigned.Command : sh idp /l2 Layer 2 passes if: State     = Tei Assigned                   Tei       = Number from 64-126	           Lap_State = Multiframe EstablishedIf 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.You should then go to layer 3 and test.If layer 2 fails :A TEI of 127 (127 is reserved for the switch) means we are requesting aTEI from the Switch and have not received that yet. Without the TEI, callsare 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 fewseconds, replugin, and retest. If you are still having problems call 
Digi Tech Support.Layer 3 - This is a test to see if we are getting full service from theISDN switch. It will check to see if the 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.Command : sh idp /l3 Layer 3 passes if:  State   = Active or Established, Awaiting Restart	          Service   = Full, Non Initializing, or Not DeterminedIf you have 2 logical terminals you will see the above fields shown twiceThe first time for the 1st logical terminal, then again for the 2nd oneCheck both because you can have a problem with 1 B channelIf layer 3 fails :Is the switch type entered during driver configuration correct?ISDN Switch TypesNI-1  - Pick if switch is National ISDN or the protocol is National ISDNNTI   - Pick if DMS100 running Functional pick NI-1 if running NationalAT&T  - Pick if AT&T running Custom pick NI-1 if running National ISDNNET3      - Standard international switch typeEuroISDN  - Identical to NET3VN4       - Identical to NET3   1TR6      - ITR6 (Germany)VN3       - VN3 (France)INS64     - INS64 (Japan)AUSTEL    - AustralianSIGNAPORE - SignaporeGENERIC   - Generic CCITT/ANSI switchAre the SPIDs (typically, only used in the U.S.) you entered duringDigi driver configuration correct? (no spaces, no dashes, just one longnumber)Otherwise, you must reconfirm this information with the ISDN serviceprovider. If still having problems call Digi Tech Support.---------------------------------------------------------------------------I'm having problems calling out, what are the basic things to check? Treat ISDN call as if you were placing a normal phone call.Local call, just use seven digits. Example: 9886928 Long distance call, 1, area code, phone number. Example: 16129886928 Enter as one long number. No spaces, dashes, or commas New Long distance carrier-add prefix (MCI 1010222, Sprint 1010333, 
AT&T 1010288)Example: conn 101022216129886928 (This will call number using MCI) Centrex or PBX, you may need to dial a 9 for an outside line. Problems 64k call, try 56k. (Not all areas or the routes support 64k)Problem with 2 channel call, try one channel call Check Datafire termination (turn off if other ISDN devices on S0/ST bus)If all the above suggestions fail, call, fax, or email Digi Tech Support ---------------------------------------------------------------------------I'm having problems calling in, what are the basic things to check? Run Digi DOS client install.exe program. Go to Configuration -> ISDN Line Parameters -> Check Address field. This should be your ISDN phone number,not the calling side. It must be one long number no spaces or dashes.In the U.S. it is usually the SPID minus any prefix or suffix. If still having problems, write down error and call Tech Support. ---------------------------------------------------------------------------Does my Datafire (or PC/IMAC) require an NT1?An NT1 (network terminator 1) is a device which provides an interfacebetween the two-wire twisted pairs used by telephone companies intheir ISDN Basic Rate (BRI) network and an end-user's four-wireterminal equipment. Any Digi Intl ISDN product with a S/T interfacewill require an extrenal NT1. Any Digi Intl ISDN product with a U interface will already have a builtin NT1.In North America, you have to buy and maintain your own NT1 device.The telephone company offers end-users a U interface.  In Europe andJapan, the telephone company provides the NT1, owns it, and offersend-users a S/T interface directly.  In North America, some ISDNequipment vendors offer devices which connect directly to the Uinterface (for example, the Datafire U).  If you have one of thesedevices, you don't need to buy a separate NT1.  The U interface can'tbe built in to the device when it's offered for sale in Europe orJapan. ---------------------------------------------------------------------------How do I place a 2 channel (bonded) ISDN call? Basically you need to modify three parameters in your calling profileor command connection line; /address, /number_of_channels, /channel.Remote side has one number repeat it: /address="9886928:9886928"Remote side has two numbers, enter both: /address="9886928:9886938"Change /number_of_channels to 2Local side has one or no spids: /channel=b1:b2Local side has two spids: /channel=b1:b2aExample: Two remote phone numbers and two local SPIDsclsh> connect "16129886928:16129886938" /num=2 /channel=b1:b2a ---------------------------------------------------------------------------What does the error message "incomplete address" mean?It means the telco switch is expecting more digits.Try adding # (pound symbol) to end of phone number Example: clsh> connect "16129886928#"---------------------------------------------------------------------------Why do I get error message "too many arguments" when using DOS batch file?Works fine at shell prompt doing "conn "1st#:2nd#" /num=2. Double quotes are not passed to the shell you must use single quote. ---------------------------------------------------------------------------Variety of problems when using Windows applications or exiting windowsMake sure you are running the latest version of DOS client driver. Try changing the Software Interrupt Vector from default. Run install, select Configuration -> Adapter Parameters Change Software InterruptVector from 62 to 78 or 79. Change Digi ISDN adapters I/O, IRQ, Memory (pcimac only) addressesSave, reboot, and reload drivers. ---------------------------------------------------------------------------Calling out getting error "interworkin, unspecified" ?Try adding a 9 to prefix of number when calling out.---------------------------------------------------------------------------Calling out getting error "protocol error, unspecified"?Try adding a 9 to prefix of number when calling out.---------------------------------------------------------------------------I'm not sure my net.cfg file is ok. Do you have an example? Yes, see example below. Comment out unused Frame types by starting line with ; (semi-colon) Comment out unused Protocol types by starting line with ; (semi-colon) Change INT to match your Digi ISDN board's interrupt Change PORT to match your Digi ISDN board's I/O port address Change MEM to match your Digi ISDN board's memory address (PC/IMAC only) Change FIRST NETWORK DRIVE to appropriate driver letter (Usually F) Change PREFERRED SERVER to match your Netware server nameFor improved performance you should use latest VLM.EXE If using VLM.EXE you must have LAST DRIVE=Z in CONFIG.SYS NET.CFG should be in same directory as LSL.COM & IPXODI.COM      Link Driver IDPODI or PPPODI      Frame Ethernet_802.3      ;Frame Ethernet_802.2      ;Frame Ethernet_II      Protocol IPX 0 Ethernet_802.3      ;Protocol IPX E0 Ethernet_802.2      ;Protocol IPX 8137 Ethernet_II      ;Protocol IP 0800 Ethernet_II      INT 11      PORT 350      NetWare DOS Requester      FIRST NETWORK DRIVE = F      PREFERRED SERVER=OPUS ---------------------------------------------------------------------------I have an ISDN connection from the DOS client system to a NetWare server, but VLM doesn't find server? Make sure correct net.cfg is being used. Duplicate copies can causeproblems. When lsl loads it will tell you from which directory net.cfg isbeing called. Make sure correct frame type is being bound. This can be doneby watching to see what gets bound when loading idpodi.com. If binding towrong protocol check net.cfg file. Make sure you are running the latestdrivers. This applies to both Digi ISDN DOS client and Novell client (VLMsand associated files - VLM current version 1.2.0). Also make sure all DigiISDN drivers are in their own directory. And Novell client files are intheir own directory with proper path statements in autoexec.bat. Try usingperferred server option for connecting to server. i.e vlm /ps=servername ---------------------------------------------------------------------------Connections fail when started from autoexec.bat or batch file at boot?After the drivers load it takes about takes the adapter about 30 seconds to sync with the ISDN switch. The checklayer3 command waits for layer 3to sync.example: adpim.exe          pcicm.exe         lsl.com         idpodi.com         ipxodi.exe          clsh checklayer3          connect "profile-name"          vlm ---------------------------------------------------------------------------How can I do a ppp trace for debugging a connection problem?Include the /log option when you load ppp.exe (ppp core module). After loading the drivers execute pdump with the z option. Attempt the the connection incoming or going. Execute pdump with the desired options. I usually use the t option. To capture the trace output to a file redirect the command output to a file Example: C:\pdump t >ppp.log---------------------------------------------------------------------------