Tenor® DX VoIP MultiPath/Gateway Switch Product Guide P/N 480-0049-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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Back Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 RJ-45 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 DB-9 Serial RS-232 Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Download and install SNMP-Related Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Configure Network Manager IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Working with SNMP. . . . . .
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 General Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 Restore Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 Reset System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this Guide P/N 480-0049-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 DX’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 via the Tenor Configuraton Manager and Tenor Monitor online help systems or the Command Line Interface online help system. See Chapter 4: Getting Started: Tenor Configuration Manager/Tenor Monitor for more information.
Chapter 1: Overview This chapter gives you a general overview of the Tenor DX including feature descriptions and capabilities. Specifically, the following topics are covered: ! A description of Tenor DX ! Features ! Capabilities ! Call Routing/Management Options ! H.
Chapter 1: Overview What is the Tenor DX? The Tenor DX is a high-density VoIP (Voice over Internet Protocol) H.323/SIP switch that converts voice, fax, and modem data on digital circuit switched trunks, and transmits it over the IP network. The Tenor DX integrates a gateway, gatekeeper, border element, intelligent call routing, and supports H.323/SIP, and QoS all in one solution.
Chapter 1: Overview The unit’s simple plug and play embedded system architecture brings VoIP technology to your network without changing your existing telephony infrastructure. Your network stays as is, and the call type is transparent to the user. This technology boasts superior voice quality without compromising reliability. The Tenor DX is available in the versions listed in Table 2-1.
Chapter 1: Overview Features The Tenor DX’s specific features are explained below. Unique Design Tenor DX packs powerful VoIP features into one compact unit. The system’s embedded design enables you to configure the unit directly without depending on another operating system; it can be either placed on a table or mounted in a 19” rack. With its MultiPath technology, the Tenor can be installed without upgrades to the existing voice or data network.
Chapter 1: Overview PacketSaver™ reduces bandwidth consumption PacketSaver packet multiplexing technology reduces the amount of IP bandwidth required to support multiple calls flowing between two endpoints. PacketSaver minimizes bandwidth usage by aggregating samples from multiple VoIP conversations and packing them into a larger IP packet with a single IP header. The process removes the need to send a bulky IP header with individual voice packets.
Chapter 1: Overview Capabilities Virtual Tie Line Tenor DX can emulate a tie trunk. It provides all of the functionality of a tie trunk, including the considerable cost savings, but eliminates the need for a PBX trunk to be configured, or marked as a tie trunk. A traditional tie trunk is a PBX-configured direct connection between two PBXs in separate locations. The tie trunk bypasses the PSTN network. Your PBX does not need any additional configuration.
Chapter 1: Overview NATAccess™ NATAccess is an intelligent network address translation technology. It enables VoIP networks with multiple H.323 endpoints to operate behind firewalls equipped with H.323 Network Address Translation (NAT); this provides maximum network security. NATAccess simplifies deployment by eliminating the need to place the Tenor on a public IP network. Using NATAccess provides easy, secure expansion between multiple VoIP sites.
Chapter 1: Overview Call Routing/Management Options Call Routing Line Circuit Originated Calls. Calls coming from a Line Circuit may be switched to either the data network as a VoIP call or to a Trunk Circuit typically for connection to another circuit switched network such as the PSTN. The routing decision made by the Tenor is based upon your configuration and the dialed number.
Chapter 1: Overview Figure 1-4 Trunk Circuit Call Routing PSTN A Trunk Circuits Circuit Call Line Circuits Trunk Circuits 1 2 3 4 5 6 7 R E S E T 8 D I A G Line/Act LAN 1 PSTN B CONSOLE LAN 2 Line/Act 100 POWER ALERT 100 Tenor DX Circuit Call PBX Tenor CMS VOIP Call Ethernet (IP Network) R Ethernet Intra-trunk Routing - “Hairpinning”.
Chapter 1: Overview Figure 1-6 Data Network Call Routing PSTN A Trunk Circuits Circuit Call Line Circuits Trunk Circuits 1 2 3 4 5 6 7 8 R E S E T D I A G Line/Act LAN 1 PSTN B CONSOLE LAN 2 100 Line/Act 100 POWER ALERT Tenor DX Circuit Call PBX Tenor CMS R Ethernet (IP Network) VOIP Call Ethernet Routing Table Options There are four types of routing databases you can configure: Bypass Directory Numbers (BPN), Hunt Local Directory Numbers (Hunt LDN), Hop-Off Directory Numbers (H
Chapter 1: Overview Call Management Features Dynamic Call Routing. Tenor DX’s intelligent call routing capabilities are state-of-the-art. The unit automatically detects and supports three call types: voice, fax, and modem. Tenor DX will first identify the call origination site—trunk circuit, line circuit, or IP routing group —and then route the call according to any parameters you have configured in the routing database.
Chapter 1: Overview H.323 Gatekeeper Services The Tenor DX unit’s built-in H.323 gatekeeper performs IP call routing functions, such as call control and administrative services to another Tenor DX unit, or another H.323 endpoint. The gatekeeper’s functionality complies with the H.323 industry specifications for voice control and management. Gatekeeper A Gatekeeper in an H.323 network provides call control services and other services to H.323 endpoints (i.e., gateways, terminals, and MCUs).
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 Admissions Control. All H.323 endpoints must register and request permission to enter the gatekeeper’s zone; the gatekeeper will confirm or deny access to the network. The gatekeeper authorizes network access and protects the integrity of the network using Admissions Request (ARQ), Admissions Confirmation (ACF) and Admissions Reject (ARJ) messages.
Chapter 1: Overview 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. SIP re-uses many of the constructs and concepts of Internet protocols such as HTTP and Simple Mail Transfer Protocol (SMTP). The purpose of SIP is only to establish/change/terminate sessions.
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 DX is a stackable/rack mountable device which provides PSTN and PBX connections (through T1/ E1/PRI lines), as well as connections to the Ethernet LAN and a PC. The unit provides eight RJ-45 ports in which you can connect to a PBX or the PSTN. The unit’s front panel includes connection jacks, LEDs, a reset button, and a diagnostics option; the back panel includes a power cord connection site, an on/off switch, and a label.
Chapter 2: Hardware Components Figure 2-2 10/100 BASE-T Ethernet Port Pin Order Table 2-1 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 # 2-4 Function Description 7 N.C. No Connect 8 N.C. No Connect 9 N.C.
Chapter 2: Hardware Components Front Panel LEDs The LEDs display the health of the system. There are different types of LEDs: network, LAN, Alert and Power. For LED definitions, see Table 2-3. Figure 2-4 Front Panel LEDs 1 2 3 4 5 6 7 R E S E T 8 D I A G LAN 1 Line/Act 100 LAN 2 CONSOLE POWER Line/Act ALERT 100 LAN LEDs Alert LED Network LEDs Power LED Table 2-3 Front Panel LEDs Definitions LED Label LED Color Description Red Receive Path Error Indication.
Chapter 2: Hardware Components Back Panel AC Receptacle Power Switch 2-6 Ground Screw Label • AC Receptacle. Receptacle in which to plug in a power cord; the other end will plug into an AC outlet for power. • Power Switch. Switch to turn power on and off. • Ground Screw. An earth ground screw provided to connect to earth ground using a Ground Safety Cable (if your AC power plug only has two prongs and does not have a third, grounded prong). • Label.
Chapter 2: Hardware Components Cables The cables listed in Table 2-4 are required to connect a Tenor DX to various interfaces. Contact Quintum for ordering information, if necessary. NOTE: A crossover cable is required when connecting to a Line side (PBX) interface (when supplied by Quintum, this is a red RJ-45 cable). A straight cable is required when connecting to the trunk side (PSTN) interface (when supplied by Quintum, this is a green RJ-45 cable).
Chapter 2: Hardware Components RJ-45 Ethernet Cable (10/100) An RJ-45 (10/100BaseT) straight through shielded cable is used to connect Tenor DX to an Ethernet LAN. Cable pinouts are listed in Table 2-5. Color specifications are applicable to the RJ-45 cable provided.
Chapter 2: Hardware Components RJ-45 to RJ-45 Straight Cable (T1/E1/PRI WAN to Trunk Side) An RJ-45 (T1/E1) straight cable is used to connect Tenor DX T1/E1 (1-8) port to the Trunk Side (PSTN). Cable pinouts are provided below. If this cable is provided by Quintum, the color is green. The color specifications are applicable to the RJ-45 straight cable provided.
Chapter 2: Hardware Components RJ-45 to RJ-45 Crossover Cable (T1/E1/PRI WAN to PBX) An RJ-45 (T1/E1) crossover cable is used to connect Tenor DX T1/E1 (1-8) port to the Line Side (PBX). Cable pinouts are provided below. If this cable is provided by Quintum, the color is red. The color specifications are applicable to the RJ-45 crossover cable provided.
Chapter 2: Hardware Components 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 DX to your PC’s asynchronous serial port. The pin order for DB-9 male and female connectors are shown in Figure 2-9 and Figure 2-10.
Chapter 3: Installation This chapter gives you installation instructions, as well as how to position the Tenor DX successfully within your network.
Chapter 3: Installation 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. • Do not connect equipment in wet conditions and keep away from dusty areas.
Chapter 3: Installation Rack Install Locate the Tenor DX unit within the same area as your PBX, Ethernet hub, switch, router, and/or PSTN patch panel. The chassis is intended to be installed in a 19” rack. Mounting brackets are attached to the chassis; the rack is not included with your system. Included with the chassis are the screws and clip nuts listed below. The sizes should allow installation in most racks.
Chapter 3: Installation Figure 3-1 Rack Installation (Front View) Tenor DX Rack Mounting Holes Wall Mount There are two mounting brackets available to mount the unit to the wall. Pre-installation Guidelines • Ensure the wall is level and stable. • Do not attach the unit to a temporary wall. • Ensure the wall mounting area is within cord distance of the power outlet.
Chapter 3: Installation Attach the unit to the wall as follows: 1. Determine the wall area to mount the unit. With chalk or a soft pencil, mark the install area according to Figure 3-2. NOTE: Ensure the unit is level. Figure 3-2 Wall Mounting Dimensions 3/16” 7 3/4” (19.9cm) 2. Position and attach one mounting bracket to the unit using a screw existing in the system and one screw included with the package. See Figure 3-3. 3.
Chapter 3: Installation Connection Connect to Line Interface - PBX Since there are many different PBX devices and connection methods, your individual PBX will determine the connection method you use to connect to the unit. For example, your PBX may be connected using a patch panel, punch down block, wire wrapped blocks, etc. If you are not sure about installation procedures, contact the network administrator or review the documentation you received with the PBX. Adjacent port pairs (i.e., 1/2, 3/4, etc.
Chapter 3: Installation Connect to Trunk Interface - PSTN Adjacent port pairs (i.e., 1/2, 3/4, etc.) are configured by default to connect to each other (power off bypass) when the unit is turned off, or when the unit is in Offline mode. This is the preferred method when connecting one of the lines to a PBX, and its adjacent pair to the PSTN. However, if you have adjacent port pairs that are connected to smaller devices (i.e.
Chapter 3: Installation 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 DX. Only LAN 1 is available for use; LAN 2 is reserved for future use.
Chapter 3: Installation Connect to PC Console You will need to connect the Tenor DX 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 3-7 Connect to PC Com Port 1 2 3 4 5 6 7 8 R E S E T D I A G LAN 1 Line/Act 100 LAN 2 CONSOLE POWER Line/Act 100 ALERT DB-9 1.
Chapter 3: Installation Install Ground Safety Cable (if required) The Tenor DX provides an Earth Ground screw (a #6 screw). This screw provides earth ground to the unit if the AC power receptacle you are plugging into does not contain a ground prong (the Quintum supplied power cable has a three prong connector). 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.
Chapter 3: Installation 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 power cord 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. Once the unit is powered up, you are ready to assign an IP address.
Chapter 3: Installation Assign IP Address Before you can configure a Tenor DX, you need to assign a valid IP address. When a Tenor DX 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 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. For IP Address, enter the IP address for the Tenor unit. 16. For Subnet Mask, enter the subnet mask.
Chapter 3: Installation Figure 3-10 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. The default login name is admin. 13.
Chapter 3: Installation 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.com.
Chapter 4: Getting Started: Tenor Configuration Manager/Tenor Monitor This chapter tells you how to get started configuring and monitoring the Tenor DX through the Tenor Configuration Manager and the Tenor Monitor.
Chapter 4: Getting Started: Tenor Configuration Manager/Tenor Monitor Overview The Tenor Configuration Manager is a user-friendly windows-based stand-alone GUI which enables you to configure a number of Quintum products, including the Tenor DX. The software was designed to run on any PC; you simply designate the IP address for the Tenor product (i.e., Tenor DX) on which you would like to configure or perform monitoring functions.
Chapter 4: Getting Started: Tenor Configuration Man- Tenor Configuration Manager The Tenor Configuration Manager is used to configure all aspects of the Tenor DX, including system, Ethernet, CDR, signaling, circuit, and VoIP configuration. Through the Configuration Manager, you are able to configure all aspects of the Tenor unit. The manager is a user-friendly GUI which enables you to configure Quintum products; you designate the IP address of the Tenor product you want to configure.
Chapter 4: Getting Started: Tenor Configuration Manager/Tenor Monitor Once you have connected to the Configuration Manager, you can move around and configure data. For complete information about the field definitions, valid entries, and submit information, see the VoIP Network Management Server’s User Guide or the online help system that came with the system. Tenor Monitor The Tenor Monitor enables you to view alarms for all Tenor units, as well as Call Event Records, and Call Detail Records.
Chapter 5: Getting Started: Command Line Interface (CLI) This chapter tells you how to use access and use the CLI.
Chapter 5: Getting Started: Command Line Interface (CLI) What is the Command Line Interface? The Command Line Interface (CLI) is a Telnet-based (also accessible via serial port) list of menu options which enable you to configure and monitor any Tenor DX unit; you can configure features and capabilities such as numbering plans, channel usage, border element, signaling type, and routing information. In addition, you are also able to monitor system alarms and run diagnostic procedures.
Chapter 5: Getting Started: Command Line Interface User Login IDs There are two types of user logins: user and admin. The admin level enables you to view and change information. The user level enables you to view the information but not configure via CLI. Access CLI You can access the CLI through a Telnet session, a terminal-like access to any Tenor DX unit. If your PC is directly connected to the Tenor DX unit, you can configure the unit directly through the serial port using HyperTerminal.
Chapter 5: Getting Started: Command Line Interface (CLI) Serial Port Connection When the Tenor DX is first shipped to you, you must connect to the unit using this method to assign an IP address. Once this is assigned, you can use the CLI to reach the serial port of the Tenor. A null-modem cable must be used to connect to the CLI using this port, if you are directly connected to the unit. To connect to the Tenor DX serial port, locate a workstation (PC) close to the Tenor DX unit. Connect as follows: 1.
Chapter 5: Getting Started: Command Line Interface Configuration via CLI Once you are connected to the Command Line Interface, you can configure the system, as well as perform diagnostics and monitor system information. For specific information, see the Online Help you received with the CD.
Chapter 6: Working with SNMP This chapter tells you how to use and manage Tenor DX ’s Simple Network Management Protocol (SNMP) feature, which is managed via Hewlett Packard®’s HP Openview™ Network Node Manager. Specifically, this chapter tells you how HP® OpenView auto-discovers a Tenor DX unit, as well as generate SNMP traps for existing alarm messages.
Chapter 6: Working with SNMP What is SNMP? Simple Network Management Protocol (SNMP) is the standard protocol used to exchange network management information. SNMP management requires two primary elements: a network manager and an SNMP agent. A network manager is the software running on a workstation through which the network administrator monitors and controls the different hardware and software systems that comprise a network.
Chapter 6: Working with SNMP Installation There are two steps you need to accomplish before HP Openview can interact with a Tenor DX unit as an SNMP agent. • Download and install HP Openview configuration files specific for Tenor DX • Configure the IP address of the network manager in the Tenor DX Download and install SNMP-Related Files For HP Openview (network manager) to view and manage the Tenor DX as an SNMP agent, you must first download and install files from the www.quintum.
Chapter 6: Working with SNMP • These lines are added to the file HPOVRoot\conf\oid_to_sym: 1.3.6.1.4.1.6618.1.1.1:Connector:QDVOIP # QUINTUM Digital Tenor 1.3.6.1.4.1.6618.1.1.2:Connector:QAVOIP # QUINTUM Analog Tenor 1.3.6.1.4.1.6618.1.1.10:Connection:QCVOIP # QUINTUM Chassis Tenor • These lines are added to the file HPOVRoot\conf\oid_to_type: 1.3.6.1.4.1.6618.1.1.1:Quintum:Epilogue:H # Quintum-Digital Tenor 1.3.6.1.4.1.6618.1.1.2:Quintum:Epilogue:H # Quintum-Analog Tenor 1.3.6.1.4.1.6618.1.1.
Chapter 6: Working with SNMP 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.ico • The quintum.fields file is added to the HPOVRoot\fields\C directory, and is installed and verified using the "OVW -fields" command. • The quintum.reg file is added to the HPOVRoot\registration\C directory.
Chapter 6: Working with SNMP 2. Type telnet in the Open box and click on Ok. The Telnet GUI will launch. 3. Click Connect> Remote System. 4. In the Host Name window, enter the IP address of the unit from which you would like to view alarms. 5. In the port window, choose telnet (port 23 is the default port for a telnet session). 6. From the TermType drop down list, select vt100. 7. Click Connect. A telnet session will be displayed. (To exit a telnet session at any time, type exit at the prompt.) 8.
Chapter 6: Working with SNMP Working with SNMP View traps You can view the traps HP Openview received from the Tenor DX unit as follows: NOTE: Ensure HP Openview is running. 1. From the HP Openview map where the Tenor DX units appear, right-click on the Tenor DX 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: Working with SNMP 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 DX unit icon and select Quintum Digital. The CLI will launch with the IP address of the unit associated with that icon (the correct IP address will appear in the URL). 2. Configure the unit. OR Launch CLI by double-clicking the icon as follows: 1.
Chapter 6: Working with SNMP 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. Only one window can be opened at a time.
Chapter 7: Call Detail Recording This chapter tells you how to display and understand the Call Detail Recording (CDR) feature. Examples are included later. Specifically, the following topics are included.
Chapter 7: Call Detail Recording Overview There are two ways to view CDRs for the Tenor DX unit: through the Command Line Interface (CLI) or through Tenor Monitor. The information for accessing CDRs via CLI is detailed in this chapter: see the Tenor Configuration Manager/ Tenor Monitor User’s Guide for information about viewing alarms via Tenor Monitor.
Chapter 7: Call Detail Recording 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 DX unit is able to generate a CDR at the completion of each call. CDRs are collected from multiple Tenor DX units simultaneously and continuously. A CDR file can be created each day to collect CDRs from each Tenor DX that connects to the server.
Chapter 7: Call Detail Recording Establish connection between Tenor DX and CDR Server In order to capture CDRs, a connection between the Tenor DX unit and the CDR server must be established. A Tenor DX can be configured to connect up to two CDR servers via port 9002, 9003, 9004, and 9005. Based on configuration, the Tenor DX unit can either establish a TCP/IP session with one or all of these CDR servers. A flow diagram (Figure 7-1) illustrates the general transfer of information.
Chapter 7: Call Detail Recording Configure Tenor DX for connection to CDR Server NOTE: The CDR Server software is a Windows-based .exe file available on the CD you received with your system; this software is not supported by Quintum. 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.
Chapter 7: Call Detail Recording Tenor DX Establishes Connection with CDR Server To capture CDR reports via CDR server (i.e., a PC or workstation you use to capture CDR data) you must first configure the IP address and port number of the CDR server in the Tenor DX unit. Once these are configured, the Tenor DX unit will be able to establish a TCP/IP session with the server on its own.
Chapter 7: Call Detail Recording 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 7: Call Detail Recording Called #: The number called. This will be in international format except for a pass-through call going from PBX to PSTN or call going from PSTN to PBX. Duration: Call duration. This value is in seconds, the value will be 0 if never connected. Call Initiation Time: The date and time the call initiated. The time will be the local time configured on the Tenor DX unit.
Chapter 7: Call Detail Recording Remote IP Address: IP address for the remote destination Tenor DX. This will be generated only if the call is VoIP; if the call is circuit based, this field will be blank. The entry will be in the following format: xxx.xxx.xxx.xxx. Origination Trunk ID: Identifies the origination trunk ID of the line that initiated the call. This field will be blank if no trunk ID is configured. The trunk ID is often configured with an account code. Call Type: The type of call.
Chapter 7: Call Detail Recording Sample Record for Extended Tenor DX 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.1 0.
Chapter 7: Call Detail Recording Disconnect Cause Code: The Q.931 cause value assigned if the call is not connected. Possible common entries are listed below. This field will be blank if the call was connected. Cause Code Definitions 16 Normal Call Clearing. The cause indicates that the call is being cleared because one of the users has requested that the call be cleared. 17 User Busy.
Chapter 7: Call Detail Recording Outgoing Slot: If the call is outgoing, this field identifies the slot the call is going out on. This entry is fixed at 2. Outgoing Device. If the call is outgoing, this field identifies the Device the call is going out on. This field is fixed at 0. Outgoing Digital Interface. If the call is outgoing, this field identifies which Digital Interface the call is going out on. Valid entry: 1 = PBX, 2 = PSTN. This field will be empty if the call is an outgoing VoIP call.
Chapter 8: System Alarms This chapter tells you how to use the Alarm Manager to view and understand alarms generated by the system.
Chapter 8: System Alarms Overview There are two ways to view alarms for the Tenor DX unit: through the Command Line Interface (CLI) or through Tenor Monitor. The information for accessing alarms via CLI is detailed in this chapter: see the Tenor Configuration Manager/Tenor Monitor User’s Guide for information about viewing alarms via Tenor Monitor.
Chapter 8: System Alarms Field Definition Valid Entry Severity Level or alarm severity. 1 = Critical (complete system is affected). 2 = Major (major problem is detected). 3 = Minor (minor problem is detected). 4 = Info (Information about a minor problem). Description A text description of the alarm; see Table 8-2 for detailed description. Varies. Slot # Defines which slot the alarm occurred on. Slot 1 or 2. Slot 1 refers to the system controller functions; slot 2 refers to DSP functions.
Chapter 8: System Alarms 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 8: System Alarms Severity Alarm Description (appears as part of severity field) Critical Definition (text appears in desc field) IVR Configuration Missing Appears if an attempt to make an IVR call has been made when a valid IP address is not configured. Occurs if an IVR call has been passed through accidently, without a real intention to use IVR for subsequent calls, while both of the servers were disabled.
Chapter 8: System Alarms Severity (appears as part of severity field) Alarm Description (text appears in desc field) Definition Minor Hardware component failed A hardware component has failed. Check all components, hardware connections, etc. Minor 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 8: System Alarms View Alarms The Command Line Interface (CLI) enables you to view alarms through the Monitor mode. You can view active alarms, as well as view an alarm history list. You are now ready to view active alarms and an alarm history, or both. See the sections which follow: Display all Alarms You are able to display both active alarms and an alarm history as follows: 1. Through CLI, access the Monitor prompt. 2. Type alarm. Both active alarms and the alarm history will be displayed.
Chapter 8: System Alarms Display Alarm History 1. Through CLI, access the Monitor prompt. 2. Type alarm h. An alarm history will be displayed. 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 8-3 Alarm History Sample IP# Sequence#Type#Severity# Desc# Slot# Device# Digital Interface# Channel# Date/Time 192.168.20.136:947:ALR:1:Yellow Alarm:1:0:1:0:THU APR 14 00:00:04 2016 192.168.20.
Chapter 9: Diagnostics/Maintenance This chapter tells you how to troubleshoot Tenor DX operation, as well as how to maintain the health of your system. You will find information about how to view the unit’s LEDs, as well as how to interpret the chassis’ alarms and check basic connections.
Chapter 9: Diagnostics/Maintenance Before you Begin 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. If the unit is not working, toggle the power switch to reset the system. If the unit is reset, the settings you configured may be lost.
Chapter 9: Diagnostics/Maintenance Diagnostics Common Symptoms/Problems Below is a list of common symptoms and problems you may encounter. Use this list as a guideline; if your problem is not listed, use the diagnostic procedure explained in the beginning of this chapter. Table 9-1 Common Symptoms/Problems Common Symptom/Problem Description/Solution Unit will not turn on. Check AC power source. Communication between Tenor DX and the PBX or PSTN cannot be established.
Chapter 9: Diagnostics/Maintenance Common Symptom/Problem Tenor DX cannot receive or transmit calls. Description/Solution Check DS1 card Span Status LEDs. If unlit, it indicates that the T1 or E1 lines may be down. Generate alarm list for more information. Contact Central Office for interface issues. For DC only: The breaker trips due to excessive current. Power on/off using the circuit breaker. Verify Unit Provisioning An error with Tenor DX‘s provisioning may cause a number of problems.
Chapter 9: Diagnostics/Maintenance Monitoring Alarms Alarms help you identify where a specific problem is occurring with the Tenor DX unit. Through the CLI, you can review alarms via Command Line Interface (CLI). Verify all severity 1 alarms first; these alarms indicate that the unit is in critical condition and the entire system is affected. See Chapter 8: System Alarms for specific information about obtaining and reading alarms.
Chapter 9: Diagnostics/Maintenance Change Unit Date and Time You can change the unit’s date and time via Command Line Interface (CLI) as follows: 1. Access the CLI through a Telnet session. See Chapter 5: Getting Started: Command Line Interface (CLI) for more information. 2. Access the Config module. 3. Type date followed by mm/dd/yy/hh:mm:ss and press Enter. 4. For example, type config# date 06/14/02/22:14:00. This command will set the current time to June 14, 2002 at 10:14 p.m.
Chapter 9: 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. 71 James Way Eatontown, NJ 07724 For domestic calls: (877) 435-7553 For international calls: (732) 460-9399 email: service@quintum.
Chapter 10: Using IVR This chapter tells you how to use the Interactive Voice Response (IVR) system. You will find information about configuring IVR as well as a description of the RADIUS server.
Chapter 10: Using IVR What is IVR? Interactive Voice Response (IVR) is a feature of the Tenor DX that enables you to offer services, such as Prepaid calling cards and Post-paid accounts to your customers. The Tenor DX uses the RADIUS (Remote Authentication Dial-In User Service), for authenticating and authorizing user access to the VoIP network.
Chapter 10: Using IVR ANI Authentication There are two types of ANI Authentication supported in the Tenor DX: 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 10: Using IVR Typical IVR Network Connection/Process See Typical Network Connection/Call Flow Process for a typical network configuration for IP based pre-paid calling card/post-paid account services. This figure illustrates the originating Tenor DX is configured to provide pre-paid/post-paid services. All the subscribers will have to dial into this Tenor DX via PSTN to get access to pre-paid/post-paid services.
Chapter 10: Using IVR 3 RADIUS server acknowledges start accounting request. Start Accounting is optional. 4 Tenor DX prompts the subscriber for the card number. 5 Caller enters the card number. 6 Tenor DX sends the card number to the RADIUS server for verification. 7 RADIUS server returns the credit balance for the account. 8 Tenor DX plays the credit amount and prompts the subscriber for the destination number. 9 Caller enters the destination number.
Chapter 10: Using IVR Configure IVR - Quick Start For a Tenor DX to be used as part of the complete IVR system, and communicate effectively with the RADIUS, you must configure basic options in the Tenor DX 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 10: Using IVR Configure Voice Prompts What is a Voice Prompt? 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 are stored internally 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 10: Using IVR 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. destination “destination number” [enter] + [destination] + [pound_key] Please enter your destination number followed by the pound key.
Chapter 10: Using IVR invalid “You have entered an invalid number.” - - language “for English press” [lang] + [one] For English press one. minute “minute” - - minutes “minutes” - - next call_ pound “To make another call press the star key twice.” - - next call_star “To make another call press the pound key twice.” - - nine “nine” - - nineteen “nineteen” - - ninety “ninety” - - no_funds “You have insufficient funds in your account.
Chapter 10: Using IVR seventeen “seventeen” - - seventy “seventy” - - six “six” - - sixteen “sixteen” - - sixty “sixty” - - ten “ten” - - thirteen “thirteen” - - thirty “thirty” - - thousand “thousand” - - three “three” - - twelve “twelve” - - twenty “twenty” - - two “two” - - wait “Thank you. Please hold.” - - welcome “Welcome!” - - yen “yen” - - you_have “You have” [you_have] + [] + [remaining] You have six cents remaining.
Chapter 10: Using IVR Call Flow - Specifications Pre-paid Calling Card - Call Flow (with default language) Pre-paid Calling Card - Call Flow (default language) 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 DX. The Tenor DX performing the IVR functions. RADIUS Server.
Chapter 10: Using IVR Figure 10-2 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 CONNECT DISC
Chapter 10: Using IVR Post-paid Calling Card - Call Flow (with default language) Post-paid Account - Call Flow (default language) 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. The Tenor DX performing the IVR functions. RADIUS Server.
Chapter 10: Using IVR Figure 10-3 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 STOP ACCOUNTI
Chapter 10: Using IVR Pre-paid and Post-paid Calling Card - Call Flow (with multiple language support) Pre-paid and Post-paid Calling Card - Call Flow (multiple language support) 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 DX performing the IVR functions. RADIUS Server.
Chapter 10: Using 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 DX asks if the caller wants another call; the user can then press the designated key.
Chapter 10: Using IVR Figure 10-5 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 Destination Number AUT
Chapter 10: Using 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 10: Using IVR Figure 10-6 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-0049-00-10 10-19
Chapter 10: Using 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 DX asks PIN number by prompt) and (3) Incoming packet has the ANI, but authentication with the ANI fails and Tenor DX prompts for the PIN number.
Chapter 10: Using IVR Figure 10-7 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 IP LEG STOP AC
Chapter 10: Using 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 10-3 lists the message attributes in the Start Accounting Request message packet sent between the Tenor DX and the RADIUS server. Start Accounting is optional.
Chapter 10: Using IVR Stop Accounting Request Message Attributes Table 10-4 lists the message attributes in the Stop Accounting Request message packet sent between the Tenor DX and the RADIUS server.
Chapter 10: Using IVR 10-24 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 Number
Chapter 10: Using IVR Authentication Request Message Attributes Table 10-5 lists the message attributes in the Authentication Request message package sent between the Tenor DX and the RADIUS server.
Chapter 10: Using 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 DX Numeric 27 Authorization Request Message Attributes Table 10-7 lists the message attributes in the Authorization Request message packet sent between the Tenor DX and the RADIUS server.
Chapter 10: Using IVR Authorization Response Message Attributes Table 10-8 lists the message attributes in the Authorization Response message packet sent between the Tenor DX and the RADIUS server.
Appendix A: Specifications/Approvals A-1 P/N 480-0049-00-10
Appendix A: Specifications/Approvals Voice/Fax Call Routing: Coding: Voice Algorithms: Fax Support: Automatic Call Detection: Line Side Interface/Trunk Side Interface A-law, u-law G.723, G.723.1A (5.3, 6.3 Kbps), G.726 (16, 24, 32, 40 Kbps), G.729, G.711 Group III at 2.4, 4.8, 7.2, 9.6, 12, 14.4 Kbps Voice/Modem/Fax Line Side (PBX) / Trunk Side (PSTN) Connections Interface: T1/E1 Signaling: Impedance: Jack: A-2 T1/E1 and Fractional T1/E1 with a built in CSU.
Appendix A: Specifications/Approvals LAN Connection LAN Support: Connection Type: 10/100 Mbps Ethernet Full Duplex/Half Duplex Physical Position: Depth: Width Height: Weight 19” (48.7 cm) rack mountable or wall-mountable 10 3/4” (27.6 cm) 17 3/8” (44.5 cm) 1 3/4 ” (4.5 cm) 7.2 lbs (3.24 kg) Electrical Ethernet: PBX/PSTN Connectors Console Port: Power Standard 10/100Base-T RJ-45 interface (IEEE 802.3) Standard RJ-45 8 RJ-45 connectors for T1/E1 connection to the PBX and the digital network.
Appendix A: Specifications/Approvals Agency Approvals A-4 EMC FCC Part 15, Class A ICES-003 AS/NZS 354:95 EN55022:98 Class A EN55024:98 EN61000-3-2:95 EN61000-3-3:95 TELECOM FCC Part 68 CS-03 TS016 TS038 TBR4 ISDN Layer4 SAFETY UL/cUL 60950 EN60950:92 TS001 P/N 480-0049-00-10
Appendix A: Specifications/Approvals 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.
Appendix A: Specifications/Approvals The Telephone Company may make changes in its facilities, equipment, operations, or procedures that could effect the operation of the equipment. If this happens, the Telephone Company will provide advance notice in order for you to make necessary modifications to maintain uninterrupted service.
Appendix A: Specifications/Approvals 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.
Appendix A: Specifications/Approvals DECLARATION OF CONFORMITY Application of Council Directives(s) 89/336/EEC, 93/68/ECC EMC Directives 73/23/EEC, 96/68/ECC Low Voltage Directives 99/5/EC, RTTE Directive Standards to which Conformity is Declared: EN55022:98, EN55024:98 EN 60950:92 +A1:92+A2:93+A3:95+A4:96 EN 61000-3-2 :95, EN 61000-3-3:95 FCC Part 68, FCC Part 15 Class A CS-03, ICES-003 Issue 3, TS001, TS016:2/34, TS038, AS/NZS 354:95 TBR4 ISDN Layer 1-3 Manufacturer: Quintum Technologies Inc.
INDEX A About this guide 1-1 Alarms 8-2 definition 9-5 display via CLI 8-7 field definitions 8-2 green 6-7 list of 8-4 monitor 8-2 orange 6-7 red 6-7 white 6-7 yellow 6-7 B Back panel 2-6 AC receptacle 2-6 ground screw 2-6 label 2-6 power switch 2-6 Bypass DN 1-10 C Cables 2-7 AC power cord 2-7 DB-9 2-11 RJ-45 2-7, 2-8 Call 1-11 Call management 1-11 hop-off PBX 1-11 passthrough support 1-11 public/private dial plan 1-11 trunk group support 1-11 Call Routing 1-8 Capabilities call routing 1-8 CDR 1-6 data net
ports 1-8 2-2 reset 2-2 G Ground Safety Cable install 3-10 H H.
T Tenor Configuration Manager 4-3 Tenor DX VoIP MultiPath Switch capabilities 1-6 description 1-2 product types 1-3 What is Tenor DX MultiPath Switch 1-2 Tenor Monitor 4-4 getting started 4-4 Troubleshoot common problems 9-3 general maintenance 9-5 monitor LEDs 9-2 unit provisioning 9-4 typographical conventions 1-3 U UPDP 1-11 Upgrade 3-15 W Wall mount install dimensions 3-5 installation 3-4 required materials 3-4 480-0049-00-10 Index-3
GLOSSARY A Alarm. A brief message that appears on your screen when the Tenor DX encounters a problem (i.e., failed interface). Alarms can be viewed through CLI (see Command Line Interface) or a Telnet connection. Auto Switching. If a network packet delay for an IP call becomes unacceptable, the Tenor DX will automatically switch the call to PSTN. B Border Element. Provides access into or out of an administrative domain. The Tenor DX has two types of Border Elements: Primary and Secondary. Bypass Number.
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. Interactive Voice Response enables you offer services, such as Pre-paid calling cards and Post-paid accounts to your customers. L LAN. Local Area Network. A local area network that carries data between workstations in the same location. Workstations in a LAN are connected together— typically by an Ethernet hub— to share information. LEDs.
Zone. A group of endpoints (e.g, gateways, terminals, etc.) in one corporate site.
WARRANTY 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.
