Analog User Guide

Product GuideP/N 480-0003-00-13

Tenor VoIP MultiPath Switch

A400/A800

Tenor MultiPath Gateway, PacketSaver, Quintum, Quintum Technologies, Inc., VoIP Made Easy, Select Net Technology, are trademarks of Quintum Technologies, Inc.

Table of Contents

About this Guide What’s included? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Product Guide Conventions . . . . . . . . . . . . . . . . . . . . . . . . . .1-3Finding Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Chapter 1: Overview What is Tenor VoIP MultiPath Switch? . . . . . . . . . . . . . . . . . . . . .1-2Typical Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Intranet Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Extranet Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

Internet Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .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

Call Control Management . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

Powerful System Monitoring . . . . . . . . . . . . . . . . . . . . . . . . .1-10

Call Detail Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10

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

P/N 480-0003-00-13 TOC-1

PPPoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11

Other Call Routing Options . . . . . . . . . . . . . . . . . . . . . . . . . .1-14

PacketSaver™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15

NATAccess™. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15

Virtual Tie Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16

Hop-off PBX Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16

SNMP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16

Flexible Networking Capabilities . . . . . . . . . . . . . . . . . . . . . .1-17Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18

Chapter 2: Hardware ComponentsHardware 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-2Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Pre-Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Inspect Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Position the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Connect the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10Power up the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15Assign IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16Software Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19

TOC-2 P/N 480-0003-00-13

Types of Upgrade Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19

Software Naming Convention: . . . . . . . . . . . . . . . . . . . . . . . .3-20

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

Other Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21Load Upgrade software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22

Load the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22

Chapter 4: Getting Started: Command Line Interface (CLI) What is the Command Line Interface? . . . . . . . . . . . . . . . . . . . . .4-2

Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

User Login IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2Access CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3

Telnet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3Configuration via CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4

Chapter 5: Working with SNMPWhat is SNMP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2

How does Tenor utilize SNMP? . . . . . . . . . . . . . . . . . . . . . . .5-2Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4

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

Configure network manager IP address . . . . . . . . . . . . . . . .5-7Working with SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10

View traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-10

View Alarm Status via Tenor icon . . . . . . . . . . . . . . . . . . . . .5-10

Set up Tenor status polling . . . . . . . . . . . . . . . . . . . . . . . . . .5-11

Set up Debug Message Display window . . . . . . . . . . . . . . . .5-11

P/N 480-0003-00-13 TOC-3

Chapter 6: System Alarms What is an Alarm Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

How to Read Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

Valid Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5View Alarms via Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

Establish Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9

Display Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10

Display Alarm History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11

Filter Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12

Delete Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

Exit Alarm Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

Chapter 7: Call Detail Recording Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2Establish connection between Tenor and CDR Server . . . . . . . . .7-3

Tenor Establishes Connection with CDR Server . . . . . . . . . .7-4

CDR Server Establishes Connection with Tenor . . . . . . . . . .7-5CDR Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6

Chapter 8: Using IVR What is IVR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2

IVR Call Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3

ANI Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4

Multi-session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4Typical IVR Network Connection/Process . . . . . . . . . . . . . . . . . . .8-6Configure IVR - Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-9

Basic IVR Data (via Trunk Group) . . . . . . . . . . . . . . . . . . . . .8-9

IVR Prompt Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-9

TOC-4 P/N 480-0003-00-13

RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-10Configure Voice Prompts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11

Voice Prompt Requirements (English Requirements) . . . . . .8-12

Create Voice Prompt Files . . . . . . . . . . . . . . . . . . . . . . . . . . .8-17

Update IVR Voice Prompts . . . . . . . . . . . . . . . . . . . . . . . . . .8-18Configure IVR via CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-19View RADIUS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-20

Display RADIUS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . .8-20

Clear RADIUS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-21Call Flow - Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-22

Pre-paid Calling Card - Call Flow (with default language) . . .8-22

Post-paid Calling Card - Call Flow (with default language) . .8-24

Pre-paid and Post-paid Calling Card - Call Flow (with multiple language support) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-26

Pre-paid and Post-paid Calling Card - Call Flow (with Multi-Session Call support) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-28

ANI Authentication Application Type 1 - Call Flow. . . . . . . . .8-30

ANI Authentication Application Type 2 - Call Flow. . . . . . . . .8-32Call Flow - Message Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . .8-34

Start Accounting Request Message Attributes . . . . . . . . . . .8-34

Stop Accounting Request Message Attributes. . . . . . . . . . . .8-36

Authentication Request Message Attributes . . . . . . . . . . . . .8-39

Authentication Response Message Attributes . . . . . . . . . . . .8-40

Authorization Request Message Attributes . . . . . . . . . . . . . .8-41

Authorization Response Message Attributes . . . . . . . . . . . . .8-43

Chapter 9: Troubleshooting/Maintenance Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2Monitor LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2View Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

P/N 480-0003-00-13 TOC-5

Verify Unit Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3Perform a Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4Common Symptoms/Problems . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5Restore Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-8Reset System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9

Reset via Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9Set the Unit to Online mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10View System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-11If you need Additional Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-11

Appendix A: Cables

Appendix B: Specifications/Approvals

Appendix C: VoIP Terms/Advanced Topics

GLOSSARY

INDEX

Warranty

TOC-6 P/N 480-0003-00-13

About this Guide

P/N 480-0003-00-13 Preface-1

About this Guide

What’s included?

This product guide is divided into chapters; each chapter describes a specific topic. The following chapters are included:

• About this Guide: Describes what is included in the product guide, including typographical conventions.

• Chapter 1: Overview: Includes a general overview of the product, including a description of how our products fit into the VoIP network.

• Chapter 2: Hardware Components: Hardware description.

• Chapter 3: Installation. Describes how to install the Tenor unit, including how to set the IP address.

• Chapter 4: Getting Started: Command Line Interface. This chapter describes how to connect to the CLI.

• Chapter 5: Working with SNMP. This chapter describes the SNMP protocol and how to use it with the Tenor unit.

• Chapter 6: System Alarms. Describes how to use the Alarm Manager and tells you how to view alarms via telnet session.

• Chapter 7: Call Detail Recording. Describes the CDR feature, including how to display and read CDRs.

• Chapter 8: Using IVR. Describes the IVR feature, including a quick start and how to configure voice prompts.

• Chapter 9: Troubleshooting/Maintenance. Describes how to troubleshoot and monitor the health of the system.

• Appendix A: Cables. Cable pinout information.

• Appendix B: Specifications/Approvals: List of Tenor’s specifications and approvals.

• Appendix C: Getting Acqainted with VoIP. A general overview of VoIP and how it relates to the Tenor unit.

• Glossary

• Index

Preface-2 P/N 480-0003-00-13

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-to’s given in previ-ous sections. (i.e., For a list of valid commands at any time, type ?)

A WARNING provides information about how to avoid harm to your VoIP equipment or other equipment. (i.e., Do not stack more than 4 units together.)

A CAUTION provides information about how to avoid injury to yourself or to others. (e.g., Do not install the equipment during a lightning storm.)

P/N 480-0003-00-13 Preface-3

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: VoIP Terms/Advanced Topics for detailed information about VoIP terms and con-cepts.

Preface-4 P/N 480-0003-00-13

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 informa-tion 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-13 1-1

Chapter 1: Overview

What is Tenor VoIP MultiPath Switch?

The Tenor VoIP MultiPath Switch A400/A800 is a VoIP (Voice over Internet Proto-col) H.323/SIP standard analog gateway that transmits voice and fax data over the IP network. It can connect to the PBX, telephone, key system and PSTN via analog lines (the A400 provides four analog lines; the A800 provides eight analog lines). It connects to the IP via 10/100 Mbps ethernet connection.

Tenor Analog is the first VoIP analog gateway that intelligently switches calls over both the IP network and the PSTN in order to ensure high voice quality and call reliability. It functions as a gateway and a gatekeeper. The gateway converts circuit switched calls to VoIP calls; the gatekeeper performs IP call routing functions.

Figure 1-1 Tenor Analog MultiPath Switch

Quality of service is virtually guaranteed. The SelectNet™ Technology provides a “safety net,” which monitors the network packet delay for an IP call. If the delay becomes unacceptable—according to the specifications you assign— the call will be switched to the PSTN automatically. The unit’s simple plug and play embedded system architecture brings VoIP technology to your network without changing your existing PBX and telephone desk set. Your network configuration stays as is. The call type is transparent to the user. This technology boasts practically free voice without compromising quality and reliability.

Tenor Analog MultiPath VoIP Gateway A400/A800

1-2 P/N 480-0003-00-13

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 communi-cation with a source outside of your company. Internet communication is commu-nication running over the public IP network. Each implementation type is defined in the sections which follow.

P/N 480-0003-00-13 1-3

Chapter 1: Overview

Intranet Implementation

The Tenor unit enables Intranet communication by transmitting data within a cor-porate data network. The Gateway functionality enables data to be sent out through a corporate LAN to reach other Gateways at separate sites. Packetized voice data is sent between intra-corporate sites without passing through the PSTN. The Gate-keeper functionality enables the two units within the same company to communi-cate.

For an illustration of intra-corporate communication, see Figure 1-2.

Figure 1-2 Intranet Tenor Implementation

DataNetwork

Router

TCP/

IP

PSTNAnalog

Ethe

rnet

PBX

Analog

Company X (California)

Company X (New York)

Company X (Tokyo)

Company X (France)

LAN 1

LAN 4

LAN 2

LAN 3

1-4 P/N 480-0003-00-13

Chapter 1: Overview

Extranet Implementation

Another application example is the Tenor unit’s ability to connect calls between two different companies (e.g., suppliers, distributors, etc.) A unit is placed at each corporate site, transmitting corporate data between companies.

Figure 1-3 Extranet Tenor Implementation

DataNetwork

Router

TCP/

IP

PSTNAnalog

Ethe

rnet

PBX

Analog

DataNetwork

Router

TCP/

IPPSTN

AnalogEt

hern

et

PBX

Analog

Company X (New York)

Company X (California)

DataNetwork Company Y (France)

P/N 480-0003-00-13 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

DataNetwork

Router

TCP/

IP

PSTNAnalog

Ethe

rnet

PBX

Analog

Your Company

Internet

1-6 P/N 480-0003-00-13

Chapter 1: Overview

Features

The Tenor’s specific features are explained below.

Unique Design

The Tenor unit packs powerful VoIP features into one compact unit. The system’s embedded design enables you to configure the unit directly without depending upon another operating system; it is all delivered in one 19” rack mountable unit.

State-of-the-Art Configuration and Network Management

Just plug and go. Through the Command Line Interface (CLI) you are able to set specific configuration options that will help you further maximize Tenor’s capabil-ities.

P/N 480-0003-00-13 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 unacceptable—according to the delay jitter and packet loss specification you configure—Tenor will transparently switch the call to the PSTN automatically, without callers even knowing. This feature virtually guarantees that each call going VoIP will be not only routed successfully, but will deliver high quality sound.

Uninterrupted Service

If power is lost to the Tenor for any reason, or the unit is down, all call routing operations will bypass the unit. This means that the Tenor unit will be ignored and all calls will “bypass” the unit and route successfully to reach the PSTN or PBX.

Dynamic Call Routing

The Tenor unit’s call routing capabilities are state-of-the-art. Voice and fax calls are transmitted through the 10/100 Ethernet LAN and routed out to the corporate WAN. Tenor will first identify the call origination site —PBX, PSTN or Data Net-work—and then route it according to the parameters or defaults you configure in the routing database.

Multiple Lines/Signaling Supported

The Tenor unit can support up to eight analog lines, which means you can support up to eight simultaneous VoIP calls, depending upon your needs.

The PBX ports implement the FXS interface (a telephone, key system or PBX can be connected directly to these ports); the PSTN ports implement the FXO interface (for direct connection to the Central Office).

In addition, the Tenor unit supports Loop Start and Ground Start signaling for incoming and outgoing calls.

1-8 P/N 480-0003-00-13

Chapter 1: Overview

Easy Connect to Console

Plugging a DB-9 cable into the unit’s asynchronous RS-232 port will connect the unit and get you up and running. Through this port, you are able to configure an IP address for your unit.

Call Control Management

Through the Tenor Analog, you have a choice through the Command Line Inter-face (CLI) of choosing either H.323 or SIP as the call control protocol. See below for a description of each.

H.323 Gatekeeper Call Control Management. The unit’s H.323 gatekeeper per-forms IP call routing functions which comply to the H.323 industry specifications for voice control and management. The Tenor’s Gatekeeper performs call routing functions for calls entering and exiting a site.

H.323 endpoints in the same zone register with the Tenor’s gatekeeper. When reg-istration is complete and a call is originated, the call request is sent to the gate-keeper. The call request provides the gatekeeper with the dialed number and requests bandwidth, authentication, and routing information. The gatekeeper con-firms the dialed number, authenticates the call, verifies the bandwidth is available, and supplies the endpoint with the destination IP address.

Tenor supports the use of two Gatekeepers, a primary and secondary. If communi-cation with the primary Gatekeeper is lost, the Tenor will register with the second gatekeeper.

The primary function of the border element is to collect, manage, and distribute call routing information. The Border Element functionality is built into each Tenor.

SIP Call Control Management. SIP (Session Initiation Protocol) is a signaling protocol used to establish a session on an IP network for voice control and manage-ment; 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 Sim-ple 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.

P/N 480-0003-00-13 1-9

Chapter 1: Overview

SIP is Transport layer-independent, which means it can be used with any transport protocol: UDP, TCP, ATM, etc. It is text-based, so it requires no encoding/decoding like H.323. And SIP supports user mobility, using proxies and redirecting requests to your current location.

Powerful System Monitoring

There are many different ways to monitor the health of the unit, including LEDs and alarms.

LEDs are on the front of the unit to indicate the status of the corresponding port. LEDs light up according to a function the port is experiencing. For example, if one PBX port is active, the LED will light as green.

Internal alarms indicate there is a problem with the unit. Through the Command Line Interface (CLI), you can view active system alarms. Each alarm tells you spe-cifically what problem the unit is encountering.

Call Detail Recording

Through the Call Detail Recording (CDR) feature, the Tenor unit is able to gener-ate a CDR at the completion of each call. A CDR is a string of data which contains call information such as call date and time, call length, calling party and called party. From this information you can capture billing type data, which can be used to create billing reports.

Interactive Voice Response (IVR)

Interactive Voice Response (IVR) enables you to offer services, such as Pre-paid calling cards and Post-paid accounts to your customers. The Tenor uses the RADIUS (Remote Authentication Dial-In User Service), for authenticating and authorizing user access to the VoIP network. The RADIUS is a standard protocol which provides a series of standardized messages formats for transmitting and receiving dialed information, account data and authorization codes between the network access gateway and the billing server.

1-10 P/N 480-0003-00-13

Chapter 1: Overview

PPPoE

The Tenor supports PPPoE (Point-to-Point Protocol over Ethernet), which is a pro-tocol used for encapsulating PPP frames into Ethernet frames; it creates the con-cept of a “session” over the Ethernet and provides residential and small business DSL (Digital Subscriber Link) broadband internet access.

A PPPoE session consists of two peers communicating over the Ethernet through a progression of messages such as Initiation, Discovery (Offer/Request/Session) and Termination. Using PPPoE enables dynamic IP addresses, along with a unique ses-sion ID for the connection.

Capabilities

The Tenor’s specific capabilities are explained below.

PBX Calls

Calls coming from a PBX are routed to either the data network or the PSTN. The decision is made by Tenor based on the information you configure. For example, you can configure certain calls to always go to the PSTN. Any calls not configured to go to the PSTN will attempt to find a destination on the IP network. If a call can-not be completed by a unit’s gatekeeper, the call will be routed to the PSTN.

Tenor is transparent to the PBX and PSTN switch. There is no need to configure or change your PBX, desk set or local PSTN switch.

P/N 480-0003-00-13 1-11

Chapter 1: Overview

Figure 1-5 PBX Call Routing

EthernetLAN

PSTNORPBX

1-12 P/N 480-0003-00-13

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

Data Network Calls

Calls coming from the data network can be routed to the PBX (for intra-corporate calls) or the PSTN (for Hop-off PBX calls supported). Tenor will route the call based on the dialed phone number. If the number is configured as a local phone number, the call will be sent to the PBX, otherwise the call is considered a “Hop-off PBX call” and the Tenor unit sends it out through the PSTN.

Figure 1-7 Data Network Call Routing

PBX

PSTNCall

PSTNCall

VoIP Call

OR

PBX(for intra-corporate) (for Hop-off calls

supported)

P/N 480-0003-00-13 1-13

Chapter 1: Overview

Other Call Routing Options

There are several routing tables you can configure through the Command Line Interface (CLI) to adjust how Tenor routes specific calls. For example, you may want to configure 911 as a “bypass number,” which means that all 911 calls coming into a Tenor unit will be routed directly to the PSTN.

There are three types of routing databases you can configure: Bypass Phone Num-bers (BPN), Local Directory 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.

1-14 P/N 480-0003-00-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 mini-mizes bandwidth usage by aggregating samples from multiple VoIP conversations and packing them into a larger IP packet with a single IP header. The process removes the need to send a bulky IP header with individual voice samples. As a result, it eliminates the transmission of redundant information.

Larger packetization helps reduce the bandwidth required for each VoIP call. This reduction in bandwidth lessens demand on routers, which decreases the possibility of dropped packets. It also reduces the possibility of packet loss that occurs with packet-based calls in congested networks.

.

NATAccess™

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 secu-rity. 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.

Tenor using PacketSaver to Minimize Bandwidth Usage

Conventional VoIP Transmission Sends Many Redundant Packet Headers

Tenor Tenor

P/N 480-0003-00-13 1-15

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 PBX-configured direct connection between two PBXs in separate locations. The tie trunk bypasses the PSTN network, which results in considerable savings.)

Your PBX does not need any additional configuration. The Tenor unit treats all trunks the same without compromising voice quality.

Hop-off PBX Call

Tenor supports those Hop-off PBX calls where the destination Tenor unit is pro-grammed to route the call to the PSTN. (A Hop-off PBX call is a toll call which hops through a private network to reduce or eliminate the toll charge.) The destina-tion Tenor unit is configured with the phone numbers to be “supported” out of that “zone”.

SNMP Support

The Tenor unit supports Simple Network Management Protocol (SNMP), the stan-dard protocol used to exchange network information between different types of networks. The Tenor unit acts as an SNMP agent to receive commands and issue responses to the network manager. The network manager will then be able to per-form certain functions, such as generate and send traps.

P/N 480-0003-00-13 1-16

Chapter 1: Overview

Flexible Networking Capabilities

Now, migrating to a global VoIP network is easy. The product’s flexible design and scalability makes it not only sensible, but essential to run your voice over IP.

The H.323 gatekeeper functionality adds to the product’s flexibility by pooling gateways within the same company to create a VoIP network and expand global networking capabilities. In addition, Tenor’s functionality makes it possible to con-nect to any PBX, anywhere. It’s universal, easy-to-connect and the unique design lends itself to network expansion.

P/N 480-0003-00-13 1-17

Chapter 1: Overview

Interoperability

The Tenor Analog A400 and A800 units interoperate with the following:

• Cisco VoIP gateways using FastStart or non-FastStart protocols

• Cisco Gatekeeper

• Microsoft Net Meeting (voice only)

• Tenor Analog VoIP MultiPath Switch Release P2-1-9 and higher

• A200, A2-1-6 and higher (voice only)

P/N 480-0003-00-13 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-13 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 unit’s front panel includes connection jacks, LEDs, and two reset/diag buttons; the back panel includes a power cord connection socket, an on/off switch, and a label. See Figure 2-1 and Figure 2-4.

The Tenor A400 unit is illustrated and defined below (the Tenor A800 looks identi-cal except there are eight PBX and eight PSTN lines available.)

Front Panel Connection and Reset Options

Figure 2-1 Tenor Analog Front Panel

• PBX Port: Four RJ-45 jacks (for connection to a PBX). For A400, each port provides one line. (For the A800 unit, each port provides two lines.)

• PSTN Port: Four RJ-45 jacks (for connection to a PSTN). For A400, each port provides one line. (For the A800 unit, each port provides two lines.)

• Reset: Enables you to reset the system.

RJ-45 jack for PSTN connect RJ-45 port

for Ethernet connect

Reset option

Diag Option

RJ-45 jack for for PBX connect RS-232 port

for PC connect

2-2 P/N 480-0003-00-13


• Diag: Enables you to perform software diagnostic procedures.

• 10/100 LAN Port: One RJ-45 jack for connection to a 10/100 Ethernet LAN switch or hub via RJ-45 cable.

• Console Port: One RS-232 jack for connection to a PC’s serial port via DB-9 cable.

Front Panel PBX/PSTN Port Assignment

Each PBX and PSTN port is assigned a port number. For A400, each port is assigned one line number, for A800, each port is assigned two line numbers. For example, for an A800 unit, the first PBX port to the left is assigned two line num-bers of 1 and 5. See below.

For port pinout information for each RJ-45, see Appendix A.

Figure 2-2 PSTN/PBX Port Assignment

Port Assignment

P/N 480-0003-00-13 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

System LEDsEthernet LEDs

PSTN/PBX LEDs

2-4 P/N 480-0003-00-13


1(E

Table 2-1 Front Panel LEDs

LED Color Description

0/100thernet)

COL Yellow Ethernet Collision Status.Flashing: Some collisions are taking place on the Ethernet LAN.Off: No collisions are taking place on the Ethernet LAN.

10 Green 10 Mbps Ethernet Indication.On: The Tenor unit detects the 10 Mbps Ethernet link integrity signal indicating normal condition.Off: The Tenor unit did not detect the 10 Mbps Ethernet link integrity signal.

100 Green 100 Mbps Ethernet location.On: The Tenor unit detects the 100 Mbps Ethernet link integrity signal, indicating normal condition.Off: The Tenor unit did not detect the 100 Mbps Ethernet link integrity sig-nal.

RX Green Ethernet Receive Status.Flashing: Data is received from Ether-net LAN. Off: Data is not being received from Ethernet LAN.

TX Green Ethernet Transmit Status.Flashing: Data is being transmitted to Ethernet LAN. Off: Data is not being transmitted to Ethernet LAN.

P/N 480-0003-00-13 2-5


S

P

P

ystem

Power Green Power Indicator. On: Power is being supplied and the internal power convertor is working. Off: Power is off.

Alert Yellow Operational Status.Off: The Tenor unit is working prop-erly. On: One or more diagnostic tests have failed or system is stills starting up.

BX

Busy (for lines 1-4; LED is located in lower left corner of RJ-45 port)

Green Operational Status. Off: Line is not active.On: Line is off hook or active.

Busy (for lines 5-8; LED is located in lower right corner of RJ-45 port)

Yellow Operational Status.Off: Line is not active.On: Line is off hook or active.

STN

Busy (for lines 1-4; LED is located in lower left corner of RJ-45 port)

Green Operational Status.Off: Line is not active.On: Line is off hook or active.

Busy (for lines 5-8; LED is located in lower right corner of RJ-45 port)

Yellow Operational StatusOff: Line is not active.On: Line is off hook or active.

LED Color Description

2-6 P/N 480-0003-00-13


Back Panel

Figure 2-4 Tenor Unit Back Panel

• Power Cord. Cord to plug into an AC outlet for power.

• Power Switch. Switch to turn power on and off.

• Label. A label that displays UL, model, and power information.

Cables

The cables listed in Table 2-2 are included with your system and are required to connect the Tenor unit to various interfaces.

Table 2-2 Cables Supported

Cable Usage

RJ-45 to RJ-45 Patch Cable Analog connection(s) to PBX.

RJ-45 to RJ-45 Patch Cable Analog connection(s) to PSTN.

RJ-45 to RJ-45 Patch Cable Connection to Ethernet LAN 10/100.

DB-9 Male to DB-9 Female Cable Connection to PC’s asynchronous console port.

Detachable AC Power Supply Cord Connection to AC power jack.

Power SwitchPower Cord Jack Label

P/N 480-0003-00-13 2-7

Chapter 3: Installation

The Tenor unit will be installed initially by a trained Quintum field engineer. This chapter gives you installation instructions, as well as how to position the unit suc-cessfully within your network.


Pre-Installation guidelines

Position the unit

Connect to PBX, PSTN, 10/100 Ethernet and PC

P/N 480-0003-00-13 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 maxi-mize your network configuration options.

Figure 3-1 Typical Office Network Configuration

Since the Tenor unit functions as a gateway/gatekeeper and is invisible to the net-work, 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 Configuration Manager; no network changes are required.

PBX

Typical Office Setup

Router

(PSTN)(CSU may be internal)

Analog

NetworkData BRI

Ethernet Hub/Switch

3-2 P/N 480-0003-00-13


Installation

Before you begin the actual installation, review the pre-installation guidelines which follow, inspect the package contents, and position the unit.

Pre-Installation Guidelines• Only trained service technicians should remove the unit cover. Inside parts

have hazardous voltages.

• Do not connect equipment in wet conditions or during a lightning storm.

Inspect Package Contents

Before you install the hardware, confirm that following components are included in your shipment.

• Tenor Analog VoIP Gateway A400 or Tenor Analog VoIP Gateway A800

• 1 AC Power Cable

• 4 RJ-45 Cable (for PSTN connection)

• 4 RJ-45 Cable (for PBX connection)

• 1 RJ-45 Cable (for Ethernet connection)

• 1 DB-9 Cable

• 2 wall mounting brackets

• 4 screws

• CD ROM

If a listed component is not included in your package, contact your customer ser-vice representative.

Position the Unit

Locate the Tenor unit within the same area as your PBX, Ethernet hub and/or PSTN patch panel. The unit can be installed on a flat surface (i.e., tabletop), mounted within a rack, or mounted directly to the wall. Each installation type is

P/N 480-0003-00-13 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 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-13


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 (86ºF). Internal rack temperature should be considered for safe operation.

• Do not restrict airflow vents when installing the unit in the rack.

• Mechanical loading of rack should be considered so that the rack remains sta-ble and unlikely to tip over.

• Consider the overall loading of the branch circuit before installing any equip-ment in a rack 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 unit’s mounting brackets with the rack’s mounting holes and install screws with star washers. See vendor specific instructions for rack installation.

5. Ensure the unit is placed firmly in the rack.

P/N 480-0003-00-13 3-5


Figure 3-2 Rack Installation

Tenor

mounting

Shown: 2 Tenor Analog units installed

Screws

Rack edge

Front View Top View

holes

rack

Washers

in rack.

3-6 P/N 480-0003-00-13


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-13 3-7


Figure 3-3 Wall Mounting Dimensions

2. Position and attach one mounting bracket to the unit using two of the screws included with the package. See Figure 3-4.

3. Position and attach the other mounting bracket to the unit using the remaining two screws included with the package. Figure 3-4.

NOTE: Wall anchors and wall mounting screws are not included with the sys-tem; we recommend you use them to add support to the mounting of the unit. See steps 4 and 5.

4. (Optional) Hammer the wall anchors into the wall 19 1/8 (48.6 cm) apart according to the dimensions shown in Figure 3-3.

5. (Optional) Using a Phillips head screwdriver insert the screws into the wall anchors according to the dimensions shown in Figure 3-3.

6. Align the unit over the anchor screws and slide the unit gently onto the screws and wall anchors. The mounting slots should engage the screws. See Figure 3-4.

7 3/4” (19.9 cm)3/16”

3-8 P/N 480-0003-00-13


Figure 3-4 Wall Mount Installation

7. Ensure the unit is firmly mounted against the wall.

7 3/4”

Wall

MountingSlots

Exploded View

Screws/Wall Anchors

Note: Ensure unit is level.

P/N 480-0003-00-13 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 pur-poses only.

Connect to PBX/Key System. There are many different PBX devices; instruc-tions which follow explain the general procedure for connecting an RJ-45 cable (included in your package) between a Tenor’s PBX port and a PBX. You must use your specific PBX documentation, along with any other PBX materials, for spe-cific information for how to connect the analog cable to your PBX.

Figure 3-5 Connect to PBX

Connect to PBX as follows:

1. Insert one end of the RJ-45 cable into the Tenor unit’s port labeled PBX.

PBX

RJ-45Cables

or Key System

3-10 P/N 480-0003-00-13


2. Insert the other end of the RJ-45 cable into the appropriate analog port on the PBX or Key System. See your PBX documentation port requirements for con-nection specifics.

Connect to Phone or Fax. You are able to connect up to four telephones or fax machines to the Tenor unit. (For supplementary services, such as voice mail, call forwarding and call waiting, you will need to connect to a PBX rather than directly to a telephone).

Figure 3-6 Connect to Phone or Fax Machine

Connect to a phone as follows:

1. Insert one end of the RJ-45 cable into the jack on the back or underside of the phone or fax machine.

2. Insert the other end of the RJ-45 cable into one of the Tenor unit’s ports labeled PBX.

3. Repeat for each phone or fax machine you would like to connect.

RJ-45Cables

P/N 480-0003-00-13 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

1. Insert one end of the RJ-45 cable into one of the unit’s ports labeled PSTN.

2. Connect the other end of the RJ-45 cable to the patch panel.

NOTE: Connecting to the patch panel may require trained personnel.

3. Repeat for each analog line you want to connect between the Tenor unit and the PSTN.

PSTN

Patch Panel

RJ-45

3-12 P/N 480-0003-00-13


Connect to Ethernet Hub/Switch. You can use these instructions for general connection only. The Ethernet hub/switch documentation should provide specific instructions for connection to another device, such as the Tenor unit.

Figure 3-8 Connect to Ethernet Hub/Switch

1. Insert one end of the RJ-45 cable into the unit’s port labeled 10/100.

2. Insert the other end of the RJ-45 connector into the appropriate Ethernet port. See your Ethernet documentation port requirements for connection specifics.

DataNetwork

Ethernet Hub/Switch

RJ-45Cable

P/N 480-0003-00-13 3-13


Connect to PC Console. You will need to connect the Tenor unit to your work-station’s serial port via RS-232 connection. (This connection will be used when you initially assign an IP address to the unit.) For the instructions below, it is assumed you are connecting to a PC.

Figure 3-9 Connect to PC Com Port

1. Insert one end of the DB-9 cable into the Tenor unit’s port labeled Console.

2. Insert the other end of the DB-9 cable into your workstation’s Com Port (see your PC documentation for more information about this port.)

DB-9

3-14 P/N 480-0003-00-13


Power up the System

Once you have all cables connected properly, you are ready to turn the system on as follows:

1. Plug in the power cord to an AC outlet.

2. Locate the on/off switch on the back of the unit and click the switch to On.

The unit will power up and the LEDs will flash and turn off; the power LED will remain lit. For information about the LEDs, see Chapter 2: Hardware Compo-nents.

Once the unit is powered up and the Alert LED goes out, you are ready to assign an IP address. See the following section Assign IP Address.

P/N 480-0003-00-13 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 connec-tion and terminal emulation software. The instructions below assume you are run-ning 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. The Connection Description window will be displayed.

2. Enter a connection description (i.e., name for each unit such as Tenor Analog A400).

3. Click Ok.

4. Choose the connection port (on your PC) from the Connect Using drop down list box (i.e., Direct to Com 1). Click Ok. The Com1 Properties window will be displayed. See Figure 3-10.

3-16 P/N 480-0003-00-13


Figure 3-10 Port Settings Window

5. From the Bits Per Second drop down list box, choose 38400.

6. From the Data Bits drop down list box, choose 8.

7. From the Parity drop down list box, choose None.

8. From the Stop bits drop down list box, choose 1.

9. From the Flow control drop down list box, choose None.

10. Click Ok. A connection to the Tenor Analog unit will be established.

11. Press the Tenor Analog unit’s power switch to On. Information about the unit will scroll on the screen.

12. To change any of this information, including re-setting the IP address, press Enter within 3 seconds.

13. Type M (to modify) (to cancel, type C).

14. For Do you want a LAN interface?, the default entry is Yes.

P/N 480-0003-00-13 3-17


15. For This Board’s LAN IP Address, enter the IP address you want to assign to the Tenor Analog unit.

16. For Subnet Mask for LAN prompt, enter the subnet mask. This address is used to differentiate the network portion of the IP address from the host portion of the IP address.

17. For Default Gateway and IP Address prompts, choose whether there should be a default gateway (router) which routes packet data outside of your LAN, and enter its IP address.

18. For Baud Rate, change this number if necessary.

19. Enter a time (in seconds) for the CPU delay before starting up (default is 3).

Upon initial configuration, the factory defaults will already be included in the system; there is no need to reset them.

3-18 P/N 480-0003-00-13


Software Upgrade Overview

During the course of a product’s life cycle, it may be necessary for Quintum to issue software maintenance releases to resolve any bugs that may not have been detected during our systems test phase. Also, new features and functionality will require new software.

Types of Upgrade Software

Within the Quintum Tenor, there are three files:

boot.bin.The boot.bin file is the Tenor’s base operating system. The Tenor requires this software just to be able to power up normally. This software is not updated often from Quintum.

sys.bin. The sys.bin file is the Tenor’s system software. This software gives the Tenor all of its features and functionality. It provides all of the routing algorithms, etc. This software is updated as needed to provide bug fixes and feature enhance-ments.

db.bin. The db.bin is where your configuration for the Tenor is stored. This soft-ware is not upgraded directly, but will be upgraded, if needed, by the sys.bin file automatically. You may archive this file for a backup and later restore it back to the unit if necessary. You may also take this file from one Tenor and load it in to other Tenors of the same model type when you are creating a network of Tenors where the configuration is mostly the same except for some minor details.

P/N 480-0003-00-13 3-19


og s-or

m an r. l r -e

Software Naming Convention:

When Quintum sends a customer new software, the file name will reflect the type of software it is. The convention that Quintum currently uses is as follows:

Parameter Name Possible Values Description

A Model Type

ta – Tenor Analog ver-siontd – Tenor Digital ver-sion

Each software is provided for either the Analor Digital Tenor. When you want to load a sytem, you must make sure that the software is fthat product type (analog or digital).

B Soft-ware Type

sy – sys.bin softwarebt – boot.bin software

As mentioned above, the two files that Quintucan provide for upgrades are the boot.bin andthe sys.bin. When the software is sent, you cidentify which software it is by this parameteAlso, when you load the Tenor, the Tenor wilonly accept a file name of boot.bin, sys.bin odb.bin, so you must rename the file to the correct type when you load the software. See thprocedures for more information.

C Soft-ware Version

Variable, based on soft-ware version

This will reflect the software version.

A

3-20 P/N 480-0003-00-13


-

on

on

Release Notes

When a new version of software is released, software release notes will be gener-ated to indicate the new features and/or bug fixes. Additionally, the release notes will tell you which files are to be upgraded (sys.bin, boot.bin, or both).

Other Software

In addition to the above software, there is also a feat.bin file. The feat.bin file is the file that provides different features to the Tenor. If you upgrade from one model type to another, Quintum may send you this file for the system. The feat.bin file is coded to a specific Tenor serial number based on the serial number you provide us. If the feat.bin file is loaded in to a system that does not have the serial number coded in this file, the Tenor will loose all of its features and stop processing calls. The correct feat.bin will need to be reloaded to this system.

D Echo Cancel-lation Type

lec – Long Echo Cancel-lation.null – Short Echo Cancel-lation.

The long echo cancellation or lec software isused to provide up to 128ms of echo cancellation. Quintum recommends that all Tenors except the D3000 be loaded with the lec versisoftware. If the file does not have lec in this position, then it is has shorter echo cancellatiand should only be loaded on the D3000.

P/N 480-0003-00-13 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 Quin-tum emails the software to you, we should provide the file size as shown from DOS. To check this, open a DOS window on your PC where the file is stored and go to the directory where that file is. At the DOS prompt type dir <enter>. You will now see a list of all files in that directory and what there file size is. If the file size does not match what Quintum said it should be, then the file may be corrupted. Contact the Quintum Technical Assistance Center (QTAC) to have them resend the file.

4. Make sure that there are no calls active on the Tenor. If possible, place the Tenor in bypass mode.

5. Make sure that you can communicate with the Tenor from your PC over IP. You can only upgrade the Tenor over IP and not from the serial interface.

Load the Software

Follow the steps below to load the new software to your Tenor. You may choose to load both the boot.bin and the sys.bin files before the final step. This procedure is 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 direc-tory 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-13 3-22


3. At the DOS prompt type ftp ipaddress <enter>. Where the ipaddress is, enter the IP address for the Tenor.

4. At the User prompt hit <enter>. The Tenor has no user name.

5. At the Password prompt, type in the Tenor’s password you assigned. If you have not set a password on the Tenor, then just hit <enter>.

6. At the ftp> prompt type bin <enter>. This will tell FTP that the file to be transferred is a binary file.

7. At the ftp> prompt type hash <enter>. This will tell FTP to provide a hash (#) mark as a status indicator.

8. At the ftp> prompt type put origfile destfile. Where origfile is enter the name of the file as it is shown in DOS when you saved the file. For example; ta-sy-p2-4-5qt-lec.bin or td-sy-p2-4-5qt-lec.bin. Where destfile is, enter the file name that the Tenor needs to see. For example; sys.bin. So a full example might be; put ta-sy-p2-4-5qt-lec.bin sys.bin.

9. When you hit <enter> the file will first be transferred to the Tenor. This will be evident by the hash (#) marks appearing across the screen.

10. When the hash (#) stop appearing, the file has been transferred and the Tenor is now erasing the old software and loading the new one. This step can take as short as 20 seconds or as long as 1-2 minutes. This is a critical step. If the Tenor looses power or resets during this period, it may not come back up.

11. When the above is completed, you should get a message of “Transfer Com-plete”. If you do not get this message, or if the message reads “connection closed by remote host”, then the load is not completed yet. Wait about 2 min-utes and then try to FTP into the Tenor again. If it allows you in, the load is complete and you can continue to step 12.

12. When you get the message Transfer Complete, the load is completed. If you have another file, like the boot.bin file to load, you can repeat step 8 to load this file now. Exit FTP by typing bye <enter>.

13.The Tenor must know be reset for the new software to be active.

P/N 480-0003-00-13 3-23


P/N 480-0003-00-13 3-24

Chapter 4: Getting Started: Command Line Inter-face (CLI)

This chapter tells you how to use access and use the CLI. Specifically, the follow-ing topics are included:

CLI Description

Access CLI

Configuration via CLI

P/N 480-0003-00-13 4-1

Chapter 4: Getting Started: Command Line Interface (CLI)

What is the Command Line Interface?

The Command Line Interface (CLI) is a Telnet-based (also accessible via serial port) list of menu options which enable you to configure and monitor any Tenor unit; you can configure features and capabilities such as numbering plans, channel usage, border element, signaling type, and routing information. In addition, you are also able to monitor system alarms and run diagnostic procedures. CLI attributes enable you to further configure CLI options; these provide additional configuration items according to the option type.

Through the CLI, there are also commands you execute to simplify the process of configuring and monitoring the Tenor unit. Some of these commands are globally used, others are specific to the mode in which you are working.

Options

Some configuration menu options can have multiple instances. As a result, those option types require an identifier to uniquely define a specific option type. Other options are part of the default system, such as dial plan. You can configure the dial plan and the corresponding attributes, but you cannot create a second dial plan. Default menu options cannot be deleted.

User Login IDs

There are two types of user logins: user and admin. The admin level enables you to view and change information. The user level enables you to view the information but not configure via CLI.

4-2 P/N 480-0003-00-13


Access CLI

You can access the CLI through a telnet session, a terminal-like access to any Tenor unit. If your PC is directly connected to the Tenor unit, you can configure the unit directly through the serial port using HyperTerminal.

NOTE: Alternatively, you may want to use other telnet clients, such as the Linux telnet client or free programs like Putty. If you choose to do so, you may have to make minor setting changes in the Telnet client in order to make it function correctly.

Telnet Connection

Once the Tenor has been initially configured with an IP address network and is connected, the easiest way to connect to the Tenor and use the CLI is through a standard Telnet session from any PC on your IP network. Connect to a Tenor unit via Telnet as follows:

For Windows 95/Windows 98:

1. Click on Start> Run. The Run dialog box will be displayed.

2. Type telnet and click on Ok.

3. Click on Connect> Remote System.

4. In the Host Name field type, enter the IP address assigned to your Tenor.

5. Click on Connect.

A connection to the Tenor unit will be established.

For Windows 2000 and later:

1. Click on Start> Run.

2. The Open dialog box will be displayed. Type telnet and click on Ok. (Or type telnet followed by the IP address and you will connect.)

P/N 480-0003-00-13 4-3


3. At the telnet prompt, type open (followed by the IP address for the unit to which you want to connect.)

A connection to the Tenor unit will be established.

Configuration via CLI

Once you are connected to the Command Line Interface (CLI), you can configure the system, as well as perform diagnostics and monitor system information. For specific information, see the Online Help you received with the CD.

4-4 P/N 480-0003-00-13

Chapter 5: Working with SNMP

This chapter tells you how to use and manage Tenor’s Simple Network Manage-ment Protocol (SNMP) feature, which is managed via Hewlett® Packard’s HP Openview Network Node Manager. Specifically, this chapter tells you how HP OpenView auto-discovers a Tenor unit, as well as how to generate SNMP traps for existing alarm messages.

Implement SNMP via HPOV

Generate and view traps

P/N 480-0003-00-13 5-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 man-ager polls the SNMP agents (such as routers, hubs or network servers) for certain requested information. The agent will then gather information about the machine it is running on and carries requests from the network manager to read and change the information.

How does Tenor utilize SNMP?

The Tenor unit supports the SNMP protocol; specifically, Hewlett® Packard’s HP Openview software acts as the SNMP network manager for the Tenor unit. Once you set up HP Openview to view and “auto-discover” Tenor as a network device using SNMP, HP Openview will be able to issue commands, get responses, and perform certain functions. For example, you can configure the SNMP agent in Tenor to generate and send traps for existing Tenor alarms to HP Openview.

A Tenor unit can report alarms to up to three network managers.

5-2 P/N 480-0003-00-13


Installation Requirements

You will need to install and run HP Openview NMS 6.0 in order to recognize the Tenor as an SNMP agent. Below are basic hardware and software requirements you will need to install HP Openview. See your HP Openview documentation for detailed information and installation instructions.

Minimum hardware requirements

• Intel Pentium 120 Mhz processor-based computer

• CD Drive

• 96 MB RAM

• 250 MB free disk space on one drive

• 80 MB free page filing space

Software requirements

• Microsoft Windows NT operating system (version 4.0), with TCP/IP version 4.0

• Microsoft SNMP Agent (SNMP Services)

• Microsoft Peer Web Services or Internet Information Server (IIS) version 4.0

• Netscape Navigator web browser (version 4.06 or higher) or Microsoft Inter-net Explorer web browser (version 4.0 or higher) with Java/JavaScript options enabled.

P/N 480-0003-00-13 5-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 as an SNMP agent, you must first download and install files from the www.quintum.com web site as follows:

1. Start up HP Openview. (For specific information, see the user documentation you received with the software.) There are two ways to download the applica-ble files: from the www.quintum.com web site or from the CD delivered with the system. To download from the web, go to step 2. Otherwise, for CD instal-lation, go to step 5.

2. From the web site, access a web browser (i.e., Microsoft Internet Explorer, Netscape) and go to the web site www.quintum.com and access Customer Ser-vice/ Training. If you are not registered, a registration form will be displayed. Once registered, you will be able to download the appropriate file. See Step 3.

3. Download the SNMP_MIB.zip file to your PC.

4. Unzip the SNMP_MIB.zip file to the HP Openview root directory (this is the directory in which HP Openview was installed).

5-4 P/N 480-0003-00-13


The following files will be listed:

5. From the Quintum CD ROM, click on TenorTools. Download the SNMP Agent Software to the HP Openview root directory (this is the directory in which HP Openview was installed).

6. From the HP Openview root directory run installquintum.bat. Installation will begin. The following section lists where the installation files are copied and which files were modified. You can use this information to make changes man-ually to files, if desired.

7. From the HP Openview root directory run installquintum.bat. Installation will begin. The following section lists where the installation files are copied and which files were modified. You can use this information to manually make changes to the files, if desired.

NOTE: If you already ran the installquintum.bat, you must first run the installlquintum.bat clean command prior to reinstalling. This command will restore any changes made to the quintum files back to the default parameters (see below for which files are modified upon installation).

• These lines are added to the file HPOVRoot\conf\oid_to_sym:

1.3.6.1.4.1.6618.1.1.1:Connector:QDVOIP # QUINTUM Digital TENOR1.3.6.1.4.1.6618.1.1.2:Connector:QAVOIP # QUINTUM Analog TENOR

• These lines are added to the file HPOVRoot\conf\oid_to_type:

1.3.6.1.4.1.6618.1.1.1:Quintum:Epilogue:H # Quintum-Digital Tenor1.3.6.1.4.1.6618.1.1.2:Quintum:Epilogue:H # Quintum-Analog Tenor

installquintum.bat quintum.reg quintum.exe

quintum.conf quintum.fields quintum_type

connector_qdvoip connector_qavoip Tenor_D.ico

quintum_sym Tenor_A.ico uninstallquintum.bat

P/N 480-0003-00-13 5-5


• 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" CriticalFORMAT Received trap:generic #$G specific #$S. $#args:$*SDESCT1IU_in_loopback;_network_requestEDESC###EVENT Major_Alarm .1.3.6.1.4.1.6618.2.0.2 "Status Events" MajorFORMAT Received trap:generic #$G specific #$S. $#args:$*SDESCCorruption_of_configuration_info.EDESC###EVENT Minor_Alarm .1.3.6.1.4.1.6618.2.0.3 "Status Events" MinorFORMAT Received trap:generic #$G specific #$S. $#args:$*SDESCRIU_not_installeEDESC###EVENT Report_Status_Alarm .1.3.6.1.4.1.6618.2.0.4 "Status Events" NormalFORMAT Received trap:generic #$G specific #$S. $#args:$*SDESCUswcommentEDESC###EVENT Uswcomment .1.3.6.1.4.1.6618.2.0.0 "Status Events" NormalFORMAT Received trap:generic #$G specific #$S. $#args:$*

5-6 P/N 480-0003-00-13


SDESCUswcommentEDESC

• The quintum.exe file is added to the HPOVRoot\bin directory.

• These files are added to the HPOVRoot\bitmaps\C directory:

TENOR_D.icoTENOR_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_QDVOIPCONNECTOR_QAVOIP

HP Openview will then identify and “auto-discover” the Tenor unit as an SNMP agent. An icon will appear on the screen to represent each Tenor unit. See below.

Figure 6-1 Tenor SNMP Agent Icon

Configure network manager IP address

Through Tenor’s Command Line interface (CLI), you can configure the IP address for the network management site where HP Openview is running. Once the IP

P/N 480-0003-00-13 5-7


address is configured, the Tenor will be able to process and generate traps for exist-ing alarms, which will enable HP Openview to monitor the Tenor unit for alarm states.

To set the IP address, use the following CLI command:

config sys snmptrapip <index><ip>. This command configures the IP address of the network management site in the Tenor unit from which the SNMP traps will be generated. Valid entry: The index number of 1-3 (the index number is used to des-ignate the index # for the network manager to be used) followed by the IP address for the network management site.You can assign a Teor unit up to three network managers; each manager will have a different index number.

Assign an IP address as follows:

NOTE: The following instructions assume your PC is running Windows 95 or later.

1. Click on Start> Run. The Run window will appear.

2. Type telnet in the Open box and click on Ok.

3. Click Connect> Remote System.

4. In the Host Name window, enter the IP address of the unit from which you would like to view alarms.

5. In the port window, choose telnet (port 32 is the default port for a telnet ses-sion).

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.

9. At the Quintum prompt, type config sys snmptrapip<index><ip>. For exam-ple, type config sys snmptrapip 3 208.226.140.121 (this will assign index of 1

5-8 P/N 480-0003-00-13


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.

P/N 480-0003-00-13 5-9


Working with SNMP

View traps

You can view the traps HP Openview receives from the Tenor unit as follows:

NOTE: Ensure HP Openview is running.

1. From the HP Openview map where the Tenor units appear, right-click on the Tenor icon for which you want to view traps and select Alarms.

2. From the Alarm Categories window, click on All Alarms. All traps (alarm mes-sages) will be listed in order of which they occurred.

View Alarm Status via Tenor icon

Through the color of a Tenor icon on the HP Openview desktop, you can determine the alarm state of the unit as well as view the corresponding alarms. Valid icon col-ors are listed below.

• Green Icon. No Alarm indicated.

• Red Icon. Critical Alarm (used for when HP Openview cannot communicate with the Tenor or there is a severity level 1 alarm)

• Orange Icon. Major Alarm (used for severity level 2 alarms)

• Yellow Icon. Minor Alarm (used for severity level 3 alarms)

• White Icon. Info Alarm (used for severity level 4 alarms)

View the alarms associated with a Tenor unit as follows:

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-13 5-10


3. To view the alarms associated with that icon, right-click from anywhere on the HP Openview desktop and select Alarms. The All Alarms Browser window will appear, which contains the list of alarms.

Set up Tenor status polling

The following explains how to configure HPOV to determine and display unit sta-tus if the Tenor is not configured to send traps. Polling is only intended for Tenors which are not accessible to configure the network manager IP address using the Tenor’s Command Line Interface (CLI). We do not recommend polling more than 10 Tenors.

1. From the HP Openview desktop, right-click on the desired Tenor unit icon and select Object Properties.

2. From the Attributes window, select Quintum Tenor attributes.

3. Click on Edit Attributes.

4. Select Turn on Tenor Status Polling (the toggle allows you to set to True or False.) Select True.

5. Click on Verify. After the verification is complete, click Ok.

Polling occurs in a 30 second interval, or whenever a Tenor trap is received.

Set up Debug Message Display window

The following explains how to display debug messages that are generated by the quintum.exe. This window is used to troubleshoot HPOV processing events for the Tenor icons.

1. From the HP Openview desktop, right-click on the desired Tenor unit icon and select Object Properties.

2. From the Attributes window, select Quintum Tenor attributes.

3. Click on Edit Attributes.

P/N 480-0003-00-13 5-11


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-13 5-12

Chapter 6: System Alarms

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

Specifically, the following topics are included:

Description of Alarm Manager

View alarms via Telnet

Delete and filter alarms

Monitor alarm history

P/N 480-0003-00-13 6-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.

How to Read Alarms

The Alarm Manager reports alarms according to criteria such as the alarm’s sever-ity 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.

Figure 6-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 1 03:16:15 1999

192.168.1.50:7:ALR:1:Loss of Framing(Red Alarm):2:1:Thu Jan 1 01:42:15 1999



192.168.1.50:8:CLR:1:Yellow Alarm:1:2:Thu Jan 1 00:00:00 1999

See Table 6-1 forvalid field entries.

6-2 P/N 480-0003-00-13


Definitions for all generated alarm fields appear in Table 6-1.

Table 6-1 Alarm Fields and Definitions

Field Definition Valid Entry

IP Address The unit’s 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 His-tory)

The type of alarm gener-ated.

ALR = Alarm. This indi-cates an active alarm con-dition.CLR= Clear. This indi-cates an alarm that has been cleared from the sys-tem. RPT= Report. Information about an alarm.

Severity Level of alarm severity. 1 = Critical (An error has occurred that affects com-plete system). 2 = Major (An error has occurred that affects sys-tem signaling or inter-faces.) 3 = Minor (A minor prob-lem is detected).4 = Info (Information report about a minor prob-lems.)

Description A text description of the alarm; see Table 6-2 for detailed description.

Varies.

P/N 480-0003-00-13 6-3


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 dig-its.Time: 6 digits (hour/min-utes/seconds based on a 24-hour clock).Year: 4 digits.

Field Definition Valid Entry

6-4 P/N 480-0003-00-13


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 6-1 and Table 6-2 for more information).

Table 6-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 signal-ing, 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 a 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 Connec-tion Lost

Indicates that the Gatekeeper lost connection with the Border Element. This is cleared if the connection is re-established.

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 Regis-tered with Gatekeeper

The Call Handler process cannot be registered with the gatekeeper.

P/N 480-0003-00-13 6-5


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 dis-carded.

RAS Message Appears 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 dis-carded.

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).

File Missing in the File Server

This alarm will be reported to the system when a particu-lar 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).


6-6 P/N 480-0003-00-13


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 param-eters 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 amountRADIUS Server: Not supported currencyRADIUS Server: Credit time (-1)RADIUS Server: Credit time < 6 secRADIUS Server: Invalid error code

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 dis-carded.


P/N 480-0003-00-13 6-7


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 Win-dows 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:

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.

6-8 P/N 480-0003-00-13


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 through the Com-mand Line Interface (CLI). See Chapter 4: Getting Started: Command Line Interface (CLI).

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 through the Com-mand Line Interface (CLI). See Chapter 4: Getting Started: Command Line Interface (CLI).

P/N 480-0003-00-13 6-9


You can now enter commands for the function you want to perform (i.e., dis-play alarms, delete alarms). See the sections which follow.

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 Con-nection).

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

Figure 6-2 Active Alarm ExampleIP# 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


192.168.1.50:11:1:Loss of Framing(Red Alarm):1:1:Thu Jan 1 00:00:00 1999


6-10 P/N 480-0003-00-13


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 Con-nection).

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 6-3.

Figure 6-3 Alarm History Example

IP# Sequence# Type Severity Desc Line# Channel# Date/Time





192.168.1.50:8:CLR:1:Yellow Alarm:1:1:Thu Jan 1 00:00:00 1999

P/N 480-0003-00-13 6-11


Filter Alarm History

The Alarm Manager via telnet session enables you to filter the alarm history. Fil-tering 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 6-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:

1. Ensure a connection to the Alarm Manager is established (see Establish Con-nection).

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 exam-ple, type filter l 2. This will filter all alarms that occur on the PSTN line. See Table 6-1 for valid line options.

4. To set the filter back to the default settings (all fields displayed in list), type fil-ter d. The alarms will not be filtered by any criteria.

6-12 P/N 480-0003-00-13


Delete Alarms

Alarms are not automatically cleared from the Tenor unit’s 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-13 6-13

Chapter 7: Call Detail Recording

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-13 7-1


Overview

Through the Call Detail Recording (CDR) feature, the Tenor unit is able to gener-ate a CDR at the completion of each call. A CDR is a string of data which contains call information such as call date and time, call length, calling party, and called party. From this information you can capture billing type data which can be used to create billing reports.

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.

7-2 P/N 480-0003-00-13


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 7-1) illustrates the general transfer of information; both connection types are described in the sec-tions which follow.

Figure 7-1 Flow of CDR Information

Before attempting to collect CDRs, you should configure the desired information. Through CLI commands, you can assign the CDR server IP address, CDR server

CDR ServerTenor

Sends Password Prompt

Provides Tenor's IPaddress and unit name

CDR Server logsinto Tenor port

9002/9003

Sends Welcome Message

Verifies Password

Provides last CDR sequencenumber received

Enters password

Begins delivering CDRs

Tenor connectsautomatically

(after initial configuration ofCDR port and IP address)

OR

TCP/IP Connection Established

P/N 480-0003-00-13 7-3


port number, CDR server password and CDR format information using the follow-ing 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 for-mat), 100 (standard format with session ID functionalit), 101 (extended for-mat 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 Tenor’s reset number. If the reset number is 0, the last sequence number will be the sequence number of the CDRs in the Tenor’s 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 num-ber 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 cap-ture 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.

7-4 P/N 480-0003-00-13


CDR Server Establishes Connection with Tenor

If no IP address/port number is configured, the CDR server has to initiate the ses-sion. 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-13 7-5


CDR Output

The following is an example of a CDR output. Each field in a CDR string is sepa-rated 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 function-ality.

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,12345678901234,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

7-6 P/N 480-0003-00-13


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 indi-vidual 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 pass-through call going from PBX to PSTN or call going from PSTN to PBX.

Duration: Call duration. This value is in seconds, the value will be 0 if never con-nected.

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: yyyymmddhhmmss where yyyy (4 digits for year), mm (2 digits for month), dd (2

P/N 480-0003-00-13 7-7


digits for day), hh (2 digits for hour), mm (2 digits for minutes), ss (2 digits for sec-onds).

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 indi-cation 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.

7-8 P/N 480-0003-00-13


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. Possi-ble 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.

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.

Cause Code Definitions

P/N 480-0003-00-13 7-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 sec-onds). 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 termina-tion 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-13 7-10

Chapter 8: Using IVR

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-13 8-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 custom-ize 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. Several language are supported for voice prompts: English, Mandarin, Persian, French, Spanish, German, and Arabic. 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 con-figured, 2 for the second language configured or 3 for the third language config-ured.

8-2 P/N 480-0003-00-13


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 plac-ing 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 secu-rity. The Tenor prompts the caller to enter an account number and a PIN (per-sonal 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 8-1 for an illustration of IVR and Billing implementation.

P/N 480-0003-00-13 8-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 informa-tion, 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 authen-tication fails, the call will not be answered but simply disconnected. If authentica-tion succeeds, the call will be answered and second dial tone will be provided.

ANI Authentication Type 2 enables calling subscribers to receive three authentica-tion 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 authentica-tion with the ANI fails, the caller is prompted for a PIN number. If the authentica-tion succeeds, a 2nd dial tone is sent to receive a DNIS.

Multi-sessionMulti-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 ##.

8-4 P/N 480-0003-00-13


Figure 8-1 IVR and Billing Implementation

Tenor IVR

Tenor IVR

Tenor IVR

Prompt Files

IP / Ethernet

IVR Prompt Server - Primary

IVR Prompt Server - Secondary

RADIUS Server - Primary

RADIUS Server - Secondary

P/N 480-0003-00-13 8-5


Typical IVR Network Connection/Process

See Figure 8-2 for a typical network configuration for IP based pre-paid calling card/post-paid account services. This figure illustrates the originating Tenor is con-figured 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 8-1.

Figure 8-2 Typical Network Connection/Call Flow Process

PSTN

Telephone

Telephone

Prepaid Enable Tenor

DestinationTenor

IVR Prompt ServerPrimary & Secondary

RADIUSServer - Secondary

RADIUS ServerPrimary & Secondary

PSTN

IP Network

1, 4, 5, 8, 9, 12

13

1314

Prepaid Enable

2, 3, 6, 7, 10, 11, 15, 16

RADIUS ServerPrimary & Secondary

Tenor

8-6 P/N 480-0003-00-13


ed .

ng

a-

on.

o-

and

Table 8-1 Call Flow Process for Figure 8-2

Number Process

1 User dials access number to initiate call (i.e., 1-800-xxx-xxxxx).

2Tenor answers call and determines user is calling a pre-paid service bason the number dialed or the trunk group to which the call is transferredTenor sends Start Accounting to RADIUS server. Start Accounting is optional.

3 RADIUS server acknowledges start accounting request. Start Accountiis optional.

4 Tenor prompts the subscriber for the card number.

5 Caller enters the card number.

6 Tenor sends the card number to the RADIUS server for verification.

7 RADIUS server returns the credit balance for the account.

8 Tenor plays the credit amount and prompts the subscriber for the destintion number.

9 Caller enters the destination number.

10 Tenor sends the destination number to the Radius server for authorizati

11 RADIUS server responds with the duration for which the caller is authrized 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 the call is established.

P/N 480-0003-00-13 8-7


15 If either side disconnects, Tenor sends stop accounting request to the RADIUS server.

16 RADIUS server acknowledges the stop accounting request.

8-8 P/N 480-0003-00-13


Configure IVR - Quick Start

For a Tenor to be used as part of the complete IVR system, and communicate effec-tively 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-13 8-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), 3 (French), 4 (Spanish), 5 (German), or 6 (Arabic).

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 account-ing” messages will be sent.

8-10 P/N 480-0003-00-13


Configure Voice Prompts

What is a Voice Prompt?

A voice prompt is a pre-recorded message played for a caller at specific times dur-ing 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 proto-col. 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 Tenor’s cache memory for replay until one of the follow-ing happens: an ivrupdate command is issued, a change of IP address in the data-base, 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 Serv-ers). 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 it fails, the active server will be switched back to the original one, and the cycle repeats itself.

P/N 480-0003-00-13 8-11


Voice Prompt Requirements (English Requirements)

NOTE: To ensure good speech quality, the voice prompts should be profession-ally recorded in a studio.

Table 8-2 specifies requirements for each voice file recorded. Definitions for each table entry are listed below.

• 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 “+” indi-cates “in addition to” the filename.

• Usage Example. This field represents the actual pre-recorded speech being used in a specific speech pattern.

Table 8-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. Good-bye.

account_number

“account number” [enter] + [account_number]+ [pound_key]

Enter account number followed by the pound key.

8-12 P/N 480-0003-00-13


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.

card_number “card number”

[enter] + [card_number]+ [pound_key]

Please enter your card number fol-lowed 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 num-ber”

[enter] + [destination] + [pound_key]

Please enter your destination num-ber followed by the pound key.

dollar “dollar” - -

dollars “dollars” - -

eight “eight” - -

eighteen “eighteen” - -

eighty “eighty” - -

eleven “eleven” - -

P/N 480-0003-00-13 8-13


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 desti-nation number.

fifteen “fifteen” - -

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 num-ber.”

- -

language “for English press” [lang] + [one] For English press one.

minute “minute” - -

P/N 480-0003-00-13 8-14


minutes “minutes” - -

next call_ pound “To make another call press the star key twice”

- -

next call_star “To make another call press the pound key twice”

- -

nine “nine” - -

nineteen “nineteen” - -

ninety “ninety” - -

no_funds “You have insuffi-cient funds in your account.”

[no_funds] + [good_bye]

You have insuffi-cient 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 tech-nical difficulties.”

[problems] + [hang_up]

We are currently experiencing technical difficul-ties. Please hang up and call again later.

P/N 480-0003-00-13 8-15


remaining “remaining.” [ <money> OR <time>] + [remaining]

Eighteen minutes remaining.Twenty cents remaining.

rial “rial” - -

second “second” - -

seconds “seconds” - -

seven “seven” - -

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” - -

P/N 480-0003-00-13 8-16


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 spe-cific 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

• For Spanish, use the filename c:\quintum\ivr\Spanish

• For German, use the filename c:\quintum\ivr\German

• For Arabic, use the filename c:\quintum\ivr\Arabic

you_have “You have” [you_have] + [<any number>] + [remain-ing]

You have six cents remaining.

yuan “yuan” - -

zero “zero” - -

zero_balance “You have zero balance in your account.”

[zero_balance] + [good_bye]

You have zero balance in your account. Good-bye.

P/N 480-0003-00-13 8-17


3. Record all voice prompts and store under the c:\quintum\ivr\English subdirec-tory.

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 Tenor’s RAM. This means 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 ivrup-dateprompts 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-13 8-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 received with your unit.

P/N 480-0003-00-13 8-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 8-3.

Figure 8-3 Radius Statistics Example

PRIMARY RADIUS SERVER STATISTICS

Attempts Responses Timeouts Accepts Rejects

Authentication: 6522 5561 961 5318 243

Accounting: 6107 5849 258

SECONDARY RADIUS SERVER STATISTICS

Attempts Responses Timeouts Accepts Rejects

Authentication: 712 99 613 6 93

Accounting: 37 21 16

P/N 480-0003-00-13 8-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-13 8-21


Call Flow - Specifications

Pre-paid Calling Card - Call Flow (with default language)

Figure 8-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-13 8-22


Figure 8-4 Pre-paid Calling Card - Call Flow (default language)

“Please Enter Your Card Number”

“Welcome ”

STOP ACCOUNTING TELEPHONY LEG

“You have X dollars and Y cents remaining”

CALLING PARTY

AUTHORIZATION ( DNIS )

STOP ACCOUNTING IP LEG ACK

CONNECT

“Please Enter The Phone Number to call”

START ACCOUNTING ACK

STOP ACCOUNTING IP LEG

DISCONNECT

AUTHORIZATION RESP (TIME)

SETUP

GET DNIS

AUTHENTICATION RESP (MONEY)

AUTHENTICATION (CARD NUMBER)GET CARD NUMBER

CONNECT

START ACCOUNTINGSETUP

PREPAID ENABLED

TENOR

RADIUS SERVER

CALLED PARTY

“You have x minutes ”

STOP ACCOUNTING TEL LEG ACK

P/N 480-0003-00-13 8-23


Post-paid Calling Card - Call Flow (with default language)

Figure 8-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.

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 message formats for transmitting and receiving dialed information, account data and authorization codes between the network access gateway and the billing server.


P/N 480-0003-00-13 8-24


V

Figure 8-5 Post-paid Account - Call Flow (default language)

“Welcome”

“Please Enter The Phone Number to call”

“Please Enter Your Pin Number”


STOP ACCOUNTING ACK

CONNECT

“Please Enter Your Account Number”

START ACCOUNTING ACK

STOP ACCOUNTING

DISCONNECT

AUTHORIZATION RESPONSE

SETUP

GET DNIS

AUTHENTICATION RESPONSE

AUTHENTICATE (ACCT, PIN)

GET ACCOUNT NUMBER

START ACCOUNTINGSETUP

POSTPAID ENABLED

TENOR RADIUS SERVER

CALLING PARTY

CALLED PARTY

GET PIN NUMBER

P/N 480-0003-00-13 8-25


Pre-paid and Post-paid Calling Card - Call Flow (with multiple language support)

Figure 8-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.



P/N 480-0003-00-13 8-26


Figure 8-6 Pre-paid and Post-paid Calling Card - Call Flow with multiple language support

“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)

CALLING PARTY

[START ACCOUNTING ACK]

Same procedure as Figure 1-4 and Figure 1-5

CONNECT

[START ACCOUNTING]SETUP

TENOR

RADIUS SERVER

CALLEDPARTY

Same procedure as in Figure 8-4 and 8-5

“Press 0 for English”“Press 1 for Persion”“Press 2 for Mandarin”“Press 3 for French”“Press 4 for Spanish”“Press 5 for German”“Press 6 for Arabic”

P/N 480-0003-00-13 8-27


Pre-paid and Post-paid Calling Card - Call Flow (with Multi-Ses-sion Call support)

For a multi-session call, the calling party can interrupt the call by pressing a multi-session key at anytime and making a new call. When the called party disconnects the call first, the Tenor asks if the caller wants another call; the user can then press the designated key. Figure 8-7 is a diagram of the call flow for pre-paid and post-paid 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.


Called Party 1. The first destination called party.

Called Party 2. The second destination called party.

P/N 480-0003-00-13 8-28


Figure 8-7 Pre-paid and Post-paid Calling Card - Call Flow (multi-session support)

Case1> ## or ** on speech

CALLING PARTY

“Please Enter Destination Number”

If you want another call, press ** or ##

GET Destination Number


AUTHORIZATION (DNIS)

CONNECT

SETUP

TENOR

RADIUS SERVER

CALLED PARTY2

DISCONNECT

CALLED PARTY1

CONNECT

STOPACCOUNTING (Leg 1)

Case 2> DISCONNECT

## or **

STOPACCOUNTING (Leg 1)

“Please Enter Destination Number”

GET Destination NumberAUTHORIZATION (DNIS)


CONNECT

P/N 480-0003-00-13 8-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 8-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.

RADIUS Server. Remote Authentication Dial-In User Service for authenticating with ANI the calling number.


P/N 480-0003-00-13 8-30


Figure 8-8 ANI Authentication Application Type 1 - Call Flow



Second Dial Tone

PARTY



CONNECT


DISCONNECT


SETUP

GET DNIS


Yes : AUTHENTICATION (ANI)

CONNECT

SETUP

ENABLED TENOR

SERVER

ANI No: Fast Busy

Auth fail of ANI

No: Fast Busy

P/N 480-0003-00-13 8-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 8-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.

RADIUS Server. Remote Authentication Dial-In User Service for authenticating with ANI the calling number.


P/N 480-0003-00-13 8-32


Figure 8-9 ANI Authentication Application Type 2 - Call Flow



Second Dial Tone

CALLING PARTY



CONNECT


DISCONNECT


SETUP

GET DNIS


Yes : AUTHENTICATION (ANI) 1

CONNECT

SETUP

ANI AUTH ENABLED

TENOR

RADIUS SERVER

CALLED PARTY

ANI No: Pin prompt Tone

GET PIN

AUTHENTICATION (PIN) 2

Auth fail of ANI

ANI auth fail : Pin prompt Tone

GET PINAUTHENTICATION (PIN) 3


P/N 480-0003-00-13 8-33


ous

p

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 8-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 8-3 Start Accounting Request Message Attributes

IETF Attribute Number

Attribute Name

Vendor Specific Attribute Number

Description Value Format Sample

4 NAS-IP-Address

IP Address of the requesting Tenor

Numeric 3506546880

26 Cisco-NAS-Port 2 Tenor's physical port on which the call is active

String Fxs1/0/1

61 NAS-Port-Type Tenor's physical port type

String 0: Asynchron

1 User-Name Account number, calling party num-ber, or blank

String 7325551212

30 Called-Station-Id

The IVR access number, normally an 800 number

String 8004609000

31 Calling-Station-Id

Calling Party Number (ANI)

String 7329701330

40 Acct-Status-Type

Account Request Type (start or stop)

Numeric 1: start, 2: sto

P/N 480-0003-00-13 8-34


r

inate

6 Service-Type Type of service requested

Numeric 1: login

26 h323-gw-id 33 Name of the Tenor String Quintum Teno

26 h323-conf-id 24 16 octets h323 GUID

16 octets

26 h323-incoming-conf-id

1 A number to match multiple calls in a session

16 octets

26 h323-call-origin 26 The call relation to the tenor

String Answer, Origetc

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 account-ing identifier - match start & stop

String 13432

41 Acct-Delay-Time

Number of sec-onds tried in send-ing a particular record

Numeric 5

P/N 480-0003-00-13 8-35


0

ou

2

0

0

Stop Accounting Request Message Attributes

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

Table 8-4 Stop Accounting Request Message Attributes

IETF ATTRIBUTE NUMBER

Attribute Name



4 NAS-IP-Address

IP Address of the requesting Tenor Numeric 350654688

61 NAS-Port-Type

Tenor's physical port type on which the call is active

Numeric0: Asynchrons

1 User-Name Account number or calling party number String 732555121

30 Called-Station-Id

Destination phone number String 732460900


Calling Party Number (ANI) String 732970133

40Acct-Status-Type

Account Request Type (start or stop) Numeric 1: start 2:

stop

6 Service-Type

Type of service requested Numeric 1: login

26 Cisco-NAS-Port 2

Tenor's physical port on which the call is active

String Fxs1/0/1

P/N 480-0003-00-13 8-36


e

or

26 h323-gw-id 33 Name of the Tenor String Quintum_Tnor

26 h323-conf-id 24 16 octets h323 GUID 16 octets

26h323-incoming-conf-id

1A number to match multiple calls in a session

16 octets

26 h323-call-origin 26 The call relation to the

tenor String Answer, Originate

26 h323-call-type 27 Protocol type used on

this leg of the call String TelephonyVOIP

26 h323-setup-time 25 Setup time in NTP

format String

26h323-connect-time

28 Connect time in NTP format String

26h323-disconnect-time

29 Disconnect time in NTP format String

26h323-disconnect-cause

30 Q.931 disconnect cause code Numeric

26h323-voice-quality

31 ICPIF of the voice quality Numeric

26 h323-remote-address

23 IP address of the remote gateway Numeric

P/N 480-0003-00-13 8-37


44 Acct-Session-Id

A unique accounting identifier-match start & stop

String

42 Acct-Input-Octets

Number of octets received for that call duration

Numeric

43Acct-

Output-Octets

Number of octets sent for that call duration Numeric

47 Acct-Input-Packets

Number of packets received during the call

Numeric

48Acct-

Output-Packets

Number of packets sent during the call Numeric

46Acct-

Session-Time

The number of seconds for which the user receives service.

Numeric

41Acct-

Delay-Time

No of seconds tried in sending a particular record.

Numeric 5

P/N 480-0003-00-13 8-38


ple

880

onous

212

330

:80055

Authentication Request Message Attributes

Table 8-5 lists the message attributes in the Authentication Request message pack-age sent between the Tenor and the RADIUS server.

Table 8-5 Authentication Request Message Attributes

IETF ATTRIBUTE

NUMBER

Attribute Name


Description Value Format Sam

4 NAS-IP-Address

IP Address of the requesting Tenor

Numeric 3506546

61 NAS-Port-Type


Numeric 0: Asynchr

1 User-Name

Account number, calling party number, or blank

String 7325551

26 h323-conf-id 24 16 octets h323 GUIDE 16 octets


Calling Party Number (ANI) String 7329701

26 h323-ivr-out 1

IVR Access Number, normally an 800 number

String ACCESS51234

2 User-Password 16 octets user password String

P/N 480-0003-00-13 8-39


n

Authentication Response Message Attributes

Table 8-6 lists the message attributes in the Authentication Response message packet sent between the Tenor and the RADIUS server.

Table 8-6 Authentication Response Message Attributes


Attribute Name



26 h323-return-code 103

The reason for failing authentication

Numeric 2 Invalid pinumber

26 h323-preferred-lang 107

Lang to play prompt specified by h323-prompt-id.

ISO 639-1 En

26 h323-credit-amount 101

Amount of credit (currency) remaining in the account

Numeric 13.25

26 h323-billing-model 109

Type of billing service for a specific call.

Numeric 1:debit/prepaid

26 h323-currency-type 110

Currency for use with h323-credit-amount

ISO 4217 USD

P/N 480-0003-00-13 8-40


ple

46880

yn-ous

51212

09000

01330

Authorization Request Message Attributes

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

Table 8-7 Authorization Request Message Attributes

31 h323-prompt-id 104

Index into an array of prompt files used by the Tenor

Numeric 27


Attribute Name



4 NAS-IP-Address

IP Address of the requesting tenor

Numeric 35065

61 NAS-Port-Type


Numeric 0: Aschron

1 User-Name Account number or calling party number or blank

String 73255

26 h323-conf-id 24 16 octets h323 GUID

16 octets

30 Called-Sta-tion-Id

Destination phone number

String 73246

31 Calling-Sta-tion-Id

Calling Party Number (ANI)

String 73297

P/N 480-0003-00-13 8-41


OW_LAG:

26 h323-ivr-out 1 Flag for subse-quent authoriza-tions in a session

String FOLLON_F0

2 User-Pass-word

16 octets user password

P/N 480-0003-00-13 8-42


ple

lid pin r

Authorization Response Message Attributes

Table 8-8 lists the message attributes in the Authorization Response message packet sent between the Tenor and the RADIUS server.

Table 8-8 Authorization Response Message Attributes


Attribute Name



26 h323-return-code 103 The reason for failing authen-tication

numeric 2 Invanumbe

26 h323-credit-time 102 Number of sec-onds for which the call is authorized

numeric 360

P/N 480-0003-00-13 8-43

Chapter 9: Troubleshooting/Maintenance

This chapter tells you how to troubleshoot calls entering and exiting the Tenor unit, as well as how to maintain the health of your system. You will find information about how to view the unit’s LEDs, as well as how to read alarms and check basic connections.


General troubleshooting

Monitor LEDs

Review alarm list

Perform loopback test

Review common symptoms/problems

P/N 480-0003-00-13 9-1


Before you Begin

Before you begin troubleshooting a potential malfunction indicated by an alarm or LED, it is a good idea to check your basic hardware connections. See below.

• Ensure power cord is firmly installed in the back panel’s power jack and the other end is plugged into the wall outlet. Verify that the Power LED is on.

• Ensure the unit’s power switch is in the On position. If the unit is not work-ing, toggle the power switch to reset the system. If the unit is reset, the set-tings you configured may be lost.

• Verify that all RJ-45 cables are fit snugly in each appropriate front panel jack. PBX/PSTN/Ethernet connection faults may cause a number of network inter-facing or connection issues.

• Verify that the DB-9 cable is fitted properly in the RS-232 port.

If you suspect the problem to be on the network end, contact your Central Office to verify proper operation.

Monitor LEDs

LEDs monitor the health of the system; they are the first signal that the unit is not working properly or that an internal or external error has occurred. LEDs appear on the front of the unit (LED descriptions are detailed in Chapter 2: Hardware Com-ponents).

Check Chapter 2: Hardware Components to ensure the correct lighting of each LED and then see Common Symptoms/Problems for troubleshooting information. If the LEDs are not lighting at all, check the AC power source to ensure power is being supplied to the unit.

9-2 P/N 480-0003-00-13


View Alarms

Alarms help you identify where a specific problem is occurring with the Tenor Gateway unit. Through the alarm list, you can read a description of the problem, and isolate where the problem is occurring. Verify all severity 1 alarms first; these alarms indicate that the unit is in critical condition and the entire system is affected.

See Chapter 6: System Alarms for how to generate an alarm list, as well as a list of alarm field definitions. To view any recurring problem or condition, generate an alarm history.

Verify Unit Provisioning

An error with Tenor Gateway’s provisioning may cause a number of problems. Sometimes, it may be simple error, such as an incorrect IP address or telephone number or it may be something more complex, such as incorrect analog specific parameters.

Evaluate your system provisioning. Check all data provisioning information; see Chapter 4: Getting Started: Command Line Interface (CLI).

P/N 480-0003-00-13 9-3


Perform a Loopback Test

A loopback test enables you to test the integrity of the unit’s PSTN and PBX ports. This test will confirm that the ports are operating correctly.

Perform a loopback test as follows:

1. Obtain the RJ-45 straight through cable (you can use one shipped with the unit or one you may already have).

2. Insert one end of the cable into one of the front panel’s PBX ports.

3. Insert the other end of the cable into one of the front panels PSTN ports.

The LEDs adjacent to each port (PSTN or PBX) will stay lit for a few seconds and go out. This indicates the ports are working correctly.

9-4 P/N 480-0003-00-13


Common Symptoms/Problems

Below is a list of common symptoms and problems you may encounter. Use this list as a guideline; if your problem is not listed, use the diagnostic procedure in the beginning of this chapter.

Table 9-1 Common Symptoms/Problems

Common Symptom/Problem Description/Solution

Unit will not turn on. Check AC power source.

Communication between Tenor Gateway and the PBX or PSTN cannot be established.

There are several reasons why commu-nication may be unsuccessful. A few of the most common are listed below.

Verify correct cables are installed in the PBX and PSTN ports.

Unit configuration may be wrong. Examine the configuration parameters.

Network issues may cause a number of problems. Contact the Central Office to perform test procedures.

ALERT LED is on and not flashing. One or more internal diagnostic tests have failed. Contact customer service. LED will stay on for a minute or so when the unit is powered up.

Communication with Ethernet Hub cannot be established.

Verify cable is firmly installed in unit’s Ethernet port.

P/N 480-0003-00-13 9-5


Communication between computer’s COM port and Tenor Gateway’s console port can-not be established.

Verify DB-9 cable is firmly placed in unit’s console port and PC’s COM port.

Verify HyperTerminal port settings. See Chapter 4: Getting Started: Com-mand Line Interface (CLI) for configu-ration information.

Tenor Gateway cannot receive or transmit calls.

Check PBX and PSTN port LEDs.

Generate alarm list for more informa-tion.

The PBX and PSTN port LEDs stay lit after initial connection

The PBX and/or PSTN ports may not be operating correctly; calls cannot be connected.

Verify cables are securely connected. Contact Central Office for interface issues.

Common Symptom/Problem Description/Solution

9-6 P/N 480-0003-00-13


Restore Factory Defaults

A factory default is a default setting that is configured in the factory before the unit is shipped. We do not advise that you reset the system back to factory defaults unless advised to do so or if your system becomes corrupted.

If you choose to restore the factory defaults, all current configuration will be deleted, including your password. Restoring factory defaults does not change or delete the Tenor’s IP address, subnet mask or default gateway; you will still be able to communicate with the unit after a reset.

You can restore factory defaults through the Command Line Interface (CLI) as fol-lows:

Reset your system to factory defaults as follows:

1. Through CLI, access the config# prompt.

2 Type factorydefault. A message will ask you confirm that you want to restore the unit to factory defaults.

3 Type y (yes) to restore to factory defaults (To cancel, type n (no) to cancel).

P/N 480-0003-00-13 9-7


Change Password

If you lose or forget your password, you must delete the current configuration, which includes the password. Once you delete this information, all configuration except the Tenor’s IP address, subnet mask and default gateway will be lost; you will still be able to communicate with the unit.

Once you re-configure, you will need to re-configure the unit through the Com-mand Line Interface.

Delete current configuration as follows:

1. Establish a HyperTerminal connection to the Tenor Gateway. See Chapter 3: Installation.

2 Reset the unit (either turn the unit on and off ). Information about the unit will scroll on the screen.

3. Press Enter within 3 seconds.

4. Type M (to modify). To cancel, type C.

5. Press Enter through the series of questions until you reach the question Do you want to restore factory defaults (Y or N)?

6. Type Y (yes) to restore the unit to factory defaults, to cancel type N (n).

You can now re-configure the unit via Command Line Interface (CLI).

9-8 P/N 480-0003-00-13


Reset System

The Reset system feature enables you to reset the system, including hardware and software.

Reset via Front Panel

Reset the system as follows:

Use a blunt, thin object to press in the Reset button, located on Tenor’s front panel. The system will reset.

P/N 480-0003-00-13 9-9


Set the Unit to Online mode

Through the CLI’s online option, you can choose whether to put the unit online or offline. Offline (Bypass) mode is when the Tenor does not provide any call routing features and allows the PBX and PSTN lines to be connected directly to each other (internal to the Tenor). Online (Termination) mode is when the Tenor performs all of its call routing features.

When shipped, or after you reset the Tenor to factory default, the Tenor will always in offline (bypass) mode and will allow calls to pass through from the PBX to the PSTN interface and vice versa. It is important to remember to change this option when you are done configuring the unit.

NOTE: For Software Release P4-1-9 and later, is possible to “toggle” the Tenor online and offline by pressing the Diag button on the front of the unit for three seconds (the button is recessed and reachable with a paper clip). Also, the amber ALARM LED next to the green Power LED on the front panel will flash if the Tenor is offline.

By default, the Tenor is offline; at any time you can set the unit to online mode. Set the Tenor online as follows:

1. Access the config unit# prompt.

2 Type online 1 (sets the Tenor in termination mode).

9-10 P/N 480-0003-00-13


View System Information

To view system information, such as release number, etc. as follows:

1. Log on to the CLI.

2 At the Quintum prompt, type dis v. System information, including release num-ber, will be displayed.

If you need Additional Help

If you suspect the problem to be on the network end, contact your Central Office to verify proper operation.

After completing all troubleshooting/maintenance procedures and reviewing the Common Symptom/Problems section, you can contact the Customer Service Department at the following:

Quintum Technologies, Inc. 71 James WayEatontown, NJ 07724For domestic calls: (877) 435-7553For international calls: (732) 460-9399email: [email protected]

P/N 480-0003-00-13 9-11

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 accom-modate 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-2.

Figure A-2 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-3 RJ-45 (10/100BT) Connector Pinouts - Diagram

A-2 P/N 480-0003-00-12

Appendix A: Cables

Figure A-4 RJ-45 (10/100BT) Connector Pinouts

Table A-1 RJ-45 (10/100BT) Connector Pinouts

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.

Pin # Signal Definition Color

1 RX ring/TX + Receive Ring/Transmit Data

White w/orange

2 RX tip/TX - Receive Tip/Transmit Data

Orange

3 RX + Transmit Data White w/green

4 TX ring Transmit Ring Blue

5 TX tip Transmit Tip White w/blue

6 RX - Receive Data Green

7 n.c. no connect White w/Brown

8 n.c. no connect Brown

P/N 480-0003-00-12 A-3

Appendix A: Cables

Figure A-5 RJ-45 (PSTN/PBX) Connector Pinouts - Diagram

Table A-2 RJ-45 Connector Pinouts


1 n.c. no connect White w/orange

2 n.c. no connect Orange

3 Ring Ring Ports 5-8 White w/green

4 Ring Ring Ports 1-4 Blue

5 Tip Tip Ports 1-4 White w/blue

6 Tip Tip Ports 5-8 Green

7 n.c. no connect White w/Brown

8 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-6 RJ-11 Connector Pinouts

Table A-3 RJ-11 Connector Pinouts


1 n.c. no connect Black

2 Ring Ring Ports 1-4 Green

3 Tip Tip Ports 1-4 Red

4 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 PC’s asynchronous console port. The pin order is shown in shown in Figure A-7.

Figure A-7 DB-9 Connector Pin Order

Table A-4 DB-9 Connector Pinouts

Pin # Function Direction Description

1 DEC Receive Data Carrier Detect

2 RX Receive Receive Data

3 TX Transmit Transmit Data

4 DTS Transmit Data Terminal Ready

5 SG Transmit Signal Ground

6 DSR Receive Data Set Ready

7 RTS Transmit Request to Send

8 CTS Receive Clear to Send

9 RI Receive Ring Indicator

1 2 3 4 5

6 7 8 9

P/N 480-0003-00-12 A-6


P/N 480-0003-00-13 B-1


Voice/Fax

Call Routing: PBX/PSTN/IPCoding: A-law, mu-lawVoice Algorithms: G.723.1A (5.3, 6.3 Kbps), G.726 (16, 24, 32, 40

Kbps), G.729A, G711Fax Support: Group III at 2.4, 4.8, 7.2, 9.6, 12, 14.4 KbpsAutomatic Call Detection: Voice/Modem/Fax

PSTN/PBX Connections

Interface: Analog, FXO Interface (PSTN side), FXS Interface (PBX side)

Connector: RJ-45Ringing 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 offMaximum Loop Current: 24 mARinger Equivalence Number:5 up to 1000 feet of 24 AWG or heavierRinging Frequency: 20, 25, or 50 HzRinging Voltage: 40 Volts RMS (at 20 Hz)

LAN Connection

LAN Support: 10/100 Mbps Ethernet Connection Type: Autosensing

Physical

Position: 19” (48.7 cm) rack mountable, desktop stackable, wall-mountable

Depth: 10 3/4” (27.6 cm)Length: 17 3/8” (44.5 cm)Height: 1 3/4” (4.5 cm)

B-2 P/N 480-0003-00-13


Weight: 8.0 lbs (3.6 kg)

Electrical

Ethernet: Standard 10/100Base-T RJ-45 interface (IEEE 802.3) PBX/PSTN: Standard RJ-45 connectorsConnectors: 4 (A400 and A800) RJ-45 connectors for PBX con-

nection4 (A400 and A800) RJ-45 connectors for PSTN con-nection

Console Port: RS-232/DB-9 Female Power: AC Power at 100-240 volts and 50-60 Hz

Environmental

Operating Temperature: 40° to 104° F (0 - 40° C) Operating Humidity: 20% to 80% non-condensingAltitude: -200 to 10,000 feet, or -60 to 3,000 metersStorage Temperature: 14° to 140° F, or -10° to 60° C

Agency Approvals

EMC EN55022: 1995; EN55024:1998FCC Part 15 Class A

Safety EN60950:1992UL 1950 3rd editionCA 22.2 No. 950-95

PSTN FCC Part 68, CSO-03, Other VCCI Class A ITE

AS/NZS 3548: 1995CNS 13438

P/N 480-0003-00-13 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 installa-tion. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful inter-ference to radio communications. However, there is no guarantee that interface will not occur in a particular installation. If this equipment does cause harmful interfer-ence 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 oper-ate 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:

• 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.

B-4 P/N 480-0003-00-13


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 equip-ment. 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 cus-tomer as soon as possible. Also, you will be advised of your right to file a com-plaint with the FCC if you believe it is necessary.

The Telephone Company may make changes in its facilities, equipment, opera-tions, or procedures that could effect the operation of the equipment. If this hap-pens, 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-13 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-13


Canadian Notice

The Industry Canada label identifies certified equipment. This certification means that the equipment meets certain telecommunications network protective, opera-tion, 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 equip-ment 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 mainte-nance facility designated by the supplier. Any repairs or alterations made by the user to this equipment, or equipment malfunctions, may give the telecommunica-tions 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: Users should not attempt to make electrical ground connections by themselves, but should contact the appropriate inspection authority or an electrician, as appropriate.

P/N 480-0003-00-13 B-7


P/N 480-0003-00-13 B-8


TAIWAN EMI NOTICE

P/N 480-0003-00-13 B-9


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 architec-ture. 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 informa-tion 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) ser-vices. 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 lim-ited 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. Con-gestion 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 real-time 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 termi-nals. The Gatekeeper communicates with other Gatekeepers through a Border Ele-ment.

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 con-trols 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.

SIPSIP is a signaling protocol that is used to established a session on an IP network. SIP is a request-response protocol that closely resembles Hypertext Transfer Protocol (HTTP), which forms the basis of the World Wide Web. It re-uses many of the constructs and concepts of Internet protocols such as HTTP and Simple Mail Transfer Protocol (SMTP).

SIP is Transport layer-independent, which means it can be used with any transport protocol: UDP, TCP, ATM, etc. It is text-based, so requires no encoding/decoding like H.323. And SIP supports user mobility, using proxies and redirecting requests to your current location.

There are three basic components of SIP:

1. User Agent (Endpoint)

• client element, initiates calls

• server element, answers calls

C-4 P/N 480-0003-00-12


2. Network Server (Proxy Server or Redirect Server)

• name resolution

• user location

• redirect and forking

3. Registrar

• Stores registration information in a location service using a non-SIP protocol.

TCP/IP

TCP/IP (Transmission Control Protocol/Internet Protocol) is a layered data com-munications 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 communica-tions (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 Command Line Interface (CLI).

P/N 480-0003-00-12 C-5


Advanced Topic - PPPoE

The Tenor supports PPPoE (Point-to-Point Protocol over Ethernet), which is a protocol used for encapsulating PPP frames into Ethernet frames; it creates the concept of a “session” over the Ethernet and provides residential and small business DSL (Digital Subscriber Link) broadband internet access.

Discovery ProcessThe ISP (Internet Service Provider) runs a PPPoE server (called an Access Concentrator), which accepts PPP connection. The Tenor will search for an access concentrator and obtain a MAC address of the server (ISP) and session number for the PPPoE session (Discovery).

A PPPoE session consists of two peers communicating over the Ethernet through messages (see below for a description of PPPoE protocol messages). Once each peer is aware of the other’s Ethernet address and the session number (Initiation/Offer/Request), the PPP (Session) can begin. PPP frames are encapsulated in PPPoE session frames. Discovery and session Ethernet frames have their own Ethernet protocol numbers, assigned by IEEE and distinct from IP or any other protocol: Discovery Protocol (0x8863) and Session Protocol (0x8864). Through the PPPoE session, PPP packets are sent between the Tenor and the server over the Ethernet, rather than a serial line.

PPPoE Initiation. Tenor sends the PPPoE Active Discovery Initiation (PADI) message to the Access Concentrator to initiate a session.

PPPoE Discovery (Offer). Through a PPPoE Active Discovery Offer (PADO), the Access Concentrator responds with an offer for a session.

PPPoE Discovery (Request): The Tenor collects the PADO responses and chooses one with which it would like to start a session, and then sends a PPPoE Active Discovery Request (PADR) to the Ethernet address of the Access Concentrator.

PPPoE Discovery (Session). The Access Concentrator sends back a PPPoE Active Discovery Session Confirmation (PADS) packet, agreeing to set up a session with the Tenor and allocate resources to set up a PPP session, and assign a number. The

P/N 480-0003-00-12 C-6


Tenor will then be able to identify the Access Concentrator’s Ethernet Address and the session number.

PPPoE Termination. After a session is established, the PPPoE Active Discovery Terminate (PADT) is sent by the Tenor or the Access Concentrator at any time to end the session. As a result, no further traffic is allowed to be send during that session. Even normal PPP termination packets must not be sent after sending or receiving a PADT.

PPPoE Session Process Once PPP is underway, packets are transmitted over unicast Ethernet instead of a serial link. PPP is a data link-level protocol; its encapsulates network-level packets over a serial line. See below for a list of events completed via PPPoE.

LCP. Once the PPPoE session is in progress, PPP (Point-to-Point) protocol sets up a link via LCP (Link Control Protocol) through a series of Configure Request, Configure Acknowledge, Configure NK, and Configure Reject messages. Through the LCP, the MRU (Maximum Receive Unit) is negotiated (default: 1492), as well as the Magic Number is set to identify a unique number for one of the peers.

TenorAccess

Concentrator

PPPoE Offer (PADO)

PPPoE Session (PADS)

PPPoE Request (PADR)

PPPoE Discovery (PADS)

PPOE Discovery Mode

P/N 480-0003-00-12 C-7


Password Authentication. Authentication by PAP (Password Authentication Protocol, 0xc023l, CHAP (Challenge Handshake Authentication Protocol, 0xc223), or No Authentication is set.

PAP provides a simple method for the peer to establish its identify using a 2-way handshake. Messages including Authenticate-Request, Authenticate-ACK, and Authenticate Nak are used with PAP authentication.

CHAP periodically verifies the identity of the peer using a 3-way handshake; this is completed upon initial establishment and may be repeated any time after the link has been established. The authenticator sends a “challenge” message to the peer; the peer responds using a value calculated with a “one-way hash” value and the authenticator checks the response against its calculation of the expected hash value. If the values match, the authentication is acknowledged; otherwise the connection is terminated.

IPCP. Once PPP reaches the Network-Layer Protocol phase, the IP control Protocol (IPCP) is responsible for configuring, enabling, and disabling the IP protocol modules on both ends of the point-to-point link. IPCP uses the same packet exchange mechanism as the Link Control Protocol (LCP).

DHCP. DHCP is optional for the ISP; it performs network configurations as well as IPCP. After establishment of PPP link and network, the DHCP client requests to use the IP address allocated by the IPCP to the server. If there is no problem, the DHCP client keeps the IP address. By this negotiation, the IP address will be managed dynamically by the DHCP server until the link goes down. To manage a large range of IP addresses, the ISP runs one DHCP server with many PPPoE servers in the local PSTN office. The PPPoE server works with the DHCP server as a DHCP relay.

P/N 480-0003-00-12 C-8


Configuring PPPoEFor information about configuring PPPoE, see the Command Line Interface (CLI) guide you received with the unit.

TenorAccess

Concentrator

Configuration Ack

Authentication Ack

Authentication Request

Configuration Request (LCP)

PPPoE Session Mode

Configuration Request (IPCP)

Configuration Ack

DHCP Request

DHCP Ack

LCP

PAP/CHAP

IPCP

DHCPOptional

P/N 480-0003-00-12 C-9

GLOSSARY

AAlarm. A brief message that appears on

your screen when the Tenor unit en-counters a problem (i.e., failed inter-face).

Auto Switching. If a network conditioning jeopardizes the voice quality, the Tenor unit will automatically switch the call to PSTN.

BBandwidth 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 El-ements: Primary and Secondary.

Bypass Number. A telephone number that is automatically sent to the PSTN, with-out going VoIP.

CCAS. 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

such as call date and time, call length, calling party and called party.

CDR Server. The server (or workstation) responsible for receiving and process-ing CDRs as they are generated.

DDB-9. A 9-pin cable used to connect the

Tenor unit to a PC’s asynchronous con-sole port.

EEthernet. A local area network design that

transmits 10-Mbit/s data over a shield-ed coaxial cable.

Extranet. Communications with a source outside your company.

GGatekeeper.An H.323 system which pro-

vides 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.

HH.323. A protocol standard for sending

multimedia communications (i.e., voice/data) simultaneously over pack-et-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.

P/N 480-0003-00-13 Glossary-1

IInternet. A packet based network which

transports voice/video/data over TCP/IP.

Intranet communication. Communication within the same company, usually through an Ethernet hub.

IP Address. A unique 32 bit address that identifies a network device is connect-ed to the network via TCP/IP.

IVR/Voice Response. Enables you to offer services such as Pre-paid calling cards and Post-paid accounts.

LLAN. Local Area Network. A data com-

munications 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 in-dividual lights that appear on the front panel.

PPBX. Private Branch Exchange. Tele-

phone switch located on a customer’s premises that establishes circuits be-tween users and the PSTN (public net-work).

PPPoE. Point-to-Point Protocol over Ethernet. A protocol used for encapsu-lating PPP frames into Ethernet frames.

PSTN. Public Switched Telephone Net-work (also known as Central Office) Telephone company switching facility.

RRJ-45. A CAT 5 cable used to connect the

Tenor unit to a PBX/PSTN/Ethernet.

SSelectNet. The Tenor monitors your net-

work for jitter, latency, and packet loss and will automatically switch customer calls to the PSTN when required.

SIP. Session Initiation Protocol. A signal-ing protocol used to established a ses-sion on an IP network for voice control and management

SNMP. Simple Network Management Pro-tocol (SNMP) is the standard protocol used to exchange network information between different types of networks.

Subnet Mask. An IP address that deter-mines how an IP address is divided into network and host portions according to the bits.

TTASQ™ (Transparent Auto-Switch Qual-

ity). 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/mo-dem data over the IP through an Ether-net LAN, bypassing the public network.

Glossary-2 P/N 480-0003-00-13

TCP/IP. Transmission Control Protocol/Internet Protocol. TCP/IP is a standard data communications protocol. It has several layers that define a different as-pect of how two devices should talk to each other over the WAN or LAN net-work.

Trunk Group. A collection of channels used to connect the Tenor unit to the network or another piece of equipment.

WWAN. Wide Area Network. A few remote

LAN sites linked together via modem.

P/N 480-0003-00-13 Glossary-3

INDEX

AAbout

view system 9-11Active alarms 6-10Alarm history 6-11Alarm Manager 6-2Alarms 6-2

active 6-10delete 6-13display 6-2exit 6-13fields 6-3filter 6-12history 6-11list of alarms 6-5orange 5-10red 5-10view 6-8view via Telnet 6-8view via UNIX 6-9white 5-10yellow 5-10

ANI Authentication 8-4

BBack panel 2-7

illustration 2-7label 2-7power cord 2-7power switch 2-7

CCables 2-7

AC power cord 2-7

DB-9 2-7, A-6RJ-11 2-7RJ-45 A-2, A-5

Call flowsamples 8-22

Capabilitiescall routing 1-14data network calls1-13flexible networking1-17hop-off PBX 1-16PBX calls 1-11PSTN calls 1-13virtual tie line 1-16

CDRconnect with server7-4connect with Tenor7-5output 7-6overview 7-2

CLIaccess via Telnet 4-3configuration 4-2, 4-4description 4-2user login IDs 4-2

ConnectPBX/Key System 3-10PC 3-14

DDB-9 2-7, A-6Default configuration

restore 9-7

EEthernet 1-2Extranet 1-5

FFax 3-11

P/N 480-0003-00-13 Index-1

FCCwarnings B-4

Features 1-7call routing 1-8CDR 1-10configuration 1-7easy connect 1-9H.323 gatekeeper1-9multiple interfaces1-8SelectNet 1-8service 1-8system monitoring1-10unique design 1-7

Finding 1-4Front panel

console port 2-3diag option 2-3Ethernet LEDs 2-5illustration 2-2LAN port 2-3LEDs 2-4PBX port 2-2port assignment 2-3PSTN port 2-2reset 2-2

GGatekeeper 1-4Gateway 1-4

HH.323 1-4Hardware

back panel 2-7description 2-2front panel 2-2

Help 1-4, 9-11

IImplementation

extranet 1-5internet 1-6intranet 1-4

Installation 3-3connect 3-10guidelines 3-3package contents3-3position unit 3-3rack 3-5tabletop 3-4wall mount 3-7

IVR 1-10call types 8-3configure via CLI 8-19definition 8-2quick start 8-6typical connection8-6voice prompts 8-11

LLAN

definition 1-2LEDs 2-4

alert 2-6PBX 2-6power 2-6PSTN 2-6system 2-6

Loopback 9-4

Mmulti-session 8-4

NNATAccess 1-15newlink pppoe

Index-2 P/N 480-0003-00-13

configure 1-9

PPacketSaver 1-15Password

change 9-8PBX

port assignment 2-3Phone

connect to Tenor 3-11Pinouts

DB-9 A-6RJ-45 A-2, A-5

post-paid account 8-3Power up 3-15pppoe 1-6Pre-installation guidelines3-4pre-paid calling card 8-3Product Guide

conventions 1-3PSTN

port assignment 2-3

RRADIUS

view statistics 8-20Reset

system 9-9via front panel 9-9

Reset system 9-9RJ-11 2-7RJ-45 2-3

SSelectNet 1-8SIP 1-9, C-4SNMP

configure 5-7

definition 5-2download files 5-4support 1-16traps 5-10

Specificationenvironmental B-3

Specificationselectrical B-3LAN B-2physical B-2PSTN/PBX B-2voice/fax B-2

Systempower up 3-15

TTASQ 1-2TCP/IP 1-5Telephony

extranet 1-3internet 1-3intranet 1-3

Tenorcapabilities 1-11description 1-2features 1-7typical implementations1-3

Troubleshoot 8-1, 9-1before you begin 9-2change password9-8how to 9-2LEDs 9-2loopback 9-4problems 9-5provisioning 9-3restore defaults 9-7review alarms 9-3symptoms 9-5

P/N 480-0003-00-13 Index-3

unit provisioning 9-3

UUnit

set to online 9-10UNIX

view alarms 6-9

Vvoice prompts

update 8-18VoIP

definition 1-2

WWall mount

install dimensions3-8installation 3-7required materials3-5, 3-7

WANdefinition 1-2

Index-4 P/N 480-0003-00-13

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 Quintum’s 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 Technolo-gies 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 prom-inently 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 Quintum’s option (i) repair or replacement of the software media or hardware that does not meet Quintum’s 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 Quintum’s 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 modifica-tions made to the hardware or software, or (iii) failure of the hardware or software as a result of accident, abuse or misapplication or (iv) any act of God such as, but not limited to, floods, earthquakes, lighting or (v) acts of terrorism or war, declared or not.

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 DIS-CLAIMS ALL OTHER WARRANTIES, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABIL-ITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, THE PROVISIONS SET FORTH ABOVE STATE QUINTUM’S 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 QUINTUM’S SUPPLIERS BE LIABLE FOR COSTS OF PRO-CUREMENT 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 SOFT-WARE) OR SERVICE, EVEN IF QUINTUM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND NOT-WITHSTANDING 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 WRIT-TEN 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 Internation-ally, 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 ship-ment and any labels to be put on the package. Unless otherwise directed by Quintum’s Customer Services Representative, please return product to Quintum at:

REF RMA NumberQuintum Technologies, Inc.71 James WayEatontown, NJ 07724 USA

5. Following all directions given by Customer Services Representative return the Product to the address given by the Customer Ser-vices 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-trans-ferable 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 sub-paragraph (c) (2) of the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19 or subpara-graph (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 docu-mentation, is governed by the restrictions defined in paragraph (a) (15) of the Rights in Technical Data and com-puter software clause at DFARS 252.227-7013,

Manufacturer/Owner: Quintum Technologies, Inc. 71 James Way, Eatontown, NJ 07724

ACKNOWLEDGEMENTS

Quintum Technologies, Inc., the Quintum Technologies logo, Tenor MultiPath VoIP Gateway, and Select Net are trademarks, and in some jurisdictions may be registered trademarks of Quintum Technologies, Inc. Other trade-marks appearing in this packaging are the property of their respective owners.

© Copyright 2003 Quintum Technologies, Inc. All Rights Reserved.

Date post:	27-Oct-2014
Category:	Documents
Upload:	metinyelken
View:	65 times
Download:	3 times

Analog User Guide

Documents