HP 480-0005-00-15 User Manual

Tenor Carrier MultiPat

Switch (CMS)

Te nor and Quintum are registered trademarks. Tenor Carrier MultiPath Switch (CMS), PacketSaver, Quintum Technologies, Inc., VoIP Made Easy, TASQ, SelectNet, and SelectNet Technology are trademarks of Quintum Technologies, Inc.

About this Guide

What’s included? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Product Guide Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Finding Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Chapter 1: Overview

What is Tenor CMS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Unique Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

State-of-the-Art Configuration and Network Management. . . . . . . . . . . . . . . . . . . . . . 1-3

SelectNet™ Technology Safety Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Dynamic Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Multiple Channels/Signaling Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Fractional T1/E1 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

PacketSaver™. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

IVR/RADIUS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Easy Connect to Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

H.323 Gatekeeper Call Control Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Powerful System Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Intra-trunk Routing - “Hairpinning” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Other Call Routing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Virtual Tie Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Hop-off PBX Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

SNMP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

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

H.323 Gatekeeper Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Zone Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Call Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Border Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Call Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

P/N 480-0005-00-15 TOC-1

Chapter 2: Hardware Components

Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Board interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Chassis - CMS (14 Slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Front (with AC power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Rear (with AC power). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Front (with DC Power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Rear (with DC power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Chassis - CMS960 (8 Slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Front (with AC power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Rear (with AC power). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Front (with DC Power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Rear (with DC power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Chassis- CMS240 (2 slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Front View (with AC power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Rear View (with AC power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Front view (with DC power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Rear View (with DC power) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

System Controller Card (Available for CMS P1.5.x ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

CPU Card (Available for CMS P2.x.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

WAN Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

DS1 WAN Card (with DSP module). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

T1 WAN Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

E1 WAN Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

DSP Resource Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

RJ-45 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

RJ-48 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

DB-9 to DB-9 Null Modem Cable (for System Controller card) . . . . . . . . . . . . . . . . . . 2-35

DB-9 Serial RS-232 Cable (for CPU card). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37

CMS (14 slot). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37

CMS960 (8 slot). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

With AC Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

With DC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

CMS240 (2 slot). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

With AC Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

With DC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

P/N 480-0005-00-15 TOC-2

Chapter 3: Installation

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

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

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

Install in Rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Connect to Trunk Interface - PSTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Connect to Line Interface - PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Connect to Ethernet LAN (with System Controller Card). . . . . . . . . . . . . . . . . . . . . . . 3-7

Connect to Ethernet LAN (with CPU Card) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Connect to PC Console (with System Controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Connect to PC Console (with CPU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Connect Power - CMS (14 slot), DC only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Material Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Connect Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Connect Power - CMS960 (8 slot) and CMS240 (2 slot), DC only . . . . . . . . . . . . . . . . . . . 3-14

Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Material Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Connect Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Install Power Cord Strain Relief (AC only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Power up the System (for AC unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Prevent Electrostatic Discharge Damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

ESD Antistatic Wrist Strap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Provide Grounding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Assign IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

Install Software Upgrade via CMS Software Update Utility . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Upgrade from Disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Upgrade via Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Restore previous versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

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

What is the Command Line Interface? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

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

Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

User Login IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

CLI Menu Tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

P/N 480-0005-00-15 TOC-3

CLI Menu Tree - Basic View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

CLI Menu Tree - Expanded View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Access CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Telnet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Serial Port Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Move around within CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Move between modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Move within modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Execute commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Mode-specific commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Global commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Menu-specific commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Global commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Monitor mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

Diagnostic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Configure Common CLI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

Border Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

Channel Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

Digital Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

Switch Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

Trunk Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

Chapter 5: Working with SNMP

What is SNMP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

How does Tenor CMS utilize SNMP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

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

Configure network manager IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Working with SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

View traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

View Alarm Status via Tenor CMS icon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Launching Command Line Interface (CLI) from HP Openview . . . . . . . . . . . . . . . . . . 5-8

P/N 480-0005-00-15 TOC-4

Set up Tenor CMS status polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

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

Chapter 6: Call Detail Recording

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Establish connection between Tenor CMS and CDR Server . . . . . . . . . . . . . . . . . . . . . . . 6-3

Configure Tenor CMS for connection to CDR server. . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Setup CDR Server and assign password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Change CDR Password (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Tenor CMS Establishes Connection with CDR Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

CDR Server Establishes Connection with Tenor CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

CDR Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Sample Record for Standard and Extended CDR Format 0, 1, 100, 101 . . . . . . . . . . 6-6

Sample Record for Extended CMS CDR Format 3, 4, 103, 104:. . . . . . . . . . . . . . . . . 6-9

Chapter 7: System Alarms

Monitor Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

How to Read Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Valid Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

View Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Display all Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Display Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Display Alarm History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Chapter 8: Diagnostics/Maintenance

Before you Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Common Symptoms/Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Unit Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Ping Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Inspect and Replace Fuse (for AC power only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Faceplate LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Inspect Backplane/Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Power Supply (CMS, 14 slot). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

Active Call Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

Component Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

General Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Replace System Fan (for CMS, 14 slot only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Clean/Replace Foam Air Filter (for CMS, 14 slot only) . . . . . . . . . . . . . . . . . . . . . . . . 8-11

P/N 480-0005-00-15 TOC-5

Reset System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

Change Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

Card Maintenance/Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

Replace WAN/System Controller/CPU cards of identical type . . . . . . . . . . . . . . . . . . 8-14

Replace/Change DSP Module (on DS1 card) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Move card location or change card type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

If you need Additional Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20

Appendix A: Getting Acquainted with Tenor CMS in the VoIP Network

Appendix B: Specifications/Approvals

GLOSSARY

INDEX

WARRANTY

P/N 480-0005-00-15 TOC-6

About this Guide

P/N 480-0005-00-15 1

About this Guide

What’s included?

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

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

• Chapter 1: Overview. Includes a general overview of the product, including a description of the Tenor

CMS’s features and capabilities.

• Chapter 2: Hardware Components. Hardware descrip tion, including the chassis, WAN cards (T1, E1, DS1), DSP Resource cards and the CPU/System Controller Card.

• Chapter 3: Installation. Describes how to install the Tenor CMS unit, including how to connect, power up and assign the IP address.

• Chapter 4: Getting Started via Command Line Interface (CLI). This chapter tells you how to access the CLI and execute commands. A description of each CLI mode is also included.

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

• Chapter 6: Call Detail Recording. Describes the Call Detail Recording (CDR) feature, including how to set up the CDR server and assign a password. In addition, instructions for reading CDR outpu t is also included.

• Chapter 7: System Alarms. Describes how to monitor and view alarms via Command Line Interface (CLI).

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

• Chapter 9: Using IVR. Describes the Interactive Voice Response (IVR) system for support of pre-paid and post-paid calls.

• Appendix A: Getting Acquainted with Tenor CMS in the VoIP Network. A general overview of VoIP and how it relates to the Tenor CMS switch.

• Appendix B: Specifications/Approvals: A list of Tenor CMS’s specifications and approvals.

•Glossary

•Index

• Warranty

2 P/N 480-0005-00-15

Typographical Conventions

Product Guide Conventions

Certain typographical conventions are used throughout this product guide. See below.

• All commands you enter via keystrokes appear in bold (e.g., Press Enter or Press Ctrl-I).

• All text commands you enter via Telnet session or command line typing appear in italics (e.g., type active).

• There are three types of special text that are designed to reveal supplemental information: Note, Warning, and Caution. See below.

A NOTE provides additional, helpful information. This information may tell you how to do a certain task or just be a reminder for how-to’s given in previous sections. (i.e., For a list of valid commands at any time, type ?)

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

About this Guide

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-0005-00-15 Preface-3

About this Guide

Finding Help

Refer to the Product Guide for help. The Table of Contents and Index tells you where to find information easily; the glossary defines specific terms. See Appendix A: Getting Acquainted with Tenor CMS in the VoIP Net- work for detailed information about VoIP terms and concepts.

Extensive configuration help is available via the Command Line Interface help system. Just type help or ? from any prompt to obtain help. See Chapter 4: Getting Started with Command Line Interface (CLI) for more information.

4 P/N 480-0005-00-15

Chapter 1: Overview

This chapter gives you a general overview of the Tenor® Carrier MultiPath Switch (CMS), including feature descriptions and capabilities. You will also find information about the organization of this product guide.

Specifically, the following topics are covered:

! A description of Tenor CMS

! Typical implementations

! Features and capabilities

P/N 480-0005-00-15 1-1

Chapter 1: Overview

What is Tenor CMS?

The Tenor Carrier MultiPath Switch (CMS) is a high-density VoIP (Voice over Internet Protocol) H.323 switch that digitizes voice and fax data and transmits it over th e IP network. Tenor CMS is available in three configurations: CMS (14 slot), CMS960 (8 slot), and CMS240 (2 slot); each is a slotted, scalable system that intelligently switches calls over both the IP network and the PSTN in order to ensure high quality voice. Tenor CMS functions as a gateway, gatekeeper, and a border element. The gateway converts circuit switched calls to VoIP calls, the gatekeeper performs IP call routing functions, and the border element distributes the call routing directories throughout the network.

Each Tenor CMS is available with either AC or DC input power.

NOTE: Figure 1-1 illustrates Tenor units with AC power.

Figure 1-1 Tenor CMS VoIP Switch

StatusAlarm

StatusAl arm

CPU PCI

CPU

PCI

BankDSP 1

TX/RXLink

10/100

Ethernet

Reset

UINTUM

TECHNOLOGIES,

INC.

Span

Status

LinkTX/RX

10/100

Ethernet

TM TM

Ground Strap

CPU

DS1

Hot Swap

Reset +3.3V +5V +12V - 12V

UINTUM

ECHNOLOGIES, INC.

Fault Fault

Hot Swap

DS1

Hot Swap

DS1

Hot Swap

DS1

Hot Swap

DS1

Hot Swap

CPU

483726

Status

483726

Status

483726

Status

483726

Status

483726

Ethernet

10/100

QUINTUM

TECHNOLOGIES, INC.

Span

TECHNOLOGIES, INC.

QUINTUM

Span

QUINTUM

TECHNOLOGIES, INC.

Span

QUINTUM

TECHNOLOGIES, INC.

Span

QUINTUM

TECHNOLOGIES, INC.

Link TX/RX

112

Link

Ethernet

DSP

10/100

TX/RX

Bank

112

Link

Ethern et

DSP

10/100

TX/RX

Bank

112

Link

Ethernet

DSP

10/100

TX/RX

Bank

112

Link

Ethernet

DSP

10/100

TX/RX

Bank

Reset

CMS960 (8 Slot)

CPU

PCI

CPU

PCI

CPU

PCI

CPU

PCI

CPU

PCI

Alarm

Status

Alarm

Stat us

Alarm

Stat us

Alarm

Status

A.C. P ow er Suppl y

Alarm

Status

A.C. P ow er Suppl y

QUINTUM

TECHNOL O GIES, INC.

QUINTUM

TECHNOL O GIES, INC.

Power

QUINTUM

TECHNOL O GIES, INC.

Power

QUINTUM

TECHNOL O GIES, INC.

Power

CMS (14 Slot)

Hot Sw ap

Hot Swap

DS1

Ethern et

CPU

Statu s

Span

483726

Link TX/RX

10/100

QUINTUM

TECHNOLOGIES, INC.

112

Link

Ethernet

10/100

Reset

Alarm

DSP

CPU

TX/RX

Bank

Status

PCI

Alarm

CPU

Statu s

PCI

QUINTU M

TECHNOLOGIES, I NC.

Power

A.C. Power Supply

QUINTU M

TECHNOLOGIES, INC.

483726

CMS240 (2 Slot)

The slotted system architecture boasts peripheral cards, which interface to various Wide Area Networks (WANs). Tenor CMS connects to T1/E1 lines operating in either a trunk circuit or line circuit configuration. The individual spans within the Tenor CMS may connect to either the PSTN or to T1/E1 termination equipment on the user premises (i.e., PBX).

The high performance System Controller/CPU card provides up to four 10/100BaseT connections and one RS-232 serial port connection; this card is an intelligent call routing engine which regulates system resources and configuration while coordinating all voice traffic activity in the unit. The DS1, T1, and E1 cards provide connections. The DS1 card also provides DSP processing (DSP is a signal processing resource; it performs

1-2 P/N 480-0005-00-15

Chapter 1: Overview

functions such as voice packet generation and multiplexing). You can also use an individual DSP card for this purpose.

Tenor CMS is managed by a unique Comman d Li ne Interface (CLI) management system. Through the CLI, you can configure remote and local units. Just log on and configure items like chassis information, trunk groups, signaling data, etc. In addition, you can assign specific numbers to be routed over the PSTN, rather than IP. The CLI also provides a comprehensive on-line help system at your fingertips.

Quality of service is virtually guaranteed. SelectNet the IP network performance for VoIP calls. If the performance characteristics become 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 telephony infrastructure. Your network stays as is and the call type is transparent to the user. This technology boasts quality voice without compromising reliability.

™ T echnology provides a “safety net,” which monitors

Features

The Tenor CMS’s specific features are explained below.

Unique Design

T enor CMS is a compact PCI chassis that supports the transmission of Vo IP traffic via Ethernet connections. It packs powerful VoIP features into one rack-mountable, slotted unit. In addition, the unit includes design features such as load sharing power supplies and peripheral cards; the chassis is available in AC or DC power.

A high performance backplane supports two types of chassis-side busses: TDM and packet. TDM supports 2048 full duplex channels; it is used for transporting circuit switched traffic. The packet bus is used for carrying packet-oriented data.

The slotted system architecture enables you to set the VoIP capabilities to suit your network’s needs; it is available in three configurations: CMS (14 slot), CMS960 (8 slot), and CMS240 (2 slot) Through WAN interface cards and DSP resources, you configure the number of VoIP channels your network requires.

State-of-the-Art Configuration and Network Management

A System Controller/CPU card controls all activity in the chassis; it passes all configuration information you set via CLI to the other peripheral cards (T1, E1, DS1) and DSP resources. In addition, the DS1 card enables you to employ T1, E1, and DSP functionality in the same card. Through the System Controller/CPU card, you can connect a PC’s console port as well as an Ethernet hub, switch, or router. In addition, the System Controller/CPU card provides one 10/100BaseT Ethernet port.

Once connected, the robust Command Line Interface (CLI) makes configuring a Tenor CMS easy. Through the CLI, you are able to set all configuration parameters, such as chassis, signaling, and call type features. You access the CLI through a simple telnet session. The state-of-the-art online help system, built into the CLI, provides help for all features and functionality. Just type help at any prompt, and data about that field will be displayed.

SelectNet™ Technology Safety Net

T enor CMS’ s built in SelectNet™ Technology safety net feature virtually guarantees that each call going VoIP will not only be routed successfully, but will deliver high voice quality.

P/N 480-0005-00-15 1-3

Chapter 1: Overview

If the network conditions for an IP call become unacceptable—according to the delay and packet loss specifications you configure—Tenor CMS will switch the call to the PSTN automatically and transparently. The T enor CMS continuously monitors your data network for jitter, latency and packet loss, and transparently switches customer calls to the PSTN when required.

Dynamic Call Routing

Tenor CMS’s intelligent call routing capabilities are state-of-the-art. The chassis automatically detects and supports two call types: voice and fax.

Tenor CMS will first identify the call origination site —trunk circuit, line circuit, or IP routing group —and then route the call according to any parameters you configure in the routing database. Each call may be routed via circuit switched path between any two circuit groups, or compressed and transported via VoIP when connecting to an IP routing group. Trunk circuits are those that typically connect to another circuit switched network such as the PSTN. Line circuits typically connect to a termination device on the user premises, such as a PBX.

Multiple Channels/Signaling Supported

Any combination of DS1, or T1 and E1 cards (up to 4) may be used to achieve up to 960 channels. The T enor CMS provides support for most Channel Associated Signaling (CAS) and ISDN protocols.

Fractional T1/E1 Support

Tenor CMS supports Fractional T1/E1.

1-4 P/N 480-0005-00-15

Chapter 1: Overview

PacketSaver™

PacketSaver packet multiplexing technology reduces the amount of IP bandwidth required to support multiple calls flowing between two endpoints. PacketSaver minimizes bandwidth usage by aggregating samp les from multiple VoIP conversations and packing them into a larger IP packet with a single IP header. The process removes the need to send a bulky IP header with individual voice packets. As a result, it eliminates the transmission of redundant information.

Conventional V oIP Transmission Sends Many Redundant Packet Headers

Tenor CMS

Tenor using PacketSaver to Minimize Bandwidth Usage

Tenor CMS

IVR/RADIUS support

Interactive Voice Response (IVR) is a feature of the Tenor CMS that enables you to offer services, such as Prepaid calling cards and Post-paid accounts, to your customers.

The Tenor CMS uses the RADIUS (Remote Authentication Dial-In User Service), for authenticating and authorizing user access to the VoIP network, including ANI Authentication (T ypes 1 and 2). The RADIUS is a standard protocol which 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. As a result, the RADIUS enables the Tenor CMS 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.

Easy Connect to Console

Plugging a serial cable (for CPU) or null modem cable (for System Controller) between the System Controller/CPU card’s asynchronous RS-232 port and a serial port of your PC, will allow local chassis management. Through the console connection, you are able to assign an IP address. In addition, if you are directly connected to the chassis, you are able to configure that chassis via Command Line Interface (CLI).

H.323 Gatekeeper Call Control Management

The Tenor CMS chassis’s built-in H.323 gatekeeper performs IP call routing functions, such as call control and administrative services to another Tenor CMS unit, or another H.323 endpoint. The gatekeeper’s functionality complies with the H.323 industry specifications for voice control and management. See H.323 Gate- keeper Services, later in this chapter, for more information.

P/N 480-0005-00-15 1-5

Chapter 1: Overview

Powerful System Monitoring

There are many different ways to monitor the health of the unit, including LEDs and alarms. LEDs appear on the front of the unit (for CMS -14 slot) and the front of WAN interface cards, as well as on the DSP cards, and the System Controller/CPU card. The LEDs light up according to operations and alarms the system is experiencing. Through the Command Line Interface (CLI) management system, you can view a list of active system alarms, as well as view an alarm history. Each alarm indicates the chassis’s operational status. Tenor CMS is also SNMP-capable with HP® Openview™ support.

1-6 P/N 480-0005-00-15

Chapter 1: Overview

Capabilities

The T enor CMS’ s specific capabilities are explained below . For illustration purposes, the Tenor CMS (14 slot) is pictured.

Line Circuit Originated Calls

Calls coming from a Line Circuit may be switched to either the data network as a VoIP call or to a Trunk Circuit typically for connection to another circuit switched network such as the PSTN. The routing decision made by the Tenor CMS is based upon your con fig uration and the dialed number.

Figure 1-2 Line Circuit Call Routing

PBX

Line

Circuits

Circuit

Call

Ground Strap

TM TM

Tenor CMS

CPU

Ethernet

TECHNOLOGIES,

Hot Swap

StatusAlarm

PCI

BankDSP

TX/RXLink

10/100

UINTUM

INC.

Span Status

DS1

StatusAlarm

CPUPCI

Reset

UINTUM

TECHNOLOGIES,

INC.

LinkTX/RX 1 2 3

10/100 Ethernet

CPU

Hot Swap

Reset +3.3V +5V + 12V -12V

Trunk

Circuits

UINTUM

ECHNOLOGIES, INC.

Trunk

Circuits

PSTN A

Circuit

Call

PSTN B

Fault Fault

Ethernet

(IP Network)

VOIP Call

Ethernet

P/N 480-0005-00-15 1-7

Chapter 1: Overview

Trunk Circuit Originated Calls

A call coming from a Trunk Circuit may be switched to either the data network as a VoIP call, a Line Circuit, or trunk typically for connection to a termination device on the users premises such as a PBX. The routing decision made by the Tenor CMS is based upon your configuration and the dialed number.

Figure 1-3 Trunk Circuit Call Routing

PSTN A

Circuit

Call

VOIP Call

PSTN B

PBX

Line

Circuits

Circuit

Call

Ground Strap

TM TM

Tenor CMS

CPU

TECHNOLOGIES,

Hot Swap

StatusAlarm

PCI

BankDSP

TX/RXLink

10/100 Ethernet

UINTUM

INC.

Span Status

DS1

StatusAlarm

CPUPCI

Reset

UINTUM

TECHNOLOGIES,

INC.

LinkTX/RX 1 2 3

10/100 Ethernet

CPU

Hot Swap

Reset +3.3V +5V + 12V -12V

Trunk

Circuits

UINTUM

ECHNOLOGIES, INC.

Fault Fault

Circuits

Ethernet

(IP Network)

Trunk

Ethernet

Intra-trunk Routing - “Hairpinning”

As a result of intra-trunk routing, incoming calls from a particular Trunk Circuit are switched by Tenor CMS to be routed back out the same trunk circuit routing group.

Figure 1-4 Intra-Trunk Routing

PSTN A

Circuit

Call

VOIP Call

PSTN B

PBX

Line

Circuits

Circuit

Call

Ground Strap

TM TM

Tenor CMS

10/100 Ethernet

UINTUM

TECHNOLOGIES,

Span Status

DS1

Hot Swap

StatusAlarm

PCICPU

BankDSP

TX/RXLink

INC.

StatusAlarm

CPU PCI

Reset

UINTUM

TECHNOLOGIES, INC.

LinkTX/RX 1

2 3

10/100 Ethernet

CPU

Hot Swap

Reset +3.3V +5V +12V -12V

Trunk

Circuits

Trunk

UINTUM

ECHNOLOGIES, INC.

Fault Fault

Circuits

Ethernet

(IP Network)

Ethernet

1-8 P/N 480-0005-00-15

Chapter 1: Overview

Data Network Calls

Calls coming from the data network can be routed to the Line circuit or Trunk circuit spans. The Tenor CMS will route calls based upon the dialed number. If the number is configured as a local phone number, the call will be sent to a Line circuit for termination, otherwise the call is considered a “Hop-Off call” and the Tenor CMS sends it out through a Trunk circuit span, typically connected to the PSTN.

Figure 1-5 Data Network Call Routing

PSTN A

Circuit

Call

VOIP Call

PSTN B

PBX

Line

Circuits

Circuit

Call

Ground Strap

TM TM

Tenor CMS

TECHNOLOGIES,

CPU

BankDSP

TX/RXLink

10/100 Ethernet

UINTUM

INC.

Span Status

DS1

Hot Swap

StatusAlarm

CPU PCI

PCI

Reset

UINTUM

TECHNOLOGIES,

INC.

LinkTX/RX

1 2

10/100

Ethernet

CPU

Hot Swap

Reset +3.3V +5V +12V -12V

Trunk

Circuits

Ethernet

Trunk

Circuits

UINTUM

ECHNOLOGIES, INC.

Fault Fault

(IP Network)

Ethernet

Other Call Routing Options

There are several routing tables you can configure via the Command Line Interface (CLI) to adjust how the Tenor CMS unit routes specific calls. For example, you may want to configure 911 as a “bypass number”, which means that all 911 calls coming into Tenor CMS from the line circuit will be routed directly to a Trunk circuit presumably connected to a PSTN. Bypass calls are never routed over IP.

There are four types of routing databases you can configure: Bypass Directory Numbers (BPN), Local Directory Numbers (LDN), Hop-Off Directory Numbers (HDN) and Static Route. Bypass Directory Numbers are directly routed from a Line circuit to a Trunk circuit. Local Directory Numbers are phone numbers that are reachable through local Line Circuits. Hop-Off Directory Numbers are phone numbers that can be routed over the IP to another Tenor location and then out to the Trunk circuit, possibly to the PSTN as a local call. Static Routes are used between networks and other H.323 devices that are not registered to the network through the Border Element (such as non-Quintum gateways).

Virtual Tie Line

Tenor CMS can emulate a tie trunk. It provides all of the functionality of a tie trunk, including the considerable cost savings, but eliminates the need for a PBX trunk to be configured, or marked as a tie trunk. A traditional tie trunk is a PBX-configured direct connection between two PBXs in separate locations. The tie trunk bypasses the PSTN network.

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

P/N 480-0005-00-15 1-9

Chapter 1: Overview

Hop-off PBX Call

Hop-off numbers are phone number patterns for calls to be routed out trunks. They are entered in a HopoffNumberDirectory and associated with TrunkCircuitRoutingGroups that govern the trunks where matching calls should be sent.

Tenor CMS supports those Hop-off PBX calls where the destination Tenor CMS is programmed to route the call to the PSTN via Trunk Circuit. (A Hop-off PBX call is a toll call which hops through a private network to reduce or eliminate the toll charge.) The destination Tenor CMS unit is configured with the phone numbers to be “supported” for this feature.

SNMP Support

The Tenor CMS unit supports Simp le Network Management Protocol (SNMP), the standard protocol used to exchange network information between different types of networks. The Tenor CMS unit acts as an SNMP agent—using HP Openview—to receive commands and issue responses to the network manager . The network manager will then be able to perform certain functions, such as receiving traps from Tenor CMS.

Call Detail Recording

Through the Call Detail Record (CDR) feature, the Tenor CMS may generate a call record at the completion of each call, typically for accounting purposes. A CDR is a string of data that contains call information such as call date and time, call duration, calling party, and called party. Tenor CMS may store call detail records locally or they can be sent to a CDR server within the network. The CDR contains sufficient information to capture billing data, which can be used to create billing reports by third party billing software.

1-10 P/N 480-0005-00-15

Chapter 1: Overview

H.323 Gatekeeper Services

Gatekeeper

A Gatekeeper in an H.323 network provides call control services and other services to H.323 endpoints (i.e., gateways, terminals, and MCUs). The Tenor CMS has a built-in H.323 gatekeeper which complies to the H.323 industry specifications for voice control and management. The gatekeeper performs call routing functions for calls entering and exiting a site.

The Gatekeeper performs IP call routing functions, such as call control signaling and call authorization for Gateways, IP phones, and H.323 terminals. The Gatekeeper communicates with other Gatekeepers through a Border Element. When using a group of Tenor CMS units, you can assign one unit as the Gatekeeper for the network. We recommend you configure each CMS as its own gatekeeper.

Tenor CMS supports gatekeeper to gatekeeper communication using LRQ (Location Request) messaging scheme.

Zone Management

A zone is a group of H.323 defined endpoints controlled by a Gatekeeper. Endpoints can be gateways (i.e., Tenor CMS), terminals, and/or multipoint conferencing units (MCU s). Endpoints establish control channels with a gatekeeper for registration, admission, security, and call routing information about the endpoint is sent to the gatekeeper, including: IP address, unit type (gateway, terminal, or MCU) and routing information (such as phone numbers, number patterns, etc.).

A collection of zones is an administrative domain. An administrative domain provides call routing services for its zones through gatekeeper to gatekeeper messages or gatekeeper to border element messages (see Border Element” for more information).

Call Registration

H.323 endpoints in the same zone register with the designated gatekeeper. When registration is complete and a call is originated, the call request is sent to the gatekeeper. The call request provides the Gatekeeper with the dialed number and requests the routing information. The gatekeeper confirms the dialed number and supplies the endpoint with the destination IP address. For example, a Tenor CMS’s gatekeeper will act as the gatekeeper for that zone and all of the other endpoints will register with it.

Border Element

The T enor CMS’ s gatekeeper uses a border element to gain access to the routing database of the administrative domain for the purpose of call completion or any other services that involve communications with other endpoints out of the administrative domain. The border element functionality is built into the Tenor CMS unit, along with the gateway and gatekeeper.

The primary function of the border element is to collect, manage, and distribute call routing information. A gatekeeper will establish a service relationship with a border element; the gatekeeper provides its zones capabilities and the border element shares call routing capabilities of other zones in the administrative domain. Through the border element, gatekeepers from multiple zones will be able to communicate.

A border element also establishes relationships with other border elements to route between administrative domains. If a gatekeeper cannot resolve an address, it contacts the border element.

P/N 480-0005-00-15 1-11

Chapter 1: Overview

In addition, if you are using more than one CMS unit, you can configure one of the border elements for that zone. The T enor CMS unit provides two border elements: primary and secondary. These work together as one entity to provide redundancy and fault tolerance; there are no hierarchical differences.

Gatekeeper

Zone

Gatekeeper

Zone

Gatekeeper

Zone

Administrative Domain

Border Element

Administrative Domain

Gatekeeper

Zone

Gatekeeper

Zone

Gatekeeper

Zone

Call Services

Gatekeepers provide services such as addressing, authorization and authentication of terminals and gateways, bandwidth management, accounting, billing, and charging. Gatekeepers also provide call-routing services. Specifically, the Tenor CMS Gatekeeper provides the functions which follow:

Address Translation. The gatekeeper translates telephone numbers into IP addresses and vice versa. It performs Alias Address (phone number) to Transport Address (IP address) translation when an endpoint requests service. The Gatekeeper uses a translation table to translate an Alias Address (an address such as an H.323 identifier that a user may not understand) to a transport address. The translation table is updated using Registration messages.

Autodiscovery. The gatekeeper is discovered in one of the following ways: An endpoint sends an IP broadcast called a Gatekeeper Request message (GRQ) message (which includes that correct gatekeeper name) to discover a Gatekeeper OR the endpoint will discover a gatekeeper by its IP address.

Routing. The gatekeeper identifies the IP address of endpoints in its administrative domain. The gatekeeper builds a routing database from information obtained from the border element and also from gateways and H.323 endpoints.

Admissions Control. All H.323 endpoints must register and request permission to enter the gatekeeper’s zone; the gatekeeper will confirm or deny access to the network. The gatekeeper authorizes network access and protects the integrity of the network using Admissions Request (ARQ), Admissions Confirmation (ACF) and Admissions Reject (ARJ) messages.

Configuration

For the Gatekeeper/Border Element functionality, the following items are configurable via Command Line Interface (CLI):

• Primary Border Element IP Address. The IP address for the administrative domain’s Border Element

(the Border Element is internal to the Tenor CMS unit; it is used to establish relationships with other

P/N 480-0005-00-15 1-12

Chapter 1: Overview

T enor CMS units in other companies). There is generally only one Primary Border Element in each organization.

• Secondary Border Element IP Address. The IP address for the alternate border element (the IP address

the Tenor CMS uses as a Border Element) is in the administrative zone. There is generally only one secondary Border Element in each organization.

• Discovery IP Address. The IP address a T enor CMS uses to communicate with a Gatekeeper for service.

• Discovery Port. The H.323 standard port a Tenor CMS uses to discover a Gatekeeper.

• Registration Port. The H.323 standard port a Tenor CMS uses to register itself with a Gatekeeper.

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

Chapter 2: Hardware Components

This chapter tells you what is contained in your hardware package. A description of each component is also included.

Specifically, the following topics are covered:

! Chassis

! Power Supplies

! WAN Cards

! Cables

P/N 480-0005-00-15 2-1

Chapter 2: Hardware Components

Hardware Description

Tenor CMS is available in CMS (14 slot), CMS960 (8 slot), and a CMS240 (2 slot).

The CMS (14 slot), CMS960 (8 slot), and CMS240 (2 slot) provide network connection and functionali ty through WAN cards, DSP resource cards, and a system controller card/CPU card. Communication through the chassis backplane is achieved through the following: packet bus and TDM bus. The packet bus is used for carrying packet-oriented data and the TDM bus is used for transporting circuit switched PCM traffic.

For the AC unit, the front side of the chassis provides access to WAN cards (T1/E1/DS1), power supplies, the system controller card/CPU card, and DSP card; the rear side exposes the back portion of the transition cards for network connection as well as power cord connection.

For the DC unit, the front side of the chassis provides access to WAN cards (T1/E1/DS1), DSP cards, the system controller/CPU card and power supplies. The rear side exposes the back portion of the transition cards for network connections, as well as the circuit breakers, power receptacles and power plugs.

Through all of these units, you can connect up to four different points: Line Circuit (PBX), Trunk Circuit (PSTN), Data network (Ethernet LAN) and a PC.

Board interoperability

Certain boards are supported in certain releases; the chart which follows lists which boards are supported according to CMS release.

Table 2-1 Board supported according to CMS Release

Board Type

T1 Card Yes Yes Yes No Yes E1 Card Yes Yes Yes No Yes DS1 Card (with DSP

module) DSP Card Yes No Yes N o No System Controller Card Yes Yes Yes No No CPU Card No No No Yes Yes

Release

P1.3.x

No Yes Yes Yes Yes

Release

P1.4.x and

higher

Release

P1.5.x

Release

P2.4.x

Release

P2.5.x

2-2 P/N 480-0005-00-15

Chapter 2: Hardware Components

Chassis - CMS (14 Slot)

The chassis is the 19” rack-mountable unit which houses all WAN cards, System Controller/CPU cards, DSP cards, and power supplies. The two system fans are installed at the top of the chassis. See the following sections for unit front and unit back details; both the AC version and DC versions are illustrated and explained.

Front (with AC power)

NOTE: For pictorial purposes, Figure 2-1 shows the unit with 1 DS1 card and the CPU card.

Figure 2-1 Tenor CMS Front View - AC unit

System Fans

WAN Card Slots

StatusAlarm

StatusAlar m

CPU PCI

CPU

PCI

BankDSP 1

TX/RXLink

10/100

Ground Strap Socket

Ground

Strap

Air Inlet

TM TM

Reset Button

Ethernet

Reset

UINTUM

TECHNOLOGIES ,

TECHNOLOGIES,

INC.

Span

Status

Link TX/RX

10/100

Ethernet

CPU

DS1

Hot Swap

Reset +3.3V +5V +12V -12V

QUINTUM

ECHNOLOGIES , INC.

ECHNOLOGIES, INC.

Faul t Faul t

Chassis LEDs

On/Off Power

• Card Slots. Fourteen slots are available for WAN cards, DSP Resource Cards, DS1 cards, and the CPU/

System Controller Card.

Power Supplies

Air Filter

• Power Supplies. Two load-sharing AC power supplies. The load sharing feature enables one power sup-

ply to take over if the other fails.

• System Fans. Two system fans, accessible through a swing down panel via thumb screws are used to

cool the chassis. These fans are “hot-swappable”, meaning you can remove/replace the fans while the unit is operational.

• Reset Button. Enables you to reset the system. This function will be supported in a future release.

• Ground Strap Socket. A ground connection is provided for ESD protection.

P/N 480-0005-00-15 2-3

Chapter 2: Hardware Components

• Air Filter. The Air Filter is accessible by opening the lower front panel. You do not have to turn off the

chassis. For cleaning, see Chapter 8: Diagnostics/Maintenance.

• Chassis LEDs. The LEDs are indicators as to the status of the four DC outputs of the power supplies.

When these are lit, they indicate the respective voltages are being output from the power supplies. When unlit, the voltage is not being supplied. See Chapter 8: Diagnostics/Maintenance for more information.

• On/Off Power: A switch to turn power on and off.

Rear (with AC power)

NOTE: For pictorial purposes, Figure 2-2 is shown with 2 DS1 cards and the CPU Card.

Figure 2-2 Tenor CMS Rear View - AC unit

Link T X/RX

10/100

Ethernet

Console

Air Exhaust

WAN Card Slots

Power Inlet

• WAN Card Slots. The rear of the T1, E1, or DS1 W AN cards (the transition modules), is used for net-

• Power Inlet. Inlet for which you insert the supplied AC power cord. The unit requires a 110-240 VAC.

• Earth Ground Stud. A Ground Stud is provided to connect to earth ground.

• Ground St rap Port. A ground connection is provided for ESD protection.

10/100

Ethernet

Link TX/RX

Off On

1 2 3 4

Config

Link TX/RX

CPU

DS1

10 A M

100-240VAC

50-60Hz

Earth Ground Stud

Label

Ground Strap Port

work connection. The quantity will vary depending upon the number of WAN cards you have inserted.

2-4 P/N 480-0005-00-15

Chapter 2: Hardware Components

Front (with DC Power)

NOTE: For pictorial purposes, Figure 2-3 shows the unit with 1 DS1 card and the CPU card.

Figure 2-3 Tenor CMS Front View - DC unit

System Fans

Card Slots

Ground Strap Socket

Ground

Strap

Air Inlet

TM TM

Reset

Button

StatusAlarm

CPU PCI

CPU

PCI

BankDSP 1

TX/RXLink

10/100

Ethernet

Reset

QUINTUM

TECHNOLOGIES ,

INC.

Span

Status

Link TX/RX

10/100

Ethernet

CPU

DS1

Hot Swap

Reset +3.3V +5V +12V -12V

QUINTUM

ECHNOLOGIES, INC.

Fault Fa ult

Chassis LEDs

Power Supplies

Air Filter

• Card Slots. Fourteen slots are available for WAN cards (T1/E1/DS1), DSP cards, and the CPU/System

Controller card.

• Power Supplies. Two load-sharing DC power supplies. The load sharing feature enables one power sup-

ply to take over if the other fails.

• System Fans. Two system fans, accessible through a swing down panel via thumb screws, are used to

cool the chassis. These fans are “hot-swappable”, meaning you can remove/replace the fans while the unit is operational.

• Reset Button. Enables you to reset the system. This function will be supported in a future release.

• Ground Strap Socket. A ground connection is provided for ESD protection.

• Air Filter. The Air Filter is accessible by opening the lower front panel. You do not have to turn off the

chassis. For cleaning, see Chapter 8: Diagnostics/Maintenance.

• Chassis LEDs. The LEDs are indicators as to the status of the four voltage supplies. When these are lit,

they indicate the respective voltages are being output from the power supplies. When unlit, the voltage is not being supplied. See Chapter 8: Diagnostics/Maintenance for more information.

P/N 480-0005-00-15 2-5

Chapter 2: Hardware Components

Rear (with DC power)

NOTE: For pictorial purposes, Figure 2-4 is shown with 1 DS1 card and the CPU card.

Figure 2-4 Tenor CMS Rear View - DC unit

Link TX/RX

Card Slots

10/100

Ethernet

Console

Air Exhaust

10/100 Ethernet

Link TX/RX

Off On

1 2 3 4

Config

Link TX/RX

Earth Ground Terminal

CPU

DS1

-48 |RTN|

Off On 0 1

-48 |RTN|-48 |RTN|

-48 |RTN|

ESD Socket

Power Receptacle

Power Plug

Power Receptacle

Circuit Breaker

• Card Slots. The rear of the cards requiring a transition module (T1, E1, DS1, CPU) is used for network

connection. The quantity will vary depending upon the number of cards you have inserted.

• Power Plug. Provides wire connections to the -42 to -60 VDC power from the DC feed(s) to the power

receptacles. Both may be used, but only one is required (one must have the power connected to its power inlet connector).

• Power Receptacle. Power inlet receives DC power from the power plug.

• Circuit Breaker. There is one circuit breaker for each power connection; an arrow from each one indi-

cates which breaker controls which power receptacle connection. The top circuit breaker controls the left power receptacle; the bottom circuit breaker controls the right power receptacle. When you push the rocker to ON, the breaker will be closed (a red indicator shows the user that the contacts are closed). When you push the rocker to OFF, the contacts will open. Both circuit breakers must always be open, even if only one power source is connected to the chassis, to ensure all power is disconnected from the power supplies.

• Earth Ground Terminal An earth ground terminal is provided to connect to a supplemental earth

ground.

• ESD Socket. A ground connection is provided for ESD protection.

2-6 P/N 480-0005-00-15

+ 155 hidden pages