Guia Tenor A400

Tenor VoIP MultiPath
Switch
A400/A800
Product Guide
P/N 480-0003-00-12
Tenor MultiPath Gateway, PacketSaver, Quintum, Quintum Technologies, Inc., VoIP Made Easy, TASQ
and TASQ Technology are trademarks of Quintum Technologies, Inc.
Table of Contents
About this Guide
Whats included? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Product Guide Conventions . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Tenor CAM Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Finding Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
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
H.323 Gatekeeper Call Control Management . . . . . . . . . . . .1-9
Powerful System Monitoring . . . . . . . . . . . . . . . . . . . . . . . . .1-9
Call Detail Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10
P/N 480-0003-00-12
1-1
Interactive Voice Response (IVR) . . . . . . . . . . . . . . . . . . . . .1-10

Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
Other Call Routing Options . . . . . . . . . . . . . . . . . . . . . . . . . .1-13
PacketSaver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-14
NATAccess. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-14
Virtual Tie Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15
Hop-off PBX Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15
SNMP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15
Flexible Networking Capabilities . . . . . . . . . . . . . . . . . . . . . .1-16
What is CAMWizard and Tenor CAM? . . . . . . . . . . . . . . . . . . . . .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
1-2
P/N 480-0003-00-12
Assign IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19
Types of Upgrade Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19
Software Naming Convention: . . . . . . . . . . . . . . . . . . . . . . . .3-20
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 via Tenor CAMWizard

Getting Started with Tenor CAMWizard. . . . . . . . . . . . . . . . . . . . .4-2
Run Tenor CAMWizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3
Chapter 5: Configuration via Tenor CAM

Getting started with Tenor CAM . . . . . . . . . . . . . . . . . . . . . . . . . .5-2
Log on Tenor CAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3
Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5
What is Change Password?. . . . . . . . . . . . . . . . . . . . . . . . . .5-5
Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6
Set Local Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7
What is Local Information? . . . . . . . . . . . . . . . . . . . . . . . . . .5-7
Configure Local Information . . . . . . . . . . . . . . . . . . . . . . . . . .5-9
Add PSTN Trunk Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10
What is a PSTN Trunk Group? . . . . . . . . . . . . . . . . . . . . . . .5-10
Configure PSTN Trunk Group . . . . . . . . . . . . . . . . . . . . . . . .5-11
Edit/Delete a PSTN Trunk Group. . . . . . . . . . . . . . . . . . . . . .5-12
What is a PBX Trunk Group? . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14
Configure PBX Trunk Group . . . . . . . . . . . . . . . . . . . . . . . . .5-16
Edit/Delete a PBX Trunk Group . . . . . . . . . . . . . . . . . . . . . . .5-17
P/N 480-0003-00-12
1-3
Configure Local Directory Numbers. . . . . . . . . . . . . . . . . . . . . . . .5-18

What are Local Directory Numbers? . . . . . . . . . . . . . . . . . . .5-18
Configure Local Directory Numbers . . . . . . . . . . . . . . . . . . . .5-20
Configure Channel Associated Signaling - Information . . . . . . . . .5-21
What is Channel Associated Signaling? . . . . . . . . . . . . . . . .5-21
Configure Channel Associated Signaling. . . . . . . . . . . . . . . .5-22
Add Hop-off PBX Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-24
What is a Hop-off PBX Number? . . . . . . . . . . . . . . . . . . . . . .5-24
Configure Hop-off PBX Number. . . . . . . . . . . . . . . . . . . . . . .5-25
Configure Bypass Directory Numbers . . . . . . . . . . . . . . . . . . . . . .5-26
What is a Bypass Directory Number? . . . . . . . . . . . . . . . . . .5-26
Configure Bypass Directory Number . . . . . . . . . . . . . . . . . . .5-27
Edit/Delete Bypass Directory Number . . . . . . . . . . . . . . . . . .5-27
Configure Border Element/Gatekeeper Information . . . . . . . . . . .5-29
What is Border Element/Gatekeeper? . . . . . . . . . . . . . . . . . .5-29
Configure Border Element . . . . . . . . . . . . . . . . . . . . . . . . . . .5-30
Assign Bandwidth to VoIP Calls . . . . . . . . . . . . . . . . . . . . . . . . . .5-32
What is Bandwidth Management? . . . . . . . . . . . . . . . . . . . . .5-32
Assign Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-33
Submit Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-34
Discard Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-35
Logout of the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-35
Problems with Flash Hook: . . . . . . . . . . . . . . . . . . . . . . . . . .5-35
Re-configure via Tenor CAMWizard . . . . . . . . . . . . . . . . . . . . . . .5-36
Chapter 6: Working with SNMP

What is SNMP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
How does Tenor utilize SNMP? . . . . . . . . . . . . . . . . . . . . . . .6-2
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4
1-4
P/N 480-0003-00-12
Download and Install SNMP Related Files . . . . . . . . . . . . . .6-4

Configure network manager IP address . . . . . . . . . . . . . . . .6-7
Working with SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9
View traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9
View Alarm Status via Tenor icon . . . . . . . . . . . . . . . . . . . . .6-9
Launching Tenor CAM from HP Openview . . . . . . . . . . . . . .6-10
Set up Tenor status polling . . . . . . . . . . . . . . . . . . . . . . . . . .6-11
Set up Debug Message Display window . . . . . . . . . . . . . . . .6-12
Chapter 7: System Alarms

What is an Alarm Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
How to Read Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
Valid Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6
View Alarms via Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10
Establish Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10
UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11
Display Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-12
Display Alarm History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-13
Filter Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-14
Delete Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-15
Exit Alarm Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-15
View Alarms via Tenor CAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16
Establish Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16
Display Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16
Display Alarm History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-18
Filter Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-19
Refresh Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-20
Clear Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-20
P/N 480-0003-00-12
1-5
Chapter 8: Call Detail Recording

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
Establish connection between Tenor and CDR Server . . . . . . . . .8-3
Tenor Establishes Connection with CDR Server . . . . . . . . . .8-4
CDR Server Establishes Connection with Tenor . . . . . . . . . .8-5
CDR Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6
Chapter 9: Using IVR

What is IVR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2
IVR Call Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3
ANI Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4
Multi-session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4
Typical IVR Network Connection/Process . . . . . . . . . . . . . . . . . . .9-6
Configure IVR - Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9
Basic IVR Data (via Trunk Group) . . . . . . . . . . . . . . . . . . . . .9-9
IVR Prompt Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9
RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10
Configure Voice Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-11
Voice Prompt Requirements (English Requirements) . . . . . .9-11
Create Voice Prompt Files . . . . . . . . . . . . . . . . . . . . . . . . . . .9-17
Update IVR Voice Prompts . . . . . . . . . . . . . . . . . . . . . . . . . .9-17
Configure IVR via CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-19
View RADIUS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-20
Display RADIUS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . .9-20
Clear RADIUS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-21
Call Flow - Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-22
Pre-paid Calling Card - Call Flow (with default language) . . .9-22
Post-paid Calling Card - Call Flow (with default language) . .9-24
Pre-paid and Post-paid Calling Card - Call Flow (with multiple language
support) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-26
1-6
P/N 480-0003-00-12
Pre-paid and Post-paid Calling Card - Call Flow (with Multi-Session Call
support) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-28
ANI Authentication Application Type 1 - Call Flow. . . . . . . . .9-30
ANI Authentication Application Type 2 - Call Flow. . . . . . . . .9-32
Call Flow - Message Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . .9-34
Start Accounting Request Message Attributes . . . . . . . . . . .9-34
Stop Accounting Request Message Attributes. . . . . . . . . . . .9-36
Authentication Request Message Attributes . . . . . . . . . . . . .9-39
Authentication Response Message Attributes . . . . . . . . . . . .9-40
Authorization Request Message Attributes . . . . . . . . . . . . . .9-41
Authorization Response Message Attributes . . . . . . . . . . . . .9-43
Appendix A: Cables
Appendix B: Specifications/Approvals
Appendix C: Getting Acquainted with VoIP
Glossary
Index
P/N 480-0003-00-12
1-7
About this Guide
P/N 480-0003-00-12
About this Guide
Whats 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 conventsions.
Chapter 1: Overview: Includes a general overview of the product, including a

description of how our product fits 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 with Tenor CAMWizard. This chapter explains

how to run the Tenor CAMWizard configuration management system, including a detailed descripton of the user interface.
Chapter 5: Configuration via Tenor CAM. This chapter describes how to perform advanced unit configuration.
Chapter 6: Working with SNMP. This chapter describes the SNMP protocol
and how to use it with the Tenor unit.
Chapter 7: System Alarms. Describes how to use the Alarm Manager and
tells you how to view alarms via telnet session or Tenor CAM.
Chapter 8: Call Detail Recording. Describes the CDR feature, including how
to display and read CDRs.
Chapter 9: Using IVR. Describes the IVR feature, including a quick start and
how to configure voice prompts.
Chapter 10: 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 Gateways specification

and approvals.
Appendix C: Getting Acqainted with VoIP. A general overview of VoIP and

how it relates to the Tenor unit.
P/N 480-0003-00-12
About this Guide
Glossary
Index
P/N 480-0003-00-12
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).
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-tos given in previous 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.)
P/N 480-0003-00-12
About this Guide
Tenor CAM Conventions

Tenor CAMWizard and Tenor CAM management systems require you to enter
information or select field entries from various field types. These field types are as
follows:
Edit box. The edit box is a field which enables you to enter alphanumeric characters. The maximum number of digits/letters you can enter depends upon the field
definition.
Figure 5-1 Edit Box sample
Radio button. Radio buttons enable you to click on the desired field entry from a
list of choices. A checked radio button indicates the option is enabled; unchecked
indicates the option is disabled.
Figure 5-2 Radio Button sample
Drop down list box. The drop down list box is a list of entries displayed when you
click on the arrow to the immediate right of the box. To select an entry, click on an
item from the drop down list.
Figure 5-3 Drop Down List sample
P/N 480-0003-00-12
About this Guide
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:
Getting Acquainted with VoIP for detailed information about VoIP terms and concepts.
For additional help, system help is available via Tenor CAM and Tenor CAMWizard. Just click on the Help buttonavailable from each screenand information
about that screen will be displayed.
P/N 480-0003-00-12
Chapter 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 information about the organization of this Product Guide.
Specifically, the following topics are covered:
A description of Tenor A400/A800 units

Typical implementations
Features and capabilities
P/N 480-0003-00-12
1-1
Chapter 1: Overview
What is Tenor VoIP MultiPath Switch?

The Tenor VoIP MultiPath Switch A400/A800 is a VoIP (Voice over Internet Protocol) H.323 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
Tenor Analog MultiPath VoIP Gateway A400/A800

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 unacceptableaccording to the specifications you assign the call will
be switched to the PSTN automatically. The units 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.
1-2
P/N 480-0003-00-12
Chapter 1: Overview
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 communication with a source outside of your company. Internet communication is communication running over the public IP network. Each implementation type is defined
in the sections which follow.
P/N 480-0003-00-12
1-3
Chapter 1: Overview
Intranet Implementation
The Tenor unit enables Intranet communication by transmitting data within a corporate 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 Gatekeeper functionality enables the two units within the same company to communicate.
For an illustration of intra-corporate communication, see Figure 1-2.
Figure 1-2 Intranet Tenor Implementation
Analog
Analog
PSTN
PBX
TCP/IP
Company X (France)
Ethernet
LAN 2
Router
Data
Network
Company X (California)
LAN 1
Company X (Tokyo)
LAN 3
Company X (New York)

LAN 4
1-4
P/N 480-0003-00-12
Chapter 1: Overview
Extranet Implementation
Another application example is the Tenor units 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

Analog
Analog
PSTN
Ethernet
TCP/IP
PBX
Router
Data
Network
Company X (New York)
Analog
Analog
Data
Network
Company Y (France)
PSTN
Ethernet
TCP/IP
PBX
Router
Data
Network
Company X (California)
P/N 480-0003-00-12
1-5
Chapter 1: Overview
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
Analog
Analog
PSTN
TCP/IP
PBX
Ethernet
Internet
Router
Data
Network
Your Company
1-6
P/N 480-0003-00-12
Chapter 1: Overview
Features
The Tenors specific features are explained below.
Unique Design
The Tenor unit packs powerful VoIP features into one compact unit. The systems
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. Tenor CAMWizard makes Tenors configuration and management
simple. Once you define an IP address via RS 232 port, the Tenor CAMWizard will
send you on your way with a default configuration.
Advanced configuration through Tenor CAM is optional; you are able to set specific configuration options that will help you to further maximize Tenors capabilities. Any standard Web browser can run Tenor CAM and Tenor CAMWizard; no
other software is needed.
P/N 480-0003-00-12
1-7
Chapter 1: Overview
SelectNet Intelligence
SelectNet is the next generation of TASQ technology. If the network packet delay
for an IP call becomes unacceptableaccording to the delay jitter and packet loss
specification you configureTenor 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 units 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 Networkand 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.
1-8
P/N 480-0003-00-12
Chapter 1: Overview
Easy Connect to Console

Plugging a DB-9 cable into the units 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.
H.323 Gatekeeper Call Control Management

The units H.323 gatekeeper performs IP call routing functions which comply to
the H.323 industry specifications for voice call control and management. The
Tenors Gatekeeper performs call routing functions for calls entering and exiting a
site.
H.323 endpoints in the same zone register with Tenors gatekeeper. When registration is complete and a call is originated, the call request is sent to the gatekeeper.
The call request provides the gatekeeper with the dialed number and requests bandwidth, authentication, and routing information. The gatekeeper confirms 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 communication 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.
Powerful System Monitoring

There are many different ways to monitor the health of the unit, including LEDs
and alarms.
LEDs 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 Tenor CAM
management system or a telnet session, you can view active system alarms. Each
alarm tells you specifically what problem the unit is encountering.
P/N 480-0003-00-12
1-9
Chapter 1: Overview
Call Detail Recording

Through the Call Detail Recording (CDR) feature, the Tenor unit is able to generate 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.
1-10
P/N 480-0003-00-12
Chapter 1: Overview
Capabilities
The Tenors 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 cannot be completed by a units 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
PBX
OR
PSTN
Ethernet
LAN
P/N 480-0003-00-12
1-11
Chapter 1: Overview
PSTN 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
PSTN
Call
PBX
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 Hopoff PBX call and the Tenor unit sends it out through the PSTN.
Figure 1-7 Data Network Call Routing
PBX
(for intra-corporate)
PSTN
Call
OR
(for Hop-off calls

supported)
VoIP Call
1-12
P/N 480-0003-00-12
Chapter 1: Overview
Other Call Routing Options

There are several routing tables you can configure through the Tenor CAM 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 Numbers (BPN), Local Directory Numbers (LDN), and Hop-off PBX Numbers.
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.
P/N 480-0003-00-12
1-13
Chapter 1: Overview
PacketSaver
PacketSaver packet multiplexing technology reduces the amount of IP bandwidth
require to support multiple calls flowing between two networks. 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 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.
.
Conventional VoIP Transmission Sends Many Redundant Packet Headers
Tenor
Tenor
Tenor using PacketSaver to Minimize Bandwidth Usage
NATAccess
NATAccess is an intelligent network address translation technology. It enables
VoIP networks with multiple H.323 endpoints to operate behind firewalls equipped
with Network Address Translation (NAT); this provides maximum network security. NATAccess simplifies deployment and installation by eliminating the need to
place the Tenor on a public IP network. Using NATAccess provides easy, secure
expansion between multiple VoIP sites.
1-14
P/N 480-0003-00-12
Chapter 1: Overview
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 PBXconfigured 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 programmed 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 destination 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 standard 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 perform certain functions, such as generate and send traps.
P/N 480-0003-00-12
1-15
Chapter 1: Overview
Flexible Networking Capabilities

Now, migrating to a global VoIP network is easy. The products 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 products flexibility by pooling
gateways within the same company to create a VoIP network and expand global
networking capabilities. In addition, Tenors functionality makes it possible to connect to any PBX, anywhere. Its universal, easy-to-connect and the unique design
lends itself to network expansion.
P/N 480-0003-00-12
1-16
Chapter 1: Overview
What is CAMWizard and Tenor CAM?

The Tenor CAMWizard is a quick step-by-step web management tool which
enables you to configure the minimal set of parameters you need to get the Tenor
unit up and running. A set of screens guide you through the configuration process.
Tenor CAM (Configuration/Alarms/Maintenance) is a web-based system management tool which enables you to configure, manage, and monitor the health of the
Tenor unit.
The following options are available from the main menu:
Configuration. Enables you to configure all system, local, signaling, line and
bandwidth data. See Chapter 5: Configuration via Tenor CAM for detailed configuration instructions. The following configuration screens are available via Configuration sub-menu.
Set Password
Local Information
PSTN Trunk Groups
PBX Trunk Groups
Local Directory Numbers
Channel Associated Signaling
Line Information
Hop-off PBX Numbers
Bypass Directory Number
Border Element/Gatekeeper
Bandwidth Management
CAMWizard
Submit
Discard
P/N 480-0003-00-12
1-17
Chapter 1: Overview
Alarms. Provides options for generating either a list of currently active alarms or
alarm history. The following items are available via Alarms sub-menu.
Active Alarms
Alarm History
Maintenance. Provides options for changing the date and time, resetting the system, and restoring factory defaults. See Chapter 9: Using IVR for more information. The following items are available via Maintenance sub-menu.
Date and Time
Reset
Factory Defaults
Online
About. Tells you the system version number and other system information.
Logout. Enables you to log out of the system.
Interoperability
The Tenor Analog A400 and A800 units interoperate with the following:
Cisco VoIP gateways using FastStart or non-FastStart protocols
Cisco Gatekeeper
Microsoft Netmeeting
Tenor VoIP MultiPath Switch - Digital Series Release P2-1-9 and higher
P/N 480-0003-00-12
1-18
Chapter 2: Hardware
Components
This chapter tells you what is contained in your hardware package. A description
of each component is also included.
Front/Back Panel descriptions

LED definitions
Cable descriptions
P/N 480-0003-00-12
2-1
Hardware 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 units 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 identical except there are eight PBX and eight PSTN lines available.)
Front Panel Connection and Reset Options

Figure 2-1 Tenor Analog Front Panel
Reset option
RJ-45 jack for RJ-45 jack
RJ-45 port
for PBX connect for PSTN connect
for Ethernet connect
Diag Option
2-2
RS-232 port
for PC connect
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.
P/N 480-0003-00-12
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 PCs 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 numbers 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
P/N 480-0003-00-12
2-3
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
PSTN/PBX LEDs
Ethernet LEDs
2-4
System LEDs
P/N 480-0003-00-12
Table 2-1 Front Panel LEDs

LED
Color
Description
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 signal.
RX
Green
Ethernet Receive Status.

Flashing: Data is received from Ethernet LAN.
Off: Data is not being received from
Ethernet LAN.
TX
Green
Ethernet Transmit Status.

Flashing: Data is being transmitted to
Ethernet LAN.
Off: Data is not being transmitted to
Ethernet LAN.
10/100
(Ethernet)
P/N 480-0003-00-12
2-5
LED
System
PBX
PSTN
2-6
Color
Description
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 properly.
On: One or more diagnostic tests have
failed or system is stills starting up.
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.

LED is located in
lower right corner of
RJ-45 port)
Yellow
Operational Status.

LED is located in
lower left corner of
RJ-45 port)
Green
Operational Status.

LED is located in
lower right corner of
RJ-45 port)
Yellow
Operational Status
P/N 480-0003-00-12
Back Panel
Figure 2-4 Tenor Unit Back Panel
Power Cord Jack
Power Switch
Label
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.
Analog connection(s) to PSTN.
Connection to Ethernet LAN 10/100.
DB-9 Male to DB-9 Female Cable
Connection to PCs asynchronous console

port.
Detachable AC Power Supply Cord
Connection to AC power jack.
P/N 480-0003-00-12
2-7
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 successfully within your network.
Pre-Installation guidelines
Position the unit
Connect to PBX, PSTN, 10/100 Ethernet and PC
P/N 480-0003-00-12
3-1
Before 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 maximize your network configuration options.
Figure 3-1 Typical Office Network Configuration
Data
Network
BRI
Router
Ethernet Hub/Switch
Analog
(PSTN)
PBX
(CSU may be internal)
Typical Office Setup
Since the Tenor unit functions as a gateway/gatekeeper and is invisible to the network, you will need to make only the physical connection between the unit and the
Ethernet hub, PBX, and PSTN. You configure the Tenor unit through the console
port and Tenor CAM; no network changes are required.
3-2
P/N 480-0003-00-12
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 service 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),
mounted within a rack, or mounted directly to the wall. Each installation type is
P/N 480-0003-00-12
3-3
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
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.
3-4
P/N 480-0003-00-12
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.)
The maximum recommended ambient temperature is 30 C (86F). 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 stable and unlikely to tip over.
Consider the overall loading of the branch circuit before installing any equipment in a rack environment.
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 units mounting brackets with the racks 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.
P/N 480-0003-00-12
3-5
Figure 3-2 Rack Installation

Rack edge
Tenor
rack
mounting
holes
Screws
Washers
Shown: 2 Tenor Analog units installed
in rack.
Front View
3-6
Top View
P/N 480-0003-00-12
Wall Mount. There are two slots located on the bottom of the unit that enable the
unit to be mounted directly to the wall.
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.
NOTE:
Ensure the unit is level.
P/N 480-0003-00-12
3-7
Figure 3-3 Wall Mounting Dimensions

7 3/4 (19.9 cm)
3/16
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 system; 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 34.
3-8
P/N 480-0003-00-12
Figure 3-4 Wall Mount Installation
Screws/Wall Anchors
Mounting
Slots
7 3/4
Wall
Exploded View
Note: Ensure unit is level.
7. Ensure the unit is firmly mounted against the wall.
P/N 480-0003-00-12
3-9
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 purposes only.
Connect to PBX/Key System. There are many different PBX devices; instructions which follow explain the general procedure for connecting an RJ-45 cable
(included in your package) between a Tenors PBX port and a PBX. You must use
your specific PBX documentation, along with any other PBX materials, for specific information for how to connect the analog cable to your PBX.
Figure 3-5 Connect to PBX
RJ-45
Cables
PBX or Key System
Connect to PBX as follows:

1. Insert one end of the RJ-45 cable into the Tenor units port labeled PBX.
3-10
P/N 480-0003-00-12
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 connection 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
RJ-45
Cables
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 units ports labeled
PBX.
3. Repeat for each phone or fax machine you would like to connect.
P/N 480-0003-00-12
3-11
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
RJ-45
PSTN
Patch Panel
1. Insert one end of the RJ-45 cable into one of the units 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.
3-12
P/N 480-0003-00-12
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
RJ-45
Cable
Data
Network
Ethernet Hub/Switch
1. Insert one end of the RJ-45 cable into the units 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.
P/N 480-0003-00-12
3-13
Connect to PC Console. You will need to connect the Tenor unit to your workstations 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
DB-9
1. Insert one end of the DB-9 cable into the Tenor units port labeled Console.
2. Insert the other end of the DB-9 cable into your workstations Com Port (see
your PC documentation for more information about this port.)
3-14
P/N 480-0003-00-12
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 and the Alert LED goes out, you are ready to assign an
IP address. See the following section Assign IP Address.
P/N 480-0003-00-12
3-15
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 connection and terminal emulation software. The instructions below assume you are running HyperTerminal (running 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>
Run. The HyperTerminal window will be displayed.
2. Click on Hypertrm.
3. Enter a Connection Description (i.e., name for each unit such as Tenor Analog
A400).
4. Click Ok.
5. 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.
3-16
P/N 480-0003-00-12
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. Click Ok. A connection to the Tenor Analog unit will be established.
12. Press the Tenor Analog units power switch to On. Information about the unit
will scroll on the screen.
13. To change any of this information, including re-setting the IP address, press
Enter within 3 seconds.
14. Type M (to modify) (to cancel, type C).
15. For Do you want a LAN interface?, the default entry is Yes.
P/N 480-0003-00-12
3-17
16. For This Boards LAN IP Address, enter the IP address you want to assign to the
Tenor Analog unit.
17. 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.
18. 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.
19. For Baud Rate, change this number if necessary.
20. 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.
3-18
P/N 480-0003-00-12
Overview
During the course of a products 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 Tenors 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 Tenors 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 enhancements.
db.bin. The db.bin is where your configuration for the Tenor is stored. This software 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.
P/N 480-0003-00-12
3-19
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
Model
Type
ta Tenor
Analog version
td Tenor
Digital version
Each software is provided for either the Analog

or Digital Tenor. When you want to load a system, you must make sure that the software is for
that product type (analog or digital).
Software
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 correct type when you load the software. See the
procedures for more information.
Software
Version
Variable,
based on software version
This will reflect the software version.
3-20
P/N 480-0003-00-12
Echo
Cancellation
Type
lec Long
Echo Cancellation.
null Short
Echo Cancellation.
The long echo cancellation or lec software is

used to provide up to 128ms of echo cancellation. 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.
Release Notes
When a new version of software is released, software release notes will be generated 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 on 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.
P/N 480-0003-00-12
3-21
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 Quintum 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
also used to restore a db.bin file that you previously archived.
1. From your PC, open a DOS window and at the DOS prompt change the directory to where the software is located (ex. cd c:\quintum).
2. At the prompt type dir <enter> to verify that the correct software is there.
P/N 480-0003-00-12
3-22
3. At the DOS prompt type ftp ipaddress <enter>. Where 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 Tenors 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-syp2-4-5qt-lec.bin or td-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 Complete. 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 minutes 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>.
13. The Tenor must know be reset for the new software to be active.
P/N 480-0003-00-12
3-23
P/N 480-0003-00-12
3-24
Chapter 4: Getting Started via

Tenor CAMWizard
This chapter tells you to how use the Tenor CAMWizard to run the basic configuration options, and get the Tenor unit up and running.
Specifically, the following topics are included:
Run Tenor CAMWizard

Configure basic information
P/N 480-0003-00-12
4-1
Getting Started with Tenor CAMWizard

The Tenor CAMWizard enables you to configure the minimal set of parameters you
need to get the Tenor unit up and running. A set of screens guide you through the
configuration process.
You can run Tenor CAMWizard using any convenient web browser. For optimal
performance, we recommend running one of the following Web browsers:
Microsoft Internet Explorer 4.0 (or later) or Netscape Navigator 4.6 or later. You
must also have an IP address assigned to the unit you want to configure. See Chapter 3: Installation.
Basic description for valid field entries appear in this chapter; detailed descriptions
appear in Chapter 5: Configuration via Tenor CAM.
NOTE:
Only one user can be connected to the Tenor CAMWizard at one time; if
a second user attempts to log into the system, an error message will be
displayed.
NOTE:
Any inactivity for a duration of 15 minutes will log you off the system
automatically.
To help navigate you through the screens, the Tenor CAMWizard displays a standard set of buttons on each screen.
4-2
Help. Provides help for the active screen.
Next. Moves you to the next screen. Changes are saved for the current
screen. Your changes will not be submitted to the Tenor unit until you complete the wizard process.
Back. Moves you back to the previous screen. Your changes on the current
screen will be saved.
Cancel. Cancels the changes you made on the current screen.
P/N 480-0003-00-12
Run Tenor CAMWizard

When you initially run the Tenor CAMWizard, you will be brought directly to the
main CAMWizard screen.
NOTE:
After the initial configuration, you will be able to reach the CAMWizard
by selecting the Tenor CAMWizard option from the left side of the Tenor
CAMs main screen.
Run the Tenor CAMWizard as follows:

1. Launch any browser.
2. At the Address line, type the IP address for the unit you would like to configure.
The Set Password screen will be displayed.
Figure 4-1 Password Screen
P/N 480-0003-00-12
4-3
3. In the Password field, enter a new password (1-31 alphanumeric characters).

NOTE:
Make a note of the password you set. If you lose your password, you
will need to restore the system back to factory default state. See Chapter
9: Using IVR for more information.
4. Click in the Confirm Password field and enter the same password (if the system
does not detect the same password, an error message will occur). You will only
need to confirm your password during initial configuration.
5. Click Next. The Date and Time screen will be displayed; this contains the current date and time set on your PC and the Tenor unit.
Figure 4-2 Date and Time screen
6. To synchronize the Tenor units time to your workstations time, click Synchronize and then Next. The Local Information screen will be displayed.
4-4
P/N 480-0003-00-12
Figure 4-3 Local Information screen
7. In the Name for this zone field, enter a name for zone or location (up to 31 characters).
8. From the Country Selection drop down list, select the country where the Tenor
unit is located. Default entry is USA.
9. In the Local Country Code field, enter the country code (code for country the
Tenor unit is located). Default entry is 1. Valid entry: up to 5 digits.
10. In the Area Code edit box, enter the area code. Valid entry: up to 5 digits.
11. Adjacent to the International Prefix field, click Add and enter the prefix code
used to make calls to the international dialing area. The default entry is 011.
Valid entry: up to 5 digits. Click Ok. (To edit or delete an International Prefix,
see Chapter 5: Configuration via Tenor CAM.)
P/N 480-0003-00-12
4-5
12. In the Long Distance Prefix field, enter the prefix used to make long distance
calls within the same country as the unit is located. The default value is up to 5
digits.
13. Click Next. The Trunk Group screen will be displayed.
Figure 4-4 Trunk Group screen
14. From the Trunk Group Name drop down list, select a trunk group name. Two
trunk groups (one for PSTN, one for PBX) will be created automatically per
Tenor unit detected in the zone. Through CAMWizard, you will be able to configure the PSTN side trunk group only. (To add, edit, or delete a PSTN or PBX
trunk group name, see Chapter 5: Configuration via Tenor CAM.)
15. In the Number of Digits to send to PBX field, enter the number of digits to be
sent to the PBX for incoming public directory numbers. The default value is 7.
Valid entry: 1-31.
16. Click Next. The Local Directory Number screen will be displayed.
4-6
P/N 480-0003-00-12
Figure 4-5 Local Directory Number screen
17. From the PBX Trunk Group Name drop down list, select a trunk group name.
18. From the Unit Selection drop down list, select the applicable unit name.
19. In the Hunt Public LDN field, enter a DN that will be routed to the PBX on the
first available line. Valid entry: up to 20 digits, including 0. You can use the *
as a wildcard option to represent any number of digits from 0-9. For example,
for a block of local numbers, you can use wildcards to enter them, 555-0*, 5551*, 555-2*, etc.
20. Select the channel from the Channel No drop down box that will be used to
route incoming numbers that match an LDN you specify in the Public LDN
field.
21. Enter a Local Directory Number in the Per-channel LDN text box. All incoming numbers matching the LDN will be routed to the PBX on the channel you
specified in the Per-Channel LDN drop box. Valid entry: up to 20 digits. You
P/N 480-0003-00-12
4-7
can use the * as a wildcard option to represent any number of digits from 0-9.
For example, for a block of local numbers, you can use wildcards to enter them,
555-0*, 555-1*, 555-2*, etc.).
22. Click Next. The Channel Associated Signaling Information screen will be displayed.
Figure 4-6 Channel Associated Signaling Information screen
23. From the Trunk drop down list, select the applicable trunk group.
24. From the Signaling Type drop down list box, select a signaling type. Default
entry: Loop Start.
25. Click Next. The Border Element Information screen will appear.
4-8
P/N 480-0003-00-12
Figure 4-7 Border Element Information screen
26. In the Primary Border Element IP Address field, enter the IP address of the
Tenor unit used as the Border Element. (The Border Element is internal to the
Tenor unit; it is used to establish relationships with other Tenor units in other
companies.) Each edit boxs value should be between 0 and 255.
27. Click Next. The Submit Changes options will be displayed.
28. Click Submit to submit the changes to the Tenor Gateway unit and exit. (To
cancel, click Cancel; to move back to previous screens, click Back.)
Your changes will be submitted to the Tenor unit.
P/N 480-0003-00-12
4-9
Chapter 5: Configuration via

Tenor CAM
This chapter tells you to how to configure Tenor Gateway via Tenor CAM. Instructions are included for configuring data such as signaling and interface type.
Configure data for each screen

Submit changes to the Tenor unit
P/N 480-0003-00-12
5-1
Getting started with Tenor CAM

Tenor CAM (Configuration/Alarms/Maintenance) enables you to configure the
Tenor unit(s). Detailed field entry descriptions appear in this chapter.
NOTE:
Only one user can be connected to the Tenor CAM at one time; if a second user attempts to log into the system, an error message will be displayed.
WARNING: Any inactivity for a duration of 15 minutes will log you off the
system automatically.
You can navigate through different screens by clicking on the desired button and
the desired screen will be displayed. There are several buttons that help you move
from screen to screen, with or without saving changes. Not all buttons appear on
each screen; definitions for all general buttons appear below. Definitions for screen
specific buttons are noted where applicable.
5-2
Help. Provides help on the active screen.
OK. Changes are saved temporarily, but they are not downloaded to the
Tenor unit until you perform a Submit. See section entitled Submit Changes.
Cancel. Cancels the changes you made on the current screen. Your cursor
will remain on the current screen.
Submit. Submits the changes to the Tenor unit.
Add/Edit/Delete. Buttons which enable you to add, edit, or delete field data
for the field to the immediate left of these buttons. Follow the instructions in
this product guide for how to use these buttons according to the specific
screen you are configuring.
P/N 480-0003-00-12
Log on Tenor CAM

Log on Tenor CAM as follows:
1. Launch any web browser.
2. At the Address line, type the IP address for the unit you would like to configure.
The Password screen will be displayed.
Figure 5-1 Password screen
3. In the Password field, enter your password (this is the same password you set
via Tenor CAMWizard).
4. In the Confirm Password field, enter the same password. (If the passwords do
not match, an error message will be displayed.) The main screen will be displayed.
P/N 480-0003-00-12
5-3

NOTE:
If you forget your password, you must reset the unit and restore factory
defaults; this will delete all existing configuration. See Chapter 9:
Using IVR.
Main menu
Sub-menu
Config sub-menu
items shown)
5. Click on Configuration from the systems main menu. The Configurations sub
menu will be displayed.
6. Click on the desired sub-menu item. That screen will be displayed.
NOTE:
Some screen fields are populated automatically with default entries; you
can change these as necessary. The following pages list all possible
entries for each field.
7. Instructions for configuring all Tenor CAM screens are included in the pages
which follow.
5-4
P/N 480-0003-00-12
Change Password
What is Change Password?
If you would like to change your password, the Set Password screen enables you to
set a new password for your system. You will use the same password to enter Tenor
CAM, as well as to perform any telnet functions.
Field definitions are as follows:
Password. The password you set to access the system. Valid entry: 1-31 characters
(alphanumeric). Required entry.
Confirm Password. The same password you set in the Password field. Valid
entry: up to 31 characters (alphanumeric). Required entry.
Figure 5-2 Set Password screen
P/N 480-0003-00-12
5-5
Change Password
Change password as follows:
1. From the Main screen, click Configuration>Set Password. The Set Password
screen willl be displayed.
2. In the Password field, enter a password.
3. In the Confirm Password field, enter the same password as you entered in the
Password field.
4. Click Ok to save the changes. (To cancel the changes, click Cancel.)
Your changes will be saved temporarily; you must perform a Submit function
before any changes will be downloaded to the Tenor unit. See Submit Changes for
more information.
5-6
P/N 480-0003-00-12
Set Local Information

What is Local Information?
Local information is the data you set for the local environment in which the Tenor
unit is located. The Local Information screen enables you to configure local
address and dialing information for the Tenor unit.
Figure 5-3 Local Information screen
Screen field definitions are as follows:
Name for this zone. A name for the zone in which your Tenor unit is located.
A zone is a group of endpoints (e.g, gateways, terminals) in one corporate
site. Valid entry: any name up to 31 alphanumeric characters. Required entry.
P/N 480-0003-00-12
5-7
5-8
Country Selection. Country where the Tenor unit resides. Valid entry: select
a country from the drop down list. Default entry: USA.
Local Country Code. Country code for the country in which the Tenor unit
resides. Valid entry: 1 to 5 digits. Default entry: 1.
Area Code: Regional area code for where the Tenor unit resides. Valid entry:
up to 5 digits. Required entry.
International Prefix. Code used for calls made from the Tenor unit to the
international dialing area. Valid entry: up to 5 digits. Default entry: 011.
Long Distance Prefix. Prefix used for calls made within the same country as
the Tenor unit. Valid entry: up to 5 digits. Default entry: 1.
Use Private Directory Numbers. Defines whether the private directory

numbers may be used to route calls. Valid entry: Yes or No. Default entry:
No.
Private Number Length. The length of the private numbering scheme; this
enables a private number to be parsed correctly. Valid entry: up to 2 digits,
range 1-20.
P/N 480-0003-00-12
Configure Local Information

Enter Local Information as follows:
1. From the Main screen, click on Configuration> Local Information. The Local
Information screen will be displayed.
2. In the NameFor This Zone field, enter a name for the zone.
3. From the Country Selection drop down list, select a country.
4. In the Local Country Code field, enter the country code.
5. In the Area Code field, enter the area code.
6. From the International Prefix drop down list, select a prefix. To add a prefix,
click Add and enter the prefix in the text box. (Click on a prefix and click on
Delete to remove a prefix from the list; click Edit to make changes to a prefix.)
7. In the Long Distance Prefix field, enter the prefix (up to 5 digits) you must use
to make an outside call.
8. Select whether the unit may use private numbers to route calls from the Use
Private Numbers radio buttons.
9. Enter a private number length in the Private Number Length edit box. Valid
entry: 1-20.
more information.
P/N 480-0003-00-12
5-9
Add PSTN Trunk Group

What is a PSTN Trunk Group?
A PSTN trunk group is a set of up to four channels (Tenor A400 unit) or up to eight
channels (Tenor A800 unit) used to connect the Tenor unit to a public switched
telephone network (PSTN).
The PSTN Trunk Group screen enables you to add/edit/delete a trunk group as well
as assign channels based on a specific trunk group. Through the channel hunting
algorithm, you will be able to configure the order in which the available channels
are used.
Figure 5-4 PSTN Trunk Group
5-10
P/N 480-0003-00-12
PSTN Trunk Group Name. The name for each trunk group. Valid entry:
Select from the drop down list. Default is one trunk group per Tenor unit. You
can either select from this list or you can add, edit, and delete trunk groups.
Channel Hunting Algorithm. The hunting algorithm used to locate available channels. Valid selection: Ascending, Descending, Ascending Round
Robin, Descending Round Robin, One-to-One. Default entry: Ascending.
Direction. Direction of call type permitted on the trunk. Valid entry: Outgoing, Incoming, and Bi-directional. Default entry: Bi-directional.
PSTN Trunk Group Channel Map
Trunk Group Association. This field shows the association between the
trunk group selected in the upper frame and the channels included in that
trunk group. The list box displays a trunk group name and the associated unit
name and channel status (channels that are part of a trunk group are indicated
with the number 1; channels that are not part of a trunk group are indicated
with the number 0). This information is displayed for the trunk group you
selected via PSTN Trunk Group Name field.
Channel Status. A set of four check boxes (for Tenor A400) or eight check
boxes (for Tenor A800). Each check box represents a channel in the trunk
group. Valid entry: selected check box indicates that the channel is included
in the selected trunk group; an empty box indicates that the channel is
excluded from the selected group.
Configure PSTN Trunk Group

Add a trunk group as follows:
1. From the Main screen, click on Configuration> PSTN Trunk Group. The PSTN
Trunk Group screen will be displayed.
2. From the PSTN Trunk Group name drop down list, select the desired trunk. (To
add, click on Add and enter a trunk group name in the text box. Click Ok. The
trunk group name will appear in the trunk group drop down list.)
P/N 480-0003-00-12
5-11
3. From the Channel Hunting Algorithm radio button list, select on the desired
type of channel hunting.
4. From the Direction radio button list, select the direction for the call.
5. For the selected trunk group and unit (appears in the Trunk Group Association
field) click on each channel you would like to enable via Channel Status check
boxes. A 1 will appear in the selected box indicating that the channel is
enabled.
6. Click Ok. (To cancel, click Cancel.)
7. Repeat step 2-6 for all subsequent trunk groups.
more information.
Edit/Delete a PSTN Trunk Group

Edit or delete an existing trunk group as follows:
1. From the Main screen, click on Configuration> PSTN Trunk Group. The PSTN
2. To edit, select an existing a trunk group from the PSTN Trunk Group drop down
list and click on Edit.
In the edit box, make the desired changes to the trunk group name and click
Ok.
Change the remaining fields, as desired.
3. To delete, select an existing a trunk group from the Trunk Group drop down list
and click on Delete. A dialog will prompt you for confirmation. Click Ok.
4. Click on Ok. (To cancel, click Cancel.)
5-12
P/N 480-0003-00-12
more information.
P/N 480-0003-00-12
5-13
What is a PBX Trunk Group?

A PBX Side trunk group is a collection of either up to four channels (for Tenor
A400) or up to eight channels (for Tenor A800) used to connect the Tenor unit to a
PBX (Private Branch Exchange).
The PBX Side Trunk Group screen enables you to add/edit/delete a trunk group as
well as assign channels based on a specific trunk group. Through the channel hunting algorithm you will be able to configure the order in which the available channels are used.
Figure 5-5 PBX Trunk Group screen
5-14
P/N 480-0003-00-12
PBX Trunk Group Name. The name for each trunk group. Valid entry:
Channel Hunting Algorithm. The hunting algorithm used to locate available channels. Drop down menu options: Ascending, Descending, Ascending
Round-robin, Descending Round-robin, One-to-One. Default entry: Ascending.
Direction. Direction of call type permitted on the trunk. Valid entry: Outgoing, Incoming, and Bi-directional. Default entry: Bi-directional.
Public Local Directory Number
Number of digits to send to PBX. Number of digits used for public calls
entering the PBX. Valid entry: range: 1-31. Default entry: 4 digits.
If the Private Directory Number field via Local Information screen was set to Yes,
the following fields will be displayed:
Number of digits to send to PBX. Number of digits used for private calls
entering the PBX. Valid entry: range of 1-31. Default entry: 4.
PBX Trunk Group Channel Map
Trunk Group Association. This field shows the association between the
trunk group selected in the upper frame and the channels included in that
trunk group. This list box displays a trunk group name and the associated unit
name and channel status (channels that are part of a trunk group are indicated
with the number 1; channels that are not part of a trunk group are indicated
with the number 0). This information is displayed for the trunk groups you
have selected via Trunk Group Name field.
Channel Status. A set of four check boxes (for Tenor A400) or eight (for
Tenor A800) check boxes. Each box represents a channel in the trunk group.
Default entry: what is in the database for the selected unit; Tenor CAM will
include all channels in the trunk group. Valid entry: selected check box indicates that the channel is included in the selected trunk group; an empty box
indicates that the channel not included in the selected trunk group.
P/N 480-0003-00-12
5-15
Auto-Switch DN
Enabled. Determines whether the auto-switch DN should be used. Valid

entry: No or Yes.
(If the Enabled field is Yes the following fields will be displayed)
Type. Determines the incoming auto-switch detection method. Valid entry:

Specified Number (DID available on line) or Check all numbers.
Number. Directory number used to receive auto-switched calls. There is no

default entry. Valid entry: up to 20 digits, including 0. This number must be a
local directory number, excluding area code.
Configure PBX Trunk Group

Add a trunk group as follows:
1. From the Main screen, click on Configuration> PBX Trunk Group. The PBX
2. From the PBX Trunk Group name drop down list, select the desired trunk. (To
add, click on Add and enter a trunk group name in the text box. Click Ok. The
trunk group name will appear in the trunk group drop down list.
3. From the Channel Hunting Algorithm radio button list, select on the desired
type of channel hunting.
4. From the Direction radio button list, select the direction for the call.
5. In the Number of digits to be sent to PBX edit box, enter the number of digits
for Public Local Directory Numbers.
If the Private Directory Number field via Local Information screen was set to Yes,
the following field will be displayed.
6. In the Number of digits to be sent to PBX edit box, enter the number of digits
for Private Local Directory Numbers.
5-16
P/N 480-0003-00-12
7. For the selected trunk group and unit (appears in the Trunk Group Association
field) click on each channel you would like to enable via Channel Status check
boxes. A 1 will appear in the selected box indicating that the channel is
enabled.
8. Select whether auto-switch should be enabled and enter the appropriate and
type of DN.
9. Click Ok. (To cancel, click Cancel.)
10. Repeat step 2-9 for all subsequent trunk groups.
more information.
Edit/Delete a PBX Trunk Group

Edit or delete an existing trunk group as follows:
1. From the Main screen, click on Configuration> PBX Trunk Group. The PBX
2. To edit, select an existing a trunk group from the Trunk Group drop down list
and click on Edit.
In the edit box, make the desired changes to the trunk group name and click
Ok.
Change the remaining fields, as desired.
3. To delete, select an existing a trunk group from the Trunk Group drop down list
and click on Delete. A dialog will prompt you for confirmation. Click Ok.
4. Click on Ok. (To cancel, click Cancel.)
more information.
P/N 480-0003-00-12
5-17
Configure Local Directory Numbers

What are Local Directory Numbers?
Local Directory Numbers (LDNs) are telephone numbers associated with PBX stations local to the Tenor unit.
Through the Local Directory Numbers screen, you are able to add and configure
directory numbers. Using the numbers you configure, the Tenor unit can identify
and route incoming calls to a PBX.
Figure 5-6 Local Directory Numbers screen
5-18
P/N 480-0003-00-12
PBX Trunk Group Name. The name for each trunk group. Valid entry:
Hunt Local Directory Numbers
Public Hunt LDNs. An incoming Directory Number (DN) that will be routed
to the PBX on the first available line. Valid entry: up to 20 digits, including 0.
You can use the * as a wildcard option to represent any number of digits
from 0-9. (For example, for a block of local numbers, you can use wildcards
to enter them, 555-0*, 555-1*, 555-2*, etc.).
Private Hunt LDN. An incoming Directory Number (DN) that will be routed
to the PBX on the first available line. Valid entry: up to 20 digits, including 0.
You can use the * as a wildcard option to represent any number of digits
from 0-9. (For example, for a block of local numbers, you can use wildcards
to enter them, 555-0*, 555-1*, 555-2*, etc.)
Per-Channel Local Directory Numbers
Channel No. The desired channel number.
Public Per-Chan LDN. An incoming Local Directory Number (LDN) that

will be routed to the PBX per a specific channel. Valid entry: select the
desired channel from the Per-Channel LDN drop down list box. Enter a corresponding public LDN in the Private LDN text box. Valid entry: up to 20 digits. You can use the * as a wildcard option to represent any number of digits
from 0-9. For example, for a block of local numbers, you can use wildcards to
enter them, 555-0*, 555-1*, 555-2*, etc.
Private Local Directory Number
If the Private Directory Number field via Local Information screen was set to
Yes, the following fields will be available:
Private Per-Chan LDN. An incoming Local Directory Number (LDN) that

will be routed to the PBX per a specific channel. Valid entry: select the
desired channel from the Per-Channel LDN drop down list box. Enter a corre-
P/N 480-0003-00-12
5-19
sponding Public LDN in the Private LDN text box. Valid entry: up to 20 digits. You can use the * as a wildcard option to represent any number of digits
from 0-9. For example, for a block of local numbers, you can use wildcards to
enter them, 555-0*, 555-1*, 555-2*, etc.
Configure Local Directory Numbers

Enter Local Directory Numbers as follows:
1. From the Main screen, click Configuration> Local Directory Numbers.
2. From the PBX Trunk Group name drop down list, select the desired trunk. (To
add, click on Add and enter a trunk group name in the text box. Click Ok.) The
trunk group name will appear in the trunk group drop down list.
3. Select a hunt DN from the Public Hunt LDN drop down box (to add an LDN,
click on Add and enter the desired DN). To edit, click on edit and change the
LDN. (To delete an LDN, click on the desired LDN and click on Delete).
4. Select a hunt DN from the Private Hunt LDN drop down box (to add an LDN,
click on Add and enter the desired DN). To edit, click on edit and change the
LDN. (To delete an LDN, click on the desired LDN and click on Delete).
5. Select a channel number from the Channel No. drop down box.
6. Enter a Public Per-Chan LDN.
For Private Local DNs: (This fields are available only if the Private Directory
Number field via Local Information screen was set to Yes).
7. Enter a Private Per-Chan LDN.
more information.
5-20
P/N 480-0003-00-12
Configure Channel Associated Signaling - Information

What is Channel Associated Signaling?
Channel Associated Signaling (CAS) is a form of signaling you can configure for
analog lines; you can choose two signaling types: Loop Start and Ground Start. The
Channel Associated Signaling screen enables you to choose the signaling type and
provision all associate parameters.
Depending upon the CAS signaling type you choose (Loop Start or Loop Start Forward Disconnect) a different set of fields will be displayed; these are noted where
applicable.
Figure 5-7 Channel Associated Signaling screen
P/N 480-0003-00-12
5-21
Trunk Group. List of available trunk groups. Valid entry: select any trunk
group in the list. Default entry: first trunk group in the list.
Signaling Type. The signaling type used for the trunk group. Valid entry:
Loop Start or Loop Start Forward Disconnect. Default entry: Loop Start.
For Loop Start only:
Connect Timeout (in ms). The amount of time set before the Tenor unit
sends a connect message to indicate that a call has been connected successfully.
For Loop Start Forward Disconnect only:
Connect Timeout (in ms). The amount of time set before the Tenor unit
sends a connect message to indicate that a call has been connected successfully.
Configure Channel Associated Signaling

Enter CAS signaling data as follows:
1. From the Main screen, click Configuration > Channel Associated Signaling.
2. From the Trunk drop down list, select a trunk group.
3. From the Signaling Type drop down list, select a signaling type. Depending
upon which signaling type you choose, a different set of parameters will be displayed. These are noted where applicable.
4. For Loop Start signaling only:
Enter a Connect Timeout time.
5. For Loop Start Forward Disconnect only:
Enter a Connect Timeout time.
5-22
P/N 480-0003-00-12
more information.
P/N 480-0003-00-12
5-23
Add Hop-off PBX Numbers

What is a Hop-off PBX Number?
The Hop-off PBX number is a telephone number that hops through a private network to reduce or eliminate public toll charges. Through the Hop-off PBX number
screen, you can configure the destination Tenor unit with the Hop-off PBX number(s) to be supported. The call can then be routed to the PSTN.
Figure 5-8 Hop-off PBX Number screen
5-24
Trunk Group Name. A list of available trunk groups. Valid entry: choose
from the list.
Maximum Number of Hop-off Calls Allowed. The maximum number of

Hop-off PBX calls to be enabled. Valid entry: select from the drop down list.
P/N 480-0003-00-12
Pattern. The telephone number used as the Hop-off PBX number. Valid entry
up to 31 digits. This number should be in international format.
Replacement. The local phone number with any special dialing patterns the
number requires (i.e., if the calling area requires a country code, area code,
etc.) The Tenor unit will use this number, in conjunction with the number in
the Pattern field, to route the calls. Valid entry: up to 31 digits.
Number Type. The type of telephone number: private or public. Valid entry:
Public or Private. Default entry: Public.
Configure Hop-off PBX Number

Configure a Hop-off PBX number as follows:
1. From the Trunk Group drop down list, select the desired trunk group for which
you would like to designate a Hop-off PBX number.
2. Click on the Add New button. Enter a number in the dialog box and click Ok.
The number will appear automatically in the Pattern field.
3. In the Replacement field, enter any special dialing patterns.
4. From the Number Type drop down list, select whether the Hop-off PBX number
is public or private.
more information.
P/N 480-0003-00-12
5-25
Configure Bypass Directory Numbers

What is a Bypass Directory Number?
A bypass directory number is a telephone number that is automatically sent to the
PSTN; it will not be routed via VoIP. Some examples of bypass numbers include
local calls, emergency calls (911), or high security calls. Through the Bypass
Directory Number screen, you are able to configure bypass directory numbers.
Figure 5-9 Bypass Directory Number screen
Field definitions are as follows:

Trunk Group Name. A list of all available trunk groups in the database. Valid
entry: select a trunk group from the list.
5-26
P/N 480-0003-00-12
Bypass DNs. The bypass number that Tenor Gateway will route automatically to
the PSTN. Valid entry: up to 31 digits. You can use the * wildcard option to represent any number of digits from 0-9. For example, for a block of local numbers,
you can use wildcards to enter them, (555-0*, 555-1*, 555-2*, etc.).You can use
the ? character to configure numbers such as 411 and 911 by using just one entry of
?11. This number should be specified in the format dialed from the PBX.
Configure Bypass Directory Number

Configure a Bypass Directory Number as follows:
NOTE:
You can configure a maximum of 32 bypass DNs.
1. From the Trunk Group drop down list box, select a trunk group.
2. Click Add and enter a bypass number in the dialog box. Click Ok. (To cancel,
click the Cancel button.) The new number will appear in the Bypass DNs drop
down list box.
3. Repeat steps 1-2 for each bypass number you would like to configure.
4. Click Ok to save the changes. (To cancel, click Cancel.)
before any changes will be downloaded to a Tenor unit. See Submit Changes for
more information.
Edit/Delete Bypass Directory Number

Edit or delete a Bypass Directory Number as follows:
1. From the Trunk Group drop down list box, select a trunk group.
2. Select the desired bypass number from the Bypass DNs drop down list and
click either Edit or Delete.
3. To edit, make the desired changes. Click Ok.
P/N 480-0003-00-12
5-27
4. To delete, select the desired bypass number from the Bypass DNs drop down
list and click on Delete. A confirmation box will ask you to confirm the delete.
Click Ok.
more information.
5-28
P/N 480-0003-00-12
Configure Border Element/Gatekeeper Information

What is Border Element/Gatekeeper?
The Gatekeeper (internal to a Tenor unit) collects, manages, and distributes call
routing information; the Border Element (internal to the Tenor unit) provides
access into or out of an administrative domain. There are two Border Elements in
an administrative domain: primary and secondary. These work together as one
entity to provide redundancy and fault tolerance.
You can configure Border Element information via Border Element Information/
Gatekeeper Information screen. Many of the field entries are defined in H.323
standards; these are noted where applicable.
Figure 5-10 Border Element/Gatekeeper screen
P/N 480-0003-00-12
5-29
All screen fields are defined below.
Primary Border Element IP Address. The IP address for the administrative

domains Border Element (the Border Element is internal to the Tenor unit; it
is used to establish relationships with other Tenor units in other companies).
Default entry: all zeros. Valid entry: a valid IP address, i.e., 192.168.1.35.
Each edit boxs value should be less than or equal to 255.
Secondary Border Element IP Address. The IP address for the alternate

border element (a Tenor unit used as a Border Element) in the administrative
zone. Default entry: 0.0.0.0. Valid entry: a valid IP address, i.e., 192.168.1.35.
Each edit box should be less than or equal to 255.
Discovery IP Address, The IP address a Tenor unit uses to communicate

with a Gatekeeper for service. Default entry is 0.0.0.0. Valid entry: each text
box should be less than or equal to 255.
Discovery Port. The H.323 standard port a Tenor unit uses to discover a
Gatekeeper. Default entry: 1718. Valid entry: this field should be less than or
equal to 65535.
Registration Port. The H.323 standard port a Tenor unit uses to register itself
with a Gatekeeper. Valid entry: this field should be less than or equal to
65535. Default entry: 1719.
Configure Border Element

Configure Border Element information as follows:
1. From the Main screen, click on Configuration> Gatekeeper.
2. In the Primary IP Address field, enter the IP address for the primary border element will be generated from the Primary IP address you configured via Tenor
CAMWizard.
3. In the Secondary IP Address field, enter the IP address for the secondary border
element.
4. In the Discovery IP Address field, enter the IP address of the Tenor unit that is
operating as the Gatekeeper. The default entry is 224.0.1.41.
5-30
P/N 480-0003-00-12
5. In the Discovery Port Number field, enter the 4 digit port number. The H.323
standard is 1718.
6. In the Registration Port Number field, enter the 4 digit port number. The H.323
standard is 1719.
more information.
P/N 480-0003-00-12
5-31
Assign Bandwidth to VoIP Calls

What is Bandwidth Management?
Bandwidth management is the ability to assign channel usage for VoIP calls
according to the time of day. Through the Bandwidth Management utility you can
assign certain bandwidth to be used for VoIP calls at specific times.
Figure 5-11 Bandwidth Management screen

Bandwidth
for day and hour
Day of Week
Hour
Each box on the Bandwidth screen represents the maximum amount of bandwidth
to be used for VoIP calls during that specified day and hour. You can enter a specific bandwidth in each box according to the day and hour.
5-32
P/N 480-0003-00-12
Assign Bandwidth
Assign bandwidth as follows:
1. From the Main screen, click on Configuration and click on Bandwidth Management. A 7x24 matrix of the days of the week and the hours of the day will
be displayed.
NOTE:
The hours displayed in the left side are listed in military time, numbers
0-11 corresponding to 12 am through 11 am; numbers 13 through 23
corresponding to 1:00 pm through 11:00 pm.
2. Click in a box corresponding to the desired day and hour.

3. Enter the desired maximum amount of bandwidth (in Kbps) to be used for VoIP
calls (i.e., 32, 64, 128, 256, 384).
4. Click Ok. (To cancel, click on Cancel.)
more information.
P/N 480-0003-00-12
5-33
Submit Changes
Once you have completed making all configuration changes, you are ready to submit the changes to the Tenor unit. When you perform a submit, all configuration
changes will be downloaded to the Tenor unit. If the system detects an error, the
changes will not be submitted.
Submit the changes as follows:
1. From the Main screen, click on Configuration> Submit. The Submit screen will
be displayed.
2. Click Submit to submit the changes (click Cancel to cancel the changes). Your
changes will be submitted.
5-34
P/N 480-0003-00-12
Discard Changes
Once you have completed making all configuration changes, you are still able to
discard the changes.
Discard the changes as follows:
1. From the Main screen, click on Configuration> Discard. A confirmation box
will ask you to confirm the discard.
2. Click Ok to delete the changes (to Cancel the discard procedure, click Cancel.)
Logout of the System

Logout of the system as follows:
1. From the Main screen, click on Logout.
If you have made changes that are not submitted, the changes will not be submitted.
Problems with Flash Hook:

When a call comes into the Tenor, and the call is answered, and then another call
comes in (on Call Waiting), if the receiver of the calls holds down the flash hook
button for too long to return to the first call AFTER disconnecting the second, the
first call will be switched to one of the other open phone ports on the Tenor. The
workaround for this is to tap the flash hook button as opposed to holding it down to
return to the first call.
P/N 480-0003-00-12
5-35
Re-configure via Tenor CAMWizard

At any time after you enter the configure the unit via Tenor CAM, you are able to
re-configure the unit using Tenor CAMWizard.
WARNING: If you re-configure using the Tenor CAMWizard, any previous

configuration or changes you made to the unit will be deleted from
the system.
Run the Tenor CAMWizard as follows:
1. From the main screen, click on Configuration> Tenor CAMWizard.
2. Click Ok to proceed (click Cancel to cancel).
3. The Tenor CAMWizard Set password screen will be displayed.
Follow the directions in Chapter 4: Getting Started via Tenor CAMWizard for configuring the unit via CAMWizard.
5-36
P/N 480-0003-00-12

This chapter tells you how to use and manage Tenors Simple Network Management Protocol (SNMP) feature, which is managed via Hewlett Packards HP
Openview Network Node Manager. Specifically, this chapter tells you how HP
OpenView auto-discovers a Tenor unit, as well as how to access TenorCAM and
generate SNMP traps for existing alarm messages.
Implement SNMP via HPOV

Generate and view traps
Access Tenor CAM via HPOV
P/N 480-0003-00-12
6-1
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. 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 manager 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 Packards 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.
6-2
P/N 480-0003-00-12
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 Internet Explorer web browser (version 4.0 or higher) with Java/JavaScript
options enabled.
P/N 480-0003-00-12
6-3
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 unit 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.)
2. Access a web browser (i.e., Microsoft Internet Explorer, Netscape) and go to
the web site www.quintum.com.
3. Download the installquintum.exe file to your PC.
4. Unzip the installquintum.zip file to the HP Openview root directory (this is the
directory in which HP Openview was installed).
The following files will be listed:
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
5. From the HP Openview root directory run installquintum.bat. Installation will

begin. The following section lists where the installation files are copied and
6-4
P/N 480-0003-00-12
6. which files were modified. You can use this information to manually make
changes to the files, if desired.
NOTE:
If you have 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
1.3.6.1.4.1.6618.1.1.2:Connector:QAVOIP
# QUINTUM Digital TENOR

# 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
1.3.6.1.4.1.6618.1.1.2:Quintum:Epilogue:H # Quintum-Analog Tenor
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
SDESC
Corruption_of_configuration_info.
EDESC
#
P/N 480-0003-00-12
6-5
#
#
EVENT Minor_Alarm .1.3.6.1.4.1.6618.2.0.3 "Status Events" Minor
SDESC
RIU_not_installe
EDESC
#
#
#
EVENT Report_Status_Alarm .1.3.6.1.4.1.6618.2.0.4 "Status Events" Normal
SDESC
Uswcomment
EDESC
#
#
#
EVENT Uswcomment .1.3.6.1.4.1.6618.2.0.0 "Status Events" Normal
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
6-6
P/N 480-0003-00-12
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 Tenors 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 existing 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 designate 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.
P/N 480-0003-00-12
6-7
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 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. At the Password prompt, enter the same password you set via Tenor CAMWizard.
9. At the Quintum prompt, type config sys snmptrapip<index><ip>. For example, type config sys snmptrapip 3 208.226.140.121 (this will assign index of 1
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.
6-8
P/N 480-0003-00-12
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 messages) 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 colors 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:

NOTE:
Ensure HP Openview is running.
1. From the HP Openview desktop, identify the icon for the Tenor unit from
which you would like to view alarms.
2. According to the color of that icon, determine the alarm state from the list
above.
P/N 480-0003-00-12
6-9
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.
Launching Tenor CAM from HP Openview

There are two ways you can launch Tenor CAM from HP Openview: right-click on
the icon and select from the pop-up menu option Quintum Web-based Tenor
CAM OR double-click on the icon. Both are defined below, along with instructions for how to manually configure an icon for double-clicking.
Launch Tenor CAM with pop-up menu as follows:
1. From the HP Openview desktop, right-click on the desired Tenor unit icon and
select Quintum Web-Based Tenor CAM.
The default internet browser will launch Tenor Cam with the IP address of the
unit associated with that icon (the correct IP address will appear in the URL).
2. Configure the unit as defined in Chapter 5: Configuration via Tenor CAM.
OR
Launch Tenor CAM by double-clicking as follows:
Step 1. Set up icon for double-click
select Symbol Properties.
2. From the Behavior options, click on the Execute radio button.
3. From the Application drop down list box, select Quintum Tenor CAM: DoubleClick.
4. Click on Ok. On the HP Openview desktop, the Tenor icon will become a
raised button.
P/N 480-0003-00-12
6-10
Double-click on the icon. The default internet browser will launch Tenor Cam with
the IP address of the unit associated with that icon (the correct IP address will
appear in the URL).
Step 2: Launch Tenor CAM by double-clicking icon
1. From the HP Openview desktop, double-click on the desired Tenor unit icon
and select Quintum Web-Based Tenor CAM.
The default internet browser will launch Tenor Cam with the IP address of the
unit associated with that icon (the correct IP address will appear in the URL).
2. Configure the unit as defined in Chapter 5: Configuration via Tenor CAM.
Set up Tenor status polling

The following explains how to configure HPOV to determine and display unit status 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
Tenors Command Line Interface (CLI). We do not recommend polling more than
10 Tenors.
select Object Properties.
2. From the Attributes window, select Quintum Tenor CAM 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.
P/N 480-0003-00-12
6-11
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.
select Object Properties.
2. From the Attributes window, select Quintum Tenor CAM 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.
P/N 480-0003-00-12
6-12

This chapter tells you how to use the Alarm Manager to view and understand
alarms generated by the system.
Description of Alarm Manager

View alarms via Tenor CAM
View alarms via Telnet
Delete and filter alarms
Monitor alarm history
P/N 480-0003-00-12
7-1
What is an Alarm Manager?

Alarms are brief text message that appear on your workstation when the Tenor unit
encounters a problem, such as a failed interface, disconnected call, etc. You can
reach the Alarm Manager via Telnet session or via Tenor CAM web based management system.
How to Read Alarms

The Alarm Manager reports alarms according to criteria such as the alarms severity level, line number the alarm occurred on, channel number, etc. There are two
alarm types displayed: Active Alarms and Alarm History. An Active Alarm list
displays all the alarms still active on the system; these alarms have not been
cleared or deleted. An Alarm History is a list of the last 100 alarms stored in the
system since the last time you performed a delete operation.
Whether you view alarm information via Telnet or Tenor CAM, the same information will be displayed (the Type field will be displayed in Alarm History only). For
example, see Figure 7-1 (Telnet generated list) and Figure 7-2 (Tenor CAM generated list). Field definitions for both views are listed in Table 7-1.
Figure 7-1 Alarm List Example (Telnet generated)

IP# Sequence# Type Severity Desc Line# Channel# Date/Time
192.168.1.50:6:ALR:2:Yellow Alarm:2:1:Thu Jan
192.168.1.50:7:ALR:1:Loss of Framing(Red Alarm):2:1:Thu Jan

7-2
1 01:42:15 1999
1 03:56:17 1999

192.168.1.50:8:CLR:1:Yellow Alarm:1:2:Thu Jan
See Table 7-1 for

valid field entries.
1 03:16:15 1999
1 00:00:00 1999
1 00:00:00 1999
P/N 480-0003-00-12
Figure 7-2 Alarm List Example (Tenor CAM generated)
See Table 7-1 for

valid field entries.
When you generate a list of alarms via Tenor CAM, each alarm is color coded
according to the severity (see Table 7-1 for a definition of alarm severity). The following are valid color codes:
Red. Critical Alarm (used for severity level 1 alarms)
Orange. Major Alarm (used for severity level 2 alarms)
Yellow. Minor Alarm (used for severity level 3 alarms)
White. Info Alarm (used for severity level 4 alarms)
P/N 480-0003-00-12
7-3
Definitions for all generated alarm fields appear in Table 7-1.
Table 7-1 Alarm Fields and Definitions

Field
Definition
Valid Entry
IP Address
The units IP address (32

bit address).
Example: 192.168.1.34.
Sequence #
Internal number used to

identify alarms.
01, 02, 03, etc.
Type (displays only if you

generate an Alarm History)
The type of alarm generated.
ALR = Alarm. This indicates an active alarm condition.

CLR= Clear. This indicates an alarm that has
been cleared from the system.
RPT= Report. Information
about an alarm.
Severity
Level of alarm severity.
1 = Critical (An error has

occurred that affects complete system).
2 = Major (An error has
occurred that affects system signaling or interfaces.)
3 = Minor (A minor problem is detected).
4 = Info (Information
report about a minor problems.)
Description
A text description of the

alarm; see Table 7-2 for
detailed description.
Varies.
7-4
P/N 480-0003-00-12
Field
Definition
Valid Entry
Line #
Specifies which analog

line type (PBX or PSTN)
has an alarm.
0.
Channel #
Defines the analog channel

the alarm is taking place
on.
0.
Date/Time
Date/time the event

occurred.
Day of week: name of

day.
Month: 2 digits.
Day of month: 1 or 2 digits.
Time: 6 digits (hour/minutes/seconds based on a
24-hour clock).
Year: 4 digits.
P/N 480-0003-00-12
7-5
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 (see Table
7-1 and Table 7-2 for more information).
Table 7-2 List of Valid Alarms

Alarm Description
(text appears in desc field)
Definition
Critical Software Error
A software error has occurred that affects the operability

of the complete system.
Major Software Error
A software error has occurred that affects system signaling, interfaces, or other major operation.
Minor Software Error
A software error has occurred but will not affect the

operation of the complete system.
Info Software Error
Indicates information about miscellaneous software

error. This does not affect system operation.
Tenor is in Bypass Mode
Indicates that the Tenor unit is bypassed; there is a direct

link between the PSTN and PBX.
Tenor Reset
Indicates that a Tenor unit has reset.
Border Element Connection Lost
Indicates that the Gatekeeper lost connection with the

Border Element. This is cleared if the connection is reestablished.
H323 Proxy not Registered

with Gatekeeper
The H323 Proxy process cannot be registered with the

gatekeeper.
Call Event(s) Lost
Buffer is full; call event data cannot be read.
Call Handler not Registered with Gatekeeper
The Call Handler process cannot be registered with the

gatekeeper.
7-6
P/N 480-0003-00-12
Alarm Description
Definition
UDP Alarm
Generated when an encoded/decoded RAS message

exceeds the UDP size limit. While encoding a message,
if the UDP size limit is exceeded, the message is discarded.
RAS Message
Appears when an encoded/decoded RAS message

IVR Configuration Missing
Appears if an attempt to make an IVR call has been

made while neither of the two IVR Prompt Server IP
addresses are set in the database; an IVR enabled trunk
group receives a call for which the IVR Prompt Server IP
is not configured.
This alarm will be cleared if you execute the fileserverip
command.
IVR File Server Not

Responding
Appears when an attempt to retrieve a voice file from a

IVR Prompt Server (File Server) failed because the IVR
Prompt Server did not respond.
Applies to a system with enabled IVR functionality (the
File Server IP is set in the database).
This alarm is cleared after the first successful file transfer
(disabling both of the IVR Prompt Servers will also clear
the alarm).
P/N 480-0003-00-12
7-7
Alarm Description
File Missing in the File
Server
Definition
This alarm will be reported to the system when a particular voice prompt file is not found in the IVR Prompt
Server.
This alarm applies only to the system with enabled IVR
functionality (i.e., File Server IP is set to the database).
RADIUS Configuration
Missing
Appears when a RADIUS request is made and one or

more required configuration parameters are missing.
This alarm is cleared when the required RADIUS parameters are configured.
RADIUS Server Not

Responding
Appears when none of the configured RADIUS servers

respond.
This alarm is cleared when any of the RADIUS servers
responds or the RADIUS server is disabled via CLI.
Switch to the other

RADIUS server
Appears when the current RADIUS server stops

responding after three consecutive calls end in timeouts
and another RADIUS server is configured. The Tenor
will then switch to the next RADIUS server.
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. Incorrect information may contain the
following:
RADIUS Server: Credit amount (-1)
RADIUS Server: Credit minus amount
RADIUS Server: Not supported currency
RADIUS Server: Credit time (-1)
RADIUS Server: Credit time < 6 sec
RADIUS Server: Invalid error code
7-8
P/N 480-0003-00-12
Alarm Description
UDP Alarm
P/N 480-0003-00-12
Definition
Generated when an encoded/decoded RAS message
7-9
View Alarms via Telnet

A telnet session provides terminal-like access to your Tenor unit. Through Telnet,
you can view active alarms, as well as generate an alarm history list. Viewing
alarms through Telnet consists of activating a telnet session and entering desired
commands.
You can run a Telnet session via Microsoft Windows (Windows 95 and later),
or a UNIX session.
The instructions in this section include running a Telnet session via Microsoft Windows or UNIX. For other terminal emulation software, see the applicable vendor
documentation for instructions.
The following are valid telnet alarm commands:
active: displays active alarms
history: displays alarm history
delete: deletes alarm history
exit: terminates alarm session
filter: displays alarms by severity, line, or IP address
help: displays a list of alarm related commands
?: displays a list of alarm related commands
Establish Connection
Establish a Telnet connection as follows:
7-10
NOTE:
Type help or ? at the prompt for a list of valid commands.
NOTE:
To exit the system at any time, type exit at the prompt.
P/N 480-0003-00-12

Windows 95 or later
1. Click on Start> Run. The Run window will appear.
2. In the Open box, type telnet 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, type 9000 (9000 is the default port number for the Alarm
Manager).
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. At the Password prompt, enter the same password you set via Tenor CAMWizard. See Chapter 4: Getting Started via Tenor CAMWizard.
You can now enter commands for the function you want to perform (such as
display alarms and delete alarms). See the sections which follow.
UNIX
1. Start a UNIX session.
2. At the command prompt, type telnet followed by the IP Address of the Tenor
unit and the port number 9000 (i.e., telnet 192.168.1.34:9000). A telnet session
will start.
3. At the Password prompt, enter the same password you set via Tenor CAMWizard. See Chapter 4: Getting Started via Tenor CAMWizard.
You can now enter commands for the function you want to perform (i.e., display alarms, delete alarms). See the sections which follow.
P/N 480-0003-00-12
7-11
Display Active Alarms

The Alarm Manager via telnet session enables you to view a list of active alarms.
Active alarms are those alarms that are currently on your system.
NOTE:
For a list of valid commands at any time, type ? at the prompt.
1. Ensure a connection to the Alarm Manager is established (See Establish Connection).

2. At the prompt, type active. All active alarms will be displayed. See Figure 7-3.
See How to Read Alarms for alarm field definitions.
Figure 7-3 Active Alarm Example

IP# Sequence# Severity Desc Line# Channel# Date/Time
192.168.1.50:6:2:Yellow Alarm:2:1:Thu Jan
1 03:16:15 1999
192.168.1.50:7:1:Loss of Framing(Red Alarm):2:1:Thu Jan

1 01:42:15 1999
1 03:56:17 1999
192.168.1.50:11:1:Loss of Framing(Red Alarm):1:1:Thu Jan

7-12
1 00:00:00 1999
1 00:00:00 1999
P/N 480-0003-00-12
Display Alarm History

The Alarm Manager via telnet session enables you to display the last 100 alarms
stored in the system since the last delete operation. This function enables you to
view the repeat occurrence of a particular alarm.
The alarms displayed in this window meet the filter criteria you set (i.e., if you set
the alarm history filtered by IP address, only alarms for that specific IP address will
be displayed). See Filter Alarm History for more information.
NOTE:
For a list of valid alarm history commands type history ? at the prompt.
Display alarm history as follows:

1. Ensure a connection to the Alarm Manager is established (see Establish Connection).
2. At the prompt, type history, followed either by c and/or d (c = display alarm
report and stay connected; d = display history and then delete). For example,
type history c. The alarm history (up to the last 100 alarms) will be displayed.
See Figure 7-4.
Figure 7-4 Alarm History Example

IP# Sequence# Type Severity Desc Line# Channel# Date/Time
1 03:16:15 1999

1 01:42:15 1999
1 03:56:17 1999

192.168.1.50:8:CLR:1:Yellow Alarm:1:1:Thu Jan
P/N 480-0003-00-12
1 00:00:00 1999
1 00:00:00 1999
7-13
Filter Alarm History

The Alarm Manager via telnet session enables you to filter the alarm history. Filtering enables you to set a criteria for which alarms are displayed. You can filter
alarms by severity, IP address and line number.
Severity: Displays alarms according to a severity level you choose, 1-4. See
Table 7-1 for definitions of severity levels.
IP Address: Displays only those alarms for a specific IP address.
Line Number: Displays alarms according to whether the alarm occurred on

line 1 (PBX) or line 2 (PSTN).
For example, if you set the filter to a specific severity, only those alarms with that
severity level and higher (i.e., if you choose severity level 2, both severity levels 1
and 2 will be displayed) will be displayed when the alarm history is generated.
NOTE:
The default value for the filter is to display all settings.
Filter the alarms as follows:

2. If desired, type filter d to display current filter settings.
3. To filter alarms by severity level: type filter s, followed by severity level. For
example, type filter s 1 to display all alarms with severity level 1.
To filter alarms by IP address: type filter i, followed by an IP address. For
example, type filter i 192.168.1.34.
To filter alarms by line: type filter l, followed by the desired line. For example, type filter l 2. This will filter all alarms that occur on the PSTN line. See
Table 7-1 for valid line options.
4. To set the filter back to the default settings (all fields displayed in list), type filter d. The alarms will not be filtered by any criteria.
7-14
P/N 480-0003-00-12
Delete Alarms
Alarms are not automatically cleared from the Tenor units Alarm History buffer,
you must manually delete them. You are able to delete the entire alarm history; you
are not able to delete individual alarms.
Delete alarms as follows:
1. Ensure a connection to the Alarm Manager via Telnet session is established.
(See Establish Connection.)
2. At the prompt, type delete. The alarm history in the buffer will be deleted.
Exit Alarm Manager

You can exit the Alarm Manager at any time.
Exit as follows:
At the prompt, type exit. The telnet window will close and you will be brought
back to the main screen.
P/N 480-0003-00-12
7-15
View Alarms via Tenor CAM

Tenor CAM enables you to view alarms through the Alarm Manager. Through
Tenor CAM, you can view active alarms, as well as view an alarm history list.
Establish Connection
Establish a connection to the Alarm Manager via Tenor CAM as follows:
1. Launch any convenient web browser.
2. Enter the IP address of the unit for which you would like to view alarms in the
web browsers Address field. The Tenor CAMs initial welcome screen will be
displayed, followed by the Password screen.
3. Enter a password in the Password field and enter the same password in the
Confirm Password field. Click Ok. The Main screen will be displayed.
You are now ready to view active alarms and an alarm history. See the sections
which follow.
Display Active Alarms

1. Ensure a connection to the Alarm Manager is established (See Establish Connection).
2. Click on Alarms. The Alarm Managers sub menu will be displayed.
3. Click Active Alarms. The Active Alarms Information screen will be displayed.
(See section How to Read Alarms for field definitions.)
7-16
P/N 480-0003-00-12
Figure 7-5 Sample Active Alarm Information screen
4. To refresh the screen and view newly generated alarms, click Refresh. (To cancel and go back to the main window, click Cancel.)
P/N 480-0003-00-12
7-17
Display Alarm History

The Alarm Manager displays the last 100 alarms stored since the last time you performed a delete operation. This function enables you to debug the repeat occurrence of a particular alarm.
The alarms displayed in this window meet the filter criteria you set (i.e., if you set
the alarm history filter by IP address, only alarms for that specific IP address will
be displayed). See Filter Alarm History for more information.
Display alarm history as follows:
2. Click on Alarms. The Alarm Managers sub menu will be displayed.
3. Click Alarm History. The Alarm History Information screen will be displayed.
See Figure 7-6. (See section How to Read Alarms for field definitions.)
7-18
P/N 480-0003-00-12
Figure 7-6 Alarm History List Example
Once the alarm history is generated, you can filter the alarms (see Filter Alarm
History), refresh the screen (see Refresh Alarm List) or clear the table (see Clear
Alarms).
Filter Alarm History

Filtering alarm history enables you to set a criteria for which alarms are displayed
in the Alarm History screen. You can filter alarms by severity and line number.
Severity: Displays alarms according to a severity level you choose: All, Critical, Major, Minor, or Info. See Table 7-1 for definitions of severity levels.
Line Number: Displays alarms according to whether the alarm occurred on

the PSTN line, PBX line, or both.
NOTE:
The default value for the filter is to display all settings.
P/N 480-0003-00-12
7-19
Filter the alarms as follows:

2. Display an alarm history list.
3. From the Severity drop down list, select the severity level for alarms to be displayed: All, Critical, Major, Minor or Info.
4. From the Line Number drop down list, select the line type for which alarms will
be displayed: Both, PBX or PSTN.
5. Click Set Filters. The filters will be set and will be applied to the next Alarm
History table you generate.
Refresh Alarm List

When you initially display an active alarm list, alarms that are generated up to that
point will be displayed. This list will stay the same; as new alarms are generated
they will not be displayed in the list until you perform a refresh.
To refresh the list, click on the Refresh button, located on the bottom of the
Active Alarm list screen.
Clear Alarms
Alarms are not automatically cleared from Tenor units Alarm History buffer; you
must manually clear them. You are able to clear the entire alarm history; you are
not able to clear individual alarms.
1. Ensure a connection to the Alarm Manager is established. (See Establish Connection.)
2. Display the alarm history list.
3. Click Clear Table.
The alarms will be cleared from the Alarm History buffer.
P/N 480-0003-00-12
7-20

This chapter tells you how to display and understand the Call Detail Recording
(CDR) feature. Examples are included later.
Description of CDR
Connect Tenor unit to CDR Server
Understand CDR data
P/N 480-0003-00-12
8-1
Overview
Through the Call Detail Recording (CDR) feature, the Tenor unit is able to generate 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.
The last 2000 CDRs generated are stored by the Tenor unit in a circular buffer (this
means that any number of CDRs over 2000 will overwrite the existing CDRs). We
advise that you set up a PC or workstation to act as a CDR server responsible for
receiving the CDRs as they are generated (up to 2 servers can be set up to collect
CDRs from the Tenor unit). The server will be responsible for capturing CDRs via
TCP/IP, processing/storing them in permanent memory, and producing billing
records. Any CDRs not collected from the Tenor unit will be lost if the unit is reset.
8-2
P/N 480-0003-00-12
Establish connection between Tenor and CDR Server

In order to capture CDRs, a connection between the Tenor unit and a CDR server
must be established. Based on configuration, the Tenor unit can either establish a
TCP/IP session with one or both of these CDR servers, or the CDR server can
establish a connection with the Tenor unit. A flow diagram (Figure 8-1) illustrates
the general transfer of information; both connection types are described in the sections which follow.
Figure 8-1 Flow of CDR Information

Tenor
CDR Server
Tenor connects
OR
automatically
(after initial configuration of
CDR port and IP address)
CDR Server logs

into Tenor port
9002/9003
TCP/IP Connection Established

Sends Welcome Message
Sends Password Prompt
Verifies Password
Enters password
Provides Tenor's IP
address and unit name
Provides last CDR sequence
number received
Begins delivering CDRs
Before attempting to collect CDRs, you should configure the desired information.
Through CLI commands, you can assign CDR server IP address, CDR server port
P/N 480-0003-00-12
8-3
number, CDR server password and CDR format information using the following
CLI commands: cdrserverip, cdserverport, cdrpassword, and cdrformat.
cdrserverip: IP addresses of the CDR server. (Used when the Tenor unit
establishes connection with CDR server.)
cdrserverport: The port numbers used by the CDR server(s). (Used when
the Tenor unit establishes connection with CDR server.)
cdrpassword: Password to be used by the CDR server(s).
cdrformat: This configuration parameter command is used to choose which

of the four possible Call Data Record output formats you would like sent to
your CDR Server: Possible entries are 0 (standard format), 1 (extended format), 100 (standard format with session ID functionality), 101 (extended format with session ID functionality).
When the CDR format is set to 100 or 10, the Tenor will send a reset number
after its unit name. The CDR server will save the Tenors reset number. If the
reset number is 0, the last sequence number will be the sequence number of
the CDRs in the Tenors current CDR file. If the reset number is not 0 and the
incoming reset number is not the same as the reset number, this implies that
the Tenor has reset or shut down before. In this case, the last sequence number will be set to 0. If the last sequence number is 0, the Tenor will send all
CDRs to the CDR server. If there are more than 10 CDRs in the Tenor, the
Tenor will send 10 CDRs at a time until it sends the rest of the CDRs. If the
last sequence number is not 0, the Tenor will send all CDRs with a sequence
number after the last sequence number.
A unique session ID number invisible to the user confirms that the unit has
not been reset and the Tenor has delivered all call records to the CDR Server.
Tenor 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 unit. Once these are configured, the Tenor unit will be
able to establish a TCP/IP session with the server on its own.
8-4
P/N 480-0003-00-12
CDR Server Establishes Connection with Tenor

If no IP address/port number is configured, the CDR server has to initiate the session. The Tenor unit uses TCP port numbers 9002 and 9003 on its side for the CDR
sessions.
Whether the Tenor unit establishes the connection with the CDR server or the CDR
server attempts to establish the connection, there is a limit of 5 attempts to enter the
correct password before the TCP session is terminated (to configure a password,
see the CLI command cdrpassword in the previous section).
After the CDR server successfully logs into the CDR port of the Tenor unit, the
CDR server will be provided with the IP address and unit name of the Tenor. The
CDR server will then supply the sequence number of the last CDR that it has
received from the Tenor unit. If the last CDR number is unknown, the server
should send 0 for the sequence number. After this exchange, the Tenor unit will
start delivering new CDRs to the server.
P/N 480-0003-00-12
8-5
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.
There are four CDR format types: Standard 0, Extended 1, Standard 100, and
Extended 101.
Standard 0: Displays the standard CDR format.
Extended 1: Displays all fields in Standard 0 plus Calling Party Number, PIN
code, Remote Call ID # and Local Call ID #.
Standard 100: Displays all fields in Standard 0 plus Session ID funtionality.
Extended 101: Displays all the fields in Extended 1 plus Session ID functionality.
See Establish connection between Tenor and CDR Server for more information.
Sample CDR Records:
Record 1 Sample: (includes fields for all formats):
1,17325551212,15,20000207062812,21060207062815,2000020706283030,16
,208.226.140.57,192.168.10.64,4,1,1,1,5,1,1,1,1,,0,0,1415551000,1234567890
1234,9876543210,0123456789
Record 1 Field Definitions Standard 0, 100
Standard 0 format includes all fields below; Standard 100 also includes all
fields below plus the Session ID.
1 (Call ID), 17325551212 (Called Number), 15 (Duration),
20000207062812 (Call Initiation Time), 20000207062815 (Call Connected
Time), 2000020706283030 (Call Disconnected Time), 16 (Cause Code),
208.226.140.57 (Local IP Address), 192.168.10.64 (Remote IP Address), 4
(Origination Trunk ID), 1 (Call Type), 1 (Call Number Type), 5 (Incoming
8-6
P/N 480-0003-00-12
Slot), 1 (Incoming Device), 1 (Incoming Line),1 (Incoming Channel), 1

(Outgoing Line), 1 (Outgoing Channel), blank AutoSwitch Time, blank
(AutoSwitch Duration), 0 (Bad IP Quality Events), 0 (AutoSwitch Flag).
Record 1 Field Definitions Standard 1, 101

Standard 1 format includes all fields used below; Standard 101 includes all the
fields below plus the Session ID:
1 (Call ID), 17325551212 (Called Number), 15 (Duration),
20000207062812 (Call Initiation Time), 20000207062815 (Call Connected
Time), 2000020706283030 (Call Disconnected Time), 16 (Cause Code),
208.226.140.57 (Local IP Address), 192.168.10.64 (Remote IP Address), 4
(Origination Trunk ID), 1 (Call Type), 1 (Call Number Type), 5 (Incoming
Slot), 1 (Incoming Device), 1 (Incoming Line),1 (Incoming Channel), 1
(Outgoing Line), 1 (Outgoing Channel), blank AutoSwitch Time, blank
(AutoSwitch Duration), 0 (Bad IP Quality Events), 0 (AutoSwitch Flag),
1415551000 (Calling Party Number), 12345678901234 (PIN Code),
9876543210 (Local Call ID #), 0123456789 (Remote Call ID #)
Definitions for each field appears below.
Call ID: Sequence number. This is a unique number assigned to identify an individual call (i.e, 1, 2, 3,). The sequence number starts from 1 and wraps around at
4,294,967,295. When a Tenor unit resets, the sequence number starts from 1 again.
If the system has a problem and loses connectivity, the CDR server can send the
Tenor unit the last Call ID that it received. The Tenor unit will reply with all
records that contain a Call ID which is greater than the one last received.
Called #: The number called. This will be in international format except for a passthrough 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 unit. The entry will be in the following format:
P/N 480-0003-00-12
8-7
yyyymmddhhmmss where yyyy (4 digits for year), mm (2 digits for month), dd (2

digits for day), hh (2 digits for hour), mm (2 digits for minutes), ss (2 digits for seconds).
Call Connected Time: The date and time the call was actually connected. The
time will be the local time configured on the Tenor unit. The entry will be in the
following format: yyyymmddhhmmss where yyyy (4 digits for year), mm (2 digits
for month), dd (2 digits for day), hh (2 digits for hour), mm (2 digits for minutes),
ss (2 digits for seconds). This field will be blank if the call never connected.
Call Disconnected Time: The date and time the call disconnected. The time will
be the local time configured on the Tenor unit. The entry will be in the following
format: yyyymmddhhmmss where yyyy (4 digits for year), mm (2 digits for
month), dd (2 digits for day), hh (2 digits for hour), mm (2 digits for minutes), ss (2
digits for seconds).
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. The called system acknowledges the connection request but
is unable to accept the call because all B channels are in use.
18
No User Responding. This cause is used when a user does not respond
to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated (in Q.931 by the
expiry of either timer T303 or T310).
28
Invalid Number Format (Address Incomplete). The cause indicates

that the called user cannot be reached because the called party number
is not a valid format or is not complete.
31
Normal, Unspecified. This cause is used to report a normal event only

when no other cause in the normal class applies.
8-8
P/N 480-0003-00-12
Cause Code
Definitions
34
No Circuit/Channel Available. The connection cannot be established

because no appropriate channel is available to take the call.
47
Resource Unavailable, Unspecified. This cause is used to report a

resource unavailable event only when no other cause applies.
Origination IP Address: The IP address for the Tenor unit originating the CDR.
The entry will be in the following format: xxx.xxx.xxx.xxx.
Destination IP Address: IP address for the remote destination Tenor if the call is a
VoIP call. This will be generated only if the call is VoIP; if the call is circuit based,
this field will be blank. This field will be the IP address of the origination Tenor if
the CDR is from the destination Tenor and will be that of the destination Tenor if
the CDR is from the origination Tenor.
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. Valid entry: 1 = voice, 2 = fax, 3 = modem, 4 =
modem.
Call Number Type: The called numbering plan used for the call per Q.931. Possible common entries are as follows: 1 = Public/E.164, 9 =Private.
Incoming Line: If the call is incoming, this field identifies which line the call
came in on. Valid entry: 1 = PBX, 2 = PSTN. This field will be empty if the call is
an incoming VoIP call.
Incoming Channel: If the call is incoming, this field identifies which channel the
call came in on. Valid entry: 1-4 or 1-8. This field will be empty if the call is an
incoming VoIP call.
Outgoing Line: If the call is outgoing, this field identifies which line the call is
going out on. Valid entry: 1 = PBX, 2 = PSTN.
P/N 480-0003-00-12
8-9
Outgoing Channel: If the call is outgoing, this field identifies which channel the
call went out on. Valid entry: 1-4 or 1-8.
Autoswitch Time: This is the date and time the autoswitched occurred (when the
call is switched from VoIP to circuit). The entry will be in the following format:
yyyymmddhhmmss where yyyy (4 digits for year), mm (2 digits for month), dd (2
digits for day), hh (2 digits for hour), mm (2 digits for minutes), ss (2 digits for seconds). If an autoswitch did not occur, this field will be blank.
AutoSwitch Duration: The number of seconds that the autoswitch call was active.
Valid entry: xx.
Bad IP Quality Events: The number of bad quality events that occur during a
VoIP call. This number determines the overall quality of the call.
Autoswitch Flag. The terminating side of the autoswitch call initially terminates to
the internal autoswitch agent before the call is actually autoswitched. This termination generates an extra CDR in addition to the original call that is autoswitched.
This field identifies a call that is terminated to the autoswitch agent, 0 = normal
call, 1 = termination to the autoswitch agent.
The following are CDR fields used in the Extended Formats 1 and 100 only.
Calling Party Number. The number called from. The format will be delivered in
whatever format the PSTN or PBX delivers to the Tenor.
PIN Code. PIN code entered. 14 digits maximum. This field will be blank if a PIN
code is not configured.
Remote Call ID #. Unique identification number, generated by the remote-side
Tenor, for call record matching purposes. Only generated for IP calls.
Local Call ID #. Unique identification number, generated by the local-side Tenor,
for call record matching purposes. Generated only for IP calls.
P/N 480-0003-00-12
8-10

This chapter tells you how to use the IVR feature, including how a quick start and
how to configure IVR voice prompts.
Definition of IVR
Definitions of RADIUS
Configure Voice Prompts
P/N 480-0003-00-12
9-1
What is IVR?
Interactive Voice Response (IVR) is a feature of the Tenor that 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. As a result, the
RADIUS enables the Tenor to interoperate directly with billing server application
software from a wide range of vendors. To provide redundancy, the Tenor supports
two RADIUS servers: Primary and Secondary.
The IVR interface enables the Tenor to play back interactive pre-recorded voice
messages to a customer calling in from the Public Switched Telephone Network
(PSTN), requesting information such as account number, PIN number, and calling
number. The caller is prompted for each piece of information and the digits are
captured by the Tenor and converted into RADIUS format. The RADIUS will use
the input data to identify the customer, verify the identity using the PIN code,
check the account status, and then send back messages in RADIUS format to
authorize the Tenor to proceed with the call. The call will then be routed over the
VoIP network to the appropriate remote Tenor.
Through an interactive IVR Prompt Server, you are able to pre-record and customize voice prompt files which lead the customer through the calling card procedure.
You can pre-record messages to meet your network and customer needs. The IVR
Prompt Server communicates with a Tenor via an IP link using TFTP protocol. An
IVR Tenor supports two IVR Prompt Servers: Primary and Secondary. The IVR
Prompt server is on the same IP network as either the Tenor or the RADIUS server.
Four language are supported for voice prompts: English, Mandarin, Persian, and
French. The multiple language feature enables you to select multiple languages in
which to play voice recordings. For example, once the welcome message is
played, a voice selection prompt asks the user in which language to play the
remainder of the messages: Press 1 for the first language configured, 2 for the second language configured or 3 for the third language configured.
9-2
P/N 480-0003-00-12
Through the Command Line Interface (CLI), you can configure all functions
within the Tenor that will be used for pre-paid/post-paid call services, including
IVR and RADIUS data.
IVR Call Types

There are two call services Tenor supports through IVR: Pre-paid Calling Card and
Post-paid Account.
Pre-paid Calling Card. A card with a set dollar amount to be used for placing voice calls. The normal call flow for a pre-paid service starts with the
caller dialing the pre-paid access number from a regular phone. The Tenor
prompts the caller for a card number and destination number which are sent to
the RADIUS server (third party software) for verification.
Post-paid Account. An account used for placing voice calls where the
account number and PIN (personal identification number) are used for security. The Tenor prompts the caller to enter an account number and a PIN (personal identification number), which are sent to the RADIUS server for
verification. Normally, there is no limit on the amount or duration the caller is
authorized to talk.
See Figure 9-1 for an illustration IVR implementation.
P/N 480-0003-00-12
9-3
ANI Authentication
There are two types of ANI Authentication supported in the Tenor: 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). If authentication fails, the call will not be answered but simply disconnected. If authentication succeeds, the call will be answered and second dial tone will be provided.
ANI Authentication Type 2 enables calling subscribers to receive three authentication types based on the calling number: (1) If there is an ANI in the setup message,
authentication with the ANI will be done (2) If there is no ANI information in the
setup message, the user will be prompted for a PIN number and (3) If the incoming
packet has the ANI, but authentication with the ANI fails, the user will be
prompted for a PIN number. If authentication succeeds, a 2nd dial tone is sent to
receive a DNIS. If there is ANI information in incoming packet but the authentication with the ANI fails, the caller is prompted for a PIN number. If the authentication succeeds, a 2nd dial tone is sent to receive a DNIS.
Multi-session
Multi-session enables the user to make another call at the end of a call, without
having to hang up and call again. At the end of the first call, a voice prompt will
ask if the user wants another call. In addition, the user will be able to terminate an
ongoing call and make another call, by pressing ** or ##.
9-4
P/N 480-0003-00-12
Figure 9-1 IVR and Billing Implementation
IP / Ethernet
IVR Prompt Server - Primary
Tenor IVR
Tenor IVR
Tenor IVR
Prompt
Files
IVR Prompt Server - Secondary
RADIUS Server - Primary
RADIUS Server - Secondary
P/N 480-0003-00-12
9-5
Typical IVR Network Connection/Process

See Figure 9-2 for a typical network configuration for IP based pre-paid calling
card/post-paid account services. This figure illustrates the originating Tenor is configured to provide pre-paid/post-paid services. All the subscribers will have to dial
into this Tenor via PSTN to get access to pre-paid/post-paid services.
Each process is denoted by a number (in bold); each number and the corresponding
process is explained in Table 9-1.
Figure 9-2 Typical Network Connection/Call Flow Process
1, 4, 5, 8, 9, 12
2, 3, 6, 7, 10, 11, 15, 16

13
PSTN
Telephone
Prepaid Enable
Prepaid
EnableTenor
Tenor
RADIUS Server
Primary & Secondary
IP Network
RADIUS Server
Primary & Secondary
RADIUS
Server - Secondary
IVR Prompt Server

Primary & Secondary
13
14
PSTN
Telephone
Destination
Tenor
9-6
P/N 480-0003-00-12
Table 9-1 Call Flow Process for Figure 9-2

Number
Process
User dials access number to initiate call (i.e., 1-800-xxx-xxxxx).
Tenor answers call and determines user is calling a pre-paid service based
on the number dialed or the trunk group to which the call is transferred.
Tenor sends Start Accounting to RADIUS server. Start Accounting is
optional.
RADIUS server acknowledges start accounting request. Start Accounting

is optional.
Tenor prompts the subscriber for the card number.
Caller enters the card number.
Tenor sends the card number to the RADIUS server for verification.
RADIUS server returns the credit balance for the account.
Tenor plays the credit amount and prompts the subscriber for the destination number.
Caller enters the destination number.
10
Tenor sends the destination number to the Radius server for authorization.
11
RADIUS server responds with the duration for which the caller is authorized to speak to the destination number.
12
Tenor plays the authorized duration.
13
The call is sent via IP network to the destination Tenor.
14
The destination Tenor sends the call via PSTN to the destination phone and
the call is established.
P/N 480-0003-00-12
9-7
9-8
15
If either side disconnects, Tenor sends stop accounting request to the

RADIUS server.
16
RADIUS server acknowledges the stop accounting request.
P/N 480-0003-00-12
Configure IVR - Quick Start

For a Tenor to be used as part of the complete IVR system, and communicate effectively with the IVR Prompt server and RADIUS, you must configure basic options
in the Tenor via Command Line Interface (CLI) for the following:
Basic IVR Data (via Trunk Group)
IVR Prompt Server
RADIUS
Instructions for configuring basic IVR information via Command Line Interface
(CLI) are described below. For detailed information about all CLI commands
available for IVR and detailed information about the commands described below,
see the Command Line Interface (CLI) guide you received with the unit.
Basic IVR Data (via Trunk Group)

Configure basic IVR information via config pstntg 1# prompt as follows:
1. Access CLI.
2. Access the config pstntg 1# prompt (i.e., config pstntg 1#).
3. Type ivrtype 2 (sets the IVR type to pre-paid calling services).
4. Type ivraccessnumber, followed by the telephone number used to access the
IVR system (up to 14 digits).
5. Type ivrcardlength 10 (10 is an example, the length of the calling card is
numeric up to 20 digits).
IVR Prompt Server

Configure IVR Prompt Server data via config ivr# prompt as follows:
1. Access CLI.
P/N 480-0003-00-12
9-9
2. Access the config ivr# prompt.

3. Type fileserverip p, followed by the IP address for the IVR Prompt Server (i.e.,
fileserverip p 208.22.234.34). The p indicates the primary IVR Prompt
Server.
4. Access the applicable config pstntg 1# or config pbxtg 1# prompt (i.e., config
pstntg 1#).
5. Set the ivrlanguage field to the applicable language: 0 (English), 1 (Persian), 2
(Mandarin), or 3 (French).
RADIUS Server
Configure RADIUS data via config radius# prompt as follows:
1. Access CLI.
2. Access the config radius# prompt.
3. Type host p, followed by the IP address for the primary RADIUS server (i.e.,
host p 208.22.234.34). The p indicates the primary RADIUS server.
4. Type host s, followed by the IP address for the secondary RADIUS server (i.e.,
host s 208.22.234.32). The s indicates the secondary RADIUS server.
5. Type sharedsecret (sharedsecret is similar to password), followed by the
RADIUS key (up to 64 characters) (i.e., sharedsecret 454AJU).
6. Ensure accountingtype is configured. If this field is set to 0, no stop accounting messages will be sent.
9-10
P/N 480-0003-00-12
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 in the
IVR prompt server in the form of audio files that can be recorded by a recording
studio. The audio files are transmitted to the Tenor using TFTP protocol. They 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.
The IVR Prompt Server communicates with a Tenor via IP link using TFTP protocol. The IVR Prompt Server acts as the TFTP Server; each Tenor represents a
TFTP client.
When a Tenor system is re-started, it does not have any voice prompts stored in its
internal memory. Each voice prompt is retrieved on demand from the IVR Prompt
Server; it will stay in the Tenors cache memory for replay until one of the following happens: an ivrupdate command is issued, a change of IP address in the database, or the Tenor has been powered off or reset.
To provide some redundancy for the system, two IVR Prompt Servers can be
optionally specified in the database. The servers should store the identical voice
prompt files (i.e., they are indistinguishable from each other as IVR Prompt Servers). One of the IVR Prompt Servers remains active during the operation, unless it
fails to respond to the Tenor for some reason. In that case, the other one will be
picked up as an active IVR Prompt Server automatically. It will be used as the
active server for all the subsequent requests; in the case that if fails, the active
server will be switched back to the original one, and the cycle repeats itself.
Voice Prompt Requirements (English Requirements)

NOTE:
To ensure good speech quality, the voice prompts should be professionally recorded in a studio.
Table 9-2 specifies requirements for each voice file recorded. Definitions for each
table entry are listed below.
P/N 480-0003-00-12
9-11
Filename. Actual filename under which the appropriate pre-recorded speech

is to be stored on the IVR Prompt Server. The voice files should be in CCITT
G711 -Law format and stored with .wav extension (no application-specific
headers, like in the files generated by the Microsoft Recorder, are allowed).
Suggested Content. This field contains a particular piece of speech which

represents the voice file, played back along with other file(s) during the actual
IVR call. For these particular cases, the voice files should be carefully
recorded, using appropriate intonation patterns.
Example with other Voice Files. This field uses the specified voice file with
other possible voice files. For example, the file [enter] + [account_number]
has the following contents: Please enter your account number. The + indicates in addition to the filename.
Usage Example. This field represents the actual pre-recorded speech being
used in a specific speech pattern.
Table 9-2 File Conventions for Recorded Files

Filename
Suggested
Content
Example with
other Voice Files
Usage
Example
account_expired
Your card has

expired.
[account_expired] +
+ [good_bye]
Your card has

expired. Goodbye.
account_numbe
r
account number
[enter] +
[account_number]
+ [pound_key]
Enter account
number followed
by the pound key.
and
and
blocked
The number you

have dialed is
blocked.
[blocked] +
[hang_up]
The number you

have dialed is
blocked. Please
hang up and call
again later.
9-12
P/N 480-0003-00-12
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.
dollar
dollar
dollars
dollars
eight
eight
eighteen
eighteen
eighty
eighty
eleven
eleven
enter
Please enter
your
[enter] +
[card_number OR
account_number OR
pin OR destination]
Please enter your

card number.
Please enter
account number.
Please enter pin.
Please enter destination number.
fifteen
fifteen
P/N 480-0003-00-12
9-13
fifty
fifty
five
five
forty
forty
four
four
fourteen
fourteen
good_bye
Good bye.
hang_up
Please hang up
and call again
later.
hundred
hundred
in_use
This account is
currently in use.
[in_use] + [hang_up]
This account is
currently in use.
Please hangup
and call again
later.
invalid
You have entered

an invalid number.
language
for English press
[lang] + [one]
For English press

one.
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
P/N 480-0003-00-12
9-14
nine
nine
nineteen
nineteen
ninety
ninety
no_funds
You have insufficient funds in your

account.
[no_funds] +
[good_bye]
You have insufficient funds in

your account.
Good bye.
one
one
pin
pin
[enter] + [pin] +
[pound_key]
Please enter your

pin followed by
the pound key.
pound_key
followed by the
pound key.
[enter] +
[account_number OR
card_number OR pin
OR destination] +
[pound_key].
Please enter your

account number
followed by the
pound key.
problems
We are currently
experiencing technical difficulties.
[problems] +
[hang_up]
We are currently
experiencing
technical difficulties. Please hang
up and call again
later.
remaining
remaining.
[ <money> OR
<time>] + [remaining]
Eighteen minutes
remaining.
Twenty cents
remaining.
rial
rial
second
second
seconds
seconds
seven
seven
P/N 480-0003-00-12
9-15
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] + [<any
number>] + [remaining]
You have six

cents remaining.
yuan
yuan
zero
zero
P/N 480-0003-00-12
9-16
zero_balance
You have zero

balance in your
account.
[zero_balance] +
[good_bye]
You have zero

balance in your
account. Goodbye.
Create Voice Prompt Files

The IVR Prompt Server contains voice prompts; it will exchange information with
a Tenor via TFTP protocol and act as the TFTP Server.
NOTE:
Although logically separate from the RADIUS server, the IVR Prompt
Server may be physically part of the same server.
Configure the IVR Prompt Server as follows:

1. Create a root directory for the IVR voice files (i.e, c:\quintum\ivr).
2. Create a subdirectory for each supported language and use the following specific naming conventions:
For English, use the filename c:\quintum\ivr\English.
For Persian, use the filename c:\quintum\ivr\Persian
For Mandarin, use the filename c:\quintum\ivr\Mandarin
For French, use the filename c:\quintum\ivr\French
3. Record all voice prompts and store under the c:\quintum\ivr\English subdirectory.
4. Launch the TFTP Server and configure the home directory to be the same as in
step 1.
5. Run the TFTP Server.
Update IVR Voice Prompts

If a particular voice prompt was retrieved from the IVR Prompt Server and is
played back during an IVR call, it will be cached in the Tenors RAM. This means
P/N 480-0003-00-12
9-17
that the next request to play the same prompt will be completed without retrieving
the file from the IVR prompt server. As a result, response time is improved.
The IVR voice prompts will be flushed automatically when the IVR Prompt Server
address has been changed in the database. In rare cases, when the total memory
usage by the voice prompts exceeds the allowed maximum, the prompts will be
also automatically flushed. At any point, you can update the Tenor to play updated
IVR voice prompts through the ivrupdatprompts command. Using the ivrupdateprompts command, the files can be updated without first restarting the unit.
You can run the ivrupdateprompts command through the Command Line Interface
(CLI) as follows:
1. Access the Command Line Interface (CLI) via serial port or telnet connection.
2. At the Quintum prompt, type ivrupdateprompts.
The Tenor will flush all cached prompts; the next IVR call will play back the
updated prompts.
P/N 480-0003-00-12
9-18
Configure IVR via CLI

All configuration for IVR, the RADIUS server and IVR Prompt Server is done
through the Command LIne Interface (CLI). For information about the available
commands, see the CLI guide you recieved with your unit.
P/N 480-0003-00-12
9-19
View RADIUS statistics

Display RADIUS statistics
At any time, you can display the statistics for connection between the RADIUS
server and the Tenor as follows:
2. At the Quintum prompt, type display radius statistics (or dis ra stat).
For each RADIUS server, Primary and Secondary (if configured), there is an
Authentication row that displays the number of authentication and authorization
attempts, responses, and timeouts accepted by the RADIUS server. Also included
is the number of authentication attempts rejected. The Accounting Row displays
the number of accounting attempts, responses, and timeouts. See Figure 9-3.
Figure 9-3 Radius Statistics Example

PRIMARY RADIUS SERVER STATISTICS
Attempts Responses
Timeouts
Accepts
Rejects
5318
243
Authentication:
6522
5561
961
Accounting:
6107
5849
258
SECONDARY RADIUS SERVER STATISTICS

Attempts Responses
Authentication:
Accounting:
P/N 480-0003-00-12
Timeouts
Accepts
Rejects
93
712
99
613
37
21
16
9-20
Clear RADIUS statistics

You can clear the RADIUS statistics as follows:
2. At the Quintum prompt, type display radius statistics 0 (or dis ra stat 0).
All RADIUS statistics fields will be set to 0.
P/N 480-0003-00-12
9-21
Call Flow - Specifications

Pre-paid Calling Card - Call Flow (with default language)
Figure 9-4 is a diagram of the call flow for pre-paid calling card service, which
details the messages transmitted between the following components:
Calling Party. The originating caller using a pre-paid calling card.
Prepaid Enabled Tenor. The Tenor performing the IVR functions.
RADIUS Server. Remote Authentication Dial-In User Service for authenticating
and authorizing user access to the VoIP network. The RADIUS 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.
Called Party. The destination called party.
P/N 480-0003-00-12
9-22
Figure 9-4 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
DISCONNECT
STOP ACCOUNTING IP LEG
STOP ACCOUNTING IP LEG ACK
STOP ACCOUNTING TELEPHONY LEG
STOP ACCOUNTING TEL LEG ACK
P/N 480-0003-00-12
9-23
Post-paid Calling Card - Call Flow (with default language)

Figure 9-5 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 performing the IVR functions.
standardized message formats for transmitting and receiving dialed information,
billing server.
P/N 480-0003-00-12
9-24
Figure 9-5 Post-paid Account - Call Flow (default language)

POSTPAID
ENABLED
TENOR
CALLING
PARTY
RADIUS
SERVER
CALLED
PARTY
V
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)
Please Enter The Phone Number to call
AUTHENTICATION RESPONSE
GET DNIS
AUTHORIZATION RESPONSE
SETUP
CONNECT
DISCONNECT
STOP ACCOUNTING
STOP ACCOUNTING ACK
P/N 480-0003-00-12
9-25
Pre-paid and Post-paid Calling Card - Call Flow (with multiple

language support)
Figure 9-6 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 or post-paid calling card.
Tenor. The Tenor performing the IVR functions.
billing server.
P/N 480-0003-00-12
9-26
Figure 9-6 Pre-paid and Post-paid Calling Card - Call Flow with multiple
language support )
CALLING
PARTY
RADIUS
SERVER
TENOR
SETUP
CONNECT
CALLED
PARTY
[START ACCOUNTING]
[START ACCOUNTING ACK]
Welcome
press 1 for English (played in English)
press 2 for Persian (played in Persian)
press 3 for Mandarin (played in Mandarin)
press 4 for French (played in French)
Same
procedure
as Figureas
1-4inand
Figure9-4
1-5
Same
procedure
Figure
P/N 480-0003-00-12
and 9-5
9-27
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 multisession key at anytime and making a new call. When the called party disconnects
the call first, the Tenor asks if the caller wants another call; the user can then press
the designated key. Figure 9-7 is a diagram of the call flow for pre-paid and postpaid call card service (with multi-session support), which details the messages
transmitted between the following components:
Calling Party. The originating caller using a pre-paid or post-paid calling card.
Tenor. The Tenor performing the IVR functions.
billing server.
Called Party 1. The first destination called party.
Called Party 2. The second destination called party.
P/N 480-0003-00-12
9-28
Figure 9-7 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)
CONNECT
Case 2> DISCONNECT
If you want another call,
press ** or ##
STOPACCOUNTING (Leg 1)
## or **
Please Enter Destination Number
GET Destination Number
AUTHORIZATION (DNIS)
CONNECT
P/N 480-0003-00-12
9-29
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.
Figure 9-8 is a diagram of the call flow for ANI Authentication Application Type
1, which details the messages transmitted between the following components:
ANI AUTH Enabled Tenor. The Tenor which enables the ANI authentication
functions.
with ANI the calling number.
P/N 480-0003-00-12
9-30
Figure 9-8 ANI Authentication Application Type 1 - Call Flow

ENABLED
TENOR
PARTY
SERVER
SETUP
No: Fast Busy
Yes : AUTHENTICATION (ANI)

ANI
No: Fast Busy
Auth fail
of ANI
CONNECT
Second Dial Tone

GET DNIS
SETUP
CONNECT
DISCONNECT
P/N 480-0003-00-12
9-31
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 asks PIN number by prompt) and
(3) Incoming packet has the ANI, but authentication with the ANI fails and Tenor
prompts for the PIN number.
Figure 9-9 is a diagram of the call flow for ANI Authentication Application Type
2, which details the messages transmitted between the following components:
ANI AUTH Enabled Tenor. The Tenor which enables the ANI authentication
functions.
with ANI the calling number.
P/N 480-0003-00-12
9-32
Figure 9-9 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
ANI auth fail : Pin prompt Tone
GET PIN
Auth fail
of ANI
AUTHENTICATION (PIN) 3
CONNECT
Second Dial Tone
GET DNIS
SETUP
CONNECT
DISCONNECT
P/N 480-0003-00-12
9-33
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 9-3 lists the message attributes in the Start Accounting Request message
packet sent between the Tenor and the RADIUS server. Start Accounting is
optional.
Table 9-3 Start Accounting Request Message Attributes

IETF
Attribute
Number
Attribute
Name
NAS-IPAddress
26
Cisco-NAS-Port
61
Vendor
Specific
Attribute
Number
Description
Value
Format
Sample
IP Address of the
requesting Tenor
Numeric
3506546880
Tenor's physical
port on which the
call is active
String
Fxs1/0/1
NAS-Port-Type
Tenor's physical
port type
String
0: Asynchronous
User-Name
Account number,
calling party number, or blank
String
7325551212
30
Called-StationId
The IVR access

number, normally
an 800 number
String
8004609000
31
Calling-StationId
Calling Party
Number (ANI)
String
7329701330
40
Acct-StatusType
Account Request
Type (start or stop)
Numeric
1: start, 2: stop
P/N 480-0003-00-12
9-34
Service-Type
Type of service
requested
Numeric
1: login
26
h323-gw-id
33
Name of the Tenor
String
Quintum Tenor
26
h323-conf-id
24
16 octets h323
GUID
16 octets
26
h323-incomingconf-id
A number to match
multiple calls in a
session
16 octets
26
h323-call-origin
26
The call relation to

the tenor
String
Answer, Originate
etc
26
h323-call-type
27
Protocol type or
family used on this
leg of the call
String
Telephony or
VOIP
26
h323-setup-time
25
Setup time in NTP

format (hours,
minutes, seconds,
microseconds,
time_zone, day,
month,
day_of_month,
year)
String
44
Acct-Session-Id
A unique accounting identifier match start & stop
String
13432
41
Acct-DelayTime
Number of seconds tried in sending a particular

record
Numeric
P/N 480-0003-00-12
9-35
Stop Accounting Request Message Attributes

Table 9-4 lists the message attributes in the Stop Accounting Request message
packet sent between the Tenor and the RADIUS server.
Table 9-4 Stop Accounting Request Message Attributes

IETF
ATTRIBUTE
NUMBER
Attribute
Name
Vendor
Specific
Attribute
Number
Description
Value
Format
Sample
NAS-IPAddress
IP Address of the
requesting Tenor
Numeric
3506546880
61
NAS-PortType
Tenor's physical port

type on which the call
is active
Numeric
0:
Asynchronou
s
User-Name
Account number or
calling party number
String
7325551212
30
CalledStation-Id
Destination phone
number
String
7324609000
31
CallingStation-Id
Calling Party Number

(ANI)
String
7329701330
40
AcctStatusType
Account Request
Type (start or stop)
Numeric
1: start 2:
stop
ServiceType
Type of service
requested
Numeric
1: login
26
CiscoNAS-Port
Tenor's physical port

on which the call is
active
String
Fxs1/0/1
P/N 480-0003-00-12
9-36
Quintum_Te
nor
26
h323-gw-id
33
Name of the Tenor
String
26
h323-confid
24
16 octets h323 GUID
16 octets
26
h323incomingconf-id
A number to match
multiple calls in a
session
16 octets
26
h323-callorigin
26
The call relation to the

tenor
String
Answer,
Originate
26
h323-calltype
27
Protocol type used on

this leg of the call
String
Telephony or
VOIP
26
h323setup-time
25
Setup time in NTP

format
String
26
h323connecttime
28
Connect time in NTP

format
String
26
h323disconnecttime
29
Disconnect time in
NTP format
String
26
h323disconnectcause
30
Q.931 disconnect
cause code
Numeric
26
h323voicequality
31
ICPIF of the voice

quality
Numeric
26
h323remoteaddress
23
IP address of the
remote gateway
Numeric
P/N 480-0003-00-12
9-37
44
AcctSession-Id
A unique accounting
identifier-match start
& stop
String
42
Acct-InputOctets
Number of octets
received for that call
duration
Numeric
43
AcctOutputOctets
Number of octets sent

for that call duration
Numeric
47
Acct-InputPackets
Number of packets
received during the
call
Numeric
48
AcctOutputPackets
Number of packets
sent during the call
Numeric
46
AcctSessionTime
The number of
seconds for which the
user receives service.
Numeric
41
AcctDelayTime
No of seconds tried in
sending a particular
record.
Numeric
P/N 480-0003-00-12
9-38
Authentication Request Message Attributes

Table 9-5 lists the message attributes in the Authentication Request message package sent between the Tenor and the RADIUS server.
Table 9-5 Authentication Request Message Attributes

IETF
ATTRIBUTE
NUMBER
Attribute
Name
Vendor
Specific
Attribute
Number
Description
Value
Format
Sample
NAS-IPAddress
IP Address of
the requesting
Tenor
Numeric
3506546880
NAS-Port-Type
Tenor's physical
port type on
which the call is
active
Numeric
0:
Asynchronous
User-Name
Account
number, calling
party number,
or blank
String
7325551212
26
h323-conf-id
16 octets h323
GUIDE
16 octets
31
Calling-StationId
Calling Party
Number (ANI)
String
7329701330
26
h323-ivr-out
IVR Access
Number,
normally an
800 number
String
ACCESS:80055
51234
User-Password
16 octets user
password
String
61
P/N 480-0003-00-12
24
9-39
Authentication Response Message Attributes

Table 9-6 lists the message attributes in the Authentication Response message
Table 9-6 Authentication Response Message Attributes

IETF
ATTRIBUTE
NUMBER
26
26
Attribute
Name
h323-returncode
h323-preferredlang
26
h323-creditamount
26
h323-billingmodel
26
h323-currencytype
P/N 480-0003-00-12
Vendor
Specific
Attribute
Number
Description
Value
Format
103
The reason
for failing
authenticatio
n
Numeric
107
Lang to play
prompt
specified by
h323-promptid.
ISO 639-1
101
Amount of
credit
(currency)
remaining in
the account
Numeric
109
Type of
billing
service for a
specific call.
Numeric
1:debit/
prepaid
110
Currency for
use with
h323-creditamount
ISO 4217
USD
Sample
2 Invalid pin
number
En
13.25
9-40
31
h323-prompt-id
104
Index into an
array of
prompt files
used by the
Tenor
Numeric
27
Authorization Request Message Attributes

Table 9-7 lists the message attributes in the Authorization Request message packet
sent between the Tenor and the RADIUS server.
Table 9-7 Authorization Request Message Attributes

IETF
ATTRIBUTE
NUMBER
Attribute
Name
Vendor
Specific
Attribute
Number
Description
Value
Format
Sample
NAS-IPAddress
IP Address of the
requesting tenor
Numeric
3506546880
61
NAS-PortType
Tenor's physical
port type on
which the call is
active
Numeric
0: Asynchronous
User-Name
Account number
or calling party
number or blank
String
7325551212
26
h323-conf-id
16 octets h323
GUID
16 octets
30
Called-Station-Id
Destination
phone number
String
7324609000
31
Calling-Station-Id
Calling Party
Number (ANI)
String
7329701330
P/N 480-0003-00-12
24
9-41
26
h323-ivr-out
User-Password
P/N 480-0003-00-12
Flag for subsequent authorizations in a session
String
FOLLOW_
ON_FLAG:
0
16 octets user
password
9-42
Authorization Response Message Attributes

Table 9-8 lists the message attributes in the Authorization Response message
Table 9-8 Authorization Response Message Attributes

IETF
ATTRIBUTE
NUMBER
26
26
Attribute Name
h323-return-code
h323-credit-time
P/N 480-0003-00-12
Vendor
Specific
Attribute
Number
103
102
Description
Value
Format
Sample
The reason for

failing authentication
numeric
2 Invalid pin
number
Number of seconds for which

the call is
authorized
numeric
360
9-43
Appendix A: Cables
P/N 480-0003-00-12
A-1
Appendix A: Cables
RJ-45 Cable Pinouts

RJ-45 cable connector pinouts are given below for the various cables used with the
Tenor unit; pinouts are given to help you identify the proper connector to accommodate your specific networking requirements. The RJ-45 (ISO 8877) connector is
the EIA/TIA standard for Unshielded Twisted Pair (UTP) cable; the wiring color
codes are UTP standard coloring. This pin order is shown in Figure A-10.
Figure A-10 RJ-45 Pin Order
RJ-45 (for 10/100BT Connection)

An RJ-45 (10/100BaseT) straight through cable can be used to connect the Tenor
unit to an Ethernet switch. The pinouts are listed below.
Figure A-11 RJ-45 (10/100BT) Connector Pinouts - Diagram
A-2
P/N 480-0003-00-12
Appendix A: Cables
Figure A-12 RJ-45 (10/100BT) Connector Pinouts
Table A-1 RJ-45 (10/100BT) Connector Pinouts

Pin #
Signal
Definition
Color
RX ring/TX +
Receive Ring/Transmit
Data
White w/orange
RX tip/TX -
Receive Tip/Transmit
Data
Orange
RX +
Transmit Data
White w/green
TX ring
Transmit Ring
Blue
TX tip
Transmit Tip
White w/blue
RX -
Receive Data
Green
n.c.
no connect
White w/Brown
n.c.
no connect
Brown
RJ-45 (for PSTN or PBX Connection)

An RJ-45 straight through cable can be used to connect the Tenor unit to the PSTN
or PBX. You can use the connector pinouts listed in the following pages to build
both cables.
P/N 480-0003-00-12
A-3
Appendix A: Cables
Figure A-13 RJ-45 (PSTN/PBX) Connector Pinouts - Diagram
Table A-2 RJ-45 Connector Pinouts

Pin #
Signal
Definition
Color
n.c.
no connect
White w/orange
n.c.
no connect
Orange
Ring
Ring Ports 5-8
White w/green
Ring
Ring Ports 1-4
Blue
Tip
Tip Ports 1-4
White w/blue
Tip
Tip Ports 5-8
Green
n.c.
no connect
White w/Brown
n.c.
no connect
Brown
A-4
P/N 480-0003-00-12
Appendix A: Cables
RJ-11 Cable Pinouts

An RJ-11 cable can be used as an alternative to an RJ-45 to connect the Tenor unit
to the PSTN or PBX. Use the connector pinouts below.
Figure A-14 RJ-11 Connector Pinouts
Table A-3 RJ-11 Connector Pinouts

Pin #
Signal
Definition
Color
n.c.
no connect
Black
Ring
Ring Ports 1-4
Green
Tip
Tip Ports 1-4
Red
n.c.
no connect
Yellow
P/N 480-0003-00-12
A-5
Appendix A: Cables
DB-9 Cable Pinouts

The DB-9 Male to DB-9 Female cable is a 9 pin cable connector (with RS-232
interface) used to connect Tenor Gateway to your PCs asynchronous console port.
The pin order is shown in shown in Figure A-15.
Figure A-15 DB-9 Connector Pin Order

12345
6789
Table A-4 DB-9 Connector Pinouts
Pin #
Function
Direction
Description
DEC
Receive
Data Carrier
Detect
RX
Receive
Receive Data
TX
Transmit
Transmit Data
DTS
Transmit
Data Terminal
Ready
SG
Transmit
Signal Ground
DSR
Receive
Data Set Ready
RTS
Transmit
Request to Send
CTS
Receive
Clear to Send
RI
Receive
Ring Indicator
P/N 480-0003-00-12
A-6
Appendix B: Specifications/
Approvals
P/N 480-0003-00-12
B-1
Voice/Fax
Call Routing:
Coding:
Voice Algorithms:
PBX/PSTN/IP
A-law, mu-law
G.723.1A (5.3, 6.3 Kbps), G.726 (16, 24, 32, 40
Kbps), G.729A, G711
Fax Support:
Group III at 2.4, 4.8, 7.2, 9.6, 12, 14.4 Kbps
Automatic Call Detection: Voice/Modem/Fax
PSTN/PBX Connections
Interface:
Analog, FXO Interface (PSTN side), FXS Interface

(PBX side)
Connector:
RJ-45
Ringing Voltage:
40 volts RMS at 20 Hz (with 5 REN load and 1000
feet of 24 AWG wiring)
Ringing Cadence:
2 seconds on and 4 seconds off
Maximum Loop Current: 24 mA
Ringer Equivalence Number:5 up to 1000 feet of 24 AWG or heavier
Ringing Frequency:
20, 25, or 50 Hz
Ringing Voltage:
40 Volts RMS (at 20 Hz)
LAN Connection
LAN Support:
Connection Type:
10/100 Mbps Ethernet

Autosensing
Physical
Position:
Depth:
Length:
Height:
B-2
19 (48.7 cm) rack mountable, desktop stackable,

wall-mountable
10 3/4 (27.6 cm)
17 3/8 (44.5 cm)
1 3/4 (4.5 cm)
P/N 480-0003-00-12
Weight:
8.0 lbs (3.6 kg)
Electrical
Ethernet:
PBX/PSTN:
Connectors:
Console Port:
Power:
Standard 10/100Base-T RJ-45 interface (IEEE 802.3)

Standard RJ-45 connectors
4 (A400 and A800) RJ-45 connectors for PBX connection
4 (A400 and A800) RJ-45 connectors for PSTN connection
RS-232/DB-9 Female
AC Power at 100-240 volts and 50-60 Hz
Environmental
Operating Temperature:
Operating Humidity:
Altitude:
Storage Temperature:
40 to 104 F (0 - 40 C)
20% to 80% non-condensing
-200 to 10,000 feet, or -60 to 3,000 meters
14 to 140 F, or -10 to 60 C
Agency Approvals
EMC
Safety
PSTN
Other
P/N 480-0003-00-12
EN55022: 1995; EN55024:1998

FCC Part 15 Class A
EN60950:1992
UL 1950 3rd edition
CA 22.2 No. 950-95
FCC Part 68, CSO-03,
VCCI Class A ITE
AS/NZS 3548: 1995
CNS 13438
B-3
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. However, there is no guarantee that interface will
not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the
equipment off and on, the user is encouraged to try to correct the interference by
one or more of the following measures.
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the
receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
CAUTION:
Changes or modifications not expressly approved by the party

responsible for compliance could void the user's authority to operate the equipment.
This device complies with Part 68 of the FCC Rules. On the back of this equipment
is a label that contains, among their information, the FCC registration number for
this equipment. If requested, this information must be provided to the Telephone
Company.
Facility Interface Codes For Digital Services supported:
B-4
04DU9-BN 1.544 Mbps Superframe Format (SF) without line power.
04DU9-DN 1.544 Mbps SF and B8ZF without line power.
04DU9-1KN 1.544 Mbps ANSI ESF without line power.
04DU9-1SN 1.544 Mbps ANSI ESF and B8ZF without line power.
04DU9-1ZN 1.544 Mbps ANSI ESF and ZBTSI without line power.
P/N 480-0003-00-12
Service Order Codes For Digital Services supported:
6.0N We do not provide billing and encoded analog protection.
An FCC compliant telephone cord with a modular plug is provided with this equipment. This device connects to the telephone network via an RJ45 plug and jack.
The plug and jack also comply with FCC part 68 rules.
If this device causes harm to the telephone network, the telephone company will
notify you in advance that temporary discontinuance of service may be required.
But, if advance notice is not practical, the Telephone Company will notify the customer as soon as possible. Also, you will be advised of your right to file a complaint with the FCC if you believe it is necessary.
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.
If trouble is experienced with this device, for repair and warranty information,
please refer to the Technical Support insert for repair information and the warranty
section of this Product Manual for warranty information.
In the event of device malfunction, all repairs should be performed by Quintum
Technologies, Inc. or an authorized agent. It is the responsibility of users requiring
service to report the need for service to our company or to one of our authorized
agents. In the event service is required, refer to the Technical Support insert for
information.
If the device is causing harm to the telephone network, the telephone company may
request that you disconnect the equipment until the problem is resolved.
This registered device is capable of providing users access to interstate providers of
operator services through those of equal access codes.
This registered device provides proper answer supervision to the PSTN when DID
calls are answered by the called station, answered by the attendant, routed to a
recorded announcement that can be administered by the CPE user, or routed to a
dial prompt and this device returns answer supervision on all DID calls forwarded
to the PSTN. Permissible exceptions are as follows: a call is unanswered, a busy
tone is received, a recorded tone is received.
P/N 480-0003-00-12
B-5
The Ringer Equivalence Number, or REN, is used to determine the number of

devices, which may be connected to the telephone line. An excessive REN may
cause the equipment to not ring in response to an incoming call. In most areas, the
sum of the RENs of all equipment on a line should not exceed three (3.0).
B-6
P/N 480-0003-00-12
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. The equipment must also be installed using an acceptable method of connection. In some
cases, the inside wiring associated with a single-line individual service may be
extended by means of a certified connector assembly. The customer should be
aware that compliance with the above conditions may not prevent degradation of
service in some situations.
Repairs to certified equipment should be made by an authorized Canadian maintenance facility designated by the supplier. Any repairs or alterations made by the
user to this equipment, or equipment malfunctions, may give the telecommunications company cause to request the user to disconnect the equipment.
Users should ensure for their own protection that the electrical ground connections
of the power utility, telephone lines, and internal metallic water pipe system, if
present, are connected together. This precaution may be particularly important in
rural areas.
CAUTION:
P/N 480-0003-00-12
Users should not attempt to make electrical ground connections by

themselves, but should contact the appropriate inspection authority
or an electrician, as appropriate.
B-7
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, CS-03
Manufacturer:
Quintum Technologies Inc.
Manufactured By:
14 Christopher Way
Eatontown NJ
USA
Type of Equipment:
Model Number:
Harvard Custom Manufacturing

94 Route 38
Owego NY
USA
Delta Networks Inc.

8, Kon Jan West Road
Liitu Industrial Zone
Keelung 206, Taiwan ROC
Analog VoIP Gateway

Tenor A400/A800
We, the undersigned, hereby declare that the equipment specified above conforms to the above
Directive(s) and standard(s) as of this date.
Place: Eatontown, NJ, USA
Date: 3/15/2001
Karl V. Stahl III

EMC/Product Safety Engineer
Technical File available through:
P/N 480-0003-00-12
William J. Truex
Director of Operations
14 Christopher Way
Eatontown, NJ 07724
USA
B-8
TAIWAN EMI NOTICE
P/N 480-0003-00-12
B-9
Appendix C: Getting Acquainted

with VoIP
P/N 480-0003-00-12
C-1
Getting Acquainted with VoIP Network

This Appendix gives you a general overview of VoIP, including how the Tenor
Analog VoIP Gateway A400/A800 fits into your network LAN and WAN architecture. You can use this information to learn VoIP terms and technology, as well as
set up your network system to maximize the voice quality and toll savings the
Tenor unit offers.
What is Voice over Internet Protocol (VoIP)?

VoIP (Voice over Internet Protocol) is a technology which enables voice and fax
communications to be passed through your existing data network using the TCP/IP
protocol, bypassing the PSTN. The Tenor Analog gateway contains a special
microprocessor called a DSP (Digital Signal Processor) which takes the analog
voice and fax data coming from your PBX, compresses it, and converts it into
packets that can be transported over your Ethernet LAN. The data can then be
transported through an IP-based router to reach a WAN or remote location. As a
result, your voice and FAX traffic runs over your data network to bypass the PSTN
and avoid long distance tolls associated with the public network.
Quick Look at WAN/LAN

A LAN is a local area network that carries data between workstations in the same
location. Workstations in a LAN are connected together usually by an Ethernet
hub to share information. A number of LANs connected together through a long
distance communications medium is called a WAN (Wide Area Network). For
example, your company may have a LAN in New York, a LAN in Tokyo, and a
LAN in Los Angeles. When these sites connect together over the data network or
the public network, it is considered a WAN. As a result, intra-corporate information is passed through the data network from one LAN to another LAN site in a
remote location.
Ethernet
Ethernet is a Local Area Network (LAN) data network design that connects
devices like computers, printers, and terminals. It transmits data over twisted pair
of coaxial cable at speeds of 10 or 100 Mbps.
C-2
P/N 480-0003-00-12
Intranet Telephony
An Intranet (also known as Enterprise IP network) is a private "Internet web site"
allowing you to deploy services within your company from a dedicated web server.
This web site is separate from your external web site for security reasons. Intranets
can be deployed within your company over the internal LAN, or a number of
LANs at corporate sites connected by an IP WAN or IP Virtual Private Network
(IP-VPN). Because Intranets are based on Internet technology and use the Internet
Protocol (IP) they may be used for deploying voice (VoIP) and FAX (FoIP) services. A major benefit of using an Intranet when deploying VoIP or FoIP services
is that the network architecture is well defined insuring that network delay, latency,
and packet loss are predictable.
Extranet Telephony
An Extranet is similar to an Intranet except that it is externally accessible by a limited number of people on a secure basis. Because Extranets are based on Internet
technology and use the Internet Protocol (IP) they may be used for deploying voice
(VoIP) and FAX (FoIP) services. A major benefit of using an Extranet when
deploying VoIP or FoIP services is that the network architecture is well defined
insuring that network delay, latency, and packet loss are predictable.
Internet Telephony
The Internet is a universally accessible public packet switched network. It consists
of a Global network of high speed computers and packet routers connected in a
complex mesh structure. This network uses the standardized Internet Protocol (IP)
to pass packets from point to point through the network. These packets are directed
from point to point within the network by data routers. The connection between
two routers is called a "hop" and a typical connection will consist of many hops.
The number of hops will determine the delay and latency in the connection. Congestion may cause packets to be lost within the network. The Internet was designed
to provide data communications on a "best available connection" basis and does
not guarantee any "Quality of Service". This mode of operation is suitable for data
and E-Mail transmissions which are not delay sensitive, but is not ideal for realtime data streams such as voice or video.
P/N 480-0003-00-12
C-3
Gatekeeper vs. Gateway

Gateways are voice-only or voice/data/video devices which connect IP packet
based networks and circuit-switched networks. A gateway converts the circuit
switched calls to VoIP calls.
The Gatekeeper performs IP call routing functions, such as bandwidth control, call
control signaling and call authorization for Gateways, IP phones, and H.323 terminals. The Gatekeeper communicates with other Gatekeepers through a Border Element.
H.323 Network
H.323 is a protocol standard for sending multimedia communications (e.g., data/
voice/video) simultaneously over packet-based networks, such as IP. H.323 controls standards such as call control and call routing. An H.323 network consists of
zones and administrative domains. A zone is a group of endpoints (e.g, gateways,
terminals, etc.) in one corporate site. Each zone is controlled by one Gatekeeper
and all zones together in a company is considered an administrative zone.
TCP/IP
TCP/IP (Transmission Control Protocol/Internet Protocol) is a layered data communications protocol defined by the IETF. Each layer defines a different aspect of
how two devices should talk to each other (i.e., when a network device should
send/receive data). For example, layer one is the physical means of communications (e.g., modem), whereas layer 3 is the network type (e.g., Internet).
TCP/IP is a combination of two layers of this communication protocol. TCP (layer
4) does the actual transport of data; IP (layer 3) sets the rules for moving the data
from one end of the network to another. TCP/IP uses an IP address to identify a
location for specific network devices. Each Tenor unit will have a unique IP
address, which you configure through the Tenor CAMWizard.
Putting it all Together

Tenor Gateway is an H.323 based VoIP gateway/gatekeeper which takes voice and
fax signals from a PBX, converts and compresses the signals into packetized data
C-4
P/N 480-0003-00-12
and drives them over TCP/IP through a 10/100 Ethernet LAN. The data can then be
routed out to your corporations WAN. The Gateway is connected to the PBX via
upstream analog lines; it is connected to the PSTN via downstream analog lines.
P/N 480-0003-00-12
C-5
C-6
P/N 480-0003-00-12
GLOSSARY
A
Alarm. A brief message that appears on
your screen when the Tenor unit encounters a problem (i.e., failed interface).
Auto Switching. If a network conditioning
jeopardizes the voice quality, the Tenor
unit will automatically switch the call
to PSTN.
B
Bandwidth Management. Controls the
amount of bandwidth available to use
for VoIP calls.
Border Element. Provides access into or
out of an administrative domain. The
Tenor unit has two types of Border Elements: Primary and Secondary.
Bypass Number. A telephone number that
is automatically sent to the PSTN, without going VoIP.
C
CAS. Channel Associated Signaling. A
form of circuit switched signaling.
CCS. Common Channel Signaling. A form
of signaling that uses the D channel as
the signal channel.
CDR. Call Detail Recording. A string of
data which contains call information
P/N 480-0003-00-12
such as call date and time, call length,

calling party and called party.
CDR Server. The server (or workstation)
responsible for receiving and processing CDRs as they are generated.
D
DB-9. A 9-pin cable used to connect the
Tenor unit to a PCs asynchronous console port.
E
Ethernet. A local area network design that
transmits 10-Mbit/s data over a shielded coaxial cable.
Extranet. Communications with a source
outside your company.
G
Gatekeeper.An H.323 system which provides call control and administrative
services in H.323 endpoints.
Gateway. A device (i.e., Tenor unit) which
connects IP packet-based networks and
circuit-switched networks.
H
H.323. A protocol standard for sending
multimedia communications (i.e.,
voice/data) simultaneously over packet-based networks, such as IP.
Hop-off PBX Call. A toll call which is
leaked out to the PSTN in order to
eliminate the toll charges.
Glossary-1
Internet. A packet based network which

transports voice/video/data over TCP/
IP.
RJ-45. A CAT 5 cable used to connect the

Tenor unit to a PBX/PSTN/Ethernet.
Intranet communication. Communication

within the same company, usually
through an Ethernet hub.
IP Address. A unique 32 bit address that
identifies a network device is connected to the network via TCP/IP.
IVR/Voice Response. Enables you to offer
services such as Pre-paid calling cards
and Post-paid accounts.
L
LAN. Local Area Network. A data communications arrangement which links
computers together at the site to share
files, printer, etc., using a local network
design, typically Ethernet.
LED.Displays the health of the unit via individual lights that appear on the front
panel.
P
PBX. Private Branch Exchange. Telephone switch located on a customers
premises that establishes circuits between users and the PSTN (public network).
PSTN. Public Switched Telephone Network (also known as Central Office)
Telephone company switching facility.
Glossary-2
S
SelectNet. The Tenor monitors your network for jitter, latency, and packet loss
and will automatically switch customer
calls to the PSTN when required.
SNMP. Simple Network Management Protocol (SNMP) is the standard protocol
used to exchange network information
between different types of networks.
Subnet Mask. An IP address that determines how an IP address is divided into
network and host portions according to
the bits.
TASQ (Transparent Auto-Switch Quality). Provides a safety net, which

monitors the network packet delay for
an IP call.
Tenor Analog Gateway. A Multi-Path
gateway which transmits voice/fax/modem data over the IP through an Ethernet LAN, bypassing the public
network.
Tenor CAM. Web-based management tool
which enables you to configure, manage, and monitor the health of a Tenor
unit.
Tenor CAMWizard. Web management
tool which enables you to configure the
minimal set of VoIP parameters.
P/N 480-0003-00-12
TCP/IP. Transmission Control Protocol/

Internet Protocol. TCP/IP is a standard
data communications protocol. It has
several layers that define a different aspect of how two devices should talk to
each other over the WAN or LAN network.
Trunk Group. A collection of channels
used to connect the Tenor unit to the
network or another piece of equipment.
W
WAN. Wide Area Network. A few remote
LAN sites linked together via modem.
P/N 480-0003-00-12
Glossary-3
INDEX
A
Active alarms
Alarm history
Alarm Manager
Alarms
active
clear
delete
display
exit
fields
filter
history
list of alarms
orange
red
view
view via Telnet
view via UNIX
white
yellow
ANI Authentication
7-12
7-13
7-2
7-2
7-12, 7-16
7-20
7-15
7-2
7-15
7-4
7-14, 7-19
7-13, 7-18
7-6
6-9, 7-3
6-9, 7-3
7-10
7-10
7-11
6-9, 7-3
6-9, 7-3
9-4
B
Back panel
illustration
label
power cord
power switch
bandwidth
configure
Bypass DN
P/N 480-0003-00-12
2-7
2-7
2-7
2-7
2-7
5-33
5-26
Cables
2-7
AC power cord 2-7
DB-9
2-7, A-6
RJ-11
2-7
RJ-45
A-2, A-5
Call flow
samples
9-22
CAMWizard
1-17
border element 4-8
CAS
4-8
date and time
4-4
local DN
4-6
local information 4-4
password
4-3
run
4-3
submit function 4-9
trunk group
4-6
Capabilities
call routing
1-13
data network calls1-12
flexible networking1-16
hop-off PBX
1-15
PBX calls
1-11
PSTN calls
1-12
virtual tie line
1-15
CDR
connect with server8-4
connect with Tenor8-5
output
8-6
overview
8-2
Configure
bandwidth
5-32
border element 5-30
bypass DN
5-26, 5-27
CAS
5-21, 5-22
gatekeeper
5-29
hop-off PBX
5-24
local DNs
5-18, 5-20
Index-1
local information
PBX trunk
PSTN trunk
Connect
PBX/Key System
PC
D
DB-9
3-10
3-14
2-7, A-6
5-27
5-6
5-12
2
1-5
F
Fax
3-11
FCC
warnings
B-4
Features
1-7
call routing
1-8
CDR
1-10
configuration
1-7
easy connect
1-9
H.323 gatekeeper1-9
multiple interfaces1-8
SelectNet
1-8
service
1-8
system monitoring1-9
unique design
1-7
Finding
6
Front panel
console port
2-3
diag option
2-3
Ethernet LEDs 2-5
Index-2
2-2
2-3
2-4
2-2
2-3
2-2
2-2
G
Gatekeeper
Gateway
E
Edit
bypass DN
password
trunk group
Ethernet
Extranet
illustration
LAN port
LEDs
PBX port
port assignment
PSTN port
reset
5-9
5-16
5-11
4
4
H
H.323
Hardware
back panel
description
front panel
Help
Hop-off PBX
4
2-7
2-2
2-2
6
5-24
I
Implementation
extranet
1-5
internet
1-6
intranet
1-4
Installation
3-3
connect
3-10
guidelines
3-3
package contents3-3
position unit
3-3
rack
3-5
tabletop
3-4
wall mount
3-7
IVR
1-10
call types
9-3
configure via CLI 9-19
definition
9-2
P/N 480-0003-00-12
quick start
9-6
typical connection9-6
voice prompts
9-11
L
LAN
definition
2
LEDs
2-4
alert
2-6
PBX
2-6
power
2-6
PSTN
2-6
system
2-6
Local Information
configure
5-7
Local Information screen5-7
M
multi-session
9-4
N
NATAccess
1-14
P
PacketSaver
1-14
PBX
port assignment 2-3
PBX trunk group
5-14
Phone
connect to Tenor 3-11
Pinouts
DB-9
A-6
RJ-45
A-2, A-5
post-paid account 9-3
Power up
3-15
Pre-installation guidelines3-4
pre-paid calling card 9-3
P/N 480-0003-00-12
Product Guide
conventions
4
PSTN
port assignment 2-3
PSTN trunk group screen5-10
R
RADIUS
view statistics
RJ-11
RJ-45
9-20
2-7
2-3
S
Screen
Border Element 4-8
Local Information 4-4
PBX trunk
5-14
PSTN Trunk
5-5
Set Password
5-5
Trunk Group
4-6
SelectNet
1-8
SNMP
configure
6-7
definition
6-2
download files
6-4
support
1-15
traps
6-9
Specification
environmental
B-3
Specifications
electrical
B-3
LAN
B-2
physical
B-2
PSTN/PBX
B-2
voice/fax
B-2
System
power up
3-15
Index-3
TASQ
1-2
TCP/IP
4
Telephony
extranet
3
internet
3
intranet
3
Telnet
active alarms
7-16
Tenor
capabilities
1-11
description
1-2
features
1-7
typical implementations1-3
Tenor CAM
1-17
alarm manager 7-2
alarms
1-18
bandwidth
5-32
border element 5-29
bypass DN
5-26
CAS
5-21
change password5-5
configuration
1-17
discard changes 5-35
getting started
5-2
hop-off PBX
5-24
local DN
5-18
local information 5-7
logoff
5-35
logon
5-3
maintenance
1-18
password
5-19
PBX trunk group 5-14
PSTN trunk group5-10
screen buttons 5-3
submit changes 5-34
view alarms
7-16
Troubleshoot
9-1
UNIX
view alarms
Index-4
7-11
V
voice prompts
update
VoIP
definition
9-17
2
W
Wall mount
install dimensions3-8
installation
3-7
required materials3-5, 3-7
WAN
definition
2
P/N 480-0003-00-12
Warranty
QUINTUM TECHNOLOGIES, INC.
LIMITED WARRANTY AGREEMENT
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 Quintums authorized reseller or distributor (the Warranty
Period).
SERVICES:
In the event that you believe that you have discovered any such defect during one of the Warranty Periods listed above, you must call
the Technical Assistance Center (TAC) at 877-435-7553 within the United States or 732-460-9399 Internationally, 9:00 AM to 5:30
PM, Eastern Standard Time, for initial problem diagnosis. Quintum Technologies will perform warranty service at Quintum Technologies designated facility, provided the customer returns the Quintum Technologies Product in accordance with Quintum Technologies'
shipping instructions. Quintum Technologies' sole responsibility under this warranty shall be, at Quintum Technologies' option, to
either repair or replace the Quintum Technologies Product within 10 days. All defective Quintum Technologies Products, or defective
components thereof, returned under this warranty shall become Quintum Technologies' property. If Quintum Technologies determines
that the original Quintum Technologies Product did not contain a Material Defect, Purchaser shall pay Quintum Technologies all costs
of handling, transportation, and repairs at Quintum Technologies' prevailing rates, including all costs of providing an interim Quintum
Technologies Product.
The customer will also be given shipping instructions and a Return Material Authorization (RMA) number. This number is to be prominently displayed on the shipping container and referenced on all correspondence pertaining to the returned product. Customers are
responsible for shipping and insurance charges to return the defective product. Quintum shall pay for shipping and insurance charges
for the part being sent to the customer.
Please return any hardware together with the accompanying software media to Quintum following the RMA Procedure set out below
(you may also be asked to provide written documentation of your purchase).
CUSTOMER REMEDIES: Quintum and its suppliers entire liability and your exclusive remedy shall be, at Quintums option (i)
repair or replacement of the software media or hardware that does not meet Quintums Limited Warranty with new or like-new software
media or hardware or (ii) return of the price paid for software media or hardware that does not meet Quintums Limited Warranty.
Quintum shall have no responsibility, warranty or other obligations whatsoever as a result of (i) the use of the hardware and/or software
in a manner inconsistent with the accompanying manuals, license and limited warranty terms or this Agreement, or (ii) any modifications made to the hardware or software, or (iii) failure of the hardware or software as a result of accident, abuse or misapplication.
NO OTHER WARRANTIES: THE WARRANTIES SET FORTH ABOVE ARE EXCLUSIVE AND IN LIEU OF ALL OTHER
WARRANTIES. QUINTUM MAKES NO OTHER WARRANTIES, EXPRESS OR IMPLIED, AND QUINTUM EXPRESSLY DISCLAIMS ALL OTHER WARRANTIES, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, THE PROVISIONS SET FORTH ABOVE STATE
QUINTUMS ENTIRE RESPONSIBILITY AND YOUR SOLE AND EXCLUSIVE REMEDY WITH RESPECT TO ANY BREACH
OF ANY WARRANTY.
LIMITATION ON LIABILITY: NO LIABILITY FOR CONSEQUENTIAL DAMAGES: UNDER NO CIRCUMSTANCES AND
UNDER NO THEORY OF LIABILITY SHALL QUINTUM OR QUINTUMS SUPPLIERS BE LIABLE FOR COSTS OF PROCUREMENT OF SUBSTITUTE PRODUCTS OR SERVICES, LOST PROFITS, LOST SAVINGS, LOSS OF INFORMTION OR
DATA, OR ANY OTHER SPECIAL, INDIRECT, CONSEQUENTIAL OR INCIDENTAL DAMAGES, ARISING IN ANY WAY
OUT OF THE SALE, LICENSE OR USE OF, OR INABILITY TO USE, ANY QUINTUM PRODUCT (HARDWARE OR SOFTWARE) OR SERVICE, EVEN IF QUINTUM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND NOTWITHSTANDING ANY FAILURE OR ESSENTIAL PURPOSE OF ANY LIMITED WARRANTY.
PRODUCT RELOCATION: THE WARRANTIES SET FORTH ABOVE SHALL BE NULL AND VOID AND OF NO FURTHER
EFFECT IN THE EVENT THAT EITHER: (A) THE PRODUCTS ARE RELOCATED, MOVED, SHIPPED OR EXPORTED
(EITHER DIRECTLY OR INDIRECTLY) TO, OR TECHNOLOGY WITH REGARD TO THE PRODUCTS IS DISCLOSED TO,
ANY DESTINATION THAT IS PROSCRIBED UNDER PART 740 OF THE U.S. DEPARTMENT OF COMMERCE EXPORT
ADMINISTRATION REGULATIONS OR TO ANY NATIONAL OF ANY ONE OF THOSE COUNTRIES UNLESS PRIOR WRITTEN AUTHORIZATION HAS BEEN OBTAINED FROM THE U.S. DEPARTMENT OF COMMERCE OR SUCH ACTIONS ARE
OTHERWISE PERMITTED BY THE U.S. DEPARTMENT OF COMMERCE 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.
Notify Quintum Technical Assistance Center on Telephone: 877-435-7553 within the United States, 732-460-9399 Internationally, Monday through Friday from 8:30am till 5:30pm U.S. Eastern time.
2.
Provide Customer Services Department the following information:
Customer Name and Contact Name

Product Part number(s)
Product serial numbers
Quantity to be returned
Type of return (i.e., warranty return)
Reason for return
Proof of purchase (invoice or PO)
3.
An RMA number will be assigned for each shipment and that number must be quoted in all correspondence relating to the RMA
in question
4.
Shipment Instructions: Customer must follow any instructions supplied by the Customer Service Representative concerning
where the Product is to be returned, how the Product is to be packaged, which carrier is to be used, who should pay for the shipment and any labels to be put on the package. Unless otherwise directed by Quintums Customer Services Representative, please
return product to Quintum at:
REF RMA Number
Quintum Technologies, Inc.

14 Christopher Way
Eatontown, NJ 07724 USA
5.
Following all directions given by Customer Services Representative return the Product to the address given by the Customer Services Representative quoting the RMA number.
6.
Any product that is deemed failing under this Warranty and a replacement product has been shipped to the customer, the failing
product must be returned and delivered to the address given by the Customer Services Representative within 30 days of the
replacement being shipped.
PLEASE NOTE: All shipments require an authorized RMA number.

If the Customer does not comply with this procedure as set out above, Quintum reserves the right to charge Customer for the cost of the
replacement Product and/or freight (including duties and taxes) from Quintum regardless of the reason for the return. Quintum also
reserves the right to invoice the Customer for a replacement Product at the same time as the replacement is cross-shipped. This invoice
will, of course, be canceled if the original Product is returned within 30 days of cross-shipment and if found to be a valid warranty
return.
QUINTUM TECHNOLOGIES, INC.

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. No part of this document may be reproduced or transmitted in any form or by
any means without the express written permission of Quintum Technologies, Inc. Quintum Technologies, Inc.
disclaims liability for any and all damages that may result from publication or use of this document and/or its
contents except for infringement of third party copyright or misappropriation of third party trade secrets.
US GOVERNMENT RESTRICTED AND LIMITED RIGHTS
All documentation supplied by Quintum Technologies, Inc. to the United States Government is provided with
Restricted Rights. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (2) of the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19 or subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, as
appropriate.
All documentation, other than the documentation which is provided with Restricted Rights, is provided with
Limited Rights. U.S. Government rights to use, duplicate, or disclose documentation other than software documentation, is governed by the restrictions defined in paragraph (a) (15) of the Rights in Technical Data and computer software clause at DFARS 252.227-7013,
Manufacturer/Owner: Quintum Technologies, Inc. 14 Christopher Way, Eatontown, NJ 07724
ACKNOWLEDGEMENTS
Quintum Technologies, Inc., the Quintum Technologies logo, Tenor MultiPath VoIP Gateway, and TASQ are
trademarks, and in some jurisdictions may be registered trademarks of Quintum Technologies, Inc. Other trademarks appearing in this packaging are the property of their respective owners.
Copyright 2002 Quintum Technologies, Inc. All Rights Reserved.

Guia Tenor A400

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Guia Tenor A400

Uploaded by

Copyright:

Available Formats

Tenor VoIP MultiPath

Interactive Voice Response (IVR) . . . . . . . . . . . . . . . . . . . . .1-10

Chapter 2: Hardware Components

Assign IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16

Chapter 4: Getting Started via Tenor CAMWizard

Chapter 5: Configuration via Tenor CAM

Configure Local Directory Numbers. . . . . . . . . . . . . . . . . . . . . . . .5-18

Chapter 6: Working with SNMP

Download and Install SNMP Related Files . . . . . . . . . . . . . .6-4

Chapter 7: System Alarms

Chapter 8: Call Detail Recording

Chapter 9: Using IVR

About this Guide

About this Guide

Chapter 1: Overview: Includes a general overview of the product, including a

Chapter 2: Hardware Components: Hardware description.

Chapter 3: Installation. Describes how to install the Tenor unit, including

Chapter 4: Getting Started with Tenor CAMWizard. This chapter explains

Chapter 10: Troubleshooting/Maintenance. Describes how to troubleshoot

Appendix A: Cables. Cable pinout information.

Appendix B: Specifications/Approvals: List of Tenor Gateways specification

Appendix C: Getting Acqainted with VoIP. A general overview of VoIP and

About this Guide

About this Guide

About this Guide

Tenor CAM Conventions

Figure 5-1 Edit Box sample

Figure 5-2 Radio Button sample

Figure 5-3 Drop Down List sample

About this Guide

A description of Tenor A400/A800 units

What is Tenor VoIP MultiPath Switch?

Figure 1-1 Tenor Analog MultiPath Switch

Tenor Analog MultiPath VoIP Gateway A400/A800

Tenor Analog MultiPath Switch Analog Series is available in two versions:

Analog MultiPath Switch A400 (provides 4 analog lines/4 simultaneous

Analog MultiPath Switch A800 (provides 8 analog lines/8 simultaneous VoIP

Figure 1-2 Intranet Tenor Implementation

Company X (New York)

Figure 1-3 Extranet Tenor Implementation

Company X (New York)

Figure 1-4 Internet Tenor Implementation

State-of-the-Art Configuration and Network Management

Dynamic Call Routing

Multiple Lines/Signaling Supported

Easy Connect to Console

H.323 Gatekeeper Call Control Management

Powerful System Monitoring

Call Detail Recording

Interactive Voice Response (IVR)

Figure 1-5 PBX Call Routing

Figure 1-6 PSTN Call Routing

Data Network Calls

Figure 1-7 Data Network Call Routing

(for Hop-off calls

Other Call Routing Options

Conventional VoIP Transmission Sends Many Redundant Packet Headers

Tenor using PacketSaver to Minimize Bandwidth Usage

Figure 1-8 Tenor with NATAccess Deployment

Virtual Tie Line

Hop-off PBX Call

Flexible Networking Capabilities

What is CAMWizard and Tenor CAM?