Frequently Asked Questions:
  1. What ISDN BRI Win NT driver version is loaded and where can I get latest?
  2. How do I install the Digi ISDN BRI Win NT driver?
  3. How do I know if the Digi ISDN BRI driver installed correctly?
  4. How do I run dginfbri.exe diag? (Datafire BRI ISA and PC/IMAC only)
  5. What should I try next if Digi ISDN BRI  Win NT driver fails to load?
  6. Does my Datafire (or PC/IMAC) require an NT1?
  7. Does Digi have any ISDN test numbers I can use?
  8. How do I make a 2 channel (Multilink PPP) call under Win NT 4.0?
  9. How do I make a 2 channel bonded (Digi to Digi) call with NT4.0?
  10. How do I make a 2 channel bonded (Digi to Digi) call with NT 3.5.1?
  11. I'm having problems calling out, what are basic things to check?
  12. I'm having problems calling in, what are basic things to check?
  13. Problems with incoming/outgoing PPP calls to other ISDN vendors products
  14. What are the three green LEDs on Datafire BRI ISA adapter for?
  15. How do I set up my Datafire BRI ISA adapter dip switches?
  16. How do I set up my PC/IMAC adapter dip switches and jumpers?
  17. What does the error message "Failure to converge PPP" mean?
  18. Calling into a Win NT with 2 channels but callback only calls back with one
  19. How can I use AT command strings with the DataFire?
  20. Can Win NT server route Digi ISDN traffic (internet) for local workstations?
  21. How can I do a ppp trace for debugging a connection problem?

  1.  
  2. What ISDN BRI Win NT driver version is loaded and where can I get latest?

    Digi FTP (ftp.dgii.com) /support/drivers/winnt/released/isdn/

    For Datafire BRI ISA or PC/IMAC:
    Select Explorer -> Win NT directory/system32/drivers/pcimac.sys
    Properties - Version -> File Version should show v2.5.1 (E)

    Datafire BRI ISA and PC/IMAC adapters latest driver is:
    ISDN Win NT 3.5.1/4.0 BRI ISA drv vers 2.5.1 filename: 4001119E.exe

    For Datafire BRI PCI
    Select Explorer -> Win NT directory/system32/drivers/DigiCBri.sys
    Properties - Version -> File Version should show 3.1.4

    Datafire BRI PCI (only) latest driver is:
    ISDN Win NT 3.5.1/4.0 BRI PCI x86 drv vers 3.1.4 file: 4001537D.exe 1 of 2
    ISDN Win NT 3.5.1/4.0 BRI PCI x86 drv vers 3.1.4 file: 4001539D.exe 2 of 2

    ISDN Win NT 3.5.1/4.0 BRI PCI Alpha drv vers 3.0.0 file: 4001550A.exe 1 of 2
    ISDN Win NT 3.5.1/4.0 BRI PCI Alpha drv vers 3.0.0 file: 4001551A.exe 2 of 2


  3. How do I install the Digi ISDN BRI Win NT driver?
  4. Before driver install: Make sure you have either a network card
    or the MS Loopback Adapter installed as an Installed Adapter Card.

    For Win NT 4.0
    To Install: Control Panel -> Network -> Adapter -> Add -> Have Disk

    For Win NT 3.5.1
    Select Main -> Control Panel -> Network -> Add Adapter ->
    Pick <Other> Requires disk from manufacturer

    For Datafire BRI ISA or PC/IMAC:

    Pick sub-directory on diskette or hard drive for your bus/pc type.
    Example: A:\I386       If you have a Intel ISA or EISA PC
      A:\ALPHA      If you have a DEC Alpha PC
      A:\MIPS       If you have a MIPS PC
      A:\PPC        If you have a Power Point PC

    For Datafire BRI PCI:

    Pick a:\ directory for diskette or hard drive directory downloaded
    file was extracted to.

    Pick your Digi ISDN BRI adapter from list
    Keep following rest of install instructions.


     

  5. ISDN How do I know if the Digi BRI ISA Win NT driver installed correctly?
  6. Check Event Viewer for any error messages. This will let you know if you
    have a conflict or problem. For Datafire BRI ISA or PC/IMAC try another
    I/O or Memory addres (PC/IMAC only), no IRQ is used with this driver. Or
    use Windows NT Diagnostics to check for hardware conflicts. If NT Diags
    reports a conflict change to a non-conflicting address (Datafire BRI PCI
    adapter does not support changing it settings at this time, change the
    other adapters settings)

    If the Digi ISDN driver loads then ISDN ports can be found either
    Win NT 4.0, Dial Up Networking, Dial Using do you see ISDN1, ISDN2, etc.
    Win NT 3.5.1 Remote Access phone book, Port do you see ISDN1, ISDN2. etc.

    For Datafire BRI ISA or PC/IMAC run dginfbri.exe diag. (see next section)

    For Datafire BRI PCI go to Control Panel -> Network -> Aadapters ->
    Datafire BRI PCI -> Properties -> Check line status


     

  7. How do I run dginfbri.exe diag? (Datafire BRI ISA and PC/IMAC only)
  8. 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.

    Digi ISDN Win NT diskette you must expand diag in the /{bus type} dir.
    Example for Intel bus: expand a:\i386\dginfbri.ex_ dginfbri.exe

    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

    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 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 number
    from 64-126. If you reboot or lose the ISDN connection to the switch
    the TEI will be reassigned.

    Run diagnostic: dginfbri -a2

    Layer 2 passes if: State     = Tei Assigned
                       Tei       = Number from 64-126
                Lap_State = Multiframe Established

    If you have 2 logical terminal you will see the above fields shown twice.
    The first time for the 1st logical termal, 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 reserverd for the switch) means we are requesting a TEIi
    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, replugin, 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

    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 termal, 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 if switch is National ISDN or the protocol is National ISDN
    NTI       - Pick if DMS100 running Functional pick NI-1 if running National
    AT&T      - Pick if AT&T running Custom pick NI-1 if running National ISDN
    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 - Signapore
    GENERIC   - Generic CCITT/ANSI switch

    Are the SPIDs (typically, only used in the North America) 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.


     

  9. ISDN What should I do next if Digi BRI  Win NT driver fails to load?
  10. * Make sure you are running latest Digi ISDN Win NT driver
    * Before you install the driver make sure that either a network card
      or the MS Loopback Adapter is installed
    * Check Windows NT Diagnostics -> Resources for hardware conflicts
    * Reseat Digi adapter or try another slot. Move away from PCI shared slots.
    * Use I/O ports 350 for Datafire BRI ISA and 320 for PC/IMAC
    * If EISA bus try loading Eisa .cfg (4000638M.exe) file for your Digi ISDN
      adapter (download Digi FTP) Reseat adapter or try another slot.
    * Sound boards may cause conflicts remove sound board and retry
    * Remove Digi ISDN Win NT driver, reboot, then reload
    * If all the above suggestions fail, call, fax, or email Digi Tech Support


     

  11. Does my Datafire (or PC/IMAC)  require an NT1?
  12. An NT1 (network terminator 1) is a device which provides an interface between the two-wire twisted pairs used by telephone companies in their ISDN Basic Rate (BRI) network and an end-user's four-wire terminal equipment. Any Digi Intl ISDN product with a S/T interface will require an extrenal NT1. Any Digi Intl ISDN product with a U interface will already have a built in 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 and Japan, the telephone company provides the NT1, owns it, and offers end-users a S/T interface directly. In North America, some ISDN equipment vendors offer devices which connect directly to the U interface (for example, the Datafire U). If you have one of these devices, you don't need to buy a separate NT1. The U interface can't be built in to the device when it's offered for sale in Europe or Japan.


     

  13. Does Digi have any ISDN test numbers I can use?
  14. Digi ISDN Test Systems (available 7 days a week - 24 hours a day)

    Phone Number   Operating System

    6129886946 (USA) - Win NT 4.0 1st B channel (PPP connections)
    6129888320 (USA) - Win NT 4.0 2nd B channel (Combine both for MP connections)
    .Login: guest Password: guest Domain: (leave blank)

    If your ISDN BRI line is provisioned with 2 SPIDs (SPIDs are not used
    internationally), you could make a loopback call. Set up both Digi ISDN RAS
    ports for Dial in and Dial out (Win NT workstation set one port dial in and
    the other dial out). Then select one of your ISDN ports and dial the phone
    number associated with the other B channel.


     

  15. How do I make a 2 channel (Multilink PPP) call under Win NT 4.0? (Win NT 3.5.1 no multilink PPP support)
  16. (NT Server) Control Panel -> Network -> Services -> Remote Access Service
    -> Digi ISDN port -> Network -> check Enable Multilink box (all Digi ports)
    (NT Workstation) Already setup for Multilink PPP outgoing calls. Limitation
    is Workstation does not support 128k MP incoming calls, only 64k/56k calls.

    Goto My Computer -> Dial Up Networking
    1. Phone Book Entry to Dial -> Select New -> Pick a name for Phone Book entry
    2. Check the box Select my plain text password if that's the only way to connect
    3. Select All available ISDN line multilinked
    4. Enter phone number for remote system you are calling
    5. Select Finish
    6. Select the phone book entry you just added and pick More icon
    7. Select Edit entry and modem properties and pick Configure icon
    8. Check the box for ISDN1 and enter first remote phone number
       Check the box for ISDN2 and enter second remote phone number
       If the remote side only has one phone number repeat for both Digi ports
    9. Now try dialing the other vendor's ISDN product


     

  17. How do I make a 2 channel bonded (Digi to Digi) call with NT4.0?
  18. Goto My Computer -> Dial Up Networking
    1. Phone Book Entry to Dial -> Select New -> Pick a name for Phone Book entry
    2. Check the box Select my plain text password
    3. Select ISDN1 or appropriate port for adapter this entry will use
    4. Enter phone number for remote system you are calling
       If separate phone number for each B channel at remote site
       Enter: 1st number colon 2nd number example 5551212:5551213

       If 1 phone number for both B channels at remote site:
       Enter: 1st number colon 1st number example 5551212:5551212
    5. Select Finish
    6. Select the phone book entry you just added and pick More icon
    7. Select Edit entry and modem properties and pick Configure icon
    8. Check the box Use old proprietary protocol
    9. Change channels to use to 2
    10. Now try dialing the other Digi ISDN Windows system


     

  19. How do I make a  2 channel bonded (Digi to Digi) call with NT 3.5.1?
  20. A two channel call is only supported in Digi to Digi ISDN connection
    Win NT 3.5.1 only supports 1 channel call to non-Digi ISDN products
    Win NT 4.0 has added Multilink PPP support for 2 channel calls
     
    If separate phone number for each B channel at remote site
    In RAS phone book Phone Number field put 1st number colon 2nd number
    example 5551212:5551213

    If 1 phone number for both B channels at remote site:
    In RAS phone books Phone Number field put 1st number colon 1st number
    example 5551212:5551212

    Then select ISDN icon in RAS phone book entry and change number
    of channels from 1 to 2..


     

  21. I'm having  problems calling out, what are basic things to check?
  22. * 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
    * Try new Long distance carrier - prefix (MCI 1010222, Sprint 1010333, AT&T 1010288)
       Example: conn 101022216129886928 (This will call the number using MCI)
    * Centrex or PBX, prefix with 9 or inside own centrex try 4 digit number
    * Problems 64k call, try 56k. (Not all areas or the routes support 64k)
    * Problem with 2 channel call, try one channel call
    * Check Remote Access Service that Digi ISDN port is set for dial out
    * 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


     

  23. I'm having problems calling in, what are basic things to check?
  24. Check Control Panel -> Network -> Adapter -> Digi ISDN Adapter
    -> Properties -> Line Options -> Phone Number field. This should contain
    the phone number your ISDN provider gave you. Not the number you are
    calling (In North America a seven digit number. Your SPID minus area code
    or suffix). There should not be any spaces or dashes in this number. Still
    having problems, you could try leaving phone number field blank
     
    Check Control Panel -> Network -> Services -> Remote Access -> Digi ISDN port

    Add -> Two ports (i.e. ISDN1 & ISDN2) per ISDN BRI line (add if necessary)
    Configure -> Set appropriate Digi ISDN ports for dial in
    Network -> Encryption -> " Allow Any Authentication Including Clear Text"

    Bring up Remote Access Admin
    Server status should be running
    Individual ports Line Condition should be Waiting for Call
    Check Users -> Permissions -> Grant Dial In box, login name, password

    If all the above suggestions fail, call, fax, or email Digi Tech Support


     

  25. Problems with incoming/outgoing PPP calls to other ISDN vendors products
  26. Check Control Panel -> Network -> Adapter -> Digi ISDN Adapter
    -> Properties -> Line Options -> Phone Number field. This should contain
    the phone number your ISDN provider gave you. Not the number you are
    calling (In North America a seven digit number. Your SPID minus area code
    or suffix). There should not be any spaces or dashes in this number. Still
    having problems, you could try leaving phone number field blank
     
    Check Control Panel -> Network -> Services -> Remote Access -> Digi ISDN port

    Add -> Two ports (i.e. ISDN1 & ISDN2) per ISDN BRI line (add if necessary)
    Configure -> Set appropriate Digi ISDN ports for dial in
    Network -> Encryption -> " Allow Any Authentication Including Clear Text"

    Bring up Remote Access Admin
    Server status should be running
    Individual ports Line Condition should be Waiting for Call
    Check Users -> Permissions -> Grant Dial In box, login name, password

    If all the above suggestions fail, call, fax, or email Digi Tech Support


     

  27. What are the three  green LEDs on Datafire BRI ISA adapter for?
  28. D1 & D2 - Transmit and Receive lights for data across ISDN link
    D3            - Sync light (on or flashes intermitently)

    All lights will stay on until Digi ISDN driver loads


     

  29. How do I set up my  Datafire BRI ISA adapter dip switches?
  30. SW1 dip switch sets I/O port address
    OFF: switch away from board  ON: switch toward the board

               switch                           switch
     ------------------            ------------------
    addr   1    2    3     4         addr    1   2    3    4
    ----   ---  ---  ---  ---       ----    --- ---  ---  ---
    110    on  on   off  off       310    off  on   off  off
    140    on  off  on   off       340    off  off   on  off
    150    on  off  off   off       350    off  off   off  off
    300    off  on  on   off

    100 OHM termination switches for DataFire (SW2):

    Datafire S/T Dip Switch SW2
    The factory setting of SW2 is down, by default this places 100 ohm
    terminating resistors across the transmit and receive lines. In the
    event that another device is installed on the same BRI line, only one
    device should be terminated. If the other device's termination can not
    be easily disabled, reposition SW2 dip switch.
     
    Datafire S/T4 Dip Switch SW2
    The factory setting of SW2 is down, by default this places 100 ohm
    terminating resistors across the transmit and receive lines. In the
    event that another device is installed on the same BRI line, only one
    device should be terminated. If the other device's termination can not
    be easily disabled, reposition SW2 dip switch. Switch 7 & 8 used for
    Port 1, Switch 5 & 6 for Port 2, Switch 3 & 4 for Port 3, Switch 1 & 2
    for Port 4.


     

  31. How do I set up my  PC/IMAC adapter dip switches and jumpers?
  32. DS1 dip switch sets I/O port address - Memory & IRQ are done with driver.
    OFF: switch away from board  ON: switch toward the board

         switch                          switch
    ------------------             ------------------
    addr    1    2    3    4       addr     1    2    3    4
    ----   ---  ---  ---  ---      ----   ---  ---  ---  ---
    100    on   off  off  on       220    on   off  on   on
    110    off  on   off  on       300    off  on   on   on
    120    on   on   off  on       320    on   on   on   on
    200    off  off  on   on

    PC/IMAC jumpers

    Jumper Settings for Digi ISDN PC/IMAC - (has 3 jumpers)
    Jumper J1 should remain at factory default between pin 1 and 2 (top 2 pins)
    Jumpers J2 & J3 factory default is between pin 1 and 2 (top 2 pins)
    Jumpers J2 & J3 by default place 100 ohm terminating resistors across the
    transmit and receive lines. In the event that another device is installed on
    the same BRI line, only one device should be terminated. If the other device's
    termination can not be easily disabled, reposition J2 & J3 on PC/IMAC.
     
    Jumper Settings for Digi ISDN PC/IMAC4 (has 9 jumpers)
    Jumper J9 should remain at factory default between pin 1 and 2 (top 2 pins)
    Jumpers J1 - J8 factory default is between pin 1 and 2 (top 2 pins)
    Jumpers J1 - J8 by default place 100 ohm terminating resistors across the
    transmit and receive lines. In the event that another device is installed on
    the same BRI line, only one device should be terminated. If the other device's
    termination can not be easily disabled, reposition J1 - J8 on PC/IMAC4.
    J1-J2 control IDP1, J3-J4 for IDP2, J5-J6 for IDP3, J7-J8 for IDP4


     

  33. What does the  error message "Failure to converge PPP" mean?
  34. It indicates either a PPP authentication problem (PAP, CHAP, etc.) or Using Async PPP or V110/V120 protocols which are not supported (only sync PPP)


     

  35. Calling into a  Win NT with 2 channels but callback only calls back with one
  36. The ability to do a 2 channel call back only works when using Win NT 3.5.1 with (SP3) Service Pack 3. It is not yet working in Win NT 4.0 with any service packs.


     

  37. How can I use  AT command strings with the DataFire?
  38. The Datafire BRI and PC/IMAC adapters are not ISDN modems. they are more like ISDN ethernet boards.
    You do not use AT commands with them. Digi uses Microsoft's Dial Up Networking GUI to make or receive
    calls. If you are connection to a device that requires a terminal screen for entering additional connection info.
    Under Dial Up Networking Phonebook properties has an option for using a script. Modify default script to
    do the things done normally from terminal window.


     

  39. Can Win NT server route Digi ISDN traffic (internet) for local workstations?
  40. Yes, Microsoft has created Routing and Remote Access Service (formerly
    code named Steelhead) for Windows NT server providing advanced routing
    and internetworking capabilities.

    Routing and Remote Access Service features include:

    * A unified service for routing and remote access that's integrated
      with the operating system
    * A full set of routing protocols for IP and IPX
    * An easy intuitive remotable graphical user interface
    * APIs for third-party routing protocols, user interface, and management
    * Demand-dial routing
    * PPTP server-to-server for secure Virtual Private Networks
    * RADIUS client support

    Microsoft Routing and Remote Access Server can be found:

    http://www.microsoft.com/ntserver/info/Routing&RASdown.html

    Note: RRAS requires Win NT 4.0 with SP3 (Win NT 3.5.1 not supported)


     

  41. How can I do a ppp trace for debugging a connection problem?
  42. Attempt a connection. The ppp trace output will be logged a text file in your winnt directory + system32\ras\ with a filename ppp.log