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.
ISDN How do I know if the
Digi BRI ISA Win NT driver installed correctly?
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
ISDN What should I do
next if Digi BRI Win NT driver fails to load?
* 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
* 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
Does my Datafire (or PC/IMAC)
require an NT1?
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.
How do I make a 2
channel (Multilink PPP) call under Win NT 4.0? (Win NT 3.5.1 no multilink
PPP support)
(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
How do I make a 2
channel bonded (Digi to Digi) call with NT4.0?
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
How do I make a 2
channel bonded (Digi to Digi) call with NT 3.5.1?
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..
I'm having problems
calling out, what are 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
* 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
I'm having problems
calling in, what are basic things to check?
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
Problems with incoming/outgoing
PPP calls to other ISDN vendors products
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
What are the three green
LEDs on Datafire BRI ISA adapter for?
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
How do I set up my
Datafire BRI ISA adapter dip switches?
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.
How do I set up my
PC/IMAC adapter dip switches and jumpers?
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
What does the
error message "Failure to converge PPP" mean?
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)
Calling into a Win NT with
2 channels but callback only calls back with one
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.
How can I use AT command
strings with the DataFire?
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.
Can Win NT server route
Digi ISDN traffic (internet) for local workstations?
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)
How can I do a ppp trace for
debugging a connection problem?
- Pull down File Menu, click on RUN and enter regedt32
- Make the following selections in regedt32:
- HKEY_LOCAL_MACHINE on Local Machine
- Change Logging: REG_DWORD: from 0 to 1
- Exit regedt32 and reboot the system.
Attempt a connection. The ppp trace output will be logged a text file in
your winnt directory + system32\ras\ with a filename ppp.log