Vanguard Applications Ware Multi-Service Feature Protocols

Transcription

1 Vanguard Applications Ware Multi-Service Feature Protocols Vanguard Integrated Services Digital Network: ISDN

2 Notice 2008 Vanguard Networks. 25 Forbes Boulevard Foxboro, Massachusetts Phone: (508) Fax: All rights reserved Printed in U.S.A. Restricted Rights Notification for U.S. Government Users The software (including firmware) addressed in this manual is provided to the U.S. Government under agreement which grants the government the minimum restricted rights in the software, as defined in the Federal Acquisition Regulation (FAR) or the Defense Federal Acquisition Regulation Supplement (DFARS), whichever is applicable. If the software is procured for use by the Department of Defense, the following legend applies: Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS If the software is procured for use by any U.S. Government entity other than the Department of Defense, the following notice applies: Notice Notwithstanding any other lease or license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the Government regarding its use, reproduction, and disclosure are as set forth in FAR (C). Unpublished - rights reserved under the copyright laws of the United States.

3 Notice (continued) Proprietary Material Information and software in this document are proprietary to Vanguard Networks (or its Suppliers) and without the express prior permission of an officer, may not be copied, reproduced, disclosed to others, published, or used, in whole or in part, for any purpose other than that for which it is being made available. Use of software described in this document is subject to the terms and conditions of the Software License Agreement. This document is for information purposes only and is subject to change without notice. Part No. T0103, Rev I Publication Code: TK First Printing: November 1998 Manual is current for Release 7.3 of Vanguard Applications Ware. To comment on this manual, please send to vntechsupport@vanguardnetworks.com

4 This page intentionally left blank.

5 Contents Chapter 1. Vanguard ISDN Chapter 2. ISDN Functionality and Supporting Services POTS Support X.25 Functionality for BRI th SCC (Software Serial Controller Channel) Vanguard ISDN Model ISDN Applications D Packet Configuration Example Quick SPID Configuration Link Back Up (LBU) Configuration Example Same Port Back Up (SPBU) Configuration Example Frame Relay Same Port Back Up Example POTS Application Examples Multiple PPP Configuration Example Chapter 3. Configuration and Statistics Configuring ISDN Ports X.25 Port Configuration BRI ISDN Interface Configuration Booting ISDN Ports ISDN BRI Voice Configuration ISDN BRI Voice and Data Configuration ISDN Statistics Other Menus Supporting ISDN Chapter 4. Cause Codes and Diagnostic Codes v

6

7 Chapter 1 Vanguard ISDN Overview Introduction About this Manual About ISDN Applications Ware ISDN Support This manual describes the Integrated Digital Services Network (ISDN) as it is offered for use on Vanguard products. At this time, only the BRI (Basic Rate Interface) version of ISDN is available for Vanguard products. This manual is only for the software-specific information associated with the Vanguard ISDN option. Hardware installation information is contained in the various Vanguard Installation manuals. This option manual assumes that you are familiar with your Vanguard and its interface via the Control Terminal Port (CTP). If you need additional information about your Vanguard system, refer to the relevant Vanguard documentation. ISDN is an all-digital, data-communications network that allows users to access a range of separate transmission services via a single set of interface standards, providing universal end-to-end connectivity over digital lines. The Vanguard ISDN functionality is available in most Applications Ware licenses for Vanguard products. Certain features, such as 5th SCC, are available only for specific Vanguards. Such limitations are indicated in this manual where applicable. ISDN Support on Vanguard Products We offer two distinct ISDN solutions for its products. One, supporting all Vanguard products is described in this manual. The second, supporting the Vanguard 6520 and Vanguard 6560 only is described in the Vanguard 6520/6560 Integrated Services Digital Network Manual (Part Number T ). The ISDN solution described in this manual is available with any Vanguard product capable of supporting the Vanguard ISDN Daughtercard or the ISDN BRI Data Feature Card (Host Card and Daughtercard) arrangment, as it is used in Vanguard 6520 and Vanguard 6560 products. Vanguard ISDN Functionality The Vanguard ISDN solution provides these features and functions: POTS Support X.25 functionality for BRI 5th SCC (Software Serial Controller Channel) ISDN applications Chapter two covers these features and functions in detail. Vanguard ISDN 1-1

8

9 Chapter 2 ISDN Functionality and Supporting Services Introduction This chapter describes the implementation of ISDN for use on all Vanguard products. In this chapter you will find: POTS Support section on page 2-2 X.25 Functionality for BRI section on page 2-6 5th SCC (Software Serial Controller Channel) section on page 2-8 Vanguard ISDN Model section on page 2-11 ISDN Applications section on page 2-14 ISDN Functionality and Supporting Services 2-1

10 POTS Support POTS Support Introduction Vanguard ISDN includes the capability to integrate both voice and data transmissions to and from Vanguard products. The voice capability is given using POTS (Plain Old Telephone System) ports on the Vanguard. For Vanguard 652 or 312 units, the POTS ports are located at the rear of the Vanguard case, and are labelled POTS1 and POTS2. Current Vanguard POTS over ISDN functionality is only available on certain Vanguard models. The ISDN BRI Data Feature Card for the Vanguard 6520/6560 does not provide POTS over ISDN capability. The POTS port operates similarly to your current analog telephone line. It allows you to connect any Standard, Good Quality telephone devices (i.e., answering machine, modem, fax machine, or Dual Tone Multi-Frequency [DTMF] telephone) to your ISDN service using your Vanguard. Dial Pulse telephone sets are not supported. ISDN BRI Data Feature Card is currently not certified for connection to the Public Switched Telephone Network. POTS Features and Functions Telephone/Fax Interface Features Tones, DTMF, and Announcements Vanguard POTS support includes the following features: Support for Off/On-Hook detection, and ringing voltage generation Ability to initiate and receive ISDN voice calls Support for in-band dial tones and ring-back tones from the ISDN network Support for the ISDN signaling of the call s progress Logging of calls placed, received, and the duration of each Vanguard POTS does not differentiate between voice, fax, or modem traffic. All traffic is handled as voice. Unless otherwise configured, all voice calls are given higher priority than data calls, and the data port is disconnected when a voice call is activated. Distinctive ringing, and pulse dialing are not supported. If the ISDN interface is unable to originate the call, the Vanguard will not generate a dial tone. This may be caused by a SPID initialization failure, TEI problem, configuration errors, or the interface itself being down. If the phone remains off-hook after a voice call has been terminated, a five-second timeout will trigger an automatic outgoing call sequence (emulating the PSTN functionality). If the phone goes back on-hook before the timeout expires, the timer is stopped. If no DTMF information is sent in the second call, the network terminates the call automatically, and the phone remains dead until it goes back on-hook. Network-generated tones and announcements are directed to the POTS port device. If tones are not available, the Vanguard will generate tones itself. 2-2 ISDN Functionality and Supporting Services

11 POTS Support Incoming Call Processing Outgoing Call Processing Caller Line ID (CLID) If each POTS port has a unique DN (Directory Number), ringing is initiated on the POTS port with the configured DN. If both ports have a common DN, ringing is initiated on the first available POTS port, and only the device on that port can answer the call. The Vanguard then sends an alerting message to the switch. For outgoing data calls, data applications use unblock mode. For voice calls, the bearer capability uses 3.1 khz audio as the default, and speech is not a configurable option. The layer 1 protocol is M-Law, and it is 64K circuit mode. CLID service displays the name and/or number of incoming calls, on any North American Call Display Unit. This feature is available provided that your ISDN service provider supports this service. This is generally an added cost feature that must be subscribed to from your ISDN service provider. This feature is available for North American display units only. Figure 2-1 identifies how to connect your Vanguard device for this feature to operate. Telco ISDN Network Vanguard CLID Display Unit Figure 2-1. Vanguard ISDN CLID Connections Call Waiting Call waiting is available for voice calls using ISDN (for NI1 ISDN switches only). When this feature is enabled, a caller hears a Call Waiting tone when a second call arrives. At that point, you can either Hang up on the current call allowing the second call through. Place the current call on hold by pressing the flash button or momentarily pressing the hook switch, so that the second call is connected. (You can alternate between the two calls by pressing the flash button or pressing the switch hook.) The Call Waiting tone is sent twice. If you do not respond to the tone, the second call is cleared. To enable Call Waiting, you must contact the ISDN provider and ask for Additional Call Offering (ACO) and HOLD supplementary services. (If these are not available, Call Waiting cannot function.) Once these services are in place, no additional configuration is necessary; the feature is fully functional. You cannot use Call Waiting when a fax is connected to a port. There is no way to disable the Call Waiting signal which can disrupt a fax call. ISDN Functionality and Supporting Services 2-3 T , Revision I Release 7.3

12 POTS Support You can disable the Call Waiting feature for the duration of a current outgoing call. To temporarily disable Call Waiting Pick up the handset and dial *70. Wait five seconds until you hear a second dial tone. Dial the number. After you hang up this call, Call Waiting is once again enabled. Alternate Voice and Data Data Over Voice (DOV) Unless otherwise configured, all voice calls are given higher priority than data calls, and the data port is disconnected when a voice call is activated (telephone is off the hook). When the voice call is disconnected, the data port is notified. It is then up to the data port to retry the connection. CVL is not supported for alternate voice and data service. Multilink, or non-multilink data calls are not dropped for an incoming voice call request. Instead, the call is rejected. Data calls can be made over Voice (CSV) channels, but there are limitations on connectivity. The connection is operable only within the ISDN environment. There is no interoperability for DOV between ISDN and Analog PSTN (as this requires modem software), ISDN and non-isdn digital networks (since it uses CSD), and ISDN connected to another ISDN over non-isdn network (since it also uses CSD). When the switch determines the call is not end-to-end ISDN, or the call has exited the ISDN network, the DOV call is cleared. The type of data protocol is not indicated in an ISDN call; therefore, both ends have to match. A data or voice call cannot be differentiated, but the ISDN call indicates 3.1Khz Audio or Speech. This feature works only with third party devices that support PPP (Point-to-Point Protocol) (RFC1662) over DOV. For an originating call, the configuration indicates that it is a DOV call. The Bearer Capability is not configurable (3.1Khz Audio will be used). When the switch determines the call is not end-to-end ISDN, or the call has exited the ISDN network, the DOV call is cleared. An automatic attempt with data bearer capability (B.C. = CVD) is tried when the first call with voice bearer capability (B.C. = 3.1K) has failed. If the network rejects the initial SETUP request (with bearer capability set as 3.1K Audio) due to incompatible bearer capability (cause code 88) or bearer capability not available (cause code 58), the Vanguard will automatically send the SETUP request again (with bearer capability set as CSD). For an incoming DOV call, the data port is connected to the B-Channel if the configuration indicates DOV call can be accepted (two DNs or POTS disabled). The POTS port will be connected to B-Channel if POTS is enabled and has a single DN. When the switch determines the call is not end-to-end ISDN, or the call has exited the ISDN network, the DOV call is cleared. The actual data rate over the voice channel is 56K. 2-4 ISDN Functionality and Supporting Services

13 POTS Support If you have one common DN, and the line provisioning is set to 1B or 2B-Channels, incoming calls cannot be discriminated between voice and data. If POTS is disabled, the incoming call will go to the data connection. If both the POTS and Data port are enabled to share the same channel, the incoming call will go to the POTS. If you have two DNs, and the line provisioning is set to 2B-Channels, the incoming call can be discriminated between voice and data. POTS disabling is not required for data connection. Enhancements for Data Support POTS Specification Compliance The following enhancements have been made to the Vanguard ISDN feature with the introduction of POTS support. You can now mix Permanent B and Dial B configuration within a single BRI provided that the D-Channel is configured. The ISDN alarms have been enhanced to track call status. Rejected incoming calls are now logged in the call history. The ISDN call history log can now be cleared using the Reset Statistics command. Since some Telcos have limited 64K circuits available, a B-Channel that is configured to 64K may encounter frequent busy signals. The redial software now checks if the previous rejected call was due to NO_CIRCUIT_AVAILABLE (cause code 34). If that is the case, the line speed is automatically dropped to 56K. Vanguard POTS functionality has been designed for compatibility with the EIA/TIA-464, PBX Switching Equipment for Voiceband Applications specification. ISDN Functionality and Supporting Services 2-5 T , Revision I Release 7.3

14 X.25 Functionality for BRI X.25 Functionality for BRI Introduction Calling Address Call Holding This section describes functionality for BRI that is specific to X.25 connections. If you need to have a pool of BRI channels and route calls dynamically on the BRI channels based on the Called X.25 addresses, use the Dynamic Routing and Dynamic DTE/DCE assignment. The system provides a user-configured Calling Addresses table. Vanguard provides Calling Address verification of incoming calls on a per-channel basis. The Calling Address is associated with the channel used for the outgoing call. The Calling Address is transmitted out-of-band in the Calling Party Number information element of the Q.931 Setup message. An ISDN call is not established unless the Calling Address matches an entry in the configured table. If a port sends an X.25 Call Request to a virtual port on a BRI line, the call is held in the Switch Service table until the BRI line is setup. Under normal circumstances, if a port sends an X.25 Call Request and encounters a BRI line that is not setup, it clears the call. This feature prevents it from doing so. The call is forwarded to the Called Address once the BRI line is setup. You must configure these records: X.25 ports that send Call Requests with the option AP+CAUSE in the X.25 Options parameter. All B-Channels as Switched Service entries. The dynamic routing table is built from the Switched Service Table. The Link Hold Timeout keeps an ISDN link open when no data is passing over the link. It activates when the node establishes Link Layer 2 of the X.25 connection and deactivates when at least one X.25 call becomes active. The Link Hold Timeout is 3 minutes. It is not configurable. This table describes when the Call Holding feature clears calls. If... The B-Channel is disabled. The ISDN Daughtercard is defective, or during initial Node Setup time (when it is booted). The node is initializing during Node Setup Time. The port or channel is booted or disabled. Then... The node clears Call Requests and sends an Out of Order cause code. The node clears the X.25 call and sends a No Path cause code. The node clears Call Requests and sends a No Path cause code. The node clears all queued Call Requests and sends an Out Of Order cause code. 2-6 ISDN Functionality and Supporting Services

15 X.25 Functionality for BRI If... The ISDN Daughtercard is operational, and both B-Channels are available but dial out fails. The application (that sends the Call Request) clears the call and the ISDN call is successful. Then... (continued) The node retries the same number on the same B-Channel. Once maximum retry attempts have expired, the call is cleared with an X.25 cause code. The Call Clear from the application does not clear the ISDN link. The ISDN link disconnects only after its detects that it is not passing data and the Link Hold Timeout expires. Dynamic Routing Dynamic DTE/DCE Assignment Dynamic Routing allows a pool of B-Channels to be routed dynamically based on the Called X.25 addresses. Here dynamic means a call with any X.25 address can be routed to any B-Channel, provided the channel is free. A channel is dedicated to a X.25 Called Address as long as the call is in place. Once the call is disconnected, the B-Channel goes back to pool. In addition, Dynamic Routing allows multiple calls to and from the Called Address to be routed onto the same B-Channel. All calls outgoing calls to and incoming calls from the Called Address pass across this (temporarily) dedicated link. A node with the Dynamic Routing feature enabled reads the Call Address Extending Facility (CAEF) in an X.25 Call Request. The CAEF contains an ISDN dialing number (SPID) that is used to route the call in the following ways: From the CAEF, the node extracts the ISDN number (SPID) to which it makes a new ISDN call. After the B-Channel is established, it is dedicated to a specific Called Address for the duration of its call. The node uses the CAEF in subsequent Call Requests to determine if there is an existing B-Channel for the specified Called Address. It scans each open link to see if any current link is dedicated to the Called Address it is looking for. The CAEF overrides the SPIDs that are configured in the ISDN Channel record. If a Call Request arrives without a CAEF, the node opens a channel with the configured SPIDs. The CSK to enable this functionality is: QBZ662KYG9SN44Y7YD6P. When you use this functionality, nodes on the network are automatically assigned DTE and DCE status. At the time it establishes the ISDN connection, the node that originated the call is assigned as the status of DTE. The node that receives the call is assigned the status of DCE. This function overrides the NEGOTIATE option in the Link Address parameter of the ISDN Channel record. The CSK to enable this functionality is E5X2B99AA45A379VBV4K. ISDN Functionality and Supporting Services 2-7 T , Revision I Release 7.3

16 5th SCC (Software Serial Controller Channel) 5th SCC (Software Serial Controller Channel) Introduction The MC68360 Communications Processor supports only four hardware serial communication controllers (SCC). A fifth SCC (5th SCC) has been implemented in software. This section explains how 5th SCC works and how it can be configured for your application. 5th SCC is only available with Vanguard 300/305, 320, 340 and 342 products. Enable 5th SCC Using 5th SCC 5th SCC is enabled by setting the ISDN Channel Parameters parameter D-Channel Port to 4. Refer to the parameter D-Channel Port on page 3-7. A typical application for 5th SCC is when a Vanguard 300 is connected to two remote LANs via separate switched ISDN B-Channels and when a serially attached FEP or controller is located at the site. The 5th SCC is limited to low-speed applications and therefore can only support the ISDN D-Channel. SCC allocation: 1 SCC is used for the Ethernet Port. 1 SCC is required for the ISDN D-Channel whether it is used for data traffic or just used for signaling. 1 SCC is required for each ISDN B-Channel (if both B-Channels are to be used then 2 SCCs are required). 1 SCC is required for each serial port used. The 5th SCC must be invoked for the ISDN D-Channel when the sum of the SCCs is 5. For example: 2 ISDN B-Channels 1 ISDN D-Channel 1 LAN port 1 serial port = 5 SCCs However, if the ISDN B-Channels are configured for permanent connection and the ISDN D-Channel is not required for data traffic, the SCC for the D-Channel is not required and can therefore, be used for a serial port. 2-8 ISDN Functionality and Supporting Services

17 5th SCC (Software Serial Controller Channel) Figure 2-2 shows the logic between the MC68360 and the ports or ISDN module. The SCCs can only be assigned to one destination, either the ISDN or the serial port (but not both). Port 1 Port 2 Port 3 Ethernet ISDN B1 Ethernet Port Processor SMC B2 D-Channel Software SCC SCC 5 Port 4 Control Port Figure 2-2. How 5th SCC Functions SCC Configuring 5th SCC To configure the Vanguard 300 for 5th SCC operation: configure port 4 for X.25 operation. Set the ISDN D-Channel port number to 4 instead of 1. The B-Channels can be configured for ports 1, 2 or 3. Port 1 must be configure as a B-Channel. Refer to Figure 2-3. Port 1 Port 2 Port 3 Ethernet ISDN B Ethernet Port Processor SMC B D-Channel Software SCC SCC 5 Port 4 SCC Control Port Figure th SCC Configuration Example ISDN Functionality and Supporting Services 2-9 T , Revision I Release 7.3

18 5th SCC (Software Serial Controller Channel) Figure 2-3 shows: Ports 1 and 3 are configured for ISDN B-Channels. Port 2 is configured for a serial protocol. Port 4 is configured for the ISDN D-Channel. Configuration Settings This table shows how to configure Port 4 and the ISDN D-Channel parameters as shown in Figure 2-3. Only those parameters related to 5th SCC are shown. The rest of the parameters are configured as usual. Parameter Setting Port Number 4 Port Type X25 Link Address DTE Number of SVC Channels 1 T1 Transmission Retry Timer (1/10 sec) 10 T4 Poll Timer 200 Frame Sequence Counting EXT K Frame Window 3 X.25 Options PDN+CUD D-Channel Port 4 5th SCC Limitations You need to be aware of these limitations when using 5th SCC: The 5th SCC is only available on port 4 and therefore the ISDN D-Channel has to be assigned to port 4. This creates a problem that there is no local CTP access. The CTP can be remotely connected using an X25 call or via Telnet. If local access is required set the front panel switch to allow CTP access via port 3 and reset the unit. The S/T bus cannot be shared by multiple ISDN devices when one of the devices is running the D-Channel over port 4. The implementation of 5th SCC causes a 30-percent load on the CPU utilization ISDN Functionality and Supporting Services

19 Vanguard ISDN Model Vanguard ISDN Model Introduction Figure 2-4 illustrates the Vanguard ISDN implementation details, and gives an overview of how to configure your Vanguard for ISDN. Vanguard 100/300/305/ 310/320/340 Port 1 Port 2 Port 3 A) Configure the node. B) Configure the ports. C) Configure ISDN BRI Interface and mode of operation D B1 B2 (Built-in on the motherboard of the Port 11 Port 12 ISDN Daughtercard Vanguard 310 and 650) Port 10 D B1 B2 ISDN BRI Interface (U or S/T) Port 7 Port 8 Port 9 D B1 B2 ISDN Daughtercard #1 Vanguard 6400 Series ISDN Daughtercard #2 BRI I/F #1 (U or S/T) BRI I/F #2 (U or S/T) Port 14 Port 15 Ports 13 D B1 B2 ISDN Daughtercard #3 BRI I/F #3 (U or S/T) Vanguard 6520/6560 ISDN Vanguard Multi-BRI Implementation ISDN BRI CARD D B1 SLOT/PORT ASSIGNMENT Slot 1: D = 7, B1 = 8, B2 = 9 (6560 Only) Slot 2: D = 13, B1 = 14, B2 = 15 Slot 3: D = 19, B1 = 20, B2 = 21 Slot 3: D = 25, B1 = 26, B2 = 27 Slot 4: D = 31, B1 = 32, B2 = 33 Slot 5: D = 37, B1 = 38, B2 = 39 Slot 6: D = 43, B1 = 44, B2 = 45 Slot 7: D = 49, B1 = 50, B2 = 51 Slot 8: D = 55, B1 = 56, B2 = 57 BRI Interface #1... #8 (U or S/T) ISDN Figure 2-4. ISDN Implementation Model ISDN Functionality and Supporting Services 2-11 T , Revision I Release 7.3

20 Vanguard ISDN Model Configuring Your Vanguard There are three primary steps to configuring your Vanguard for ISDN operation. Step Action Details 1 Configure the node. You must configure the node for the application you are running. 2 Configure the BRI ISDN Interface. 3 Configure the BRI ISDN Interfaces. You need to configure each BRI ISDN Interface appropriately: D-Channel Port must be configured for FRI or X.25 for ISDN Permanent B, and must be X.25 for Switched B with D- Channel signaling (Q931) or D Packet data. B-Channel port types are PPP, X.25, or FRI. Configure them as usual. If you set the Connection Type to SIMP, the port will be Power Up Dial capable. If you set the Connection Type to DIM0, it will be Dial on Demand enabled. There is no ISDN port (as there is for 652). ISDN is configured by assigning the appropriate channels to ports. You must configure each BRI ISDN Interface, and the mode of operation for the application you are running, according to the parameters supplied by your ISDN Service Provider. BRI Interface Ports These tables identify how ports are allocated on Vanguard products. Port Type VG100 VG300/ 305 VG320/ 340, 342 VG310 Series 650 Vanguard 6400 Series D-Port 1 Either 1 or B-Port 2 or 3 Port 1 and 2 and/or 3 (if port 1 is the D-Port) or 2 or 3 (if port 4 is the D-Port) 2 and/or 3 2 or 3 8 and 9 11 and and ISDN Functionality and Supporting Services

21 Vanguard ISDN Model Port Type Vanguard 6520/6560 Slot Number Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 D-Port B1-Port B2-Port Slot 1 is available only on the Vanguard ISDN Functionality and Supporting Services 2-13 T , Revision I Release 7.3

22 ISDN Applications ISDN Applications Introduction The following sections outline some sample ISDN network configurations, and how to configure these examples. For detailed information on the individual parameters used in these examples, refer to Chapter 3. The Vanguard 6400 Series and Vanguard 6520/6560 models may have different port assignments. Auto-Configuration Auto-configuration allows you to plug in your Vanguard and have it configured remotely. This enables your central site system administrator to log into the control port of the Vanguard remotely, and complete the necessary configuration. Default X.25 Port 1 Settings Any Vanguard product, running a licensed Applications Ware image that includes the X.25 protocol, is activated with a pre-defined, factory-default configuration. This configuration sets Port 1 to X.25, and configures the first ISDN Channel. These are the X.25 port configuration parameter defaults: Parameter Setting Clock Source EXT Link Address DTE Number of SVC Channels 1 T1 Transmission Retry Timer 10 T4 Poll Timer 200 N2 Transmission Tries 3 Frame Sequence Counting EXT K Frame Window 3 P Packet Size 256 X.25 Options PDN+CUD+NP Number of Routing Digits in Call User Data 5 Number of SubAddress Digits in X.25 Address ISDN Functionality and Supporting Services

23 ISDN Applications Default ISDN Port 1 Settings This table identifies the default ISDN settings for Port 1: Parameter Channel Type D Associated Port 1 Switch Type NI-1 TEI 128 SPID none Setting The Vanguard 6400 Series and the 6520/6560 do not use Port 1 for ISDN. Many ISDN services in North America require that you configure a SPID. Please check with your ISDN service provider. This functionality is only available if: The licensed Applications Ware image running on the Vanguard device contains X.25 protocol capability. This is not available for Frame Relay option packages. The ISDN service is DMS100 Custom or NI-1, and the TEI for packet data is 21. This is the most common value, but if the carrier requires a different value you must configure the value before the unit can be accessed remotely. The ISDN service is 5ESS Custom or NI-1, and provisioned 0B+D. If the line is 1B+D or 2B+D, and requires a SPID to initialize the BRI, you must configure the SPID before the unit can be accessed remotely. Dialing Configurations Power-Up Dial Configuration There are 2 main dialing configurations that are typically used for an ISDN application: Power-up Dial Dial-on-Demand For the Power-Up Dial configuration, whenever the node or the port is booted, an ISDN call is automatically established, as shown in Figure 2-5. T1 Local Vanguard Telco ISDN Network Remote Vanguard Figure 2-5. Power-Up Dial Test Configuration In Figure 2-5, to call the remote node, boot the local node Port 2 or 3, whichever is configured to Power-Up Dial. An ISDN call is initiated, and a link between the remote and local node ports is established. ISDN Functionality and Supporting Services 2-15 T , Revision I Release 7.3

24 ISDN Applications To terminate the ISDN call when you are in Power-Up Dial mode, disable the port. To configure the node for this application, you must: Configure your Port Connection Type (Port 2 or 3) as SIMP The Port configurations are: - Port 1 = X25 (mandatory Q931 signaling) - Port 2 = X25 or FRI or PPP; EIA type MUST be SIMP (your data port) Change the BRI ISDN Interface configuration to include at least one outbound number. BRI ISDN Interface configuration parameters are: - D-Channel Port = 1 - D Packet Data = Disable (enable only if your line has D-packet provision) - Switch Type = NI-1 (or match the ISDN service provided) - First B-Channel Port = 2 (for this example) - (First) Access Type = CMD (CVL will provide virtual leased line) - (First) Line Speed (must match the rate of your line subscription) - (First) TEI = 127 (default is auto-negotiation) - (First) SPID (only required if your provider assigns one) - (First) Local DN (optional, if nothing entered, will accept all incoming calls) - (First) Outbound Dial Number #1 (phone number that your BRI should dial) - (First) Outbound Dial Number #2 (alternate phone number if #1 is unavailable) CVL for Power-Up Dial If you set the node for the Power-up Dial configuration, set the Access Type to CVL (Circuit Mode Virtual Leased Line), and set a non-zero redial timer, this enables the call-originating node to enter into automatic redial mode when the ISDN network has dropped the outbound call. This configuration will attempt to keep the line up indefinitely, emulating a leased line. It is recommended that you only configure one end of a link with Power-up Dial, with or without CVL, to avoid call collisions ISDN Functionality and Supporting Services

25 ISDN Applications Dial on Demand Configuration This mode is used for LBU (Link Back-Up) and BoD (Bandwidth on Demand) applications. For example: T1 Local Vanguard Telco ISDN Network Remote Vanguard T1 Figure 2-6. Dial on Demand Test Configuration Figure 2-6 depicts the configuration required when the application or protocol needs to establish a connection (on demand), such as the case where the LBU detects that the main link is down. The Vanguard initiates an ISDN call and reestablishes the link. To configure the node for this application, you must: Configure your port as follows: - Port 1 = X25 (mandatory Q931 signaling) - Port 2 = X25, Connection Type MUST be DIMO, X25 option MUST have BKUP enabled and the IDLE DISCONNECT TIMER set to a non-zero value. FRI has no support for Dial on Demand. Change the ISDN configuration to include an outbound number. BRI ISDN Interface configuration parameters are: - D-Channel Port = 1 - D Packet Data = Disable (enable only if your line has D-packet provision) - Switch Type = NI-1 (or match the ISDN service provided) - First B-Channel Port = 2 (for this example) - (First) Access Type = CMD (optionally, CVL) - (First) Line Speed (must match the rate of your line subscription) - (First) TEI = 127 (default is auto-negotiation) - (First) SPID (only required if your provider assigns one) - (First) Local DN (optional, if nothing entered, will accept all incoming calls) - (First) Outbound Dial Number #1 (phone number that your BRI should dial) Change your routing table to have priority 0 for any address going out on the specified port. (In this example, the remote node s address is 100.) Routing Table: - X25 Address = 100* (remote node s address) - Destination = P2 - Priority = 0 ISDN Functionality and Supporting Services 2-17 T , Revision I Release 7.3

26 ISDN Applications To call the remote node s CTP: - From the APAD prompt, type: C 10098, C - From the ATPAD prompt, type: ATD 10098, A In each of these examples, the first call to initiates the ISDN call, and the second portion, after the comma, is the X.25 call. Whenever a (first-time) call is made to 100XX, it initiates an ISDN dial sequence. When the ISDN connection is made, you should observe an X25 Link Up event. You can then call 100XX to reach the remote destination. When all the calls on this link have been terminated, and the idle disconnect timer has expired, the BRI ISDN connection is dropped. The other method for terminating the ISDN call is to reboot the port, BRI ISDN Interface, or node. A typical application will involve autocall setup on an access port to automatically retry this X.25 address. The most common error you will encounter is that in your routing table configuration, the priority is not set to 0. Additional Application Examples There are additional application examples provided in the following sections. These are full configuration examples, including detailed application descriptions, of some typical application environments that you may be setting up: D Packet (starting on page 2-19) Link Backup (starting on page 2-25) Same Port Backup (starting on page 2-27) Frame Relay Same Port Backup (starting on page 2-29) POTS-Specific Applications (starting on page 2-30) To simplify these examples, use default parameters whenever possible. These examples describe only the pertinent routing information and differences from a default configuration. If the parameter value is not shown here, it is assumed that the default is being used ISDN Functionality and Supporting Services

27 ISDN Applications D Packet Configuration Example Introduction The example application is provided to help you understand the configuration of D-Channel Packet related ISDN parameters. Refer to the Vanguard Basics Manual (Part Number T0113) for operation of routing, mnemonic calling, SNA, and so forth. For Node 1... For Node 2... Node Record Node Record Port Records Port Records Station Record Station Record Network Services ISDN Channel Route Selection Table Mnemonic Table Network Services Route Selection Table Mnemonic Table D-Channel Application The following section shows a typical application that would use the Vanguard 100 with the ISDN daughtercard option in its configuration. Access to the X.25 PDN through the D-Channel is supported with this release. This can result in savings over the connection fee for a 9.6 Kbps X.25 PDN access. This mode allows economies on the cost of the infrastructure and the support for the PDN equipment. It is of interest in countries where Central Office Exchanges are ISDN-compatible and where X.25 PDN is in wide use. In Figure 2-7, the Vanguard product on the left is connected through an X.25 connection to a PDN. Connectivity is provided to the second Vanguard through the D-Channel of an ISDN interface. In this particular example, the host is establishing a connection to an Automatic Teller Machine (ATM). Host T1 P2 Node 1 Node 2 Vanguard X.25 Telco ISDN PDN Network ISDN P2 Network Vanguard P1 P1 P3 P3 Local ID: Local ID: ATM T2 Figure 2-7. X.25 Access to PDN Using the ISDN D-Channel ISDN Functionality and Supporting Services 2-19 T , Revision I Release 7.3

28 ISDN Applications Application Configuration X.25 Call Numbering and Addressing This example application shows how to configure key parameters for the following requirements: Configure the X.25 port for D-Channel Packet operation Configure the LAPD parameters for D-Channel Packet operation Configure the X.25 level 3 for ISDN D-Channel Packet and PDN operation Ensure the ISDN management entity knows the association of the X.25 port and D-Channel Packet The application shown is for an SNA FEP/host connecting to an Automatic Teller Machine (ATM). The FEP connects to an HPAD (Node 1), and the HPAD connects to the TPAD (Node 2) over PDN-ISDN D-Channel Packet service. The Async terminal T1 connects to the CTP of Node 2, and the Async terminal T2 connects to the CTP of Node 1. ISDN and PDN use different addressing schemes. The addressing scheme for internetworking is specified in the X.121 and X.122 specifications. An escape code of 0 or 9 indicates that the address that follows uses a different addressing scheme. A PDN-attached terminal calling an ISDN (Packet service) terminal adds an escape code of 0 to the called address (ISDN type address). The network strips the 0 from the called address and adds a 0 to the calling address (calling address uses the X.121 PDN scheme) when it delivers the call request packet to the ISDN terminal. The ISDN-attached terminal (Packet service) calling a PDN terminal adds an escape code of 0 to the called address. The network strips the 0 from the called address and adds a 0 to the calling address before delivering the call request to the PDN terminal. To distinguish between different address formats within a PDN, a prefix is used. The PDNs may have their own numbering and addressing system. Verify this with your ISDN service provider. About This Sample Application Node 1 to Node 2 Call This X.25 call connection application example transports private X.25 addresses in the Call User Data (CUD) field. The example configuration is for Datapac (a Canadian PDN). The Mnemonic table entries have 0 or 101 added to the destination address PDN and ISDN X.25 packet service internetworking requirements. The ISDN destination address, contained in the mnemonic table of Node 1, adds 101 to the ISDN destination address (1 is the PDN prefix, 0 is an escape code indicating a non-pdn address type, and 1 is the international dialing code for North America). The PDN destination address contained in the mnemonic table of Node 2 has 0 added to the PDN destination address. The 0 indicates a non-isdn address type. In this example, the Node 1 call request packet will have a called address of and a calling address of The call received by Node 2 will have a called address of and a calling address of ISDN Functionality and Supporting Services

29 ISDN Applications Node 2 to Node 1 Call D Packet Example In this example, the Node 2 call request packet will have a called address of and a calling address of The call received by Node 1 will have a called address of and a calling address of Figure 2-8 shows a sample configuration for the D Packet example. Node 100 is a non-isdn device. Port 1 is configured as type X.25 with LAPB and X.25 parameters. The Port 1 X.25 protocol stack is LAPB and PLP (X.253). The X.25 option has PDN, CUD (for address transportation), NP, and REGO to insert the PDN subscriber address. Host T1 P2 P3 Node 100 Node 200 Vanguard X.25 Telco ISDN PDN Network Network P1 P1 Vanguard Local ID: Local ID: P2 P3 ATM T2 Node 100 Node Record Node Node Name Node Address 200 Port Record 1 Port Number 1 X25 Port Type X25 DTE Link Address DTE 2 Port Number 2 SDLC Port Type SDLC HPAD Subtype TPAD Station Record 1 Station Number 1 C7 Station Address C7 None Autocall Mnemonic Host C Protocol ID C Station Subaddress 61 QRRs Options RNRs Network Services Route Selection Table 1 Entry 1 1 Address 0 X25-1 Destination #1 X25-1 Mnemonic Call Table 1 Entry Number 1 Remote Mnemonic Name Local d20098 Call Parameters d Entry Number 2 abm Mnemonic Name Host d20061 Call Parameters d10061 BRI ISDN Interface N/A D-Channel Port 1 N/A Switch Type NI-1 N/A TEI 21 Figure 2-8. Sample Configuration for D Packet Network ISDN Functionality and Supporting Services 2-21 T , Revision I Release 7.3

30 ISDN Applications Node 200 is an ISDN device. Port 1 is configured as type X.25. The ISDN module is configured to use PLP (X.25) on Port 1 for D-Channel Packet link. The D-Channel Packet protocol stack is X.25 on Port 1, and LAPD is added to it for layer 2, making it a D-Channel Packet port. The LAPD packet D link parameters are configured as part of the Port 1 parameters (T200 for T1 Transmission Retry Timer, N200 for N2 Transmission Tries, T203 for T4 Poll Timer, Frame Sequence Counting to EXT, and K frame Window). The X.25 parameters with PDN option have PDN, CUD (for address transportation), and NP. Generally, SPID is not required for ISDN X.25 packet service. It may be needed for X.25 PVC operation ISDN Functionality and Supporting Services

31 ISDN Applications Quick SPID Configuration Introduction Configuration This feature enables auto-configuration permits the configuration of a Telcoprovided SPID, using a touch tone telephone, to allow remote access to the device from a data center over the D-packet channel. This function is necessary if the BRI ISDN service is supported by an AT&T 5ESS (NTI or custom) switch and D and both B-Channels are supplied. This feature is not required if the BRI ISDN line is serviced by a DMS1OO switch and the configured D-Channel Terminal End-point Identifier (TEI) value is less that 63. You perform Quick SPID configuration during the 5 second period that the TEST LED flashes after a node power-up or reset. If you do not wish to use this feature, perform no actions and normal Start-up Diagnostics occur. To configure the SPID: Step Action Result 1 Lift up the receiver off the telephone. This is known as going Off-Hook. 2 Enter *** to enter the configuration mode. The POTS1 LED flashes at a very fast rate. You now have 20 seconds to start Step 2. The POTS1 LED stops flashing and remains on. This indicates the acceptance of the number entry. The TEST LED flashes at a steady rate. If you do not enter this information within 20 seconds, or keys other than that indicated here are entered, the software continues with normal Start-up diagnostics. 3 Enter the SPID using this format: s#xxxxxxxxxxxxxxxxxxxx*** where: s = the switch type in use. 0 = 5ESS (with NI-1 software) 1 = 5ESS with custom software x = the SPID (D-Channel or first B-Channel) provided to you by your BRI ISDN service provider. You must start the SPID entry sequence by entering three asterisks. If the SPID provided to you is fewer than 20 characters in length, you must end the SPID format with 3 asterisks. Use the D-Channel SPID if your service provider has supplied SPIDs for D and both B-Channels, otherwise enter the SPID supplied for the first B-Channel. ISDN Functionality and Supporting Services 2-23 T , Revision I Release 7.3

32 ISDN Applications Step Action Result (continued) 4 If... Then... Result You want to terminate this procedure without modifying the original SPID record, You have entered the complete SPID and want to end this procedure by saving all changes, Place the receiver back On-Hook Replace the receiver after entering the last asterisk. a) A reset takes place a short time later. b) Whatever entries were entered previously are discarded. c) The original SPID record is not modified. This applies only if the node had previously been configured with a non-default SPID. Once the SPID is accepted, Test and POTS1 leds go off and POTS2 led latch on. After 1 to 2 seconds, UUT reboots and starts the normal power up sequence again. 5 Place the receiver back On-Hook; the node will continue to boot. Troubleshooting Once the device has been re-booted, the Status LED lights and the D LED starts to flash (Figure 2-9). Approximately 30 seconds after the correct SPID is entered, the D LED stops flashing and remains on. At this point, you have remote access to the node and the POTS port has a dial tone. The D LED flashes if a SPID was entered correctly and stays on The D LED stops flashing and stays lit if it is registered with the Telco. If the LED continues to flash, a SPID error occurred. Re-enter the SPID or The Node exists the diagnostics mode and boots. STATUS LED T = 30 to 60 T = 60 seconds seconds (max) TEI is Learned The node is ready for remote Figure 2-9. Quick SPID Troubleshooting Timeline If the D LED does not stop flashing after approximately 120 seconds: Step Action 1 Verify that the SPID provided to you is correct (check with your ISDN service provider). 2 Verify that you have the correct switch type. 3 Repeat the configuration procedure ISDN Functionality and Supporting Services

33 ISDN Applications Link Back Up (LBU) Configuration Example Overview Figure 2-10 shows how to set up a simple Link Back Up (LBU) network. This configuration contains parameters valid for a LAN connection over a primary X.25 link being backed up over ISDN BRI Channel B1. This example is only used for a Vanguard 300/305. In the example shown in Figure 2-10, you configure parameters in these areas. Node record Port records BRI ISDN Channels For Node For Node Network Services Route Selection Table Switched Services Table Router Table Interface States IP Table IP Interfaces Table LAN Connection Table Mnemonic Table Node record Port records BRI ISDN Channels Network Services Route Selection Table Switched Services Table Router Table Interface States IP Table IP Interfaces Table LBU Network Example Figure 2-10 shows a sample configuration for an LBU network. Node 100 is making the LAN autocall. ISDN Functionality and Supporting Services 2-25 T , Revision I Release 7.3

34 ISDN Applications Node 100 Node 200 PC PDN Vanguard Port 3 PC X.25 Port 3 Vanguard Port 1 Port 1 Eth ISDN ISDN Port 2 ISDN Port 2 B-Channel Network B-Channel Node 100 Node Record Node Node Name Node Address 200 High+med+conn Alarm Selection High+med+conn Port Record 1 Port Number 1 X25 Port Type X25 DTE Link Address DTE 2 Port Number 2 X25 Port Type X25 Negotiate Link Address DTE 3 Port Number 3 X25 Port Type X25 Negotiate Link Address Negotiate 5 Port Number 5 ETH Port Type ETH BRI ISDN Interface 1 D-Channel Port 1 (service provided) Switch Type (service provided) 2 First B-Channel Port SPID 2 (service provided) (First) SPID (service provided) (service provided) (First) Local Subscriber Directory Number (service provided) Network Services Route Selection Table 1 Entry Address 100 X25-3 Destination #1 X Priority 1 N/A Entry 2 N/A Address N/A Destination #1 LCON N/A Priority 0 Network Services Switched Services Table (choice) Destination Name LBU Port X25-2 Monitored Port X25-2 Port 3 Backup or Switched Services Port Port 3 Fail Activation Mode Fail (Node 200 s Phone #) Dial Sequence (Node 100 s Phone #) IMM Deactivation Mode IMM 300 Link Hold Time (Can t be 0) Redial Timer 30 (Can t be 0) Router Table Interface States Enabled Interface 1 Enabled Enabled Interface 5 Enabled Router IP Table ; Parameters ; Router Table IP Interfaces Table 1 Entry 1 1 Interface 1 Determined by network ( ) IP Address Determined by network ( ) Determined by network ( ) Address Mask Determined by network ( ) 2 Entry 2 5 Interface 5 Determined by network ( ) IP Address Determined by network ( ) Determined by network ( ) Address Mask Determined by network ( ) Mnemonic Table 1 Entry N/A Callan Mnemonic Name N/A Call Parameters N/A LAN Connection Table Rout Forwarder Type N/A 5 Router Interface N/A Callan Autocall Mnemonic N/A Figure Sample Configuration for LBU Network 2-26 ISDN Functionality and Supporting Services

35 ISDN Applications Same Port Back Up (SPBU) Configuration Example Overview Figure 2-11 shows how to set up a simple Same Port Back Up (SPBU) network. This configuration contains parameters valid for a LAN connection over a primary X.25 link being backed up over ISDN BRI Channel B1. This example is only used for a Vanguard 300/305. SPBU is also available for Vanguard 100, and the configuration is similar to what is given here, but the user port is serial, not Ethernet. The Vanguard 6400 Series does not support Same Port Back-up. In the example shown in Figure 2-11, you configure parameters in the following areas. For Node For Node Node record Node record Port records Port records BRI ISDN Channels BRI ISDN Channels Network Services Route Selection Table Router Table Interface States IP Table IP Interfaces Table LAN Connection Table Mnemonic Table Network Services Route Selection Table Router Table Interface States IP Table IP Interfaces Table SPBU Network Example Figure 2-11 shows a sample configuration for an SPBU network. Node 100 is making the LAN autocall. ISDN Functionality and Supporting Services 2-27 T , Revision I Release 7.3