Symbol
Type of notice
Description
Information
Important functions and notes
Warning
Information about hazards to important components
Congratulations on your purchase of a USRobotics ISDN PCI Card TA. The advanced technology implemented in your new ISDN PCI Card TA opens up new horizons in data communications. Additional information about USRobotics is available at:
The ISDN PCI Card TA gives you access to the ISDN network via your PC. It uses an S0 –interface that connects to your ISDN basic access through the enclosed cable.
The USRobotics ISDN PCI Card TA offers the following functions:
This documentation describes the installation and operation of the USRobotics ISDN PCI Card Terminal Adapter (TA) and contains other information about ISDN and about using your ISDN PCI Card TA in conjunction with application programs.
In the event information from the readme.txt file (located on the Installation CD-ROM) differs from information found within this manual, follow the instructions in the readme.txt file.
The following tables explain symbols and typographic conventions used in this documentation.
|
Symbol |
Type of notice |
Description |
|
|
Information |
Important functions and notes |
|
|
Warning |
Information about hazards to important components |
|
Style |
Description |
|
Boldface type |
Used for emphasis |
|
|
The CAPI Tray program is not available in Windows NT 4.0. |
The CAPI tray program displays the connection status of the two ISDN B channels on the Windows task bar. Each of the two B channels is represented by a colored dot that looks like an LED.
|
|
Red – No activity, no connection Green – Connection exists |
To terminate the CAPI tray program, right-click one of the two LEDs and then click Exit.
To start the CAPI tray program automatically each time Windows is started, copy the CAPI tray program symbol to the Windows Startup folder.
|
|
The Loopback Test Program is not available in Windows NT 4.0. |
The Loopback Test Program is a simple program for checking your ISDN PCI Card TA and your ISDN access.
The program will establish a connection with itself, sending and receiving data. The data received will be compared to the data sent.
This program is found in the ISDN Tools program group. Click the Loopback Test icon to start the program.
More:
Testing Criteria and Testing Procedure
Test Execution and Test Result
The following conditions must be met for the loopback test to be run:
The Loopback Test program tests the following components:
The Loopback Test follows this pattern:
|
1. |
The ISDN PCI Card TA is addressed (initialized). |
|
2. |
An ISDN data connection is established to the subscriber number (MSN) given. If the MSN is correct, a connection is established in order to be able to transmit data. |
|
3. |
Test data is sent on one B channel of the S0 bus and received on the second B channel. |
|
4. |
The test data is checked for transmission errors. |
|
5. |
The test result is displayed. |
|
1. |
Start the Loopback Test program if you have not already done so. |
|
2. |
Enter the subscriber number (MSN) to be used for testing. If this number was provided during configuration, it is automatically obtained from the Windows registry. If no number was provided during configuration, enter the MSN for your ISDN PCI Card TA. |
|
3. |
Click Start Test. |
|
4. |
Watch the messages in the status window showing the current status of the test connection and the test result. Status messages are displayed in text form and as CAPI or ISDN error numbers. |
If the Loopback Test succeeds, you can assume that your ISDN PCI Card TA hardware and software are operating properly.
If the Loopback Test fails, this could be due to one of the following errors:
For additional information, refer to the loopback testing program error messages and the CAPI or ISDN error numbers.
The ControlCenter software from USRobotics provides an attractive graphic interface that makes it easy for you to set up your USRobotics communications device.
As ControlCenter opens, it detects all the supported USRobotics communications devices installed on your system. Icons for each device found appear on the left. Click the icon for the device you want to configure, and its Device Information screen appears. Then click Configuration Manager to prepare your device.
When you launch ControlCenter, it scans your system for supported USRobotics communications devices. In a few moments, ControlCenter will display icons for all the devices it finds. Click the icon for your device.
When you click a device, ControlCenter displays the Device Information screen.
This screen identifies your device and gives technical specifications and the serial number. Help topics for the device you chose are now available.
If you don't see an icon for your communications device in the left panel, make sure that your device is connected properly and is turned on. Click Start, Settings, Control Panel, and then Modems and see if your operating system has assigned a driver for your device. The operating system must recognize your device before your ControlCenter software can find it. You may need to restart your computer.
When you have confirmed that your communications device is turned on and is properly connected, and that your operating system has assigned a good driver for your device, click Detect and ControlCenter will search for it again.
To reopen ControlCenter on a PC running Windows 2000, Windows 98, Windows 95, or Windows NT4:
Click the icon for a communications device (or click the Back button after configuring one) and the Device Information screen appears. Help topics for the device you chose will now be available.
This tab identifies your device and gives technical specifications and the serial number.
Click Configuration Manager to prepare your device for use or to edit your default communications settings. There are three tabs within the Configuration Manager option: ISDN Line, Loopback Test, and MSN. The values for the options within these tabs should be automatically entered. If they are not, you must enter the values in order to use your ISDN Terminal Adapter. Refer to the screenshots below to see the options that are available and examples of the values that should be entered.
ISDN Line
You can download the latest USRobotics software for this device automatically by clicking Instant Update.
The Instant Update utility checks whether the USRobotics software installed in this device is the latest version available. If not, it will download the latest software for you automatically. You can then click Flash From Disk to install the latest USRobotics software for this device manually from the flash file you've downloaded and saved onto a disk or local drive.
One of the features of the USRobotics ISDN PCI Card TA is the ability to establish a second concurrent Internet connection. This will allow you to achieve download speeds of up to 128K. Perform the following steps, depending on your Operating System, to activate the Multi-Link Point to Point Protocol (MLPPP) feature.
Click Windows Start, Programs, and then Accessories. Click Communications and then Dial-Up Networking. If a connection does not already exist, create one now. If you created a new connection, select USR ISDN Line 0 and click Next. Enter the ISDN access phone number supplied by your ISDN provider, click Next, and then click Finish. After you have created the new connection or if a connection already existed, right-click the appropriate connection and click Properties. Click the Multilink tab, select Use additional devices, and click Add. Select USR ISDN Line 1 from the drop-down menu and click OK. If your ISDN provider does not require a different number for the second connection line, click OK to finish the configuration. If your ISDN provider requires a different phone number for your second connection line, select USR ISDN Line 1 and click Edit. Enter the new phone number and click OK. Click OK to finish the configuration.
Click Windows Start, Settings, and then Dial-Up Networking. If a connection does not already exist, create one now. If you created a new connection, select USR ISDN Line 0 and click Next. Enter the ISDN access phone number supplied by your ISDN provider, click Next, and then click Finish. After you have created the new connection or if a connection already existed, right-click the appropriate connection and click Properties. Click the Multilink tab, select Use additional devices, and click Add. Select USR ISDN Line 1 from the drop-down menu and click OK. If your ISDN provider does not require a different number for the second connection line, click OK to finish the configuration. If your ISDN provider requires a different phone number for your second connection line, select USR ISDN Line 1 and click Edit. Enter the new phone number and click OK. Click OK to finish the configuration.
Click Windows Start, Settings, and then Network and Dial-Up Connections. Right-click your ISDN Dial-Up Connection and then click Properties. Under the General tab, check the box next to each of the ISDN devices. If your ISDN provider only requires one phone number for both of the ISDN connection lines, select the check box for All devices call the same numbers. Enter the phone number in the phone number box and click OK. If your ISDN provider requires you to use two different numbers for the two ISDN connection lines, make sure the check box for All devices call the same numbers is not selected. Select the first ISDN modem in the list and enter the phone number. Select the second ISDN modem in the list and enter the phone number. When you are finished, click OK to complete the configuration.
Click Windows Start, Programs, Accessories, and then Dial-Up
Networking. Create a new phonebook entry and then click Next. Select
I am calling the Internet or all that apply and then click Next.
Select All available ISDN lines mult-linked and click Next. Enter
the phone number to connect to your ISDN provider, click Next, and then
click Finish. If your ISDN service provider requires two different numbers
for the two ISDN connection lines, open Dial-Up Networking. Click More
and then select Edit Entry and modem properties. Under the Basic
tab, click Configure. Make sure that the check boxes next to both of
the ISDN devices are selected. Select the modem identified as the second device
and click Phone numbers. Enter the second phone number, click Replace,
and then click OK. Click OK on the remaining screens to finish
the configuration.
The PC cannot be turned on.
Check to see if all boards were inserted correctly.
Dial-up connection is not possible.
Check to see if the device is connected to the S0 bus. If a connection still cannot be established, check the PABX hookup.
No calls can be accepted.
Check the settings of your software to see whether it is set to automatic or manual answer. Also, ensure that the correct MSN has been assigned to the device.
Internet connection cannot be established.
Check to see if the TCP/IP is activated. Double-click the Network icon in Control Panel and check the Dial-Up Networking Windows online help topic to see which other protocols must be activated.
Device is not recognized.
Start the PC with only indispensable boards installed, plus the ISDN PCI Card TA. If the device still is not recognized, exchange or check for system compatibility with the ISDN PCI Card TA.
If you wish to use the ISDN PCI Card TA with the Windows Dial-Up Networking, you will first have to configure a connection. Once a connection is configured, double-click the Connection icon to establish the connection. The current connection status will be displayed in the status window. Error messages indicating possible causes of the error will be displayed in case a connection cannot be established.
Connection is broken before "Verifying user name and password" is shown.
If the connection is broken before the message "verifying user name and password" appears, no ISDN connection could be established with the server. Use the Loopback Test to check whether the ISDN PCI Card TA and ISDN access work properly. Also, check that you are using the correct access number for your server. If using a PABX, it may be necessary to dial 0 or 9 before the number. Try calling a different server (test server) known to be fully functional.
Connection broken after "Verifying user name and password" is shown.
If the connection is broken before the message "verifying user name and password" appears, an ISDN connection was established with the server. If problems occur after this point, they may be related to the network configuration or the server configuration. Contact the server's PC or LAN administrator.
In Windows Me, I was disconnected from the Internet during a large download.
If you are using Dial-Up Networking in Windows Me, you may be disconnected during a large download. This may occur if the "Enable idle disconnect" option is activated within Dial-Up Networking. Make sure you do not have an active Internet connection, open Dial-Up Networking, and right-click the connection you are using. Click Properties and select the Dialing tab. Make sure the box for "Enable idle disconnect" is not checked.
The CAPI tray is not indicating the correct status for the b-channel in Windows 2000.
Restart either Windows 2000 or the CAPI tray.
If you experience problems with CAPI applications, you should first perform the Loopback Test. If the test passed, all CAPI applications should operate properly. There are, however, the following exceptions:
|
The CAPI application uses a B-channel protocol not supported by the ISDN PCI Card TA. A list of supported protocols is found in the Appendix. |
|
|
The CAPI application uses the CAPI.VxD or CAPI.SYS kernel mode drivers instead of the CAPI2032.DLL user mode driver. The kernel mode drivers are not tested by the loopback test. Contact your application manufacturer’s customer support. |
|
Country
|
Voice
|
Online
|
Support Hours
|
| Austria | 07 110 900 116 | emea_modemsupport@usr.com | 8:00 A.M. – 6:00 P.M., Monday - Friday |
| Belgium (Flemish) | +32 (0) 70 233 545 | emea_modemsupport@usr.com | 9:00 A.M. – 6:00 P.M., Monday - Friday |
| Belgium (French) | +32 (0) 70 233 546 | emea_modemsupport@usr.com | 9:00 A.M. – 6:00 P.M., Monday - Friday |
| Denmark | +45 7010 4030 | emea_modemsupport@usr.com | 9:00 A.M. – 5:00 P.M., Monday - Friday |
| Finland | +358 98 171 0015 | emea_modemsupport@usr.com | 10:00 A.M. – 6:00 P.M., Monday - Friday |
| France | 080 307 0693 | france_modemsupport@usr.com | 9:00 A.M. – 6:00 P.M., Monday - Friday |
| Germany/Hungary | 0180 567 1548 | germany_modemsupport@usr.com | 8:00 A.M. – 6:00 P.M., Monday - Friday |
| Ireland | +44 870 844 4546 | emea_modemsupport@usr.com | 9:00 A.M. – 6:00 P.M., Monday - Friday |
| Israel | emea_modemsupport@usr.com | 9:00 A.M. – 5:30 P.M., Monday - Friday | |
| Italy | 848 80 9903 | italy_modemsupport@usr.com | 9:00 A.M. – 6:00 P.M., Monday - Friday |
| Luxembourg | +352 342 080 8318 | emea_modemsupport@usr.com | 9:00 A.M. – 6:00 P.M., Monday - Friday |
| Middle East/Africa | +44 870 844 4546 | emea_modemsupport@usr.com | 9:00 A.M. – 6:00 P.M., Monday - Friday |
| Netherlands | 0900 20 25 857 | emea_modemsupport@usr.com | 9:00 A.M. – 6:00 P.M., Monday - Friday |
| Norway | +47 (0) 23 50 0097 | emea_modemsupport@usr.com | 9:00 A.M. – 5:00 P.M., Monday - Friday |
| Poland | emea_modemsupport@usr.com | 8:00 A.M. – 6:00 P.M., Monday - Friday | |
| Portugal | +35 11 415 4034 | emea_modemsupport@usr.com | 9:00 A.M. – 5:00 P.M., Monday - Friday |
| Spain | 902 117 964 | spain_modemsupport@usr.com | 9:00 A.M. – 5:00 P.M., Monday - Friday |
| Sweden | +46 (0) 851 992 035 | emea_modemsupport@usr.com | 8:00 A.M. – 5:00 P.M., Monday - Friday |
| Switzerland | +0848 840 200 | emea_modemsupport@usr.com | 8:00 A.M. – 6:00 P.M., Monday - Friday |
| UK | 0870 8444 546 | uk_modemsupport@usr.com | 9:00 A.M. – 5:30 P.M., Monday - Friday |
We declare under our sole responsibility that the Product: USRobotics ISDN PCI Card TA
Model Number: 3409 (ST Interface)
To which this declaration relates, is in conformity with the following standards or other normative documents:
EN55022: Class B
EN55024
EN60950 1992: A1-A4
TS001 & AS/NZS3260
ETS 300 047 (08.92)
CTR 3 (05/97) A1 (06/98)
TS031 (1997)
CE Compliance
This device complies with the requirements of European Directive 1995/5/EC.
HARDWARE: USRobotics warrants to the end user (“Customer”) that this hardware product will be free from defects in workmanship and materials, under normal use and service, for the following length of time from the date of purchase from USRobotics or its authorised reseller:
Two (2) years
USRobotics’s sole obligation under this express warranty shall be, at U.S. Robotics’s option and expense, to repair the defective product or part, deliver to Customer an equivalent product or part to replace the defective item, or if neither of the two foregoing options is reasonably available, USRobotics may, in its sole discretion, refund to Customer the purchase price paid for the defective product. All products which are replaced will become the property of USRobotics. Replacement products may be new or reconditioned. USRobotics warrants any replaced or repaired product or part for ninety (90) days from dispatch, or the remainder of the initial warranty period, whichever is longer.
SOFTWARE: USRobotics warrants to Customer that each software program
licensed from it will perform in substantial conformance to its program specifications,
for a period of ninety (90) days from the date of purchase from USRobotics
or its authorised reseller. USRobotics warrants the media containing software
against failure during the warranty period. No updates are provided. USRobotics’s sole obligation under this express warranty shall be, at USRobotics’s option
and expense, to refund the purchase price paid by Customer for any defective
software product, or to replace any defective media with software which substantially
conforms to applicable USRobotics published specifications. Customer assumes
responsibility for the selection of the appropriate applications program and
associated reference materials. USRobotics makes no warranty or representation
that its software products will meet Customer’s requirements or work in combination
with any hardware or applications software products provided by third parties,
that the operation of the software products will be uninterrupted or error free,
or that all defects in the software products will be corrected. For any third-party
products listed in the USRobotics software product documentation or specifications
as being compatible, USRobotics will make reasonable efforts to provide compatibility,
except where the non-compatibility is caused by a “bug” or defect in the third
party’s product or from use of the software product not in accordance with USRobotics’s published specifications or User Guide.
THIS USRobotics PRODUCT MAY INCLUDE OR BE BUNDLED WITH THIRD-PARTY SOFTWARE,
THE USE OF WHICH IS GOVERNED BY A SEPARATE END-USER LICENCE AGREEMENT. THIS
USRobotics WARRANTY DOES NOT APPLY TO SUCH THIRD-PARTY SOFTWARE. FOR THE
APPLICABLE WARRANTY, PLEASE REFER TO THE END-USER LICENCE AGREEMENT GOVERNING
THE USE OF SUCH SOFTWARE.
OBTAINING WARRANTY SERVICE: Customer must contact a USRobotics Corporate
Service Centre or an Authorised USRobotics Service Centre within the applicable
warranty period to obtain warranty service authorisation. Dated proof of purchase
from USRobotics or its authorised reseller may be required. Products returned
to USRobotics’s Corporate Service Centre must be pre-authorised by USRobotics
with a Service Repair Order (SRO) number marked on the outside of the package,
and sent prepaid and packaged appropriately for safe delivery, and it is recommended
that they be insured or sent by a method that provides for tracking of the package.
The repaired or replaced item will be dispatched to Customer, at U.S. Robotic’s
expense, not later than thirty (30) days after USRobotics receives the defective
product. Return the product to:
In Europe:
FRS Europe BV.
Draaibrugweg 2
1332 AC Almere
The Netherlands
USRobotics shall not be responsible for any software, firmware, information or memory data of Customer contained in, stored on, or integrated with any products returned to USRobotics for repair, whether under warranty or not.
WARRANTIES EXCLUSIVE: IF A USRobotics PRODUCT DOES NOT OPERATE AS WARRANTED ABOVE, CUSTOMER’S SOLE REMEDY FOR BREACH OF THAT WARRANTY SHALL BE REPAIR, REPLACEMENT, OR REFUND OF THE PURCHASE PRICE PAID, AT USRobotics’s OPTION. TO THE FULL EXTENT ALLOWED BY LAW, THE FOREGOING WARRANTIES AND REMEDIES ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER WARRANTIES, TERMS, OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING WARRANTIES, TERMS, OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY, CORRESPONDENCE WITH DESCRIPTION, AND NON-INFRINGEMENT, ALL OF WHICH ARE EXPRESSLY DISCLAIMED. USRobotics NEITHER ASSUMES NOR AUTHORISES ANY OTHER PERSON TO ASSUME FOR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE OR USE OF ITS PRODUCTS.
USRobotics SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS TESTING AND EXAMINATION DISCLOSE THAT THE ALLEGED DEFECT OR MALFUNCTION IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY CUSTOMER’S OR ANY THIRD PERSON’S MISUSE, NEGLECT, IMPROPER INSTALLATION OR TESTING, UNAUTHORISED ATTEMPTS TO OPEN, REPAIR OR MODIFY THE PRODUCT, OR ANY OTHER CAUSE BEYOND THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE, LIGHTNING, OTHER HAZARDS OR ACTS OF GOD.
LIMITATION OF LIABILITY: TO THE FULL EXTENT ALLOWED BY LAW, USRobotics
ALSO EXCLUDES FOR ITSELF AND ITS SUPPLIERS ANY LIABILITY, WHETHER BASED IN CONTRACT
OR TORT (INCLUDING NEGLIGENCE), FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL
OR PUNITIVE DAMAGES OF ANY KIND, OR FOR LOSS OF REVENUE OR PROFITS, LOSS OF
BUSINESS, LOSS OF INFORMATION OR DATA, OR OTHER FINANCIAL LOSS ARISING OUT OF
OR IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE, USE, PERFORMANCE,
FAILURE OR INTERRUPTION OF ITS PRODUCTS, EVEN IF USRobotics OR ITS AUTHORISED
RESELLER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND LIMITS ITS
LIABILITY TO REPAIR, REPLACEMENT OR REFUND OF THE PURCHASE PRICE PAID, AT U.S.
Robotics’s OPTION. THIS DISCLAIMER OF LIABILITY FOR DAMAGES WILL NOT BE
AFFECTED IF ANY REMEDY PROVIDED HEREIN SHALL FAIL OF ITS ESSENTIAL PURPOSE.
DISCLAIMER: Some countries, states, or provinces do not allow the exclusion
or limitation of implied warranties or the limitation of incidental or consequential
damages for certain products supplied to consumers, or the limitation of liability
for personal injury, so the above limitations and exclusions may be limited
in their application to you. When the implied warranties are not allowed to
be excluded in their entirety, they will be limited to the duration of the applicable
written warranty. This warranty gives you specific legal rights which may vary
depending on local law.
GOVERNING LAW: This Limited Warranty shall be governed by the laws of the State of Illinois, USA, excluding its conflicts of laws principles and excluding the United Nations Convention on Contracts for the International Sale of Goods.
USRobotics Corporation
935 National Parkway
Schaumburg, IL 60173
USA
|
Hardware |
|
|
Dimensions |
Short PCI card |
|
Supply voltage |
5V via PCI bus |
|
Power consumption |
Approx. 50 mA |
|
ISDN-Interface |
RJ-45 |
|
Basic software |
Winphone |
|
D channel protocols |
|
|
Network |
NDIS WAN Miniport drivers |
|
Operating system |
Windows 95 / 98 / Me / NT 4.0 / 2000 |
|
B channel protocol |
Transparent HDLC |
|
CAPI |
CAPI 2.0 |
|
B channel protocol |
|
|
Number (hex) |
Description |
|
0x1001 |
Error in API_REGISTER |
|
0x1002 |
Invalid application ID |
|
0x1003 |
Invalid message |
|
0x1004 |
Invalid command or subcommand |
|
0x1005 |
Queue full |
|
0x1006 |
Queue empty |
|
0x1007 |
Queue overflow |
|
0x1008 |
Deinstallation error |
|
0x2001 |
Invalid controller |
|
0x2002 |
Invalid PLCI |
|
0x2003 |
Invalid NCCI |
|
0x2004 |
Invalid type |
|
0x3101 |
Error in B channel |
|
0x3102 |
Error in info mask |
|
0x3103 |
Error in MSN service mask |
|
0x3104 |
Error in SI service mask |
|
0x3105 |
Invalid protocol layer 2 |
|
0x3106 |
Invalid DLPD |
|
0x3107 |
Invalid protocol layer 2 |
|
0x3108 |
Invalid NCPD |
|
0x3109 |
Invalid NCPIs |
|
0x3201 |
General controller error |
|
0x3202 |
LISTEN_REQs not unique |
|
0x3203 |
Unsupported function |
|
0x3204 |
PLCI not active |
|
0x3205 |
NCCI not active |
|
0x3206 |
Protocol l2 not supported |
|
0x3207 |
Cannot select protocol I2 now |
|
0x3208 |
Protocol l3 not supported |
|
0x3209 |
Cannot select protocol I3 now |
|
0x320a |
Invalid DLPD parameter |
|
0x320b |
Invalid NCPD parameter |
|
0x320c |
Invalid NCPI parameter |
|
0x320d |
Data length not supported |
|
0x3301 |
Setup error D channel, layer 1 |
|
0x3302 |
Setup error D channel, layer 2 |
|
0x3303 |
Setup error B channel, layer 1 |
|
0x3304 |
Setup error B channel, layer 2 |
|
0x3305 |
Turned off D channel, layer 1 |
|
0x3306 |
Turned off D channel, layer 2 |
|
0x3307 |
Turned off D channel, layer 3 |
|
0x3308 |
Turned off B channel, layer 1 |
|
0x3309 |
Turned off B channel, layer 2 |
|
0x330a |
Turned off B channel, layer 3 |
|
0x330b |
Restored B channel, layer 2 |
|
0x330c |
Restored B channel, layer 3 |
|
0x34xx |
Connection ended/terminated xx = Cause according to ETS 300 102-1 / Q.931. |
| Normal: | |
| 80 | Normal Disconnect |
| 81 | Unassigned (Unallocated number) |
| 82 | No route to specified transit network |
| 83 | No route to destination |
| 86 | Channel unacceptable |
| 87 | Call awarded and being delivered in an established channel |
| 90 | Normal call clearing |
| 91 | User busy |
| 92 | No user responding |
| 93 | User alerting, no answer |
| 95 | Call rejected |
| 96 | Number changed |
| 9A | Non-selected user clearing |
| 9B | Destination out of order |
| 9C | Invalid number format |
| 9D | Facility rejected |
| 9E | Response to Status Enquiry |
| 9F | Normal unspecified |
| Resource unavailable: | |
| A2 | No circuit/channel available |
| A6 | Network out of order |
| A9 | Temporary failure |
| AA | Switching equipment congestion |
| AB | Access information discarded |
| AC | Requested circuit/channel not available |
| AF | Resource unavailable, unspecified |
| Service or option not available: | |
| B1 | Quality of service unavailable |
| B2 | Requested facility not subscribed |
| B9 | Bearer capability not authorized |
| BA | Bearer capability not presently available |
| BF | Service or option not available, unspecified |
| Service or option not implemented: | |
| C1 |
Bearer capability not implemented |
| C2 | Channel type not implemented |
| C5 | Requested facility not implemented |
| C6 | Only restricted information bearer capability available |
| CF | Service or option not available, unspecified |
| Invalid message: | |
| D1 | Invalid call reference value |
| D2 | Identified channel does not exist |
| D3 | A suspended call exists, but this identity does not |
| D4 | Call identity in use |
| D5 | No call suspended |
| D6 | Call having the requested call identity has been cleared |
| D8 | Incompatible destination |
| DB | Invalid transit network selection |
| DF | Invalid message, unspecified |
| Protocol error: | |
| E0 | Mandatory Information Element is missing |
| E1 | Message type non-existent or not implemented |
| E2 | Message not compatible with call state, or not implemented |
| E3 | Information Element non-existent or not implemented |
| E4 | Invalid Information Element contents |
| E5 | Message not compatible with call state |
| E6 | Recovery on time expiry |
| EF | Protocol Error, unspecified |
| Interworking: | |
| FF | Interworking, unspecified |
An S0 bus must be "terminated," which means that the bus must have terminating resistors of 100 ohms at the farthest point on the bus. This allows the signals carried along the bus to flow and return in the proper fashion. The S0 bus will function unreliably or not at all if the bus is not properly terminated.
The function of the JP1 jumpers is to connect or disconnect the terminating resistors whenever necessary.
Factory settings:
The JP1 jumpers on pins 1 and 2 will turn on the terminating resistors if the USRobotics ISDN PCI Card is the only terminal adapter on the S0 bus or is connected on the last RJ-45 socket of your ISDN S0 bus.
The JP1 jumpers on pins 2 and 3 will turn off the terminating resistors if the USRobotics ISDN PCI Card is connected to any other RJ-45 socket of your ISDN S0 bus.
ISDN S0 interface pin assignment (RJ-45 plug/jack)
(CCITT I.430/ISO 8877)
|
|
|
|
RJ-45 plug |
RJ-45 jack |
|
Pin |
Signal |
|
1 |
Not used |
|
2 |
Not used |
|
3 |
STA (Sending A) |
|
4 |
SRA (Receiving A) |
|
5 |
SRB (Receiving B) |
|
6 |
STB (Sending B) |
|
7 |
Not used |
|
8 |
Not used |
