PO Box 3000
San Gregorio CA 94074 USA
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form by any means (electronic, mechanical, photocopied, recorded, or otherwise), without prior written permission from ISDN*tek, Inc. Except that ISDN*tek grants these rights to users of the ISDN*tek product for the customer's use in the normal operation and maintenance of the product.
CyberSpace Freedom, CyberSpace Card, CyberSpace Machines, “the Interface to Cyberspace”, PC*TE, CyberSpace Internet, CyberSpace Commuter, CyberSpace Enterprise, and ISDN*tek are trademarks of ISDN*tek, Inc. 5ESS is a trademark of AT&T. IBM/PC/XT/AT are registered trademarks of International Business Machines Corporation. Windows is a trademark of Microsoft Corporation. Chameleon and NetManage are trademarks of NetManage, Inc. InterRamp is a trademark of Performance Systems International, Inc. All other product names are trademarks of their respective owners.
ISDN*tek assumes no responsibility for the use of any circuitry other than circuitry embodied in ISDN*tek products. No other circuit patent licenses are implied.
Information furnished by ISDN*tek is believed to be accurate and reliable. However, no responsibility is assumed by ISDN*tek for its use, nor for any infringements of patents or other rights of third parties which may result from its use. No license is granted by implications or otherwise under any patent or patent right of ISDN*tek. Further, ISDN*tek reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation to notify any person or organization of such revision or changes; and ISDN*tek makes no commitment to update the information contained herein.
For more information see Copyright, Trademark, Patent & Warranty
Information in Appendix D.
Chapter One - What You Need
Chapter Two - Install Software
Chapter Three - Installing Under Windows 3.x
Chapter Four - Installing Your CyberSpace Card
Handset/Headset for Voice
Chapter Five - Board & Line Tests
Chapter Six - Troubleshooting
Your local phone company may use switching equipment from AT&T (5ESS), Northern Telecom (DMS100), or Siemens ( EWSD). The phone company will configure your line based on their central office (CO) equipment as well as your terminal equipment (TE). Your CyberSpace card (TE) will automatically work with all of that equipment without any special configuration on your part. However, it is important to provide the phone company with the template on the next page.
Pacific Bell has extensively tested the CyberSpace cards and has come up with a template for their engineers to use in programming ISDN lines for the CyberSpace products. Other telephone companies may also find this line translation information helpful. We are reprinting that table for the convenience of your telephone company service representative. When you call your telephone company’s ISDN order department, give them the information provided in the template.
When your line is installed, the phone company will provide you with your telephone (Directory) number and your Service Profile Indentifier (SPID). You may receive one set of numbers or two sets, depending on your telephone company’s equipment. Record this information, as you will need it later for hardware and software setups of any ISDN equipment that you install.
ISDN*tek CyberSpace Card Line Configuration Template
(B-Channels for CSV and CSD)
(D-channel for signalling only)
# channels for CSV
# channels for CSD
# of Call Appear
(Voice and Data for each B-channel)
(No D-channel packets)
PVC Protocol Version
Max# Programmable Keys
Release Key (N/Key#)
Ringing Indicator (Y/N)
(Voice and Data for each B-channel)
(No D-channel packets)
This section is purely optional. In addition to using the previous Line Configuration Template, you may also choose your own line configuration based on your current needs, economics, or future requirements, since each telephone company may bill differently for each group of options. The following capability sets are compatible with ISDN*tek equipment and may be viewed as alternative options for ordering your line. ISDN*tek recommends choice “M” for the most flexibility, which is the default selection for the previous Line Configuration Template.
NIUF Cyber # of Chan Typical Use Code Card Chan Type Description ----- ----- ----- ------- ------------------------------ B. I (1B) CSD 64K Internet access (data only) C. I,C (1B) CSVD 64K Internet OR voice G. I,C (2B) CSD+CSV 64K Internet AND voice (best choice for 64K Internet and POTS) I. I (2B) CSD+CSD 64K or 128K Internet (data only) J. I,C (2B) CSD+CSVD 64K Internet and voice, OR 128K Internet (Good choice for 128K Internet and sporadic POTS) K. I,C (2B) CSD+CSVD same as J but wih some calling features that are not used by the CyberSpace cards. L. I,C (2B) CSD+CSVD same as K but with EKTS for an ISDN telephone set with programmable feature keys. M. I,C (2B) CSVD+CSVD 64K data and voice, OR 128K data, OR two voice lines (best choice for the Commuter Card and the most flexible choice for the Internet Card with POTS)
If you have other hardware working over ISDN and have no other cards in your computer, you may want to shortcut the installation procedure using the steps outlined below. However, because of the complexity of current PCs, we recommend following the installation and test procedure outlined in the following chapters.
From the Windows Program Manager, select Run, and enter A:ISDNTEK.EXE to auto install from the distribution diskette. The following programs and files will be decompressed and copied to the directory that you specify in the installation procedure.
DDEML.DLL Visual Basic Support
DIALER.EXE Voice Dialer for Commuter Card
ISDNTEK.DLL ISDN*tek ISDN Specific Driver
ISDNTEST.EXE Program to Test Board and Line
SETUP.EXE Driver Installer
VBRUN300.DLL Visual Basic Run-Time DLL
VWINISDN.386 VxD-Based ISDN Driver
VWNISDN.D16 DLL Helper for VxD Driver
ISDNTEK.SYS NT ISDN Driver
ISDNTEK.SYS NT ISDN Driver
(Requires MSISDN_PAK 1.1 or WSOCKUPD.EXE and MSDUN12.EXE)
ISDNTEK.SYS Win95 ISDN Driver
IMPORTANT: Two files required by some applications are not included on the installation diskette. They will be created when you run the ISDNtest program:
ISDN.INI Initialization File
WINISDN.DLL Hardware Driver
The ISDNtek.exe self-extraction program writes all files to a temporary location on disk. A setup program is automatically invoked to allow you to choose a destination subdirectory and to install or un-install the VxD or DLL drivers. The default VxD installation is recommended for all but NT and OS/2 users.
The 32-bit VxD-based ISDN Driver (vwinisdn.386) is the default at installation, and in addition to allowing simultaneous use of the ISDN Accelerator Pack and WinISDN-based applications, it is ShivaPPP approved for communicating with the LanRover on a Novell network from Win 3.1x and Windows for Workgroups (WFW) machines.
An NT subdirectory is created containing Drivers for NT machines. Check the Windows NT installation manual for information on the current version supported and for installation instructions.
The Win95 subdirectory contains the latest mini-port drivers for installation and use with the Microsoft ISDN Accelerator Pack. The Microsoft files should be loaded prior to installing the ISDNtek drivers. Installation instructions and supported versions are found in the readme file.
After installing the files, reboot Windows, select the Test ISDN Hardware icon or run the ISDNtest.exe program to configure and test your ISDN hardware.
See applicable installation manuals for other operating systems.
The ISDNTEST install/test program provides configuration assistance for your ISDN*tek CyberSpace Card. There are many systems that must work together to provide you with a seamless interface to CyberSpace, and this card sits squarely in the middle. For this reason, it is important to check each interface at every step of the installation.
It is also important that you perform the following tasks before you install the hardware: set switch settings, search for memory conflicts, and enter ISDN line information..
Note: This installation and test software may have been distributed in compressed format.
Access the ISDN*tek software interface through the following path: START, PROGRAMS, ISDN SETUP, and, finally, TEST ISDN HARDWARE.
You can run certain sections of the program while you still have the card in your hand. The first section of the Setup screen allows you to see the values of the switch settings. The default address is D000 and the IRQ is factory set to 10. If you are aware of system conflicts at this time, then you should physically change the settings on your board now. Use the icons on the screen to assist you. You should also review the “Troubleshooting” section on system memory conflicts.
Optional starting addresses are D000, D400, D800, DC00, etc. Available interrupts usually range among 9,10,11,12,14,15, or 5. See Chapter Four - Installing Your CyberSpace Card for more details.
The Board Description is an arbitrary name of your choice for saving your diagnostics log to file. If omitted, a name will be assigned. (A special suffix ~RevB should be added for some upgraded boards.)
When you think you have appropriate settings, then click on SET. This will save your settings to the ISDN.INI file and will search through your CONFIG.SYS and SYSTEM.INI and make recommendations regarding memory conflicts. It will not actually change your files, nor will it test for conflicting settings. It will, however, print the path and contents of these files into the log window.
your diagnostic log to file using the Test Log pull-down, as you may need
this information later. You may repeat this stage as often as you wish
or need, and save your log as often as you want.
The Save Settings and Get Settings options in the pull-down menu allow you to save and retrieve the information in your ISDN.INI file at any time as well.
Each ISDN line is assigned a Service Profile Indentifier (SPID) which tells the local switch what kind of features are supported by your equipment. This SPID generally looks like your phone number, with a few extra digits placed before and after. Depending on your phone company’s equipment, you may have been assigned either one, two, or no SPIDs, which you should enter here. Not all switches require a SPID, but for the ones that do, it is VERY IMPORTANT that you enter the SPID correctly. The SPID should be entered before installing your card. If your card is already installed, then reset the card after entering or changing the SPID.
When you click the SET button, these settings will be saved to your ISDN.INI file and to a section in your SYSTEM.INI file.
Now it's time to install your ISDN*tek card. Proceed to Chapter Four.
full range of Memory Addresses from 0000 to FFFF are available to the board
through switch settings. Four are shown:
Below is a list of typical IRQ assignments. Check for possible conflicts before assigning an IRQ to your CyberSpace Card.
IRQ Typical IRQ Assignment
The CyberSpace boards with an S/T-interface provide100 ohm termination resistors that are preset with jumpers on W3 and W4 near the phone jack. Removing the jumpers will remove the resistors from the circuit. These jumpers will generally remain as set on the board unless additional equipment is on the same phone line. The CyberSpace+Plus boards, with a U-interface, do not use termination resistors.
For voice applications, the Commuter Card has a standard 4-wire jack for a handset or headset. Generally, the handset from your existing analog phone should work just fine. Headsets are available in a wide variety of styles, and most of them include a volume control for comfort and aural safety. Not all headsets will work with the CyberSpace Commuter card, so ISDN*tek will be publishing a list of compatible types on it’s homepage at http://www.isdntek.com.
In order to run board and line diagnostics, you will need to return to the ISDN*tek software interface. From Windows 3.x, you may access Test ISDN Hardware through ISDN SETUP Group, Test ISDN Hardware program. From Windows '95, the path from the Start button is: START, PROGRAMS, ISDN SETUP, TEST ISDN HARDWARE.
NOTE: Board and Line diagnostics are not yet available under Windows NT operating systems.
This is the first actual test. Clicking the TEST button will tell the program to read three information fields from the board. If the fields cannot be read, an error message will indicate that there is a problem in the hardware settings on the board, or in the configuration files, or with conflicting hardware. This should be resolved before proceeding. If you get a partial reading of the board information, then you may need to reset the hardware, using the RESET button at the top of the screen or in the TEST pull-down, and try again.
This final test is the first attempt at touching the telephone side of the system. It should not be attempted until you have seen a successful Board Test and have resolved any hardware conflicts.
Plug the telephone cable into the CyberSpace Card in your computer and into the S/T jack on your Network Termination (NT1) box (or directly into the wall jack if you have a “Plus” card).
The screen provides an area for entering the number of a nearby phone. You should enter a number to be called during the test. The number should be that of a nearby phone, so that you can hear it ring as an indiction of a good telephone connection. Option buttons at the bottom are for setting the type of call, either Voice, 56K, 64K, 112K, or 128K. The Voice button is the default, to be used for the Ringing test to the nearby phone. After clicking the Start button, the test is automatic and begins with Open ISDN Board, Start Diagnostics, and Dialing your phone number.
the Connect to ISDN request is transmitted. At this point, if you have
a good line connection, you will receive several switch responses such
as, Setup, Setup Acknowledge, Information, Call Proceeding, etc. (if you
answer the phone you will also see a Connect response and a green indicator
on the screen), otherwise you will experience a 30 second timeout. You
can stop the test at any time by clicking the Stop button (the same button
used to Start the test), which has the same effect as hanging up the phone.
Timeouts may occur for various reasons, including forgetting to plug in the phone cable. Other reasons include incompatibility with the local switch (not upgraded to the current NI-1 standard), an improperly configured line, or a bad or incomplete SPID. You should save your diagnostics log to file for troubleshooting with your service representative. See the “Troubleshooting” chapter for problems.
If your nearby phone rang successfully, you are ready to try a call into your Internet Provider’s ISDN access point or to another ISDN device. Replace your local test phone number with the access phone number for the Internet and select the 56K option. (Although the 64K option is presented, not all trunk lines are capable of carrying a 64K call to another exchange, so you should confirm the 56K connection before attempting a 64K connection). As the messages flow down the screen, you should see a Connect message from the switch, indicating that you have reached your service provider’s router.
Congratulations! Now you can use your TCP/IP software to access the Internet or transfer files directly to another ISDN computer.
Notice there are three test modes available. The line test will automatically run for 30 seconds in Auto mode. To run the test for an unlimited amount of time, select the Manual option before starting the test. The Monitor option is useful in applications such as Win95, since the Microsoft ISDN dialer does not provide any diagnostics. The Monitor does not perform any tests, it simply listens to the connection and displays diagnostic information. Select Monitor mode and start the Test, then make a call using the Microsoft Dialer. The ISDN messages will be displayed in the Log window. You may terminate the Monitor at any time without affecting your connection.
The pull-down menus follow typical Windows conventions. More detailed information on each menu item is presented in this section.
The File section provides Save features for both the INI file and the diagnostics Log. For convenience, these features are also duplicated in other menus and are described later.
The Exit selection terminates the program and is identical to using the Windows Program Close option in the upper left corner of the program window.
The Setup section allows you to enter new Board settings or Line settings. You may also save to, and retrieve these settings from, the initialization file.
When you have changed the information in the Board Settings and Line Info screens, you may save this information to your initialization file to be used each time the program is restarted. There are two ways to save these settings, with either the SET button on each screen, or through the pull-down menu. If you have not made any changes since the last save, then nothing will happen. Otherwise, you will be asked whether you want to save these changes to the Initialization file.
Get Settings from File
If you have made modifications to the Board or Line settings, and have not saved them or selected SET, then you may recall the prior settings with the Get Settings option. Each time you Get Settings, the Board and Line settings will be written into the Log Window. This is useful to have for troubleshooting documentation.
The Test pull-down provides access to the two test routines for the Board and the Line. You may also reset the board from this menu if you have encountered difficulties in operating the software.
The hardware will need to be reset if you changed your SPID, or if hardware or software problems occur. The Reset selection is identical to the reset button found in the upper right area of the screen. Generally, you will not want to reset the hardware unless necessary, since it is the equivalent of unplugging your equipment. When you do reset, the switch at your local phone company may take several minutes to re-establish a communications link with the board. This is consistent with the time required for a line to stabilize after connecting any kind of equipment to your ISDN line.
3. Test Board
The Test Board selection is equivalent to clicking the Board Test button. It will test the CyberSpace card to verify that it is communicating with the software without system conflicts.
4. Start Line Test
The Start Line Test selection is equivalent to the the Start button on the Line Test screen, and will run the Line test to verify that the ISDN line is up and operational.
The Log selection manipulates the Log Window output. The Log may be Viewed, Saved to disk, Printed, or Cleared from memory.
Save option will save the entire Log to a disk file. You will be prompted
for the file name, and may use any valid DOS name, including drive and
path designations. If the file already exists, then you will be asked whether
the file should be overwritten. Before the Log is written to file, time
and date information will be written above the data, providing tracking
info for each Log file.
The Print option will print the entire contents of the Log Window to the Windows designated Printer Port. Time and date information will precede the Log contents, so that the printout can be easily identified.
The Clear option will erase the entire Log Window contents on the screen. You may wish to save the Log Window to file before erasing the Log. Once erased, the Log contents cannot be restored. The Log Window will hold about 20 pages of information, and should be cleared if you are nearing that limit.
The Log window automatically opens with the program and can be Minimized or closed. The Open command displays a previously minimized log or opens a new empty log if it was previously closed.
Advanced features are available for testing multiboard installations and for receiving incoming calls.
Answer mode allows the user to test a two-channel line by calling out one B-channel into the other B-channel. It also allows a service representative to call into the site for remote testing of line problems. Answer mode is always disabled when the program is started. To use answer mode, checkmark the option prior to starting a line test, so that incoming calls will automatically be answered by the software. While Answer mode is allowable in Monitor mode, it should be used carefully. Undesirable behavior may result if the monitor answers a call intended for the application being monitored.
Up to four ISDN*tek cards may reside in a single computer, although there are a limited number of applications that support four boards. The multiboard option allows the user to select any one of four boards for testing purposes. Only one board at a time may be tested. As each board is selected, the board profile parameters (memory, IRQ, and SPIDs) are displayed in the Board Settings and Line Info fields. If changes are made to the settings, then the user should save those settings before selecting the next board.
Information is provided about the current version of the software and
the underlying DLL driver for the CyberSpace card.
For your convenience, ISDN*tek provides a simple Phone Dialer Mini-Application to use voice products such as the CyberSpace Commuter Card. This application will run on the CyberSpace card simultaneously with the TCP/IP Internet software and provides support for incoming and outgoing voice calls. The Dialer application must be running in order to receive incoming calls. Your computer will alert you with a ringing tone. The voice channel can be active while the Internet software is running on the data channel of your ISDN phone line.
You may use a mouse and the Dialer Keypad or you may use your computer keyboard to dial phone numbers.
To Dial a number without changing or creating a new phone book entry, simply enter a dialing number leaving the name field blank. Either Carriage Return or clicking on the CALL button will dial the number and place the call. There is also a pull-down menu Call/Answer option to place a call, or the keyboard shortcut Ctrl-C can be used.
Either the other party may hang up the call, or you may click the HANG-UP (Call) button (or use the Call pull-down menu) to terminate the call first. If the other party hangs up first, there will be a time delay before you will see your Dialer screen display the call termination and restore the Call button to its ready position.
An incoming call will ring your computer with an alerting tone and will convert the Call button to a flashing green ANSWER icon. Click on the ANSWER button or use the pull-down Call/Answer option or Ctrl-C to answer the call. Once a call is connected, a green HANG-UP icon will appear to let you know what action is available next.
a call is connected, typing any number key from the keyboard or from the
software panel will send DTMF “TouchTones” over the line. To store a DTMF
Tone with a phone number, there are two punctuation symbols that may be
inserted in the dialing string. A semicolon (;) is used to detect a connection
with the other end, and any numbers after the semicolon will be sent as
DTMF tones. A comma (,) is used for a three-second pause between sequences
of numbers, which is useful when engaging tone activated menu trees. Multiple
pauses may be inserted in a number. There are two shortcut buttons on the
screen for these two features, "Detect" and "Pause."
To automatically dial a number from the phone directory, double-click on the directory name or number of the party you wish to call. To view and then dial a number, single-click on the directory name or number. This places the name and number in the input fields, which you may alter. Now click the CALL button to place the call.
Initial phone book entries are saved in a simple comma-delimited file called PHONE.LST in the local program directory. This is the default phone book that will always be loaded at the beginning of each session, but additional phone directories can be created. The first time you start, you will have an empty phone directory. Each time you add an entry, it is automatically saved to file. You can create a new phone book by saving an empty or full phone book to a new name and then editing or deleting the entries. The name of the file being edited will be displayed at the top of the phone book.
If you know you have an existing phone book called PHONE.LST and it is not displayed at startup, then either it is not in the current directory or the path is not properly set in the Window Properties for this program.
New entries are made in the two input fields, Dialing Name and Dialing Number. Begin with empty input fields. Use the CLEAR button if necessary to clear out any previous information in the two entry fields. It is necessary to enter both the Name and the Number. A Carriage Return (ENTER) after the second entry adds the entry to the Phone Directory. The new entry can also be added to the directory using the ADD button or the Add option within the EDIT pull-down menu.
There are times when you may wish to change either the name or number of a party in the Phone Book. Click on the Directory listing to display the information in the input fields. Edit the name OR number and press Carriage Return (ENTER) to save the changes to the Phone Book. If you change BOTH the name and the number and then press Carriage Return (ENTER), you will create a new listing. Alternatively, you may change both entries and use the pull-down Edit menu and select REVISE, to replace your old listing with the new one, without creating a new entry.
To delete a listing from the Phone Book, click on the party’s directory name or number to display the information in the input fields. Then use the EDIT pull-down menu and select Delete.
To undelete the last deleted directory listing, use the EDIT pull-down menu and click on Undelete. Undelete works on only the last delete. You cannot undelete several items.
Use the FILE pull-down menu and select Print to send your directory listings to your Windows printer.
Dialer provides volume control for both the micophone (Talk) and the speaker
(Hear) of your handset or headset. There is a slider on the screen for
each function, which can be adjusted once a call is underway.
A pair of option buttons allow you to choose between incoming calls that ring so that you may manually answer, or incoming calls that are automatically answered by the software, immediately connecting the incoming caller without announcement. Each time the software is launched, it defaults to Ringing. Generally, for privacy, you will want to leave your software set to the Ringing default.
Caller ID is available for NI-1 lines that have the Caller ID feature implemented. The Caller ID information automatically displays in a pop-up window when an incoming call is announced.
Some of the troubleshooting procedures are performed on ther basis of information supplied by ISDN*tek's diagnostic tools. These diagnostic tools (Line and Board tests) are not yet available under the Windows NT operating system.
The first four sections of Troubleshooting are based on where in the installation process the trouble occurs:
Each of these four categories assumes you have successfully bypassed all the previous potential problems. For instance, a Line test should have been preceeded by a Board test; and you should not report an Application problem if you have not performed and passed the Board test and the Line test. The four sections address the most likely problems, the reason for occurrence, and typical solutions. The convention used is:
[ Problem (symptom), Cause (reason), Solution ]
Complete end-to-end connections required for Internet access.
This section describes major system failures. Although the symptoms seem fatal, the problem is relatively easy to locate and resolve by removing the hardware and changing the Address and/or IRQ setting.
1. The system locks up.
The problem may appear after installing the card, when the system, video, keyboard, or mouse will not respond because of hardware conflicts between one of the system components and the card.
This is usually a Memory conflict or an Interrupt Request (IRQ) conflict with other hardware in the system. The conflicting hardware could include the above essential systems components, or another added card.
First check your IRQ. Although the CyberSpace Card presents the entire range of IRQs, many of them are already used by the system, as listed in the chapter on “Installing your CyberSpace Card”. Generally, the IRQs available to add-in hardware are 5, 9, 10, 11, and 15.
Second, be sure to select an available Memory Address. For additional information on how to resolve memory conflicts, review the Board Memory Diagnostics section later in this chapter.
2. Windows won’t boot or dies on exit
The Problem could involve a conflict (with other hardware, or with memory managers, or TSRs) that was not encountered until provoked in a Windows session.
The solution is the same as for the system lockup above and generally represents a Memory or IRQ conflict with system or add-in hardware that is not critical to starting the system, but which is activated later in a session.
This section describes failures encountered from within the “ISDNtest” Test/Install program that display in a pop-up dialog window (this program's features are not available under Windows NT) In this section, the BOARD TEST option failed or was only partially successful.
Failures usually involve a Memory or IRQ conflict with other add-in hardware (video monitor, LAN card, SoundBlaster, CD Rom, etc), a Shadow Memory issue, or a mismatch between the board settings and the software settings.
1. “Memory Access Error” Message
The problem could involve System Shadow Functions that hide the memory space required by the board:
Use the computer Setup utility to disable shadowing for the address range selected for the card (disabling shadowing enables direct access to the board). For additional information on how to disable Shadow Memory, review the Board Memory Diagnostics section later in this chapter.
The problem could involve a conflict with other hardware trying to use the same memory space:
Use a different address selection to avoid conflicts. With the card out of the system, run MSD to determine available locations. Review MSD and Memory Conflicts under Board Memory Diagnostics later in this chapter.
The problem could involve a conflict with system memory managers that remap the Real memory (required by the board) into Protected memory:
Use exclude statements to prevent memory managers from using the address range selected for the card. The format of the Memory Exclude statements is discussed in the Board Memory Diagnostics section later in this chapter.
The problem could involve a mismatch between the card switch settings and software:
Be sure the physical board settings for both the memory address and the IRQ match the software settings. You must change both when modifying your settings. You may also wish to refer to the Hardware Installation Chapter for a side view of the memory switch depicting the ON and OFF positions for the switches.
2. “No Response from Hardware” Message
The problem could involve Memory Conflicts with other hardware or with the system:
Generally, the memory existed and was encountered by the test program, but the lack of response could indicate that the memory belonged to other hardware. Review possible conflicts from Memory Access Error. For additional information on how to resolve memory conflicts, review the Board Memory Diagnostics section later in this chapter.
The problem could involve an Interrupt Conflict with other hardware, although this is the least likely problem:
Select an interrupt request (IRQ) not used by other devices. The typical IRQ values used by the system are listed in the chapter on “Installing your CyberSpace Card”.
The problem could involve a mismatch between card jumper settings and software:
Be sure the physical board settings for both the memory address and the IRQ match the software settings. You must change both hardware and software when modifying your settings. You may also wish to refer to the Hardware Installation Chapter for a side view of the memory switch depicting the ON and OFF positions for the switches.
The problem could be that you are using the wrong WinISDN.DLL driver version:
Check the driver version in the ABOUT pull-down menu to verify that the Test program is utilizing the latest version that came with your hardware. If you have installed an application program AFTER you have installed the test routines, then you may need to re-install the WinISDN.DLL and ISDNtek.DLL that were delivered with your hardware. Contact ISDN*tek or your sales person to verify the appropriate driver version.
3. “Cannot Perform Function” Message
The problem could involve an Interrupt Conflict with other hardware in the system:
Select an interrupt request (IRQ) not used by other devices. The typical IRQ values used by the system are listed in the chapter on “Installing your CyberSpace Card”.
The problem could involve a mismatch between the card IRQ settings and software settings:
Be sure the physical board settings for both the memory address and the IRQ match the software settings. You must change both the hardware and the software values when modifying your settings.
This section assumes successful completion of the BOARD TEST option of the “ISDNtest” Test/Install program (again, this program's features are not available under Windows NT). Here, we describe LINE TEST failures that display as messages in the program’s Log Window.
In this section, the LINE TEST option failed or returned inconclusive results. These failures generally involve problems with the phone number, Service Profile Identifier (SPID), or ISDN line configuration. Most problems are resolved without Telco intervention, but occasionally, where line configuration and transport trunk lines are concerned, the Telco will need to be involved and will need the information displayed in your Log window. Therefore, we recommend that you always save your Log Window to file.
1. “No Response from Switch” Message (From within the “ISDNtest” Test/Install program, the LINE TEST option failed to engage the telephone company’s switch, the equivalent of a dead line).
The problem could involve an improper IRQ setting that prevented Switch responses from reaching the Log window:
If the called phone successfully rang but the Test software returns a “No Response from Switch”, then the IRQ setting is wrong and the hardware could not interrupt the computer to pass along the Switch messages. Check that the board is using an available interrupt and that the hardware settings match the software settings.
The problem could involve using two SPIDs when only one is allowed by your line configuration:
If the Test log timed out at the “SPID=” sentence, then it is possible that the SPID is invalid or that too many SPIDs have been entered. Point-to-point lines use only one SPID, and entering more than one SPID for that type of line will cause faulty behavior. Review the other SPID problems later in this section for additional information.
The problem could be that the NT1 is not connected:
Be sure the phone cables are in the correct jacks on the NT1 and that the NT1 power supply is plugged into a live electrical outlet. Check that the cable from the board is plugged into the “S/T” jack of the NT1 and the cable from the wall jack is plugged into the “U” jack of the NT1. (review your NT1 documentation). Look for error lights on the NT1.
The problem could be that the CyberSpace Card is not connected to the NT1:
Be sure you are using the correct cable type and that it is firmly plugged into the card and into the NT1 “S/T” jack.
The problem could involve conflicting ISDN Hardware:
Do not connect non-ISDN equipment to your NT1. LAN equipment may use an RJ45 jack similar to the ISDN jack. Check your cabling carefully.
2. Immediate “Release Complete . . .Facility not Subscribed” (Switch RESPONDED during the line test, but the call was unsuccessful.)
The Problem could involve an incorrect or incomplete SPID:
Sometimes a SPID must be followed by a SPID suffix (from the phone company) and a TID (2 digits determined by the user). The user defined TID (Terminal ID) should be non-zero and unique for each TID, such as 11 and 22. Confirm with your Telephone company the complete number of digits required by your line. Enter the correct SPID, save to the ISDN.INI file (SET command), and reset the card to activate a new SPID. It is sometimes best to pull the S-interface cable, reset the card, then plug the cable in again to force the Switch to restart the line.
The problem could involve using the wrong SPID:
Given two SPIDs, the wrong SPID was chosen for your call type. Reverse the SPIDs that will be saved to your ISDN.INI File. Proceed as for Incomplete SPID above.
The problem could be a Line Configuration problem:
You may be trying to place a voice call on a line with only data service, or a data call on a line with only voice service. Contact your Telco to change line configuration to allow the requested call type — circuit switched voice/data is most flexible. Note, be sure to try a 56K call if a 64K call fails, in case 64K is not supported in your area.
3. Immediate “Release Complete” . . then other diagnostic cause codes. (Switch RESPONDED during the line test, but the call was unsuccessful.)
The problem could involve a line configuration problem or could be alternate terminology for “facility not subscribed”:
Try to determine what the cause code is telling you. Review problems from the preceding “Immediate Release Complete, facility not subscribed” description.
4. “Setup Acknowledge” followed by a “Disconnect” or “Release Complete”. (Switch RESPONDED during the line test, but the call was unsuccessful.)
The problem may involve an improperly formed telephone number:
Verify the number you are dialing, including prefix for outside line if Centrex (9) and one (1) before area code. Avoid punctuation in phone number string.
The problem may involve a Telco Routing Problem:
Try to dial a different phone number. Contact your Telco to test routing for the number you are trying to dial. Problem could be in trunk line or long distance service, not the local connection between you and the central office.
5. “Call Proceeding”, followed by a “Disconnect ”, or“Release Complete”, or no other messages. (Switch RESPONDED during the line test, but the call was unsuccessful.)
The problem could involve an incorrect telephone number or a routing problem:
Review problems from Setup Acknowledge above.
The problem could involve Long Distance Service or trunk line problems:
Contact your Telco to verify routing for the phone number desired, and ISDN data capabilities of the long distance service used, if a long distance call.
The “ISDNtest” Test/install procedure works (though not in Windows NT as "ISDNtest" is not available), but trouble arises from using your application software.
1. Call Fails
The problem could involve an improperly formed telephone number:
Avoid punctuation within the dialing string. Verify that you are using the correct telephone number, including any necessary prefixes such as one (1) or nine (9). Try dialing the same number using ISDNTEST software. Enable diagnostics in your application, if available, to see messages as the call is placed.
The problem may involve WinISDN.DLL driver or ISDN.INI file problems:
Be sure the same versions of WinISDN.DLL and ISDN.INI are used by the TCP/IP software and ISDNTEST software, by keeping these files in the Windows or System directory. Remove any duplicate copies of these files from directories in the path. Use the most recent version of WinISDN.DLL, as supplied with the board.
2. Call Connects, but Service Provider logon fails
The problem could involve an incorrect logon user name, password, or account number:
Verify entries for your logon account number and password (Password Authentication Protocol, PAP).
The problem could involve an incorrect telephone number or call type:
Check that you are using a data call and are calling the correct telephone number for the ISDN data service of your service provider. This may or may not be different from the number used for analog modem calls.
3. Previously working system fails after software update
The problem could involve TCP/IP software that came with an old Driver:
The installation of a TCP/IP software upgrade could have written an old WinISDN driver over the existing driver. Confirm the DLL version in the About menu option of the ISDNTEST Test/Install program. If the version is invalid, remove or rename any copies of WinISDN.DLL that are on the system. Reinstall or Copy the ISDNtek.DLL that came with the card. The compressed file ISDNtek.DL_ can be unzipped with the Expand.exe program supplied with Windows if necessary, using the command structure: EXPAND Source Destination
example: EXPAND A:ISDNTEK.DL_ C:\Path\ISDNTEK.DLL
Then copy the ISDNTEK.DLL into WINISDN.DLL, or run the ISDNTEST program which will recreate the WinISDN.DLL in the Windows or System directory.
Any card you install in your computer may potentially conflict with other hardware unless you set each card with a unique address and interrupt. This section could help you resolve conflicts with any hardware you may have installed, including your ISDN*tek board. These conflicts generally fall into three different classes, Shadow Memory, conflicts with other hardware, and memory managers.
Memory conflicts may be suspected if you try to run the ISDN*tek software, but get errors during hardware resets of the boards, cannot get a proper serial number display, or if some part of the system fails to boot after installing the hardware.
Many machines, in an effort to improve “benchmark” speed tests, use Shadow Memory functions, in which regions of hardware memory, such as ROM BIOS, adaptor ROM, and adaptor RAM are copied and remapped into faster system memory. More recent machines are also shadowing the entire upper memory region between A000h and FFFFh.
This upper Shadow Memory can cause problems for hardware, since all memory access would be remapped into system RAM instead of the real hardware of an adaptor board, such as the CyberSpace Card. The remapping prevents access to the real hardware, and thus keeps the CyberSpace Card from working.
The symptoms of Shadow Memory problems, as seen by the CyberSpace Card, include “System Memory Access” errors when trying to use the Card, or the Memory Footprint of the CyberSpace Card not showing up on the MSD Memory Map (see MSD later).
Fortunately, these systems allow you to disable the shadowing function for a specified address region, allowing access to the real hardware again. This is normally controlled in the system setup program, accessed at bootup by various key combinations, such as F1, Ctrl-S, Ctl-Alt-Enter, or Esc, etc. Refer to your system documentation or the message on the screen during bootup.
The control of shadowing is located in various places within the setup program. Sometimes it is located in Advanced CMOS settings, with options such as a display of Shadow RAM for various segments. Be sure that Shadow RAM is “Disabled” for the segment containing the CyberSpace Card.
In most systems you will set “Shadow RAM: Disabled” but, in some systems the entry reads “Disable Shadow ROM:” which must be “Enabled” to turn off the shadow function (watch carefully for the double negative wording)!
In other systems, the word “shadowing” is not used. For example, some systems have a “Plug and Play” page within setup, and in this page have an entry called “ISA Shared Memory Size”. When this is “disabled”, shadowing is used for the entire upper memory region (more double negative wording). You must select a memory size of no less than 4K bytes (up to 16K bytes) to match the amount of memory space required by the CyberSpace Card.
Once the size option is specified, another option is enabled, requesting the memory “Base Address”. Here, you should select the base address set for the board, such as D000, D400, etc. When both the Shared Memory Size and Base Address have been set, the system will no longer use shadowing for the specified memory window, and the CyberSpace boards will work well in the system.
The second potential conflict is with other system adaptors and memory. You must find an area of real mode (under 1 MByte) memory that is not used in your system. For example, most systems do not have any memory in the 64 KByte region D000:0000 to D000:FFFF.
Some utilities may help you identify available regions of address space in your system, but they will be system specific. In general, you must find out where any hardware adaptors are located, and how much ROM BIOS area is used in your system.
Windows includes a DOS program called MSD which is fairly helpful in identifying which sections of memory are allocated. However, it cannot always detect all memory uses.
should be started from DOS, not from Windows. After starting MSD (C:>MSD),
select the Memory button in the first screen to display a memory map of
your computer. You will generally be looking for a section of memory that
is mapped as solid black, “available”, when the CyberSpace Card is not
plugged into the system. With the card plugged in, some of the selected
memory space for the card will display as RAM. You DO NOT want any other
pattern in the memory space of the card, such as page frames, UMBs, etc.
Each horizontal line of the display represents a 400h block (16K bytes)
of memory. You will need 4K bytes (1/4 line) of available memory for the
If no satisfactory region displays as available, you may be able to use a section of memory that is allocated to Expanded Memory (EMS) functions, or to Upper Memory Blocks (UMBs), by placing EXCLUDE statements in your configuration files, as described in the next section.
The third potential memory conflict is usually associated with memory managers, such as EMM386.EXE, or protected mode systems environments, such as Windows 3.x.
In these cases, the memory management program might choose to map some of the real mode memory areas into protected mode memory, to implement Expanded Memory (EMS) functions, or to provide Upper Memory Blocks (UMBs) for device drivers and TSR programs. These actions may conflict with the access to the real hardware on ISDN*tek boards if the mapping is performed in address regions used by the boards.
Fortunately, these memory managers usually have options that allow you to specify regions of memory to exclude from the mapping functions. Two specific examples are given for the DOS/Windows environment. If you use a different memory manager, check the documentation for it, to determine an equivalent function.
If your CONFIG.SYS file contains a “device=emm386.exe” statement, you may need to add an option to exclude the memory region used by ISDN*tek boards. If you select the 64 KByte region D000:0000 to D000:FFFF, as mentioned above, an example command might be:
DEVICE=C:\DOS\emm386.exe 2048 RAM X=A000-AFFF X=D000-DFFF
where the “X=A000-AFFF” may already have been in the statement and you are adding the “X=D000-DFFF” to specify the regions of memory to exclude, in real mode paragraph notation. Note that if you are using fewer than four ISDN*tek boards, you may exclude as little as 16Kbytes per board (4K bytes for newer versions). For example, one board located at D000:0000 would only need to exclude “X=D000-D3FF” for 16K (X=D000-D0FF for 4K).
Under Windows 3.x, you might also need to modify the SYSTEM.INI file, to contain an EMMExclude command, which performs a similar function to the example shown above. The proper command would be:
to again specify a full 64 KByte region. A smaller region can be used for fewer boards, for example “D000-D7FF” for two boards, at D000:0000 and D400:0000.
The EMMExclude command must be added to the SYSTEM.INI file under the “[386Enh]” section. The file may be modified by a standard word processor program.
The WinISDN DLL supports diagnostic messages to assist in determining the cause of any problems that relate to either the ISDN card or the ISDN line, including those problems where the call has left the local telephone central office and has gotten lost in the phone system.
Most TCP/IP stacks will display a “Log” window. The WinISDN driver, if enabled, will send ISDN diagnostic messages received from the switch to the log window (Not yet available under Windows NT).
The following section explains some of the diagnostic messages and structures and refers to a table of ISDN info element and cause code messages in an appendix.
While your TCP/IP program may not translate these info elements, the ISDNTEST program provided by ISDN*tek does include the translations. If you do not wish to deal with Info elements and Cause codes, you may, under Windows 3.x and Win95, want to run LINE TEST diagnostics from the ISDN*tek test program.
All diagnostic message data is received as binary data. The message is converted into a readable translation, followed by hex data “info elements” as appropriate. As shown above, a typical diagnostic message has the following format:
Message xx xx xx xx xx
where “Message” is the English translation and “xx” represents a two-digit hex value.
The expected Network messages are the following:
The above network messages can be expected to appear in the log window when the diagnostic mode is enabled.
Network messages are usually, but not always, followed by “information elements” which always have the format:
INFO ELEMENT INFO ELEMENT INFO ELEMENT Type field Length field Data field
18 01 8A
18 = Channel ID info element
01 = Length (01=one data element)
8A = Channel B2 is assigned.
34 01 00
34 = Signal info element
01 = Length
00 = Tones ON the B-channel
Some messages are followed by a “cause” info element (with hex value 08) which contains information that may be useful for trouble shooting purposes. For example, most DISCONNECT network messages are followed by the “Cause” info element:
08 02 80 90
08 = Cause info element
02 = Length of data field
80 = ITU (CCITT) std msg from user
90 = Normal clearing
Normal clearing means that the other end simply hung up. Because there are many possible causes that may be communicated by the switch, National ISDN1 cause coding is presented in an appendix.
Cause & Progress Locations
private net serving local user
public net serving local user
public net serving remote user
private net serving remote user
net beyond interworking point
(ie: 82 = CCITT standard / public net serving local user,
ITU (CCITT) Cause Codes
Unallocated (unassigned) number
No route to specified transit network
No route to destination
Call awarded and being delivered in established chan
Normal call clearing
No user responding
User alerting, no answer
Nonselected user clearing
Destination out of order
Invalid number format (incomplete address)
Response to STATUS Enquiry
(Network out of order - non NI1)
Switching equipment congestion
Access information discarded
Requested circuit/channel not available
Resource unavailable, unspecified
|Service or Option not available
(Quality of service not available - non NI1)
Requested facility not subscribed
Bearer capability not authorized
Bearer capability not presently available
Service or option not available, unspecified
|Service or Option not implemented
Bearer capability not implemented
(Channel type not implemented - non NI1)
Requested facility not implemented
(Only restricted digital info bearer capability available - non NI1)
Service or option not implemented, unspecified
|Invalid Message (Parameter out of Range)
Invalid call reference value
(Indentified channel does not exist - non NI1)
(A suspended call exists, but this call ID does not)
(Call identity in use - non NI1)
(No call suspended - non NI1)
(Call having the requested call ID has been cleared)
(Invalid transit network selection - non NI1)
(Invalid message, unspecified - non NI1)
|Protocol Error (or unknown message)
Mandatory Info Element is missing
Message type nonexistent or not implemented
(Message not compatible with call state or message type
nonexistent or not implemented - non NI1)
Information element nonexistent or not implemented
Invalid information element contents
Message not compatible with call state
Recovery of timer expiry
Protocol error, unspecified
Prefix 0 dialed in error
Prefix 1 dialed in error
Prefix 1 not dialed
Excessive digits received, call is proceeding
Call is proceeding
Special Intercept Announcement
Special Intercept Announcement, undefined code
Special Intercept Announcement, number unassigned
Special Intercept Announcement, call blocked due to group restriction
Call Type incompatible with service request
Service operation violated
Protocol error threshold exceeded
Call is not end-to-end ISDN
Called equipment is not ISDN
Calling equipment is not ISDN
Inband information is available
(Delay in response at called interface - non NI1)
(ANSI standard T1.601-1988 compatible)
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following:
Standard shielded cables and I/O cords must be used for this equipment to comply with the relevant FCC regulations. Changes or modifications not expressly approved in writing by ISDN*tek may void the user’s authority to operate this equipment.
This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
ISDN*tek warrants to the original owner that the product delivered in this package will be free from defects in material and workmanship for one year following the date of purchase - but only if you register by returning or faxing the registration card as indicated. This warranty does not cover the product if it is damaged in the process of being installed. ISDN*tek recommends that you have a qualified service technician install this product.
The above warranty is in lieu of any other warranty, whether express, implied, or statutory; including, but not limited to, any warranty of merchantability, fitness for a particular purpose, or any warranty arising out of any proposal, specification, or sample. The User must determine if this product is suitable for any given application. ISDN*tek cannot warrant the suitability of this product for any specific application other than connection to the Internet through National ISDN 1 and for voice calls using a telephone handset. The CyberSpace Commuter Card is a digital product and will only provide voice capabilities through an approved handset or headset, not through an analog (POTS) telephone. It is not an analog modem and it can not communicate with an analog modem.
This warranty does not cover replacement of products damaged by abuse, accident, misuse, neglect, alteration, repair, disaster, improper installation, or improper testing. If the product is found to be otherwise defective, ISDN*tek, at its option, will replace or repair the product at no charge except as set forth below, provided that you deliver the product along with a return material authorization (RMA) number (see below) either to the company from whom you purchased it or to ISDN*tek. If you ship the product, you must assume the risk of damage or loss in transit. You must use the original container (or the equivalent) and pay the shipping charge. ISDN*tek may replace or repair the product with either a new or reconditioned product, and the returned product becomes ISDN*tek’s property. ISDN*tek warrants the repaired or replaced product to be free from defects in material and workmanship for a period of the greater of 90 days from the return shipping date or the period of time remaining on the original one year warranty.
This warranty gives you specific legal rights and you may have other rights which vary from state to state. All parts or components contained in this product are covered by ISDN*tek’s limited warranty for this product; the product may contain fully tested, recycled parts, warranted as if new.
Before returning any product, contact the ISDN*tek Customer Service Group at the main telephone number, to obtain an RMA number. If the Customer Service Group verifies that the product is defective, they will have a Return Material Authorization number issued to you. This number should be placed on the outer packaging when returning the product. ISDN*tek cannot accept any returned product without an RMA number on the package.
ISDN*tek shall have no liability for any indirect or speculative damages (including, without limiting the foregoing, consequential, incidental, and special damages) arising from the use of or inability to use this product, whether arising out of contract, negligence, tort, or under any warranty, irrespective of whether ISDN*tek has advance notice of the possibility of any such damages, including, but not limited to loss of use, business interruptions, and loss of profits. Notwithstanding the foregoing, ISDN*tek’s total liability for all claims under this agreement shall not exceed the price paid for the product. These limitations on potential liabilities were an essential element in setting the product price. ISDN*tek neither assumes, nor authorizes anyone to assume for it, any other liabilities.
Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above limitations or exclusions may not apply to you.
Please read before copying the CyberSpace Card Installation Manual.
The CyberSpace Card Installation Manual dated 03/01/98 contains information related to products and services of ISDN*tek. Contents are provided as a courtesy to ISDN*tek's customers and potential customers. By accessing, copying, or using any information contained in this HTML/online manual, you agree to be bound by the terms and conditions described in this Legal Notice.
The documentation contained in this HTML/online manual is owned and copyrighted by ISDN*tek. Copyright © 1998 ISDN*tek, PO Box 3000, San Gregorio, CA 94074, USA, all rights reserved.
You are licensed to copy documentation from the HTML/online manual provided you agree to the following terms and conditions.
Failure to comply with these terms and conditions will terminate the license.
ISDN*tek, CyberSpace Freedom, CyberSpace Card, CyberSpace Machines, "the Interface to CyberSpace", PC*TE, CyberSpace Internet, CyberSpace Commuter, CyberSpace Enterprise, and other names of ISDN*tek products, product features, and services are trademarks and/or service marks of ISDN*tek in the United States and other countries. Other product and company names mentioned in this HTML/online manual may be the trademarks of their respective owners.
Nothing contained in this legal notice shall be construed as conferring by implication, estoppel, or any other legal theory, a license or right to any patent, trademark, copyright, or other intellectual property right, except those expressly provided herein. The products, processes, and other technology described in this HTML/online manual may be the subject of other intellectual property rights owned by ISDN*tek or by third parties, and no licenses are granted herein.
No warranties: the documentation provided is "as is" without any express or implied warranty of any kind including warranties of merchantability, noninfringement of intellectual property, or fitness for any particular purpose. In no event shall ISDN*tek or ots suppliers be liable for any damages whatsoever (including, without limitation, damages for loss of profits, business interruption, or loss of information) arising out of the use of or inability to use the documentation provided in this HTML/online manual, even if ISDN*tek has been advised of the possibility of such damages. Because some jurisdictions prohibit the exclusion or limitation of liability for consequential or incidental damages, some of the above limitations may not aply to you.
ISDN*tek further does not warrant the accuracy or completeness of the information, text, graphics, or other items contained within this HTML/online manual. ISDN*tek may make changes to these materials, or to the products described therein, at any time without notice. ISDN*tek makes no commitment to update this documentation.
Copyright © 1998 ISDN*tek, PO Box 3000,
San Gregorio, CA 94074, USA, all rights reserved.
By using any information in this HTML manual, you agree to be bound by the terms of ISDN*tek's Legal Notice.