Frequently Asked Questions (FAQ)Digi ISDN BRI ISA products under Novell - Last Update: (2/8/99) -------------------------------------------------------------------------------How do I know what Digi ISDN Novell driver version I'm using?For PCIMAC.NLMAt server: run modules command, pcimac.nlm should be v2.0.8 of disk v1.5.2 At client: edit /system/pcimac/build file should be v2.0.8 of disk v1.5.2 OS: Novell 3.1X - 4.X Digi: PC IMAC, PC IMAC/X, Datafire U S1, Datafire S/T S1 ISDN Novell Classic (pcimac.nlm ONLY) drv vers 1.5.2Digi FTP (ftp.dgii.com) /support/legacy/digi/drivers/novell/4001220G.exe (disk 1 of 2) Digi FTP (ftp.dgii.com) /support/legacy/digi/drivers/novell/4001221G.exe (disk 2 of 2)ISDN Novell Netware Connect/MPR drv (dgncmdrv.nlm) filename: 4001544D.exeNote: Only Datafire BRI ISA S1 adapters are supported (not PC/IMAC) -------------------------------------------------------------------------------How do I know if the pcimac.nlm driver installed correctly?First, check for errors during install of pcimac.nlm on server console.Next run Line Status diag to check connection status to ISDN provider.From inconfig select Diagnostics -> Line Status -> ISDN portLayer 3 (Q.931) - This is a test to see if we are getting full serviceifrom the ISDN switch. It will check to see if switch type entered duringDigi driver configuration is correct. It will also check the SPIDs(typically, only used in the U.S.) against the values setup at the ISDNservice provider. These values must match exactly. It is just like apassword being approved.Layer 3 passes if: State = Active or Established, Awaiting Restart Service = Full or Non Initializing are acceptableIf you have 2 SPIDs you will see the above fields shown twiceThe first time for the 1st SPID, then again for the 2nd SPIDCheck both because you can have a problem with 1 B channel.If layer 3 fails :You should then go to layer 2 and test with dginfbri.Is the switch type entered during driver configuration correct?ISDN SwitchesNI-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.Layer 2 (Q.921) - 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 /l2Pass if : State = Tei Assigned Tei = Number between 64-127 Lap_State = Multiframe EstablishedIf layer 2 fails :You should then go to layer 1 and test with dginfbri.A TEI 127 means we are requesting a TEI from the Switch and have notreceived that yet. Without the TEI, calls are not possible.Causes for waiting TEI assignment:Command : sh idp /l3Line OK : State = Active or Established, Awaiting Restart Service = Full or Non Initializing are acceptableLayer 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 /l1Pass if : TX_Info_Pattern = Info3 RX_Info_Pattern = Info4If Layer 1 fails : Did the Digi driver load correctly, where there any errors on bootup? Check cabling. Use cables that came with Digi or find 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.-------------------------------------------------------------------------------Does Digi have any ISDN test numbers I can use?If your ISDN BRI line is provisioned for multipoint (1 SPID for each Bchannel) you can make a loopback call. Loopback testing can be found inyour software manual (calling out one B channel and in on the other). Digi U.S. ISDN Test Systems (available 7 days a week - 24 hours a day)Phone Number Operating System612-988-8328 Netware 4.1 Test System Line 1612-988-9011 Netware 4.1 Test System Line 2Login: guest Password: guest-------------------------------------------------------------------------------Problems calling out (pcimac.nlm), 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 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 -------------------------------------------------------------------------------Problems calling in (pcimac.nlm), what are basic things to check?Run iconfig.exe program. Under Installed Boards, select your Digi ISDNboard -> Installed Lines -> Check Address field. This should be yourISDN phone number, not the calling side. It must be one long number nospaces or dashes. In the U.S. it is usually the SPID minus any prefix orsuffix.iconfig -> Networks -> highligh listening network and select configureDoes the Remote field have a * (asterisk) to allow anyone to call in orif there is anything else the calling Network or profile name must matchIf all the above suggestions fail, call, fax, or email Digi Tech Support -------------------------------------------------------------------------------Virtual LAN Extension (pcimac.nlm) connection is staying up.First setup the link using the latest drivers and instructions fromISDN Novell software manual 92000205 (call Cust Service for new manual)Change your Timeout value to 15 seconds, if the line now drops but comesright back, you need to get the tech tip nov1sttx.txt and use it to findout what packet is keeping the link up. Otherwise, call Digi Tech supportNote: If using Netware 4.1 or 4.11 under your Install Network -> IPX Frame Type add NLSP=NO under Bind Options: -------------------------------------------------------------------------------Windows client running iconfig (pcimac.nlm) can't see Novell server Usually caused by not having a Novell shell (or correct one) configuredUsing Win 3.1 Main --> Windows Setup --> Network and pick a Netware shell.Using WFWG 3.11 Network --> Network Setup and pick correct Netware shell (Workstation shell 3.X for netx or Workstation shell 4.0 and above for vlms).-------------------------------------------------------------------------------Can my Digi ISDN Netware driver call Internet or other ISDN vendor products.To interconnect differnet vendors ISDN equipment you need a common protocolfor everyone to use. This protocol is PPP (point to point protocol).The pcimac.nlm does not have PPP support (uses Digi proprietary protocol) Use Digi's ISDN Netware MPR 3.1/Netware Connect 2.0 driver (dgncmdrv.nlm)The dgncmdrv.nlm driver does have PPP support, this driver requires you getfrom Novell either MPR 3.1 or Netware connect 2.0, (dgnvmdrv.nlm does notsupport PC/IMAC ISDN adapter), supports PPP connections to other ISDNvendors products. The latest driver 4001544C has a Novell early accessrelease of Multilink PPP for MPR 3.1 and Internetware NIAS4 (mlppp1.zip). -------------------------------------------------------------------------------I need to upgrade to a new Digi ISDN pcimac.nlm driver, what should I do?All of you current iconfig ISDN configuration information is stored in afile called pcimac.cfg in the f:\system directory. You should print out a copy of this file or make a backup copy of this file. file to another name or print this out.Load new ISDN Novell driver as if this were a brand new install.At server console prompt type - load a:\setupAnswer Yes to question "Update PCIMAC for Netware product files?"Answer Yes to question "Create default configuration file?"Current pcimac.cfg setting will be overwritten (backup/print pcimac.cfg first)Intermitent problems can occur using old pcimac.cfg and new driversRun inconfig utility and re-add ISDN and network configuration information-------------------------------------------------------------------------------ISDN (pcimac.nlm) connection is Active but I can't see the servers.This usually indicates a net number conflict in the system. Once youhave the active ISDN connection, you can now think of this as if youhave put ethernet cards in the servers and a ethernet cable in between.All servers are all connected as if on the same LAN. All internal netnumbers as well as those bound to the internal ethernet cards must beunique. So check all autoexec.ncf for problems.If you configured multiple installed networks with iconfig you will haveto check to make sure you are connecting to the correct one. If not thenet numbers will not match up and they need to when bridging. You canforce which installed network receives a call by using the remote field.Change the * (asterisk) to the name of the calling profile. It is justlike a password and must match exactly (it is case sensitive).The above scenario applies to both servers and clients. If a client callsin once fine but has problem if he reconnects. It may be connecting toa different installed Network. Use iconfig -> Networks -> highligh listeningnetwork and select configure Does the Remote field have a * (asterisk) toallow anyone to call in? If so change so calling profile name and Remotefield match this forces it to use the correct installed Network.-------------------------------------------------------------------------------DOS client connecting problems to Novell server (pcimac.nlm)Get dfbridos.txt this contains frequently asked questions ISDN DOS client.-------------------------------------------------------------------------------Problem with 2 channel outgoing calls (pcimac.nlm)Use iconfig - Highlight calling Network under Installed Networks and hitconfigure. Highlight the calling channel and hit configure. You shouldhave 2 channels under Assigned channels field.1st calling channel setup:Address - 1st phone number of remote sideLogical Terminal - Change to 1stB Channel - Change to B12nd calling channel setup:Address - 1st phone number again (only if) remote side has zero or 1 SPIDs - 2nd phone number if remote has 2 SPIDsLogical Terminal - Change to 1st - if remote has zero or 1 spids - Change to 2nd - if remote has 2 SPIDsB Channel - Change to B2-------------------------------------------------------------------------------Can I use Win95 or Win NT system to run iconfig (pcimac.nlm) program from?Yes, but must run the pcimac.nlm vers 1.4.3 or later. The vipx dependencythat was in earlier versions has been removed in the latest driver.-------------------------------------------------------------------------------How do I setup Digi ISDN card for TCP/IP under Novell pcimac.nlm?In the Novell environment with the PC/IMAC you may add a frame typeto allow the use of TCP/IP.Have TCP/IP installed in the Novell server (see Novell's TCP/IP manualfor further details).Open iconfigConfigure network that you want TCP/IP to be bridged over,Select configure for Assigned Frame TypeAdd frame type of Ethernet_IIEnable check-box ARPA (TCP/IP) Protocol.Enable Auto Bind check boxType in the IP address to be assignedUnder bind options enter option just like you would in autoexec.ncffile, i.e. mask=255.255.255.0 Click OK's to exit out.Check Novell console for errors with new binding. -------------------------------------------------------------------------------How should I set my Datafire hardware configuration Switch settings for Digi ISDN Datafire or Datafire4 cards. DS1 switch sets I/O port address - Memory & IRQ are done with driver. DS1 switches - OFF: switch away from board ON: switch toward board DS1 Switch: 1 2 3 4 DS1 Switch: 1 2 3 4 DS1 Switch: 1 2 3 4 I/O Port off: - - - - I/O Port off: x - - - I/O Port off: - x - - 350h on: x x x x 300h on: - x x x 140h on: x - x x DS1 Switch: 1 2 3 4 Pick non-conflicting I/O port address, best choices I/O Port off: x x - - are 350h or 340h. Use 110h or 140h as last choice 340h on: - - x x these are reserved or used by a number of devices. DS1 Switch: 1 2 3 4 DS1 Switch: 1 2 3 4 DS1 Switch: 1 2 3 4 I/O Port off: - - x - I/O Port off: x - x - I/O Port off: - x x - 110h on: x x - x 310h on: - x - x 150h on: x - - x DS2 dip switch sets Line Termination Datafire S/T Dip Switch DS2 The factory setting of DS2 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 DS2 dip switch. Datafire S/T4 Dip Switch DS2 The factory setting of DS2 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 DS2 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 should I set my PC/IMAC hardware configuration DS1 switches - OFF: switch away from board ON: switch toward board DS1 Switch: 1 2 3 4 DS1 Switch: 1 2 3 4 DS1 Switch: 1 2 3 4 I/O Port off: - - - - I/O Port off: x - - - I/O Port off: - x - - 320h on: x x x x 300h on: - x x x 220h on: x - x x DS1 Switch: 1 2 3 4 Pick non-conflicting I/O port address, best choices I/O Port off: x x - - are 320h or 300h. Use 100h or 110h as last choice 200h on: - - x x these are reserved or used by a number of devices. DS1 Switch: 1 2 3 4 DS1 Switch: 1 2 3 4 DS1 Switch: 1 2 3 4 I/O Port off: - - x - I/O Port off: x - x - I/O Port off: - x x - 120h on: x x - x 110h on: - x - x 100h on: x - - x 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's an NT1, why do I need one, and where do I get one?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 or Japan.