Quintum Technologies Tenor AS User Manual
®
V
ay
Tenor AS
oIP MultiPath/Gatew
Switch
d
u
c
P
r
o
4
P
/
N
t
0
8
-
0
0
u
G
0
0
-
1
5
9
0
-
i
d
e
Tenor and Quintum are registered trademarks. PacketSaver, Quintum Technologies, Inc., Risk Free VoP,
VoIP Made Easy, T ASQ, SelectNet, and SelectNet Technology are trademarks of Quintum Technologies,
Inc.
Table of Contents
About this Guide
What’s included? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Product Guide Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Finding Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Chapter 1: Overview
What is the Tenor AS?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Unique Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
State-of-the-Art GUI Configuration and Network Management . . . . . . . . . . . . . . . . . . 1-4
Easy Connect to Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Powerful System Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
SelectNet™ Technology Safety Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
PacketSaver™ reduces bandwidth consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Virtual Tie Trunk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
SNMP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Call Detail Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
IVR/RADIUS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
NATAccess™. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Dynamic Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Tenor AS Call Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Tenor MultiPath Switch (ASM200 and ASM400) Configuration. . . . . . . . . . . . . . . . . . 1-8
Tenor VoIP Gateway (ASG200 and ASG400) Configuration. . . . . . . . . . . . . . . . . . . . 1-10
Advanced Features/Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Call Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Dial Plan Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
H.323 Gatekeeper Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
SIP User Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Chapter 2: Hardware Components
Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Front Panel Connections and Reset Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Back Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
P/N 480-0059-00-10 TOC-1
RJ-11 Cables (for ASM200, ASG200) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
RJ-11 Splitter Cable (for ASM400 and ASG400). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
RJ-45 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
DB-9 Serial RS-232 Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Voice/Fax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
PSTN/PBX Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
LAN Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Physical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Chapter 3: Installation/Basic Troubl eshooting
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Pre-Installation Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Inspect Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Connect to Phone/FXS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Connect to Line/FXO Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Connect to Ethernet LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Connect to PC Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Install Supplemental Ground Safety Cable (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Power up the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Assign IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Change IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Getting Started with Configuration/Making the First Call. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Load Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Common Symptoms/Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Chapter 4: Advanced Topic: View Call Detail Records
What is a CDR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Establish connection between Teno r AS and CDR Server . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Configure Tenor AS for connection to CDR Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Setup CDR Server and assign password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Change CDR Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Tenor AS Establishes Connection with CDR Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
CDR Server Establishes Connection with Tenor AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
CDR Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Sample Record for Standard and Extended CDR Format 0, 1, 100, 101 . . . . . . . . . . 4-6
Sample Record for Extended Tenor AS CDR Format 3, 4, 103, 104: . . . . . . . . . . . . . 4-10
Chapter 5: Advanced Topic: Diagnostics/Maintenance
Monitor LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
P/N 480-0059-00-10 TOC-2
Monitor Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
How to Read Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Valid Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Display all Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Display Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Display Alarm History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Verify Unit Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Maintenance Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Restore Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Reset System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Change Unit Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
If you need Additional Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Chapter 6: Advanced Topic: SNMP/IVR
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
How does Tenor AS utilize SNMP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Install SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Download and install SNMP-Related Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Configure Network Manager IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Working with SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
View traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
View Alarm Status via Tenor AS icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Launching Command Line Interface (CLI) from HP Openview . . . . . . . . . . . . . . . . . . 6-8
Set up Tenor AS status polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Set up Debug Message Display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
IVR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
IVR Call Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
ANI Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Multi-session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Typical IVR Network Connection/Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Configure IVR - Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Basic IVR Data (via Trunk Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Configure IVR Voice Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Voice Prompt Requirements (English Requirements) . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Create Voice Prompt Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
IVR Call Flow - Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Pre-paid Calling Card - Call Flow (with default language) . . . . . . . . . . . . . . . . . . . . . . 6-21
P/N 480-0059-00-10 TOC-3
Post-paid Calling Card - Call Flow (with default language) . . . . . . . . . . . . . . . . . . . . . 6-23
Pre-paid and Post-paid Calling Card - Call Flow (with multiple language support) . . . 6-25
Pre-paid and Post-paid Calling Card - Call Flow (with Multi-Session Call support). . . 6-26
ANI Authentication Application Type 1 - Call Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
ANI Authentication Application Type 2 - Call Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
Call Flow - Message Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32
Start Accounting Request Message Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32
Stop Accounting Request Message Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33
Authentication Request Message Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35
Authentication Response Message Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35
Authorization Request Message Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36
Authorization Response Message Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37
GLOSSARY
INDEX
Warranty/Approvals
Quintum Limited Warranty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Documentation Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Agency Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
FCC WARNINGS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Canadian Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
P/N 480-0059-00-10 TOC-4
About this Guide
P/N 480-0059-00-10 Preface-1
About this Guide
What’s included?
This product guide is divided into chapters; each chapter describes a specific topic. The following
chapters ar e included:
• About this Guide: Describes what is included in the Product Guide, including typographical
conventions.
• Chapter 1: Overview. In cludes a gen eral overv iew of th e product, in cludin g a descript ion of the
Tenor AS’s features and capabilities.
• Chapter 2: Hardware Components. Hardware description, including the front and rear panels,
as well as LEDs and required cables.
• Chapter 3: Installation/Basic Troubleshooting. Describes how to install the Tenor AS unit,
including how to connect, power up and assign the IP address.
• Chapter 4: Advanced Topic: View Call Detail Records. Describes the Call Detail Recording
(CDR) feature, including how to set up the CDR server and assign a password. In addition,
instructions for reading CDR output are also included.
• Chapter 5: Advanced Topic: Diagnostic/Maintenance: Describes how to troubleshoot and
monitor the health of the s ystem.
• Chapter 6: Advanced T opic: SNMP/IVR: This chapter d escribes the SNMP pro tocol an d how to
use it with the Tenor AS. In addition, it describes the Interactive Voice Response (IVR) system
for support of pre-paid and post-paid calls.
•Glossary
• Index
• Warranty
Preface-2 P/N 480-0059-00-10
Typographical Conventions
Product Guide Conventions
Certain typographical conventions are used throughout this product guide. See below.
• All commands you enter via keystrokes appear in bold (e.g., Press Enter or Press Ctrl-I).
• All text commands you enter via Telnet session or command line typing appear in italics (e.g.,
type active).
• There are three types of special text that are designed to reveal supplemental information:
Note, Warning, and Caution. See below.
A NOTE provides additional, helpful information. This information may tell you how to do a
certain task or jus t be a remi nder for how-to’s given in previous sections. (i .e., For a l ist of va lid
commands at any time, type ?)
A WARNING provides information about how to avoi d harming your VoIP equipment or other
equipment (i.e., Do not stack more than 4 units together.)
About this Guide
A CAUTION provides informat ion about how to avoid injury t o yourself or to others (e .g., Do
not install the equipment during a lightning storm).
P/N 480-0059-00-10 Preface-3
About this Guide
Finding Help
Refer to the Product Guide for help. The Table of Contents and Index tells you where to find information easily.
Extensive configuration help is available from the Tenor Configuration Manager/Tenor Monitor
User Guide or the Command Line Interfac e User Guide . Both documen ts are on the CDR ROM you
received with unit or you can download the latest documentation from www.quintum.com
Preface-4 P/N 480-0059-00-10
Chapter 1: Overview
This chapter gives you a general overview of the Tenor AS including feature descriptions and capabilities. Specifically, the following topics are covered:
! A description of Tenor AS
! Features
! Capabilities
! Call Paths
! H.323 Gatekeeper Services
! Advanced Features
P/N 480-0059-00-00 1-1
Chapter 1: Overview
What is the T enor AS?
The Tenor AS is a VoIP (Voice over Internet Prot ocol) H.32 3/SIP swit ch that digiti zes voice , fax, and
modem data and transmits it over t he IP net wor k. De si gned as a SOHO produc t, the Tenor AS gives
small to medium sized businesses with analog voice infrastructure an easy, cost-effective way to
capitalize on the power of Voice over IP (VoIP).
The Tenor AS integrates a gate way, gatekeeper, bo rder element inte ll igent call rout ing, a nd supp orts
H.32/SIP and QoS all in on e so lut ion. The gateway converts c ir cui t swit ch ed calls to VoIP calls, the
gatekeeper performs IP call routing functions, and the border element distributes the call routing
directories throug hout th e networ k. Through t he FXS port , you can c onnect a tele phone, key syst em
or PBX; through the FXO port, you can connect to the PSTN (through direct connection to the Central Office).
Figure 1-1
Tenor AS VoIP Switch
The Tenor AS is available in two configuration types:
• ASG VoIP Gateway. The ASG VoIP Gateway is mainly intended for applica tions interfa cing
between the PBX and the VoIP network. The number of VoIP channels equals the number of
FXS ports. Calls can be routed in any direction between any of the ports.
• ASM Multipath Switch. The AXM MultiPath Switch is mainly intended for symmetrical multipath applicatio ns, with an equa l n umber of FXO and FXS ports .The number of VoIP channels
is equal to half the number of telephony (i.e. PSTN) channels.
With its MultiPath architecture, the Tenor AS can intelligently route calls between the FXS,
FXO, and the VoIP network to achieve the best combination of cost and quality. The Tenor AS
also routes calls over IP to reduce costs, and then transparently “hops off” to the PSTN, to
reach off-net locations. Calls can be routed in any direction between any of the ports.
Table 1-1 Tenor AS Configuration Types
Series Configuration FXS Ports FXO Ports VoIP Ports
ASM200 2 2 2
ASM MultiPath
ASG VoIP Gateways
1-2 P/N 480-0059-00-00
ASM400 4 4 4
ASG200 2 0 2
ASG400 4 0 4
Chapter 1: Overview
Whichever configuration you choose, the high performance unit provides one Autosensing BaseT
connection, along with one RS-232 serial console port connection. The unit also incorporates an
intelligent call routing engine which regulates system resources and configuration while coordinating all voice traffic activity in the unit.
The unit’s simple plug-and-play embedded system architecture brings VoIP technology to your network without changing your existing t el epho ny inf ra st ruc ture. Your network stays as is, an d t he call
type is transparent to the user. This technology boasts superior voice quality without compromising
reliability.
P/N 480-0059-00-10 1-3
Chapter 1: Overview
Features
The Tenor AS’s specific features are explained below.
Unique Design
Tenor AS packs powerful VoIP features into one compact unit. The Tenor can be installed without
upgrades to the existing voice or data network. You can install the unit in a home or office environment, without affecting the network infrastructure you already have in place. As with all Tenor
architecture, the Tenor AS provides the power of VoIP in an easy-to-use product that takes just minutes to get up and running.
State- of-the-Art GUI Configuration and Network Management
The Tenor AS is managed/monitored by the Tenor Configuration Manager and Tenor Monitor.
Through the Tenor Configuration Manager, you can configure all options, such as dial plans, call
routing numbers, etc. An easy-to-use Java-based installation process enables you to an install the
manager and start configuring within minutes. Through the Tenor Monitor, you can monitor the
health of the system, including alarms, call detail records, etc. Both the Tenor Configuration Man-
ager and Tenor Monitor provide comprehensive on-line help systems that are available at your fin-
gertips.
In addition, you can configure the unit via Command Line Interface (CLI). Through this telnet session, you can access all configuration options, including an online help system, built into the CLI,
which provides help for all featur es and functions. Just type help at any prompt, and data about that
field will be displayed.
Easy Connect to Console
Plugging a serial cable between the unit’s RS-232 port and your PC’s console port, will allow local
unit management. Through the cons ole c onnect ion, yo u are able to as sign a n IP addr ess. I n addi tion ,
through the RS-232 port, you are able to configure the unit via Command Line Interface (CLI).
Powerful System Monitoring
There are many different ways to monitor the health of the unit, including LEDs and alarms. LEDs
appear on the front of the unit.The LEDs light up according to operations and alarms the system is
experiencing.
For more advanced monitoring , see Chapter 5: Advanced Topic: Diagnosti cs/Mainte nance to view a
list of active al arms, as well as view an alarm hi stor y. Each alarm indicates the uni t’s operational status.
1-4 P/N 480-0059-00-00
Capabilities
SelectNet™ Technology Safety Net
Chapter 1: Overview
Quality of service is vi rtually guaranteed. Tenor AS ’s built-in patented SelectNet
™ T ec hnol ogy
provides a “safety ne t,” which virtually guar ant ee s that each call going VoIP will not only be routed
successfully, but will deliver high voice quality.
SelectNet monitors the IP network performance for VoIP calls. If the performance characteristics
become unacceptable—acc ording to the delay, jitter, and pa cket los s spe cificat ions you co nfi gure—
the Tenor AS will switch the call to the PSTN automatically and transparently. The Tenor continuously monitors your data network for jitter, latency and packet loss, and transparently switches customer calls to the PSTN when required.
PacketSaver™ reduces bandwidth consumption
PacketSaver packet multiplexing technology reduces the amount of IP bandwidth required to support multiple calls flowing between two endpoints. PacketSaver minimizes bandwidth usage by
aggregating packet samples from multiple VoIP conversations and packing them into a larger IP
packet with a single I P header. The process removes the need t o send a bulky I P header with i ndivid ual voice packets. As a result, it eliminates the transmission of redundant information.
Figure 1-2 PacketSaver
Conventional VoIP Tran smi ssi o n Sends Man y R ed und an t Pack e t Heade r s
Tenor AS
Tenor
Tenor using PacketSaver to Minimize Ban dwidth Usage
Tenor AS
Tenor
Virtual Tie Trunk
The Tenor unit can emu la te any t ie tr unk. It provides all of t he functionality of a ti e t run k, including
the considerable cost savings, but eliminates the need for a PBX trunk to be configured, or marked
as a tie trunk. (A traditional tie trunk is a PBX-configured direct connection between two PBXs in
separate locations . The t ie tr unk bypa sses t he PSTN net work, whi ch res ults in cons id erabl e savi ngs.)
Your PBX does not need any additional configuration. The Tenor AS treats all trunks the same without compromising voice quality.
P/N 480-0059-00-10 1-5
Chapter 1: Overview
SNMP Support
The Tenor AS supports Simple Network Management Protocol (SNMP), the standard protocol used
to exchange network information between different types of networks. The Tenor AS unit acts as an
SNMP agent—using HP®
Openview™—to receive commands and issue responses to the Network
Manager. The Network Manager will then be able to perform certain functions, such as receiving
traps from the Tenor AS.
Call Detail Recording
Through the Call Detail Record (CDR) feature, the Tenor AS generates a call record at the comple-
tion of each call, typically for accounting purposes. A CDR is a string of data that contains call
information such as call date and time, call duration, calling party, and called party. Tenor AS may
store Call Detail Records locally or they can be sent to a CDR server within the network. The CDR
contains sufficient information to capture billing data, which can be used to create billing reports
using third party billing software.
IVR/RADIUS Support
Interactive Voice Response (IVR) is a feature of the Tenor AS that enables you to of fer se rvices, 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, including ANI Authentication (Types 1 and 2). The
RADIUS is a standard protocol which provides a series of standardized message formats for transmitting and rec eivin g dia led i nformat ion, acc ount d ata a nd aut horiz ation codes betwe en the network
access gateway and the billing server.
NATAccess™
NATAccess is an intelligent network address translation technology. It enables VoIP networks with
multiple H.323 endpoints to operate behind firewalls equipped with H.323 Network Address Translation (NAT); this provides maximum network security. NATAccess simplifies deployment by elim-
inating the need to place the Tenor on a public IP network. Using NATAccess provides easy, secure
expansion between muli tpl e VoIP sites. In addition, NAT technology in t he Tenor permits the use of
private subnets at the same time; in -house calls will never go over the public internet.
Figure 1-3 Tenor with NATAccess Deployment
Router
“Public” LAN
“DMZ” LAN
“DMZ” Port
“Private” port
Firwall NAT
“Private” LAN
1-6 P/N 480-0059-00-00
Chapter 1: Overview
Dynamic Call Routing
Tenor AS’s intell igent c all rou ting capa biliti es are state-o f-the-a rt. Th e unit a utomati cally detects and
supports three call types: voice, fax, and modem.
Tenor AS will first identify the call origination site—Line/FXO, Phone/FXS, or IP routing group —
and then route the call according to the parameters you have configured in the routing database.
Each call may be routed via circuit switched path between any two circuit groups, or compressed
and transported via VoIP when connecting to an IP routing group. Trunk circuits are those that typically connect to another circuit switched network such as the PSTN. Line circuits typically connect
to a termination device on the user premises, such as a PBX.
P/N 480-0059-00-10 1-7
Chapter 1: Overview
Tenor AS Call Paths
Tenor MultiPath Switch (ASM200 and ASM400) Configuration
The T eno r Mult iPath Switch Configur ation is symmetri cal with an equ al nu mber of Phone/ FXS and
Line/FXO ports. Calls are routed from the Phone/FXS, Line/FXO, or IP Network. Calls can be
routed in any direction between any of the ports.
FXS (Phone) Originated Calls. Calls coming from the Phone/FXS interface (i.e. PBX) may be
switched to either the d ata network a s a VoIP call or to the FXO interface , typical ly for c onnection to
another circuit switched network such as the PSTN. The routing decision made by the Tenor is
based upon your configuration and the dialed number. See Figure 1-4 for an example of a call originated from a PBX.
Figure 1-4 FXS (Phone) Originated Calls
PBX
Keyswitch
Phone
FXS Port
FXO Port
PSTN
OR
IP Network
FXO (Line) Originated Calls. A call coming from a Line/FXO inter face m ay be swit ched to ei ther
the data network as a VoIP call, a Line Circuit, or trunk typically for connection to a termination
device on the user’s premises such as a PBX. The routing decision made by the Tenor AS is based
upon your configuration and the dialed number. See Figure 1-5 for an example of a call originated
from the PSTN.
Figure 1-5 FXO (Line) Originated Calls
PBX
Keyswitch
Phone
FXS Port
OR
FXO Port
PSTN
IP Network
1-8 P/N 480-0059-00-00
Chapter 1: Overview
IP Network Calls. Calls coming from the IP network ( data n etwork) can b e rout ed to th e Line/F XO
or Phone/FXS interfaces. The Tenor will route calls based upon the dialed number. If the number is
configured as a loc al phone number, the call will be sent to a Phone/FXS cir cuit for te rminat ion, otherwise the call is considered a “Hop-Off call” and the Tenor sends it out through a Line/FXO interface, typically co nnected t o the PSTN. See Figure 1- 6 for an example of a call originated from th e IP
network.
Figure 1-6 IP Network Originated Calls
PBX
Keyswitch
Phone
PSTN
FXS Port
OR
IP Network
FXO Port
P/N 480-0059-00-10 1-9
Chapter 1: Overview
Tenor VoIP Gateway (ASG200 and ASG400) Configuration
The Tenor VoIP Gateway Configuration is used for Phone/FXS port connecting to the VoIP Network. The number of VoIP ports is equal to the number of FXS ports. Calls can be routed in any
direction between any of the ports. See Figure 1-7 for an example of a call origination from the
PBX.
FXS (Phone) Originated Calls. Calls coming from the Phone/FXS interface (i.e. PBX) may be
switched to the data network as a VoIP call. The routing decision made by the Tenor is based upon
your configuration and the dialed number. See Figure 1-7 for an example of a call originated from a
PBX.
Figure 1-7 FXS (Phone) Originated Calls
PBX
Keyswitch
Phone
FXS Port
IP Network
1-10 P/N 480-0059-00-00
Chapter 1: Overview
Advanced Features/Capabilities
Call Management
There are four types of routing databases you can configure: Bypass Directory Numbers (BPN),
Hunt Local Directory Numbers ( Hunt LDN), Ho p-Of f Dir ectory Numbe rs (HDN) a nd S tati c Route s.
Bypass Directory Numbers. Bypass Directory Numbers (BDN) are telephone numbers that are
automatically routed directly from a line circuit to the PSTN; they will not be routed VoIP. Some
examples of bypass numbers include toll-free calls, emergency calls (i.e., 911), or high security
calls.
Hunt Local Directory Numbers. A Hunt Local Directory Number ((Hunt LDN) is a phone number
reachable through local Line Circuits.
Hop-Off Directory Number. A Hop-off PBX call travels over IP, and then “hops” off into the public network (PSTN) on t he destination side t o r ed uce or eliminate public t o l l cha rges (also known as
Leaky Area Map). A Hop -Off Directory Number i s routed over the IP to another Tenor location and
then out to the Trunk circuit, possibly to the PSTN as a local call.
Static Routes. Static Routes are used between networks and other H.323 devices that are not registered to the network through the Border Element (such as non-Quintum gateways). A static route
associates endpoints (as represented by their IP address) with Directory Number patterns.
Dial Plan Options
Public/Private Dial Plan Support.The Tenor AS supports public and private dial plans. A public
dial plan includes numbers which conform to the international dialing plan (E.164) of a country
code + city/area code + local number. For a public dial plan, you can define the numbering plan
structure for the Tenor AS to use for outgoing calls.
A private dial plan does not conform to a public dialing plan (i.e., 3 digit dialing plan); through the
Tenor AS you are able to configure the unique pattern/dialing plan structure, including number
length.
You are able to configure which dia l plan to use for incoming and outgoing call s, including whether
other options such as hop-off calls, will use a public or private dial plan.
User Programmable Dial Plan Support. The User Programmable Dial Plan Support (UPDP)
enables the Tenor to identify a completely customizable set of digit sequences, such as Local,
National, International or Private Numbers.
PassThrough support for certain call types. Certain call types can be directly routed to a trunk
circuit, without going IP. There are several routing tables you can configure via the Tenor Configu-
ration Manager to adj us t ho w the Tenor AS unit route s t hes e t ypes of “pass through” nu mb ers . For
example, you may want to conf i gure 911 as a “bypass number”, which means that al l 911 calls coming into Tenor AS from the line circuit will be routed directly to a Trunk circuit presumably con-
nected to a PSTN. Bypass calls are never routed over IP.
P/N 480-0059-00-10 1-11
Chapter 1: Overview
Hop-off PBX Calls. Hop-off numbers are phone number patterns for calls to be routed out to the
PSTN. (A hop-off PBX call is a toll call which hops through a private network to reduce or eliminate the toll charge.) They are entered in a Hop-off Number Directory and associated with trunks
where matching calls should be sent.
Tenor AS supports those hop-off PBX calls where the destination Tenor AS is programmed to route
the call to the PSTN. The destination Tenor AS unit is configured with the phone numbers to be
“supported” for this feature.
H.323 Gatekeeper Services
The Tenor AS unit’s built-in H.323 gatekeeper performs IP call routing functions, such as call con-
trol and administrative services to another Tenor AS unit, or another H.323 endpoint. The gate-
keeper’s functionality complies with the H.323 industry specifications for voice control and
management.
Gatekeeper. A Gatekeeper in an H.323 network pro vides call control servi ce s and other services to
H.323 endpoints (i.e., gateways, terminals, and MCUs). The Tenor AS has a built-in H.323 gate-
keeper which complies to the H.323 industry specifications for voice control and management. The
gatekeeper performs call routing functions for calls entering and exiting a site.
The Gatekeeper pe rf orm s IP call routing f unc ti ons , such as Call Contro l Signaling and Call Authorization for Gateways, IP phones, and H.323 terminals. The Gatekeeper communicates with other
Gatekeepers through a Border Element. When using a group of Tenor AS units, you can assign one
unit as the Gatekeeper for the network. We recommend you configure each as its own gatekeeper.
Tenor AS supports gatekeeper to gatekeeper communication using the standard LRQ (Location
Request)/LCF (Location Confirm) messaging scheme.
Zone Management. A zone is a gr oup of H.323 defined endpoints controlled by a Gatekeeper. Endpoints can be gateways (i.e., Tenor AS), terminals, and/or multipoint conferencing units (MCUs).
Endpoints establ ish contr ol channe ls with a gatekeep er for r egistra tion, admi ssion, and secur ity. Call
routing information about the endpoint is sent to the gatekeeper, including: IP address, unit type
(gateway, terminal, or MCU) and routing information (such as phone numbers, number patterns,
etc.).
A collection of zones is an administrative domain. An administrative domain provides call routing
services for its zones through gatekeeper to gatekeeper messages or gatekeeper to border element
messages (see below for more information).
Call Registration. When registration from an H.323 endpoint 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 the routing information. The gatekeeper confirms the dialed number and supplies the endpoint with the destination IP address. For example, a Tenor AS’s gatekeeper will act as
the gatekeeper for that zone and all of the other endpoints will register with it.
Border Element. The Tenor AS’s gatekeeper uses a border element to gain access to the routing
database of the administrative domain for the purpose of call completion or any other services that
involve communication s with other endpoin ts ou t of the administr ative domain. The bo rder el ement
functionality is built into the Tenor AS unit, along with the gateway and gatekeeper.
P/N 480-0059-00-10 1-12
Chapter 1: Overview
The primary function of the border element is to collect, manage, and distribute call routing information. A gatekeeper wil l e st abl is h a s er v ic e r el at ion shi p with a border element; th e ga tekeeper provides its zones capabilities and the border element shares call routing capabilities of other zones in
the administrative domain. Through the border element, gatekeepers from multiple zones will be
able to communicate.
A border element also establishes relationships with oth er border elements to route betwee n administrative domains. If a gatekeeper cannot resolve an address, it contacts the border element.
In addition, if you are us ing mo re than one Tenor unit, you can configure one of the bor der el ements
for that zone. The Tenor AS unit can use two border elements: primary and secondary. These work
together as one en ti ty to provide redund ancy and fault tolerance; there ar e no hierarchal differences.
Gatekeeper
Zone
Gatekeeper
Zone
Gatekeeper
Zone
Administrative Domain
Border Element
Border Element
Administrative Domain
Gatekeeper
Zone
Gatekeeper
Zone
Gatekeeper
Zone
Call Services. Gatekeepers provide services suc h a s a ddr essing, authorization and authenticati on of
terminals and gateways, bandwidth management, accounting, billing, and charging. Gatekeepers
also provide call-routing services. Specifically, the Tenor AS Gatekeeper provides the functions
which follow:
Address Translation. The gatekeeper translates telephone numbers into IP addresses and vice
versa. It performs Alias Addr ess (pho ne number) to T r ansport Address ( IP addres s) transl ation when
an endpoint requests service. The Gatekeeper uses a translation table to translate an Alias Address
(an address such as an H.323 identifier that a user may not understand) to a transport address. The
translation table is updated using Registration messages.
Autodiscovery. The gatekeeper is discovered i n one of t he foll owing ways: An endpoi nt sends a n IP
broadcast called a Gatekeeper Request message (GRQ) message (which includes that correct gatekeeper name) to disco ver a Gatekee per OR the endpo int will disc over a gate keeper by it s IP addres s.
Routing. The gatekeeper identifies the IP address of endpoints in its administrative domain. The
gatekeeper builds a routing database from information obtained from the border element and also
from gateways and H.323 endpoints.
Admissions Control. All H.323 endpoints must register and request permission to enter the gatekeeper’s zone; t he gatekeep er will conf irm or deny acc ess to the ne twork. The gatekeeper authorizes
P/N 480-0059-00-10 1-13
Chapter 1: Overview
network access and protects the integrity of the network using Admission Request (ARQ), Admission Confirmation (ACF) and Admission Reject (ARJ) messages.
SIP User Agent
SIP (Session Initiat ion Protocol) is a sign al ing prot oc ol used to establish a se ss ion on an IP network
for voice control and management; it is a request-response protocol that closely resembles Hypertext Transfer Protocol (HTTP), which forms the basis of the World Wide Web. SIP re-uses many of
the constructs and concepts of Internet protocols such as HTTP and Simple Mail Transfer Protocol
(SMTP). The purpose of SIP is only to establish/change/terminate sessions. SIP is not concerned
with the content or details of the session.
SIP is Transport layer-independent, which means it can be used with any transport protocol: UDP,
TCP, ATM, etc. It is text-based, so it requires no encoding/decoding like H.323. And SIP supports
user mobility, using proxies and redirecting requests to your current location.
When configured for SIP the Te nor will act as a SIP User Agent (Endpoint) as defined in IETF
RFC3261. Multiple user ag ent s a ll ow f or separate agents t o be al lo cat ed to each SIP call. I t wil l b e
able to gateway calls to and from the IP network, and Customer Premise Equipment (CPE) such as
phones, PBX's, and FAX machines, or the Pu bli c Swit che d Telephone Network (PSTN). The Tenor
SIP User Agent will work in conjunction with an external SIP proxy or redirect server to route and
connect calls over SIP based networks.
There are three basic components of SIP:
1. User Agent (Endpoint)
• client element, initiate s calls
• server element, answers calls
2. Network Server (Proxy Server or Redirect Server)
• name resolution
• user location
• redirect an d forking
3. Registrar
• Stores registration information in a location service using a non-SIP protocol.
P/N 480-0059-00-10 1-14
Chapter 2: Hardware Components
This chapter tells you what is contained in your hardware package. A description of each component
is also included.
Specifically, the following topics are covered:
! Hardware Description
! Cables
! Specification
P/N 480-0059-00-10 2-1
Chapter 2: Hardware Components
Hardware Description
The Tenor AS is a stackable device which provides Phone/FXS and Line/FXO connections as well
as connections to the Ethernet LAN and a PC.
The unit’s front panel includes LEDs; the back panel includes connection jacks, a diagnostics
option, reset button, and an on/off power switch.
Front Panel Connections and Reset Options
Figure 2-1 Tenor AS Front Panel
Power LED
Status LED
LAN LEDs
Analog Port LEDs
The LEDs display the health of the system. There are differe nt types of LEDs: Power, Status, LAN
and Analog Ports. A description of each is described in Table 2-1.
Table 2-1 Front Panel LEDs Definitions
LED Label LED Color Description
Power Power Green On: Indicates power is on.
Off: Power is off.
Status Status Green Flashing Operational Statu s.
Off: Tenor AS is working properly.
On: One or more diagnostic
tests have failed.
Line LED - Green On indicates activity is occur-
ring on the Line/FXO port.
Analog Ports 1, 2 3, and 4
Phone LED - Green On indicates activity is occur-
ring on the Phone/FXS port.
2-2 P/N 480-0059-00-10
Chapter 2: Hardware Components
LED Label LED Color Description
Link Green On: Link is working properly
and there is ac tivity on t he li ne.
Off: Link has failed.
LAN
100Mb Green On : The advertised link rate is
100Mb if the link is not connected, or the actual link rate is
100b if the link is connected.
Off: The advertised link rate is
10Mb if the link is not connected, or the actual link rate is
10Mb if the link is connected.
Activity Green Flashing On: indicates there is activity
(i.e., transmit/receive) on the
line.
Off: No activity is occurring.
P/N 480-0059-00-10 2-3
Chapter 2: Hardware Components
Back Panel
Ground
Screw
Power Switch
Power
Receptacle
Phone/FXS port
Line/FXO port
LAN port
Console
port
Diag
Reset
• Ground Screw. An earth ground screw is provided to connect to supplemental earth ground
using a Ground Safety Cable, if supplemental ground is needed.
• Phone/FXS port. Provides an RJ-11 jack for connection to a PBX, Keyphone or phone.
Figure 2-2 RJ-11 Phone/FXS Port Pin Order
Port 1
4 3 2 1
Pair 1
Pair 3
Port 2
4 3 2 1
Pair 2
Pair 4
Table 2-2 Input/Output RJ-11 Phone/FXS port
Pin # Used with Definition
1 Port 1, pin 4 Tip
Port 1
2-4 P/N 480-0059-00-10
2 Port 1, pin 3 Ring
3 Port 1, pin 2 Tip
4 Port 1, pin 1 Ring
Chapter 2: Hardware Components
Pin # Used with Definition
1 Port 2, pin 4 Tip
Port 2
2 Port 2, pin 3 Ring
3 Port 2, pin 2 Tip
4 Port 2, pin 1 Ring
• Line/FXO port. Provides an RJ-11 jack for connection to the Central Office to provide direct
connection to the PSTN.
Figure 2-3 RJ-11 Phone/FXO Port Pin Order
Port 1
4 3 2 1
Pair 1
Pair 3
Port 2
4 3 2 1
Pair 2
Pair 4
Table 2-3 Input/Output RJ-11 Phone/FXS port
Pin # Used with Definition
1 Port 1, pin 4 Tip
Port 1
Port 2
2 Port 1, pin 3 Ring
3 Port 1, pin 2 Tip
4 Port 1, pin 1 Ring
1 Port 2, pin 4 Tip
2 Port 2, pin 3 Ring
3 Port 2, pin 2 Tip
4 Port 2, pin 1 Ring
• LAN port. 10/100 Base-T Ethernet port. This port provides an RJ-45 jack for an individual
connection to a 10/100 Ethernet LAN switch or hub via RJ-45 cable; it is individually configured with a unique IP and MAC address.
P/N 480-0059-00-10 2-5
Chapter 2: Hardware Components
Figure 2-4 10/100 BASE-T Ethernet Port Pin Order
Table 2-4 Input/Output 10/100 Ethernet port
Pin # Signal Definitio n Color
1 TX + Transm it Data White w/orange
2 TX - Transmit Data Orange
3 RX + Receive Data White w/green
4 RSVD Reserved Blue
5 RSVD Reserved White w/blue
6 RX - Receive Data Green
7 RSVD Reserved White w/Brown
8 RSVD Reserved Brown
• Console port. This RS-232 connector is used for connection to a PC’s serial port via DB-9
serial cable at 38400 BPS 8N1, without flow control. The input/output signals are listed in
Table 2-5.
Figure 2-5 DB-9 Female Connector Pin Order
5 4 3 2 1
9 8 7 6
Table 2-5 Serial RS232 DB-9 Connector Pinouts
Pin # Function Description
1 DTR Data Terminal Ready
2 TXD Transmit Data
3 RXD Receive Data
4 CD Carrier Detect
5 GND Signal Ground
6 N.C. No Connect
2-6 P/N 480-0059-00-10
Chapter 2: Hardware Components
Pin # Function Description
7 N.C. No Connect
8 N.C. No Connect
9 N.C. No Connect
• Diag. Enables you to perform software diagnostic procedures.
• Reset. Enables you to reset the system. See
Chapter 5: Advanced Topic: Diagnostics/Maintenance
for more information.
• Power Switch. Switch to turn power on and off.
• Power Socket. Connection port to external power supply block.
P/N 480-0059-00-10 2-7
Loading...