series 5100/6100 voice/data router -...

Series 5100/6100™

Voice/Data Router

Reference ManualSIP Telephony

Trademarks and copyrightsAll trademarks and registered trademarks listed belong to their respective owners.

Vpacket, Vpacket Communications, and the Vpacket 5100/6100 Series Voice/Data Router are registered trademarks of Vpacket Communications, Inc., Milpitas, California.

Vpacket Communications, Inc. does not warrant that the hardware will work properly in all environments and applications, and makes no warranty and representation, either implied or expressed, with respect to the quality, performance, merchantability, or fitness for a particular purpose.

The products and programs described in this document are licensed products of Vpacket Communications, Inc. This document contains proprietary information protected by copyright, and this document and all accompanying hardware, software, and documentation are copyrighted. Vpacket Communications, Inc. has made every effort to ensure that this manual is accurate. However, information in this guide is subject to change without notice and does not represent a commitment on the part of Vpacket Communications, Inc. Vpacket Communications, Inc. makes no commitment to update or keep current the information in this document, and reserves the right to make changes to this manual and/or product without notice. Vpacket Communications, Inc. assumes no responsibility for any inaccuracies and omissions that may be contained in this document. If you find information in this document that is incorrect, misleading, or incomplete, we would appreciate your comments and suggestions.

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the purchaser's personal use, without the express written permission of Vpacket Communications, Inc.

Copyright © 2000-2002 by Vpacket Communications, Inc.™ U.S. Patents Pending. All Rights Reserved. Reproduction or media conversion by any means is protected by copyright and may only occur with prior written permission of Vpacket Communications, Inc.

The PSQM technology included in this product is protected by copyright and by European, US, and other patents, and is provided under license from OPTICOM Dipl. Ing. M. Keyhl GmbH, Erlangen, Germany, 2001

1390 McCarthy BoulevardMilpitas, CA 95035

Tel: 1(866)VPACKET (872-2538)Fax: 1(408)433-5870E-mail: [email protected]: http://www.vpacket.com

Document title Date issued Product number Release

Vpacket Series 5100/6100 Voice/Data Router Reference ManualSIP Telephony

June 2002 750-0032-001, Rev A 2.1.1

Vpacket Series 5100/6100 Voice/Data Router Reference Manual MGCP Configuration

750-0031-001, Rev A

Vpacket 5100/6100 Series Voice/Data Router Reference Manual (Data Features)

750-0025-001, Rev A

Vpacket 5100/6100 Series Voice/Data Router H.323 Telephony Configuration

750-0033-001, Rev A

Vpacket 5100/6100 Series Voice/Data Router Web Interface Manual 750-0035-001, Rev A

About this manual

About this manual

ii Vpacket 5100/6100 Series SIP Telephony

Content summary

AudienceThis manual is written for the technical staff of a service provider, who are responsible for the configuration of a Vpacket 5100/6100 Voice/Data Router (VDR) that is running in a SIP environment. These users include, but are not limited to, network technicians, systems administrators, and network operation staff.

Content summaryThis manual contains all of the information you need to configure a 5100/6100 VDR with a digital T1 or FXS voice interface to run in a SIP environment. Table 1 lists the chapters and appendixes and a summary of each.

Table 1. Chapter summaries

Location Contents

Chapter 1 About SIP Describes SIP and the 5100/6100 VDR

Chapter 2 Configuring SIP for FXS and T1 Models

Describes the procedures to set up SIP with a VDR with a T1-CAS or FXS Voice interface

Chapter 3 Coding profile commands

Describes the coding profile commands that can be customized

Chapter 4 TCID commands Describes the TCID parameters that can be customized

Chapter 5 Configuring SIP with ISDN PRI

Describes the procedures to set up SIP to use ISDN PRI signaling

Chapter 6 Configuring ATPM Describes how to make a dial plan by using the ATPM

Chapter 7 Default Coding Profiles

Lists the default coding profiles that are available with the 5100/6100 VDR

Vpacket 5100/6100 Series SIP Telephony iii

About this manual

ConventionsThis manual uses typeface, syntax, and messages to alert you to information of special interest.

TypefacesTable 2 lists the typefaces that are used in this manual.

Command syntaxThe syntax of commands is described using the following conventions:• Angle brackets (<fill_in_the_blank >) denote required parameters or arguments.• Square brackets ([ ]) denote optional elements.• A pipe (|) separates choices.

MessagesNotes, cautions, and warnings are posted throughout the manuals to give supplementary information and encourage safety awareness and safe practices.

NotesNotes are supplemental information requiring your attention.For example:

Note. Please remember to go to the Vpacket Web site and complete the online Warranty Registration Card. Doing so registers your Vpacket 5100/6100 VDR and allows you to receive the latest information, technical support, and upgrades applicable to your unit.

Table 2. Typefaces and their meanings

Typeface Description

Bold Designates menus, commands, and parameters

Courier Designates output resulting from a command issued by a user and messages issued via a telnet or terminal-emulation screen

iv Vpacket 5100/6100 Series SIP Telephony

Related documentation

CautionsCautions are information requiring extra attention. For example:

Caution. No system-level confirmation message appears during the deletion.

WarningsWarnings are information that, if not followed, could result in injury or equipment damage. For example:

Warning. Use of longer screws could result in damage to internal components.

Related documentationThe documentation set related to the Vpacket 5100/6100 VDR includes all documents on the CD-ROM that was shipped with the unit:• Vpacket 5100/6100 Series Voice/Data Router Installer’s Guide, Release 2.1.1• Quick Start Guides

• T1 and dual T1 Quick Start Guide• SDSL Quick Start Guide• Ethernet WAN Quick Start Guide• T1-PRI Voice Quick Start Guide

• Vpacket 5100/6100 Series Voice/Data Router Datasheet

The reference manual is broken down into five sections allowing you to print only the sections that apply to your network environment:• Vpacket 5100/6100 Series Voice/Data Router Reference Manual (Data Features)• Vpacket 5100/6100 Series Voice/Data Router MGCP Telephony Configuration• Vpacket 5100/6100 Series Voice/Data Router SIP Telephony Configuration• Vpacket 5100/6100 Series Voice/Data Router H.323 Telephony Configuration• Vpacket 5100/6100 Series Voice/Data Router Web Interface Manual

!

WARNING

Vpacket 5100/6100 Series SIP Telephony v

About this manual

Contact informationFor more information about the Vpacket 5100/6100 Series VDRs, please contact us using any of the following methods.

Voice callsWe welcome your calls at 1(866) 872-2538 (VPACKET) Monday through Friday, from 9:00 am to 6:00 pm Pacific Time. Voice mail is available during non-business hours.

E-mailIf you prefer, you can send information requests to our e-mail address: [email protected]

Fax numberYou can also send your requests for information to our 24-hour fax number: 1(408) 433-5870

WebsiteOur website contains valuable information about our products. We encourage you to visit us at http://www.vpacket.com

vi Vpacket 5100/6100 Series SIP Telephony

Contents

About SIP 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Accessing SIP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Accessing the help feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Configuring SIP for FXS and T1 Models 5Defining the Caller ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Defining the SIP controller interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Defining the SIP RTP controller interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Assigning an ATPM destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

T1-CAS and SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10T1 voice interface commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Viewing the T1 configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Setting the T1 frame mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Setting the T1 line coding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Setting the T1 clock source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Setting the T1 loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Coding profile commands 15Coding profile command list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Assigning codecs to coding profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Setting the coding usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Setting the fax data rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Setting the fax packet rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Setting the packet-level redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Setting the high-speed redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Setting the fax transmission method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

TCID commands 23TCID commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Setting the TCID mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Setting the preferred voice coding profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Setting the preferred fax coding profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Vpacket 5100/6100 Series SIP Telephony vii

CONTENTS

Setting the companding law . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Setting the caller ID name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Setting the caller ID time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Setting the protocol type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Setting the FXS off hook level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Setting the on hook level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Setting the seize detect parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Setting the originator clear detect parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Setting the answer-side clear detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Configuring SIP with ISDN PRI 35PRI Signaling commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Configuring SIP with PRI signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configuring ATPM 45Viewing ATPM commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48ATPM Telephone Address to Hunting Group Table . . . . . . . . . . . . . . . . . . . . . . . . . . 49Hunt Group ID to Destination ID Mapping Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Destinations List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53ATPM System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56ATPM Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Managing the Flash Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Storing and Activating ATPM Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Generating an ATPM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configuring a dial plan for T1-CAS or FXS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59ISDN PRI script for generating a dial plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

viii Vpacket 5100/6100 Series SIP Telephony

About SIP
1
Contents
Overview, page 3
Accessing SIP commands, page 4Accessing the help feature, page 4

CHAPTER 1About SIP

2 Vpacket 5100/6100 Series SIP Telephony

Overview

OverviewSession Initiation Protocol (SIP) as implemented by Vpacket Communications is defined in RFC 2543. SIP is a signaling protocol that provides a mechanism for:• call establishment• call teardown• call control• other supplementary services in an IP network

There are two major architectural components within SIP: the SIP user agent (UA) and the SIP network server. The UA is the end system component responsible to initiate and answer calls. The SIP server is the network device that handles the signaling associated with multiple calls.The UA itself has a client element, the User Agent Client(UAC) and a server element, the User Agent Server (UAS). The client element initiates the calls and the server element answers the calls. This allows peer-to-peer calls to be made using a client-server protocol. The main function of the SIP server is to provide name resolution and user location, since the caller is unlikely to know the IP address or host name of the called party, and to pass on messages to other servers or SIP endpoints. Other functions performed by the SIP servers are redirecting, forking, and registration.Together these components make up a basic SIP infrastructure. Application servers can sit above these components delivering SIP supplementary services to end users. The 6100 VDR is implemented as a SIP UA and supports basic call only, supplementary services (eg. Call Hold, Call Transfer, Conference, etc.) are not supported. The 5100/6100 VDR UA communicates with other UAs and SIP proxy servers. The 5100/6100 VDR support UDP transport only for SIP. The following telephony interfaces on the 6100 VDR are supported:• ISDN PRI• T1 CAS• FXS Analog port

The SIP feature is supported on the software image file named s020101.bin.You can easily configure SIP from within the telephony command shell.This chapter contains the following information:• Accessing the telephony command shell• Accessing help• SIP commands

Chapter 2 explains how to use scripts to configure SIP for use with Channel Associated Signaling (CAS) or with FXS loop start. Chapter 3 explains how to use scripts to configure SIP for use with ISDN PRI signaling. You are required to completely set up the voice interface, save, and reset the 5100/6100 VDR before using the ATPM to generate a dial plan.

Vpacket 5100/6100 Series SIP Telephony 3

CHAPTER 1About SIP

Accessing SIP commandsSIP commands are available within the command line interface (CLI) under the telephony command shell. Once you establish connectivity to the 5100/6100 VDR either through a HyperTerminal session or a telnet session, you can access the telephony shell by entering tel and pressing the Enter key (Figure 1-1).

Figure 1-1. Entering the telephony command shellIn this example, the user exited the main CLI and entered the telephony command shell.

Accessing the help featureOnce inside the telephony command shell, you can view a listing of SIP commands by entering either the set or show keywords (Figure 1-2).

Figure 1-2. Viewing SIP helpIf you enter a two word combination, you can view the entire list of available commands within that group. The list contains both basic and advanced commands; so, it is possible to change parameters that might adversely affect a network. You can view ATPM commands by entering the telephony command shell and then entering the leyword: atpm.

VPacket# teltelephony#

VPacket# teltelephony# setset tcidset codingset ssmuOKtelephony# showShow Commands: show coding [prof_id] show tcid [tcid] show call_record [tcid] show dsp_version [dsp] show ssmu cfg show ssmu regOKtelephony#


Contents

2Configuring SIP forFXS and T1 Models

Overview, page 7Defining the Caller ID, page 7

Defining the SIP controller interface, page 7T1-CAS and SIP, page 10

CHAPTER 2Configuring SIP for FXS and T1 Models


Defining the Caller ID

OverviewLike other signaling protocols, SIP uses a combination of tcid, coding profile, and atpm commands. SIP-specific commands are ssmu commands. For SIP, you identify users at hosts by providing the following information: • a SIP URL or the user’s phone number (the phone number associated with each phone line) • the IP address of the 6100 VDR The SIP URL takes a form similar to a mailto or telnet URL, i.e. user@host <mailto:user@host>. A typical SIP address for one 6100 VDR line is like “[email protected]” or [email protected] <mailto:[email protected]> when you have a registered DNS name. Because a DNS register is not required for and does not affect SIP implementation, the rest of the examples use [email protected] <mailto:[email protected]> as SIP example addresses.

Defining the Caller IDBefore entering the SIP command to set up ATPM entries, you need to define the caller ID numbers. Phone numbers are defined by the CALLER ID of each TCID by issuing the set tcid cid number command.

Note. Vpacket also suggests that the user name display string in the caller id field by issuing the set tcid x cid name firstname_lastname command.

Defining the SIP controller interfaceA hostname is defined by setting the SIP controller interface. This is the name you will use to present to the public network. It is possible this name will not be the same name as your hostname. One example is when the 6100 VDR is inside a NATed network.

Note. The 6100 VDR is designed to use a hostname as SIP controller interface. The 6100 VDR cannot use an internal IP address because the 6100 VDR does not operate inside a firewall setup.

The first two commands provide for SIP functionality; however, you only need to make a change from the default settings if your particular softswitch requires a change. Usually the default settings are sufficient to support SIP. The ATPM command provides for fast lookup and hunting is a required command. The last section explains the requirement for VQM and VQS support for SIP.



Defining the SIP RTP controller interfaceYou can set up the address-related configuration by issuing the set ssmu cfg command. After making changes, you need to issue activate and then commit. A reset of the unit is required for the changes to be saved to the Flash. The RTP interface might not be the same as host interface address. If the RTP interface and the host interface address are the same, you can enter “0” Syntax: set ssmu cfg <udp_ctl_<nwa>> <rtp_data_<nwa>> Arguments:

<udp_ctl_<nwa>> Signaling control host interface address; 0 = default (ie. Use the VDR’s voice Interface IP address as defined in the “set ip voice” for this SIP host interface address; the system default port number of 5060 is used)

<rtp_data_<nwa>> RTP data address. 0 = default (sets the RTP interface to use the VDR’s voice interface IPaddress and use the system default port number of 2070).

<nwa> (0 | udp <x.x.x.x> <port#>) If <nwa> is 0, the UDP's default IP and port will be used for the address

Example 1:

In this example, the SIP controller interface is being set to 1.1.1.1 (port 1234), the RTP controller interface is being set to 2.2.2.2 (port 2080). You need to activate and commit the new configuration and then reset the unit for changes to take effect.Example 2:

In this example, the 6100 VDR SIP settings are returned to the defaults. You need to activate and commit the new configuration and then reset the unit for changes to take effect.

VPacket# tel

telephony# set ssmu cfg udp 1.1.1.1 1234 udp 2.2.2.2 2080

THE SSMU CONFIG NEEDS TO BE COMMITTED AND THE BOX

NEEDS TO BE REBOOTED FOR THE SSMU CONFIG TO TAKE EFFECT...

VPacket# tel

telephony# set ssmu cfg 0 0 0

THE SSMU CONFIG NEEDS TO BE COMMITTED AND THE BOX

NEEDS TO BE REBOOTED FOR THE SSMU CONFIG TO TAKE EFFECT...


Defining the SIP controller interface

Assigning an ATPM destination SIP uses the ATPM as the outgoing routing table. Defining a proxy server address is not a requirement, but assigning a ATPM destination is a requirement. You set an ATPM SIP destination address by issuing the atpm dadd id ssmu command. This command is used to add a SSMU mode destination to the destination table for routing of SIP calls. Syntax: atpm dadd <dest_id> ssmu udp <dest_SIP_URL> <port> <use_server_addr> Arguments:

<dest_id> Destination ID in the ATPM Destination List<dest_SIP_URL> Remote SIP URL address (user@host_ip), eg. SIP Server’s URL

or another SIP endpoint. Another format of this address is +&@host_ip which means that the phone number is used as the user name.

<port> Port number of remote SIP URL. Default is 5060<use_server_addr> 1 = use SIP server’s IP address in the “From” header field of

the SIP messages (required to interoperate with the CommWorks SIP server). Default: VDR’s IP address

Example:

In this example, the ATPM database is accessed, the destination address +&@192.168.5.111 is entered, then the entry is saved.

VPacket# tel

telephony# atpm dadd 1 ssmu udp +&@192.168.5.111

NMM: ATPM not in Database update state. Use

"atpm req" (database update request)

telephony# atpm req

01/21/2002 20:14:07 - [3] NMM: ATPM Update Database Granted

OK

telephony# atpm dadd 1 ssmu udp +&@192.168.5.111

OK

telephony# atpm done

01/21/2002 20:15:16 - [3] NMM: ATPM Update database done

OK

telephony# atpm store

OK



T1-CAS and SIPYou need to set up the digital T1 voice interface port. From within the telephony shell, you can access the T1 commands necessary for configuring digital voice over a T1 port with channel associated signaling (CAS) or primary rate interface (PRI) signaling.

Note. If, after customizing the T1 configuration, you use the flashclean command, all T1 settings will return to the default settings.

For 5100/6100 VDR models with a digital T1 voice port, the following parameters must be set prior to use:• frame mode• linecoding• clock source• loopback source

T1 voice interface commandsTable 2-1 lists the T1 voice interface commands found within this chapter.

From within the telephony shell, you can access the T1 commands necessary for configuring digital voice over a T1 port with channel associated signaling.

Note. If, after customizing the T1 configuration, you use the flashclean command, all T1 settings will return to the default settings.

Table 2-1. T1 voice interface commands

Command See...

show t1 page 11

set t1 framemode [ESF|D4] page 12

set t1 linecoding [B8ZS|AMI] page 12

set t1 clocksource [internal|network] page 12

set t1 loopback [noloopback|payload|line] page 14


T1 voice interface commands

Viewing the T1 configuration settingsYou can view the T1 configuration settings by issuing the show t1 command. The particular configuration shown in the example is one of the recommended T1 configurations for a SIP environment.Syntax: show t1Example:

In this example, the T1 parameters are shown.

VPacket# teltelephony# show t1 ----------------- T1 Configuration --------- Signaling protocol : CAS Frame mode : ESF Line coding : B8ZS Clock source : network Loopback mode : noloopback Cable length : 133ft ----------------- T1 Status ---------------- State : Up Loopback : None Red Alarm : No Yellow Alarm : No ----------------- T1 Statistics ------------ Frame errors : 11 Current interval : 355 Line code violations : 0 Path code violations : 0 Controlled slip seconds : 0 Frame loss count : 0 Error seconds : 0 Unavailable seconds : 0 Bursty error seconds : 0 Severely error seconds : 0 Line error seconds : 0 Severely error framing seconds : 0telephony#



Setting the T1 frame modeYou can set the T1 frame mode by issuing the set t1 framemode command.Syntax: set t1 framemode [ESF|D4]Arguments:

ESFD4

Example:

In this example, the T1 frame mode is set to ESF.

Setting the T1 line codingYou can set the T1 line coding by issuing the set t1 linecoding command.Syntax: set t1 linecoding [B8ZS|AMI]Arguments:

B8ZSAMI

Example:

In this example, the T1 linecoding is set to B8ZS.

Setting the T1 clock sourceYou can set the T1 clock source to either internal time keeping or from the network by issuing the set t1 clocksource command.Syntax: set t1 clocksource [internal|network]Argument:

internal | networkinternal sets the VDR to use the internal clock for time keeping; network forces the VDR to use the network clock

VPacket# teltelephony# set t1 framemode esfOKtelephony#

VPacket# teltelephony# set t1 linecoding B8ZSOKtelephony#


T1 voice interface commands

Example:

In this example, the T1 port is configured to use the network clock for time keeping.

VPacket# teltelephony# set t1 clocksource networkOKtelephony#



Setting the T1 loopbackYou can set the T1 loopback by issuing the set t1 loopback command. The loopback must be set to “no loopback” to interoperate within a SIP environment.Syntax: set t1 loopback [noloopback|payload|line]Argument:

noloopback | payload | linenoloopback (default) is the recommended choice for use with SIP

Example:

In this example, the T1 port is configured to no loopback.

VPacket# teltelephony# set t1 loopback noloopbackOKtelephony#


Contents

3Coding profilecommands

Overview, page 17Coding profile command list, page 17

CHAPTER 3Coding profile commands


Coding profile command list

OverviewTo set the Vpacket 5100/6100 VDR for operation within a SIP environment, you need to set the coding type and usage (voice or fax) for each TCID. If the usage is set to fax, you also need to set the coding profile to reflect the recommended settings. The recommended coding profile settings for fax (G.711) are:• set coding 11 copyof 0• set coding 11 usage fax on• set coding 11 usage voice off• set coding 11 vad off• set coding 11 nom_delay 80• set coding 11 max_delay 160• set coding 11 adaptive_playout off• set coding 11 tone_detect off The number 11 (eleven) is a place holder indicating the profile number. You can choose a different number. In addition to these commands, you also need to assign the fax coding profile to a TCID (set tcid 0 fax_prof 11). After the settings are configured, you need to activate and commit the changes.

Coding profile command listTable 3-1 lists the coding profile commands.

Table 3-1. Coding profile commands

Coding profile set coding [prof_id] coding_type page 18

set coding [prof_id] usage page 19

T.38 fax-related coding profile parameters

set coding [prof_id] rate page 20

set coding [prof_id] fax_hs_pkt_rate page 20

set coding [prof_id] fax_ls_redundancy page 21

set coding [prof_id] fax_hs_redundancy page 21

set coding [prof_id] fax_tcf_method page 22



Warning. Other coding commands are available in the CLI help, but any changes made using other commands are not recommended and could adversely affect the performance of the 5100/6100 VDR.

Caution. Before using any coding commands, Vpacket strongly recommends that you prepare a backup configuration of your installation as you have benchmarked it.

Assigning codecs to coding profilesYou can specify the codec type for a coding profile by issuing the set coding command.Syntax: set coding [prof_id] coding_type [tx|rx] <codec type>Argument: [tx|rx] <codec type>Range: Refer to Table 3-2.

Example:

Table 3-2. Codec types

Codec Type/parameter Description

pcm_mu PCM u-Law coding

pcm_a PCM a-Law coding

a16 ADPCM 16kbps coding

g723_53 G.723.1 5.3 kbps coding

g723_63 G.723.1 6.3 kbps coding

g729ab G.729 annex a, annex b 8kbps coding

fax Fax relay

fax_t38 Fax relay in T.38 mode

VPacket# teltelephony# set coding 1 coding_type pcm_muOKtelephony#

WARNING

!



In this example, the telephony submenu is accessed and then the coding command is entered. The 5100/6100 VDR responds to confirm the action.

Setting the coding usageYou can set the coding usage for either voice or fax use by issuing the set coding [prof_id] usage command.

Caution. Voice or fax usage are allowed. The 5100/6100 VDR does not allow modem or data coding profile use.

Syntax: set coding [prof_id] usage <voice | fax | modem | data> <on | off>Argument:

voice | fax | modem | datachoices of coding profile use

on | off to enable or disable the parameterExample:

In this example, the coding profile is set to use voice.

telephony# set coding 2 usage voice onOKtelephony#

!



Setting the fax data rateYou can set the maximum data rate for a fax coding profile by issuing the set coding [prof_id] rate command. Syntax: set coding [prof_id] rate <rate>Argument:

rate 2400 | 4800 | 7200 | 9600 | 12000 | 14400 | 5300 | 6300Example:

In this example, the coding rate for coding profile number 1 is set to 12,000.

Setting the fax packet rateYou can set the rate at which high speed data will be sent across the network for a fax coding profile by issuing the set coding [prof_id] fax_hs_pkt_rate command.Syntax: set coding [prof_id] fax_hs_pkt_rate <value>Argument:

value in milliseconds; 10, 20, 30 or 40Example:

In this example, the fax high-speed packet rate is set to 30.

VPacket# teltelephony# set coding 1 rate 12000OKtelephony#

VPacket# teltelephony# set coding 0 fax_hs_pkt_rate 30OKtelephony#



Setting the packet-level redundancyYou can specify the packet-level redundancy for low-speed data transmissions (the T.30 handshaking information) for a fax coding profile by issuing the set coding [prof_id] fax_ls_redundancy command. The method used involves assembling an additional number of prior packets after the primary with decreasing sequence numbers. For example, if each payload contains a primary and two or more secondary fields, this sequencing protects against a loss of two consecutive UDP Transport Layer (UDPTL) packets.Syntax: set coding [prof_id] fax_ls_redundancy <value>Argument:

value 0, 1, 2, 3, 4 or 5Example:

In this example, the fax packet-level redundancy is set to 2.

Setting the high-speed redundancyYou can specify the packet-level redundancy for high-speed data transmissions (the T.4 image data) for a fax coding profile by issuing the set coding [prof_id] fax_hs_redundancy command.Syntax: set coding [prof_id] fax_hs_redundancy <0, 1 or 2>Argument:

0, 1 or 2 number of repeat packets to be sentExample:

In this example, the redundancy is set to 1.

VPacket# teltelephony# set coding 1 fax_ls_redundancy 2OKtelephony#

VPacket# teltelephony# set coding 1 fax_hs_redundancy 1OKtelephony#



Setting the fax transmission methodYou can control the method with which data for a fax coding profile is moved over a network by issuing the set coding [prof_id] fax_tcf_method command. Method 1 (Local) requires that the Training Check Field (TCF) training signal be generated and checked locally by the gateway and is not forwarded over the network. In Method 2 (Network), TCF data is sent over the network. These correspond to Data Management methods 1 and 2 in specification T.38.Syntax: set coding [prof_id] fax_tcf_method <method>Argument:

method 1 (local) or 2 (over the network)Example:

In this example, Method 2 is chosen, which requires that a TCF training signal be sent over the network.

VPacket# teltelephony# set coding 1 fax_tcf_method 2OKtelephony#


Contents

4TCID commands

Overview, page 25TCID commands, page 26

CHAPTER 4TCID commands


OverviewTCIDs are typically configured with the following information:• A preferred coding profile to use for voice• An alternate coding profile to switch to when FAX tones are detected• Other possible coding profiles to use if the preferred voice profile cannot be negotiated• Additional local configuration parameters

The following sections contain each command with a definition, parameters, and an example to show how to modify an existing TCID channel description or build a new one. • The set tcid commands describe and modify the local configuration parameters of the TCID

channel as a whole.• The set coding commands describe and modify the coding profile attached to the TCID. See

page 17.• The set ssmu commands modify SIP parameters pertaining to a TCID. See page 7.

Warning. Other coding commands are available in the CLI help, but any changes made using those other commands are not supported and could adversely affect the performance of the 5100/6100 VDR.

Caution. Before using any TCID modification commands, Vpacket strongly recommends that you prepare a backup configuration of your installation as you have benchmarked it.

WARNING

!



TCID commandsTable 4-1 lists all of the TCID-related commands listed in this chapter.

Table 4-1. TCID commands

Group Command See...

TCID set tcid [tcid] mode [sw | trans] [cas | ccs | proxy | xgcp] page 27

set tcid [tcid] voice_prof <prof_id number, -1> page 29

set tcid [tcid] fax_prof <prof_id number, -1> page 29

set tcid [tcid] companding [a_law | mu_law | linear] page 30

set tcid [tcid] cid name <Caller ID name> page 30

set tcid [ticd] cid time <Caller ID number> page 31

set tcid [tcid] proto <emi | emw | emd | fxsls | fxsgs > page 31

TCID FXS loopstart set tcid [tcid] fxsls offhook_db page 32

set tcid [tcid] fxsls onhook_db page 32

set tcid [tcid] fxsls seize_detect page 33

set tcid [tcid] fxsls orig_clear_detect page 33

set tcid [tcid] fxsls answ_clear_detect page 34


TCID commands

Setting the TCID modeYou can set the operating mode for each TCID (0-23) by issuing the set tcid [tcid] mode command. The mode is set on a per TCID basis.Syntax: set tcid [tcid] mode [sw | trans] [cas | ccs | proxy | xgcp]

Miscellaneous TCID commands

set tcid [tcid] prof_bit See SIP help within the CLI

set tcid [tcid] call_cap

set tcid [tcid] companding

set tcid [tcid] rxgain

set tcid [tcid] txgain

set tcid [tcid] idle_noise

set tcid [tcid] cp_tone_det_ctrl

set tcid [tcid] cp_tone_det_config

set tcid [tcid] tone_out_on

set tcid [tcid] tone_out_off

set tcid [tcid] dial_in plar

set tcid [tcid] call_limit

set tcid [tcid] ans_wait

set tcid [tcid] hangup_wait

set tcid [tcid] fax_holdover

set tcid [tcid] cid name

set tcid [tcid] cid number

set tcid [tcid] cid time

set tcid [tcid] tone_table

set tcid [tcid] state

set tcid [tcid] copyof

Table 4-1. (continued) TCID commands

Group Command See...



Arguments:tcid 0-23; the ID number of the TCID you want to sw |trans sw is softswitch (choice for H.323)cas | ccs | proxy | xgcp

cas is channel associated signaling (valid); ccs is clear channel signaling; proxy; xgcp is MGCP (valid)

Example:

In this example, the mode for TCID 4 is set to use T1 CAS.

VPacket# teltelephony# set tcid 4 mode sw casOKtelephony#


TCID commands

Setting the preferred voice coding profileYou can set the preferred voice coding profile for the TCID by issuing the set tcid [tcid] voice_prof command.Syntax: set tcid [tcid] voice_prof <prof_id>Argument:

tcid the number of the TCID to which you are setting the preferred coding profile

prof_id profile ID number; from 0 to maximum number of profiles -1; -1 means no preferred profile

Example:

In this example, the preferred voice coding profile for TCID 0 is set to coding profile number 1.

Setting the preferred fax coding profileYou can set the preferred fax coding profile for the TCID indicated by issuing the set tcid [tcid] fax_prof command.Syntax: set tcid [tcid] fax_prof <prof_id>Argument:

tcid the number of the TCID to which you are setting the preferred coding profile

prof_id profile ID number; from 0 to maximum number of profiles -1; -1 means no preferred profile

Example:

In this example, the preferred fax coding profile for TCID number 3 is set to profile number 5.

VPacket# teltelephony# set tcid 0 voice_prof 1OKtelephony#

VPacket# teltelephony# set tcid 3 fax_prof 5OKtelephony#



Setting the companding lawYou can set the companding law by issuing the set tcid [tcid] companding command. Syntax: set tcid [tcid] companding [a_law | mu_law | linear]Arguments:

tcid the ID number of the TCID that you want to configurea_law | mu_law | linear

a_law is for use in Asia and Europe; mu_law is for use in North America Example:

In this example, TCID number 5 is set to use A-law for companding.

Setting the caller ID nameYou can set the caller ID name by issuing the set tcid [tcid] cid name command.Syntax: set tcid [tcid] cid name <Caller ID name>Arguments:

tcid 0-23; the number of the TCID that corresponds to the channels assigned to a particular person

caller ID name 1-15 alphanumeric characters; underscore character is supported for spaces; P for private; O for unavailable

Example:

In this example, Emmett Otter’s name is programmed into the caller ID feature of TCID 5.

VPacket# teltelephony# set tcid 5 companding a_lawOKtelephony#

VPacket# teltelephony# set tcid 5 cid name Emmett_OtterOKtelephony#


TCID commands

Setting the caller ID timeYou can set the caller ID time by issuing the set tcid [tcid] cid time command.Syntax: set tcid [tcid] cid time <MMDDhhmm>Arguments:

tcid 0-23; the number of the TCID that you want to set the time forMMDDhhmm MM=month; DD=date; hh=hour in 24-hour format; mm=minutes

Example:

In this example, the caller ID time and date is set to 4:00 pm on November 23 for TCID 5.

Setting the protocol typeYou can set the protocol type by issuing the set tcid [tcid] proto command.Syntax: set tcid [tcid] proto [emi | emw |emd | fxsls | fxsgs]Arguments:

emi E & M immediate start emw E & M wink start emd E & M delayed startfxfls FXS loop startfxsgs FXS ground start

Example:

In this example, the protocol is set to E&M wink start.

VPacket# teltelephony# set tcid 5 cid time 11231600OKtelephony#

VPacket# teltelephony# set tcid 2 proto emwOKtelephony#



Setting the FXS off hook levelYou can set the off hook level by issuing the set tcid [tcid] fxsls offhook_db command. This command applies only to models with FXS voice interface ports.Syntax: set tcid [tcid] fxsls offhook_db <value in ms>Argument:

value in msExample:

In this example, the off hook level is set to 3 ms.

Setting the on hook levelYou can set the on hook level by issuing the set tcid [tcid] fxsls onhook_db command. This command applies only to models with FXS voice interface ports.Syntax: set tcid [tcid] fxsls onhook_db <value in ms> Argument:

value in msExample:

In this example, the on hook level is set to 5 ms.

telephony# set tcid 2 fxsls offhook_db 3OKtelephony#

telephony# set tcid 2 fxsls onhook_db 5OKtelephony#


TCID commands

Setting the seize detect parameterYou can set the seize detect parameter by issuing the set tcid [tcid] fxsls seize_detect command. This command applies only to models with FXS voice interface ports.Syntax: set tcid [tcid] fxsls seize_detect <value in ms>Argument:

value in msExample:

In this example, the seize detect is set to 3 ms.

Setting the originator clear detect parameterYou can set the originator clear detect parameter by issuing the set tcid [tcid] fxsls orig_clear_detect command. This command applies only to models with FXS voice interface ports.Syntax: set tcid [tcid] fxsls orig_clear_detect <value in ms>Argument:

value in msExample:

In this example, the clear originator detect parameter is set to 5 ms.

telephony# set tcid 2 fxsls seize_detect 3OKtelephony#

telephony# set tcid 2 fxsls orig_clear_detect 5OKtelephony#



Setting the answer-side clear detectYou can set the answer-side clear detect by issuing the set tcid [tcid] fxsls answ_clear_detect command. This command applies only to models with FXS voice interface ports.Syntax: set tcid [tcid] fxsls answ_clear_detect <value in ms>Argument:

value in msExample:

In this example, the answer-side clear detect is set to 4 ms.

telephony# set tcid 2 fxsls answ_clear_detect 4OKtelephony#


Configuring SIP withISDN PRI

5

Contents
Overview, page 37
PRI Signaling commands, page 37Configuring SIP with PRI signaling, page 38

CHAPTER 5Configuring SIP with ISDN PRI


PRI Signaling commands

OverviewTo set up SIP with Primary Rate Interface (PRI) signaling you can follow the steps in this chapter.All of the necessary commands reside within the telephony command shell. First, you will set the voice interface to use ISDN and then you will create a dial plan by using the Address Translation Parsing Module (ATPM).Before sending or receiving calls, you also need to make sure that the PBX is set up to send the caller ID number and name to the 5100/6100 VDR.

PRI Signaling commandsTable 5-1 lists the commands required to configure the 5100/6100 for PRI signaling within a SIP environment.

Table 5-1. PRI signaling commands

Command groupf Command Meaning

SIP set t1 sigproto ccs See help within the telephony shell for parameters

ISDN commands

show isdn l2_stats specifies the Level 2 statistics for the TCID

show isdn chan_stats shows the status of all of the B channels

show isdn restart_msg shows whether or not the layer 3 restart messaging is activated (default: off)

show isdn alert_tone show shows whether or not the VDR provides the Inband ringback tone(default: off)

show isdn disconnect_tone shows whether or not the VDR provides the Inband disconnect tone (default: off)

set isdn restart_chan [chan_id] chan_id in range [1-24]

set isdn restart_msg [off/on] turns the restart message feature on or off (default:off)

set isdn alert_tone [off/on] turns the ISDN alert tone on or off (default:off)



Configuring SIP with PRI signalingYou can cut and paste these scripts to quickly configure your 5100/6100 VDR to use SIP with PRI signaling. 1. Enter the telephony command shell by entering tel.Example:

2. Set the voice interface module (VIM) by using the following script to configure the VDR for ISDN.

Note. After entering the set t1 sigproto ccs command, you must finish configuring all of the ports.

ISDN commands (continued)

set isdn disconnect_tone [off/on] turns the ISDN disconnect tone on or off (default:off)

TCID commands for PRI

set tcid 23 isdn dchan 0 Refer to the telephony shell help for parameter details

set tcid 23 isdn isdnproto net

set tcid 23 isdn dsltype pri-t1

set tcid 23 isdn swtype ni2

set tcid 0 isdn bchan 23 1

Table 5-1. (continued) PRI signaling commands

Command groupf Command Meaning

Vpacket# teltelephony#


Configuring SIP with PRI signaling

Example:

3. Set the ISDN Bchannel for each TCID.

set t1 sigproto ccs

set tcid 0 mode sw ccs


























Example:

Note. A reset is required to set ISDN mode before configuring the ATPM dialplan.

4. Commit, activate, and reset the unit.Example:

set tcid 23 isdn dchan 0

set tcid 23 isdn isdnproto net

set tcid 23 isdn dsltype pri-t1

set tcid 23 isdn swtype ni2
























telephony#telephony# commitOKtelephony#activatecommitOKtelephony#reset



5. Log in by entering your user name and password.6. Enter the telephony shell by entering tel7. Set these ISDN commands as follows:

set isdn restart_chan [chan_id] where: chan_id in range [1-24]set isdn restart_msg [off/on]set isdn alert_tone [off/on]set isdn disconnect_tone [off/on]

8. Commit the changes, activate, and reset the unit.Example:

VPacket# tel

telephony# show t1

----------------- T1 Configuration ---------

Signaling protocol : CCS

Frame mode : ESF

Line coding : B8ZS

Clock source : internal

Loopback mode : noloopback

Cable length : 133ft

----------------- T1 Status ----------------

State : Up

Loopback : None

Red Alarm : No

Yellow Alarm : No

----------------- T1 Statistics ------------

Frame errors : 10

Current interval : 518

Line code violations : 0

Path code violations : 0

Controlled slip seconds : 0

06/11/2002:18:02:30 - System is up and running

**** 4.00, 4.00, 3.30, 3.30, 3.00 ***

06/11/2002 18:02:30 - [4] Sip Stack Created.

SNMP Research SNMP Agent Resident Module Version 15.1.1.8

Copyright 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998 SNMP Resear

ch, Inc.

06/11/2002 18:02:31 - [4] TIUHW: Red Alarm On

06/11/2002 18:02:31 - [4] ISDM: 23 Set Channel State Done (SUCCESS)


06/11/2002 18:02:31 - [4] ISDM: 23 [D] Channel Config Done (SUCCESS)


06/11/2002 18:02:36 - [4] TIUHW: Red Alarm Off



Frame loss count : 0

Error seconds : 0

Unavailable seconds : 0

Bursty error seconds : 0

Severely error seconds : 0

Line error seconds : 0

Severely error framing seconds : 0

telephony#

telephony# show tcid 0

Configuration for TCID 0:

Mode: Switched CCS

Isdn Parameters: B Channel: 1 of D

Channel-Tcid: 23

telephony#

Isdn States: IMU: tcid(0): is idle, available for calls.

telephony# show tcid 23

Configuration for TCID 23:

Mode: Switched CCS

Pref Voice coding profile: 0

Pref Fax coding profile: 8

Pref Modem coding profile:None

Pref Data coding profile: None

Allowed Coding Prof Ids\Call Caps: (x - y means x to y both inclusive)

Coding prof: 0- 8. Call cap: None.

Telephony Interface Configuration:

Companding = Mu-Law

Gain (RX,TX) = (-1,-1)

Idle noise level = -6500 x .01 dB

Call Progress Tone Detection Control = Always off

Call Progress Tone Detection Configuration = Default

ISDN Parameters:

D Channel: Dsl = 0, Proto = net, Type = pri-t1, Switch = ni2

Only enbloc mode supported

Call Timing Parameters:

Call Limit: forever

Answer Wait: forever

Hangup Wait: forever



Fax Holdover: 2000 msec

Tone Table: N. America(na)

Dial Out Parameters:

Out Wait: 400 msec

Out Type: tone

Tone Out Off Time: 200 msec

Tone Out On Time: 200 msec

Tone Out Power: -130 x 0.1 dB (not configurable)

ISDN States:

IMU: tcid(23): is UP

telephony#

9. Check to make sure that TCID 23 is UP.10. Configure a dial plan. See page 47.


Configuring ATPM
6
Contents
Overview, page 47
Viewing ATPM commands, page 48ATPM Telephone Address to Hunting Group Table, page 49

Hunt Group ID to Destination ID Mapping Table, page 52Destinations List, page 53

ATPM System Parameters, page 56ATPM Utilities, page 57

Configuring a dial plan for T1-CAS or FXS, page 59ISDN PRI script for generating a dial plan, page 64

CHAPTER 6Configuring ATPM


OverviewThe Address Translation Parsing Module (ATPM) provides the translation capability for connecting the IP addressing scheme of the Internet to the telecommunications addressing scheme of the PSTN.

The ATPM functions in two exclusive environments:

• Performing address translation when a gatekeeper is not present.• Performing enhanced call routing when a gatekeeper is present.Whether it is working to do address translation or call routing, the ATPM builds up telephony connection characteristics by supplying configuration tables based on these sets of values:• IP and network addresses• Hunting Groups provide a grouping mechanism for directing traffic within a domain of tele-

phone numbers.• Destinations: The Destinations List table maps a specified network address to an arbitrary

number called a Destination ID. • System-wide Call Parameters• Various utilitiesRemoving the system Call Parameters and utilities from consideration since they define and manipulate general call characteristics and not the actual connections (TCIDs) themselves, the following values combine to build three ATPM Amapping tables:

1. The Telephony Address Mapped to Hunt Group Identity.2. The Hunt Group Identity Mapped to Destination Identity.3. The Destinations Identity to an internal Channel Number or the terminating entity for a call.

Before addressing the definition of the ATPM mapping tables and the ATPM System parameters, it is important to get an overview of how all these parts interconnect.

For example, if you needed to set up a connection to channel 10 (physical line 10 of the VDR) which has the official telephone company number of 408-571-7100, you would set up the following interconnected lists (here listed with their example values):

• An Address List (aadd): 408-571-7100 mapped to Hunt Group 7• A Hunt List (hadd): Hunt Group 7 mapped to Destination ID 6• A Destination List (dadd): Destination ID 6 mapped to (telephony port) Channel 10



Viewing ATPM commandsThe figure below shows the ATPM commands as displayed within the CLI.

VPacket# teltelephony# atpmATPM Commands (All commands prefixed by "atpm"):Database update control related commands: req (database update request) done (database update doneSystem commands: sys <dial_time> <1st_digit_wait> <inter_digit_wait> <dial_out_code> <area_code> <office_code> <first_dn> [dial_term_digit] slist (Show system params)Address entry commands: aadd <tele_number> <min_digits> <max_digits> <hunt_group_id> <prefix_strip_len> [prefix_number] adel <tele_number> afind <tele_number> alist (List Address entries)Hunt group entry commands: hadd <hunt_group_id> <hunt_type> <member1_id> [member2_id].... hdel <hunt_group_id> hfind <hunt_group_id> hlist (List hunt groups)Destination entry commands: dadd <dest_id> <tsgm|hsmu> <dest related params> ddel <dest_id> dfind <dest_id> dlist (List destinations)Utilities genlist <all | addr | hunt | dest> (Auto generate specified list based on IP address) purge <all | addr | hunt | dest> (Delete all entries in specified list) store (Store all ATPM Entries into flash) restore (Restore all ATPM Entries from flash)

telephony#


ATPM Telephone Address to Hunting Group

ATPM Telephone Address to Hunting Group TableThe ATPM Telephone Address to Hunt Group ID List (alist) provides mapping from a telephony address to one of the hunt groups specified in the Hunt Group List.

Use the atpm add command syntax to define this table:

atpm aadd <tele_number> <min_digits> <max_digits> <hunt_group_id> <prefix_strip_len> [prefix_number]

where

• <tele_number>: Telephone Number to match. This is only a part of the total dialed string.• <min_digits>: Minimum number of digits to be collected. This must be less than or equal to the

number of digits in tele_number to match.• <max_digits>: Maximum number of digits to be collected. (Max_dial_digits).• <hunt_group_id>: Hunt group ID for this telephone number.• <prefix_strip_len>: The number of digits to be stripped at the beginning of the collected

address. • [prefix_number]: Digit to be attached to the beginning of the address before forwarding it. Note

that this optional step of attaching a new prefix address is done only after the previous step of stripping some prefix digits on the collected digits.

Note. The prefix_number value is an optional parameter, that is, if no number is entered, no prefix number is configured.

Table 5-1 alist Parameters Defined

Parameter Range Description

tele_numberPortion of the total dialed number to match

Maximum number of digits that can be dialed. Each digit can be 0 to 9, a, b, c, d, *, #. If a dial-terminat-ing digit has been configured, then that digit cannot be a part of the tele_number.

min_digits 1 to maximum dial-able digits

Minimum number of digits to be collected Should be greater than or equal to the number of digits in tele_number.

max_digits1 to maximum dial-able digits

Maximum number of digits to be collected match. Should be greater than or equal to the value of min_digits.



To view a particular member of the list, use the afind <tele_number> command.

To delete a particular member of the list, use the adel <tele_number>

hunt_group_id0 to (Maximum number of Hunt Groups – 1)

Should be greater than or equal to the value of Hunt Groups set.

prefix_strip_len 0 to (Maximum number of digits you can dial – 1)

The number of digits to be stripped at the beginning of the collected address.

[prefix_number] 1-4 digits Digits to be attached to the beginning of the address before forwarding it. Attaching a prefix address is done only after the previous step of strip-ping some prefix digits on the collected digits.

Table 5-1 alist Parameters Defined


tele_numberPortion of the total dialed number to match

Maximum number of digits that can be dialed. Each digit can be 0 to 9, a, b, c, d, *, #. If a dial-terminat-ing digit has been configured, then that digit cannot be a part of the tele_number.


ATPM Telephone Address to Hunting Group

To view the address list, issue the atpm alist command (see following example):

VPacket(telephony)# atpm alist Address Hunt Min Max Prefx Prefix Entry Grp_Id Digits Digits strip Address 14085715600 0 11 11 11 None 14085715601 1 11 11 11 None 14085715602 2 11 11 11 None 14085715603 3 11 11 11 None 14085715604 4 11 11 11 None 14085715605 5 11 11 11 None 14085715606 6 11 11 11 None 14085715607 7 11 11 11 None 14085715608 8 11 11 11 None 14085715609 9 11 11 11 None 14085715610 10 11 11 11 None 14085715611 11 11 11 11 None 14085715612 12 11 11 11 None 14085715613 13 11 11 11 None 14085715614 14 11 11 11 None 14085715615 15 11 11 11 None 14085715616 16 11 11 11 None 14085715617 17 11 11 11 None 14085715618 18 11 11 11 None 14085715619 19 11 11 11 None 14085715620 20 11 11 11 None 14085715621 21 11 11 11 None 14085715622 22 11 11 11 None 14085715623 23 11 11 11 None 5600 0 4 4 4 None 5601 1 4 4 4 None 5602 2 4 4 4 None 5603 3 4 4 4 None 5604 4 4 4 4 None 5605 5 4 4 4 None 5606 6 4 4 4 None 5607 7 4 4 4 None 5608 8 4 4 4 None 5609 9 4 4 4 None 5610 10 4 4 4 None 5611 11 4 4 4 None 5612 12 4 4 4 None 5613 13 4 4 4 None 5614 14 4 4 4 None 5615 15 4 4 4 None 5616 16 4 4 4 None 5617 17 4 4 4 None 5618 18 4 4 4 None 5619 19 4 4 4 None 5620 20 4 4 4 None 5621 21 4 4 4 None 5622 22 4 4 4 None 5623 23 4 4 4 None 5715600 0 7 7 7 None 5715601 1 7 7 7 None 5715602 2 7 7 7 None 5715603 3 7 7 7 None 5715604 4 7 7 7 None



5715605 5 7 7 7 None 5715606 6 7 7 7 None 5715607 7 7 7 7 None 5715608 8 7 7 7 None 5715609 9 7 7 7 None 5715610 10 7 7 7 None 5715611 11 7 7 7 None 5715612 12 7 7 7 None 5715613 13 7 7 7 None 5715614 14 7 7 7 None 5715615 15 7 7 7 None 5715616 16 7 7 7 None 5715617 17 7 7 7 None 5715618 18 7 7 7 None 5715619 19 7 7 7 None 5715620 20 7 7 7 None 5715621 21 7 7 7 None 5715622 22 7 7 7 None 5715623 23 7 7 7 None 9 12 8 32 1 NoneOKVPacket(telephony)#

This alist covers all three possible cases for the numbers 408-571-5600 to 408-571-5611, twelve numbers which match the VDR physical telephone lines:

• The first 12 are incoming, “fully-qualified” numbers which include the full 10-digits of long-distance and area code.

• The second 12 are “in-house” or “intercom” options which support port-to-port connections.• The third 12 are “local” numbers and support local connections.The last number is the minimum for accessing an outside line.

Hunt Group ID to Destination ID Mapping TableThis configuration table is used to hunt for destinations in the specified Hunt Group. This list contains entries that specify the following information:

• Hunt Type• Hunt MembersEach Hunt Group must have at least one member. The maximum number of members is decided by the amount of space in the Hunt Members list (hlist). The parameter MAX_HUNT_MEMBERS contains this value for all Hunt Group members.

Creating a Hunt Group IDTo create a Hunt Group use the following command:


Destinations List

atpm hadd <hunt_group_id> <hunt_type> <member1_id> [member2_id] ...

Additional Commands to Maintain the hlist table:• atpm hdel <hunt_group_id> deletes the specified Hunt group from the Hunt group list.• atpm hfind <hunt_group_id> finds and displays information related the specified Hunt Group in

the Hunt Group list. • atpm hlist displays all the entries in the Hunt group list.• atpm hdel <hunt_group_id>removes a specific entries in the Hunt group list.

Destinations ListThe ATPM Destination List builds a list (dlist) which provides a mapping from a destination ID to the physical termination of a call using SIP (CCS).

Note. ATPM will show ISDN in the destinations list only after you configure CCS.

To set up the destination list, use the following two commands with this syntax:

Table 5-2 hlist Parameters Defined


hunt_group_id 0 to (maximum number of Hunt Groups – 1)

Numerical value for each Hunt Group.

hunt_type

1 -> GG_HUNT_ROUND_ROBIN_PER_HUNT_GROUP2 -> GG_HUNT_ROUND_ROBIN_PER_SESSION

Starts from the last-used member each time a hunt request comes in (last-used member is remembered across sessions).

Starts from the first member in the hunt group each time a new session is started.All other values are invalid.

member1_id, ..member2_id,

0 to (maximum number of destinations - 1)

Numerical identifiers for each Hunt Group memberOnly member1_id is necessary to create a Hunt Group.



1. atpm dadd <dest_id> tsgm <tcid> where <dest_id> and <tcid> are valid TCID channels.

2. atpm dadd <dest_id> isdn <D channel tcid> where <dest_id> is 0-23 and <D channel tcid> is 23.

3. atpm dadd <dest-id> ssmu udp <user address> <port>where <dest_id> is 0-23 and the <user address> is a valid IP address and <port> is a port number.

Additional commands used to maintain the dlist table:• atpm ddel <dest_id> deletes the specified destination from the destination table.• atpm dfind <dest_id> finds and displays the specified destination in the destination table.• atpm dlist displays all the destinations currently configured in the destination table.To view the destination list, issue the atpm dlist command and you will see something similar to the following example:telephony# atpm dlist

Dest id = 0, D Channel TCID = 23









Table 5-3 dlist Parameters Defined (T1-CAS mode)


<dest_id> 0 to 23 The range of destination

<tcid> 23 TCID-numbered channel for SIP

Table 5-4 dlist Parameters Defined (SIP mode)


dest_id 0 to (maximum number of des-tinations -1)

The range of physical destination connec-tions (phone lines).

network address

Valid IP address and port num-ber in dotted-decimal format.

Ethernet address of end point for the con-nection.


Destinations List















Dest id = 25, Mode = SSMU, Ctl dst = +&@10.10.19.1 call_opt=0x0000

OK

telephony#



ATPM System ParametersThe system-wide parameters are configured with this command:

atpm sys <dial_time> <1st_digit_wait> <inter_digit_wait> <dial_out_code> <area_code> <office_code> <first_dn> [dial_term_digit]

Table 5-5 slist Parameters defined


dial_time 1 to 4294967295 ms

Time between going off hook and dialing the first digit

first_digit_wait 1 to 4294967295 ms

Time between going off hook and dialing the first digit

Inter_digit_wait 1 to 4294967295 ms

Time between successive digits

<dial_out_code> 9 Single number which signals leaving an internal exchange

<area_code> 2–9 Under the North American Numbering Plan, a three-digit “toll area” prefix; there are 796.

<office_code> 101–929 First three digits of seven digit local number.

<first_dn> 1000–9999 Local branch exchange numbers begin with this prefix.

dial_term_digit

Optional parame-ter. Any valid dial digit (Values 0 to 9, a, b, c, d,...*, #)

Digit which indicates end of dial string.It cannot be part of a valid number. All the digits dialed till the “dial term digit” are considered valid and the “dial term digit” is discarded. If no parameter is entered, then no dial terminating digit is configured.


ATPM Utilities

To view the system-wide parameters, use the slist command. For example, if you entered atpm slist you might get the following:

VPacket(telephony)# atpm slistSystem Info: Total dial time = 120000ms, First digit wait = 30000ms, Interdigit wait = 10000ms, Dial term digit = #, Dial out code = 9, Area Code = 408, Office Code = 571, First DN= 5600OKVPacket(telephony)#

The preceeding translates into the following: the dial time is 120000ms or 2 minutes, the interval allowed between picking up the phone and dialing the first number before the system sends you a busy signal is 30 seconds, the allowed interval between dialing the numbers of your call is also 10 seconds, the digit you dial to terminate the call is the pound sign (#), the digit you dial to access an outside line is the 9, your area code is 408, the local or Office code is 571 and the local branch of internal numbers begins with 5600.The first three parameters define line activity characteristics, the second four provide the information for generating an ATPM database, and the optional final parameter allows the caller to end the call before anyone can answer it.

ATPM UtilitiesThis section covers the ATPM utilities and describes procedures for using them to maintain the VDR’s capabilities.

The ATPM provides a set of utilities to perform these tasks: • Store and retrieve configuration information from Flash.• Delete all configured entries.• Generate a limited number of entries automatically.

Managing the Flash ConfigurationOn startup, the ATPM database can be configured in one of two ways:

• If no valid configuration record is found in Flash, the ATPM database is set to some predefined default.

• If a valid configuration has previously been stored in Flash memory, then the ATPM database is read from the record in the Flash.

Of course, a new configuration can be developed by using the commands described previously, but then this configuration must then be stored in Flash memory.

The following commands support the management of the Flash-based ATPM configuration:



• atpm genlist <all | addr | hunt | dest> automatically generates lists based on the system parame-ters and the IP addresses which are found in the three lists or tables (addr for alist, hunt for hlist, and dest for dlist).

• atpm purge <all | addr | hunt | dest> deletes all entries from the ATPM configuration in all lists or the specified list.

• atpm store stores all entries from the ATPM configuration into Flash memory. The Flash ATPM sector will be erased before storing the current entries

• atpm restores all ATPM entries from Flash to the ATPM tables. If some entries are already configured in ATPM when the restore command is used, there could be errors reported due to conflicting entries. It is best to execute an atpm purge all command before using a restore command.

Storing and Activating ATPM ConfigurationsWhen a command has been issued, it is in the Active area where it can be stored or removed by user operation. To implement a change, that command must be stored so when it is rebooted it can be used by the ATPM.

To change the ATPM database, the configuring module must initiate the process by making an ATPM update database request with the command atpm req.

The module can then start configuring the ATPM database after the ATPM responds with a Database update granted response. The ATPM will give the Database Update granted after all the translation and hunt sessions that were in progress during the update request command, are closed. When the module has completed its configuration changes, it sends the CLI the ATPM update database message atpm done.

For example, to update the database you issue the atpm req command:

VPacket (telephony)# atpm req0005957541 - NMM: ATPM Update Database GrantedOKVPacket(telephony)#

The ATPM database accepts no update requests until the ATPM database signals that changed have been made, so no new translations or Hunt sessions will be accepted. This is to avoid wrong trans-lation due to inconsistent ATPM database.

Generating an ATPM ConfigurationTo generate your own ATPM configuration (numbering plan) that you can store to use in the future or employ immediately, perform the following steps:

1. Use atpm req to request an ATPM database update.

2. Use atpm purge to delete the current configuration.


Configuring a dial plan for T1-CAS or FXS

3. Use atpm dadd, atpm hadd, and atpm aadd to build a new configuration.

4. Use atpm done to indicate end of database update.

5. Use atpm store to save this configuration.

The following commands are used to configure a SIP dialplan.gure below is a representation of the ATPM commands as viewed from the CLI.

Configuring a dial plan for T1-CAS or FXSUse the following script for basic dial plan configuration. Edit accordingly with correct phone numbers, ip addresses, PBX and Call Agent requirements.

Note. In this example the alist is purged and manually add for 10 digit dialing (Broadsoft interop) and configure to strip 6 digits for PBX 4 digit dialing support. The dlist also has to be purged and reconfigured for ISDN support. The genlist all command defaults to TSGM (fxs) versus ISDM (ISDN Module).



Example:

atpm req

atpm purge all

atpm sys 120000 30000 10000 9 408 571 3010 #

atpm genlist all

atpm purge dest

atpm purge addr

atpm aadd 4085713010 10 10 0 6

atpm aadd 4085713011 10 10 1 6

atpm aadd 4085713012 10 10 2 6

atpm aadd 4085713013 10 10 3 6

atpm aadd 4085713014 10 10 4 6

atpm aadd 4085713015 10 10 5 6

atpm aadd 4085713016 10 10 6 6

atpm aadd 4085713017 10 10 7 6

atpm aadd 4085713018 10 10 8 6

atpm aadd 4085713019 10 10 9 6

atpm aadd 4085713020 10 10 10 6

atpm aadd 4085713021 10 10 11 6

atpm aadd 4085713022 10 10 12 6

atpm aadd 4085713023 10 10 13 6

atpm aadd 4085713024 10 10 14 6

atpm aadd 4085713025 10 10 15 6

atpm aadd 4085713026 10 10 16 6

atpm aadd 4085713027 10 10 17 6

atpm aadd 4085713028 10 10 18 6

atpm aadd 4085713029 10 10 19 6

atpm aadd 4085713030 10 10 20 6

atpm aadd 4085713031 10 10 21 6

atpm aadd 4085713032 10 10 22 6

atpm aadd 4085713033 10 10 23 6

atpm aadd 9 8 32 24 1

atpm aadd * 1 3 25 0

atpm aadd 4 7 32 26 0

atpm dadd 0 isdm 23

atpm dadd 1 isdm 23

atpm dadd 2 isdm 23

atpm dadd 3 isdm 23

atpm dadd 4 isdm 23

atpm dadd 5 isdm 23



6. Review your atpm config.Example:

atpm dadd 6 isdm 23

atpm dadd 7 isdm 23

atpm dadd 8 isdm 23

atpm dadd 9 isdm 23

atpm dadd 10 isdm 23














atpm dadd 24 ssmu udp +&@64.139.10.173



atpm hadd 24 1 24

atpm hadd 25 1 25

atpm hadd 26 1 26

atpm done

atpm store

telephony#

04/23/2002:17:56:43 - NMM: ATPM Update Database Granted

telephony# atpm alist

Address Hunt Min Max Prefx Prefix

Entry Grp_Id Digits Digits strip Address

4 26 7 32 0 None

4085713010 0 10 10 6 None

4085713011 1 10 10 6 None

(Continued)



4085713012 2 10 10 6 None

4085713013 3 10 10 6 None

4085713014 4 10 10 6 None

4085713015 5 10 10 6 None

4085713016 6 10 10 6 None

4085713017 7 10 10 6 None

4085713018 8 10 10 6 None

4085713019 9 10 10 6 None

4085713020 10 10 10 6 None

4085713021 11 10 10 6 None

4085713022 12 10 10 6 None

4085713023 13 10 10 6 None

4085713024 14 10 10 6 None

4085713025 15 10 10 6 None

4085713026 16 10 10 6 None

4085713027 17 10 10 6 None

4085713028 18 10 10 6 None

4085713029 19 10 10 6 None

4085713030 20 10 10 6 None

4085713031 21 10 10 6 None

4085713032 22 10 10 6 None

4085713033 23 10 10 6 None

9 24 8 32 1 None

* 25 1 3 0 None

OK

telephony# atpm dlist


























Dest id = 25, Mode = SSMU, Ctl dst = +&@10.10.19.1 call_opt=0x0000

OK

telephony# atpm hlist

Hunt group id: 0, Hunt type = 1, Num members = 1, Member ids = 0


























OK

telephony#telephony# atpm slist

System Info: Total dial time = 120000ms, First digit wait = 30000ms, Interdigit wait = 10000ms, Dial term digit = #, Dial out code = 9, Area Code = 408, Office Code = 571, First DN= 3010

OK

telephony#



Note. The command atpm req is required to view the atpm configuration. Be sure to enter the atpm done command before attempting calls. Enter atpm done and atpm store if changes were made to the atpm configuration.

ISDN PRI script for generating a dial planTo generate a dial plan to use with ISDN PRI signaling, use this script. Only the portion that begins “atpm dadd 0 isdm 23...” is specific to PRI signaling and is required. The code in the boxes indicates optional commands. Their use depends on your specific network requirements.


ISDN PRI script for generating a dial plan

Optional commands

Required commandsThe next script is required for ISDN PRI signaling.

atpm req

atpm purge all

atpm sys 120000 30000 10000 9 408 571 3000 #

atpm genlist all

atpm ddel 0

atpm ddel 1

atpm ddel 2

atpm ddel 3

atpm ddel 4

atpm ddel 5

atpm ddel 6

atpm ddel 7

atpm ddel 8

atpm ddel 9

atpm ddel 10

atpm ddel 11

atpm ddel 12

atpm ddel 13

atpm ddel 14

atpm ddel 15

atpm ddel 16

atpm ddel 17

atpm ddel 18

atpm ddel 19

atpm ddel 20

atpm ddel 21

atpm ddel 22

atpm ddel 23

(End of optional commands)

atpm dadd 0 isdm 23

atpm dadd 1 isdm 23

atpm dadd 2 isdm 23

atpm dadd 3 isdm 23

atpm dadd 4 isdm 23

(Continued)



Optional commandsDepending on your network requirements, these commands might be optional.

atpm dadd 5 isdm 23

atpm dadd 6 isdm 23

atpm dadd 7 isdm 23

atpm dadd 8 isdm 23

atpm dadd 9 isdm 23















(End of required commands)

atpm adel 3000

atpm adel 3001

atpm adel 3002

atpm adel 3003

atpm adel 9

atpm adel 14085713002

atpm adel 14085713003

atpm aadd 3000 4 4 0 0

atpm aadd 3001 4 4 1 0

(Optional commands continued)


ISDN PRI script for generating a dial plan

atpm aadd 3002 4 4 2 0

atpm aadd 3003 4 4 3 0

atpm aadd 4085713002 4 32 2 6

atpm aadd 4085713003 4 32 2 6

atpm aadd 9 4 8 24 1

atpm aadd 8 4 32 25 1 408571



atpm hadd 24 1 24

atpm hadd 25 1 25

atpm done

atpm store

(End of optional commands)


Default coding profiles
7
Contents
Overview, page 3

APPENDIX 7Default coding profiles

7-2 Vpacket 5100/6100 Series H.323 Telephony

OverviewVpacket supplies the following default coding profiles for the 5100/6100 VDR. The first six are for data and the last two are for fax. Coding profiles numbered 0 through 5 are specifically for data. To access the default coding profiles , enter show coding <coding profile number> at the telephony prompt.

Configuration for coding profile id 0:Tx Coding = G.711 MU

Rx Coding = G.711 MU

Coding profile for voice

Tx VIF size = 1280 (bits)

Rx VIF size = 1280 (bits)

VAD = ENABLED

VAD threshold = 0 (dB) (relative to ref level of -30dBm)

Playout nominal delay = 30 (msec)

Playout maximum delay = 60 (msec)

Adaptive Playout = ENABLED

Rate = 14400

DTMF Relay = ENABLED

Tone detect = ENABLED

Call Progress Tone detect = DISABLED

V.18 Tone detect = DISABLED

SS7 COT Tone detect = DISABLED

SF Sig Tone detect = DISABLED

EC = ENABLED

EC NL = ENABLED

EC NL Sens = 327

EC Tail = 16 (msec)

EC Freeze = UPDATE

EC Coeffs = RESET

Modem TX level = -13 (dB)

Modem CD threshold = 0

Modem no activity timeout = 20 (sec)

Silence detection time = 60 (msec)

Silence detection level = -50 (dB)

Fax debug level = 0

Caller ID Support = ENABLED

Resampling = DISABLED

Vpacket 5100/6100 Series H.323 Telephony 7-3


EC Config = NLP_FIXED

NLP Comfort Noise = -40 (dB)

Encapsulation = RTP

Configuration for coding profile id 1:Tx Coding = G.711 A

Rx Coding = G.711 A




VAD = ENABLED





Rate = 14400







EC = ENABLED

EC NL = ENABLED

EC NL Sens = 327

EC Tail = 16 (msec)

EC Freeze = UPDATE

EC Coeffs = RESET






Fax debug level = 0






Encapsulation = RTP

Configuration for coding profile id 2:Tx Coding = G723 5.3 kbps

Rx Coding = G723 5.3 kbps




VAD = ENABLED





Rate = 14400







EC = ENABLED

EC NL = ENABLED

EC NL Sens = 327

EC Tail = 16 (msec)

EC Freeze = UPDATE

EC Coeffs = RESET






Fax debug level = 0





Encapsulation = RTP



Configuration for coding profile id 3:Tx Coding = G723 6.3 kbps

Rx Coding = G723 6.3 kbps




VAD = ENABLED





Rate = 14400







EC = ENABLED

EC NL = ENABLED

EC NL Sens = 327

EC Tail = 8 (msec)

EC Freeze = UPDATE

EC Coeffs = RESET






Fax debug level = 0





Encapsulation = RTP


Configuration for coding profile id 4:Tx Coding = G.729AB

Rx Coding = G.729AB




VAD = ENABLED





Rate = 14400







EC = ENABLED

EC NL = ENABLED

EC NL Sens = 327

EC Tail = 16 (msec)

EC Freeze = UPDATE

EC Coeffs = RESET






Fax debug level = 0





Encapsulation = RTP



Configuration for coding profile id 5:Tx Coding = G.726 32K

Rx Coding = G.726 32K




VAD = ENABLED





Rate = 14400







EC = ENABLED

EC NL = ENABLED

EC NL Sens = 327

EC Tail = 16 (msec)

EC Freeze = UPDATE

EC Coeffs = RESET






Fax debug level = 0





Encapsulation = RTP


Configuration for coding profile id 6:Tx Coding = T.38 FAX

Rx Coding = T.38 FAX

Coding profile for fax



VAD = DISABLED




Adaptive Playout = DISABLED

Rate = 14400







EC = ENABLED

EC NL = ENABLED

EC NL Sens = 327

EC Tail = 16 (msec)

EC Freeze = FREEZE

EC Coeffs = RESET






Fax debug level = 0

T.38 Fax Parameters

-------------------

Fax high-speed packet rate = 20 (msec)

Fax low-speed redundancy for T.38 UDP = 3

Fax high-speed redundancy for T.38 UDP = 0

TCF handling = Method 1 (Locally generated and checked)







Encapsulation = RTP

Configuration for coding profile id 7:Tx Coding = FAX

Rx Coding = FAX




VAD = DISABLED





Rate = 14400







EC = ENABLED

EC NL = ENABLED

EC NL Sens = 327

EC Tail = 16 (msec)

EC Freeze = FREEZE

EC Coeffs = RESET






Fax debug level = 0






Encapsulation = RTP

Configuration for coding profile id 8:Tx Coding = G.711 MU

Rx Coding = G.711 MU




VAD = DISABLED





Rate = 14400


Tone detect = DISABLED





EC = ENABLED

EC NL = ENABLED

EC NL Sens = 327

EC Tail = 16 (msec)

EC Freeze = UPDATE

EC Coeffs = RESET






Fax debug level = 0







Encapsulation = RTP


Index
AATPM
alist 49alist parameters 49atpm aadd, afind, and adel commands

50atpm dadd, dfind, and ddel commands

53atpm req command 58Destination list (dlist) 53dlist parameters for MGCP 54dlist parameters for SIP 54function and definition 47genlist 58mapping tables 47store command 58utilities 57

audience iii

Bbold type iv

Ccautions ivchapter summaries iiicommand syntax ivcontact information vicourier typeface ivcustomer care contact information vi

Ddocumentation, related v

HHunt Group

atpm hlist, hfind, and hdel commands53

creating using atpm hadd 52

Nnotes iv

Vpacket 5100/6100 Series SIP Telephony

PSIP commands

set coding 19protocol, T1 CAS 31

Rrelated documentation v

SSIP commands

show t1 11syntax

command iv

TT1 CAS commands

set tcid proto 31technical support vitelephony commands

set tcid fax_prof 29set tcid voice_prof 29

Uusage 19

Wwarnings iv

Index-1

INDEX

Index-2
Vpacket 5100/6100 Series SIP Telephony

series 5100/6100 voice/data router -...

Documents