Wheelchair User Manual

ManualsBrandsLucent Technologies ManualsWheelchair7820-0802-003

APX 8000

™

/MAX

TNT/DSLMAX

™

Physical Interface Configuration Guide

Part Number 7820-0802-003

For software version 8.0

May 2000

Summary of content (242 pages)

PAGE 1
APX 8000™/MAX® TNT/DSLMAX™ Physical Interface Configuration Guide Part Number 7820-0802-003 For software version 8.
PAGE 2
Copyright© 2000 Lucent Technologies. All rights reserved. This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Lucent Technologies. For permission to reproduce or distribute, please email your request to techpubs@ascend.com.
PAGE 3
Customer Service Customer Service provides a variety of options for obtaining information about Lucent products and services, software upgrades, and technical assistance. Finding information and software on the Internet Visit the Web site at http://www.lucent.com/ins for technical information, product information, and descriptions of available services. Visit the FTP site at ftp://ftp.ascend.com for software upgrades, release notes, and addenda.
PAGE 4
support services provide hardware and software solutions to keep your network operating at peak performance. For more information, call (800) 272-3634. Other telephone numbers For a menu of Lucent’s services, call (800) 272-3634. Or call (510) 769-6001 for an operator.
PAGE 5
Contents Customer Service ..................................................................................................................... iii About This Guide ............................................................................ xvii What is in this guide.............................................................................................................. xvii What you should know .........................................................................................................
PAGE 6
Contents Configuring the APX 8000 for shelf-controller redundancy ................................................. 2-3 Assigning the system IP address..................................................................................... 2-4 Assigning an Ethernet IP address ................................................................................... 2-4 Examples of setting shelf-controller Ethernet IP address........................................
PAGE 7
Contents Chapter 6 Configuring MultiDSP Cards (MAX TNT, APX 8000)...................................................................... 6-1 Introduction to MultiDSP....................................................................................................... 6-1 48-port MultiDSP card.................................................................................................... 6-2 96-port MultiDSP card...........................................................................................
PAGE 8
Contents Specifying analog encoding for TAOS unit codecs............................................................. Configuring specialized options........................................................................................... Sample T1 configuration...................................................................................................... Default Call-Route profiles ..................................................................................................
PAGE 9
Contents Routing protocols.......................................................................................................... RADIUS........................................................................................................................ SNMP............................................................................................................................ Overview of E1 FrameLine configuration ...........................................................................
PAGE 10
Contents Chapter 15 Configuring OC3-ATM Cards (MAX TNT/DSLTNT)....................................................................... 15-1 Introduction to OC3-ATM ................................................................................................... Overview of OC3-ATM settings.......................................................................................... Using OC3-ATM ports as a clock source ............................................................................
PAGE 11
Contents Sample Frame Relay IDSL configuration .................................................................. Configuring the DSLTNT ................................................................................... Configuring the Pipeline...................................................................................... Sample ADSL nailed PPP connection ........................................................................ Configuring the ADSL profile............................................
PAGE 12
Contents Start and Stop records.......................................................................................... 18-21 Disconnect cause codes ....................................................................................... 18-21 SNMP support for SS7....................................................................................................... 18-23 Chapter 19 Configuring Call Routing .............................................................
PAGE 13
Figures Figure 13-1 Figure 14-1 Figure 15-1 Figure 16-1 Figure 17-1 Figure 17-2 Figure 17-3 Figure 17-4 Figure 17-5 Figure 17-6 Figure 18-1 Figure 18-2 Figure 19-1 Figure 19-2 Example of unchannelized DS3 slot card application ..................................... 13-1 DS3-ATM interface to ATM network ............................................................. 14-1 OC3-ATM interface to ATM network............................................................. 15-1 Example STM-0 configuration ..............
PAGE 14
PAGE 15
Tables Table 1-1 Table 5-1 Table 7-1 Table 9-1 Table 11-1 Table 11-2 Table 12-1 Table 12-2 Table 13-1 Table 17-1 Table 18-1 Table 19-1 Table A-1 Basic TAOS unit configuration tasks ................................................................ 1-2 Modem configuration tasks ............................................................................... 5-2 T1 line configuration tasks ................................................................................ 7-3 E1 line configuration tasks ..........
PAGE 16
PAGE 17
About This Guide What is in this guide This guide provides the following instructions for an APX 8000™, MAX TNT®, or DSLTNT™ multiservice access concentrator: ! • Basic configuration of your unit • Configuring shelf controller redundancy (APX 8000 only) • Configuring Ethernet and modem cards • Configuring T1, E1, DS3, and other network slot cards • Configuring the unit in a Signaling System 7 (SS7) network • Configuring call routing • Provisioning the switch Note: This manual describes the f
PAGE 18
Documentation conventions • Network security Documentation conventions Following are all the special characters and typographical conventions used in this manual: Convention Meaning Monospace text Represents text that appears on your computer’s screen, or that could appear on your computer’s screen. Boldface mono- Represents characters that you enter exactly as shown (unless the charspace text acters are also in italics—see Italics, below).
PAGE 19
Documentation set Documentation set The APX 8000/MAX TNT/DSLTNT documentation set consists of the following manuals. • • • Read me first: – Access Networks Safety and Compliance Guide Contains important safety instructions and country-specific compliance information that you must read before installing a TAOS unit. – TAOS Command-Line Interface Guide Introduces the TAOS command-line environment and shows how to use the command-line interface effectively.
PAGE 20
Documentation set xx • RADIUS: TAOS RADIUS Guide and Reference Describes how to set up a TAOS unit to use the Remote Authentication Dial-In User Service (RADIUS) server and contains a complete reference to RADIUS attributes. • Administration and troubleshooting: APX 8000/MAX TNT/DSLTNT Administration Guide Describes how to administer a TAOS unit, including how to monitor the system and cards, troubleshoot the unit, and configure the unit to use the Simple Network Management Protocol (SNMP).
PAGE 21
1 Performing Basic Configuration Introduction to basic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Connecting to a new unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Configuring the shelf-controller IP address on a nonredundant unit . . . . . . . . . . . . . . . 1-4 Setting the system date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 22
Performing Basic Configuration Introduction to basic configuration Table 1-1. Basic TAOS unit configuration tasks Section Description of task Related commands or parameters “Connecting to a new unit” on page 1-3 Connect the TAOS unit to a terminal or workstation and an Ethernet network. “Configuring the shelf-controller IP address on a nonredundant unit” on page 1-4 Specify the date and time for the TAOS unit system clock.
PAGE 23
Performing Basic Configuration Connecting to a new unit Connecting to a new unit To communicate with a new TAOS unit, you must assign an IP address to the shelf controller. Once this is done, you can perform further configuration over a LAN using Telnet. Use the following procedures to connect a new TAOS unit, if you have not already done so, and assign an Ethernet IP address.
PAGE 24
Performing Basic Configuration Configuring the shelf-controller IP address on a nonredundant unit 4 Verify that the connection and the IP address are correct by pinging any device on the network. admin> ping 10.10.10.1 64 bytes from 10.10.10.1: icmp_seq=0 ttl=255 time=0 ms 5 Exit the terminal or workstation. 6 Telnet to the MAX TNT or DSLTNT using a workstation on the LAN. The system will prompt you for a username and password. User: admin Password: Ascend 7 Complete the configuration.
PAGE 25
Performing Basic Configuration Setting the system date Setting the system date If the system date displayed on your screen is incorrect, set the correct date and time with the Date command. For example, to set the date and time to October 22, 2000, 8:50 in the morning: admin> date 0010220850 The format for setting the date and time is ymmddhhmm. Enter the hour in military (24-hour) time. Setting the system name You can assign the TAOS unit a system name of up to 24 characters.
PAGE 26
Performing Basic Configuration Configuring a default gateway To change the log level, specify an option for the Save-Level parameter: admin> set save-level = [none|emergency|alert|critical|error|warning|notice|info|debug] admin> write If your local network supports a Syslog server, you can configure the server’s IP address and the Syslog facility number by setting the Host and Facility parameters in this profile.
PAGE 27
Performing Basic Configuration Pinging the TAOS unit from a local host domain-name = "" dns-primary-server = 0.0.0.0 dns-secondary-server = 0.0.0.0 netbios-primary-ns = 0.0.0.0 netbios-secondary-ns = 0.0.0.0 must-accept-address-assign = no pool-base-address = [ 0.0.0.0 0.0.0.0 ] .. .. admin> set domain-name = abc.com admin> set dns-primary-server = 10.1.2.3 admin> set dns-secondary-server = 10.24.112.
PAGE 28
Performing Basic Configuration Recommended basic security measures Changing the Admin password A user who knows the password to the Admin level can perform any operation on the TAOS unit, including changing the configuration. The Admin password is set to Ascend by default. Lucent recommends that you assign a secret password immediately to prevent unauthorized users from gaining access to the unit by means of the default password.
PAGE 29
Performing Basic Configuration Recommended basic security measures Following is an example of assigning a Telnet password: admin> read ip-global IP-GLOBAL read admin> set telnet-password = SDwiw87 admin> write IP-GLOBAL written All users attempting to access the TAOS unit unit via Telnet are prompted for the Telnet password. They are allowed three tries, each with a 60-second time limit, to enter the correct password. If all three tries fail, the connection attempt times out.
PAGE 30
Performing Basic Configuration Recommended basic security measures To prevent the TAOS unit router from being used as an intermediary in this type of denial-of-service attack launched from another network, you must disable the TAOS unit from forwarding the directed broadcasts it receives from another network.
PAGE 31
Performing Basic Configuration Recommended basic security measures Following are the parameters related to SNMP security: SNMP enabled = no read-community = public read-write-community = write enforce-address-security = no read-access-hosts = [ 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 ] write-access-hosts = [ 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.
PAGE 32
Performing Basic Configuration Where to go next In the following example, commands enforce address security and specify a trusted address for read and write access: admin> read snmp SNMP read admin> list enabled = no read-community = public read-write-community = write enforce-address-security = no read-access-hosts = [ 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 ] write-access-hosts = [ 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.
PAGE 33
Configuring Shelf-Controller Redundancy (APX 8000) 2 Overview of redundancy operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Configuring the APX 8000 for shelf-controller redundancy . . . . . . . . . . . . . . . . . . . . . 2-3 Obtaining status information about redundant shelf controllers . . . . . . . . . . . . . . . . . . 2-9 Overview of redundancy operations The APX 8000 can operate with a single shelf controller or with two redundant shelf controllers.
PAGE 34
Configuring Shelf-Controller Redundancy (APX 8000) Overview of redundancy operations The controllers next elect the controller that will be primary. The election process is based on a hierarchical list of complex criteria. The first criterion in the list is evaluated and if the criterion is found to be true, one of the controllers is made primary. If the criterion is found to be false, the next criterion in the list is evaluated.
PAGE 35
Configuring Shelf-Controller Redundancy (APX 8000) Configuring the APX 8000 for shelf-controller redundancy Controller switchover If the primary controller fatals, the secondary controller automatically takes over as primary controller. The new primary (old secondary) downs all slot cards and then brings the system back up. All connections are dropped. After the primary shelf controller comes up, the slot cards are reset. The system is now ready to take new calls.
PAGE 36
Configuring Shelf-Controller Redundancy (APX 8000) Configuring the APX 8000 for shelf-controller redundancy Assigning the system IP address To configure an APX 8000 that has redundant shelf controllers, you must map system IP settings to the unit’s soft IP interface. The soft IP interface is associated with the shelf controller that is currently primary. Set the IP-Global profile’s System-IP-Addr parameter to the address of the soft IP interface.
PAGE 37
Configuring Shelf-Controller Redundancy (APX 8000) Configuring the APX 8000 for shelf-controller redundancy admin> set ip-address = 192.168.100.2/24 admin> write IP-INTERFACE/{ { shelf-1 right-controller 1 } 0 } written After you assign IP addresses to the controllers, you can verify that the TAOS unit is a valid IP host on its configured networks by pinging other hosts on those networks, as shown in the following example: admin> ping 192.168.100.56 PING 192.168.100.56: 56 Data bytes 64 bytes from 192.168.
PAGE 38
Configuring Shelf-Controller Redundancy (APX 8000) Configuring the APX 8000 for shelf-controller redundancy Configuring shelf-controller redundancy When setting up shelf-controller redundancy, you might need to configure the following profiles: • Physical interface profiles (such as IP-Interface, Serial, Ethernet, Ether-Info) • Redundancy profile Note: Lucent recommends that you modify profiles on the primary controller only. Modified profiles are sent to the secondary controller.
PAGE 39
Configuring Shelf-Controller Redundancy (APX 8000) Configuring the APX 8000 for shelf-controller redundancy admin> read redundancy REDUNDANCY read admin> list [in REDUNDANCY] context = [ { } { } ] primary-preference = no-preference The following example shows how you can configure the Primary-Preference parameter to indicate a preference for the controller in the right shelf-controller slot to be elected primary: admin> read redundancy REDUNDANCY read admin> set primary-preference = right-controller-prefer
PAGE 40
Configuring Shelf-Controller Redundancy (APX 8000) Configuring the APX 8000 for shelf-controller redundancy Switching the primary controller at the command-line interface You can manually switch primary shelf-controller functionality to the secondary controller by entering the command redundant-controller-switch at the command-line interface. This command causes the primary controller to give up bus (slot card) ownership and allow the other controller to become primary.
PAGE 41
Configuring Shelf-Controller Redundancy (APX 8000) Obtaining status information about redundant shelf controllers the default security level is reactivated. In addition, a system reset can cause a WAN line to temporarily be shut down due to momentary loss of signaling or framing information. After a reset, the unit runs power-on self-tests (POST). The reset -r command resets the secondary controller or both controllers. The reset -f command resets the controller where the command is invoked.
PAGE 42
Configuring Shelf-Controller Redundancy (APX 8000) Obtaining status information about redundant shelf controllers disrupted and then reestablished, the uptime command reports the time elapsed since the secondary controller reestablished communications with the primary. The uptime command does not report the version number of code used by the controllers, but instead reports the primary or secondary status of each controller. The code version is obtained with the version command.
PAGE 43
Configuring Shelf-Controller Redundancy (APX 8000) Obtaining status information about redundant shelf controllers The following example displays the show command entered on the secondary controller when the right controller is primary: admin> show Controller { left-controller } ( SECONDARY ): { right-controller ) UP ( PRIMARY ) Setting up a trap to monitor the secondary controller In the Trap profile, you can configure the Secondary-Controller-State-Change-Enabled parameter to send a trap to the NavisAcces
PAGE 44
PAGE 45
Configuring the Thermal Profile for Fan Tray Operations (APX 8000) 3 Overview of the Thermal profile for fan tray operations. . . . . . . . . . . . . . . . . . . . . . . . 3-1 Thermal status reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 46
Configuring the Thermal Profile for Fan Tray Operations (APX 8000) Overview of the Thermal profile for fan tray operations Parameter Specifies Operation-Mode Mode of operation in which the fan tray runs. When the parameter is set to full-speed-only, the fans in the fan tray operate at full speed at all times. (This is the default mode.) When set to lownoise-speed-only, the fans operate at the low noise speed (as specified in the Fantray-Lownoise-RPM setting) at all times.
PAGE 47
Configuring the Thermal Profile for Fan Tray Operations (APX 8000) Overview of the Thermal profile for fan tray operations admin> write THERMAL written admin> list [in THERMAL] fantray-lownoise-rpm = 2500 operation-mode = auto-regulation low-temperature-trigger = 30 high-temperature-trigger = 37 alarm-temperature-trigger = 50 Related log messages When the fan tray is in auto-regulation mode, the system can generate the following Info log messages to indicate that the system has switched the fans from low n
PAGE 48
Configuring the Thermal Profile for Fan Tray Operations (APX 8000) Thermal status reporting Thermal status reporting A power-on self test (POST) is run on the fan tray of the APX 8000 during the BOOT loader and during the operational load.
PAGE 49
Configuring the Thermal Profile for Fan Tray Operations (APX 8000) Thermal status reporting Thermalstatus command The thermalstatus command displays a number of temperature-related values to show the overall thermal status of the unit. For example, it displays: • Ambient temperature at fan tray intake. • Shelf controller temperature. • High, Low, and Alarm temperature thresholds. • Slot card temperature for slot cards that support temperature reporting.
PAGE 50
PAGE 51
4 Configuring Ethernet Cards Introduction to Ethernet slot cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Overview of Ethernet configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Understanding the Ethernet-related profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Configuring duplex mode on the 100Mbps Ethernet port . . . . . . . . . . . . . . . . . . . . . . .
PAGE 52
Configuring Ethernet Cards Overview of Ethernet configuration Upgrading to the Ethernet-2 and Ethernet-3 slot cards To upgrade from an existing 10Mbps or 10/100Mbps Ethernet card to an Ethernet-2 or Ethernet-3 slot card, proceed as in the following example: 1 Remove the existing Ethernet slot card. 2 Enter the Slot command with the -r option to remove the existing Ethernet profiles.
PAGE 53
Configuring Ethernet Cards Configuring duplex mode on the 100Mbps Ethernet port 5 5 08/06/1998 17:11:46 08/06/1998 17:11:46 { shelf-2 slot-4 3 } { shelf-2 slot-4 4 } If the 10/100 Mbps Ethernet-2 card is installed, the 100Mbps Ethernet port is displayed as port 4. IP-Interface profile TAOS creates a default IP-Interface profile for each Ethernet port it detects, including the shelf controller.
PAGE 54
PAGE 55
5 Configuring Series56 II and III Modem and Hybrid Access Cards Overview of configuring modem cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Specifying modem negotiation settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Specifying modem modulation for Series56 II and III modem cards . . . . . . . . . . . . . . 5-3 Configuring an additional AT answer string for modem calls . . . . . . . . . . . . . . . . . . . .
PAGE 56
Configuring Series56 II and III Modem and Hybrid Access Cards Specifying modem negotiation settings Table 5-1. Modem configuration tasks Description of task Section Associated parameters Some analog modem calls might require changes to the digital modem’s default behavior to successfully complete negotiation.
PAGE 57
Configuring Series56 II and III Modem and Hybrid Access Cards Specifying modem modulation for Series56 II and III modem cards 2 List the parameters in the Modem-Configuration subprofile. For example: admin> list modem-configuration v42/mnp = will-v42 max-baud-rate = 33600-max-baud modem-transmit-level = -13-db-mdm-trn-level cell-mode-first = no cell-level = -18-db-cell-level 7-even = no 3 Modify the parameters as required. For information about the parameters, see the APX 8000/MAX TNT/DSLTNT Reference.
PAGE 58
Configuring Series56 II and III Modem and Hybrid Access Cards Series56 II and III Call-Route profiles rate and the AT-Answer-String parameter specifies a different baud rate, the answer string overwrites the configured maximum baud rate. Following is the relevant parameter, which is shown with its default setting: [in TERMINAL-SERVER:modem-configuration] AT-answer-string = "" The value of this parameter must be valid AT commands, up to 36 characters. Do not begin the string with AT.
PAGE 59
Configuring Series56 II and III Modem and Hybrid Access Cards Preventing Series56 II and III cards from delaying Frame Relay connections Preventing Series56 II and III cards from delaying Frame Relay connections If the APX 8000 or MAX TNT has a Frame Relay datalink that uses a single nailed channel, you must install Series56 II or Series56 III slot cards in lower-numbered slots than the Hybrid Access (HDLC) slot cards, or dedicate the Series56 cards to modem processing by deleting the Digital Call-Type pro
PAGE 60
PAGE 61
6 Configuring MultiDSP Cards (MAX TNT, APX 8000) Introduction to MultiDSP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Supported MultiDSP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Obtaining status information about a MultiDSP card . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Configuring a MultiDSP card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 62
Configuring MultiDSP Cards (MAX TNT, APX 8000) Introduction to MultiDSP 48-port MultiDSP card The 48-port MultiDSP card supports up to 48 ports of service. Note: In MAX TNT and APX 8000 profiles and parameters, the 48-port MultiDSP card is identified as madd or madd-card. For a MAX TNT or APX 8000 unit with a 48-port MultiDSP card, Lucent recommends that you limit the number of enabled MultiDSP services to two. Voice over IP (VoIP) is currently supported on the MAX TNT only.
PAGE 63
Configuring MultiDSP Cards (MAX TNT, APX 8000) Supported MultiDSP services Card configuration constraints The following constraints affect the mixing of slot cards in MAX TNT and APX 8000 units. Using 48-port and 96-port MultiDSP cards You cannot mix 48-port and 96-port MultiDSP cards in the same MAX TNT or APX 8000 unit. However, you can use multiple 48-port or multiple 96-port MultiDSP in the same unit.
PAGE 64
Configuring MultiDSP Cards (MAX TNT, APX 8000) Supported MultiDSP services V.110 features supported by the MultiDSP card include the following: • Asynchronous, answer-mode only (answer, but no call out), with 1 start bit, 8 data bits, and 1 stop bit. • Rate-adaptive mode. Supported rates are 2400bps, 4800bps, 9600bps (default), 19200bps and 38400bps. PHS The Personal Handyphone System (PHS) provides mobile telephone access to users located in Japan and other Asian countries.
PAGE 65
Configuring MultiDSP Cards (MAX TNT, APX 8000) Obtaining status information about a MultiDSP card A VoIP software license is required for MultiDSP support of the VoIP service. An additional software license is required for support of real-time fax functionality. VoIP functionalities, including real-time fax, are configured through the MAX TNT VoIP profile. For details about VoIP and MultiVoice configuration, refer to the MultiVoice for MAX TNT Configuration Guide.
PAGE 66
Configuring MultiDSP Cards (MAX TNT, APX 8000) Configuring a MultiDSP card For example, enter the following command to display information about a 96-port MultiDSP card (identified as madd2-card) installed in shelf 1, slot 10 of a MAX TNT unit: admin> show 1 10 { shelf-1 { shelf-1 { shelf-1 { shelf-1 ...
PAGE 67
Configuring MultiDSP Cards (MAX TNT, APX 8000) Configuring a MultiDSP card • Verifying that all other configurations associated with the MultiDSP services have been performed. For example, for VoIP MultiDSP support, all required configurations for VoIP, real-time fax (optional), and other desired MultiVoice features must also be performed. • Adding support for an additional MultiDSP service, if necessary.
PAGE 68
Configuring MultiDSP Cards (MAX TNT, APX 8000) Configuring a MultiDSP card ... phs-support = yes ... voip-enabled = no ... v110-enabled = disabled ... rtfax-enabled = no ... Verifying call routes for MultiDSP services You can verify call routes for enabled MultiDSP services by viewing the Call-Route profiles and the call route entries. Procedures for viewing the Call-Route profiles and entries are described in this section.
PAGE 69
Configuring MultiDSP Cards (MAX TNT, APX 8000) Configuring a MultiDSP card Call-Route profile entry field number Associated MultiDSP service type 1 Digital 2 PHS 3 VoIP 4 V.110 The following example shows a Call-Route profile for the VoIP service (entry is 3) on a 48-port MultiDSP card installed in slot 5: 33 12/10/1999 18:25:32 {{{shelf-1 slot-5 0} 0} 3} About the Call-Route-Type parameter Each Call-Route profile contains the Call-Route-Type parameters specific to that profile.
PAGE 70
Configuring MultiDSP Cards (MAX TNT, APX 8000) Configuring a MultiDSP card Viewing call-routing database entries Unlike the Call Route profiles, entries in a call-routing database are created for the analog modem service, digital service, and for each licensed MultiDSP service. When a card comes up, the MAX TNT or APX 8000 unit creates a call-routing database. The number of database entries created per service depend on the following: • Type (48-port or 96-port) of MultiDSP card being used.
PAGE 71
Configuring MultiDSP Cards (MAX TNT, APX 8000) Configuring a MultiDSP card admin> slot -r 1 5 admin> slot -u When the MultiDSP cards are brought up, the unit creates new profiles and call route entries for each service, including the new service.
PAGE 72
PAGE 73
Configuring T1 Cards 7 Introduction to T1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Overview of T1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Making a profile the working profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Assigning names to T1 line profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 74
Configuring T1 Cards Introduction to T1 Introduction to T1 A T1 line consists of 24 channels. Each channel can transmit and receive data or digitized voice. The line uses framing and signaling to achieve synchronous and reliable transmission. The most common configurations for T1 lines are ISDN Primary Rate Interface (PRI) and nailed (leased) or unchannelized T1, including fractional T1. (For information about provisioning your T1 line for use with the TAOS unit, see Appendix A, “Provisioning the Switch.
PAGE 75
Configuring T1 Cards Overview of T1 configuration Overview of T1 configuration Table 7-1 lists the sections describing common tasks you might have to perform to configure a T1 line. The table includes a brief description of each task and lists the parameters you will use. For information about administering the T1 card, including such tasks as specifying a facilities data link (FDL) and displaying the status of the lines, see the APX 8000/MAX TNT/DSLTNT Administration Guide.
PAGE 76
Configuring T1 Cards Overview of T1 configuration Table 7-1. T1 line configuration tasks (continued) Section Description of task Associated parameters “Configuring inband robbed-bit signaling” on page 7-11 If the lines use inband signaling, change the signaling mode to robbed bit and specify the type of robbed bit signaling to use.
PAGE 77
Configuring T1 Cards Overview of T1 configuration Table 7-1. T1 line configuration tasks (continued) Section Description of task Associated parameters “Configuring nailed channels” on page 7-21 You must assign a nailed channel to a group to make it available for use. The group number can be referred to in a Connection or Frame-Relay profile to specify a permanent leased connection using that group of nailed channels.
PAGE 78
Configuring T1 Cards Making a profile the working profile Making a profile the working profile When the TAOS unit detects that a T1 card has been installed, it creates a default T1 profile for each of the eight lines on the card.
PAGE 79
Configuring T1 Cards Assigning names to T1 line profiles nfas-group-id = 0 nfas-id = 0 incoming-call-handling = internal-processing call-by-call = 0 data-sense = normal idle-mode = flag-idle FDL = none front-end-type = dsx DSX-line-length = 1-133 CSU-build-out = 0-db overlap-receiving = no pri-prefix-number = "" trailing-digits = 2 t302-timer = 10000 channel-config = [ { unused-channel 9 "" { any-shelf any-slot + maintenance-state = no input-sample-count = one-sample sendDisc-val = 0 hunt-grp-phone-number-1
PAGE 80
Configuring T1 Cards Enabling a line Enabling a line By default each T1 line is disabled. To enable the T1 line, read its profile to make it the working profile, then set the Line Interface subprofile’s Enabled parameter to Yes, as in the following example: admin> read t1 {1 2 1} T1/{ shelf-1 slot-2 1 } read admin> set line enabled = yes admin> write T1/{ shelf-1 slot-2 1 } written Specifying the framing and encoding You must specify the framing and the encoding for each T1 line.
PAGE 81
Configuring T1 Cards Configuring ISDN network-side emulation admin> set line switch-type = switchtype admin> set line channel 24 channel-usage=d-channel admin> write T1/{ shelf-1 slot-2 1} written To see a complete list of switch types supported on the TAOS unit, refer to the TAOS unit online help or the APX 8000/MAX TNT/DSLTNT Reference. Configuring ISDN network-side emulation You can configure PRI lines to use either network-side or user-side ISDN emulation.
PAGE 82
Configuring T1 Cards Configuring overlap receiving on PRI lines trailing-digits = 2 t302-timer = 10000 [in E1/{ shelf-1 slot-12 1 }:line-interface] signaling-mode = isdn overlap-receiving = yes pri-prefix-number = 3069 trailing-digits = 2 t302-timer = 10000 To configure overlap receiving, you need to set some or all of the following parameters: Parameter Specifies Signaling-Mode Type of signaling on the T1 or E1 line. It must specify ISDN (or ISDN-NFAS, for T1) to use overlap receiving.
PAGE 83
Configuring T1 Cards Configuring inband robbed-bit signaling Parameter Specifies T302-Timer Number of milliseconds that the system waits for additional called number information for an incoming call. The valid range is from 100 to 30000 (.10 second and 30 seconds). The default is 10000 (0.10 seconds).
PAGE 84
Configuring T1 Cards Configuring inband robbed-bit signaling accounting. (On lines configured for PRI signaling, this information is presented as part of the call setup message and does not require special configuration on the TAOS unit.) To configure the TAOS unit to process the DTMF digits in a call, use the Collect-Incoming-Digits and DSP-DTMF-Input-Sample-Count parameters in a T1 profile. The Collect-Incoming-Digits parameter enables the TAOS unit to process the DTMF digits in a call.
PAGE 85
Configuring T1 Cards Configuring NFAS Configuring NFAS A group of T1 lines configured for NFAS signaling shares a D channel. One line in the group is configured with a primary D channel, and another line is configured with a secondary D channel. The secondary D channel is used only if the primary line fails or receives a signal commanding a change to the other D channel. All lines within an NFAS group must reside on the same slot card.
PAGE 86
Configuring T1 Cards Configuring NFAS admin> read t1 {1 2 1} T1/{ shelf-1 slot-2 1 } read admin> set line signaling-mode = isdn-nfas admin> set line nfas-id = 0 admin> set line nfas-group-id = 1 admin> set channel 24 channel = nfas-primary admin> write T1/{ shelf-1 slot-2 1 } written admin> read t1 {1 2 2} T1/{ shelf-1 slot-2 2 } read admin> set line signaling-mode = isdn-nfas admin> set line nfas-id = 1 admin> set line nfas-group-id = 1 admin> set line channel 24 channel = nfas-secondary admin> write T1/{
PAGE 87
Configuring T1 Cards Configuring T1 R1 and R1-Modified (Taiwan) with ANI and called-number processing admin> write T1/{ shelf-1 slot-2 6 } written admin> read t1 {1 2 7} T1/{ shelf-1 slot-2 7 } read admin> set line signaling-mode = isdn-nfas admin> set line nfas-id = 2 admin> set line nfas-group-id = 2 admin> write T1/{ shelf-1 slot-2 7 } written admin> read t1 {1 2 8} T1/{ shelf-1 slot-2 8 } read admin> set line signaling-mode = isdn-nfas admin> set line nfas-id = 3 admin> set line nfas-group-id = 2 admin>
PAGE 88
Configuring T1 Cards Configuring T1 R1 and R1-Modified (Taiwan) with ANI and called-number processing the switch, you can also specify how long it waits before sending the request, and how long the ANIR signal lasts. The following parameters enable R1 signaling on T1 lines and specify the timing of certain signals from the switch.
PAGE 89
Configuring T1 Cards Configuring clocking Configuring clocking You can configure the TAOS unit to use any of the T1 lines as a master phase-locked loop (PLL) clock source for synchronous connections for an entire system. In synchronous transmission, both the sending device and the receiving device must maintain synchronization to determine where one block of data ends and the next begins. From the T1 lines configured as eligible clock sources, the TAOS unit chooses a clock source on the basis of priority.
PAGE 90
Configuring T1 Cards Configuring channel usage To specify CSU settings, proceed as in the following example after reading in the line’s T1 profile: admin> set front-end-type = csu admin> set csu-build-out = 7.5-db admin> write Configuring channel usage You must specify how each of the 24 channels of a T1 line is to be used. By default, T1 channels are configured as switched. (If you are going to set up the lines for NFAS, see “Configuring NFAS” on page 7-13 for additional channel-configuration information.
PAGE 91
Configuring T1 Cards Assigning telephone numbers to switched channels Assigning telephone numbers to switched channels Channel assignments typically specify add-on numbers, not full telephone numbers. Add-on numbers include only the rightmost digits needed to distinguish one number from another. For example, if a line is assigned 23 numbers, all of which begin with 212-555-, the add-on number is the unique set of digits to the right of these common digits.
PAGE 92
Configuring T1 Cards Configuring trunk groups admin> set 13 phone = 72 admin> write Configuring trunk groups Like nailed channels that have been assigned a group number, switched channels in a trunk group can be referred to from a Connection profile and Call-Route profile to direct outbound calls to use that specific bandwidth.
PAGE 93
Configuring T1 Cards Configuring nailed channels phone-number = "" call-route-info = { any-shelf any-slot 0 } nailed-group = 0 admin> set trunk-group = 4 admin> write Note: Command history is very useful for repeating commands. Press the Up-Arrow to redisplay the command, and then press Enter. (For more information, see the TAOS Command-Line Interface Guide.) Configuring nailed channels The number of nailed (leased) channels must be the same at both ends of the connection.
PAGE 94
Configuring T1 Cards Specifying analog encoding for TAOS unit codecs • Clock-Source set to Eligible (the default) In T1 profile for the other end of the line, specify the following values: • Signaling-Mode set to Inband (the default) • Robbed-Bit-Mode set to Inc-W-200 or Inc-W-400 • Clock-Source set to Eligible (the default) Connect the two ports with a T1-crossover cable. You can now configure Connection profiles between the units and dial over the connection as you would over the WAN.
PAGE 95
Configuring T1 Cards Sample T1 configuration Sample T1 configuration This section provides an example of how to configure a T1 slot card. The example uses the following setup: • The card is in shelf 1, slot 2. • All lines use PRI signaling. • Switch type is NTI-PRI. • The line is connected to a DSX and is less than 100 feet (30.5m) long. It therefore uses the default settings for Front-End-Type and DSX-Line-Length.
PAGE 96
Configuring T1 Cards Default Call-Route profiles 4 Enable the line: admin> set enabled = yes 5 Set the frame type: admin> set frame-type = est 6 Set the line encoding: admin> set encoding = b8zs 7 Set the signaling mode: admin> set signaling-mode = isdn 8 Set the switch type: admin> set switch-type = nti-pri 9 Next, assign all the channels to trunk group 7: admin> set channel 1 truck-group = 7 10 Press the Up-Arrow key or Ctrl-P to redisplay the Set command you just entered.
PAGE 97
8 Configuring T1 FrameLine Cards (MAX TNT, DSLTNT) Introduction to T1 FrameLine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Overview of supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Overview of T1 FrameLine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Configuring the clock source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 98
Configuring T1 FrameLine Cards (MAX TNT, DSLTNT) Overview of T1 FrameLine configuration • Multilink Protocol (MP) and Multilink Protocol Plus (MP+) are not supported. The connection profile must specify only PPP. • Users are authenticated by the local profile or RADIUS. • Stac compression is not supported. Frame Relay The T1 FrameLine slot card supports Frame Relay as follows: • Only one Frame Relay link, possibly containing multiple data-link connection identifiers (DLCIs), can be active per line.
PAGE 99
Configuring T1 FrameLine Cards (MAX TNT, DSLTNT) Configuring the clock source – Call-by-Call – Channel-Usage – Default-Call-Type – Data Sense – FDL – Idle-Mode – Maintenance-State – NFAS-ID – Robbed-Bit-Mode – SendDisc-Val – Switch-Type For information about configuring T1 profiles, see Chapter 7, “Configuring T1 Cards.
PAGE 100
PAGE 101
Configuring E1 Cards 9 Introduction to E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Overview of E1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Understanding configuration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Making a profile the working profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 102
Configuring E1 Cards Introduction to E1 Introduction to E1 An E1 line supports 32 64Kbps channels, each of which can be used to transmit and receive data or digitized voice. The line uses framing and signaling to achieve synchronous and reliable transmission. The most common configurations for E1 lines are PRI and unchannelized. (For information about provisioning your E1 line for use with the TAOS unit, see Appendix A, “Provisioning the Switch.
PAGE 103
Configuring E1 Cards Overview of E1 configuration Table 9-1. E1 line configuration tasks (continued) Section Description of task Associated parameters “Configuring a back-to-back connection” on page 9-7 A back-to-back connection lets you connect two TAOS units to one another over a crossover E1 cable. Back-to-Back “Specifying the framing” on page 9-7 Framing specifies how the bits are sent on the line.
PAGE 104
Configuring E1 Cards Understanding configuration requirements Table 9-1. E1 line configuration tasks (continued) Section Description of task Associated parameters “Configuring the front-end E1 transceiver” on page 9-13 Set the front end type of the E1 transceiver to Long-Haul or Short-Haul, depending on the type of termination your line uses. Front-End-Type “Configuring channel usage” on page 9-14 Specify how each of the E1 channels is to be used.
PAGE 105
Configuring E1 Cards Making a profile the working profile • Rate adaption protocol—DASS 2 and DPNSS only (X.30 and V.110) Note: The TAOS unit cannot receive multichannel calls using Multilink Protocol (MP) encapsulation unless all channels of the call share a common telephone number (namely, a hunt group). You can request that your service provider supply you with a hunt group.
PAGE 106
Configuring E1 Cards Assigning names to E1 line profiles line-interface = { no none g703 eligible middle-priority + back-to-back = false [in E1/{ shelf-1 slot-15 5 }:line-interface] enabled = yes t-online-type = none frame-type = g703 clock-source = eligible clock-priority = middle-priority signaling-mode = isdn default-call-type = digital switch-type = net5-pri incoming-call-handling = reject-all front-end-type = short-haul overlap-receiving = no pri-prefix-number = "" trailing-digits = 2 t302-timer = 1000
PAGE 107
Configuring E1 Cards Enabling a line admin> read e1 {1 12 0} admin> set name = E1 Trunk admin> write E1/{ shelf-1 slot-12 0 } written admin> dir e1 17 04/17/1997 19:00:02 { shelf-1 slot-12 0 } "E1 Trunk" For E1 lines, the Line Status window displays either the name (if assigned) or the physical address. If the name is longer than eight characters, the last character displayed is a plus sign (+). Enabling a line By default each E1 line is disabled.
PAGE 108
Configuring E1 Cards Specifying E1 signaling admin> set line frame-type = [G703|2DS|D4|esf] admin> write E1/{ shelf-1 slot-2 1 } written Specifying E1 signaling An E1 line’s signaling mode can be any of the following: • ISDN • DPNSS (DPNSS or DASS 2 signaling) • Channel-associated signaling (CAS).
PAGE 109
Configuring E1 Cards Configuring ISDN network-side emulation Configure ISDN PRI service as in the following example: admin>read e1 {1 15 5} E1/{ shelf-1 slot-15 5 } read admin>list [in E1/{ shelf-1 slot-15 5 }] name = "" physical-address* = { shelf-1 slot-15 5 } line-interface = { no none g703 eligible middle-priority isdn + back-to-back = false admin>list line-interface [in E1/{ shelf-1 slot-15 5 }:line-interface] enabled = no t-online-type = none frame-type = g703 clock-source = eligible clock-priority =
PAGE 110
Configuring E1 Cards Configuring E1 R1 signaling ISDN emulation enables you to build, send, receive, and process ISDN data. ISDN monitoring, on the other hand, allows you only to decode the ISDN data. Configuring E1 R1 signaling R1 is a multifrequency inband signaling protocol that uses a set of register signals known as MFR1 tones as addressing signals. Each address (telephone number) is preceded by a KP pulse and followed by an ST pulse denoting the end of addressing.
PAGE 111
Configuring E1 Cards Configuring E1 R2 signaling Parameter Specifies Number-Complete Number of digits considered to be a complete number on an incoming call using R2 signaling. You can specify End-of-Pulsing to have the TAOS unit continue receiving digits until the caller stops sending them, or you can specify a fixed number of digits (up to 10). In all cases, the digits received before the call is answered are considered the called number for call-routing purposes.
PAGE 112
Configuring E1 Cards Configuring DPNSS signaling admin> list line enabled=no frame-type=g703 clock-source=eligible clock-priority=middle-priority signaling-mode=isdn switch-type=net5-pri front-end-type=short-haul channel-config=[ { unused-channel 9 "" { any-shelf any-slot+ .. ..
PAGE 113
Configuring E1 Cards Configuring overlap receiving on PRI lines admin> set loop-avoidance = 7 admin> write Configuring overlap receiving on PRI lines Overlap receiving affects the procedure of establishing an incoming call received on a T1 or E1 PRI line in the TAOS unit. With overlap receiving, the TAOS unit can gather the complete called number from the network switch via a series of Information messages, enabling the use of features such as called-number authentication.
PAGE 114
Configuring E1 Cards Configuring channel usage Configuring channel usage You must specify how each of the 32 channels of an E1 line is to be used. By default, E1 channels are configured as switched. Each of the 32 channels of an E1 line can be configured for one of the following uses: • Unused-Channel—Channel is unused. Send the single idle code defined for this channel.
PAGE 115
Configuring E1 Cards Configuring nailed channels idle-logout = 0 parallel-dialing = 2 single-file-incoming = yes analog-encoding = a-law sessionid-base = 0 admin> set use-trunk-groups = yes admin> write Then assign the channels of each E1 line to a trunk group, as in the following example: admin> read e1 {1 1 1} E1/{ shelf-1 slot-1 1 } read admin> list line channel 1 [in E1/{ shelf-1 slot-15 1 }:line-interface:channel-con +] channel-usage = switched-channel trunk-group = 9 phone-number = "" call-route-info
PAGE 116
Configuring E1 Cards Specifying analog encoding for TAOS unit codecs When you configure Connection profiles to use the leased connection, you must specify the Nailed-Group number in the Telco-Options subprofile. To configure a nailed channel, proceed as in the following example: admin> list line channel 1 channel-usage = switched-channel trunk-group = 9 phone-number = "" call-route-info = { any-shelf any-slot 0 } nailed-group = 0 admin> set channel = nailed admin> set nailed = 3 admin> list ..
PAGE 117
Configuring E1 Cards Default Call-Route profiles This default Call-Route profile routes outbound trunk calls to any line on the card. To handle inbound modem and LAN-session traffic, you must configure specific call routes. For details, see Chapter 19, “Configuring Call Routing.
PAGE 118
PAGE 119
Configuring E1 FrameLine Cards (MAX TNT, DSLTNT) 10 Introduction to E1 FrameLine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Overview of supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Overview of E1 FrameLine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2 Administrative profiles for E1 FrameLine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 120
Configuring E1 FrameLine Cards (MAX TNT, DSLTNT) Overview of E1 FrameLine configuration PPP The E1 FrameLine slot card supports PPP as follows: • Only one PPP session per line. • Bandwidth per session is 1-31 DS0 channels. Channel 1 is not available. • Channels need not be contiguous. • Multilink Protocol (MP) and Multilink Protocol Plus (MP+) are not supported. The connection profile must specify only PPP. • Users are authenticated by the local profile or RADIUS.
PAGE 121
Configuring E1 FrameLine Cards (MAX TNT, DSLTNT) Overview of E1 FrameLine configuration • Channel-Usage for channel must be set to Unused-Channel. • For all other channels, Channel-Usage must be set to either Unused-Channel or Nailed-64-Channel. • Channel 17 is usable. • You cannot have the same nailed group on two different E1 lines. • Unlike the E1 card, channels in the same nailed group do not need to be contiguous. For example, channels 1 and 3 can be in same nailed group with channel 2 unused.
PAGE 122
Configuring E1 FrameLine Cards (MAX TNT, DSLTNT) Administrative profiles for E1 FrameLine hunt-grp-phone-number-2 = "" hunt-grp-phone-number-3 = "" To configure the E1 FrameLine card: admin> read E1 {1 2 2} UE1/{ shelf-1 slot-2 2 } read admin> set enabled = yes admin> list channel 1 channel-usage = unused-channel trunk-group = 9 phone-number = ““ call-route-info = { any-shelf any-slot 0 } nailed-group = 0 admin> set channel-usage = nailed-64-channel admin> set nailed-group = 3 admin> list ..
PAGE 123
Configuring E1 FrameLine Cards (MAX TNT, DSLTNT) Administrative commands and status information Admin-State profile When you install the E1 FrameLine slot card, the MAX TNT or DSLTNT creates 20 Admin-State profiles; 10 are associated with the E1 lines and 10 are associated with the SCA devices that do HDLC framing. Profiles are retained during card resets. The unit deletes these profiles if you install a different type of card into a slot.
PAGE 124
Configuring E1 FrameLine Cards (MAX TNT, DSLTNT) Configuring the clock source Configuring the clock source The E1 FrameLine slot card uses the same system-wide PLL synchronous clock source for DS1 transmission as do the eight-port T1 and E1 cards. Any of the lines can serve as the clock source for the unit. To configure the E1 FrameLine card’s clock source, use the same parameters (Clock-Source and Clock-Priority) that you use for other cards. All 10 lines must use the same clock source.
PAGE 125
Configuring T3 Cards 11 Introduction to T3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 Overview of T3 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1 Understanding T3 configuration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2 Understanding T3 slot card profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 126
Configuring T3 Cards Understanding T3 configuration requirements For complete information about the associated parameters, see the APX 8000/MAX TNT/DSLTNT Reference. Table 11-1. T3 line configuration tasks Section Description of task Associated parameters “Understanding T3 configuration requirements” on page 11-2 Although you configure the T3 card similarly to the eight-port T1 card, there are important differences you must understand before configuring the card.
PAGE 127
Configuring T3 Cards Understanding T3 slot card profiles Table 11-2. Differences between T3 card configuration and T1 card configuration (continued) Parameter Difference FDL The DS1-level FDL services supported by the T3 card are the same as for the eight-port T1 card. DS3-level FDL capabilities such as the Far-End Alarm and Control Channel (FEAC) and Path Maintenance Data Link are currently unsupported. (For information on specifying FDL, see the APX 8000/MAX TNT/DSLTNT Adminstration Guide.
PAGE 128
Configuring T3 Cards Assigning a name to a T3 profile 13 13 13 13 13 02/28/1997 02/28/1997 02/28/1997 02/28/1997 03/21/1997 10:54:49 10:54:49 10:54:49 10:54:49 10:18:40 { { { { { { { { { { { { { { { shelf-1 shelf-1 shelf-1 shelf-1 shelf-1 slot-8 0 } 0 } 0 } slot-11 0 } 0 } 0 } slot-16 0 } 0 } 0 } slot-13 0 } 0 } 0 } slot-7 0 } 0 } 0 } T1 profiles The TAOS unit also creates 28 T1 profiles for the T3 interface. You use these profiles to configure parameters for each of the DS1s that make up the T3.
PAGE 129
Configuring T3 Cards Enabling a line admin> read t3 {1 12 0} admin> set name = T3 Trunk admin> write T3/{ shelf-1 slot-12 0 } written admin> dir T3 17 04/17/1997 19:00:02 { shelf-1 slot-12 0 } "T3 Trunk" For T3 lines, the Line Status window displays the first eight characters of the name if one has been assigned. For example: "T3 Trunk" 1/15/00 LA la la la la la la la If the name is longer than eight characters, the last character displayed is a plus sign (+).
PAGE 130
PAGE 131
Configuring Serial WAN (SWAN) Cards (MAX TNT, DSLTNT) 12 Introduction to SWAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1 Overview of SWAN configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1 Understanding SWAN card configuration requirements . . . . . . . . . . . . . . . . . . . . . . . 12-2 Making a profile the working profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 132
Configuring Serial WAN (SWAN) Cards (MAX TNT, DSLTNT) Understanding SWAN card configuration requirements For complete information about the associated parameters, see the APX 8000/MAX TNT/DSLTNT Reference. Table 12-1. SWAN-card configuration tasks Section Description of task Associated parameters “Understanding SWAN card configuration requirements” on page 12-2 Explains important configuration information you should understand before you configure the SWAN card.
PAGE 133
Configuring Serial WAN (SWAN) Cards (MAX TNT, DSLTNT) Making a profile the working profile Table 12-2. SWAN card configuration (continued) Element Explanation Activation The Activation parameter tells the MAX which signals control the data flow through the serial WAN port. The DCE to which the serial WAN port is connected (for example, a Frame Relay switch) determines how to set the serial WAN port Activation value. Flow control is always handled by the Clear To Send (CTS) signal.
PAGE 134
Configuring Serial WAN (SWAN) Cards (MAX TNT, DSLTNT) Assigning a name to a SWAN profile clocking clock-mode = external-clock divider = 1 exp = 2 Assigning a name to a SWAN profile In a SWAN profile, the Name parameter enables you to assign the profile a name of up to 16 characters. By default, the name displays the address of the card as shelf:slot:item. Note that the TAOS unit uses only the physical address to identify the SWAN line.
PAGE 135
Configuring Serial WAN (SWAN) Cards (MAX TNT, DSLTNT) Specifying the SWAN internal clock speed Specifying the SWAN internal clock speed The SWAN slot card can generate a transmit or receive internal clock based on the clock speed of its Serial Communication Adapter (SCA) chips. The maximum clock speed is 5.55 MHz. To generate an internal clock for a SWAN line, you configure the following parameters: Parameter Description Clock-Mode Specifies whether the SWAN card generates an internal clock.
PAGE 136
Configuring Serial WAN (SWAN) Cards (MAX TNT, DSLTNT) Frame Relay configuration divider = 1 exp = 2 5 Specify the Divider and exponent to use for calculating the clock speed: admin>set divider=4 admin>set exp=2 6 Write the profile: admin>write This example sets the internally generated clock to 1.042 Mhz—that is, (16.667/4)/22=1.042. Frame Relay configuration Complete details about Frame Relay configuration can be found in the APX 8000/MAX TNT/DSLTNT Frame Relay Configuration Guide.
PAGE 137
Configuring Unchannelized DS3 Cards (MAX TNT, DSLTNT) 13 Introduction to unchannelized DS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1 Supported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1 Overview of unchannelized DS3 configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2 Using the UDS3 profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 138
Configuring Unchannelized DS3 Cards (MAX TNT, DSLTNT) Overview of unchannelized DS3 configuration Overview of unchannelized DS3 configuration Table 9-1 lists the sections describing common tasks you might have to perform to configure an unchannelized DS3 line. The table includes a brief description of each task, and lists the parameters you will use. For complete information about the associated parameters, see the APX 8000/MAX TNT/DSLTNT Reference. Table 13-1.
PAGE 139
Configuring Unchannelized DS3 Cards (MAX TNT, DSLTNT) Configuring the UDS3 physical link By default, each unchannelized DS3 line is disabled. When the DS3 interface is disabled, it transmits the DS3 Idle Signal to the far end.
PAGE 140
PAGE 141
14 Configuring DS3-ATM Cards Introduction DS3-ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1 Overview of DS3-ATM settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1 Examples of DS3-ATM configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3 Introduction DS3-ATM The DS3-ATM cards (DS3-ATM and DS3-ATM2) support one 44.736Mbps interface for connecting to one ATM switch.
PAGE 142
Configuring DS3-ATM Cards Overview of DS3-ATM settings [in DS3-ATM/{ any-shelf any-slot 0 }:line-config] trunk-group = 9 nailed-group = 1 activation = static call-route-info = { any-shelf any-slot 0 } loopback = no-loopback high-tx-output = no framer-mode = C-BIT-PLCP vpi-vci-range = 0-15/32-4095 traffic-shapers = [ { no 1000 1000 2 no 0 } { no 1000 1000 2 no 1 } {+ cell-payload-scramble = yes Parameter Specifies Name Name of the interface.
PAGE 143
Configuring DS3-ATM Cards Examples of DS3-ATM configurations Parameter Specifies Traffic-Shapers Settings for shaping traffic on the interface. For details, see the APX 8000/MAX TNT/DSLTNT ATM Configuration Guide. Cell-Payload-Scramble Enable/disable scrambling and descrambling of the 48-byte ATM cell payload. This function is enabled by default. Disable it only if the far-end switch has disabled the corresponding functions.
PAGE 144
Configuring DS3-ATM Cards Examples of DS3-ATM configurations Looping back the line To diagnose possible line problems, you can loop back the DS3-ATM interface by using the Loopback parameter in the line profile. While the interface is looped back, normal data traffic is interrupted. The Loopback parameter in the DS3-ATM profile supports the following settings: • No-Loopback. The default, specifies that the line is operating normally. • Facility-Loopback.
PAGE 145
15 Configuring OC3-ATM Cards (MAX TNT/DSLTNT) Introduction to OC3-ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1 Overview of OC3-ATM settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1 Using OC3-ATM ports as a clock source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3 Example of an OC3-ATM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 146
Configuring OC3-ATM Cards (MAX TNT/DSLTNT) Overview of OC3-ATM settings rx-descramble-disabled = no tx-scramble-disabled = no rx-cell-payload-descramble-disabled = no tx-cell-payload-scramble-disabled = no loop-timing = yes vpi-vci-range = 0-15/32-4095 clock-source = not-eligible clock-priority = middle-priority traffic-shapers = [ { no 1000 1000 2 no 0 } { no 1000 1000 2 no 1 } {+ Parameter Specifies Name Name of the interface.
PAGE 147
Configuring OC3-ATM Cards (MAX TNT/DSLTNT) Using OC3-ATM ports as a clock source Parameter Specifies Tx-Cell-PayloadScramble-Disabled Enable/disable scrambling of the 48-byte ATM cell payload in transmitted cells. This function is enabled by default. Disable it by setting this parameter to yes only if the far-end switch has disabled the corresponding functions. Loop-Timing Enable/disable derivation of transmission timing from receiver inputs. Loop timing is enabled by default.
PAGE 148
Configuring OC3-ATM Cards (MAX TNT/DSLTNT) Example of an OC3-ATM configuration For example, the following commands configure an OC3-ATM port as an eligible clock source. If this port becomes unavailable and is not backed up, the unit begins using the built-in clock on the shelf controller.
PAGE 149
16 Configuring STM-0 Cards Introduction to STM-0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1 Using STM and T1 profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2 Sample STM-0 configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2 Introduction to STM-0 The Synchronous Transport Module (STM)-0 card is an optical 51.
PAGE 150
Configuring STM-0 Cards Using STM and T1 profiles Using STM and T1 profiles When the TAOS unit first detects the presence of an STM-0 card, it creates a default STM profile for the card as well as 28 T1 profiles for each component T1 line.
PAGE 151
Configuring STM-0 Cards Sample STM-0 configurations Example of configuring a T1 data trunk The following commands configure a T1 line as an SS7 data trunk, enabling the signaling gateway to control the line: admin> read t1 {1 1 7} T1/{ shelf-1 slot-1 7 } read admin> set line-interface enabled = yes admin> set line-interface signaling-mode = ss7-data-trunk admin> set line-interface incoming-call-handling = internal-pro- cessing admin> write T1/{ shelf-1 slot-1 7 } written APX 8000/MAX TNT/DSLTNT Physical
PAGE 152
PAGE 153
Configuring DSL Connections (DSLTNT) 17 Introduction to DSL technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1 DSL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4 Configuring switched connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4 Configuring nailed connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 154
Configuring DSL Connections (DSLTNT) Introduction to DSL technologies The IDSL line card provides the following features: • ISDN BRI (2B1Q) signaling • Two DB37 connectors, each providing 16 IDSL sessions for a total of 32 sessions • 128Kbps user bit rate over a two-wire subscriber loop • Line Termination (LT) mode • No switch required • Point-to-point connectivity • Support for both switched channels and nailed channels (including Lucent’s SuperDigital 128) • Support for maintenance function
PAGE 155
Configuring DSL Connections (DSLTNT) Introduction to DSL technologies Wire gauge (AWG) Upstream rate Downstream rate Distance 24 928 Kbps 9248 Kbps 10,000 feet (3.05 km) 26 736 Kbps 6976 Kbps 10,000 feet (3.05 km) SDSL overview The SDSL card supports symmetric data transfer rates of 768 Kbps for a distance of up to 12,000 feet (3.7 km) over a single pair of copper wires. The SDSL-HS data card expands on features offered in the 16-port SDSL card.
PAGE 156
Configuring DSL Connections (DSLTNT) DSL configuration For complete details of configuring authentication or Frame Relay and PPP connections on your DSLTNT, see the APX 8000/MAX TNT/DSLTNT WAN, Routing and Tunneling Configuration Guide and the APX 8000/MAX TNT/DSLTNT Frame Relay Configuration Guide. DSL configuration You configure DSL connections in much the same way you configure ISDN or modem connections.
PAGE 157
Configuring DSL Connections (DSLTNT) Configuring nailed connections • Set the Dial # parameter in the Configure profile to the DSL port number, which in the case of a single DSLPipe is always 1. To configure a switched connection on the DSLTNT for an incoming connection from a DSLPipe, you must set the Call-Type parameter to Off in the Connection profile for the DSLPipe.
PAGE 158
Configuring DSL Connections (DSLTNT) Configuring data transfer rates Configuring data transfer rates You can configure DSL upstream and downstream rates in the line profiles for each card, and in Connection or RADIUS profiles. The data transfer rates in the line profiles apply to the port. The data rate limits in Connection or RADIUS profiles apply only to sessions using that particular profile.
PAGE 159
Configuring DSL Connections (DSLTNT) Configuring data transfer rates For example, if the transceiver is configured for 1088000bps and the loop quality is so poor that the transceiver will not connect to the remote side, the transceiver does not automatically adjust the down-rate into the 952000bps range. The administrator needs to configure the Max-Down-Stream-Rate to the lower rate. Note: For more information about the Max-Downstream-Rate parameter, see the APX 8000/MAX TNT/DSLTNT Reference.
PAGE 160
Configuring DSL Connections (DSLTNT) Configuring data transfer rates To configure the maximum transfer rate for the 24-port SDSL card: 1 Open the SDSL profile: admin>read sdsl {2 1 7} SDSL/{ shelf-2 slot-1 7 } read 2 Enable the line: admin>set enabled=yes 3 List the Line-Config profile: admin> list line-config [in SDSL/{ shelf-2 slot-1 7 }:line-config] trunk-group = 0 nailed-group = 1 activation = static call-route-info = { any-shelf any-slot 0 } data-rate-mode = singlebaud max-rate = 784000 unit-type
PAGE 161
Configuring DSL Connections (DSLTNT) Configuring data transfer rates Parameter/RADIUS attribute Specifies Ses-Rate-Mode/ Ascend-Dsl-Rate-Mode (97) Per-session DSL data rate mode. The default setting, Autobaud, specifies that the DSLTNT must train up to a set data rate. If a DSL modem cannot train to this data rate, it will connect at the closest rate to which it can train (the modem’s ceiling rate). Currently Autobaud is the only supported option.
PAGE 162
Configuring DSL Connections (DSLTNT) Configuring data transfer rates admin> set session ses-rate-type = adsl-cap admin> set session ses-adsl-cap-down-rate = 7168000 admin> write CONNECTION/adslpipe-1 written Following is a comparable RADIUS profile: adslpipe-1 Password = "pipepw", User-Service = Framed-User Framed-Protocol = PPP, Framed-Address = 10.2.3.31, Framed-Netmask = 255.255.255.
PAGE 163
Configuring DSL Connections (DSLTNT) Configuring data transfer rates LOG info, Shelf 1, Controller, Time: 16:47:11-[1/7/1/1] Incoming Call [MBID 18] LOG info, Shelf 1, Controller, Time: 16:47:11-[1/7/1/0] Assigned to port [MBID 18] LOG info, Shelf 1, Controller, Time: 16:47:11-[1/7/1/1] Call Connected [MBID 18] LOG info, Shelf 1, Slot 7, Time: 16:47:14-[1/7/1/0] LAN session up: [MBID 18] [adslpipe-1] LOG notice, Shelf 1, Slot 7, Time: 16:47:14-Line 1 (radius) profile adslpipe-1 from
PAGE 164
Configuring DSL Connections (DSLTNT) Configuring DSLPipe Plug and Play LOG info, Shelf 1, Controller, Time: 16:47:34-[1/7/1/0] Assigned to port [MBID 19] LOG info, Shelf 1, Controller, Time: 16:47:34-[1/7/1/1] Call Connected [MBID 19] LOG info, Shelf 1, Slot 7, Time: 16:47:39-[1/7/1/0] LAN session up: [MBID 19] [adslpipe-1] LOG notice, Shelf 1, Slot 7, Time: 16:47:39-Line 1 (radius) profile adslpipe-1 from to LOG notice, Shelf 1, Slot 7, Time
PAGE 165
Configuring DSL Connections (DSLTNT) Configuring DSLPipe Plug and Play Figure 17-1. DSLPipe unit obtaining its configuration (Plug and Play) DHCP server 10.178.10.125 DSLTNT with DSL cards DHCP Unconfigured DSLPipe unit WAN TFTP session TFTP server 10.156.134.11 The DSLPipe unit uses the minimal configuration it obtains via DHCP to access the specified TFTP server and a configuration file, which is identified by a filename that matches the unit’s serial number.
PAGE 166
Configuring DSL Connections (DSLTNT) Configuring DSLPipe Plug and Play TFTP Host Name=host-1.abc.com Boot File Path=/tftpboot/config For a Pipeline unit to operate as a DHCP server, DHCP Spoofing and Always Spoof must be set to Yes. To enable the server to return an IP address, netmask, path to a more detailed configuration file, and TFTP server name, configure the following parameters: • Set the IP Group 1 parameter and Group 1 Count parameters to represent a valid IP address pool.
PAGE 167
Configuring DSL Connections (DSLTNT) Configuring DSLPipe Plug and Play Configuring the DSLTNT DSLPipe Plug and Play support requires the following configuration on the DSLTNT: • BOOTP Relay enabled • A nailed DSL connection to the DSLPipe • A Frame Relay profile that makes use of the DSL line • A Connection profile for each DSLPipe unit This section does not include the DSLTNT IP and DNS configurations, which are required for Plug and Play to work.
PAGE 168
Configuring DSL Connections (DSLTNT) Configuring DSLPipe Plug and Play 1 Read in the SDSL profile.
PAGE 169
Configuring DSL Connections (DSLTNT) Configuring IDSL voice connections 6 Write the profile: admin> write FRAME-RELAY/fr written Configuring a Connection profile This example Connection profile uses the Frame Relay profile configured in the previous section to reach the DSLPipe.
PAGE 170
Configuring DSL Connections (DSLTNT) Configuring IDSL voice connections Figure 17-2. Incoming and outgoing voice calls INCOMING channelized T1 or PRI PSTN OUTGOING Incoming calls Incoming IDSL voice calls require that the Central Office (CO) switch support Dialed Number Identification Service (DNIS). DNIS allows the DSLTNT to route incoming calls to the Pipeline or IDSN TA. The DSLTNT does this by comparing the DNIS number it receives to Answer-Number settings in IDSL profiles.
PAGE 171
Configuring DSL Connections (DSLTNT) Configuring IDSL voice connections 1 Read the IDSL profile the remote user is connected to.
PAGE 172
Configuring DSL Connections (DSLTNT) Configuring IDSL voice connections remote-address = 0.0.0.0/0 local-address = 0.0.0.0/0 .. .. 5 Specify the Pipeline IP address: admin> set remote-address=192.1.2.1/24 6 List the Telco-Options profile: admin> list.. telco-options [in CONNECTION/pipeline:telco-options (new)] answer-originate = ans-and-orig callback = no call-type = off nailed-groups = 1 ft1-caller = no force-56kbps = no data-service = 56k-clear .. ..
PAGE 173
Configuring DSL Connections (DSLTNT) Configuring IDSL voice connections techpubs-lab-25> list line-interface channel-config [in T1/{ shelf-1 slot-1 1 }:line-interface:channel-config] channel-config[1] = { switched-channel 9 "" { any-shelf any-slot channel-config[2] = { switched-channel 9 "" { any-shelf any-slot channel-config[3] = { switched-channel 9 "" { any-shelf any-slot channel-config[4] = { switched-channel 9 "" { any-shelf any-slot channel-config[5] = { switched-channel 9 "" { any-shelf any-slot .. .
PAGE 174
Configuring DSL Connections (DSLTNT) Sample DSL configurations – My Name=buffer – My Addr=192.1.2.1/24 – Rem Name=bufferstnt – Rem Addr=192.1.1.1/24 – Route=IP 3 Exit and save the Configure profile. 4 Open Ethernet > Connections > bufferstnt 5 Set the encapsulation to MP+: Encaps=MPP MP+ enables the Pipeline to drops one channel of a data call to answer the voice call instead of sending a busy signal. See the Pipeline documentation for details. 6 Exit and save the Connection profile.
PAGE 175
Configuring DSL Connections (DSLTNT) Sample DSL configurations Configuring the DSLTNT This example assumes the DSLTNT has already been configured with the following information: • IP address of 192.1.
PAGE 176
Configuring DSL Connections (DSLTNT) Sample DSL configurations admin> write Configuring the IDSL profile To configure the DSLTNT IDSL profile, proceed as in the following example: 1 Read the IDSL profile that the remote user is connected to.
PAGE 177
Configuring DSL Connections (DSLTNT) Sample DSL configurations admin> write Configuring a static route to the gateway To configure a static route to the gateway: 1 Read in the IP-Route Default profile: admin> read ip-route default 2 Enter the address of the Gateway on the local LAN to the remote network. set gateway-address = 192.1.1.
PAGE 178
Configuring DSL Connections (DSLTNT) Sample DSL configurations 3 – Name=idsl-fr – Active=Yes – Call Type=Nailed – Nailed Grp=1 Exit the Frame Relay profile and save your changes.
PAGE 179
Configuring DSL Connections (DSLTNT) Sample DSL configurations Configuring the ADSL profile To configure the ADSL profile in this example: 1 Read in the ADSL profile: admin> read adsl-cap {1 7 3} 2 Enable the port: admin> set enabled=yes 3 List the contents of the Line-Config profile: admin> list line-config [in ADSL-CAP/{ shelf-1 slot-7 3 }:line-config] trunk-group = 0 nailed-group = 0 activation = static call-route-info = { any-shelf any-slot 0 } max-down-stream-rate = 7168000 4 Assign this port t
PAGE 180
Configuring DSL Connections (DSLTNT) Sample DSL configurations 6 Verify that IP routing is enabled (the default) for this Connection profile: admin> set ip-routing-enabled = yes 7 Verify that VJ header prediction is not enabled for this Connection profile: admin> set vj-header-prediction = no 8 List the PPP-Options submenu: admin> list ..
PAGE 181
Configuring DSL Connections (DSLTNT) Sample DSL configurations 2 Specify the following values: – Chan Usage=Leased/Unused – My Name=dslpipe – My Addr=10.10.73.1/24 – Rem Name=max-tnt – Rem Addr=104.178.115.163/24 – Route=IP – Bridge=No 3 From the Main Edit menu, select Ethernet > Connections > max-tnt. 4 Specify the following values: – Active=Yes – Encaps=PPP – Bridge=No – Route IP=Yes 5 Open the Encaps Options submenu.
PAGE 182
Configuring DSL Connections (DSLTNT) Sample DSL configurations Figure 17-5. Example SDSL setup with interface-based routing 192.168.216.1/24 SDSL port address 192.168.23.142/30 DSLPipe address 192.168.23.141/30 local loop (SDSL) COE (MAX TNT) CPE (DSLPipe-S) LAN Adrs= 192.168.23.141/30 WAN Alias=0.0.0.0 IF Adrs=192.168.23.
PAGE 183
Configuring DSL Connections (DSLTNT) Sample DSL configurations admin> set local-address=192.168.23.142/30 7 List the submenu for Frame Relay options: admin> list ..
PAGE 184
Configuring DSL Connections (DSLTNT) Sample DSL configurations Configuring the SDSL profile To configure the SDSL profile: 1 Read in the SDSL profile.
PAGE 185
Configuring DSL Connections (DSLTNT) Sample DSL configurations Configuring the DSLPipe-S This section provides an example of configuring the SDSL Pipeline (DSLPipe-S). For complete information about configuring the DSLPipe-S, see the documentation that came with your Pipeline unit. Before you configure the Pipeline, make sure of the following: • The PC connected to the Pipeline has an IP address on the same subnet as the Pipeline.
PAGE 186
Configuring DSL Connections (DSLTNT) Sample DSL configurations 2 3 Specify the following values: – Name=Frame Relay – Active=Yes – Call Type=Nailed If your Pipeline supports it, set LinkUp to Yes: – LinkUp=Yes Note that this parameter does not appear in recent versions of Pipeline software. 4 Exit the Frame-Relay profile and save your changes. Sample SDSL Frame Relay configuration using system-based routing This section describes a common SDSL application.
PAGE 187
Configuring DSL Connections (DSLTNT) Sample DSL configurations 3 Specify the encapsulation type as Frame Relay: admin> set encapsulation-protocol=frame-relay 4 List the IP-Options submenu: admin> list ip-options [in CONNECTION/sdsl-pipeline:ip-options] ip-routing-enabled = yes vj-header-prediction = yes remote-address = 0.0.0.0/0 local-address = 0.0.0.0/0 .... 5 Set the IP address of the DSLPipe-S connecting to the DSLTNT: admin> set remote-address=192.168.216.
PAGE 188
Configuring DSL Connections (DSLTNT) Sample DSL configurations Configuring the SDSL profile To configure the SDSL profile: 1 Read in the SDSL profile.
PAGE 189
Configuring DSL Connections (DSLTNT) Sample DSL configurations Before you configure the Pipeline, make sure of the following: • The PC connected to the Pipeline has an IP address on the same subnet as the Pipeline. • The IP address of the Pipeline is configured as the default gateway for the PC. To configure the Pipeline: 1 From the Main Edit menu, select Configure. 2 Specify the following values: – Chan Usage=Leased/Unused – My Name=sdsl-pipeline – My Addr=192.168.216.
PAGE 190
PAGE 191
18 Signaling System 7 (SS7) Introduction to SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1 System requirements for SS7 operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2 Configuring an SS7 signaling gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4 Cause codes for SS7 ASGCP calls to the TAOS unit . . . . . . . . . . . . . . . . . . . . . . . . 18-19 SNMP support for SS7. .
PAGE 192
Signaling System 7 (SS7) System requirements for SS7 operations System requirements for SS7 operations A TAOS unit configured for SS7 in communication with an SS7 signaling gateway is a service switching point (SSP).
PAGE 193
Signaling System 7 (SS7) System requirements for SS7 operations TAOS unit as terminator of voice and data calls in an SS7 network With the IPDC license, the TAOS unit can communicate with the signaling gateway by means of IPDC. IPDC enables the TAOS unit to terminate voice or data calls. An example of TAOS units being used both for Internet call diversion (data) and Voice over IP (VoIP) is shown in Figure 18-2. Figure 18-2.
PAGE 194
Signaling System 7 (SS7) Configuring an SS7 signaling gateway See MultiVoice for MAX TNT Configuration Guide for a more detailed description of how VoIP calls are processed by IPDC. Interface between a signaling gateway and TAOS unit TCP/IP is the transport service used to carry control messages between a signaling gateway and the TAOS unit. The data delivery layer (DDL) uses a TCP/IP socket on both the signaling gateway and TAOS unit.
PAGE 195
Signaling System 7 (SS7) Configuring an SS7 signaling gateway Settings in the SS7-Gateway profile configure the signaling interface. The TAOS unit resets the signaling link whenever changes are written to the profile. Following are the parameters (shown with default settings) for configuring the signaling interface: [in SS7-GATEWAY] enabled = no control-protocol = asgcp primary-ip-address = 0.0.0.0 primary-tcp-port = 0 secondary-ip-address = 0.0.0.
PAGE 196
Signaling System 7 (SS7) Configuring an SS7 signaling gateway Parameter Specifies System-Type This parameter does not apply when Control-Protocol is set to asgcp. When Control-Protocol is set to ipdc-0.x, the system sends its value as an ASCII string to the media gateway controller in the device registration message. The TAOS unit does not interpret the value. Interpretation on the signaling gateway is gateway dependent.
PAGE 197
Signaling System 7 (SS7) Configuring an SS7 signaling gateway Parameter Specifies Device-ID Logical SS7 command control device where these values apply. Currently, the settings in this profile apply only to the TAOS unit’s operations. This parameter is currently not used. T1-Duration Value of the acknowledgement (ACK) delay timer in milliseconds. This timer specifies the maximum delay for an acknowledgement when an information frame (I-frame) is received. The default value is 1000 (1 second).
PAGE 198
Signaling System 7 (SS7) Configuring an SS7 signaling gateway For some sites, administrative policy or other constraints introduce a requirement to use the system address for some purposes, but to use a separate source address for communication with the signaling gateway.
PAGE 199
Signaling System 7 (SS7) Configuring an SS7 signaling gateway [in T1/{ shelf-1 slot-1 7 }:line-interface:channel-config:24] channel-usage = switched-channel Parameter Usage for SS7 data trunks Signaling-Mode For an SS7 data trunk, which carries no signaling, this parameter can be set to either of the following values. The setting registers the line with the signaling gateway and allows the gateway to take control of the line and its calls.
PAGE 200
Signaling System 7 (SS7) Configuring an SS7 signaling gateway admin> set line-interface enabled = yes admin> set line-interface signaling-mode = ss7-data-trunk admin> set line-interface incoming-call-handling = internal-processing admin> set line-interface channel-config 24 channel-usage = switched admin> write T1/{ shelf-1 slot-1 7 } written E1 lines as SS7 data trunks Configuring the E1 SS7 data trunks is very similar to configuring T1 data trunks.
PAGE 201
Signaling System 7 (SS7) Configuring an SS7 signaling gateway For example, the following commands configure an E1 line as an SS7 data trunk, enabling the signaling gateway to control the line: admin> read e1 {1 10 1} E1/{ shelf-1 slot-10 1 } read admin> set line-interface enabled = yes admin> set line-interface signaling-mode = ss7-data-trunk admin> set line-interface incoming-call-handling = internal-processing admin> set line-interface channel-config 17 channel-usage = switched admin> write E1/{ shelf-1 s
PAGE 202
Signaling System 7 (SS7) Configuring an SS7 signaling gateway per-line basis. Both the native 2-wire continuity check (GR-246-CORE Section B.2) and 4-wire-to-2-wire emulation (GR-246-CORE Section B.3) are supported. Note: Outgoing continuity tests are supported only on T1 and T3 cards. E1 cards support receipt of 4-wire continuity check requests only, and cannot originate continuity tests.
PAGE 203
Signaling System 7 (SS7) Configuring an SS7 signaling gateway TAOS also supports the 4-wire-to-2-wire continuity check, with the following requirements: The exchange that terminates 4 wires must use a transmitting frequency of 1780 ± 20Hz and a receiving frequency 2010 ± 30Hz. The exchange that terminates the 2 wires must use a transmitting frequency of 2010 ± 8Hz and a receiving frequency of 1780 ± 30Hz.
PAGE 204
Signaling System 7 (SS7) Configuring an SS7 signaling gateway Element Description Duration Duration of the tone in milliseconds. This value can range from 0 to 2631. If the duration is 0, a tone will be played continuously until it is stopped by a second STN command.
PAGE 205
Signaling System 7 (SS7) Configuring an SS7 signaling gateway ss7nmi debug-level command The TAOS unit reports the VoIP call statistics in the output of the ss7nmi debug-level command. When the command is entered with the -s option, the results displayed include the number of release channel request (RCR) and release channel completed (ACR) messages sent with and without VoIP call statistics, and the number of unknown SS7 VoIP messages.
PAGE 206
Signaling System 7 (SS7) Configuring an SS7 signaling gateway Number of CONNECT to ASG: Number of CONNECT_ACK from ASG: Number of SETUP rejected from: Number of DISCONNECT requests from: Number of REGISTRATION to ASG: Number of REGISTRATION_ACK from ASG: Number of DL_REL_IND from L2: Number of DL_EST_IND from L2: Number of T303 expiry events: Number of T305 expiry events: Number of T308 expiry events: Last L3 counters reset timestamp: Data Transport Layer: Number of link fail-overs: Number of persistent err
PAGE 207
Signaling System 7 (SS7) Configuring an SS7 signaling gateway Output field Description Number of CONNECT to ASG Total number of active connections to the signaling gateway since it was last reset. Number of CONNECT_ACK from ASG Number of connection acknowledgements the TAOS unit has received from the signaling gateway. Number of SETUP rejected from: Number of setup requests rejected by layer 3 and the signaling gateway call control.
PAGE 208
Signaling System 7 (SS7) Configuring an SS7 signaling gateway Output field Description Number of link fail-overs In a dual LAN configuration, the number of times the TAOS unit switched from one TCP/IP messaging link to another due to the failure of the link. Number of persistent errors Number of times the TAOS unit tried to reestablish a layer 2 link. Last error Type of last error. Possible values are: Last error status change timestamp • No Error: L2 is operating normally.
PAGE 209
Signaling System 7 (SS7) Cause codes for SS7 ASGCP calls to the TAOS unit Number of T308 expiry events: Last L3 counters reset timestamp: 0 [02/16/1999 10:33:31] Data Transport Layer: Number of link fail-overs: Number of persistent errors: Last error: Last error status change timestamp: 0 0 No Error [01/01/1990 00:00:00] When errors are detected, the command output displays the fields explained in the previous section plus the following additional information: Output field Description Number of memory
PAGE 210
Signaling System 7 (SS7) Cause codes for SS7 ASGCP calls to the TAOS unit • The TAOS unit reports User busy (17) if it cannot find a route, or if no resource is available for the call. SS7 IPDC support for call ID and disconnect cause codes The TAOS unit reports a globally unique call identifier to call-logging servers for SS7 data or VoIP calls. This feature enables the NavisAccess software to associate call statistics information generated by the signaling gateway and by the TAOS unit.
PAGE 211
Signaling System 7 (SS7) Cause codes for SS7 ASGCP calls to the TAOS unit ft1-caller = 0 calling-number = { "" unknown unknown unspecified unspecified } force-56kbps = 0 redirect-number = "" call-direction = 0 global-call-id = 03040506-0102-0900-0807-010203040506 Start and Stop records The Ascend_Global_Call_Id attribute in the Start and Stop records for SS7 VoIP and data calls is for call-logging only, not RADIUS, and is reported only when the global call ID is available.
PAGE 212
Signaling System 7 (SS7) Cause codes for SS7 ASGCP calls to the TAOS unit Event Code Q.
PAGE 213
Signaling System 7 (SS7) SNMP support for SS7 Event Code Q.850 Definition DIS_Q850_PROTOCOL_ERROR 911 Message with unrecognized parameter was discarded DIS_Q850_INTERWORKING_UNSPEC 927 Unspecified internetworking event SNMP support for SS7 The SS7 MIB (mgstat.mib) is implemented as a branch object with the main object, mgGroup, linked into the Ascend enterprise MIB. For definitions and descriptions of objects, see the mgstat.mib file distributed with TAOS 8.0.2 software.
PAGE 214
PAGE 215
19 Configuring Call Routing : Network, host, and dual-purpose devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1 Understanding the call-routing database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2 Working with Call-Route profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5 Another way to route incoming calls (deprecated) . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9 Call routing algorithms .
PAGE 216
Configuring Call Routing Understanding the call-routing database Some slot cards act in a dual capacity, performing both network and host functions. Some dual-purpose cards provide their own HDLC resources. For example, T1 and E1 FrameLine cards have HDLC channels integrated into the card and support Frame Relay protocols. Other cards establish the physical connection and terminate calls. Calls on these cards do not require additional HDLC processing.
PAGE 217
Configuring Call Routing Understanding the call-routing database Table 19-1. Fields in a call-routing database entry (continued) Field Contains Source The address of a device that receives calls The address has the same format as the Device field. Type The call-routing type. For default entries (entries created by the system) the value depends on the type of installed device. For entries created by user-specified Call-Route profiles, see “Call-Route profile settings” on page 19-5.
PAGE 218
Configuring Call Routing Understanding the call-routing database 3:1:4 ... The system uses the first modem on the lower-numbered card, then the first modem on the next card. It then uses the second modem on each of the cards, and so forth. This sort order causes the channels of different cards to be interspersed, resulting in load balancing across all cards that match a call’s parameters, even after a system reset.
PAGE 219
Configuring Call Routing Working with Call-Route profiles Hybrid Access card. See “Dedicating Series56 cards to modem processing” on page 19-9 for related information. Trunk line usage and sort order Trunk lines are sorted in the order in which they are installed in the system, with lines in lower-numbered slots preceding those in higher-numbered slots.
PAGE 220
Configuring Call Routing Working with Call-Route profiles Parameter Specifies Phone-Number Telephone number assigned to TAOS unit network lines. For lines that use ISDN service, the telephone number can contain a subaddress, as described in “Second pass: ISDN subaddresses” on page 19-12. Preferred-Source Source of a call. The address of a device in the system. Call-Route-Type Type of call to be routed to the device.
PAGE 221
Configuring Call Routing Working with Call-Route profiles Without an explicit call route for trunk group 8, the system always tries the first E1 card, finds that it does not use trunk group 8, and then drops the call.
PAGE 222
Configuring Call Routing Working with Call-Route profiles The next set of commands creates another Call-Route profile for the Hybrid Access card and sets the preferred source to the second E1 interface in slot 2: admin> new call-route { { { shelf-1 slot-3 0 } 0 } 2 } CALL-ROUTE/{ { { shelf-1 slot-3 0 } 0 } 1 } read admin> set preferred-source = { { 1 2 2 } 0 } admin> write CALL-ROUTE/{ { { shelf-1 slot-3 0 } 0 } 2 } written Note that the default Call-Route profile for the Hybrid Access card was not modifie
PAGE 223
Configuring Call Routing Another way to route incoming calls (deprecated) The following commands create a Call-Route profile to route calls received on trunk group 4 to the Hybrid Access card in slot 4: admin> new call-route { { { 1 4 0 } 0} 0} CALL-ROUTE/{ { { shelf-1 slot-4 0 } 0 } 0 } read admin> set trunk-group = 4 admin> write CALL-ROUTE/{ { { shelf-1 slot-4 0 } 0 } 0 } written This profile creates a call-routing database entry such as the following: device 1:04:01/1 # source 0 0:00:00/0 type digita
PAGE 224
Configuring Call Routing Call routing algorithms Parameter Specifies Call-Route-Info Address of an interface to which a call can be routed, using the following format: { shelf slot item } The default value is nonspecific, with zero values in each field. This parameter is deprecated. Use of Call-Route profiles is preferred. However, if you specify both methods, the Call-Route-Info setting takes precedence. For more information, see “Fourth pass: destination device addresses” on page 19-13.
PAGE 225
Configuring Call Routing Call routing algorithms How the system finds a route After sorting the call-routing database, the TAOS unit compares the information it has gathered about a call to the values in the database, looking for a match. Values are compared in the sorted order. After each comparison, profiles that do not contain zero or a matching value in that compared field are dropped from consideration, so after each pass the list is narrowed considerably.
PAGE 226
Configuring Call Routing Call routing algorithms Details of how a route is chosen The system compares call information to its database entries.
PAGE 227
Configuring Call Routing Call routing algorithms equal to the input number, and its digits must match the add-on digits of the input number.
PAGE 228
Configuring Call Routing Call routing algorithms voice service, all profiles that specify Digital-Call-Type are removed from consideration. Only profiles that specify Voice-Call-Type or Any-Call-Type remain in the list. Note: For T1 lines that use inband signaling, bearer-capability is not known. The TAOS unit treats all calls that terminate on a T1 and use inband signaling as digital calls unless the T1 profile sets the default call type to voice.
PAGE 229
A Provisioning the Switch Provisioning the switch for T1 access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 What you need from your T1 service provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 What you need from your E1 service provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 This appendix provides the information necessary for properly provisioning a switch for T1/EI or T1/E1 PRI access to the WAN.
PAGE 230
What you need from your T1 service provider What you need from your T1 service provider Request the following information about your T1 interface from your WAN provider: • Type of signaling (inband or ISDN D channel) • Type of line encoding (B8ZS or AMI) • Type of framing (ESF or D4) • Each telephone number assigned to the line, on a channel-by-channel or service-by-service basis • Number of nailed-up channels, if any • Number of unused channels, if any • Types of call-by-call services (also c
PAGE 231
Index B A ACM.
PAGE 232
bearer capability and, 9-10 signaling modes described, 9-8 cause codes access SS7 gateway control protocol (ASGCP) calls, 18-19 disconnect, signaling system 7 (SS7) support for call ID, 18-20 CCITT.
PAGE 233
serial WAN card configuration requirements, 12-2 setting date and time, 1-5 setting log level, 1-5 shelf-controller redundancy, 2-1, 2-6 signaling interface parameters, 18-5 signaling system 7 (SS7) gateway, 18-4 specifying default gateway, 1-6 specifying digital modem negotiation, 5-2 specifying DNS information, 1-6 specifying IP address of shelf controller, 1-4 specifying name, 1-5 T1 data trunk for signaling system 7 (SS7) data, example, 18-9 T1 lines, signaling system 7 (SS7) data trunks, 18-8 T1 parame
PAGE 234
DS3-ATM physical interface, 14-2 DS3-ATM port physical-address, 14-2 DSL configuring nailed connections, 17-5 configuring switched connections, 17-4 data transfer rates, configuring, 17-6 enabling only active ports, 17-4 IDSL voice connections, 17-17 incoming IDSL voice, 17-18 MAX TNT configuration for Plug and Play, 17-15 modem rate control for, 17-9 outgoing IDSL voice, 17-18 per-session data transfer rates, configuring, 17-8 Plug and Play, 17-12 Plug and Play BOOTP Relay configuration for, 17-15 Plug and
PAGE 235
Ethernet configuring full duplex mode on Ethernet-2 card, 4-3 installing Ethernet-2 card, 4-2 overview of Ethernet card configuration, 4-2 related profiles, 4-2 shelf controller and routing load, 1-4 shelf controller interface for management, 4-2 specifying default gateway for system, 1-6 specifying DNS information, 1-6 specifying IP address of system, 1-4 verifying configuration of system with Ping, 1-7 Ethernet cards, overview of, 4-1 Ethernet IP address assigning, 2-4 Ethernet profiles described, 4-2 ove
PAGE 236
I IAM. See initial address message (IAM) ICD.
PAGE 237
modems AT modem strings, configuring additional, 5-3 configuring V.34 modulation, 5-3 specifying negotiation settings, 5-2 modulation, configuring V.
PAGE 238
TAOS default value, 18-6 Use-System-IP-Address-As-Source, 18-7 passwords assigning to serial port, 1-8 changing Admin, 1-8 not saved by default, 1-8 SNMP community strings, 1-11 Telnet, 1-8 permissions, Allow-Password not enabled by default, 1-8 phone numbers add-on numbers described, 7-19 assigning to T1 channels, 7-19 example E1 profile configuration, 9-14 example T1 profile configuration, 7-19 hunt groups described, 7-19 used to route calls, 19-12 Physical interface profiles configuration, setting up she
PAGE 239
shelf-controller, 2-6 shelf-controller primary election, 2-1 shelf-controller startup election, 2-1 robbed-bit configuration, 7-11 routing protocols supported by E1 FrameLine card, 10-2 protocols supported by FrameLine card, 8-2 shelf controller Ethernet port and, 1-4, 4-2 calls.
PAGE 240
cause codes for access SS7 gateway control protoco (ASGCP) calls, 18-19 connections statistics, 18-15 connections, error reporting, 18-15 control protocol specification, 18-6 E1 lines as data trunks, 18-10 gateway, configuration, 18-4 incoming calls, 18-4 integration methods, 18-1 introduction, 18-1 IP device control (IPDC) support for call ID, disconnect cause codes, 18-20 signaling gateway platform, 18-1 SNMP support, for, 18-23 system requirements, 18-2 T1 network, 18-4 T3 network, 18-4 T5 timer, 18-11 V
PAGE 241
usage, 7-4, 7-18 T1 line continuity check, two-wire, 18-11 T1 lines assigning name to profile, 7-7 call control for, 7-11 call control for line-side, 7-11 call control for trunk-side, 7-11 clock source and priority, 7-4, 7-17 clocking for, 7-17 configuration, 18-8 configuration parameters, 7-6 configuring channelized, 7-11 configuring NFAS signaling for, 7-13 CSU or DSX, 7-17 data sense (PRI), 7-22 default call route created by system, 11-3 enabling, 7-8 encoding, 7-8 example configurations, 7-23 ISDN NFAS,
PAGE 242
W transport service TCP/IP, 18-4 transport-layer options configuration, 18-6 Trap pfofile setting up, 2-11 Trap profile configuring, 2-11 trunk groups assigning to E1 channels, 9-14, 9-15 assigning to T1 channels, 7-20 configuring, 7-20 explained, 9-14 limiting multichannel calls, 7-20, 9-14 serial WAN card and, 12-2 system-wide enabling, 7-20, 9-14, 9-15 used to route calls, 19-12 trunk-side T1 call control, 7-11 described, 7-2 WAN connecting DS3-ATM card for redundancy, 14-3 Write command, using, 7-6 U