Product Guide
P/N 480-0003-00-13
Tenor VoIP MultiPath
Switch
A400/A800
Tenor MultiPath Gateway, PacketSaver, Quintum, Quintum Technologies, Inc., VoIP Made Easy, Select Net Technology, are trademarks of Quintum Technologies, Inc.
T
able of Contents
About this Guide
What’s included? . . . .1-2 Typographical Conventions . . . .1-3 Product Guide Conventions . . . .1-3 Finding Help. . . .1-4
Chapter 1: Overview
What is Tenor VoIP MultiPath Switch? . . . .1-2 Typical Implementations . . . .1-3 Intranet Implementation . . . .1-4 Extranet Implementation . . . .1-5 Internet Implementation . . . .1-6 Features. . . .1-7 Unique Design . . . .1-7 State-of-the-Art Configuration and Network Management. . .1-7 SelectNet™ Intelligence. . . .1-8 Uninterrupted Service . . . .1-8 Dynamic Call Routing . . . .1-8 Multiple Lines/Signaling Supported . . . .1-8 Easy Connect to Console . . . .1-9
Other Call Routing Options . . . .1-14 PacketSaver™ . . . .1-15 NATAccess™. . . .1-15 Virtual Tie Line . . . .1-16 Hop-off PBX Call . . . .1-16 SNMP Support . . . .1-16 Flexible Networking Capabilities . . . .1-17 Interoperability . . . .1-18
Chapter 2: Hardware Components
Hardware Description . . . .2-2 Front Panel Connection and Reset Options . . . .2-2 Front Panel PBX/PSTN Port Assignment . . . .2-3 Front Panel LEDs. . . .2-4 Back Panel. . . .2-7 Cables . . . .2-7
Chapter 3: Installation
Before you Begin . . . .3-2 View Current Network Architecture . . . .3-2 Installation . . . .3-3 Pre-Installation Guidelines . . . .3-3 Inspect Package Contents . . . .3-3 Position the Unit. . . .3-3 Connect the Unit . . . .3-10 Power up the System. . . .3-15 Assign IP Address . . . .3-16
Release Notes . . . .3-21 Other Software. . . .3-21 Load Upgrade software . . . .3-22 Before you begin . . . .3-22 Load the Software . . . .3-22
Chapter 4: Getting Started: Command Line Interface (CLI)
What is the Command Line Interface? . . . .4-2Options. . . .4-2 User Login IDs . . . .4-2 Access CLI. . . .4-3 Telnet Connection . . . .4-3 Configuration via CLI . . . .4-4
Chapter 5: Working with SNMP
What is SNMP? . . . .5-2 How does Tenor utilize SNMP? . . . .5-2 Installation Requirements . . . .5-3 Installation . . . .5-4 Download and Install SNMP Related Files . . . .5-4 Configure network manager IP address . . . .5-7 Working with SNMP. . . .5-10
How to Read Alarms . . . .6-2 Valid Alarms. . . .6-5 View Alarms via Telnet . . . .6-8 Establish Connection . . . .6-8 UNIX . . . .6-9 Display Active Alarms . . . .6-10 Display Alarm History. . . .6-11 Filter Alarm History . . . .6-12 Delete Alarms . . . .6-13 Exit Alarm Manager . . . .6-13
Chapter 7: Call Detail Recording
Overview . . . .7-2 Establish connection between Tenor and CDR Server . . . .7-3 Tenor Establishes Connection with CDR Server . . . .7-4 CDR Server Establishes Connection with Tenor . . . .7-5 CDR Output . . . .7-6
Chapter 8: Using IVR
What is IVR? . . . .8-2 IVR Call Types . . . .8-3 ANI Authentication . . . .8-4 Multi-session . . . .8-4 Typical IVR Network Connection/Process . . . .8-6 Configure IVR - Quick Start . . . .8-9 Basic IVR Data (via Trunk Group) . . . .8-9 IVR Prompt Server. . . .8-9
Voice Prompt Requirements (English Requirements) . . . .8-12 Create Voice Prompt Files . . . .8-17 Update IVR Voice Prompts . . . .8-18 Configure IVR via CLI . . . .8-19 View RADIUS statistics . . . .8-20 Display RADIUS statistics . . . .8-20 Clear RADIUS statistics . . . .8-21 Call Flow - Specifications. . . .8-22 Pre-paid Calling Card - Call Flow (with default language) . . .8-22 Post-paid Calling Card - Call Flow (with default language) . .8-24 Pre-paid and Post-paid Calling Card - Call Flow (with multiple language support) . . . .8-26 Pre-paid and Post-paid Calling Card - Call Flow (with Multi-Session Call support) . . . .8-28 ANI Authentication Application Type 1 - Call Flow. . . .8-30 ANI Authentication Application Type 2 - Call Flow. . . .8-32 Call Flow - Message Attributes . . . .8-34 Start Accounting Request Message Attributes . . . .8-34 Stop Accounting Request Message Attributes. . . .8-36 Authentication Request Message Attributes . . . .8-39 Authentication Response Message Attributes . . . .8-40 Authorization Request Message Attributes . . . .8-41
Common Symptoms/Problems . . . .9-5 Restore Factory Defaults . . . .9-7 Change Password . . . .9-8 Reset System . . . .9-9 Reset via Front Panel . . . .9-9 Set the Unit to Online mode. . . .9-10 View System Information . . . .9-11 If you need Additional Help . . . .9-11
Appendix A: Cables
Appendix B: Specifications/Approvals
Appendix C: VoIP Terms/Advanced Topics
GLOSSARY
INDEX
Warranty
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 how our products fit into the VoIP network.
• Chapter 2: Hardware Components: Hardware description.
• Chapter 3: Installation. Describes how to install the Tenor unit, including how to set the IP address.
• Chapter 4: Getting Started: Command Line Interface. This chapter describes how to connect to the CLI.
• Chapter 5: Working with SNMP. This chapter describes the SNMP protocol and how to use it with the Tenor unit.
• Chapter 6: System Alarms. Describes how to use the Alarm Manager and tells you how to view alarms via telnet session.
• Chapter 7: Call Detail Recording. Describes the CDR feature, including how to display and read CDRs.
• Chapter 8: Using IVR. Describes the IVR feature, including a quick start and how to configure voice prompts.
• Chapter 9: Troubleshooting/Maintenance. Describes how to troubleshoot and monitor the health of the system.
• Appendix A: Cables. Cable pinout information.
• Appendix B: Specifications/Approvals: List of Tenor’s specifications and approvals.
• Appendix C: Getting Acqainted with VoIP. A general overview of VoIP and how it relates to the Tenor unit.
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).
• All pull down menu options, figure references, and table references appear in italics (i.e., Choose File> Open).
• There are three types of special text that are designed to reveal supplemental information: Note, Warning, and Caution. See below.
A NOTE provides additional, helpful information. This information may tell you how to do a certain task or just be a reminder for how-to’s given in previ-ous sections. (i.e., For a list of valid commands at any time, type ?)
A WARNING provides information about how to avoid harm to your VoIP equipment or other equipment. (i.e., Do not stack more than 4 units together.) A CAUTION provides information about how to avoid injury to yourself or to others. (e.g., Do not install the equipment during a lightning storm.)
Finding Help
Refer to this user guide for help. The table of contents and index tells you where to find information easily; the glossary gives you specific terms. See Appendix C: VoIP Terms/Advanced Topics for detailed information about VoIP terms and con-cepts.
C
hapter 1: Overview
This chapter gives you a general overview of the Tenor MultiPath Switch Analog series, including feature descriptions and capabilities. You can also find informa-tion about the organizainforma-tion of this Product Guide.
Specifically, the following topics are covered:
A description of Tenor A400/A800 units
Typical implementationsWhat is Tenor VoIP MultiPath Switch?
The Tenor VoIP MultiPath Switch A400/A800 is a VoIP (Voice over Internet Proto-col) H.323/SIP standard analog gateway that transmits voice and fax data over the IP network. It can connect to the PBX, telephone, key system and PSTN via analog lines (the A400 provides four analog lines; the A800 provides eight analog lines). It connects to the IP via 10/100 Mbps ethernet connection.
Tenor Analog is the first VoIP analog gateway that intelligently switches calls over both the IP network and the PSTN in order to ensure high voice quality and call reliability. It functions as a gateway and a gatekeeper. The gateway converts circuit switched calls to VoIP calls; the gatekeeper performs IP call routing functions.
Figure 1-1 Tenor Analog MultiPath Switch
Quality of service is virtually guaranteed. The SelectNet
™
Technology provides a “safety net,” which monitors the network packet delay for an IP call. If the delay becomes unacceptable—according to the specifications you assign— the call will be switched to the PSTN automatically. The unit’s simple plug and play embedded system architecture brings VoIP technology to your network without changing your existing PBX and telephone desk set. Your network configuration stays as is. The call type is transparent to the user. This technology boasts practically free voice without compromising quality and reliability.
Tenor Analog MultiPath Switch Analog Series is available in two versions: • Analog MultiPath Switch A400 (provides 4 analog lines/4 simultaneous
VoIP conversations)
• Analog MultiPath Switch A800 (provides 8 analog lines/8 simultaneous VoIP conversations)
Typical Implementations
The Tenor Analog unit can utilize private and public IP networks to bypass the PSTN anywhere in the world. Call routing from many different locations makes it ideal for enterprises and institutions with remote locations. For example, Tenor supports Intranet, Extranet, and Internet implementations. Intranet communication is communication within the same company; Extranet communication is communi-cation with a source outside of your company. Internet communicommuni-cation is commu-nication running over the public IP network. Each implementation type is defined in the sections which follow.
Intranet Implementation
The Tenor unit enables Intranet communication by transmitting data within a cor-porate data network. The Gateway functionality enables data to be sent out through a corporate LAN to reach other Gateways at separate sites. Packetized voice data is sent between intra-corporate sites without passing through the PSTN. The Gate-keeper functionality enables the two units within the same company to communi-cate.
For an illustration of intra-corporate communication, see Figure 1-2.
Figure 1-2 Intranet Tenor Implementation
Data Network Router T C P /IP PSTN Analog Et hernet PBX Analog Company X (California)
Company X (New York)
Company X (Tokyo) Company X (France) LAN 1 LAN 4 LAN 2 LAN 3
Extranet Implementation
Another application example is the Tenor unit’s ability to connect calls between two different companies (e.g., suppliers, distributors, etc.) A unit is placed at each corporate site, transmitting corporate data between companies.
Figure 1-3 Extranet Tenor Implementation
Data TC P/IP PSTN Analog Ethernet PBX Analog Data Network Router TC P/IP PSTN Analog Ethernet PBX Analog
Company X (New York)
Data
Internet Implementation
The Internet is a packet switched network. When you place a call, your voice is digitized into packet signals and transmitted over the World Wide Web.
Figure 1-4 Internet Tenor Implementation
Data Network Router TC P/IP PSTN Analog Et hernet PBX Analog Your Company Internet
Features
The Tenor’s specific features are explained below.
Unique Design
The Tenor unit packs powerful VoIP features into one compact unit. The system’s embedded design enables you to configure the unit directly without depending upon another operating system; it is all delivered in one 19” rack mountable unit.
State-of-the-Art Configuration and Network Management
Just plug and go. Through the Command Line Interface (CLI) you are able to set specific configuration options that will help you further maximize Tenor’s capabil-ities.
SelectNet™ Intelligence
SelectNet is the next generation of TASQ technology. If the network packet delay for an IP call becomes unacceptable—according to the delay jitter and packet loss specification you configure—Tenor will transparently switch the call to the PSTN automatically, without callers even knowing. This feature virtually guarantees that each call going VoIP will be not only routed successfully, but will deliver high quality sound.
Uninterrupted Service
If power is lost to the Tenor for any reason, or the unit is down, all call routing operations will bypass the unit. This means that the Tenor unit will be ignored and all calls will “bypass” the unit and route successfully to reach the PSTN or PBX.
Dynamic Call Routing
The Tenor unit’s call routing capabilities are state-of-the-art. Voice and fax calls are transmitted through the 10/100 Ethernet LAN and routed out to the corporate WAN. Tenor will first identify the call origination site —PBX, PSTN or Data Net-work—and then route it according to the parameters or defaults you configure in the routing database.
Multiple Lines/Signaling Supported
The Tenor unit can support up to eight analog lines, which means you can support up to eight simultaneous VoIP calls, depending upon your needs.
The PBX ports implement the FXS interface (a telephone, key system or PBX can be connected directly to these ports); the PSTN ports implement the FXO interface (for direct connection to the Central Office).
In addition, the Tenor unit supports Loop Start and Ground Start signaling for incoming and outgoing calls.
Easy Connect to Console
Plugging a DB-9 cable into the unit’s asynchronous RS-232 port will connect the unit and get you up and running. Through this port, you are able to configure an IP address for your unit.
Call Control Management
Through the Tenor Analog, you have a choice through the Command Line Inter-face (CLI) of choosing either H.323 or SIP as the call control protocol. See below for a description of each.
H.323 Gatekeeper Call Control Management. The unit’s H.323 gatekeeper per-forms IP call routing functions which comply to the H.323 industry specifications for voice control and management. The Tenor’s Gatekeeper performs call routing functions for calls entering and exiting a site.
H.323 endpoints in the same zone register with the Tenor’s gatekeeper. When reg-istration is complete and a call is originated, the call request is sent to the gate-keeper. The call request provides the gatekeeper with the dialed number and requests bandwidth, authentication, and routing information. The gatekeeper con-firms the dialed number, authenticates the call, verifies the bandwidth is available, and supplies the endpoint with the destination IP address.
Tenor supports the use of two Gatekeepers, a primary and secondary. If communi-cation with the primary Gatekeeper is lost, the Tenor will register with the second gatekeeper.
The primary function of the border element is to collect, manage, and distribute call routing information. The Border Element functionality is built into each Tenor. SIP Call Control Management. SIP (Session Initiation Protocol) is a signaling
SIP is Transport layer-independent, which means it can be used with any transport protocol: UDP, TCP, ATM, etc. It is text-based, so it requires no encoding/decoding like H.323. And SIP supports user mobility, using proxies and redirecting requests to your current location.
Powerful System Monitoring
There are many different ways to monitor the health of the unit, including LEDs and alarms.
LEDs are on the front of the unit to indicate the status of the corresponding port. LEDs light up according to a function the port is experiencing. For example, if one PBX port is active, the LED will light as green.
Internal alarms indicate there is a problem with the unit. Through the Command Line Interface (CLI), you can view active system alarms. Each alarm tells you spe-cifically what problem the unit is encountering.
Call Detail Recording
Through the Call Detail Recording (CDR) feature, the Tenor unit is able to gener-ate a CDR at the completion of each call. A CDR is a string of data which contains call information such as call date and time, call length, calling party and called party. From this information you can capture billing type data, which can be used to create billing reports.
Interactive Voice Response (IVR)
Interactive Voice Response (IVR) enables you to offer services, such as Pre-paid calling cards and Post-paid accounts to your customers. The Tenor uses the RADIUS (Remote Authentication Dial-In User Service), for authenticating and authorizing user access to the VoIP network. The RADIUS is a standard protocol which provides a series of standardized messages formats for transmitting and receiving dialed information, account data and authorization codes between the network access gateway and the billing server.
PPPoE
The Tenor supports PPPoE (Point-to-Point Protocol over Ethernet), which is a pro-tocol used for encapsulating PPP frames into Ethernet frames; it creates the con-cept of a “session” over the Ethernet and provides residential and small business DSL (Digital Subscriber Link) broadband internet access.
A PPPoE session consists of two peers communicating over the Ethernet through a progression of messages such as Initiation, Discovery (Offer/Request/Session) and Termination. Using PPPoE enables dynamic IP addresses, along with a unique ses-sion ID for the connection.
Capabilities
The Tenor’s specific capabilities are explained below. PBX Calls
Calls coming from a PBX are routed to either the data network or the PSTN. The decision is made by Tenor based on the information you configure. For example, you can configure certain calls to always go to the PSTN. Any calls not configured to go to the PSTN will attempt to find a destination on the IP network. If a call can-not be completed by a unit’s gatekeeper, the call will be routed to the PSTN. Tenor is transparent to the PBX and PSTN switch. There is no need to configure or change your PBX, desk set or local PSTN switch.
Figure 1-5 PBX Call Routing
Ethernet LAN PSTN OR PBXPSTN Calls
Calls coming from the public network (PSTN) are unconditionally routed to the PBX. The Tenor unit transparently passes the call through to the PBX.
Figure 1-6 PSTN Call Routing
Data Network Calls
Calls coming from the data network can be routed to the PBX (for intra-corporate calls) or the PSTN (for Hop-off PBX calls supported). Tenor will route the call based on the dialed phone number. If the number is configured as a local phone number, the call will be sent to the PBX, otherwise the call is considered a “Hop-off PBX call” and the Tenor unit sends it out through the PSTN.
Figure 1-7 Data Network Call Routing
PBX PSTN Call PSTN Call OR PBX
(for intra-corporate) (for Hop-off calls
Other Call Routing Options
There are several routing tables you can configure through the Command Line Interface (CLI) to adjust how Tenor routes specific calls. For example, you may want to configure 911 as a “bypass number,” which means that all 911 calls coming into a Tenor unit will be routed directly to the PSTN.
There are three types of routing databases you can configure: Bypass Phone Num-bers (BPN), Local Directory NumNum-bers (LDN), and Hop-off PBX NumNum-bers. BPN numbers are directly routed to the PSTN. LDN numbers are phone numbers for either a common trunk group or for each analog line within that trunk group. Hop-off PBX numbers are phone numbers which can be routed over the IP network to another location and then out to the PSTN as a local call.
PacketSaver™
PacketSaver packet multiplexing technology reduces the amount of IP bandwidth require to support multiple calls flowing between two networks. PacketSaver mini-mizes 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 samples. As a result, it eliminates the transmission of redundant information.
Larger packetization helps reduce the bandwidth required for each VoIP call. This reduction in bandwidth lessens demand on routers, which decreases the possibility of dropped packets. It also reduces the possibility of packet loss that occurs with packet-based calls in congested networks.
.
NATAccess™
Tenor using PacketSaver to Minimize Bandwidth Usage
Conventional VoIP Transmission Sends Many Redundant Packet Headers
Figure 1-8 Tenor with NATAccess Deployment
Virtual Tie Line
The Tenor unit can emulate any 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, which results in considerable savings.) Your PBX does not need any additional configuration. The Tenor unit treats all trunks the same without compromising voice quality.
Hop-off PBX Call
Tenor supports those Hop-off PBX calls where the destination Tenor unit is pro-grammed to route the call 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.) The destina-tion Tenor unit is configured with the phone numbers to be “supported” out of that “zone”.
SNMP Support
The Tenor unit supports Simple Network Management Protocol (SNMP), the stan-dard protocol used to exchange network information between different types of networks. The Tenor unit acts as an SNMP agent to receive commands and issue responses to the network manager. The network manager will then be able to per-form certain functions, such as generate and send traps.
Flexible Networking Capabilities
Now, migrating to a global VoIP network is easy. The product’s flexible design and scalability makes it not only sensible, but essential to run your voice over IP. The H.323 gatekeeper functionality adds to the product’s flexibility by pooling gateways within the same company to create a VoIP network and expand global networking capabilities. In addition, Tenor’s functionality makes it possible to con-nect to any PBX, anywhere. It’s universal, easy-to-concon-nect and the unique design lends itself to network expansion.
Interoperability
The Tenor Analog A400 and A800 units interoperate with the following: • Cisco VoIP gateways using FastStart or non-FastStart protocols • Cisco Gatekeeper
• Microsoft Net Meeting (voice only)
• Tenor Analog VoIP MultiPath Switch Release P2-1-9 and higher • A200, A2-1-6 and higher (voice only)
C
hapter 2: Hardware
Components
This chapter tells you what is contained in your hardware package. A description of each component is also included.
Specifically, the following topics are covered:
Front/Back Panel descriptions
LED definitionsHardware Description
Tenor Analog VoIP Gateway is a stackable/rack mountable device which provides connections to four different sites: PBX, PSTN, Ethernet LAN and a PC.
The unit’s front panel includes connection jacks, LEDs, and two reset/diag buttons; the back panel includes a power cord connection socket, an on/off switch, and a label. See Figure 2-1 and Figure 2-4.
The Tenor A400 unit is illustrated and defined below (the Tenor A800 looks identi-cal except there are eight PBX and eight PSTN lines available.)
Front Panel Connection and Reset Options
Figure 2-1 Tenor Analog Front Panel
• PBX Port: Four RJ-45 jacks (for connection to a PBX). For A400, each port provides one line. (For the A800 unit, each port provides two lines.)
• PSTN Port: Four RJ-45 jacks (for connection to a PSTN). For A400, each port provides one line. (For the A800 unit, each port provides two lines.) • Reset: Enables you to reset the system.
RJ-45 jack
for PSTN connect for Ethernet connectRJ-45 port Reset option
Diag Option RJ-45 jack for
for PBX connect RS-232 port
• Diag: Enables you to perform software diagnostic procedures.
• 10/100 LAN Port: One RJ-45 jack for connection to a 10/100 Ethernet LAN switch or hub via RJ-45 cable.
• Console Port: One RS-232 jack for connection to a PC’s serial port via DB-9 cable.
Front Panel PBX/PSTN Port Assignment
Each PBX and PSTN port is assigned a port number. For A400, each port is assigned one line number, for A800, each port is assigned two line numbers. For example, for an A800 unit, the first PBX port to the left is assigned two line num-bers of 1 and 5. See below.
For port pinout information for each RJ-45, see Appendix A.
Figure 2-2 PSTN/PBX Port Assignment
Port Assignment
Front Panel LEDs
The LEDs display the health of the system. The LEDs are separated into four groups: System, 10/100 Ethernet, PBX, and PSTN. For general LED definitions see Table 2-1.
Figure 2-3 Front Panel LEDs
System LEDs Ethernet LEDs
Table 2-1 Front Panel LEDs
LED
Color
Description
10/100 (Ethernet)
COL Yellow Ethernet Collision Status.
Flashing: Some collisions are taking place on the Ethernet LAN.
Off: No collisions are taking place on the Ethernet LAN.
10 Green 10 Mbps Ethernet Indication. On: The Tenor unit detects the 10 Mbps Ethernet link integrity signal indicating normal condition.
Off: The Tenor unit did not detect the 10 Mbps Ethernet link integrity signal. 100 Green 100 Mbps Ethernet location.
On: The Tenor unit detects the 100 Mbps Ethernet link integrity signal, indicating normal condition.
Off: The Tenor unit did not detect the 100 Mbps Ethernet link integrity sig-nal.
RX Green Ethernet Receive Status.
Flashing: Data is received from Ether-net LAN.
Off: Data is not being received from Ethernet LAN.
TX Green Ethernet Transmit Status.
Flashing: Data is being transmitted to Ethernet LAN.
System
Power Green Power Indicator.
On: Power is being supplied and the internal power convertor is working. Off: Power is off.
Alert Yellow Operational Status.
Off: The Tenor unit is working prop-erly.
On: One or more diagnostic tests have failed or system is stills starting up.
PBX
Busy (for lines 1-4; LED is located in lower left corner of RJ-45 port)
Green Operational Status. Off: Line is not active. On: Line is off hook or active. Busy (for lines 5-8;
LED is located in lower right corner of RJ-45 port)
Yellow Operational Status. Off: Line is not active. On: Line is off hook or active.
PSTN
Busy (for lines 1-4; LED is located in lower left corner of RJ-45 port)
Green Operational Status. Off: Line is not active. On: Line is off hook or active. Busy (for lines 5-8;
LED is located in lower right corner of RJ-45 port)
Yellow Operational Status Off: Line is not active. On: Line is off hook or active.
Back Panel
Figure 2-4 Tenor Unit Back Panel
• Power Cord. Cord to plug into an AC outlet for power. • Power Switch. Switch to turn power on and off.
• Label. A label that displays UL, model, and power information.
Cables
The cables listed in Table 2-2 are included with your system and are required to connect the Tenor unit to various interfaces.
Table 2-2 Cables Supported
Cable
Usage
RJ-45 to RJ-45 Patch Cable Analog connection(s) to PBX. RJ-45 to RJ-45 Patch Cable Analog connection(s) to PSTN. RJ-45 to RJ-45 Patch Cable Connection to Ethernet LAN 10/100. DB-9 Male to DB-9 Female Cable Connection to PC’s asynchronous console
Power Switch
C
hapter 3: Installation
The Tenor unit will be installed initially by a trained Quintum field engineer. This chapter gives you installation instructions, as well as how to position the unit suc-cessfully within your network.
Specifically, the following topics are covered:
Pre-Installation guidelines
Position the unitBefore you Begin
View Current Network Architecture
Before you install or configure a Tenor unit, take a look at your current network architecture, including the PBX, Ethernet LAN, and switch type products you have in place. Check any analog lines you have connected to the PBX or PSTN. It is a good idea to diagram your current network architecture, or use the Typical Office Network Configuration (Figure 3-1) as a baseline. This will help you maxi-mize your network configuration options.
Figure 3-1 Typical Office Network Configuration
PBX
Typical Office Setup Router
(PSTN)
(CSU may be internal)
Analog NetworkData BRI
Installation
Before you begin the actual installation, review the pre-installation guidelines which follow, inspect the package contents, and position the unit.
Pre-Installation Guidelines
• Only trained service technicians should remove the unit cover. Inside parts have hazardous voltages.
• Do not connect equipment in wet conditions or during a lightning storm.
Inspect Package Contents
Before you install the hardware, confirm that following components are included in your shipment.
• Tenor Analog VoIP Gateway A400 or Tenor Analog VoIP Gateway A800 • 1 AC Power Cable
• 4 RJ-45 Cable (for PSTN connection) • 4 RJ-45 Cable (for PBX connection) • 1 RJ-45 Cable (for Ethernet connection) • 1 DB-9 Cable
• 2 wall mounting brackets • 4 screws
• CD ROM
If a listed component is not included in your package, contact your customer ser-vice representative.
Position the Unit
Locate the Tenor unit within the same area as your PBX, Ethernet hub and/or PSTN patch panel. The unit can be installed on a flat surface (i.e., tabletop),
detailed in the sections which follow; pre-installation guidelines are included for each installation type.
Tabletop Install. The unit can be located on any sturdy, flat surface. If necessary, you can stack up to four units together. Before locating the unit on a tabletop, read the location guidelines which follow.
WARNING: If installing on a tabletop or any other flat surface, we recommend that you stack no more than four units together.
Pre-installation Guidelines • The surface must be sturdy.
• Avoid exposing the unit to excessive vibrations. • Keep the unit away from wet or dusty areas.
• The area must not exceed the temperature and humidity guidelines outlined in in Appendix B: Specifications/Approvals.
• Leave at least 3” clearance surrounding the unit. • Do not cover vent holes on top of unit.
Locate the unit on a tabletop as follows:
1. Place the unit on a desk, tabletop, or any flat, solid surface. 2. Ensure the unit will not slip or fall from the surface. 3. Ensure the power cord is in reach of the power outlet.
Rack Install. The unit can be located in a standard 19” rack. The rack is not included with your system. (See the documentation that comes with your rack for detailed installation instructions.)
Pre-installation Guidelines
• The maximum recommended ambient temperature is 30º C (86ºF). Internal rack temperature should be considered for safe operation.
• Do not restrict airflow vents when installing the unit in the rack.
• Mechanical loading of rack should be considered so that the rack remains sta-ble and unlikely to tip over.
• Consider the overall loading of the branch circuit before installing any equip-ment in a rack environequip-ment.
• Ensure that a reliable earthing path is maintained in a rack system. This unit is intended to be connected to earth ground.
Required Materials
• 2 wall mounting brackets (delivered with system) • 4 screws (delivered with system)
Install the unit in a rack as follows:
1. Position and attach one mounting bracket to the unit using two of the screws included with the package. See Figure 3-2.
2. Position and attach the other mounting bracket to the unit using the remaining two screws included with the package. Figure 3-2.
3. Place the unit in a 19” rack. See Figure 3-2.
4. Align the unit’s mounting brackets with the rack’s mounting holes and install screws with star washers. See vendor specific instructions for rack installation. 5. Ensure the unit is placed firmly in the rack.
Figure 3-2 Rack Installation
Tenor mounting
Shown: 2 Tenor Analog units installed Screws
Rack edge
Front View Top View
holes rack
Washers
Wall Mount. There are two slots located on the bottom of the unit that enable the unit to be mounted directly 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. Required Materials
• 2 wall mounting brackets (delivered with system) • 4 screws (delivered with system)
• 2 wall mounting screws (optional, not delivered with system) • 2 wall anchors (optional, not delivered with system)
• Drill • 3/16 drill bit
• Measuring tape or ruler • Hammer
• Phillips head screwdriver 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-3.
Figure 3-3 Wall Mounting Dimensions
2. Position and attach one mounting bracket to the unit using two of the screws included with the package. See Figure 3-4.
3. Position and attach the other mounting bracket to the unit using the remaining two screws included with the package. Figure 3-4.
NOTE: Wall anchors and wall mounting screws are not included with the sys-tem; we recommend you use them to add support to the mounting of the unit. See steps 4 and 5.
4. (Optional) Hammer the wall anchors into the wall 19 1/8 (48.6 cm) apart according to the dimensions shown in Figure 3-3.
5. (Optional) Using a Phillips head screwdriver insert the screws into the wall anchors according to the dimensions shown in Figure 3-3.
6. Align the unit over the anchor screws and slide the unit gently onto the screws and wall anchors. The mounting slots should engage the screws. See Figure 3-4.
Figure 3-4 Wall Mount Installation
7. Ensure the unit is firmly mounted against the wall.
7 3/4” Wall Mounting Slots Exploded View Screws/Wall Anchors
Connect the Unit
There are several different devices you can connect directly to the analog unit. The following steps are required to fully connect the Tenor Analog A400/A800:
• Connect to PBX/Key System • Connect to Telephone/Fax • Connect to Ethernet hub/Switch • Connect to PSTN
• Connect Console to PC Serial Com Port
NOTE: Other devices (PBX, Ethernet hub, etc.) are shown for pictorial pur-poses only.
Connect to PBX/Key System. There are many different PBX devices; instruc-tions which follow explain the general procedure for connecting an RJ-45 cable (included in your package) between a Tenor’s PBX port and a PBX. You must use your specific PBX documentation, along with any other PBX materials, for spe-cific information for how to connect the analog cable to your PBX.
Figure 3-5 Connect to PBX
RJ-45
2. Insert the other end of the RJ-45 cable into the appropriate analog port on the PBX or Key System. See your PBX documentation port requirements for con-nection specifics.
Connect to Phone or Fax. You are able to connect up to four telephones or fax machines to the Tenor unit. (For supplementary services, such as voice mail, call forwarding and call waiting, you will need to connect to a PBX rather than directly to a telephone).
Figure 3-6 Connect to Phone or Fax Machine
Connect to a phone as follows:
1. Insert one end of the RJ-45 cable into the jack on the back or underside of the phone or fax machine.
2. Insert the other end of the RJ-45 cable into one of the Tenor unit’s ports labeled PBX.
3. Repeat for each phone or fax machine you would like to connect.
RJ-45 Cables
Connect to PSTN. To connect to the PSTN, 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 about installation procedures, contact the network administrator or review the documentation you received with the equipment.
You can have up to four connections to the PSTN.
Figure 3-7 Connect to PSTN
1. Insert one end of the RJ-45 cable into one of the unit’s ports labeled PSTN. 2. Connect the other end of the RJ-45 cable to the patch panel.
NOTE: Connecting to the patch panel may require trained personnel.
3. Repeat for each analog line you want to connect between the Tenor unit and the PSTN.
PSTN
Patch Panel RJ-45
Connect to Ethernet Hub/Switch. You can use these instructions for general connection only. The Ethernet hub/switch documentation should provide specific instructions for connection to another device, such as the Tenor unit.
Figure 3-8 Connect to Ethernet Hub/Switch
1. Insert one end of the RJ-45 cable into the unit’s port labeled 10/100.
2. Insert the other end of the RJ-45 connector into the appropriate Ethernet port. See your Ethernet documentation port requirements for connection specifics.
Data
Network
Ethernet Hub/Switch RJ-45
Connect to PC Console. You will need to connect the Tenor unit to your work-station’s serial port via RS-232 connection. (This connection will be used when you initially assign an IP address to the unit.) For the instructions below, it is assumed you are connecting to a PC.
Figure 3-9 Connect to PC Com Port
1. Insert one end of the DB-9 cable into the Tenor unit’s port labeled Console. 2. Insert the other end of the DB-9 cable into your workstation’s Com Port (see
your PC documentation for more information about this port.)
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 Compo-nents.
Once the unit is powered up and the Alert LED goes out, you are ready to assign an IP address. See the following section Assign IP Address.
Assign IP Address
Before you can configure the Tenor unit, you need to assign a valid IP address for each unit. An IP address is a 32 bit 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.
Communication between the Tenor unit and the PC is enabled via RS-232 connec-tion and terminal emulaconnec-tion software. The instrucconnec-tions below assume you are run-ning HyperTerminal (runrun-ning on Windows 95 or later) on your PC. For all other terminal emulation packages, the specific Tenor commands used to assign the IP address will be the same, but the software specific instructions will be different. Consult the applicable documentation for more information.
NOTE: The instructions which follow assume the serial (RS-232) connection has been established as part of the installation process. If you need more information, see Connect to PC Console.
Assign IP Address as follows:
1. Click on Start> Programs> Accessories> Communications> HyperTerminal. The Connection Description window will be displayed.
2. Enter a connection description (i.e., name for each unit such as Tenor Analog A400).
3. Click Ok.
4. Choose the connection port (on your PC) from the Connect Using drop down list box (i.e., Direct to Com 1). Click Ok. The Com1 Properties window will be displayed. See Figure 3-10.
Figure 3-10 Port Settings Window
5. From the Bits Per Second drop down list box, choose 38400. 6. From the Data Bits drop down list box, choose 8.
7. From the Parity drop down list box, choose None. 8. From the Stop bits drop down list box, choose 1. 9. From the Flow control drop down list box, choose None.
10. Click Ok. A connection to the Tenor Analog unit will be established.
11. Press the Tenor Analog unit’s power switch to On. Information about the unit will scroll on the screen.
12. To change any of this information, including re-setting the IP address, press Enter within 3 seconds.
15. For This Board’s LAN IP Address, enter the IP address you want to assign to the Tenor Analog unit.
16. For Subnet Mask for LAN prompt, enter the subnet mask. This address is used to differentiate the network portion of the IP address from the host portion of the IP address.
17. For Default Gateway and IP Address prompts, choose whether there should be a default gateway (router) which routes packet data outside of your LAN, and enter its IP address.
18. For Baud Rate, change this number if necessary.
19. Enter a time (in seconds) for the CPU delay before starting up (default is 3). Upon initial configuration, the factory defaults will already be included in the system; there is no need to reset them.
Software Upgrade Overview
During the course of a product’s life cycle, it may be necessary for Quintum to issue software maintenance releases to resolve any bugs that may not have been detected during our systems test phase. Also, new features and functionality will require new software.
Types of Upgrade Software
Within the Quintum Tenor, there are three files:
boot.bin.The boot.bin file is the Tenor’s base operating system. The Tenor requires this software just to be able to power up normally. This software is not updated often from Quintum.
sys.bin. The sys.bin file is the Tenor’s system software. This software gives the Tenor all of its features and functionality. It provides all of the routing algorithms, etc. This software is updated as needed to provide bug fixes and feature enhance-ments.
db.bin. The db.bin is where your configuration for the Tenor is stored. This soft-ware is not upgraded directly, but will be upgraded, if needed, by the sys.bin file automatically. You may archive this file for a backup and later restore it back to the unit if necessary. You may also take this file from one Tenor and load it in to other Tenors of the same model type when you are creating a network of Tenors where the configuration is mostly the same except for some minor details.
Software Naming Convention:
When Quintum sends a customer new software, the file name will reflect the type of software it is. The convention that Quintum currently uses is as follows:
Parameter
Name
Possible
Values
Description
A Model Type ta – Tenor Analog ver-sion td – Tenor Digital ver-sion
Each software is provided for either the Analog or Digital Tenor. When you want to load a sys-tem, you must make sure that the software is for that product type (analog or digital).
B Soft-ware Type sy – sys.bin software bt – boot.bin software
As mentioned above, the two files that Quintum can provide for upgrades are the boot.bin and the sys.bin. When the software is sent, you can identify which software it is by this parameter. Also, when you load the Tenor, the Tenor will only accept a file name of boot.bin, sys.bin or db.bin, so you must rename the file to the cor-rect type when you load the software. See the procedures for more information.
Release Notes
When a new version of software is released, software release notes will be gener-ated to indicate the new features and/or bug fixes. Additionally, the release notes will tell you which files are to be upgraded (sys.bin, boot.bin, or both).
Other Software
In addition to the above software, there is also a feat.bin file. The feat.bin file is the file that provides different features to the Tenor. If you upgrade from one model type to another, Quintum may send you this file for the system. The feat.bin file is coded to a specific Tenor serial number based on the serial number you provide us. If the feat.bin file is loaded in to a system that does not have the serial number coded in this file, the Tenor will loose all of its features and stop processing calls. The correct feat.bin will need to be reloaded to this system.
D Echo Cancel-lation Type lec – Long Echo Cancel-lation. null – Short Echo Cancel-lation.
The long echo cancellation or lec software is used to provide up to 128ms of echo cancella-tion. Quintum recommends that all Tenors except the D3000 be loaded with the lec version software. If the file does not have lec in this position, then it is has shorter echo cancellation and should only be loaded on the D3000.
Load Upgrade software
Before you begin
Before you upgrade the Tenor with new software, you should check the following: 1. Make sure that you have received the correct software for your system from
Quintum.
2. Make sure you have saved the software file to a directory on your PC. For example purposes, we will use c:\Quintum as the directory.
3. Check the file size from a DOS window of the file you received. When Quin-tum emails the software to you, we should provide the file size as shown from DOS. To check this, open a DOS window on your PC where the file is stored and go to the directory where that file is. At the DOS prompt type dir <enter>. You will now see a list of all files in that directory and what there file size is. If the file size does not match what Quintum said it should be, then the file may be corrupted. Contact the Quintum Technical Assistance Center (QTAC) to have them resend the file.
4. Make sure that there are no calls active on the Tenor. If possible, place the Tenor in bypass mode.
5. Make sure that you can communicate with the Tenor from your PC over IP. You can only upgrade the Tenor over IP and not from the serial interface.
Load the Software
Follow the steps below to load the new software to your Tenor. You may choose to load both the boot.bin and the sys.bin files before the final step. This procedure is
3. At the DOS prompt type ftp ipaddress <enter>. Where the ipaddress is, enter the IP address for the Tenor.
4. At the User prompt hit <enter>. The Tenor has no user name.
5. At the Password prompt, type in the Tenor’s password you assigned. If you have not set a password on the Tenor, then just hit <enter>.
6. At the ftp> prompt type bin <enter>. This will tell FTP that the file to be transferred is a binary file.
7. At the ftp> prompt type hash <enter>. This will tell FTP to provide a hash (#) mark as a status indicator.
8. At the ftp> prompt type put origfile destfile. Where origfile is enter the name of the file as it is shown in DOS when you saved the file. For example; ta-sy-p2-4-5qt-lec.bin or td-sy-ta-sy-p2-4-5qt-lec.bin. Where destfile is, enter the file name that the Tenor needs to see. For example; sys.bin. So a full example might be; put ta-sy-p2-4-5qt-lec.bin sys.bin.
9. When you hit <enter> the file will first be transferred to the Tenor. This will be evident by the hash (#) marks appearing across the screen.
10. When the hash (#) stop appearing, the file has been transferred and the Tenor is now erasing the old software and loading the new one. This step can take as short as 20 seconds or as long as 1-2 minutes. This is a critical step. If the Tenor looses power or resets during this period, it may not come back up. 11. When the above is completed, you should get a message of “Transfer
Com-plete”. If you do not get this message, or if the message reads “connection closed by remote host”, then the load is not completed yet. Wait about 2 min-utes and then try to FTP into the Tenor again. If it allows you in, the load is complete and you can continue to step 12.
12. When you get the message Transfer Complete, the load is completed. If you have another file, like the boot.bin file to load, you can repeat step 8 to load this file now. Exit FTP by typing bye <enter>.
C
hapter 4: Getting Started:
Command Line
Inter-face (CLI)
This chapter tells you how to use access and use the CLI. Specifically, the follow-ing topics are included:
CLI Description
Access CLIWhat 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 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. CLI attributes enable you to further configure CLI options; these provide additional configuration items according to the option type.
Through the CLI, there are also commands you execute to simplify the process of configuring and monitoring the Tenor unit. Some of these commands are globally used, others are specific to the mode in which you are working.
Options
Some configuration menu options can have multiple instances. As a result, those option types require an identifier to uniquely define a specific option type. Other options are part of the default system, such as dial plan. You can configure the dial plan and the corresponding attributes, but you cannot create a second dial plan. Default menu options cannot be deleted.
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 unit. If your PC is directly connected to the Tenor unit, you can configure the unit directly through the serial port using HyperTerminal.
NOTE: Alternatively, you may want to use other telnet clients, such as the Linux telnet client or free programs like Putty. If you choose to do so, you may have to make minor setting changes in the Telnet client in order to make it function correctly.
Telnet Connection
Once the Tenor has been initially configured with an IP address network and is connected, the easiest way to connect to the Tenor and use the CLI is through a standard Telnet session from any PC on your IP network. Connect to a Tenor unit via Telnet as follows:
For Windows 95/Windows 98:
1. Click on Start> Run. The Run dialog box will be displayed. 2. Type telnet and click on Ok.
3. Click on Connect> Remote System.
4. In the Host Name field type, enter the IP address assigned to your Tenor. 5. Click on Connect.
A connection to the Tenor unit will be established. For Windows 2000 and later:
1. Click on Start> Run.
3. At the telnet prompt, type open (followed by the IP address for the unit to which you want to connect.)
A connection to the Tenor unit will be established.
Configuration via CLI
Once you are connected to the Command Line Interface (CLI), 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.
C
hapter 5: Working with SNMP
This chapter tells you how to use and manage Tenor’s Simple Network Manage-ment 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 unit, as well as how to generate SNMP traps for existing alarm messages.
Implement SNMP via HPOV
Generate and view trapsWhat 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. The agent is a piece of software running in a piece of network equipment that implements the SNMP protocol. SNMP defines exactly how a network manager communicates with an SNMP agent. For example, SNMP defines the format of requests that a network manager sends to an agent and the format of replies the agent returns.
Through an SNMP management system, the network manager can communicate and manage several different network devices at the same time. The network man-ager polls the SNMP agents (such as routers, hubs or network servers) for certain requested information. The agent will then gather information about the machine it is running on and carries requests from the network manager to read and change the information.
How does Tenor utilize SNMP?
The Tenor unit supports the SNMP protocol; specifically, Hewlett® Packard’s HP Openview software acts as the SNMP network manager for the Tenor unit. Once you set up HP Openview to view and “auto-discover” Tenor as a network device using SNMP, HP Openview will be able to issue commands, get responses, and perform certain functions. For example, you can configure the SNMP agent in Tenor to generate and send traps for existing Tenor alarms to HP Openview. A Tenor unit can report alarms to up to three network managers.
Installation Requirements
You will need to install and run HP Openview NMS 6.0 in order to recognize the Tenor as an SNMP agent. Below are basic hardware and software requirements you will need to install HP Openview. See your HP Openview documentation for detailed information and installation instructions.
Minimum hardware requirements
• Intel Pentium 120 Mhz processor-based computer • CD Drive
• 96 MB RAM
• 250 MB free disk space on one drive • 80 MB free page filing space 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
Inter-net Explorer web browser (version 4.0 or higher) with Java/JavaScript options enabled.
Installation
There are two steps you need to accomplish before HP Openview can interact with a Tenor unit as an SNMP agent.
• Download and install HP Openview configuration files specific for Tenor. • Configure the IP address of the network manager in the Tenor.
Download and Install SNMP Related Files
For HP Openview (network manager) to view and manage the Tenor as an SNMP agent, you must first download and install files from the www.quintum.com web site as follows:
1. Start up HP Openview. (For specific information, see the user documentation you received with the software.) There are two ways to download the applica-ble files: from the www.quintum.com web site or from the CD delivered with the system. To download from the web, go to step 2. Otherwise, for CD instal-lation, go to step 5.
2. From the web site, access a web browser (i.e., Microsoft Internet Explorer, Netscape) and go to the web site www.quintum.com and access Customer Ser-vice/ Training. If you are not registered, a registration form will be displayed. Once registered, you will be able to download the appropriate file. See Step 3. 3. Download the SNMP_MIB.zip file to your PC.
4. Unzip the SNMP_MIB.zip file to the HP Openview root directory (this is the directory in which HP Openview was installed).
The following files will be listed:
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 man-ually to files, if desired.
7. 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 manually make changes to the files, if desired.
NOTE: If you already ran the installquintum.bat, you must first run the installlquintum.bat clean command prior to reinstalling. This command will restore any changes made to the quintum files back to the default parameters (see below for which files are modified upon installation). • 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
• 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
installquintum.bat quintum.reg quintum.exe quintum.conf quintum.fields quintum_type connector_qdvoip connector_qavoip Tenor_D.ico quintum_sym Tenor_A.ico uninstallquintum.bat
• These lines are added to the file HPOVRoot\conf\C\trapd.conf using the "xnmevents -load" HPOV command:
OID_ALIAS Quintum .1.3.6.1.4.1.6618 #
# #
EVENT Critical_Alarm .1.3.6.1.4.1.6618.2.0.1 "Status Events" Critical FORMAT Received trap:generic #$G specific #$S. $#args:$*
SDESC T1IU_in_loopback;_network_request EDESC # # #
EVENT Major_Alarm .1.3.6.1.4.1.6618.2.0.2 "Status Events" Major FORMAT Received trap:generic #$G specific #$S. $#args:$* SDESC Corruption_of_configuration_info. EDESC # # #
EVENT Minor_Alarm .1.3.6.1.4.1.6618.2.0.3 "Status Events" Minor FORMAT Received trap:generic #$G specific #$S. $#args:$* SDESC RIU_not_installe EDESC # # #
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
• The quintum.exe file is added to the HPOVRoot\bin directory. • These files are added to the HPOVRoot\bitmaps\C directory:
TENOR_D.ico TENOR_A.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. • These files are added to the D:\hpovnnm\symbols\C\Connector directory:
CONNECTOR_QDVOIP CONNECTOR_QAVOIP
HP Openview will then identify and “auto-discover” the Tenor unit as an SNMP agent. An icon will appear on the screen to represent each Tenor unit. See below.
Figure 6-1 Tenor SNMP Agent Icon
Configure network manager IP address
Through Tenor’s Command Line interface (CLI), you can configure the IP address for the network management site where HP Openview is running. Once the IP
address is configured, the Tenor will be able to process and generate traps for exist-ing alarms, which will enable HP Openview to monitor the Tenor unit for alarm states.
To set the IP address, use the following CLI command:
config sys snmptrapip <index><ip>. This command configures the IP address of the network management site in the Tenor unit from which the SNMP traps will be generated. Valid entry: The index number of 1-3 (the index number is used to des-ignate the index # for the network manager to be used) followed by the IP address for the network management site.You can assign a Teor unit up to three network managers; each manager will have a different index number.
Assign an IP address as follows:
NOTE: The following instructions assume your PC is running Windows 95 or later.
1. Click on Start> Run. The Run window will appear. 2. Type telnet in the Open box and click on Ok. 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 32 is the default port for a telnet ses-sion).
to indicate the first network manager being assigned to that Tenor unit and assign the IP address 208.226.140.12 as the network manager.)
10. Repeat step 9 for each network manager (up to 3).
11. Type submit. The new IP address(es) will be submitted to the applicable Tenor unit.
Working with SNMP
View traps
You can view the traps HP Openview receives from the Tenor unit as follows: NOTE: Ensure HP Openview is running.
1. From the HP Openview map where the Tenor units appear, right-click on the Tenor icon for which you want to view traps and select Alarms.
2. From the Alarm Categories window, click on All Alarms. All traps (alarm mes-sages) will be listed in order of which they occurred.
View Alarm Status via Tenor icon
Through the color of a Tenor icon on the HP Openview desktop, you can determine the alarm state of the unit as well as view the corresponding alarms. Valid icon col-ors are listed below.
• Green Icon. No Alarm indicated.
• Red Icon. Critical Alarm (used for when HP Openview cannot communicate with the Tenor or there is a severity level 1 alarm)
• Orange Icon. Major Alarm (used for severity level 2 alarms) • Yellow Icon. Minor Alarm (used for severity level 3 alarms) • White Icon. Info Alarm (used for severity level 4 alarms) View the alarms associated with a Tenor unit as follows:
3. To view the alarms associated with that icon, right-click from anywhere on the HP Openview desktop and select Alarms. The All Alarms Browser window will appear, which contains the list of alarms.
Set up Tenor status polling
The following explains how to configure HPOV to determine and display unit sta-tus if the Tenor is not configured to send traps. Polling is only intended for Tenors which are not accessible to configure the network manager IP address using the Tenor’s Command Line Interface (CLI). We do not recommend polling more than 10 Tenors.
1. From the HP Openview desktop, right-click on the desired Tenor unit icon and select Object Properties.
2. From the Attributes window, select Quintum Tenor attributes. 3. Click on Edit Attributes.
4. Select Turn on Tenor Status Polling (the toggle allows you to set to True or False.) Select True.
5. Click on Verify. After the verification is complete, click Ok.
Polling occurs in a 30 second interval, or whenever a Tenor trap is received.
Set up Debug Message Display window
The following explains how to display debug messages that are generated by the quintum.exe. This window is used to troubleshoot HPOV processing events for the Tenor icons.
1. From the HP Openview desktop, right-click on the desired Tenor unit icon and select Object Properties.
2. From the Attributes window, select Quintum Tenor attributes. 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 will appear that displays debug messages being processed that are associated with that icon. Only one window can be opened at one time.
C
hapter 6: System Alarms
This chapter tells you how to use the Alarm Manager to view and understand alarms generated by the system.
Specifically, the following topics are included:
