® Tenor AS VoIP MultiPath/Gateway Switch Product Guide P/N 480-0059-00-10 Tenor and Quintum are registered trademarks. PacketSaver, Quintum Technologies, Inc., Risk Free VoP, VoIP Made Easy, TASQ, SelectNet, and SelectNet Technology are trademarks of Quintum Technologies, Inc.
Table of Contents About this Guide What’s included? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Product Guide Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Finding Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RJ-11 Cables (for ASM200, ASG200) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 RJ-11 Splitter Cable (for ASM400 and ASG400) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 RJ-45 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 DB-9 Serial RS-232 Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Specifications. . . . . . . . . . . . . .
Monitor Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 How to Read Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Valid Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Display all Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Post-paid Calling Card - Call Flow (with default language) . . . . . . . . . . . . . . . . . . . . . 6-23 Pre-paid and Post-paid Calling Card - Call Flow (with multiple language support) . . . 6-25 Pre-paid and Post-paid Calling Card - Call Flow (with Multi-Session Call support) . . . 6-26 ANI Authentication Application Type 1 - Call Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28 ANI Authentication Application Type 2 - Call Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this Guide P/N 480-0059-00-10 Preface-1
About this Guide What’s included? This product guide is divided into chapters; each chapter describes a specific topic. The following chapters are included: • About this Guide: Describes what is included in the Product Guide, including typographical conventions. • Chapter 1: Overview. Includes a general overview of the product, including a description of the Tenor AS’s features and capabilities. • Chapter 2: Hardware Components.
About this Guide Typographical Conventions Product Guide Conventions Certain typographical conventions are used throughout this product guide. See below. • All commands you enter via keystrokes appear in bold (e.g., Press Enter or Press Ctrl-I). • All text commands you enter via Telnet session or command line typing appear in italics (e.g., type active). • There are three types of special text that are designed to reveal supplemental information: Note, Warning, and Caution. See below.
About this Guide Finding Help Refer to the Product Guide for help. The Table of Contents and Index tells you where to find information easily. Extensive configuration help is available from the Tenor Configuration Manager/Tenor Monitor User Guide or the Command Line Interface User Guide. Both documents are on the CDR ROM you received with unit or you can download the latest documentation from www.quintum.
Chapter 1: Overview This chapter gives you a general overview of the Tenor AS including feature descriptions and capabilities. Specifically, the following topics are covered: ! A description of Tenor AS ! Features ! Capabilities ! Call Paths ! H.
Chapter 1: Overview What is the Tenor AS? The Tenor AS is a VoIP (Voice over Internet Protocol) H.323/SIP switch that digitizes voice, fax, and modem data and transmits it over the IP network. Designed as a SOHO product, the Tenor AS gives small to medium sized businesses with analog voice infrastructure an easy, cost-effective way to capitalize on the power of Voice over IP (VoIP). The Tenor AS integrates a gateway, gatekeeper, border element intelligent call routing, and supports H.
Chapter 1: Overview Whichever configuration you choose, the high performance unit provides one Autosensing BaseT connection, along with one RS-232 serial console port connection. The unit also incorporates an intelligent call routing engine which regulates system resources and configuration while coordinating all voice traffic activity in the unit. The unit’s simple plug-and-play embedded system architecture brings VoIP technology to your network without changing your existing telephony infrastructure.
Chapter 1: Overview Features The Tenor AS’s specific features are explained below. Unique Design Tenor AS packs powerful VoIP features into one compact unit. The Tenor can be installed without upgrades to the existing voice or data network. You can install the unit in a home or office environment, without affecting the network infrastructure you already have in place.
Chapter 1: Overview Capabilities SelectNet™ Technology Safety Net Quality of service is virtually guaranteed. Tenor AS ’s built-in patented SelectNet™ Technology provides a “safety net,” which virtually guarantees that each call going VoIP will not only be routed successfully, but will deliver high voice quality. SelectNet monitors the IP network performance for VoIP calls.
Chapter 1: Overview SNMP Support The Tenor AS supports Simple Network Management Protocol (SNMP), the standard protocol used to exchange network information between different types of networks. The Tenor AS unit acts as an SNMP agent—using HP® Openview™—to receive commands and issue responses to the Network Manager. The Network Manager will then be able to perform certain functions, such as receiving traps from the Tenor AS.
Chapter 1: Overview Dynamic Call Routing Tenor AS’s intelligent call routing capabilities are state-of-the-art. The unit automatically detects and supports three call types: voice, fax, and modem. Tenor AS will first identify the call origination site—Line/FXO, Phone/FXS, or IP routing group — and then route the call according to the parameters you have configured in the routing database.
Chapter 1: Overview Tenor AS Call Paths Tenor MultiPath Switch (ASM200 and ASM400) Configuration The Tenor MultiPath Switch Configuration is symmetrical with an equal number of Phone/FXS and Line/FXO ports. Calls are routed from the Phone/FXS, Line/FXO, or IP Network. Calls can be routed in any direction between any of the ports. FXS (Phone) Originated Calls. Calls coming from the Phone/FXS interface (i.e.
Chapter 1: Overview IP Network Calls. Calls coming from the IP network (data network) can be routed to the Line/FXO or Phone/FXS interfaces. The Tenor will route calls based upon the dialed number. If the number is configured as a local phone number, the call will be sent to a Phone/FXS circuit for termination, otherwise the call is considered a “Hop-Off call” and the Tenor sends it out through a Line/FXO interface, typically connected to the PSTN.
Chapter 1: Overview Tenor VoIP Gateway (ASG200 and ASG400) Configuration The Tenor VoIP Gateway Configuration is used for Phone/FXS port connecting to the VoIP Network. The number of VoIP ports is equal to the number of FXS ports. Calls can be routed in any direction between any of the ports. See Figure 1-7 for an example of a call origination from the PBX. FXS (Phone) Originated Calls. Calls coming from the Phone/FXS interface (i.e. PBX) may be switched to the data network as a VoIP call.
Chapter 1: Overview Advanced Features/Capabilities Call Management There are four types of routing databases you can configure: Bypass Directory Numbers (BPN), Hunt Local Directory Numbers (Hunt LDN), Hop-Off Directory Numbers (HDN) and Static Routes. Bypass Directory Numbers. Bypass Directory Numbers (BDN) are telephone numbers that are automatically routed directly from a line circuit to the PSTN; they will not be routed VoIP. Some examples of bypass numbers include toll-free calls, emergency calls (i.e.
Chapter 1: Overview Hop-off PBX Calls. Hop-off numbers are phone number patterns for calls to be routed out to the PSTN. (A hop-off PBX call is a toll call which hops through a private network to reduce or eliminate the toll charge.) They are entered in a Hop-off Number Directory and associated with trunks where matching calls should be sent. Tenor AS supports those hop-off PBX calls where the destination Tenor AS is programmed to route the call to the PSTN.
Chapter 1: Overview The primary function of the border element is to collect, manage, and distribute call routing information. A gatekeeper will establish a service relationship with a border element; the gatekeeper provides its zones capabilities and the border element shares call routing capabilities of other zones in the administrative domain. Through the border element, gatekeepers from multiple zones will be able to communicate.
Chapter 1: Overview network access and protects the integrity of the network using Admission Request (ARQ), Admission Confirmation (ACF) and Admission Reject (ARJ) messages. SIP User Agent SIP (Session Initiation Protocol) is a signaling protocol used to establish a session on an IP network for voice control and management; it is a request-response protocol that closely resembles Hypertext Transfer Protocol (HTTP), which forms the basis of the World Wide Web.
Chapter 2: Hardware Components This chapter tells you what is contained in your hardware package. A description of each component is also included.
Chapter 2: Hardware Components Hardware Description The Tenor AS is a stackable device which provides Phone/FXS and Line/FXO connections as well as connections to the Ethernet LAN and a PC. The unit’s front panel includes LEDs; the back panel includes connection jacks, a diagnostics option, reset button, and an on/off power switch. Front Panel Connections and Reset Options Figure 2-1 Tenor AS Front Panel Power LED Status LED Analog Port LEDs LAN LEDs The LEDs display the health of the system.
Chapter 2: Hardware Components LED LAN Label LED Color Description Link Green On: Link is working properly and there is activity on the line. Off: Link has failed. 100Mb Green On: The advertised link rate is 100Mb if the link is not connected, or the actual link rate is 100b if the link is connected. Off: The advertised link rate is 10Mb if the link is not connected, or the actual link rate is 10Mb if the link is connected. Activity Green Flashing On: indicates there is activity (i.e.
Chapter 2: Hardware Components Back Panel Power Switch Ground Screw Power Receptacle Phone/FXS port Line/FXO port LAN port ConsoleDiag port Reset • Ground Screw. An earth ground screw is provided to connect to supplemental earth ground using a Ground Safety Cable, if supplemental ground is needed. • Phone/FXS port. Provides an RJ-11 jack for connection to a PBX, Keyphone or phone.
Chapter 2: Hardware Components Pin # Port 2 Used with Definition 1 Port 2, pin 4 Tip 2 Port 2, pin 3 Ring 3 Port 2, pin 2 Tip 4 Port 2, pin 1 Ring • Line/FXO port. Provides an RJ-11 jack for connection to the Central Office to provide direct connection to the PSTN.
Chapter 2: Hardware Components Figure 2-4 10/100 BASE-T Ethernet Port Pin Order Table 2-4 Input/Output 10/100 Ethernet port Pin # Signal Definition Color 1 TX + Transmit Data White w/orange 2 TX - Transmit Data Orange 3 RX + Receive Data White w/green 4 RSVD Reserved Blue 5 RSVD Reserved White w/blue 6 RX - Receive Data Green 7 RSVD Reserved White w/Brown 8 RSVD Reserved Brown • Console port.
Chapter 2: Hardware Components Pin # Function Description 7 N.C. No Connect 8 N.C. No Connect 9 N.C. No Connect • Diag. Enables you to perform software diagnostic procedures. • Reset. Enables you to reset the system. See Chapter 5: Advanced Topic: Diagnostics/Maintenance for more information. • Power Switch. Switch to turn power on and off. • Power Socket. Connection port to external power supply block.
Chapter 2: Hardware Components Cables The cables listed in Table 2-6 are required to connect a Tenor AS to various interfaces. Contact Quintum for ordering information, if necessary. Table 2-6 Cables Supported Cable Usage RJ-11 to RJ-11 Cable Connection to FXO/Line. (For the AS400 unit. a Dual Port Splitter Cable is required.) RJ-11 to RJ-11 Cable Connection to FXS/Phone. (For the AS400 unit, a Dual Port Splitter Cable is required.
Chapter 2: Hardware Components Figure 2-7 RJ-11 Connector Pinouts Pin # 1 2 3 4 Connects to Pin # 1 2 3 4 Table 2-7 RJ-11 Connector Pinouts Pin # P/N 480-0059-00-10 Definition 1 TIP 2 Ring 3 Tip 4 Ring 2-9
Chapter 2: Hardware Components RJ-11 Splitter Cable (for ASM400 and ASG400) An RJ-11 cable is used to connect the Tenor AS to an FXO or FXS external device. The RJ-11 cable connector pinouts are given in this section to help you identify the proper connector to accommodate your specific networking requirements. The RJ-11 connector is the EIA/TIA standard for Unshielded Twisted Pair (UTP) cable; the wiring color codes are UTP Standard Coloring.
RJ-45 Cables RJ-45 cable connector pinouts are given in this section to help you identify the proper connector to accommodate your specific networking requirements. The RJ-45 (ISO 8877) connector is the EIA/ TIA standard for Unshielded Twisted Pair (UTP) cable; the wiring color codes are UTP Standard Coloring. The pin order is shown in Figure 2-1.
DB-9 Serial RS-232 Cable The Serial RS-232 9-pin cable with a DB-9 male connector (with RS-232 interface) is used to connect the Tenor AS to your PC’s asynchronous serial port. The pin order for DB-9 male and female connectors are shown in Figure 2-3 and Figure 2-4.
Chapter 2: Hardware Components Specifications Voice/Fax Call Routing: FXO/FXS/IP Coding: A-law, mu-law Voice Algorithms: G.723.1A (5.3, 6.3 Kbps), G.726 (16, 24, 32, 40 Kbps), G.729A, G711 Fax Support: Group III at 2.4, 4.8, 7.2, 9.6, 12, 14.
Chapter 3: Installation/Basic Troubleshooting This chapter gives you installation instructions, as well as how to position the Tenor AS successfully within your network.
Chapter 3: Installation/Basic Troubleshooting Installation Before you begin the actual installation, review the pre-installation guidelines which follow and inspect the package contents. Pre-Installation Guidelines • Always use an anti-static wrist strap when handling the unit. • Do not open the unit cover. Inside parts have hazardous voltages and are extremely sensitive to static. If the unit has been opened, your warranty is void.
Chapter 3: Installation/Basic Troubleshooting Connect to Phone/FXS Interface Since there are many different PBX devices, keys systems, fax machines and phones you can connect to the Tenor AS, the instructions which follow explain the general procedure for connecting an RJ-11 cable (included in your package) between the Phone/FXS port and an external device. Use the phone/FXS ports for on-premise wiring only. For the ASM200 and ASG200, you can connect one device to each FXS port.
Chapter 3: Installation/Basic Troubleshooting Connect to Line/FXO Interface To connect to the Line/FXO port, you must first connect the analog phone lines to another piece of equipment that houses your telephone lines running to the PSTN, such as the patch panel, punch down block or wire wrap blocks. If you are unsure of the installation procedures, contact the network administrator or review the documentation you received with the PBX.
Chapter 3: Installation/Basic Troubleshooting Connect to Ethernet LAN You can use these instructions for general connection purposes only. The Ethernet hub/switch manufacturer’s documentation should provide specific instructions for connection to another device, such as the Tenor AS. Figure 2-3 Connect to Ethernet Hub/Switch Data Network Ethernet Hub/Switch 1. Plug one end RJ-45 Ethernet cable into the port labeled LAN. 2. Plug the other end of the cable into one of the Ethernet hub/switch ports.
Chapter 3: Installation/Basic Troubleshooting Connect to PC Console You will need to connect the Tenor AS to your workstation’s serial port via RS-232 connection. (This connection will be used when you assign an IP address to the unit.) For the instructions below, it is assumed you are connecting to a Windows PC. Figure 2-4 Connect to PC Com Port DB-9 1. Insert the male end of the DB-9 cable into the port labeled Console. (See Chapter 2: Hardware Components for RS-232 connector pinouts.) 2.
Chapter 3: Installation/Basic Troubleshooting Install Supplemental Ground Safety Cable (if required) The Tenor AS provides a supplemental Earth Ground screw (a #6 screw). This screw provides earth ground to the unit if additional grounding is required. To provide ground via the grounding screw, you will need to connect the grounding screw to a Ground Safety Cable, which can then be connected to an approved safety earth ground. Connect the Ground Safety Cable as follows: 1.
Chapter 3: Installation/Basic Troubleshooting Power up the System Once you have all cables connected properly, you are ready to turn the system on as follows: 1. Plug in the AC power cord adaptor to an AC outlet. 2. Locate the on/off switch on the back of the unit and click the switch to On. The unit will power up and the LEDs will flash and turn off; the power LED will remain lit. For information about the LEDs, see Chapter 2: Hardware Components.
Chapter 3: Installation/Basic Troubleshooting Assign IP address Before you can configure a Tenor AS, you need to assign a valid IP address. When a Tenor AS is shipped to a customer, you need to assign a valid IP address for each unit. An IP address is a 32 bit (up to 12 numeric characters) address used to identify each network device in the TCP/IP network. If the unit does not have an IP address, data will not be able to be sent to or from the unit.
Chapter 3: Installation/Basic Troubleshooting 10. From the Flow control drop down list box, choose None. 11. Click Ok and a connection to the Tenor will be established. Information about the unit will scroll on the screen. 12. Enter login and password. Both are admin by default. 13. A message will appear on the screen “Tenor Analog does not have an Ethernet interface configured. Would you like to configure an Ethernet Interface?” (y/n). 14. Type y. 15.
Chapter 3: Installation/Basic Troubleshooting Figure 2-7 Port Settings Window 6. From the Bits Per Second drop down list box, choose 38400. 7. From the Data Bits drop down list box, choose 8. 8. From the Parity drop down list box, choose None. 9. From the Stop bits drop down list box, choose 1. 10. From the Flow control drop down list box, choose None. 11. Press the Tenor AS power switch to On. After the bootup sequence, the login prompt will appear. 12. Enter a login name.
Chapter 3: Installation/Basic Troubleshooting Getting Started with Configuration/Making the First Call This section includes basic information for making the first call using VoIP and a Tenor AS; for an example, this call will enable you to dial Quintum Technology’s test unit and hear a recorded message. Once you have accomplished that, you can modify the configuration to meet your own specific needs.
Chapter 3: Installation/Basic Troubleshooting 2. At the prompt, enter the IP address for your unit and enter the default login and password (admin/ admin). 3. At the Phone(FXS)/Line(FXO)> AnalogInterface-Line screen, enable all four lines (or two lines, depending upon the unit type) under FXO Channel Assignment. Click on Confirm/OK. 4. At the System-Wide Configuration> Dial Plan screen, enter an Area Code (default is 732) and check Use 10 Digit Local Dial. Click on Confirm/OK.
Chapter 3: Installation/Basic Troubleshooting inside the test Gateway at 208.226.140.40), and sends the appropriate data to the other endpoint (in this case, the Quintum test unit). The Gateway is merely another function or application of 208.226.140.40. The Gateway functions allow the incoming call to be connected to Quintum’s PBX. Load Software Upgrade To upgrade the software, download the upgrade from the CD ROM you received with the unit, or download the latest software/documentation from www.quintum.
Chapter 3: Installation/Basic Troubleshooting Common Symptoms/Problems Before you begin troubleshooting a potential malfunction, it is a good idea to check your basic hardware connections. See below. • Ensure power cord is firmly installed in the back panel’s power jack and the other end is plugged into the AC power source. • Ensure the unit’s power switch is in the On position. • Verify that all RJ-45, RJ-11 and DB-9 cables fit snugly in each back panel jack.
Chapter 3: Installation/Basic Troubleshooting Common Symptom/Problem Communication with Ethernet Hub, or switch cannot be established. Description/Solution Verify RJ-45 cable is firmly installed in the Ethernet port. Check MDI/MDIX configuration. Check duplex setting on the switch in which they were connected and the speed of 10MB or 100 MB. Communication between the computer’s COM port and Tenor AS serial port cannot be established.
Chapter 4: Advanced Topic: View Call Detail Records This chapter tells you how to display and understand the Call Detail Recording (CDR) feature, which enables you to view call information. Examples are included later in this chapter. Specifically, the following topics are included.
Chapter 4: Advanced Topic: View Call Detail Records What is a CDR? A Call Detail Record (CDR) is a string of data which contains call information such as call date and time, call length, calling party, and called party. Through the Call Detail Recording (CDR) feature, the Tenor AS unit is able to generate a CDR at the completion of each call. CDRs are collected from multiple Tenor AS units simultaneously and continuously.
Chapter 4: Advanced Topic: View Call Detail Records Establish connection between Tenor AS and CDR Server In order to capture CDRs, a connection between the Tenor AS unit and the CDR server must be established. A Tenor AS can be configured to connect up to two CDR servers via port 9002 and 9003. Based on configuration, the Tenor AS unit can either establish a TCP/IP session with one or all of these CDR servers. A flow diagram (Figure 4-1) illustrates the general transfer of information.
Chapter 4: Advanced Topic: View Call Detail Records The instructions below are performed via Command Line Interface (CLI). See the Command Line Interface (CLI) user guide for specific information. 1. Through CLI, access the Configuration prompt. 2. Access the config-CDRServer-1# prompt (the number will change according to the desired server). 3. Type set CDRServerIPaddr followed by the IP address of the CDR server and press Enter. 4.
Chapter 4: Advanced Topic: View Call Detail Records Change CDR Password Change the CDRserver password, if desired, as follows: 1. From the directory in which you are working, right click on the cdrserver.cfg file. At the Open with option, choose Notebook. 2. Scroll down to the line stating cdr_password. Next to that line, enter the password. Valid entry: up to 30 characters. Tenor AS Establishes Connection with CDR Server To capture CDR reports via CDR server (i.e.
Chapter 4: Advanced Topic: View Call Detail Records CDR Output The following is an example of a CDR output. Each field in a CDR string is separated by a comma (any blank fields are designated by a comma). See below for field definitions.
Chapter 4: Advanced Topic: View Call Detail Records the CDR server can send the Tenor AS unit the last Call ID that is received. The Tenor AS unit will reply with all records that contain a Call ID which is greater than the one last received. Called #: The number called. This will be in international format except for a pass-through call going from PBX to PSTN or a call going from PSTN to PBX. Duration: Call duration. This value is in seconds, the value will be 0 if never connected.
Chapter 4: Advanced Topic: View Call Detail Records Cause Code Definitions 47 Resource Unavailable, Unspecified. This cause is used to report a resource unavailable event only when no other cause applies. Local IP Address: The IP address for the Tenor AS unit originating the CDR. The entry will be in the following format: xxx.xxx.xxx.xxx. Remote IP Address: IP address for the remote destination Tenor AS.
Chapter 4: Advanced Topic: View Call Detail Records The following are CDR fields used in the extended format (1 or 101) only. Calling Party Number. The number called from. The format will be delivered in whatever format the PSTN or PBX delivers to the Tenor AS. PIN Code. PIN code entered. 14 digits maximum. This field will be blank if a PIN code is not configured. Remote Call ID #. Unique identification number, generated by the remote-side Tenor AS, for call record matching purposes.
Chapter 4: Advanced Topic: View Call Detail Records Sample Record for Extended Tenor AS CDR Format 3, 4, 103, 104: Record 1 Sample: (includes fields for formats 3 and 103) 1,17325551212,15,20000207062812,21060207062815,2000020706283030,16,208.226.140.57,192 .168.10.
Chapter 4: Advanced Topic: View Call Detail Records Call Disconnected Time: The date and time the call disconnected. The time will be the local time configured on the Tenor AS unit. The entry will be in the following format: yyyymmddhhmmss where yyyy (4 digits for year), mm (2 digits for month), dd (2 digits for day), hh (2 digits for hour), mm (2 digits for minutes), ss (2 digits for seconds). Disconnect Cause Code: The Q.931 cause value assigned if the call is not connected.
Chapter 4: Advanced Topic: View Call Detail Records Incoming Device: If the call is incoming, this field identifies which Analog Interface the call came in on. This entry is fixed at 0. Incoming Analog Interface: If the call is incoming, this field identifies which device interface the call came in on. Valid entry: 1 = PBX, 2 = PSTN. This field will be empty if the call is an incoming VoIP call. Incoming Channel: If the call is incoming, this field identifies which channel the call came in on.
Chapter 4: Advanced Topic: View Call Detail Records The following is a CDR field used in the extended format 4 and 104: Incoming/Outgoing IP DN. If this is an incoming IP call, the number displayed will be the number as received from the other endpoint. If this number is an Outgoing IP call, the number displayed will be the DN as it was sent out over IP (Outgoing number plus prepended digits).
Chapter 5: Advanced Topic: Diagnostics/ Maintenance This chapter explains the advanced topics for diagnosing problems with the unit, viewing system alarms, and performing maintenance procedures, such as upgrading the software.
Chapter 5: Advanced Topic: Diagnostics/Maintenance Monitor LEDs LEDs monitor the health of the system; they are the first signal that the unit is not working properly or that an internal or external error has occurred. LEDs appear on the front of the unit. See Chapter 2: Hardware Components to ensure the correct lighting of each LED. If the LEDs are not lighting at all, check the AC power source to ensure power is being supplied to the unit.
Chapter 5: Advanced Topic: Diagnostics/Maintenance Field 5-3 Definition Valid Entry Type (displays only if you generate an Alarm History) The type of alarm generated. ALR = Alarm. This indicates an active alarm. CLR= Clear. This indicates an alarm that has been cleared from the system. RPT= Report. This indicates that the alarm has been generated for a report. This entry is for internal use only; if you see an alarm that is causing problems, contact customer service.
Chapter 5: Advanced Topic: Diagnostics/Mainte- Valid Alarms The following is a list of all alarm descriptions (text that appears in the Alarm Description field) for all possible alarms the system can generate. In the generated alarm list, the alarm description appears as part of the Description field.
Chapter 5: Advanced Topic: Diagnostics/Maintenance Severity (appears as part of severity field) Critical Alarm Description Definition (text appears in desc field) RADIUS Server Not Responding Appears when none of the configured RADIUS servers respond. This alarm is cleared when any of the RADIUS servers responds or the RADIUS server is disabled via CLI. Major Major Software Error A software error has occurred that affects system signaling, interfaces, or other major operation.
Chapter 5: Advanced Topic: Diagnostics/Maintenance Severity (appears as part of severity field) Minor Alarm Description Definition (text appears in desc field) Log RADIUS server error Displayed when the RADIUS server fails to send required data or the data sent by the RADIUS server has improper values.
Chapter 5: Advanced Topic: Diagnostics/Maintenance Display Active Alarms You are able to display all active alarms as follows: 1. Through CLI, access the Monitor prompt. 2. Type alarm a. The active alarms will be listed. See section How to Read Alarms for field definitions. If you enter alarm without a command following it, both active alarms and the alarm history will be displayed. Figure 5-2 Active Alarm Sample IP# Sequence#Type#Severity# Desc# Slot# Device#Analog Interface# Channel# Date/Time 192.166.
Chapter 5: Advanced Topic: Diagnostics/Maintenance Verify Unit Provisioning An error with provisioning the Tenor AS may cause a number of problems. It may be a simple error, such as an incorrect IP address or telephone number. See the Command Line Interface (CLI) guide or the Tenor Configuration Manager/Tenor Monitor User’s Guide for provisioning information.
Chapter 5: Advanced Topic: Diagnostics/Maintenance Command Line Interface (CLI). You can reset the system through the Command Line Interface (CLI) as follows: 1. Access the CLI through a Telnet session. See the Command Line Interface (CLI) guide for more information. 2. Access the Maintain-MasterChassis-1# prompt. 3. Type reset. You will be asked if you are sure you want to set the unit back to factory defaults. 4. Type yes to confirm (type no to cancel the restore).
Chapter 5: Advanced Topic: Diagnostics/Maintenance If you need Additional Help If you suspect the problem to be on the network end, contact your Central Office to verify proper operation. After completing all troubleshooting/maintenance procedures and reviewing the Common Symptoms/Problems section, you can contact the Customer Service Department at the following: Quintum Technologies, Inc.
Chapter 6: Advanced Topic: SNMP/IVR This chapter explains advanced topics for using the unit, including SNMP and IVR.
Chapter 6: Advanced Topic: SNMP/IVR SNMP Simple Network Management Protocol (SNMP) is the standard protocol used to exchange network management information. It is managed by Hewlett Packard®’s HP Openview™ Network Node Manager. Specifically, this chapter tells you how HP® OpenView auto-discovers a Tenor AS unit, as well as generate SNMP traps for existing alarm messages. SNMP management requires two primary elements: a network manager and an SNMP agent.
Chapter 6: Advanced Topic: SNMP/IVR Software requirements • Microsoft Windows NT operating system (version 4.0), with TCP/IP version 4.0 • Microsoft SNMP Agent (SNMP Services) • Microsoft Peer Web Services or Internet Information Server (IIS) version 4.0 • Netscape Navigator web browser (version 4.06 or higher) or Microsoft Internet Explorer web browser (version 4.0 or higher) with Java/JavaScript options enabled.
Chapter 6: Advanced Topic: SNMP/IVR 5. From the Quintum CD ROM, click on TenorTools. Download the SNMP Agent Software to the HP Openview root directory (this is the directory in which HP Openview was installed). 6. From the HP Openview root directory run installquintum.bat. Installation will begin. The following section lists where the installation files are copied and which files were modified. You can use this information to make changes manually to files, if desired.
Chapter 6: Advanced Topic: SNMP/IVR # # # EVENT Report_Status_Alarm .1.3.6.1.4.1.6618.2.0.4 "Status Events" Normal FORMAT Received trap:generic #$G specific #$S. $#args:$* SDESC Uswcomment EDESC # # # EVENT Uswcomment .1.3.6.1.4.1.6618.2.0.0 "Status Events" Normal FORMAT Received trap:generic #$G specific #$S. $#args:$* SDESC Uswcomment EDESC • The quintum.exe file is added to the HPOVRoot\bin directory. • These files are added to the HPOVRoot\bitmaps\C directory: Tenor_chassis.ico Tenor_A.ico Tenor_D.
Chapter 6: Advanced Topic: SNMP/IVR To set the IP address, use the following CLI command: con-MasterChassis> snmptrapip1 . This command configures the IP address of the network management site in the Tenor AS unit from which the SNMP traps will be generated. Valid entry: The index number of 1-3 (the index number is used to designate the index # for the network manager to be used) followed by the IP address for the network management site.
Chapter 6: Advanced Topic: SNMP/IVR Working with SNMP View traps You can view the traps HP Openview received from the Tenor AS unit as follows: NOTE: Ensure HP Openview is running. 1. From the HP Openview map where the Tenor AS units appear, right-click on the Tenor AS icon for which you want to view traps and select Alarms. 2. From the Alarm Categories window, click on All Alarms. All traps (alarm messages) will be listed in the order in which they occurred.
Chapter 6: Advanced Topic: SNMP/IVR Launching Command Line Interface (CLI) from HP Openview Launch Command Line Interface with pop-up menu as follows: 1. From the HP Openview desktop, right-click on the desired Tenor AS unit icon and select Quintum Analog. 2. The CLI will launch with the IP address of the unit associated with that icon (the correct IP address will appear in the URL). 3. Configure the unit. OR Launch CLI by double-clicking the icon as follows: 1.
Chapter 6: Advanced Topic: SNMP/IVR 1. From the HP Openview desktop, right-click on the desired Tenor AS unit icon and select Object Properties. 2. From the Attributes window, select Quintum Tenor AS. 3. Click on Edit Attributes. 4. Select Turn on Debug Window (the toggle allows you to set to True or False). Select True. 5. Click on Verify. After the verification is complete, click Ok. The Debug Message Display window displays debug messages being processed that are associated with that icon.
Chapter 6: Advanced Topic: SNMP/IVR IVR Interactive Voice Response (IVR) is a feature of the Tenor AS that enables you to offer services, such as Pre-paid calling cards and Post-paid accounts to your customers. The Tenor AS uses the RADIUS (Remote Authentication Dial-In User Service), for authenticating and authorizing user access to the VoIP network.
Chapter 6: Advanced Topic: SNMP/IVR ANI Authentication There are two types of ANI Authentication supported in the Tenor AS: Type 1 and Type 2. ANI Authentication Type 1 enables calling subscribers to receive authentication based on the calling number. If an incoming call has no associated ANI information, the call will not be answered, but simply disconnected. If ANI is present, it will be authenticated with the Radius server (before answering the call).
Chapter 6: Advanced Topic: SNMP/IVR Typical IVR Network Connection/Process See Figure 6-2 for a typical network configuration for IP based pre-paid calling card/post-paid account services. This figure illustrates the originating Tenor AS is configured to provide pre-paid/ post-paid services. All the subscribers will have to dial into this Tenor AS via PSTN to get access to pre-paid/post-paid services.
Chapter 6: Advanced Topic: SNMP/IVR 3 RADIUS server acknowledges start accounting request. Start Accounting is optional. 4 Tenor AS prompts the subscriber for the card number. 5 Caller enters the card number. 6 Tenor AS sends the card number to the RADIUS server for verification. 7 RADIUS server returns the credit balance for the account. 8 Tenor AS plays the credit amount and prompts the subscriber for the destination number. 9 Caller enters the destination number.
Chapter 6: Advanced Topic: SNMP/IVR Configure IVR - Quick Start For a Tenor AS to be used as part of the complete IVR system, and communicate effectively with the RADIUS, you must configure basic options in the Tenor AS via Command Line Interface (CLI) for the following: • Basic IVR Data • RADIUS Instructions for configuring basic IVR information via Command Line Interface (CLI) are described below.
Chapter 6: Advanced Topic: SNMP/IVR 5. Type sharedsecret (sharedsecret is similar to password), followed by the RADIUS key (up to 63 characters) (i.e., sharedsecret 454AJU). 6. Ensure accountingtype is configured. If this field is set to 0, no “stop accounting” messages will be sent.
Chapter 6: Advanced Topic: SNMP/IVR Configure IVR Voice Prompts A voice prompt is a pre-recorded message played for a caller at specific times during a call; the actual voice messages used in the prompting process is stored in the system controller card in the form of audio files that can be recorded by a recording studio. The audio files can then be played back over the PSTN connection to the caller in messages such as “ Enter Account Number”, “Enter PIN number”, “Enter Card Number”, etc.
Chapter 6: Advanced Topic: SNMP/IVR blocked “The number you have dialed is blocked.” [blocked] + [hang_up] The number you have dialed is blocked. Please hang up and call again later. card_number “card number” [enter] + [card_number] + [pound_key] Please enter your card number followed by the pound key. cent “cent” - - cents “cents” - - credit_limit “Your credit limit is exceeded.” [credit_limit] + [good_bye] Your credit limit is exceeded. Good bye.
Chapter 6: Advanced Topic: SNMP/IVR hang_up “Please hang up and call again later.” - - hundred “hundred” - - in_use “This account is currently in use.” [in_use] + [hang_up] This account is currently in use. Please hangup and call again later. invalid “You have entered an invalid number.” - - language “for English press” [lang] + [one] For English press one.
Chapter 6: Advanced Topic: SNMP/IVR pound_key “followed by the pound key.” [enter] + [account_number OR card_number OR pin OR destination] + [pound_key]. Please enter your account number followed by the pound key. Please enter your card number followed by the pound key. Please enter your pin followed by the pound key. Please enter your destination number followed by the pound key. problems “We are currently experiencing technical difficulties.
Chapter 6: Advanced Topic: SNMP/IVR two “two” - - wait “Thank you. Please hold.” - - welcome “Welcome!” - - yen “yen” - - you_have “You have” [you_have] + [] + [remaining] You have six cents remaining. yuan “yuan” - - zero “zero” - - zero_balance “You have zero balance in your account.” [zero_balance] + [good_bye] You have zero balance in your account. Goodbye. Create Voice Prompt Files Configure the directory which houses the voice prompts as follows: 1.
Chapter 6: Advanced Topic: SNMP/IVR IVR Call Flow - Specifications Pre-paid Calling Card - Call Flow (with default language) Figure 6-3 is a diagram of the call flow for pre-paid calling card service, which details the messages transmitted between the following components: Calling Party. The originating caller using a pre-paid calling card. Prepaid Enabled Tenor. The Tenor AS performing the IVR functions. RADIUS Server.
Chapter 6: Advanced Topic: SNMP/IVR Figure 6-3 Pre-paid Calling Card - Call Flow (default language) PREPAID ENABLED TENOR CALLING PARTY SETUP CONNECT RADIUS SERVER CALLED PARTY START ACCOUNTING START ACCOUNTING ACK “Welcome ” “Please Enter Your Card Number” GET CARD NUMBER “You have X dollars and Y cents remaining” AUTHENTICATION (CARD NUMBER) AUTHENTICATION RESP (MONEY) “Please Enter The Phone Number to call” GET DNIS “You have x minutes ” AUTHORIZATION ( DNIS ) AUTHORIZATION RESP (TIME) SETUP
Chapter 6: Advanced Topic: SNMP/IVR Post-paid Calling Card - Call Flow (with default language) Figure 6-4 is a diagram of the call flow for post-paid service, which details the messages transmitted between the following components: Calling Party. The originating caller using a post-paid calling party. Prepaid Enabled Tenor AS. The Tenor AS performing the IVR functions. RADIUS Server. Remote Authentication Dial-In User Service for authenticating and authorizing user access to the VoIP network.
Chapter 6: Advanced Topic: SNMP/IVR Figure 6-4 Post-paid Account - Call Flow (default language) POSTPAID ENABLED TENOR CALLING PARTY RADIUS SERVER CALLED PARTY VPH SETUP START ACCOUNTING START ACCOUNTING ACK “Welcome” “Please Enter Your Account Number” GET ACCOUNT NUMBER “Please Enter Your Pin Number” GET PIN NUMBER AUTHENTICATE (ACCT, PIN) AUTHENTICATION RESPONSE “Please Enter The Phone Number to call” GET DNIS AUTHORIZATION ( DNIS ) AUTHORIZATION RESPONSE SETUP CONNECT DISCONNECT STOP ACCOUNTING
Chapter 6: Advanced Topic: SNMP/IVR Pre-paid and Post-paid Calling Card - Call Flow (with multiple language support) Figure 6-5 is a diagram of the call flow for pre-paid calling card service, which details the messages transmitted between the following components: Calling Party. The originating caller using a pre-paid calling card. Tenor. The Tenor AS performing the IVR functions. RADIUS Server. Remote Authentication Dial-In User Service for authenticating and authorizing user access to the VoIP network.
Chapter 6: Advanced Topic: SNMP/IVR Pre-paid and Post-paid Calling Card - Call Flow (with Multi-Session Call support) For a multi-session call, the calling party can interrupt the call by pressing a multi-session key at anytime and making a new call. When the called party disconnects the call first, the Tenor AS asks if the caller wants another call; the user can then press the designated key.
Chapter 6: Advanced Topic: SNMP/IVR Figure 6-6 Pre-paid and Post-paid Calling Card - Call Flow (multi-session support) CALLING PARTY RADIUS SERVER TENOR CALLED PARTY1 CALLED PARTY2 SETUP CONNECT Case1> ## or ** on speech DISCONNECT “Please Enter Destination Number” STOPACCOUNTING (Leg 1) GET Destination Number AUTHORIZATION (DNIS) AUTHENTICATION RESPONSE CONNECT Case 2> DISCONNECT STOPACCOUNTING (Leg 1) If you want another call, press ** or ## ## or ** “Please Enter Destination Number” GET Destinati
Chapter 6: Advanced Topic: SNMP/IVR ANI Authentication Application Type 1 - Call Flow ANI Authentication Application Type 1 enables calling subscribers to receive authentication based on the calling number. If you configure the ivrtype to 4 (ANI Type 1), when an incoming call comes in, the call will be authenticated with ANI by a RADIUS server.
Chapter 6: Advanced Topic: SNMP/IVR Figure 6-7 ANI Authentication Application Type 1 - Call Flow ANI AUTH ENABLED TENOR CALLING PARTY RADIUS SERVER CALLED PARTY SETUP No: Fast Busy Yes : AUTHENTICATION (ANI) ANI AUTHENTICATION RESPONSE No: Fast Busy Auth fail of ANI CONNECT Second Dial Tone GET DNIS AUTHORIZATION ( DNIS ) AUTHORIZATION RESPONSE SETUP CONNECT DISCONNECT STOP ACCOUNTING IP LEG STOP ACCOUNTING IP LEG ACK STOP ACCOUNTING TELEPHONY LEG STOP ACCOUNTING TEL LEG ACK P/N 480-0059-00-10
Chapter 6: Advanced Topic: SNMP/IVR ANI Authentication Application Type 2 - Call Flow ANI Authentication Application Type 2 enables calling subscribers to receive three authentication types based on the calling number: (1) Authentication with ANI, (2) No ANI case (if no ANI in coming packet, Tenor AS asks PIN number by prompt) and (3) Incoming packet has the ANI, but authentication with the ANI fails and Tenor AS prompts for the PIN number.
Chapter 6: Advanced Topic: SNMP/IVR Figure 6-8 ANI Authentication Application Type 2 - Call Flow ANI AUTH ENABLED TENOR CALLING PARTY SETUP No: Pin prompt Tone RADIUS SERVER CALLED PARTY Yes : AUTHENTICATION (ANI) 1 ANI GET PIN AUTHENTICATION (PIN) 2 AUTHENTICATION RESPONSE ANI auth fail : Pin prompt Tone Auth fail of ANI GET PIN AUTHENTICATION (PIN) 3 AUTHENTICATION RESPONSE CONNECT Second Dial Tone GET DNIS AUTHORIZATION ( DNIS ) AUTHORIZATION RESPONSE SETUP CONNECT DISCONNECT STOP ACCOUNTING
Chapter 6: Advanced Topic: SNMP/IVR Call Flow - Message Attributes The sections which follow indicate the message attributes for specific message packets; the Quintum vendor ID is 6618. Start Accounting Request Message Attributes Table 6-3 lists the message attributes in the Start Accounting Request message packet sent between the Tenor AS and the RADIUS server. Start Accounting is optional.
Chapter 6: Advanced Topic: SNMP/IVR Stop Accounting Request Message Attributes Table 6-4 lists the message attributes in the Stop Accounting Request message packet sent between the Tenor AS and the RADIUS server.
Chapter 6: Advanced Topic: SNMP/IVR 26 h323-voicequality 31 ICPIF of the voice quality Numeric 26 h323-remoteaddress 23 IP address of the remote gateway Numeric 44 Acct-Session-Id A unique accounting identifier-match start & stop String 42 Acct-Input-Octets Number of octets received for that call duration Numeric 43 Acct-OutputOctets Number of octets sent for that call duration Numeric 47 Acct-InputPackets Number of packets received during the call Numeric 48 Acct-OutputPackets
Chapter 6: Advanced Topic: SNMP/IVR Authentication Request Message Attributes Table 6-5 lists the message attributes in the Authentication Request message package sent between the Tenor AS and the RADIUS server.
Chapter 6: Advanced Topic: SNMP/IVR 26 h323-billingmodel 109 Type of billing service for a specific call. Numeric 1:debit/prepaid 26 h323-currencytype 110 Currency for use with h323-credit-amount ISO 4217 USD 31 h323-prompt-id 104 Index into an array of prompt files used by Tenor AS Numeric 27 Authorization Request Message Attributes Table 6-7 lists the message attributes in the Authorization Request message packet sent between the Tenor AS and the RADIUS server.
Chapter 6: Advanced Topic: SNMP/IVR Authorization Response Message Attributes Table 6-8 lists the message attributes in the Authorization Response message packet sent between the Tenor AS and the RADIUS server.
GLOSSARY A Alarm. A brief message that appears on your screen when the Tenor AS encounters a problem (i.e., failed interface). Alarms can be viewed through CLI (see Command Line Interface), a Telnet connection, or Tenor Monitor. Auto Switching. If a network packet delay for an IP call becomes unacceptable, the Tenor AS will automatically switch the call to PSTN. B Border Element. Provides access into or out of an administrative domain. The Tenor AS has two types of Border Elements: Primary and Secondary.
Authentication Dial-In User Service) is used for authenticating and authorizing user access to the VoIP network. of a PBX into a private network in order to eliminate toll charges. I Internet. A packet based network which transports voice/video/data over TCP/IP. Intranet communication. Communication within the same company, usually through an Ethernet hub. IP Address. A unique 32 bit address that identifies a network device is connected to the network via TCP/IP. IVR.
the public network, it is considered a WAN. As a result, intra-corporate information is passed through the data network from one LAN to another LAN site in a remote location. Zone. A group of endpoints (e.g, gateways, terminals, etc.) in one corporate site.
INDEX overview 4-2 Configuration 3-13 Connection line interface (PBX) 3-3 A About this guide 1-1 Alarms 5-2 active 5-7 display 5-6 display via CLI 5-6 field definitions 5-2 green 6-7 history 5-7 list of 5-4 monitor 5-2 orange 6-7 red 6-7 white 6-7 yellow 6-7 D Date/Time 5-9 DB-9 2-12 dial plan 1-11 B Back panel ground screw 2-4 power switch 2-7 Bypass DN 1-11 C Cables 2-8 DB-9 2-12 RJ-45 2-8, 2-10, 2-11 Call 1-7 Call management public/private dial plan 1-11 trunk group support 1-7 Capabilities CDR 1-6 I
Hunt LDN 1-11 I Installation 3-2 connect to Ethernet 3-5 connect to line/FXO 3-4 connect to PC 3-6 connect to phone/FXS 3-3 ground safety cable 3-7 guidelines 3-2 package contents 3-2 IP Network Calls 1-9 IVR 1-6, 6-10 ANI 6-11 basic configuration 6-14 call flow 6-16 call flow specifications 6-21 call types 6-10 configure voice prompts 6-16 create voice prompts 6-16, 6-20 multi-session 6-11 post-paid 6-10 pre-paid 6-10 quick start 6-14 typical connection 6-12 voice prompts 6-16 L LEDs monitor 5-2 M Maintena
Warranty/Approvals QUINTUM TECHNOLOGIES, INC. LIMITED WARRANTY AGREEMENT Quintum Limited Warranty QUINTUM WARRANTY: Quintum warrants that under normal use and conditions (i) the Quintum hardware products covered by this warranty, for a period of two years, and (ii) all software media, also for a period of two years, will be free from significant defects in materials and workmanship from the date of purchase from Quintum or Quintum’s authorized reseller or distributor (the “Warranty Period”).
MERCE EXPORT ADMINISTRATION REGULATIONS, EXPORT OR OTHERWISE (B) THE PRODUCTS ARE RELOCATED, MOVED, SHIPPED OR EXPORTED TO ANY LOCATION WHICH WOULD RESULT IN (WHETHER AS A RESULT OF THE USE OF THE PRODUCTS OR FOR ANY OTHER REASON) A VIOLATION OF ANY INTERNATIONAL, NATIONAL OR LOCAL LAW, STATUTE, REGULATION, ORDER OR SIMILAR AUTHORITY. Quintum RMA Procedure 1.
Documentation Notice Information in this document is subject to change without notice and does not represent a commitment on the part of Quintum Technologies, Inc. The recipient of this document has a personal, non-exclusive and non-transferable license to use the information contained within solely with Quintum Technologies, Inc. products for the purpose intended by the agreement.
Agency Approvals EMI/EMC Standards FCC Part 15 Class B ICES-003 EN55022:98 EN55024:98 EN61000-3-2 :95 EN61000-3-3:95 AS/NZS 3548:1995 Safety Standards UL60950-1 CSA C22.2 No.
FCC WARNINGS This equipment has been tested and found to comply with the limits for Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy, and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications.
If trouble is experienced with this device, for repair and warranty information, please refer to the Technical Support insert for repair information and the warranty section of this Getting Started Guide for warranty information. In the event of device malfunction, all repairs should be performed by Quintum Technologies, Inc. or an authorized agent. It is the responsibility of users requiring service to report the need for service to Quintum Technologies or to one of our authorized agents.
Canadian Notice The Industry Canada label identifies certified equipment. This certification means that the equipment meets certain telecommunications network protective, operation, and safety requirements. The Department does not guarantee the equipment will operate to the users' satisfaction. Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local Telecommunications Company.
