Cisco Voice Interworking Services (VISM) Installation & Configuration Guide, Release 3.0
Configuring VISM Features
Downloads: This chapterpdf (PDF - 753.0KB) The complete bookPDF (PDF - 5.39MB) | Feedback

Configuring VISM Features

Table Of Contents

Configuring VISM Features

Using the Command Line Interface

VISM Command Attributes

Connecting to Cisco MGX 8000 Series Platforms

Logging In to PXM and VISM Cards

VISM Card Prompt

Logging Out of VISM and PXM Cards

Configuring VISM Features

Initial VISM Configuration

Initial Card Level Configuration

Configuring the Operating Mode

Allocating Resources

Configuring Connection Admission Control

Placing the VISM Card In Service

Placing the VISM Card Out of Service

Configuring the TDM Side

Configuring T1 and E1 Lines

Configuring the PXM and VISM Cards Clocking Source

Configuring the PXM1E or PXM45 Card as Clocking Source

Configuring DS0 Channels

Configuring Bearer Processing

Configuring Codecs

Configuring ECAN

Configuring Jitter

Configuring PNNI for AAL1/AAL2 SVCs

Configuring the ATM Network Side

Configuring PVC Connections for All Operating Modes

Configuring VoIP Switching/Trunking Operating Mode Parameters

Configuring AAL2 Trunking Operating Mode Parameters

Configuring Switched AAL2 PVC Operating Mode Parameters

Configuring the Call Agent Interface

Configuring Domain Names and IP Addresses

Setting Up Call Agents and Protocols

Configuring Gateway Control Protocols

Configuring ISDN PRI Backhaul

Configuring Additional VISM Features

Mid-Call DTMF

Configurable Jitter Buffer

Adjustable Gain

Adjustable Music On-Hold Threshold

CALEA

MGC Redundancy

External DNS

2 IP Address Support

VoIP Trunking

T.38 Fax Relay

CAS Feature Enhancements

Programmable Tone Plans

Loop Start, DID, and Delay Dial

FGD

Configure Flash Hook and Glare Condition Attributes

Configure ANI and DNIS Digit Order

RFC 3064 Package Support

RFC 2833 Support

VISM Network Continuity Test

Configure PVC OAM Cell Parameters

PXM1E and PXM45 Card-Only Features

Call Agent-Controlled VoATM AAL1 and AAL2 SVC

AAL1 SVC-Based TDM Hairpinning

High Complexity Codec Support for VISM-PR—G.723.1

Announcement File System

Announcement Timeouts

Announcement Direction

Broadcast Announcements

Multiple Announcement Requests for the Same Endpoint

Announcement File Server

Announcement File Server Name

Announcement File Server Directory Structure

VISM Announcement Cache Management

Announcement Expiry

Permanent Announcements

Call Agent-Controlled T.38 Fax

Additional Support for MGCP 1.0

RSVP-Based Admission Control

Clock Slip Counters

RTP Connection Statistics

CAS Immediate Start and Ground Start Glare Handling

Grooming for Local Traffic

MGX 8000 Series Implementation Enhancements

Additional VBR Enhancements

Expanded Clock Source Selection

Private Network-to-Network Interface Priority Routing

Additional SPVC Connection Management Capabilities

192 T1/248 E1 DS0 Support with High Complexity Codecs on VISM-PR

Channel Alarm Enhancement

VISM TDM Line Statistics Collection


Configuring VISM Features


The command line interface (CLI) is a DOS-like interface used to configure VISM cards. This chapter describes the following:

"Using the Command Line Interface" section

"Connecting to Cisco MGX 8000 Series Platforms" section

"Configuring VISM Features" section

Using the Command Line Interface

CLI commands may be followed by a string of required or optional argument identifiers and argument values. The entire string, from the command to the last argument value, is referred to as a command line. Spaces are used to separate all elements in a command line. Type the command, any necessary argument identifiers and argument values, then press Enter.


Note You must press the Enter key at the end of all CLI command lines to complete the command.


For example, the Add Endpoint command, addendpt, adds an endpoint to VISM and has three required arguments. An endpoint defines one end of a connection. The addendpt command format is as follows:

addendpt endpt-num ds1-num ds0-num

When you type a command, use argument values to represent the arguments. For example, to add an endpoint with number 10 on DS1 number 4 and DS0 number 3, the command line is as follows:

addendpt 10 4 3

Some commands require you to type an argument identifier before the argument value. For example, the Clear Alarm command, clralm, requires you to enter an identifier, -ds1, before the argument value. The clralm command format is as follows:

clralm -ds1 line-num

To clear alarms on line 4, the command line is as follows:

clralm -ds1 4

VISM Command Attributes

Use the information in Table 4-1 to determine the log file attributes, VISM card state requirements for command use, and personnel privileges for all VISM commands.

Table 4-1 VISM Command Attributes—Log File, Card State, and Privilege Level 

Commands that begin with...
...write to the log file?
...are usable in what state?
...can be used by personnel with what privilege level?

?1

No

All

All

add

Yes

Active

1

cc1

Yes

All

All

chkflash1

Yes

Active

1

clr

No

Active

1 to 5

cnf

Yes

Active

1

del

Yes

Active

1

dsp

No

Active

All

Help1

No

All

All

pinglndsp1

No

Active

All

tst

No

Active

All

version1

No

Active

All

1 The text shown represents the complete CLI command name.



Note For a complete description of the CLI commands in this chapter, see "CLI Commands."


Connecting to Cisco MGX 8000 Series Platforms

The VISM card operates in the following MGX 8000 Series platforms:

Cisco MGX 8850 Release 1, wide area switch

Cisco MGX 8250, edge concentrator

Cisco MGX 8230, edge concentrator

Each platform contains a Processor Module (PXM) back card (see Figure 4-1). Connect your CLI command administration terminal or workstation to the PXM back card's control port—locally or remotely through a modem.


Note The MGX 8000 Series platform PXM back card contains all connections for managing VISM cards. The VISM card itself has no physical management ports.


Figure 4-1 PXM Back Card

Use any of the following devices to connect to a PXM back card:

A simple alphanumeric terminal (such as a DEC VT100 or equivalent) connected to the control port of the MGX 8000 Series platform PXM back card.

A computer emulating an alphanumeric terminal (such as the Microsoft Windows Hyper Terminal program) connected to the control port of the MGX 8000 Series platform PXM back card.

A computer running a Telnet session over Ethernet and connected to the LAN port on the MGX 8000 Series platform PXM back card.

Logging In to PXM and VISM Cards

Complete the following steps to log in to PXM and VISM cards:


Step 1 Physically connect your terminal or workstation to the PXM back card.

The login prompt is displayed:

Login:

Step 2 Type your user name and press Enter.


Note The default user name is cisco. You may change this username after your initial login is complete. Consult the system administrator for valid user names.


The password prompt is displayed:

password:

Step 3 Type your password and press Enter.

For security, the password is displayed as asterisks:

password: *****


Note The default password is cisco. You may change this password after your initial login is complete. Consult the system administrator for valid passwords.


The following prompt is displayed:

card number [7]:

Step 4 If you know the VISM card slot number of the card you want to configure, proceed to Step 5. If you do not know the VISM card slot number of the card you want to configure, proceed to Step 6.

Step 5 Type the VISM card slot number and press Enter.

The VISM card prompt is displayed. See the "VISM Card Prompt" section for more information. You have completed logging in to the PXM and VISM cards and can now perform the mandatory initial VISM card configuration. Proceed to the "Initial VISM Configuration" section.

Step 6 Type the slot number of the active PXM card (either 7 or 8) and press Enter.

The PXM card prompt is displayed:

NODENAME.1.7.PXM.a >

Step 7 Type the dspcds command to display available card types and press Enter.

A list of available card types and associated states is displayed for the MGX 8000 Series platform with which you are connected. The display is similar to the following:

NODENAME.1.7.PXM.a > dspcds

Slot CardState    CardType     CardAlarm   Redundancy
----  -----------  --------     ---------  -----------
1.1   Empty                     Clear
1.2   Active       VISM-8T1     Clear
1.3   Empty                     Clear
1.4   Empty                     Clear
1.5   Empty                     Clear
1.6   Empty                     Clear
1.7   Active       PXM1-OC3     Minor
1.8   Empty                     Clear
1.9   Active       VISM-8E1     Clear
1.10  Empty                     Clear
1.11  Active       VISM-8T1     Clear
1.12  Boot         VISM-8T1     Clear
1.13  Active       VISM-8T1     Clear
1.14  Active       VISM-8E1     Clear
1.15  Empty                     Clear
1.16  Empty                     Clear
1.17  Empty                     Clear
1.18  Empty                     Clear
1.19  Empty                     Clear
1.20  Empty                     Clear
1.21  Boot         VISM-8T1     Clear
1.22  Empty                     Clear
1.25  Reserved     VISM-8E1     Clear
1.26  Empty                     Clear
1.27  Empty                     Clear
1.28  Active       VISM-8E1     Clear
1.29  Empty                     Clear
1.30  Empty                     Clear
1.31  Empty                     Clear
1.32  Empty                     Clear
NODENAME.1.7.PXM.a >

Step 8 Identify, from the list displayed in Step 7, the slot number of the VISM card you want to configure.

Step 9 Type the cc command (to change card), the VISM card slot number identified in Step 8, and press Enter.

The VISM card prompt is displayed. See the "VISM Card Prompt" section for more information.

You have completed logging in to the PXM and VISM cards and can now perform the mandatory initial VISM card configuration. Proceed to the "Initial VISM Configuration" section.


VISM Card Prompt

The VISM card prompt is displayed when you successfully log in to a VISM card and has the following format:

NODENAME.1.9.VISM8.a

The VISM card prompt contains the following data:

Name of the MGX 8000 Series platform to which you are connected

Number of the shelf—always 1

Slot number

Card type

Card state—active (a) or standby (s)

Logging Out of VISM and PXM Cards

Enter one of the following commands to log out of the VISM and PXM cards:

bye

logout

Configuring VISM Features

The CLI allows you to configure all features and functions of VISM. Configure mandatory commands when you require argument values that are different from the default. Configure optional commands when necessary.

Perform the following tasks with CLI commands to enable your VISM card applications:

1. Perform the mandatory initial VISM configuration.

2. Perform the initial card-level configuration.

3. Configure the TDM side.

4. Configure bearer processing.


Note Configure one type of signaling—CAS or CCS—for each application.


5. Configure the ATM network side.

6. Configure the call agent interface.


Note If you are using a VoIP or an AAL2 trunking application, do not configure a call agent interface.


Initial VISM Configuration

You must execute a sequence of mandatory commands, specific to your operating mode, to make the VISM card fully operational. The mandatory commands for each operating mode are listed in Table 4-2 in order of execution. The remainder of this chapter assists you with using these commands, and commands specific to your operating system.

Table 4-2 Mandatory Initial VISM Configuration Command Sequence for All Operating Modes
 

Operating Mode
Command
Notes

VoIP Switching

cnfvismmode1

cnfvismip

addport

addrscprtn

adddn

adddnip

Use this command if you are not using an external DNS.

addmgc

addmgcgrpentry

cnfcac

addln

cnflnsig

addendpt

addcon

cnftftpdn

addcasvar

cnfcasendpt

addmgcgrpprotocol

cnfdnssrvr

Use this command if you are using an external DNS.

Switched AAL2 PVC

cnfvismmode1

cnfvismip

addport

addrscprtn

addmgc

cnfcac

addln

cnflnsig

addendpt

addcon

adddn

cnftftpdn

addcasvar

cnfcasendpt

cnfconvcci

AAL2 Trunking

cnfvismmode1

addport

addrscprtn

cnfcac

addln

cnflnsig

addendpt

addcon

addcid

addccs

1 The cnfvismmode command may be mandatory or optional, depending upon the operating mode with which the VISM card is seen as displayed on your terminal. A VISM card that is not configured is initially displayed in the VoIP operating mode. Subsequent accesses to the VISM card result in the card being displayed in the VoIP operating mode or in the operating mode you have last configured for the card. If the card is displayed as being in the wrong operating mode, the cnfvismmode command is mandatory to change the operating mode. Use the dspvismparam command to verify the VISM card's current operating mode.


Initial Card Level Configuration

You must complete the following configuration tasks when you initially configure your VISM card.

1. Configure the operating mode.

2. Allocate resources.

3. Configure the connection admission control (CAC).

4. Bring VISM into service.

Configuring the Operating Mode

Complete the following steps to configure the correct operating mode for your VISM card immediately after power is applied:


Step 1 Type the dspvismparam command and press Enter to determine the current VISM operating mode.


Note A new VISM card (one that has not been configured) is displayed by default in VoIP operating mode.


The operating mode of the VISM card is displayed in the first line of the VISM card parameter list.

Step 2 If the VISM card operating mode displayed in Step 1 is correct for your application, proceed to the "Allocating Resources" section. If the VISM card operating mode displayed in Step 1 is not correct for your application, proceed to Step 3.

Step 3 Type the cnfvismmode command, an oper-mode argument value, and press Enter to configure the VISM operating mode. Specify the oper-mode argument with one of the following values:

1 = VoIP switching/VoIP trunking

2 = AAL2 trunking

3 = Switched AAL1 SVC

7 = Switched AAL2 SVC

8 = Switched AAL2 PVC—this mode is not supported in VISM Release 3.0

9 = VoIP and Switched ATM AAL1 SVC

You have completed configuring the operating mode for your VISM card. Proceed to the "Allocating Resources" section.


Allocating Resources

Complete the following steps to allocate resources—virtual ports, controller resources, and codec templates—to your VISM card.


Step 1 Type the addport command and press Enter to add a virtual port to your VISM card.

This command adds an ATM port on a VISM. There are no arguments for this command. When you add the ATM port, the bandwidth, VPI range, and VCI range are determined. The VPI range is a single VPI value, the slot ID. The added port is not detected by the controller until you create a resource partition (refer to Step 2). The VISM ATM port is pseudo physical.

Step 2 Type the addrscprtn command, the control-id argument value 1, and press Enter to specify the controller resources.


Note Always specify the control-id argument value as 1.


A port can be controlled by more than one controller (for example PNNI and PAR), but supports only one controller at a time. VISM can create one resource partition for each controller in a non-overlapping way. The controller number you specify associates a resource partition to a controller. All resources of a port are associated with the resource partition you specify. When you add a resource partition, the associated controller detects the port as limited by the resource partition.

Step 3 Type the cnfcodectmpl command, a template-num argument value, and press Enter to specify the codec template used with your VISM card. Specify the template-num argument with one of the following values:

1 = G.711u, G.711a, G.726-16K, G.726-24K, G.726-32K, G.726-40K, G.729a, and G.729ab codecs, and clear channel


Note Template 1 is not supported for the VoIP operating mode.


2 = G.711u and G.711a uncompressed codecs, and clear channel

3 = G.711u, G.711a, G.726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, and G.729ab codecs and clear channel


Note Codec template number 3 = template number 1 with T.38 support added. Maximum channels = 120.


4 = G.711u, G.711a, G. 726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, G.729ab, G.723.1-H, G.723.1a-H, G.723.1-L, G.723.1a-L codecs and clear channel


Note Template 4 supports a maximum of 64 channels for VISM, and a maximum of 144 channels for VISM-PR. The G.723.1 codecs are not supported for the VISM card.


You have completed allocating resources to your VISM card. Proceed to the "Configuring Connection Admission Control" section.


Configuring Connection Admission Control

Complete the following steps, which allow you to:

Enable or disable CAC.

Define CAC parameters.

Configure voiceband data policies for fax/modem carrier loss and fax/modem CAC failure events.


Step 1 Type the cnfcac command, a cac-enable argument value, and press Enter to enable or disable CAC on your VISM card. Specify the argument with one of the following values:

1 = On

2 = Off


Note If your application does not require CAC, specify the cac-enable argument as value 2 in Step 1 and proceed to the "Placing the VISM Card In Service" section.


Step 2 Type the cnfcacparams command, vad-duty-cycle and vad-tol argument values, and press Enter to configure card level CAC parameter values for VAD tolerance and duty cycle, which are used in CAC algorithms. Specify the arguments with the following values:

vad-duty-cycle: In the range from 1 to 99 (default = 61)

vad-tol: In the range from 0 to 10000 (default = 100)

Step 3 Type the cnfconcacparams command, lcn, vad-tol, and vad-duty-cycle argument values, and press Enter to configure values for VAD tolerance and duty cycle, which are used in the CAC algorithms, for a specified logical connection number (PVC). Specify the arguments with the following values:

lcn: In the range from 131 to 510

vad-tol: In the range from 1 to 10000 (default = 100)

vad-duty-cycle: In the range from 1 to 99 (default = 61)

Step 4 Type the cnfvbdpol command, carrier-loss-pol and cac-reject-pol argument values, and press Enter to specify card level default policies for a fax/modem carrier loss and a fax/modem CAC failure. Specify the arguments with the following values:

carrier-loss-pol:

1 = Revert to the previous codec.

2 = Maintain the upspeed codec.

cac-reject-pol:

1 = Delete the connection.

2 = Maintain the connection and revert to the previous codec.

You have completed configuring CAC on your VISM card. Proceed to the "Placing the VISM Card In Service" section.


Placing the VISM Card In Service

Type the cnfgwis command and press Enter to place the VISM card in service. The VISM card prompt terminates with an a to indicate the in-service state:

NODENAME.1.9.VISM8.a

Placing the VISM Card Out of Service

Type the cnfgwoos command, a oos-method argument value, and press Enter to place the VISM card out of service. Specify the oos-method argument with one of the following values:

2—Forceful

3—Graceful

The VISM card prompt terminates with an s to indicate the out-of-service (standby) state:

NODENAME.1.9.VISM8.s

Configuring the TDM Side

You must perform the following tasks to configure the TDM side of your networking application:

1. Configure T1 and E1 lines.

2. Configure VISM card clocking.

3. Configure DS0 channels.

Configuring T1 and E1 Lines

This section deals with the configuration of the eight physical T1/E1 ports on the VISM back card or, if bulk distribution is used, the equivalent ports being fed from the Service Resource Module (SRM) card.

Complete the following steps to:

Add and configure your eight T1 or E1 line ports on the VISM back card.

Add and configure your eight T1 and E1 line ports on the SRM card if your application requires bulk distribution.


Note You can configure the DS0s on a line after a line is added and configured.



Step 1 Type the addln command, a line-num argument value, and press Enter to add a line to your VISM card. Specify the line-num argument value in the range 1 to 8.

The VISM card prompt and line number are displayed.

Step 2 Type the cnfln command, line-num, line-code, line-length, clock-source, line-type, and loopback-detection argument values, and press Enter to specify the operating parameters for the line added in Step 1. Specify the arguments with the following values:

line-num: In the range from 1 to 8

line-code:

2 = B8ZS for T1 lines

3 = HDB3 for E1 lines

4 = AMI for T1 or E1 lines

line-length:

8 = AX-SMB-8E1 and AX-R-SMB-8E1 back card types

9 = AX-RJ48-8E1 and AX-R-RJ48-8E1 back card types

10 to 15 = T1 back cards, where 10 = 0 to 131 ft, 11 = 131 to 162 ft, 12 = 262 to 393 ft, 13 = 393 to 524 ft, 14 = 524 to 655 ft, and 15 = over 655 ft

clock-source:

1 = Loop clock

2 = Local clock

line-type:

1 = DSx1ESF

2 = DSx1D4

3 = E1

4 = E1CRC

5 = E1MF

6 = E1MFCRC

7 = E1 Clear

8 =

9 =

loopback-detection:

1 = Disabled

2 = Enabled

Step 3 Type the cnfalm command, argument identifiers and argument values—-ds1 line-num -red red-sev -rai rai-sev -neu ne-alarm-up -ned ne-alarm-down -net ne-alarm-thresh -feu fe-alarm-up -fed fe-alarm-down -fet fe-alarm-thresh—and press Enter to configure a line for alarm condition handling. Specify the arguments with the following values:

-ds1 line-num: In the range from 1 to 8

-red red-sev:

1 = Minor

2 = Major

-rai rai-sev:

1 = Minor

2 = Major

-neu ne-alarm-up: In the range from 1 to 65535

-ned ne-alarm-down: In the range from 1 to 65535

-net ne-alarm-thresh: In the range from 1 to 65535

-feu fe-alarm-up: In the range from 1 to 65535

-fed fe-alarm-down: In the range from 1 to 65535

-fet fe-alarm-thresh: In the range from 1 to 65535

Step 4 Type the cnflnsig command, line-num and line-signal-type argument values, and press Enter to configure the signaling mode for the specified line. Specify the line-num and line-signal-type arguments with the following values:

line-num: In the range from 1 to 8

line-signal-type:

1 = CAS

2 = CCS

3 = No signaling


Note If you choose CAS signaling for a VISM/VISM-PR E1 line, the supported operating modes are AAL2 trunking and VoIP trunking.


Step 5 Type the cnftrunkcond command, line-num and trunk-cond-enable argument values, and press Enter to enable or disable trunk line conditioning on a line. Specify the arguments with the following values:

line-num: In the range from 1 to 8

trunk-cond-enable:

1 = On

2 = Off

If you enable trunk line conditioning, VISM conditions the affected DS0 when an alarm indication signal (AIS) is detected on the ATM side. Trunk line conditioning consists of transmitting an idle code pattern for 2.5 seconds followed by the seized code specified in the cnfcascode command.


Note This command is not allowed if endpoints or CCS channels are enabled on the line.


Step 6 Type the addlnloop command, a line-num argument value, and press Enter to set a specified line to the local loopback state. Specify the line-num argument in the range from 1 to 8.

Use the dellnloop command to remove the local loopback state on a VISM line.


Note The VISM CLI has no command for setting a line to the remote loopback state. Use the cnfbert command on the PXM card to set a line to the remote loopback state.


You have completed configuring T1 and E1 lines for your VISM card. Proceed to the "Placing T1 and E1 Lines In Service" section.


Placing T1 and E1 Lines In Service

Type the cnflnis command, a line-num argument value, and press Enter to place a T1 or E1 line in service. Specify the line-num argument in the range from 1 to 8.


Note If the VISM card is rebooted, this information configuration using this command is lost.


Placing T1 and E1 Lines Out of Service

Type the cnflnoos command, line-num and oos-method argument values, and press Enter to place a T1 or E1 line out of service. Specify the arguments with the following values:

line-num: In the range from 1 to 8

oos-method:

2 = Forceful

3 = Graceful

Configuring the PXM and VISM Cards Clocking Source

Complete the following steps to configure the clocking source on your PXM and VISM cards.


Note Refer to "VISM and VISM-PR Card Clocking Options," and the "Expanded Clock Source Selection" section for additional instructions on using the commands and specifying argument values to configure the clocking source on your PXM and VISM cards.



Step 1 Examine the entire configuration of the MGX 8000 Series platform to determine the single clock source.

The type of equipment connected to the VISM T1 or E1 lines may dictate this choice. If the selected clock source is from one of the VISM T1 or E1 lines, that line must be connected to port 1 of the VISM back card. See Figure 1-3 for more information on VISM back cards and port locations.

Step 2 Type the cnfclksrc command, slot-num.port-num, and clk-type argument values, and press Enter to configure the PXM card clock source. Specify the arguments with the following values:

slot-num.port-num:

slot-num = 7 or 8, port-num = 1 to n.


Note Ensure that you type the period with no spaces on either side, between the slot-num argument value and the port-num argument value.


clk-type argument values:

P = Primary

S = Secondary

N = Null (no external clocking source; use the PXM card's internal crystal)

Specify the cnfclksrc command argument values according to the following rules:

If the clock source is the external BITS clock (a T1 or E1 port on the PXM back card), specify the configuration as:

cnfclksrc 7.35 P


Note Type 7 for the slot number regardless of the PXM card's location in the chassis. Type 35 for the port number—the BITS port is always port 35.


If the clock source is an external signal on one of the PXM OC3 ports, specify the configuration as:

cnfclksrc 7.n P


Note Type 7 for the slot number regardless of the PXM card's location in the chassis. The n port parameter value is the OC3 port number in the range 1 to 4.


If the clock source is the PXM's internal crystal and no other clock source has been specified, do not configure the clock source. The crystal is the automatic default.

If you want to change the clocking source from external to the PXM card's internal crystal, specify the configuration as:

cnfclksrc 7.X N


Note Type 7 for the slot number regardless of the PXM card's location in the chassis. The X argument value is the either 35 or the OC3 port number, depending upon which is the currently specified source. The null port number argument value cancels the previous configuration and returns the clocking source to the default internal crystal.


If the clock source is from a line on a VISM card, specify the configuration as:

cnfclksrc y.1 P


Note The y argument value is the actual slot number of the VISM card. Always type 1 for port argument value, which represents the line number in this configuration. VISM-PR cards do not have this requirement.


Step 3 Type the cnfln command, the line-num, line-code, line-length, clock-source, line-type, and loop-detection argument values, and press Enter to configure the clocking option defined in Step 2 on your VISM card. Specify the arguments with the following values:

line-num: In the range from 1 to 8

line-code:

2 = B8ZS for T1

3 = HDB3 for E1

4 = AMI for T1 or E1

line-length:

8 = E1 lines with AX-SMB-8E1 and AX-R-SMB-8E1 back card types

9 = E1 lines with AX-RJ48-8E1 and AX-R-RJ48-8E1 back card types

In the range from 10 to 15 = T1 lines

clock-source:

1 = Loop clock—clocking from the T1 or E1 line


Note If the clocking source is from a line on your VISM card, you must configure that line—which must be line 1—as loop clock. Configure all remaining lines on all remaining VISM cards as local.


2 = Local—clocking from the PXM card


Note You must configure all lines on all VISM cards as local if the clocking source to the VISM cards is from the PXM card.


line-type:

1 = DSx1ESF

2 = DSx1D4

3 = E1

4 = E1CRC

5 = E1MF

6 = E1MFCRC

7 = E1 clear

loop-detection:

1 = Disabled

2 = Enabled


Note You must include all argument values when using the cnfln command; however, the line-num and clock-source are the only relevant arguments for configuring the clocking source on your VISM cards.


You have completed configuring the clocking source for your PXM and VISM cards. Proceed to the "Configuring DS0 Channels" section.


Configuring the PXM1E or PXM45 Card as Clocking Source

Use the cnfncdpclksrc command to configure the PXM1E or PXM45 card as the primary clock source.

Use the following commands to display and verify your configuration:

dspncdpclkinfo

dspncdpclksrc

Refer to the "Related Documentation" section for the appropriate document to use the commands in this section.

Configuring DS0 Channels

You are now ready to configure the 24 (T1) or 31 (E1) DS0 channels on the VISM card's T1 or E1 lines. Table 4-3 describes the VISM/VISM-PR DS0 density when the cards are used in combination with the supported codecs.

Table 4-3 VISM/VISM-PR DS0 Density with Codec Support 

Codec
VISM
VISM-PR
T1
E1
T1
E1

G.711

192

248

192

248

G.723

144

144

G.726

145

145

192

248

G.729

145

145

192

248


You must complete the following tasks to configure a DS0 channel:

1. Add and configure DS1 line and DS0 endpoints.

2. Configure CCS or CAS signaling.

Add and Configure DS1 Lines and DS0 Endpoints

Complete the following steps to add and configure a DS1 line and DS0 endpoints:


Step 1 Type the addendpt command, endpt-num, ds1-num, and ds0-num argument values, and press Enter to add a DS1 line and a DS0 endpoint. This step ensures that a call with a specified endpoint is tied to a specific line and channel. Specify the arguments with the following values.


Note If you choose CAS signaling for a VISM/VISM-PR E1 line, the supported operating modes are AAL2 trunking and VoIP trunking.


endpt-num:

For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 2:

For VISM T1, in the range from 1 to 192

For VISM E1, in the range from 1 to 248

For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 4:

For VISM-PR, in the range from 1 to 144

ds1-num: The physical line number in the range 1 to 8

ds0-num:

For T1 lines, from 1 to 24

For non-CAS E1 lines, from 1 to 31

For CAS E1 lines, from 1 to 15 and 17 to 31


Note You must specify DS0 16 for E1 lines if your application requires CAS signaling.


Step 2 Type the addendpts command, start-endpt, start-line-num, start-ds0-num, and endpt-quantity argument values, and press Enter to add a number of endpoints in one command. Specify the arguments with the following values:

start-endpt:

For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 2:

For VISM T1, in the range from 1 to 192

For VISM E1, in the range from 1 to 248

For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 4:

For VISM-PR, in the range from 1 to 144

start-line-num (DS1 line): In the range from 1 to 8

start-ds0-num (DS0 channel):

For T1 lines, from 1 to 24

For non-CAS E1 lines, from 1 to 31

For CAS E1 lines, from 1 to 15 and 17 to 31

endpt-quantity:

For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 2:

For VISM T1, in the range from 1 to 192

For VISM E1, in the range from 1 to 248

For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 4:

For VISM-PR, in the range from 1 to 144

Step 3 Type the addendptloop command, an endpt-num argument value, and press Enter to place a specific endpoint—and so a specific DS1/DS0—into the loopback state in the TDM direction. Specify the endpt-num argument value from the following ranges:

For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 2:

For VISM T1, in the range from 1 to 192

For VISM E1, in the range from 1 to 248

For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 4:

For VISM-PR, in the range from 1 to 144

Step 4 Type the cnfds0loop command, line-num, ds0-num, and loopback-type argument values, and press Enter to place a specific DS1/DS0 into one of three loopback states. Specify the arguments with the following values:

line-num: In the range from 1 to 8

ds0-num:

In the range from 1 to 31 for E1 lines

In the range from 1 to 24 for T1 lines

loopback-type:

1 = No loopback

2 = Remote loopback

3 = Local loopback

You have completed adding and configuring a DS1 line and DS0 endpoints. Proceed to one of the following sections:

"Configuring TDM Side Signaling for Applications Using CCS" section.

"Configuring TDM Side Signaling for Applications Using CAS" section.


Configuring TDM Side Signaling for Applications Using CCS


Note If your application requires CAS signaling, proceed to the "Configuring TDM Side Signaling for Applications Using CAS" section.


CCS signaling uses a dedicated channel on a DS1 line to carry the signaling for the other channels on the line. You must identify the signaling channel to the VISM card. CCS signaling is used for the following operating modes:

VoIP trunking.

AAL2 trunking—Signaling is transported across the trunk as Q.931 messages in ATM cells using AAL5.

Switched AAL2 PVC—Signaling is backhauled to the call agent using Q.921 frames on the TDM side and RUDP/UDP/IP/Q.2931 on the call agent side.

Complete the following steps to add and configure CCS signaling:


Step 1 Type the addccs command, line-num, ds0-num, and lcn argument values, and press Enter to add a CCS channel to your VISM card. Specify the arguments with the following values:

line-num: In the range from 1 to 8

ds0-num:

In the range from 1 to 24 for T1

In the range from 1 to 31 for E1

lcn: In the range from 131 to 510

Step 2 If you are configuring CCS for the AAL2 trunking operating mode, the CCS configuration is complete. Proceed to the "Configuring Bearer Processing" section. If you are configuring CCS for the VoIP switching operating mode, you must create a Q.921 link access protocol for the D channel (LAPD) link for the channel and specify its argument values. Proceed to Step 3.

Step 3 Type the addlapd command, line-num, ds0-num, |lapd-side| and |lapd-app-type| argument values, and press Enter to add an ISDN PRI channel on a DS1/DS0.

Specify the arguments with the following values:

line-num: Type the value used in Step 1.

ds0-num: Type the value used in Step 1.

|lapd-side|:

1 = Network (default)

2 = User

|lapd-app-type|:

1 = PRI (default)

2 = GR-303 (currently unsupported)

Step 4 Type the cnflapdtype command, line-num, ds0-num, and lapd-type argument values, and press Enter to specify the LAPD stack type. Specify the arguments with the following values:

line-num: Type the value used in Step 1.

ds0-num: Type the value used in Step 1.

lapd-type:

1 = ITU

3 = ATT5ESSPRA

4 = ATT4ESS

6 = NTDMS100PRA

7 = VN2 or 3

8 = INSNet

9 = TR6MPC

10 = TR6PBX

12 = AUSP

13 = NIL

14 = SSETSI

15 = BC303TMC

16 = BC303CSC

17 = NTDMS250

18 = Bellcore

19 = NI2

Step 5 Type the cnflapdwinsize command, line-num, ds0-num, and iframe-num argument values, and press Enter to specify the LAPD window size. The iframe-num value is the maximum number of outstanding I-frames that can be accumulated before sending an acknowledgment. Specify the arguments with the following values:

line-num: Type the value used in Step 1.

ds0-num: Type the value used in Step 1.

iframe-num: In the range from 1 to 127

Step 6 Type the cnflapdretrans command, line-num, ds0-num, and n200 argument values, and press Enter to specify the maximum allowable frame retransmissions. Specify the arguments with the following values:

line-num: Type the value used in Step 1.

ds0-num: Type the value used in Step 1.

n200: In the range from 1 to 10

Step 7 Type the cnflapdtimer command, line-num, ds0-num, frame-trans-time, and frame-exchange-time argument values, and press Enter to specify the two LAPD timers. Specify the arguments with the following values:

line-num: Type the value used in Step 1.

ds0-num: Type the value used in Step 1.

frame-trans-time (time, at the end of which, a frame transmission can be initiated):

1000 to 1023000 for PRI (specify in increments of 50 ms)

100 to 350 for GR-303 (specify in increments of 50 ms)


Note The specified value for frame-trans-time must be less than the specified value for frame-exchange-time.


frame-exchange-time (maximum time allowed without frames being exchanged) argument values:

1000 to 1023000 for PRI (specify in increments of 10000 ms)

10000 to 300000 for GR-303 (specify in increments of 10000 ms)

You have completed adding and configuring CCS. Proceed to the "Configuring Bearer Processing" section.


Configuring TDM Side Signaling for Applications Using CAS


Note If your application requires CCS, see the "Configuring TDM Side Signaling for Applications Using CCS" section.


CAS signaling is used for the following operating modes:

VoIP trunking.

VoIP switching—TDM side signaling is translated in xGCP messages to the call agent.

AAL2 trunking—Signaling is transported across the trunk as Q.931 messages in AAL2 cells using AAL5.

Switched AAL2 PVC—Signaling is backhauled to the call agent using xGCP on the TDM side and Reliable User Datagram Protocol (RUDP)/User Datagram Protocol (UDP)/IP/Q.2931 on the call agent side.

Complete the following steps to add and configure CAS signaling.


Note If you choose CAS signaling for a VISM/VISM-PR E1 line, the supported operating modes are AAL2 trunking and VoIP trunking. In addition Step 1 through Step 8 and Step 11 through Step 13 are used only in the VoIP switching and switched AAL2 PVC operating modes.



Step 1 Type the cnfcasparamsource command, endpt-num and cas-source argument values, and press Enter to configure the source of CAS-related timer parameters for a specified endpoint. Specify the arguments with the following values:

endpt-num:

For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 2:

For VISM T1, in the range from 1 to 192

For VISM E1, in the range from 1 to 248

For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 4:

For VISM-PR, in the range from 1 to 144

cas-source:

1 = CAS application file

2 = Current VISM MIB file


Note The cnfcasparamsource command permits different CAS-related timer values for different endpoints, but all are associated with the same CAS variant.


Step 2 Type the cnfcasonhooktime command, endpt-num and onhooktime argument values, and press Enter to specify the minimum time an on hook-pattern must be present to be recognized as an on-hook signal. Specify the arguments with the following values:

endpt-num: Type the value used in Step 1.

onhooktime: In the range from 10 to 1000

Step 3 Type the cnfcasoffhooktime command, endpt-num and offhooktime argument values, and press Enter to specify the minimum time an off-hook pattern must be present to be recognized as an off-hook signal. Specify the arguments with the following values:

endpt-num: Type the value used in Step 1.

offhooktime: In the range from 10 to 1000

Step 4 Type the cnfcaswinktime command, endpt-num, min-make-time, max-make-time, and min-break-time argument values, and press Enter to specify the minimum and maximum make times and the minimum break time. A wink begins with an on-hook pattern, goes to off-hook, and returns to on-hook. Specify the arguments with the following values:

endpt-num: Type the value used in Step 1.

min-make-time: In the range from 10 to 1000

max-make-time: In the range from 10 to 3000

min-break-time: In the range from 10 to 1000


Note All three make and break duration time argument values must be observed for the signaling sequence to be recognized as a wink.


Step 5 Type the cnfcasglaretime command, endpt-num and glaretime argument values, and press Enter to specify the glare time. Specify the arguments with the following values:

endpt-num: Type the value used in Step 1.

glaretime: In the range from 10 to 1000

Step 6 Type the cnfcasguardtime command, endpt-num and guardtime argument values, and press Enter to specify the guard time. Specify the arguments with the following values:

endpt-num: Type the value used in Step 1.

guardtime argument values:

In the range from 10 to 1000

Step 7 Type the cnfcasdialdelay command, endpt-num and dial-delay argument values and press Enter to configure the CAS dial delay (wait time).

Dial delay is the time that VISM waits before sending dialing digits after sending an off-hook event.


Note The cnfcasdialdelay command applies to immediate start protocols only.


Specify the arguments with the following values:

endpt-num: Type the value used in Step 1.

dial-delay: In the range from 10 to 1000

Step 8 To configure CAS for the switched AAL2 PVC operating mode, proceed to Step 11. To configure CAS for the AAL2 trunking operating mode, proceed to Step 9.

Step 9 Type the cnfcascode command, endpt-num, |endpt-num|, idle-code, and seized-code argument values and press Enter to specify the idle and seized codes for one or more endpoints. Specify the arguments with the following values:

endpt-num: Type the value used in Step 1.


Note If the |endpt-num| optional argument value is used in combination with this argument, the endpt-num argument value is the first endpoint in a consecutive range of endpoints.


|endpt-num|:

For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 2:

For VISM T1, in the range from 1 to 192

For VISM E1, in the range from 1 to 248

For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 4:

For VISM-PR, in the range from 1 to 144


Note The |endpt-num| optional argument value indicates the last endpoint in a consecutive range of endpoints.


idle-code (4-bit idle code): In the range from 0 to 15 represents the four A, B, C, and D signaling as bits 3, 2, 1, and 0 respectively with bit 3 the most significant.

seized-code (4-bit seized code): In the range from 0 to 15 represents the four A, B, C, and D signaling as bits 3, 2, 1, and 0 respectively with bit 3 the most significant.

Step 10 Type the cnfds0localcas command, line-num, ds0-num, local-cas-enable, and local-cas-pattern argument values, and press Enter to configure a local CAS bit pattern for a T1 line and DS0.


Note The cnfds0localcas command is not allowed if the line is E1 or not enabled, or the DS0 is in a remote loop state, or if the line signaling type is CAS.


Specify the arguments with the following values:

line-num: 1 to 8 (T1 lines only)

ds0-num: 1 to 24

local-cas-enable:

1 = Enable

2 = Disable

local-cas-pattern: In the range from 1 (default) to 15


Note If the local-cas-enable argument value = 1, you must specify a local-cas-pattern argument value.


Step 11 Type the addcasvar command, var-name, file-name and |source| argument values, and press Enter to add a CAS variant to your VISM card.


Note A file containing the CAS variant information must be downloaded to your MGX 8000 Series PXM card using a separate application (TFTP) before you can execute this command.


Specify the arguments with the following values:

var-name (name of the CAS variant): A text string of 1 to 64 alphanumeric characters.

file-name:

wink_did_dod.o = wink start

ground_start.o = ground start

wink_did_dod_mf.o = wink start multifrequency

q50.o = Q.50

fgd_ea_incoming.o = for endpoints connected to an end office

fgd_ea_outgoing.o = for endpoints connected to an access carrier

fgd_os_e911.o = for endpoints connected to FDG OSS (Feature group D operator services system.

loop_start.o = loop start

delay_did_dod.o = dial delay, DTMF

delay_did_dod_mf.o = dial delay, MF

immed_did_dod.o = immediate start

immed_did_dod_mf.o = immediate start, MF

In the range from 1 to 32 alphanumeric characters—user configured files only.

|source| (CAS variant file location):

1 = Unspecified. If TFTP domain is configured, the location is the TFTP server. If not found in the TFTP server, the file is treated as built-in.

2 = User configured (built-in) file location.

3 = External—resides on the TFTP server.

Step 12 Type the cnfcasvar command, var-name, country-code, partial-time, critical-time, and interdigit-timeout argument values, and press Enter to configure a CAS variant and CAS timing parameters for the variant added in Step 11. Specify the arguments with the following values:

var-name: Type the value used in Step 11.

country-code: The two-character country code of the variant.

partial-time (partial dial time): In the range from 10 to 10000, in increments of 10 seconds.

critical-time (critical timing): In the range from 0 to 10000, in increments of 10 seconds.

interdigit-timeout (interdigit timeout for MF digits): In the range from 1 to 10 seconds.

Step 13 Type the cnfcasendpt command, endpt-num and var-name argument values, and press Enter to associate an endpoint with a CAS variant. Specify the arguments with the following values:

endpt-num: Type a value used in Step 9.

var-name: Type the value used in Step 11.

You have completed adding and configuring CAS signaling. Proceed to the "Configuring Bearer Processing" section.


Configuring Bearer Processing

Processing of the bearer payload takes place either upon receipt of the payload from a T1 or E1 line or prior to transmission over a T1 or E1 line. You must complete the following tasks to configure bearer processing:

1. Configure codecs.

2. Configure ECAN.

3. Configure jitter.

Configuring Codecs

Complete the following steps to assign and configure a codec template:


Step 1 Type the cnfcodectmpl command, a template-num argument value, and press Enter to specify a codec template. Specify the template-num argument value from the following:

1 = G.711u, G.711a, G.726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, and G.729ab codecs, and clear channel


Note Template 1 is not supported for the VoIP operating mode.


2 = G.711u and G.711a codecs, and clear channel


Note The cnfcodectmpl command is included in the "Allocating Resources" section but is included here for your convenience.


3 = G.711u, G.711a, G.726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, and G.729ab codecs, clear channel, and T.38 fax transfer

4 = G.711u, G.711a, G. 726-16k, G.726-24k, G.726-32k, G.726-40k, G.729a, G.729ab, G.723.1-H, G.723.1a-H, G.723.1-L, G.723.1a-L codecs and clear channel

Step 2 Type the cnfcodecparams command, codec-type, codec-pkt-period, |preference, codec-string, and iana-type| argument values, and press Enter to specify various codec parameters for use in the VoIP operating mode.

The packetization period is defined in three separate commands depending upon the ATM method used:

Use the cnfcodecparams command for VoIP switching applications. Complete this step.

Use the addcid command for AAL2 trunking applications. See the "Configuring AAL2 Trunking Operating Mode Parameters" section.

Use the addrtpcon command for AAL2 trunking applications.

Use the cnfprofelemvoice command for switched AAL2 PVC applications. See the "Configuring Switched AAL2 PVC Operating Mode Parameters" section.

Specify the arguments with the following values:

codec-type: In the range from 1 to 14.

codec-pkt-period:

10

20

30

40

60

preference:

0 = Ignore preference

In the range from 1 (highest) to 13 (lowest).

codec-string: In the range from 1 to 20 ASCII characters.

iana-type (IANA registered codec type): In the range from 0 to 96.

Step 3 Type the cnfcodecneg command, the codec-priority argument value, and press Enter to specify a codec preference order when there are several codec lists—from the call agent local connection option (LCO) list, local MIB, or a list received from the remote gateway in the session description protocol (SDP) data. Specify the codec-priority argument value with one of the following:

1 = LCO list, remote SDP data list, local MIB

2 = LCO list, local MIB, remote SDP data list

3 = Remote SDP data list, LCO list, local MIB

4 = Remote SDP data list, local MIB, LCO list

5 = Local MIB, LCO list, remote SDP data list

6 = Local MIB, remote SDP data list, LCO list

You have completed assigning and configuring the codec template. Proceed to the "Configuring ECAN" section.


Configuring ECAN

Complete the following steps to enable and configure echo cancellation (ECAN) on a line-by-line basis:


Step 1 Type the cnfecanenable command, line-num and ecan-enable argument values, and press Enter to enable (or disable) ECAN for a line. Specify the arguments with the following values:

line-num: In the range from 1 to 8.

ecan-enable:

1 = Disable

2 = Enable

Step 2 Type the cnfecanrec command, line-num and res-echo-control argument values, and press Enter to set the residual echo control. Specify the arguments with the following values:

line-num: Type the value used in Step 1.

res-echo-control:

1 = Cancel only

2 = Suppress residual

4 = Comfort noise

Step 3 Type the cnfecantail command, line-num and max-ecan-tail argument values, and press Enter to specify the ECAN algorithm's maximum tail length. Specify the arguments with the following values:

line-num: Type the value used in Step 1.

max-ecan-tail (defined in milliseconds):

24

32

48

64

80

96

112

128

Step 4 Type the cnferl command, the echo-ret-loss argument value, and press Enter to specify the ECAN algorithm's return echo loss applied by ECAN DSPs, in decibels. Specify the echo-ret-loss argument with one of the following values:

echo-ret-loss:

1 = 0 dB

2 = 3 dB

3 = 6 dB

4 = 1 dB

Step 5 Type the cnfconvbdpol command, lcn, carrier-loss-pol, and cac-reject-pol argument values, and press Enter to specify the fax/modem upspeed connection admission control (CAC) failure and carrier loss policies for a channel. Specify the arguments with the following values:

lcn (logical channel number): In the range from 131 to 510.

carrier-loss-pol (carrier loss policy):

1 = Revert to the previous codec

2 = Maintain the upspeed codec

3 = Unspecified

cac-reject-pol (CAC rejection policy):

1 = Delete the connection

2 = Maintain the connection

3 = Unspecified

You have completed enabling and configuring ECAN on your lines. Proceed to the "Configuring Jitter" section.


Configuring Jitter

You can dejitter the voice payload to improve the quality of the egress voice stream.


Note If your application uses the AAL2 trunking operation mode, you cannot change the jitter parameters while the CIDs are active.


Complete the following steps to specify and configure jitter mode:


Step 1 Type the cnfjtrmode command, the jitter-mode argument value, and press Enter to set the jitter mode. Specify the jitter-mode argument with one of the following values:

1 = Fixed buffer size; recommended value if the jitter amount is expected to be constant or near constant.

2 = Adaptive; you specify a starting buffer size and VISM adapts the buffer size to handle jitter.

Step 2 If you chose a fixed buffer size in Step 1, you have completed configuring jitter. Proceed to the "Configuring the ATM Network Side" section. If you chose an adaptive buffer size in
Step 1, proceed to Step 3.

Step 3 Type the cnfjtrinitdelay command, the jitter-buffer-size argument value, and press Enter to specify the starting buffer size. Specify the jitter-buffer-size argument (defined in bytes) with a value from one of the following ranges:

For template numbers 1, 3, and 4, in the range from 0 to 100 in increments of 10.

For template number 2, in the range from 0 to 100 in increments of 5.

You have completed configuring jitter. Proceed to the "Configuring the ATM Network Side" section.


Configuring PNNI for AAL1/AAL2 SVCs

Use the cnfpncon command to configure Private Network-to-Network Interface (PNNI) priority routing for AAL1/AAL2 switched virtual circuits (SVCs). Refer to "CLI Commands," for more information on using the cnfpncon command.

Configuring the ATM Network Side

Configuring the ATM network side consists of setting up ATM PVCs across the network and providing the mechanism by which calls are routed over the correct PVC. The PVC configuration depends on the VISM operating mode you require for your application.

The Voice over IP switching operating mode requires you to set up an AAL5 PVC between the VISM card and the PXM card, and then to an edge router. A single PVC is set up (a secondary PVC may also be set up for redundancy). The PVC is used for bearer voice traffic and gateway protocol communication between VISM and the call agent. The router extracts the IP frames from the ATM cells and routes the frames accordingly.

The AAL2 trunking operating mode requires you to set up as many as 64 AAL2 PVCs connected to each remote location supported by the network. The PVCs carry voice traffic and optional CAS signaling.

Each PVC is set up as three segments consisting of two local segments and one network segment. The local segments are set up between the two VISM cards (one at the end of the PVC) and their respective PXM cards. The network segment is set up between the two PXM cards across the network. Refer to the Cisco MGX 8250 and MGX 8230 Release l installation and configuration guides for more information.

In AAL2 trunking operating mode, you must bind endpoints to specific DS0s using the addendpoint(s) commands. You must also create CIDs (connection identifiers) for each PVC that binds the endpoints to the CID and a PVC. This ensures that calls arriving at a specific DS0 are automatically routed to the preconfigured CID and PVC over nailed-down trunks. There is no switched or call agent involvement.

The switched AAL2 PVC operating mode requires you to set up as many as 64 AAL2 PVCs connected to each remote location supported by the network. The PVCs carry voice traffic across the ATM network.

Each PVC is set up as three segments consisting of two local segments and one network segment. The local segments are set up between the two VISM cards (one at the end of the PVC) and their respective PXM cards. The network segment is set up between the two PXM cards across the network. Refer to the Cisco MGX 8850 Release 1 installation and configuration guides for more information.

In switched AAL2 PVC operating mode, you must bind endpoints to specific DS0s using the addendpoint(s) commands. You must also create VCCIs (virtual circuit connection identifiers), which identify each PVC and associate each PVC with a specific remote ATM address. At call setup time, the call agent informs VISM which VCCI to use for the call and instructs VISM to set up a CID for transport across the VCCI. This ensures that the binding of a DS0 to a CID and PVC is dynamic by using of the called address.

Configuring PVC Connections for All Operating Modes

Complete the following steps to configure PVC connections for all operating modes:


Step 1 Type the addcon command, local-vci, pref-level, pvc-conn-type, conn-app, peak-cell-rate, conn-type, |remote-conn-id, service-type, sus-cell-rate, and max-burst-rate| argument values, and press Enter to add an ATM PVC between the VISM card and the MGX 8000 Series platform PXM card. Specify the addcon command arguments with the following values:

local-vci: In the range from 131 to 510.

pref-level:

1 = Primary

2 = Secondary (for redundancy)

pvc-conn-type:

1 = AAL5

2 = AAL2

3 = AAL1

conn-app:

1 = Control

2 = Bearer

3 = Signaling

peak-cell-rate (defined as cells per second):

In the range from 1 to 80000 for VoIP bearer.

In the range from 1 to 20000 for VoIP control.

In the range from 1 to 50000 for AAL2 T1.

In the range from 1 to 60000 for AAL2 E1.

In the range from 1 to 400 for AAL2 signaling (trunking).

In the range from 1 to 90000 for AAL5 bearer.

In the range from 1 to 10000 for AAL5 control.

conn-type (type of connection):

1 = Master

2 = Slave (default)

|remote-conn-id| (remote connection identifier):

Type the value in the following format: nodename.slot.port.vpi.vci


Note Use the optional |remote-conn-id| argument only if you selected the conn-type argument value of 1 (master).


|service-type|:

1 = Constant bit rate (CBR)

2 = Variable bit rate real time, VBR (RT)

3 = Variable bit rate non-real time, VBR (NRT)

4 = VBR (RT) 3

5 = VBR (RT) 2

6 = VBR (NRT) 2

7 = VBR (NRT) 3

|sus-cell-rate| (sustainable cell rate):

In the range from 1 to the value you specified for the peak-cell-rate argument.

|max-burst-rate| (maximum number of cells transmitted at the peak cell rate):

In the range from 1 to 10 times the value you specified for the sus-cell-rate argument.

Step 2 Type the cnfcon command, lcn, peak-cell-rate, service-type, sus-cell-rate, and max-burst-rate argument values and press Enter if you need to refine the configuration parameters of the connection added in Step 1 and identify the connection by the logical channel number. Specify the arguments with the following values:

lcn: Type the value you entered for the local-vci argument in Step 1.

peak-cell-rate (defined as cells per second):

In the range from 1 to 80000 for VoIP bearer.

In the range from 1 to 20000 for VoIP control.

In the range from 1 to 50000 for AAL2 T1.

In the range from 1 to 60000 for AAL2 E1.

In the range from 1 to 400 for AAL2 signaling (trunking).

In the range from 1 to 90000 for AAL5 bearer.

In the range from 1 to 10000 for AAL5 control.


Note The peak-cell-rate argument value cannot be changed if the calls or connections for signaling and control are active.


service-type:

1 = Constant bit rate (CBR)

2 = Variable bit rate real time—VBR (RT)

3 = Variable bit rate non-real time—VBR (NRT)

4 = VBR (RT) 3

5 = VBR (RT) 2

6 = VBR (NRT) 2

7 = VBR (NRT) 3

sus-cell-rate (sustained cell rate, defined as cells per second):

In the range from 15 to the value you specified for the peak-cell-rate argument.

max-burst-rate (maximum burst rate, defined as cells per second):

In the range from 1 to 10 times the value you specified for the sus-cell-rate argument.

Step 3 Type the addconloop command, the lcn argument value, and press Enter to set a loopback on a VISM PVC with the loopback in the direction of cellbus. Specify the lcn argument value with a value in the range from 131 to 510.


Note You can use the delconloop command to remove a loopback on a VISM PVC.


You have completed configuring PVC connections. Proceed to one of the following sections, as appropriate:

Configuring VoIP Switching/Trunking Operating Mode Parameters.

Configuring AAL2 Trunking Operating Mode Parameters.

Configuring Switched AAL2 PVC Operating Mode Parameters.


Configuring VoIP Switching/Trunking Operating Mode Parameters

Complete the following steps to configure VoIP switching operating mode parameters:


Step 1 Type the cnfconprotect command, lcn, protect-enable, lock-state, and second-lcn argument values, and press Enter to configure primary and secondary PVCs to provide protection in the event of a PVC failure. Specify the argument with the following values:

lcn: In the range from 131 to 510.

protect-enable:

1 = On

2 = Off

lock-state:

1 = Unlock

2 = Lock

second-lcn (secondary LCN): In the range from 131 to 510.

Step 2 Type the cnfdeftos command, control-prec, control-tos, |bearer-prec|, and |bearer-tos| argument values, and press Enter to configure the type of service for both control and bearer IP packets.


Note If you do not execute the cnfdeftos command, card level default values are used.


Specify the arguments with the following values:

control-prec: In the range from 0 to 7 (default = 3)

control-tos (type of service for control packets):

0 (default)

1

2

4

8

bearer-prec: In the range from 0 to 7 (default = 5)

bearer-tos (type of service for bearer packets):

0 (default)

1

2

4

8


Note The bearer-prec and bearer-tos arguments are used during call setup in cases where values are not supplied by a call agent.


Step 3 Type the cnfvoiptransparams command, dtmf-trans, cas-trans, and |event-neg-enable|, |event-neg-pol|, and |sid-type| argument values, and press Enter to configure the VoIP transportation characteristics across the network. Specify the arguments with the following values:

dtmf-trans (DTMF tones relayed to the other endpoint):

1 = On

2 = Off

cas-trans (CAS bits relayed to the other endpoint):

1 = On

2 = Off

event-neg-enable (Optional):

1 = On

2 = Off

event-neg-pol (Optional; event negotiation policy):

1 = None

2 = Proprietary (default)

3 = All

sid-type (Optional; SID payload type): In the range from 0 to 255 (default = 13)

You have completed configuring the VoIP switching operating mode parameters. Proceed to the "Configuring the Call Agent Interface" section.


Configuring AAL2 Trunking Operating Mode Parameters

Complete the following steps to configure AAL2 trunking operating mode parameters:


Step 1 Type the addcid command, endpt-num, lcn, cid-num, codec-type, profile-type, profile-num, |vad-enable, vad-init-timer, ecan-enable, type-3-red, cas-trans, dtmf-trans, idle-code-sup, and pkt-period| argument values, and press Enter to add a channel identifier (CID) to an AAL2 PVC.

The CID is a mechanism within AAL2 that allows multiple calls to be transported across a single AAL2 PVC. The addcid command binds an endpoint to a logical channel (PVC). Specify the arguments with the following values:

endpt-num (endpoint to be related to the LCN/CID pair being added):

For template number 1:

For VISM, in the range from 1 to 145

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 2:

For VISM T1, in the range from 1 to 192

For VISM E1, in the range from 1 to 248

For template number 3:

For VISM, in the range from 1 to 120

For VISM-PR T1, in the range from 1 to 192

For VISM-PR E1, in the range from 1 to 248

For template number 4:

For VISM-PR, in the range from 1 to 144

lcn (LCN of the LCN/CID pair): In the range from 131 to 510.

cid-num (CID of the LCN/CID pair): In the range from 8 to 255.

codec-type:

1 = G.711u

2 = G.711a

3 = G.726-32k

4 = G.729a

5 = G.729ab

6 = Clear channel (VAD must be off)

7 = G.726-16k

8 = G.726-24k

9 = G.726-40k

11 = G.723-H

12 = G.723a-H

13 = G.723.1-L

14 = G.723.1a-L

profile-type (used for the CID):

1 = International Telecommunication Union (ITU) I.366.2

3 = Custom

profile-num:

1 = for the ITU profile

2 = for the ITU profile

3 = for the ITU profile

7 = for the ITU profile

8 = for the ITU profile

12 = for the ITU profile

100 = for custom profiles

101 = for custom profiles

110 = for custom profiles

200 = for custom profiles

vad-enable:

1 = On

2 = Off

vad-init-timer (holdover timer; in milliseconds): In the range from 250 to 65535 (default = 250)

ecan-enable:

1 = On (default)

2 = Off

type-3-red (triple redundancy protection for CAS type 3 packets):

1 = On

2 = Off

cas-trans:

1 = On (default)

2 = Off

dtmf-trans (DTMF tone transport as AAL2 type 3 packets):

1 = On (default)

2 = Off


Note The dtmf-trans argument value must be set to 1 (on) when the codec-type is configured for codecs other than G.711 and G.726.


idle-code-sup (idle code suppression):

1 = On

2 = Off

pkt-period (defined in milliseconds):

10

The pkt-period argument requires you to configure packetization in the following ways for the other two operating modes:

Use the cnfcodedecparams for the VoIP operating mode.

Use the cnfprofelemvoice command for the switched AAL2 PVC operating mode. See the "Configuring Switched AAL2 PVC Operating Mode Parameters" section for more information.

Step 2 Type the cnfaal2subcellmuxing command, the mux-enable argument value, and press Enter to enable or disable subcell multiplexing. Specify the mux-enable argument with one of the following values:

1 = On

2 = Off

You have completed configuring the AAL2 trunking operating mode parameters.


Configuring Switched AAL2 PVC Operating Mode Parameters


Note The switched AAL2 PVC operating mode is not supported in VISM Release 3.0.


You must complete the following tasks to configure the switched AAL2 PVC operating mode parameters:

1. Configure a virtual circuit connection identifier (VCCI).

2. Modify the AAL2 PVC profile table.


Note Modifying the AAL2 PVC profile table is not mandatory.


3. Configure AAL2 PVC parameters.

Configuring a Virtual Circuit Connection Identifier

Complete the following steps to configure a VCCI for the switched AAL2 PVC operating mode:


Step 1 Type the cnfconvcci command, lcn, vcci-num, addr-type, and |fe-addr| argument values, and press Enter to create a new VCCI with an associated logical channel number and a remote ATM address. Specify the arguments with the following values:

lcn: In the range from 131 to 510.

vcci-num: In the range from 0 to 65535.

addr-type (address type):

1 = Not applicable

2 = Network service access point (NSAP); a 20-byte hexadecimal address

3 = E.164 public network addressing; a 1- to 15-byte decimal address

4 = Gateway ID; a 1- to 64-byte ASCII character address

5 = Unspecified

|fe-addr|: The actual remote address

Step 2 Repeat Step 1, as needed, to configure VCCIs on other LCNs.

You have completed configuring VCCIs for the switched AAL2 PVC operating mode. Proceed to the "Modifying the AAL2 PVC Operating Mode Profile Table" section.


Modifying the AAL2 PVC Operating Mode Profile Table

A profile table is associated with each AAL2 operating mode. This profile table specifies the encoding format, which tells the card how to interpret the packets.

You can use the dspaal2profile command to see the values for a profile type. Example 4-1 shows the default values for ITU profile type 1.

Example 4-1 Default Values for ITU Profile 1

nodename.1.28.VISM8.a > dspaal2profile 1 1

	UUI      Packet                          Packet  Seq. No.
Codepoint   Length                           Time   Interval
  Range    (octets)  Codec       SID     M   (ms)     (ms)  
   0-15       40     PCMU        No SID  1     5        5    
   0-15       40     PCMA        No SID  1     5        5 

Table 4-4 describes the fields shown in the display.

Table 4-4 dspaal2profile Field Descriptions  

Field
Description

UUI Codepoint Range

User-to-user indication.

Packet Length (octets)

Packet length for the encoding format.

Codec

Type of codec.

SID

Silence insertion descriptor.

M

Multiple of the service data unit (SDU) for the profile. The SDU is the smallest packet length.

Packet Time (ms)

Voice packetization period.

Seq. No. Interval (ms)

Sequence number interval.


VISM/VISM-PR creates the profile table with the defaults that are listed in Table 4-5. This table is a summary of the output from the dspaal2profile command.

Table 4-5 AAL2 Operating Mode Profiles 

Profile Type
Profile Number
UUI Codepoint Range
Packet Length
Voice codec
VAD
M
Voice Packet Period
Sequence Number Interval
Voice Band Data Codec
Voice Band Data Packet Period

ITU

1

0-15

40

G.711u

Off

1

5

5

G.711u

5

ITU

2

0-15

40

G.711u

SIDG

1

5

5

G.711u

5

ITU

3

0-15

0-15

0-15

0-15

0-15

40

10

15

20

25

G.711u

G.726-16k

G.726-24k

G.726-32k

G.726-40k

SIDG

1

1

1

1

1

5

5

5

5

5

5

5

5

5

5

G.711u

5

ITU

7

0-15

0-15

0-15

40

10

10

G.711u

G.729a

G.729ab

SIDG

Off

SID729

1

1

1

5

10

10

5

5

5

G.711u

5

ITU

8

0-15

0-15

0-15

0-15

40

20

10

10

G.711u

G.726-32k

G.729a

G.729ab

Off

Off

Off

SID729

1

1

1

1

5

5

10

10

5

5

5

5

G.711u

5

ITU

12

0-15

0-15

0-15

0-15

24

24

20

20

G.723.1-H

G.723.1a-H

G.723.1-L

G.723.1a-L

Off

SID723

Off

SID723

1

1

1

1

30

30

30

30

5

5

5

5

G.711u

5

Custom

100

0-7

8-15

40

40

G.711u

G.726-32

SIDG

SIDG

1

2

5

10

5

5

G.711u

5

Custom

101

0-7

8-15

8-15

8-15

40

40

10

10

G.711u

G.726-32

G.729a

G.729ab

Off

Off

Off

SID729

1

2

1

1

5

10

10

10

5

5

5

5

G.711u

5

Custom

110

0-7

8-15

8-15

8-15

40

40

30

30

G.711u

G.726-32

G.729a

G.729ab

SIDG

SIDG

Off

SID729

1

2

3

3

5

10

30

30

5

5

5

5

G.711u

5

Custom

200

0-15

40

Clear channel

Off

40

5

5

G.711u

5


Complete the following steps to assign a profile preference and to modify the packet period and SID values of the profile table, as necessary.


Note Modifying the AAL2 PVC profile table is not mandatory. Proceed to the "Configuring AAL2 PVC Parameters" section if the values shown in Table 4-5 are correct for your application and configuration requirements.



Step 1 Type the cnfprofparams command, profile-type, profile-num, and profile-pref argument values, and press Enter to specify the preference for a given profile during call setup profile negotiation. Specify the arguments with the following values:

profile-type:

1 = ITU

3 = Custom

profile-num:

1 = for the ITU profile

2 = for the ITU profile

3 = for the ITU profile

7 = for the ITU profile

8 = for the ITU profile

12 = for the ITU profile

100 = for custom profiles

101 = for custom profiles

110 = for custom profiles

200 = for custom profiles

profile-pref:

0 = No preference; excludes a profile from negotiation

In the range from 1 (highest) to 9 (lowest)

Step 2 Type the cnfprofelemvoice command, profile-type, profile-num, codec-type, pvoice-pkt-period, and sid argument values, and press Enter to configure the voice profile element for a specified profile. Specify the arguments with the following values:

profile-type: Refer to the options listed in Step 1.

profile-num: Refer to the options listed in Step 1.

codec-type argument values:

1 = G.711u

2 = G.711a

3 = G.726-32k

4 = G.729a

5 = G.729ab

6 = Clear channel (VAD must be off)

7 = G.726-16k

8 = G.726-24k

9 = G.726-40k

11 = G.723.1-H

12 = G.723.1a-H

13 = G.723.1-L

14 = G.723.1a-L

pvoice-pkt-period (defined in milliseconds):

5

10

20

30

40

60

sid:

1 = VAD off

2 = VAD on

3 = SID generic

4 = SID 729

5 = SID 723

Step 3 Type the cnfprofelemvbd command, profile-type, profile-num, codec-type, and vbd-pkt-period argument values, and press Enter to configure the voiceband data element for a specified profile. Specify the arguments with the following values:

profile-type—Refer to the options listed in Step 1.

profile-num—Refer to the options listed in Step 1.

vbd-codec-type—Refer to the options listed in Step 2.

vbd-pkt-period (defined in milliseconds):

5

10

30

Step 4 Type the cnfprofneg command, the codec-priority argument value, and press Enter to specify the priority preference order for the profile lists. Profiles can be from the call agent local connection option (LCO) list, local MIB, or a list received from the remote gateway in the session descriptor protocol (SDP) data. Specify the codec-priority argument value with one of the following:

1 = LCO list, remote SDP data list, local MIB

2 = LCO list, local MIB, remote SDP data list

3 = Remote SDP data list, LCO list, local MIB

4 = Remote SDP data list, local MIB, LCO list

5 = Local MIB, LCO list, remote SDP data list

6 = Local MIB, remote SDP data list, LCO list

You have completed modifying the switched AAL2 PVC operating mode profile table. Proceed to the "Configuring AAL2 PVC Parameters" section.


Configuring AAL2 PVC Parameters

Complete the following steps to configure AAL2 PVC parameters:


Step 1 Type the cnfaal2timerparams command, vad-init-timer and cid-fill-timer argument values, and press Enter to configure the holdover and maximum wait time arguments. Specify the arguments with the following values:

vad-init-timer (defined in milliseconds): In the range from 250 to 65535.

cid-fill-timer (defined in milliseconds): In the range from 5 to 100.

The vad-init-timer is the holdover time before activating silence suppression. The cid-fill-timer is the maximum waiting time for filling up the cell when the next packet is not ready.

Step 2 Type the cnfaal2transparams command, dtmf-trans, cas-bits-trans, and type-3-red argument values, and press Enter to enable or disable three parameters regarding the transport of CAS signaling.

dtmf-trans (transportation of DTMF digits):

1 = On

2 = Off

cas-bits-trans (transportation of CAS bits):

1 = On

2 = Off

type-3-red (transportation of AAL2 Type 3 redundancy packets):

1 = On

2 = Off

You have completed configuring the switched AAL2 PVC operating mode parameters. Proceed to the "Configuring the Call Agent Interface" section.


Configuring the Call Agent Interface


Note The CLI call agent configuration commands are used for the VoIP switching and switched AAL2 PVC operating modes only. If your application requires the AAL2 trunking operating mode, do not use the CLI call agent configuration commands described in this section.


VISM can use one to eight call agents to accomplish the following:

Receive backhauled signaling

Perform call setup

Perform call teardown

VISM uses IP connectivity in order to communicate with the call agents (see Figure 4-2).

Figure 4-2 VISM to Call Agent Communication

Physical connectivity is through a PVC on an MGX 8000 Series platform PXM card's OC-3 port, to a router (in the IP Connectivity cloud in Figure 4-2), and then to the call agents.

Logical IP connectivity is performed by resolving domain name and IP address associations. The associations are accomplished in the following ways:

Statically, by using the CLI call agent configuration commands.

Dynamically, by using an external domain name server (DNS), which is connected to VISM through IP connectivity.

Figure 4-2 shows a TFTP server which also has an IP connection to VISM.

You must complete the following tasks to configure the call agent interface:

1. Configure domain names and IP addresses.

2. Set up call agents and protocols.

3. Configure gateway control protocols.

4. Configure ISDN PRI backhaul (optional).

Configuring Domain Names and IP Addresses

Complete the following steps to configure domain names and IP addresses for VISM cards and call agents:


Step 1 Type the cnfvismdn command, the domain-name argument value, and press Enter to specify a domain name for a VISM card. Specify the domain-name argument with the following value:

A text string of up to 64 alphanumeric characters; spaces are not allowed. Default = cisco.com.


Note You must use the domain-name argument value you entered for Step 1 when configuring the call agent(s) domain-name argument in Step 3.


Step 2 Type the cnfvismip command, vip-addr, netmask, |bearer-ipaddr|, and |bearer-netmask| argument values, and press Enter to specify an IP address and a subnet mask for your VISM card. Specify the arguments with the following values:

vip-addr: Type the IP address of your VISM card in dotted decimal format—nnn.nnn.nnn.nnn

netmask (local network mask): Type 255.255.255.248

|bearer-ipaddr| (optional): Bearer IP address in dotted decimal format: nnn.nnn.nnn.nnn

|bearer-netmask| (optional): Bearer IP subnet mask in dotted decimal format: nnn.nnn.nnn.nnn

Step 3 Type the cnftftpdn command, the domain-name argument value, and press Enter to set up the domain names and IP addresses for the call agent(s). The domain name can be a text string of 1 to 64 alphanumeric characters.

Step 4 Repeat Step 1 through Step 3 to configure your remaining VISM cards and call agents.

You have completed configuring domain names and IP addresses for VISM cards and call agents. Proceed to the "Setting Up Call Agents and Protocols" section.


Setting Up Call Agents and Protocols

Complete the following steps to set up call agents and media gateway control protocols:


Step 1 Type the adddn command, the domain-num, domain-name, and |resol-type| argument values, and press Enter to add a domain name for a call agent. Specify the arguments with the following values:

domain-num: A domain number used to identify the domain in the range 1 to 11.

domain-name (call agent name): A text string of 1 to 64 alphanumeric characters.

|resol-type| (the optional resolution type to configure for the specified domain name):

1 = Internal only

2 = External only

3 = Internal first

4 = External first

Step 2 If you are not using an external DNS to resolve domain names (resol-type = 1 in Step 1), proceed to
Step 3. If you are using an external DNS to resolve domain names, proceed to Step 3.

Step 3 Type the adddnip command, resol-num, domain-name, ip-addr, and addr-order argument values, and press Enter to add the IP address for the domain name you added in Step 1. Specify the arguments with the following values:

resol-num (resolution number of the domain name): In the range from 1 to 88.

domain-name (call agent name): In the range from 1 to 64 alphanumeric characters.

ip-addr (IP address which corresponds to domain-name): IP address, which must be in the following format—nnn.nnn.nnn.nnn.

addr-order (IP address resolution preference order): In the range from 1 (highest) to 8.

Step 4 Type the addmgcgrpentry command, mgc-group, mgc-num, and mgc-priority argument values, and press Enter to add the MGC to a redundancy group. Specify the arguments with the following values:

mgc-group (call agent redundancy group number): In the range from 1 to 8.

mgc-num (protocol number): In the range from 1 to 8.

mgc-priority (preference of the MGC within the group): In the range from 1 (highest) to 8.

Step 5 Type the cnfmgcgrpparam command, mgc-group, state-change-notify, and the optional mgc-priority argument values, and press Enter to change the parameters of the MGC group, if needed.


Note This step is optional; use only if you need to change the MGC group parameters.


Specify the arguments with the following values:

mgc-group (call agent redundancy group): In the range from 1 to 8.

state-change-notify (state change message notification):

1 = Enable (default)

2 = Disable

|mgc-priority| (call agent priority): In the range from 0 to 8 (default = 1)

Step 6 Type the addmgcgrpprotocol command, mgc-group and protocol-num argument values, and press Enter to associate a call agent redundancy group with a gateway control protocol. Specify the arguments with the following values:

mgc-group (call agent redundancy group): In the range from 1 to 8.

protocol-num (gateway control protocol): In the range from 1 to 8.

Step 7 Repeat Step 1 through Step 6 for each call agent that you need to make active in your application.

You have completed setting up call agents and media gateway control protocols. Proceed to the "Configuring Gateway Control Protocols" section, if necessary.


Configuring Gateway Control Protocols

Complete the following steps to configure gateway control protocols.


Note Use the configure gateway control CLI commands in this section only if you need to configure argument values for the commands that are different than the default argument values.



Step 1 Type the cnfxgcppeer command, mgc-num, protocol-num, and remote-udp-pnum, and press Enter to configure a port number for a particular call agent and protocol. The port is used to send gateway-initiated messages to the call agent. Specify the arguments with the following values:

mgc-num: In the range 1 to 8.

protocol-num: A protocol number which is displayed by using the dspmgcgrpprotocols command.

remote-udp-pnum: The remote UDP port number used for MGCP/SGCP protocol communication with the call agent.

Step 2 Type the cnfxgcpmwd command, max-wait-delay argument value, and press Enter to specify the maximum waiting time before a Restart in Progress (RSIP) message is sent to the call agent. Specify the max-wait-delay argument value as follows:

max-wait-delay (maximum wait time; defined in milliseconds): In the range from 0 to 600000; (default = 10000; 10 seconds)


Note The max-wait-delay argument value sets the maximum wait time for the entire VISM card, not for a particular call agent.


Step 3 Type the cnfxgcpretry command, min-vtoca-tout, vtoca-retrans-num, and |max-vtoca-tout| argument values, and press Enter to specify the VISM minimum and maximum wait time, and number of retries, for a call agent message acknowledgment. Specify the arguments with the following values:

min-vtoca-tout (defined in milliseconds): In the range from 1 to 100000; (default = 500)

vtoca-retrans-num:

Default = 3

|max-vtoca-tout|: In the range from 0 to 100000.

Step 4 Type the cnfxgcpbt command, network-type, vc-type, and aal-conn-type argument values, and press Enter to specify the type of bearer channel VISM uses, if one is not specified by the call agent in protocol local connection options. Specify the arguments with the following values:

network-type:

1 = IP

2 = ATM

vc-type:

1 = PVC

2 = SVC

aal-conn-type:

1 = AAL1

2 = AAL2

3 = Not applicable


Note You must type 3 for the aal-conn-type argument if the network-type argument = 1.


Step 5 Type the addxgcppersistevt command, event-num and pkg-event argument values, and press Enter to designate xGCP events as persistent.


Note Do not complete this step if persistent events are not required for your application.


Specify the arguments with the following values:

event-num: In the range from 1 to 64.

pkg-event:

r/co3 = VISM initiated AAL2 type 3 packet (CO3) network continuity test

r/co4 = Network continuity test detect

g/ft = Fax tone

g/mt = Modem tone

g/vbd = Voiceband data

g/vbdt = Voiceband data termination

l/hu, bl/hu = On hook

l/hd, blhd = Off hook

ms/ans, dt/ans, md/ans, mo/ans = Answer

ms/sup, dt/sup, md/sup = Setup

ms/rel, dt/rel, md/rel, mo/rel = Release

ms/rtc, dt/rlc, md/rlc, mo/rlc = Release complete

ms/res, dt/res, md/res = Resume

ms/sus, dt/sus, md/sus = Suspend

md/awk = Acknowledgment wink

mo/rbz = Reverse make busy

Step 6 Type the cnfsrcppeer command, peer-num and udp-port-num argument values, and press Enter to specify the SRCP parameters for communication between VISM and the call agent. Specify the arguments from the following values:

peer-num: The peer (call agent) identification number, as displayed in the dspsrcppeers command list; in the range from 1 to 8.

udp-port-num: In the range from 1025 to 65535


Note If you do not execute this command, the default MGCP/SGCP port number = 2428.


Step 7 Type the cnfsrcppeergrpparam command, the mgc-group, hbeat-int, and max-udp-size argument values, and press Enter to configure the SRCP heartbeat interval and maximum UDP size for a specified call agent redundancy group. Specify the arguments with the following values:

mgc-group (call agent redundancy group): In the range from 1 to 8

hbeat-int (interval between heartbeats; defined in milliseconds):

0

In the range from 100 to 65535.

max-udp-size (maximum allowable UDP size): In the range from 4095 to 65535.

Step 8 Type the cnfsrcpretry command, srcp-min-tout, max-srcp-retries, and srcp-max-tout argument values, and press Enter to configure the minimum and maximum timeout periods, and retry attempts, for transmitting SRCP commands to the call agent. Specify the arguments with the following values:

srcp-min-tout (defined in milliseconds): In the range from 1 to 10000 (default = 500).

max-srcp-retries: In the range from 1 to 10.

srcp-max-tout: In the range from 1 to 10000 (default = 500).

Step 9 Type the cnfco4timer command, a co4-timeout argument value, and press Enter to configure CO4 bearer continuity. Specify the argument with the following value:

co4-timeout (defined in milliseconds): In the range from 50 to 10000 (default = 1000).

You have completed configuring gateway control protocols. Proceed to the "Configuring ISDN PRI Backhaul" section if necessary.


Configuring ISDN PRI Backhaul

ISDN PRI backhaul configuration consists of setting up RUDP session structures:

Session sets

Session groups

Sessions

A session group applies to a specified call agent and allows automatic switching to another session in the group if an active session fails. You can configure individual sessions when you have completed setting up the session sets and session groups. Refer to "VISM Functional Description," for more information on session structures.


Note Use the commands in this section only if backhauling of ISDN PRI signaling to the call agent is required for your application.


Complete the following steps to configure ISDN PRI backhaul:


Step 1 Type the addsesset command, set-num and fault-tol-enable argument values, and press Enter to create a session set. Specify the arguments with the following values:

set-num: In the range from 1 to 16

fault-tol-enable:

1 = Yes

2 = No

Step 2 Type the addsesgrp command, group-num, set-num, and mgc-name argument values, and press Enter to create a session group for a session set and a call agent. Specify the arguments with the following values:

group-num: In the range from 1 to 16

set-num: In the range from 1 to 8

mgc-name: A text string of up to 64 alphanumeric characters

Step 3 Type the addses command, session-num, group-num, priority, local-port-num, and remote-port-num argument values, and press Enter to create an ISDN PRI backhaul RUDP session within a specified group. Specify the arguments from the following values:

session-num: In the range from 1 to 64

group-num: In the range from 1 to 16

priority: In the range from 1 (highest) to 4 (lowest)

local-port-num: The VISM port number you want to use for the session

remote-port-num: The call agent (remote) port number you want to use for the session


Note The following session configuration commands apply to a single session which is identified by the first argument, the session-num.


Step 4 Type the cnfsesack command, session-num, ack-timeout, and max-acks argument values, and press Enter to change the timeout period for sending out an acknowledgment and the maximum number of acknowledgments that can accumulated before sending them. Specify the arguments with the following values:

session-num: In the range from 1 to 64

ack-timeout (defined in milliseconds): In the range from 100 to 65535

max-acks: In the range from 0 to 255

Step 5 Type the cnfsesmaxreset command, session-num and max-resets argument values, and press Enter to configure the maximum number of resets that VISM performs before a connection is reset. Specify the arguments with the following values:

session-num: Type the value entered for the session-num argument in Step 4.

max-resets: In the range from 0 to 255

Step 6 Type the cnfsesmaxseg command, session-num and seg-size argument values, and press Enter to configure the maximum segment size VISM can receive after sending a SYN message. Specify the arguments with the following values:

session-num: Type the value entered for the session-num argument in Step 4.

seg-size (defined in octets): In the range from 30 to 65535

Step 7 Type the cnfsesmaxwindow command, session-num and window-size argument values, and press Enter to configure the maximum number of segments that can be sent without getting an acknowledgment for a specific RUDP session. Specify the arguments with the following values:

session-num: Type the value entered for the session-num argument in Step 4.

window-size: In the range from 1 to 64

Step 8 Type the cnfsesnullsegtmout command, session-num and null-seg-tout argument values, and press Enter to configure the amount of idle time before sending a null segment. Specify the arguments with the following values:

session-num: Type the value entered for the session-num argument in Step 4.

null-seg-tout (defined in milliseconds): In the range from 0 to 65535

Step 9 Type the cnfsesoutofseq command, session-num and max-seq-pkts argument values, and press Enter to configure the maximum number of out-of-sequence packets that will be accumulated before sending an EACK packet. Specify the arguments with the following values:

session-num: Type the value entered for the session-num argument in Step 4.

max-seq-pkts: In the range from 0 to 255.


Note If you specify 0 for the max-seq-pkts argument, a DACK message is sent immediately upon receiving an out-of-sequence packet.


Step 10 Type the cnfsesport command, session-num, local-port-num, and remote-port-num argument values, and press Enter to configure the local (VISM end) and remote (call agent end) port numbers for a session number. Specify the arguments with the following values:

session-num: Type the value entered for the session-num argument in Step 4.

local-port-num: In the range from 1124 to 65535

remote-port-num: In the range from 1124 to 65535

This command allows the user to configure the local and remote port numbers.

Step 11 Type the cnfsesretrans command, session-num, unack-timeout, and max-ses-retrans argument values, and press Enter to configure the retransmission of unacknowledged packet timeout value and the maximum number of consecutive retransmission attempts before the connection is considered failed. Specify the arguments with the following values:

session-num: Type the value entered for the session-num argument in Step 4.

unack-timeout (in milliseconds): In the range from 100 to 65535

max-ses-retrans: In the range from 0 to 255

Step 12 Type the cnfsesstatetmout command, session-num and tstate-tout argument values, and press Enter to configure the amount of time VISM waits for the transfer state before executing an auto reset. Specify the arguments with the following values:

session-num: Type the value entered for the session-num argument in Step 4.

tstate-tout (in milliseconds): In the range from 0 to 65535

Step 13 Type the cnfsessyncatmps command, session-num and max-sync-attempts argument values, and press Enter to configure the maximum number of attempts to synchronize VISM with the call agent. Specify the arguments with the following values:

session-num: Type the value entered for the session-num argument in Step 4.

max-sync-attempts: In the range from 1 to 32

Step 14 Repeat Step 4 through Step 13 for all additional session numbers, as required for your application.

You have completed configuring ISDN PRI backhaul.


The basic configuration of your VISM cards is complete. Use the configuration instructions in this chapter to reconfigure VISM for your application needs as they change. Use the commands described in "CLI Commands," to further configure your VISM cards, if necessary.

Configuring Additional VISM Features

The following features are available for users of VISM 3.0 and higher:

Support for the MGCP 0.1 subset of the MGCP 1.0 protocol


Note The restart method (RM) is not defined as part of the MGCP 0.1 subset, and is not supported.


Verified MGCP 0.1 protocol compliance

PBX CAS event delivery to a call agent using MGCP 0.1:

DTMF: Wink and ground start

MF: Wink

TFTP download of CAS variant state machine


Note RFC 3064 CAS packages—BL, MS, and DT—are not supported.


Interoperability enhancements:

Configurable codec strings (IANA naming conventions as well as customized ones)

Codec negotiation with configurable preference order

Exponential backoff for:

XGCP retry timers

SRCP retry timers

Configurable per CAS variant

DTMF Relay using Cisco-rtp (FRF-11 Annex A based)

Enhancement to Fax/modem up-speed/pass-through procedures:

Configurable CAC failure and carrier loss policies

Up-speed to clear channel

Added support for G.726: 16, 24, 32, and 40 kbps, with packetization periods ranging from 10 to 40 ms

Support for VBR-rt (variable bit rate real time) and VBR-nrt (non real time) ATM traffic classes, including traffic shaping to the relevant traffic descriptors

Configurable VAD model parameter for traffic engineering

In E1 applications, support for 31 DS0 per span and a total of 248 channels per card

Tested CRTP support through RPM for voice and voice band data calls

Verified bearer interoperability with 3810

Switched PVCs using SGCP 1.5:

SDP and SGCP extensions allowing xGCP call agent control of AAL2 bearers

Support of SGCP 1.5 digit maps and error codes

Support for card level coexistence of switched AAL2 mode (under Call Agent control) and trunked AAL2 mode on PVCs, on an endpoint (DS0) basis

PBX CAS event delivery to a Call Agent using SGCP 1.5:

DTMF: Wink and ground start

MF: Wink

TFTP download of CAS variant state machine

Interoperability and configuration enhancements:

Configurable codec strings (IANA naming conventions as well as customized ones)

Profile negotiation and configurable preference order

Configurable voice and VBD (for example, up-speed codec) per profile

Added support for custom profile 110 and 200 (clear channel), ITU profiles 3 and 8

User-configurable AAL2 Silence Indicator Description (SID) for all profiles

Type 3 Packet Support for proxy ringback (xrbk), packet side bearer continuity check (co3/co4 COT), and midcall DTMF relay

Connection admission control (CAC) enhancements:

Patented CAC method factoring in VAD and subcell multiplexing savings

Configurable VAD model parameter for traffic engineering

Configurable AAL2 cell fill timer

AAL2 alarm enhancements: per span, VC, and per channel (CID) conditioning

Display, clear, and reset AAL2 performance related counters

In E1 AAL2 trunking applications, support for 31 DS0 per span and a total of 248 channels per card

Verified bearer interoperability with 3810 and third-party vendors

Infrastructure work and enhanced support for three operating modes: VoIP switching, AAL2 trunking, and switched AAL2 PVC

Graceful upgrade VISM 2.0 and 2.0(1) to VISM 2.1(0)

The ability to enable or disable the call agent protocol SDP OST feature in the event the peer gateway may or may not support SDP OST. This feature allows interoperability with the Cisco AS5300 Universal Access Server and other equipment

The ability for VISM to perform as either the network or user side of the LAPD protocol for PRI backhaul

CCS/PRI backhaul between VISM and a call agent in VoIP mode

Support VoIP G.729ab compression

Idle channel suppression

Support for setting the IP precedence bit

Support for Q.50 CAS signaling variant

Negotiable packetization period

AAL2 subcell multiplexing

E1 back card support in AAL2 trunking mode

E1 back card support (VoIP mode only)

Provides 8 standard T1 interfaces with B8ZS, AMI and HDB3 line coding

Support for voice over ATM using AAL2 cells (multiplexing only, no LLC/SNAP encapsulation.

VoIP using AAL5 cells to RFC 1889

Support for both PCM a-law and u-law

Programmable 24, 32, 48, 64, 80, 96, 112, 128 ms near end echo cancellation

Voice compression to G.711 and G.726-32k standards

Nx64 clear channel (N = 1 only) support

Voice activity detection (VAD) and comfort noise generation (CNG) using variable threshold energy (Cisco proprietary)

Support for call agent Simple Gateway Control Protocol (SGCP) Version 1.0, SGCP 1.1+, and Media Gateway Control Protocol (MGCP) 0.1

Support for CCS signaling transport across an AAL5 trunk

Support for Fax and modem VoIP bearer transmissions

Support for dual (redundant) virtual circuits across the packet network

Support for full continuity testing (COT). Supports origination and terminating loopback and transponder COT towards the packet bearer and the TDM sides

Support for loop timing, payload and line loopbacks

1:N cold redundancy using SRM-3T3 capabilities (bulk mode support for T1 lines only) for switched calls

1:N hot redundancy for trunking applications only

Courtesy downing of ongoing voice calls when the VISM is taken out of service for maintenance or other reasons

Mid-Call DTMF

The mid-call dual tone multifrequency (DTMF) feature enables the collection and notification of digits to the call agent following a call setup for an endpoint, and supports the outpulsing of DTMF digits at a call agent's request. This feature is used for services that require two stage dialing, such as calling card applications.

Mid-call DTMF is supported for all the CAS variants, for DTMF mode only.

Configurable Jitter Buffer

The configurable jitter buffer feature provides configuration of jitter buffer mode and initial delay time on a codec basis. Fax, modem, and CCD calls have less packet loss with the addition of this feature.

Adjustable Gain

The adjustable gain feature allows you to adjust gain on a DS0 channel basis for both input and output signals. The adjustable gain can be set when there is active call going on at the DS0 channel, and at both bounded non-active and unbounded endpoints.

Adjustable Music On-Hold Threshold

The adjustable music on-hold threshold feature allows you to adjust the dB level, on a DS0 basis, of when DSPs interpret TDM side silence or voice.

CALEA

The Commission on Accreditation for Law Enforcement Act (CALEA) feature, used with VoIP applications, provides data (eavesdropping) about an intercepted subject (the user/subscriber) in two forms for both the receive and transmit directions:

Call identifying data

Call content data

The call identifying data (called number) is provided by call agents. The call content data (voice) is provided by the edge/access routers (7200, for example) and trunking gateways (MGX 8000 series platforms) in combination with VISM cards.

The VISM CALEA implementation supports the CALEA law intercept confirmation interface.

MGC Redundancy

The media gateway controller (MGC) redundancy feature provides redundancy for call agents on VI SM cards. You can associate one or more call agents as members of a redundancy group.

An MGC redundancy group consists of one or more MGCs (which are identified by their domain name). An MGC can be part of one redundancy group, although there can be multiple MGCs per redundancy group. At any given time, only one MGC in the redundant group is active.

This feature requires you to add more than one domain name and configure these as redundant call agents or the same logical MGC. Only the IP addresses corresponding to each physical entity are returned by the DNS server. In order to allow VISMs to traverse all the IP addresses, you must identify these physical entities as redundant call agents.

External DNS

The external domain name server (DNS) feature allows VISM to use an external DNS to resolve the IP address you configure. The domain names can be MGCs, call agents, or trivial file transfer protocol (TFTP) servers used for CAS file downloads. Resolution of IP addresses can be configured with the following methods:

Internal static tables only

External DNS only

External DNS, followed by the internal static tables if the external DNS method fails

Internal static tables, followed by the external DNS if the internal static table method fails

2 IP Address Support

The 2 IP address allows you to add separate IP addresses for the control and data paths for VISM. This feature removes the restriction of control and data traffic going to two different domains.

VoIP Trunking

The Voice over IP (VoIP) trunking feature allows the VISM to connect to the PBX, or central office digital systems, using T1/E1 digital interfaces and converts the TDM bit stream into RTP packets, after ECAN and compression, and transports it over the IP network.

No call agent is required for setting up and tearing down calls. You must configure the DS0 circuits. The connection between VISM and the first router will be ATM after which it will be IP only. VISM and the router can have one or multiple PVCs to transport the data. You have the option to configure PVC for bearer or control. If the PVC is configured as bearer and no control PVC exists, then PRI signal traffic and bearer traffic will go through this PVC. If you configure separate PVCs for control and bearer, PRI signaling will go through control traffic only. You can modify some of the connection parameters after it is added.

CAS is transported to the far end using a Cisco proprietary format (not NSEs). PRI is transported over RUDP to the far end once the trunk is provisioned between the originating and terminating VISM.

PRI transport is handled in a way identical to PRI backhaul except that the PRI traffic is sent to remote gateway instead of a call agent. You can configure one line for PRI trunking and another line for PRI backhauling.

You must provision the LAPD trunk when using this feature. You must configure a line number, remote gateway IP address, local UDP port, and remote gateway UDP port, and then open a trunk. You must then configure the D-channel as a trunk or backhaul:

To configure the D channel as trunk, use the addlapdtrunk command prior to the addlapd command. If the addlapd command has been previously executed for that line, the command is rejected.


Note Two D channels on one line are not supported.


To configure the D channel as backhaul, use the addses command prior to the addlapd command. If you do not configure either trunk or session, the addlapd command is rejected.

T.38 Fax Relay

The ITU T.38 recommendation for fax relay feature assists fax transmission over IP networks. You must configure T.38 parameters—fax rate, information field size, data packet size, data redundancy, and NSF values—to use this feature.


Note You must use codec template 3 with the T.38 fax relay feature enabled. The T.38 feature supports 120 DS0s when enabled.


CAS Feature Enhancements

VISM Release 2.2 allows you to configure different CAS packages on different endpoints. The following CAS feature enhancements are also added to this release.

Programmable Tone Plans

This enhancement provides you the ability to provision a tone plan in a CAS independent scenario so that any inband call progress tone can be played on any endpoint (CAS, CCS, or clear channel) when signaled by the call agent.

VISM Release 3.0 contains the built-in (preconfigured) version 1 tone plans shown in Table 4-6, which you cannot modify or remove from the system.

Table 4-6 VISM 3.0 Built-in (Preconfigured) Tone Plans 

Tone Plan
Tone Plan
Tone Plan
Tone Plan

ITU1

Finland

Japan

Singapore

North America

France

Korea Republic

Slovakia

Argentina

Germany

Luxembourg

Slovenia

Australia

Greece

Malaysia

South Africa

Austria

Hong Kong

Mexico

Spain

Belgium

Hungary

Netherlands

Sweden

Brazil

Iceland

New Zealand

Switzerland

Canada

India

Norway

Taiwan

China

Indonesia

Philippines

Thailand

Cyprus

Ireland

Poland

Turkey

Czech Republic

Israel

Portugal

United Kingdom

Denmark

Italy

Russia

United States

1 ITU = International Telecommunications Union (formerly CCITT).


VISM Release 3.0 allows you to configure provisional tone plans if the built-in tone plans do not meet your application needs. Provisional tone plans are created by assigning new region/country, version, and file names, and configuring the following call progress tones:

Ringback

Busy

Reorder/Congestion

Dial

Stutter dial

Offhook alert/warning

Loop Start, DID, and Delay Dial

The exchange side (FXO) of the loop start protocol is implemented with this release. VISM can accept calls from, and terminate calls to, loop start PBXs. When a PBX sends a subscriber call to the gateway, it sends the loop close signal through the CAS signaling channel. To hang up, it sends the loop-open signal.

Direct inward dial enables a caller outside a company to call internal extensions without having to go through an operator or an attendant. VISM has this ability—it outpulses the digit stream handed down by the call agent.

Dial delay is an E&M signaling protocol similar to wink start. The originating VISM, on receiving a seize (AB=11) from the PBX, responds by sending the delay-dial (AB=11) signal back to the PBX. When the originating VISM is ready to collect the digits, it sends start-dial (AB=00) signal. This operation is symmetric. So the terminating VISM, on seizing a trunk, should receive AB=11 (as an acknowledgment that the trunk is operational). Subsequently when it receives the start signal (AB=00) from the connected PBX, it should outpulse the digits. The rest of the operation is similar to wink-start.

FGD

FGD enables long distance calls through one of the following methods:

Preselected access carrier (AC) by dialing 1 + area code + number.

Selecting the AC on a per call basis by dialing 101xxxx before the area code and phone number to within a local exchange carrier's (LEC) network in North America.

FGD supports the following protocols:

Terminating Protocol

Equal Access North American (EANA)

Operator Services (OS)

Configure Flash Hook and Glare Condition Attributes

You can configure both flash hook and glare condition attributes with VISM Release 2.2. Flash hook configuration allows you to modify the duration of a flash hook. Duration shorter or longer than that configured are interpreted as incoming calls and disconnects. Glare condition attribute configuration allows you to control the CAS direction—incoming, outgoing, or bidirectional—and the glare handling policy—controlling or releasing.

Configure ANI and DNIS Digit Order

You can configure the order in which a call agent sends automatic number identification (ANI) digits—the caller's number—and dial number identification service (DNIS) digits—the called number—to VISM during an outgoing Feature Group D (FGD) call for the endpoints of a specified VISM card line.

RFC 3064 Package Support

This release fully supports the following packages from RFC 3064:

MS—MF single stage dialing trunks. This includes wink start and immediate start PBX DID/DOD trunks as well as basic R1 and FGD Terminating protocol.

DT—Immediate start and basic DTMF and dial-pulse trunks.

MD—North American MF FGD EANA and EAIN, which allows VISM to be at the end office, the carrier, or the tandem side of the circuit.

MO—FGD Operator Services Signaling, outgoing trunks only.

BL—DTMF and dial pulse (DP) basic PBX trunks.

RFC 2833 Support

Support for RFC 2833 enables VISM to support DTMF relay using named telephony events (NTEs), named signaling event (NSE) based relay, and Cisco-RTP based relay. For all other tones, VISM uses NSEs.

VISM Network Continuity Test

You can configure VISM network continuity testing with VISM Release 2.2(0).

Configure PVC OAM Cell Parameters

This feature allows you to configure the transmitted and received permanent virtual circuit (PVC) Operations, Administration, and Maintenance (OAM) cell parameters—cell gap, recovery cell count, and unacknowledged cell count.

PXM1E and PXM45 Card-Only Features

Software Release 3.0(0) for VISM/VISM-PR introduces a new card—VISM-PR. You can use the VISM-PR card in combination with any of the following MGX 8000 Series switch Processor Module cards:

PXM1

PXM1E

PXM45

Table 4-7 describes the configuration requirements for VISM/VISM-PR in combination with the MGX 8000 Series switches and supported processor modules.

Table 4-7 VISM/VISM-PR and MGX 8000 Series Switch Support 

VISM Module
MGX 8230 with PXM1
MGX 8830 with PXM1E
MGX 8250 with PXM1
MGX 8850 with PXM1
MGX 8850 with PXM1E
MGX 8850 with PXM45

MGX-VISM-8T1

Yes

No

Yes

Yes

No

No

MGX-VISM-8E1

Yes

No

Yes

Yes

No

No

MGX-VISM-PR-8T1

Yes

Yes

Yes

Yes

Yes

Yes

MGX-VISM-PR-8E1

Yes

Yes

Yes

Yes

Yes

Yes


Refer to the Cisco MGX 8850 Hardware Installation Guide, Release 3 for information on installing and maintaining the PXM1, PXM1E, and PXM45 cards.


Note You cannot use the VISM card in combination with either the PXM1E or PXM45 card.


The VISM-PR card supports 144 channels when used with the G.723.1 codec. The VISM card does not support the G.723.1 codec.

The following software Release 3.0(0) for VISM/VISM-PR features require either the PXM1E or PXM45 card and are not supported if you are using PXM1 cards in your MGX 8000 Series switch chassis:

Call Agent-Controlled VoATM AAL1 and AAL2 SVC

AAL1 SVC-Based TDM Hairpinning

Expanded Clock Source Selection


Note Clock source configuration support and procedures are not changed from previous releases of software if you are using a PXM1 card in your MGX 8000 Series switch chassis.


Private Network-to-Network Interface Priority Routing

Additional SPVC Connection Management Capabilities

Call Agent-Controlled VoATM AAL1 and AAL2 SVC

The following operating modes are supported with software Release 3.0(0) for VISM/VISM-PR:

VoAAL1 switched virtual circuit (SVC), supported with the G.711 codec and clear channel.


Note VAD is not supported in combination with AAL1 SVCs.


VoAAL2 SVC, supported with the G.711, G.726, G.729a, G.729ab, and G.723 codecs and ITU profiles 1, 2, 3, 7, 8, and custom profiles 100, 101, 110, and 200.


Note CAS is not supported in combination with switched virtual circuits.


Use the cnfvismmode command to configure VISM operating modes.


Note This feature requires you to use a PXM1E or PXM45 in your MGX 8000 Series switch chassis.


AAL1 SVC-Based TDM Hairpinning

VoAAL1 switched virtual circuit (SVC) operating mode is supported with the G.711 codec and clear channel. The AAL1 SVC operating mode supports TDM hairpinning.


Note VAD is not supported in combination with AAL1 SVCs. CAS is not supported in combination with SVCs


Use the cnfvismmode command to configure VISM operating modes.


Note This feature requires you to use a PXM1E or PXM45 in your MGX 8000 Series switch chassis.


High Complexity Codec Support for VISM-PR—G.723.1

The VISM-PR card supports high complexity codec G.723.1 in template number 4. Template number 4 supports all the codecs in template number 3 and the following:

G.723.1 high rate (6.3Kbps)—G.723.1-H

G.723.1 high rate with VAD—G.723.1a-H

G.723.1 low rate (5.3Kbps)—G.723.1-L

G.723.1 low rate with VAD—G.723.1a-L

The G.723.1 codec, used in combination with the VISM-PR card, supports 144 channels. Refer to Table 4-3 for a description of VISM-PR DS0 density when the cards are used in combination with supported codecs.

Several CLI commands have been modified to allow you to use the G.723.1 codec and template number 4.


Note The G.723.1 codecs are not supported for VISM cards.


Announcement File System

This release allows VISM to play prerecorded local announcements in switched VoIP connections. Under the control of a call agent, announcements can be played toward any IP endpoint or toward any VISM endpoint.

Up to 125 different announcements may be cached on the VISM card for immediate playout. A persistent announcement storage area exists in the packet network. Announcements are downloaded on demand from the announcement storage area and remain on the VISM card until they have reached expiry or are replaced. If the 125 announcement maximum is reached, subsequent requests for announcements not on the VISM card result in the replacement of "cached" announcements.

Announcements can be played over established connections in any VISM supported codec, but they must exist on the announcement file server in the desired encoding.


Note You must play announcements in the exact codec in which they have been recorded.


VISM announcements require the support of the MGCP 0.1/1.0 call agent.

Announcement Timeouts

VISM uses a provisionable timeout value of 5 seconds. If an announcement cannot start playing within the timeout value of receiving the request, the action is canceled and, if requested by the call agent, an "of" event is reported. If the call agent specifies a timeout value in the request, this value will be ignored.

Announcement Direction

Announcements can be played toward the packet network or toward the TDM network (not both). The direction is determined by the notation of the MGCP S: line. Announcement direction examples:

S: a/ann(all-lines-busy.au)

Explanation    Indicates that all-lines-busy.au is to be played toward the TDM network.

S: a/ann@connid(all-lines-busy.au)

Explanation    Indicates that all-lines-busy.au is to be played toward the packet network.

Broadcast Announcements

VISM supports announcement requests for a single endpoint or connection. The request may only specify a single announcement to be played on a single endpoint in a single direction. Broadcast announcements are not supported.

Multiple Announcement Requests for the Same Endpoint

If an announcement is being played on an endpoint (in one direction) and a subsequent announcement request is received for the same endpoint (in the same direction), the playing announcement will continue and the new announcement request is ignored.

If an announcement is being played on an endpoint (in one direction) and a subsequent announcement request is received for the same endpoint (in the other direction), the playing announcement is stopped and the new announcement is then played. Events are not generated for the stopped announcement.

Announcement File Server

Announcements are contained in an announcement file server, which resides on an IP network reachable from the VISM using Trivial File Transfer Protocol (TFTP).

Announcement File Server Name

You can configure the announcement file server node name on the VISM the same way that you configure a node name for the TFTP server.

Announcement File Server Directory Structure

You may use any directory or path on the file server as the main directory for storing announcement files. If you do not provision an announcement path prefix on VISM, the main announcement file directory is the default TFTP directory on the server. If a path prefix is provisioned, this prefix is used as the main announcement directory. If the prefix is not absolute (does not begin with a forward slash (/)), the prefix is relative to the default TFTP directory.

You can configure codec subdirectories under the main announcement directory on the announcement file server. A codec subdirectory exists for each codec used for announcement files.The subdirectories may be one or more of the following:

g711u/

g711a/

g726_32k/

g726_24k/

g726_16k/

g729_a/

g7231_high_rate/

g7231_a_high_rate/

g7231_low_rate/

g7231_a_low_rate/

When the call agent requests that an announcement is to be played toward the TDM network on an unconnected endpoint, you can specify the codec to be used.

Another level of directories might be configured to group announcement files by language. These directories would be specified by the call agent (or when provisioning the VISM) as part of the announcement file name. For example, the call agent might specify the announcement file name to be english/ann1.au. If the file was encoded in G.729a and the prefix was /tftpboot, the file would reside at /tftpboot/g729_a/english/ann1.au.

VISM Announcement Cache Management

VISM maintains an announcement cache in resident memory. When an announcement is requested to be played, it is retrieved from the announcement file server and placed in the on-board announcement cache. Subsequent requests for the same announcement do not require retrieval of the announcement file from the announcement file server.


Note An announcement in one encoding is a different file than the same announcement in a different encoding.


Announcement Expiry

You can provision an announcement aging policy. Once an announcement has aged (reached expiry) in the on-board cache, it is refreshed—retrieved again from the announcement file server. This provides you with the means to balance the cost of file server access with the time before an announcement changed on the file server is propagated to the VISM. In addition, you can delete dynamic files from the announcement cache at any time.

Permanent Announcements

You can provision permanent announcements for VISM. A permanent announcement is retrieved from the announcement file server and installed permanently in the VISM announcement file cache. Permanent announcements are excluded from aging (and being automatically refreshed) and excluded from being replaced if the announcement cache becomes full. Permanent announcements can only be removed from the cache explicitly by using a CLI command. If VISM is reset or fails over to a standby card, permanent announcements are retrieved as soon as the card becomes active. The announcement encoding must be specified when provisioning or deleting permanent announcements.

Use the CLI commands in Table 4-8 to configure the announcement file system feature.

Table 4-8 Announcement File System Feature CLI Commands 

Command
Description

addannpermanent

Configures an announcement server file and associated codec type as permanent.

cnfannagetime

Configures the time that a nonpermanent announcement is to remain valid after it is placed into the VISM announcement cache.

cnfanndn

Designates an announcement file server domain name.

cnfannpathprefix

Designates the main prefix directory TFTP path from which to retrieve announcement files from the announcement file server.

cnfannprefcodec

Configures the codec type used for announcements played on unconnected TDM endpoints.

cnfannreqtimeout

Configures the expiration time for announcements to begin playing after the VISM receives the announcement signal (request) from the call agent.

delannalldynamic

Deletes all announcement files and their associated codec types from the temporary announcement files currently saved in the VISM card.

delanndynamic

Deletes an announcement file and associated codec type from the temporary announcement files currently saved in the VISM card.

delannpermanent

Deletes a permanent announcement file and its associated codec type from the announcement file server.

dspannagetime

Displays the time that a nonpermanent announcement is to remain valid after it is placed into the VISM announcement cache.

dspanncache

Displays all available temporary announcement file names, and associated age times before being refreshed from the announcement file server.

dspanncontrols

Displays a summary list of all provisionable announcement file variables, including variables associated with all announcement file CLI commands.

dspanndn

Displays the announcement file server domain name.

dspannpathprefix

Displays the main prefix directory path from which VISM retrieves announcement files from the announcement file server.

dspannpermanents

Displays all available permanent announcement files with their associated codec types and identifying index numbers.

dspannprefcodec

Displays the codec type used for announcements played on unconnected TDM endpoints.

dspannreqtimeout

Displays the expiration time for announcements to begin playing before being aborted.


Call Agent-Controlled T.38 Fax

The call agent-controlled T.38 fax feature is an additional operational mode for MGCP 1.0 to request T.38. This addition allows VISM to interoperate with H.323 and non-Cisco gateways, and is supported for VoIP calls. This feature is activated based on the fax tone and signaling carried with the call agent. The modified cnft38fxlco command allows you to configure the local connection option fax preamble response to off. All previous options are valid.

Additional Support for MGCP 1.0

This release expands the support for the Media Gateway Control Protocol (MGCP) 1.0, which was introduced in VISM 2.2. The following are implemented for the MGCP 1.0 feature support:

Restart in Progress command disconnect procedure wait delay timer value specification for the following:

Initial

Minimum

Maximum

Call agent redundancy group protocol configuration for the following:

Quarantine handling method for persistent events

Default quarantine handling method for each protocol

Ability to keep events from previous lists, until explicitly requested to be removed

Ability to send provisional responses

Ability to send response acknowledgments

Ability to provide a disconnect method

Ability to cancel previously issued graceful restart commands

Use the CLI commands in Table 4-9 to configure the MGCP 1.0 feature.

Table 4-9 MGCP 1.0 Feature CLI Commands 

Command
Description

addmgcgrpprotocol

Associates a call agent redundancy group to a gateway control protocol.

cnfdisctimers

Specifies the wait delay times for the disconnected procedure, restart in progress command—initial, minimum, and maximum timer values.

cnfmgcgrpprotocol

Configures call agent group protocol data.

cnfxgcppeer

Configures the UDP port number used to send gateway-initiated messages to the call agent.

delmgcgrpprotocol

Deletes an MGCP from a specified call agent redundancy group.

dspdisctimers

Displays the Restart in Progress command disconnect type method wait delay times.


RSVP-Based Admission Control

Resource Reservation Protocol (RSVP)-based admission control signaling with MGCP is supported, which allows for quality VoIP connections. For the connections, the RSVP-MGCP interaction results in the following:

Establish or originate unidirectional resource reservation for sending voice packets for connections established and controlled by MGCP.

Accept unidirectional resource reservations for receiving voice packets from MGCP controlled connections.

Tear down originated or established unidirectional resource reservations.

Tear down accepted resource reservations.


Note VISM supports RSVP in the VoIP switching operating mode only, with a 5 calls per second limitation; RSVP is not supported in the VoIP trunking operating mode.


In previous releases of VISM software, the following connection data is returned in response to the call agent initiated DLCX, and gateway initiated DLCX or AUCX commands:

Number of packets sent

Number of octets sent

Number of packets received

Number of octets received

VISM Release 3.0(0) provides the following additional connection data:

Number of packets lost

Inter-arrival jitter—If a DSP is configured to operate in the adaptive jitter buffer mode, the jitter data provided indicates the delay that the jitter-algorithm is adapted to. If a DSP is configured to operate in the fixed jitter buffer mode, the jitter data provided indicates the value that was configured when the channel was opened.


Note For adaptive mode you can use the value to indicate that the configured initial delay value is too low or too high, since the algorithm adapts according to the actual network jitter.


Average transmission delay (latency)

Use the commands in Table 4-10 to configure the RSVP-based admission control feature.

Table 4-10 RSVP-Based Admission Control Feature CLI Commands 

Command
Description

cnfrsvp

Configures RSVP for a specified connection.

cnfrsvprefreshmiss

Configures the number of times VISM waits for a missed RSVP minimum refresh message for a specified connection.


Clock Slip Counters

The clock counter information feature allows you to clear the current frame slip counters for a specified VISM or VISM-PR card line and display the current frame slip counters for a specified VISM or VISM-PR card line. Use the new clrslipcnt and dspslipcnt to use this feature.

RTP Connection Statistics

Real-Time Transport Protocol (RTP) connection statistics are collected for individual endpoints and sent to the call agent. Use the new dsprtpconnstat command to display collected RTP connection statistics.

Jitter delay data collection at call completion is on a per call basis. Jitter delay data and number of packets sent and received, and number of octets sent and received, are reported to the call agent through MGCP.

CAS Immediate Start and Ground Start Glare Handling

CAS Immediate Start—The CAS variants immediate start and immediate start, multifrequency are supported. Use the addcasvar command to configure CAS variants.


Note The immediate start protocol does not define glare handling procedures—do not use the immediate start protocol on incoming or outgoing endpoints only. Endpoints are added as bidirectional by default. To make them incoming or outgoing, use the cnfcasglarepolicy command. If the endpoints are left as bidirectional, configured for immediate start operation, and glare occurs, the results may be unpredictable.


Ground Start Glare Handling—This release supports CAS glare condition handling according to RFC 3064. The VISM sends a NACK message in response to the call agent's request for ringing with error code 401 (off hook) in the event of a glare condition.

On receiving the request for ringing from call control, CAS transmits a seize signal to the PBX and starts the glare timer, returning a provisional response code to call control indicating that CAS is still processing the request. If the timer expires (normal case) or an incoming seizure is observed on the endpoint, CAS generates an asynchronous response code to call control that is comparable to an MGCP response code of 200 or 401, respectively.

Grooming for Local Traffic

VISM supports the call agent controlled grooming feature. Grooming allows VISM to avoid routing local traffic through the IP network. Voice packets from a local connection are switched locally in the ATM switch.

A call agent determines if a call needs to be setup as local. To set up a local call, the call agent selects an ATM connection over a VoIP connection. The VISM card, as a gateway, receives the connection request message from the call agent for an ATM connection. The VISM card allows VoIP calls and VoAAL1 SVC calls to coexist and allows provisioning of VoIP and ATM simultaneously.

To achieve this, VISM uses VoIP and Switched ATM AAL1 SVC as local switching mode. VISM receives an ATM AAL1 SVC call setup request from the call agent for local calls.

You must use the cnfvismmode command and select the VoIP and switched ATM AAL1 SVC operating mode to use the grooming feature. Using this mode does not change any other settings on your card. The type of connection for a call is determined by the connection request (CRCX) from the call agent or by the bearer type configuration.

MGX 8000 Series Implementation Enhancements

The following enhancements are supported with this release to you with additional implementation of your MGX 8000 Series switch:

Additional VBR Enhancements

Expanded Clock Source Selection

Private Network-to-Network Interface Priority Routing

Additional SPVC Connection Management Capabilities

192 T1/248 E1 DS0 Support with High Complexity Codecs on VISM-PR

Channel Alarm Enhancement

VISM TDM Line Statistics Collection

Additional VBR Enhancements

Setting connections between a VISM-PR card and a RPM-PR card in your MGX 8000 Series switch chassis requires you to use the new VBR (NRT) 3 connection type. Use the modified addcon or cnfcon commands to configure this connection type. In addition, the following new connection service types can be configured with the modified commands in this release:

VBR (RT) 2

VBR (RT) 3

VBR (NRT) 2

Expanded Clock Source Selection

This release supports an expanded clock source selection, which allows you to configure any VISM-PR card line as the clock source. You cannot delete a VISM-PR line that is configured as the clock source; you must configure a different line as the clock source and then you can delete the original clock source line. The previously released CLI commands allow you to use this feature.


Note This feature requires you to use a PXM1E or PXM45 in your MGX 8000 Series switch chassis.


Private Network-to-Network Interface Priority Routing

This release supports the Private Network-to-Network Interface (PNNI) routing priority feature. This feature allows you to specify connections with a routing priority. The PNNI controller uses your configuration selections to route the higher priority connections before routing the lower priority connections. Use the cnfpncon command to configure a routing priority for a specified connection.


Note This feature requires you to use a PXM1E or PXM45 in your MGX 8000 Series switch chassis.


Additional SPVC Connection Management Capabilities

Use the PXM1E or the PXM 45 card in combination with the VISM-PR card in an MGX 8000 Series switch chassis to specify a connection up or down. Specifying a connection up allows you to direct traffic to the specified connection. Specifying a connection down allows you to prevent traffic from being directed to a specified connection. Use the upcon and dncon commands to use this feature.


Note This feature requires you to use a PXM1E or PXM45 in your MGX 8000 Series switch chassis.


192 T1/248 E1 DS0 Support with High Complexity Codecs on VISM-PR

VISM-PR T1 lines support up to 192 DS0 channels and VISM-PR E1 lines support up to 248 DS0 channels, with clear channel and the following codec types:

G.711

G.726

G.729a

G.729ab

Table 4-3 describes the VISM/VISM-PR DS0 density when the cards are used in combination with clear channel and the supported codecs.

Table 11 VISM/VISM-PR DS0 Density with Codec Support 

Codec
VISM
VISM-PR
T1
E1
T1
E1

G.711

192

248

192

248

G.723.1

144

144

G.726

145

145

192

248

G.729a/ab

145

145

192

248

Clear channel

192

248

192

248


Channel Alarm Enhancement

The channel alarm enhancement feature uses the modified dspconcnt command, which allows you to view the channel status bit map data.

VISM TDM Line Statistics Collection

This release allows you to configure VISM to collect Time Division Multiplex (TDM) line statistics. Use the dspalmcnt command to collect and display TDM line statistics. Use the cnfalmcnt command to configure the thresholds for TDM line statistics.