----------------------------------------------- README for X.TOLL 21st March 1996 ----------------------------------------------- (c) Copyright RACAL DATA GROUP, 1996 ------------------------- HOW TO VIEW THIS DOCUMENT ------------------------- To view Readme.txt on screen in Windows Notepad, maximise the Notepad window. To print Readme.txt, open it in Windows Notepad or another word processor, then use the Print command on the File menu. Select the smallest possible margin widths to prevent unnecessary line breaks. -------- CONTENTS -------- 1. MODES OF OPERATION 2. WINDOWS 95 SPECIFIC ISSUES 3. WINDOWS NT SPECIFIC ISSUES 4. WINDOWS FOR WORKGROUPS SPECIFIC ISSUES 5. THIRD PARTY HARDWARE ISSUES 6. ISDN CAUSE CODES -------- 1. MODES OF OPERATION ================== There are two modes of operation described in the X.TOLL User Manual: TA (Terminal Adapter) Emulation Mode NDIS WAN Mode In this release these modes are supported as follows: Operating System | Mode Supported ----------------------------------------------- Windows 95 | TA Emulation Mode only Windows for Workgroups | TA Emulation Mode only Windows NT | NDIS WAN Mode only 2. WINDOWS 95 SPECIFIC ISSUES ========================== Refer to the README.TXT file on the X.TOLL for Windows 95 installation disk for Windows 95 specific issues. 3. WINDOWS NT SPECIFIC ISSUES ========================== Refer to the README.TXT file on the X.TOLL for Windows NT installation disk for Windows 95 specific issues. 4. WINDOWS FOR WORKGROUPS SPECIFIC ISSUES ====================================== 4.1 HARDWARE CONFIGURATION ---------------------- The hardware parameters for the X.TOLL ISA card are requested at install time. These can be changed through the X.TOLL configuration utility if required. The configuration information for the X.TOLL PCMCIA card is detected automatically at Windows startup and does not need to be configured in this file. For both ISA and PCMCIA cards, it is up to the user to ensure that there is no clash with any other installed hardware. 4.2 X.TOLL CONFIGURATION CHANGES ---------------------------- The X.TOLL device driver is loaded at Windows startup. Changes made to the X.TOLL configuration will not take effect until Windows is restarted. 4.3 PCMCIA CARD SUPPORT UNDER WINDOWS FOR WORKGROUPS ------------------------------------------------ 4.3.1 Configuration ------------- The X.TOLL PCMCIA card must be enabled by the Generic Enabler within the Socket and Card Services supplied with your PC. The mechanism for this will be explained in your PC documentation. The configuration requirements for the X.TOLL card are very simple, requiring a single 16 byte I/O address range and a single IRQ. No restrictions are placed on the actual address or IRQ chosen. See the ‘Third Party Hardware’ section for specific information on enabling the X.TOLL card with SystemSoft's CardSoft Enabler. Socket and Card Services software include a resource manager responsible for allocating resources (IRQs, I/O and memory address ranges) to PCMCIA cards. In order to do this correctly, sufficient resources must be made available to the resource manager. This is usually in a configuration file; see your system documentation for further information. It is very important that resources made available to the resource manager are not in use by other parts of the system. The X.TOLL PCMCIA card must be installed in the socket at Windows startup and must not be removed while Windows is running. Failure to observe this could cause the system to become unstable. At Windows startup, the X.TOLL driver will detect the X.TOLL card and read the configuration from Card Services. Consequently there is no need to configure the I/O address or IRQ in the X.TOLL configuration utility. 4.3.2 PCMCIA Card Display Utility --------------------------- The program CARDUTIL.EXE is provided with the Windows for Workgroups installation to interrogate the PCMCIA Card Services for the status of installed X.TOLL PCMCIA Cards. This program must be run from DOS or a DOS session in Windows. It displays the status of any X.TOLL cards currently installed in a PCMCIA socket. The program relies on the Card Services correctly identifying the X.TOLL PCMCIA card. The status of a PCMCIA card will be one of the following: No card Not a RACAL X.TOLL Card Not an X.TOLL Card Unconfigured X.TOLL Card X.TOLL card I/O [xxx] IRQ [yy] Only the last of these possible messages indicates an X.TOLL PCMCIA card which has been correctly identified and enabled by the Card Services Enabler. For each of the other messages, check that the X.TOLL PCMCIA card is correctly inserted and refer to your PC documentation for further troubleshooting techniques. 4.4 ASYNCHRONOUS PPP SUPPORT ----------------------- PC protocol stacks that support asynchronous PPP (e.g. Dial-Up Networking, Trumpet, Chameleon) can be run over X.TOLL by virtue of the async-to-sync PPP protocol conversion that is included as part of the X.TOLL terminal adapter. For this protocol conversion to operate successfully it is important that the protocol stack is configured to not send any async control characters (e.g. XON, XOFF). Consequently, please consider the following when configuring your local PC protocol stack: 1. If flow-control is configurable, turn OFF Software flow-control; 2. If the async PPP transmit ACCM value is configurable, ensure it is set to zero. 4.4.1 Trumpet Winsock and Checksum Errors ----------------------------------- If file transfers fail to complete when using Trumpet Winsock on Windows 95 or Windows for Workgroups, it may be due to PPP Frame Checksum Errors. These are displayed in the Trumpet Winsock window if PPP tracing is enabled in the Trumpet Winsock Tracing menu. This problem may be resolved by reducing the TCP Maximum Segment Size in the Trumpet setup from the default value of 1460 to a value of 1450. 4.5 HAYES AT COMMAND SET -------------------- In the TA Emulation Mode, the Hayes AT command set is used to control call setup and interface operation. 4.5.1 Unsupported AT Command Set Feature ---------------------------------- X.TOLL does not respond to the escape sequence +++ or to the /a repeat command syntax. To disconnect the line it is necessary to drop the DTR signal or close the COM port. From most communications packages including Windows for Workgroups Terminal this is possible by selecting the disconnect option. Where this is not possible, closing the application will drop the ISDN line. Also note that X.TOLL does not report a speed identifier after a connection has been made. 4.5.2 Aborting a Call in Progress --------------------------- While an outgoing call is still in the process of connecting (ie before receiving the CONNECT message), it may be aborted by pressing any key. 4.5.3 Problems with outgoing calls via the Hayes Command Interface ------------------------------------------------------------ If you encounter problems making outgoing calls through the Hayes command interface, it may be because of the terminal program settings. In particular, if the cause code 144 (Normal call clearing - local) is displayed it may mean that extra characters are being sent to the Hayes interface after the call setup string causing the call to be aborted (see section 4.5.2). One way extra characters can be generated is if Carriage Return is being mapped to Carriage Return plus Line Feed by the application. Switching off this translation in the terminal package preferences would rectify this problem. 4.5.4 ATS0 Command Change ------------------- The description of the ATS0 command in Appendix A of the User Instruction manual is incorrect. The correct description is shown below: AT DESCRIPTION RESULT CODES Verbose Terse ATS0= Auto answer selection OK 0 Ringing indication is not affected 0 = Disable auto answer by this register. All values 1 = Enable auto answer other than 0 are treated as 1. Default = 0 (may also be changed in the X.TOLL Configuration Utility). 4.5.5 Extra AT Commands ----------------- Some extra AT commands have been added to those described in the manual, which may be useful for determining current system status. The responses from the messages are fairly verbose, so they are not documented completely here. Command Description ------- ----------- ATS101 Show Local Options ATS105 Show TA Parameters ATS106 Show LAPF Parameters 4.6 SELF TEST UTILITY UNDER WINDOWS FOR WORKGROUPS ---------------------------------------------- The Self Test utility requires both ports to be configured for V.120 operation. 4.7 ISDN NETWORK ISSUES ------------------- 4.7.1 Calling Subaddress ------------------ Although the X.TOLL product allows filtering of incoming calls by Calling Party Number and Calling Party Subaddress, certain ISDN networks (including BT ISDN2) do not supply the Calling Party Subaddress on an incoming call. You should check whether this is the case with your ISDN service supplier before relying on this information for filtering of incoming calls. 4.8 SPOOFING -------- Spoofing is the name given to the technique of disconnecting and later reconnecting the actual communications connection (eg ISDN call) without affecting the applications using it. This can save on call charges which are time based such as those for ISDN. In general it is best to control spoofing and line inactivity at the highest level possible. If the application or protocol stack (eg TCP/IP) using the X.TOLL adapter supports these types of facility they should be used in preference to the similar, but lower placed, X.TOLL features. 4.8.1 Protocol Spoofing ----------------- Protocol Spoofing is the local generation of responses to IPX, IP or NetBEUI maintenance packets (eg RIPs and SAPs) in order to prevent them being forwarded over the WAN interface. This release of X.TOLL does not support protocol spoofing, however checking any of the protocol spoofing boxes in the Connection Charge Optimisation section of the X.TOLL Configuration utility will cause X.TOLL to connect and disconnect the ISDN line when inactive in a way which is transparent to the application above. See section 4.8.2 for details on how this can be used when making Internet connections. 4.8.2 IP Spoofing for WWW Browsing ---------------------------- Generally, when using ISDN, it is recommended that the ISDN connections should be hung up during periods of inactivity. This obviously greatly reduces the overall ISDN charges. For example, when using a World Wide Web (WWW) browser, the Internet connection can be disconnected when idle (e.g. going to lunch, or reading a long WWW page). Note: Some Internet Service Providers issue PPP LCP Echo frames. These are usually transmitted at least once a minute and will have the effect of keeping the line up continually. In this case it will be necessary to disconnect manually prior to periods of inactivity in order to minimise ISDN line costs. 4.8.3 Spoofing and V.120 ------------------ X.TOLL COM Port Emulation uses the LAP-F link-layer protocol and supports both Multiple Frame Acknowledged and Unnumbered modes of operation. By default X.TOLL will attempt to negotiate the use of Multiple Frame Acknowledged mode when establishing a new V.120 connection. If the remote device does not support Multiple Frame Acknowledged mode then Unnumbered mode will be used. Multiple Frame Acknowledged mode requires polling at regular intervals, by default X.TOLL issues these every 30 seconds. Therefore if the idle timeout period is set greater than 30 seconds the ISDN line will never be disconnected due to inactivity. The RR polling interval is controlled by the T203 timer, the value of which can be set in the LAPF section of the XTOLLCFG.INI file. Note that both the local and remote devices issue polling frames and therefore both ends require their local T203 timer to be modified. 4.9 WINDOWS FOR WORKGROUPS REMOTE ACCESS ------------------------------------ 4.9.1 Configuration ------------- This section is an amendment to page 12-1 of the X.TOLL manual. When selecting a port to work with RAS service select the COM port ,either COM 3 or 4, that is associated with your X.TOLL configuration. After a port has been selected a modem list will appear, select the following; Hayes Compatible 9600. Finally select whether you wish the port to accept incoming calls or otherwise. The server feature of the Windows for Workgroups Remote Access software is not supported in this release. The client operation to a Windows 95 Dial-up Networking server is supported. 4.10 X.TOLL RE-INSTALLATION FOR WINDOWS FOR WORKGROUPS ------------------------------------------------- If the X.TOLL software is reinstalled and the XTOLLCFG.INI file has been deleted, but the line "device=xtollta.386" has not been removed from SYSTEM.INI, the installation will add another device entry in the SYSTEM.INI file. When Windows is started, the message "X.TOLL COM Port Emulation: Cannot assign IRQ" will be displayed. Remove one of the "device=xtollta.386" entries and restart the system. 4.11 X.TOLL REMOVAL FOR WINDOWS FOR WORKGROUPS ----------------------------------------- There is no uninstall utility to remove the Windows for Workgroups X.TOLL installation. To remove X.TOLL delete the files in the X.TOLL installation directory and the following additional files (where WINDOWS should be replaced by the name of your main Windows directory): \WINDOWS\XTOLL*.* \WINDOWS\SYSTEM\XTOLL*.* Remove the following lines from the [386Enh] section of \WINDOWS\SYSTEM.INI: device=xtollmon.386 device=xtollta.386 The following lines in the [386Enh] section of \WINDOWS\SYSTEM.INI should be restored to their original state by removing the ';' character and the comment 'Removed by X.TOLL ISDN' on each line: COM3Base=; Removed by X.TOLL ISDN COM4Base=; Removed by X.TOLL ISDN The next time Windows is restarted, a message will be displayed warning that it has failed to find the Program Manager group file for X.TOLL. This warning may be ignored, and should be selected when asked whether the group should be loaded in future. 5. THIRD PARTY HARDWARE ISSUES =========================== 5.1 X.TOLL PCMCIA CARD AND SYSTEMSOFT’S CARDSOFT -------------------------------------------- SystemSoft supply the Card and Socket Services support shipped with many portable PCs including at least some models from DELL, Compaq, Digital and others. The SystemSoft name for this software is "CardSoft", but some manufacturers may brand it with their own name. The CardSoft Enabler (CARDID.EXE) will only enable cards which are known to it. To identify the X.TOLL PCMCIA card to the CardSoft Enabler, perform the following steps. 1. Find the directory containing the CardSoft software. This directory will contain at least one file with the extension '.CLB' and also the Enabler itself (CARDID.EXE). 2. Copy the file XTOLL.CLB from the X.TOLL directory to the CardSoft directory. 3. Edit the CARDID.INI file and in the [Libraries] section add the following line: CardLib=XTOLL.CLB 4. Restart your system so that CARDID.EXE is reloaded. The X.TOLL PCMCIA Card should now be recognised and configured by the CardSoft Enabler. 6. ISDN CAUSE CODES ================ When an ISDN call fails to connect, a cause code may be used to pinpoint the problem. A cause may be returned locally from the ISDN software, or from the ISDN exchange. The cause code may be viewed in the Monitor Utility when the call is cleared, or at the TA command interface if the verbose result code form is enabled with the command ATV1. To receive text messages describing the cause code, enable extended result codes with the command ATX1. Below is a list of common ISDN cause codes, some of which may differ according to your ISDN particular service. Contact your service supplier for a complete list of codes for your particular service. Cause codes are shown as decimal numbers with a brief description. If any problem is persistent, contact your service supplier in the first instance, who will check your network connection. 6.1 NETWORK GENERATED CAUSE CODES ----------------------------- NORMAL EVENT CLASS 1 Unallocated (unassigned) number - NUMBER UNOBTAINABLE 2 No route to specified transit network 3 No route to destination 4 Channel unacceptable 6 Channel unacceptable 7 Call awarded and being delivered in an established channel 16 Normal call clearing - CLEARED 17 User busy - NUMBER BUSY 18 No user responding - NO REPLY 19 No answer from user (user alerted) 21 Call rejected - NUMBER UNOBTAINABLE, TERMINAL UNAVAILABLE 22 Number changed - USER HAS CHANGED NUMBER 26 Non-selected user clearing 27 Destination out of order - LINE OUT OF SERVICE 28 Invalid number format 29 Facility rejected 31 Normal call clearing (unspecified) RESOURCE UNAVAILABLE CLASS 34 No circuit/channel available 38 Network out of order 41 Temporary failure - SERVICE TEMPORARILY UNAVAILABLE 42 Switching equipment congestion - NETWORK BUSY 43 Access information discarded 44 Requested circuit/channel not available 47 Resources unavailable, unspecified SERVICE OR OPTION NOT AVAILABLE CLASS 49 Quality of service unavailable 50 Requested facility not subscribed 57 Bearer capability not authorised 58 Bearer capability not presently available 63 Service or option not available, unspecified SERVICE OR OPTION NOT IMPLEMENTED CLASS 65 Bearer capability not implemented 66 Channel type not implemented 69 Requested facility not implemented 70 Only restricted digital information bearer capability is available 79 Service or option not implemented, unspecified INVALID MESSAGE CLASS (EG PARAMETER OUT OF RANGE) 81 Invalid call reference value 82 Identified channel does not exist 83 A suspended call exists, but this call identity does not match it 84 Call identity in use 85 No call suspended 86 Call having the requested call identity has been cleared 88 Incompatible destination - NUMBER UNOBTAINABLE 90 Destination address missing or incomplete - NUMBER INCOMPLETE 91 Invalid transit network selection 95 Invalid message, unspecified PROTOCOL ERROR CLASS (E.G. UNKNOWN MESSAGE) 96 Mandatory information element is missing 97 Message type non-existent or not implemented 98 Message not compatible with call state or message type non-existent or not implemented 99 Information element non-existent or not implemented 100 Invalid information element contents 101 Message not compatible with call state 102 Recovery on timer expiry 111 Protocol error, unspecified INTERWORKING CLASS 127 Interworking, unspecified 6.2 LOCALLY GENERATED CAUSE CODES ----------------------------- NORMAL EVENT CLASS 144 Normal call clearing - local 149 Call rejected - local 154 Non-selected user clearing - local 155 Destination out of order - local 159 Normal call clearing (unspecified) - local RESOURCE UNAVAILABLE CLASS 169 Temporary failure - local 172 Requested circuit/channel not available - local SERVICE OR OPTION NOT IMPLEMENTED CLASS 194 Channel type not implemented - local 216 Incompatible destination - local PROTOCOL ERROR CLASS 230 Recovery on timer expiry - local INTERWORKING CLASS (USED IN PROGRESS INDICATIONS) 240 Dialtone - local 241 Alerting - local 249 Call proceeding - local 254 Unspecified progress - local 255 Silence - local 6.3 GERMAN 1TR6 NETWORK SPECIFIC CAUSE CODES ---------------------------------------- 1 Invalid call reference value 3 Bearer service not implemented 7 Call identity does not exist 8 Call identity in use (by a suspended call) 10 No channel available 16 Requested facility not implemented 17 Requested facility not subscribed 32 Outgoing calls barred 33 User access busy (B channels occupied) 34 Not CUG compatible 6.4 ACTION ON SPECIFIC ISDN CAUSE CODES ----------------------------------- Some ISDN codes may indicate local problems. For example cause code 155 may indicate a cabling problem or that the exchange or local ISDN software was not ready for the call. Retrying the call may be sufficient to establish a connection. Clearing cause 216 indicates that an incoming call was cleared locally as no application was listening for the call on the particular number or sub- address called.