Cisco Voice Interworking Services (VISM) Configuration Guide & Command Reference, Release 3.2
Configuring VISM/VISM-PR Features

Table Of Contents

Configuring VISM/VISM-PR Features

Using the Command Line Interface

VISM/VISM-PR Command Attributes

Connecting to Cisco MGX 8000 Series Platforms

Overview

Logging In to PXM and VISM/VISM-PR Cards

Logging Out of VISM/VISM-PR and PXM Cards

Configuring the VISM/VISM-PR

Initial Configuration of the VISM/VISM-PR Card

Configuring the TDM Side

Configuring Bearer Processing

Configuring the ATM Network Side

Configuring the Call Agent Interface

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 Features

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

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 Features

Configuring VISM/VISM-PR Features


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

"Using the Command Line Interface" section

"Connecting to Cisco MGX 8000 Series Platforms" section

"Configuring the VISM/VISM-PR" 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/VISM-PR 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 <LineNum>

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

clralm -ds1 4

VISM/VISM-PR Command Attributes

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

Table 6-1 VISM/VISM-PR 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

cc 1

Yes

All

All

chkflash 1

Yes

Active

1

clr

No

Active

1 to 5

cnf

Yes

Active

1

del

Yes

Active

1

dsp

No

Active

All

Help 1

No

All

All

pinglndsp 1

No

Active

All

tst

No

Active

All

version 1

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 Chapter 7, "CLI Commands."


Connecting to Cisco MGX 8000 Series Platforms

This section contains the following topics:

Overview

Logging In to PXM and VISM/VISM-PR Cards

Logging Out of VISM/VISM-PR and PXM Cards

Overview

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

Cisco MGX 8850 (PXM1), wide area switch

Cisco MGX 8250, edge concentrator

Cisco MGX 8230, edge concentrator

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

Cisco MGX 8850 (PXM1), wide area switch

Cisco MGX 8250, edge concentrator

Cisco MGX 8230, edge concentrator

Cisco MGX 8830

Cisco MGX 8850 (PXM1E and PXM45) platforms

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

For more information about connecting to PXM1E or PXM45 cards, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide.

For more information about connecting to PXM1 cards, refer to the Cisco MGX 8850 Multiservice Switch Installation and Configuration Guide.


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


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/VISM-PR Cards

To log in to the PXM and VISM/VISM-PR cards, complete the following steps:


Note Except where noted, the use of PXM refers to the three different PXM cards (PXM1, PXM1E, and PXM45).



Step 1 Connect your terminal or workstation to the PXM back card via one of the methods listed in the above bullets.

The login prompt is displayed:

Login:

Step 2 At the prompt, type your user name.


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


The password prompt is displayed:

password:

Step 3 At the prompt, type your password.

For security, the password is displayed as asterisks:

password: *****


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



For PXM1E or PXM45 cards, the active PXM card is automatically displayed:

PXM1E_SJ.7.PXM.a > 

For PXM1 cards, the following prompt is displayed:

card number [7]:

Step 4 To go to the active PXM1 card, press enter or return.

NODENAME.1.7.PXM.a >

Step 5 To display the available cards, enter the dspcds command.

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 for all of the PXM cards:

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 6 Identify, from the list displayed in Step 5, the slot number of the VISM/VISM-PR card you want to configure.

Step 7 To change to the VISM/VISM-PR card you identified in Step 6, enter the cc command (to change card), with the corresponding VISM/VISM-PR card slot number.

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

NODENAME.1.9.VISM8.a

The VISM/VISM-PR 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)

You have completed logging in to the PXM and VISM/VISM-PR cards and can now perform the mandatory initial VISM/VISM-PR card configuration.


Logging Out of VISM/VISM-PR and PXM Cards

To log out of the VISM/VISM-PR and PXM cards, enter one of the following commands:

bye

logout

Configuring the VISM/VISM-PR

The CLI allows you to configure all features and functions of VISM/VISM-PR.

Configure mandatory commands when you require argument values that are different from the default. Configure optional commands when necessary.

For a list of initial configuration commands for each operating mode, see Table 6-2.

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

1. Initial Configuration of the VISM/VISM-PR Card

2. Configuring the TDM Side

3. Configuring Bearer Processing


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


4. Configuring the ATM Network Side

5. Configuring the Call Agent Interface


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


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

VoIP Trunking

cnfvismmode 1

addport

addrscprtn

addcon

cnfvismip

addln

cnflnsig

addendpt

addrtpcon

AAL2 Trunking

cnfvismmode 1

addport

addrscprtn

cnfcac

addln

cnflnsig

addendpt

addcon

addcid

addccs

AAL1 Switching

cnfvismmode 1

cnfvismip

addport

addrscprtn

addcon

adddn

adddnip

addmgc

addmgcgrpentry

addmgcgrpprotocol

cnfvismdn

addln

addendpt

Switched AAL2 SVC

cnfvismmode 1

cnfvismip

addport

addrscprtn

addcon

adddn

adddnip

addmgc

addmgcgrpentry

addmgcgrpprotocol

cnfvismdn

addln

addendpt

 

Switched AAL2 PVC

cnfvismmode 1

cnfvismip

addport

addrscprtn

addmgc

cnfcac

addln

cnflnsig

addendpt

addcon

adddn

cnftftpdn

addcasvar

cnfcasendpt

cnfconvcci

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 Configuration of the VISM/VISM-PR Card

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

1. Configuring the Operating Mode

2. Allocating Resources

3. Configuring Connection Admission Control

4. Placing the VISM Card In Service

5. Placing the VISM Card Out of Service

Configuring the Operating Mode

To configure the correct operating mode for your VISM/VISM-PR card, complete the following steps immediately after you apply power:


Step 1 To determine the current VISM/VISM-PR operating mode, enter the dspvismparam command.

PXM1E_SJ.1.28.VISM8.a > dspvismparam

  VISM mode:                   voipSwitching/voipTrunking
  VISM features Bit Map:       0x5bc
  FunctionModuleType:          VISM-PR-8T1
  CAC flag:                    enable
  DS0s available:              192
  Template number:             2
  Percent of functional DSPs:  100
  IP address:                  172.29.52.229
  Subnet mask:                 255.255.255.0
  Bearer IP address:           0.0.0.0
  Bearer Subnet mask:          0.0.0.0
  RTCP report interval:        5000 msec
  RTCP receive multiplier:     3
  RTP receive timer:           disable
  ControlPrecedence/Tos:       0x60
  BearerPrecedence/Tos:        0xa0
  Aal2 muxing status:          disable
  Tftp Server Dn               cisco.com
  Aggregate Clipping           enable
  Aggregate Svc Bandwidth      50

Type <CR> to continue, Q<CR> to stop: 

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


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

If the VISM/VISM-PR card operating mode displayed in Step 1 is not correct for your application, proceed to Step 3.

Step 3 To configure the VISM/VISM-PR operating mode, enter the cnfvismmode command.

PXM1E_SJ.1.28.VISM8.a > cnfvismmode <mode_number>

Replace <mode_number> 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

9 = VoIP and Switched AAL1 SVC

10 = VoIP Trunking and AAL2 Trunking

Step 4 Type a y at the following message:

WARNING: Available CLI Commands will be changed, do you want to proceed (Yes/No)? y

A message about the number of available commands displays before the card returns the prompt. The following example shows the number of available commands for AAL2 trunking mode:

INFORMATION: The new 'aal2Trunking' mode has 188 CLI commands.


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

Allocating Resources

To allocate resources—virtual ports, controller resources, and codec templates—to your VISM/VISM-PR card, complete the following steps.


Step 1 To add a virtual port, enter the addport command (no arguments).

This command adds an ATM port on a VISM/VISM-PR card. This command does not have arguments. 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 (see Step 2).

Step 2 To specify the controller resources, enter the addrscprtn command.

PXM1E_SJ.1.28.VISM8.a > addrscprtn <controller_id>

Replace <controller_id> with a value 1.


Note Always specify the <controller_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/VISM-PR 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 To specify the codec template used with your VISM/VISM-PR card, enter the cnfcodectmpl command.

PXM1E_SJ.1.28.VISM8.a > cnfcodectmpl <template_number>

Replace <template_number> 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.


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

Step 4 Type a y at the following message:

The card will be reset, do you want to proceed (Yes/No)? y

The card resets and returns the prompt.


Configuring Connection Admission Control

Complete the following steps, which allow you to:

Define CAC parameters.

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


Step 1 To ensure that CAC is enabled, enter the dspvismparam command.

PXM1E_SJ.1.28.VISM8.a > dspvismparam 

VISM mode:                   aal2Trunking
VISM features Bit Map:       0x2b2
FunctionModuleType:          VISM-8T1
CAC flag:                    enable
DS0s available:              24
Template number:             3
Percent of functional DSPs:  100
IP address:                  11.11.11.1
Subnet mask:                 255.255.255.248
Bearer IP address:           15.15.15.1
Bearer Subnet mask:          255.255.255.248
RTCP report interval:        5000 msec
RTCP receive multiplier:     3
RTP receive timer:           disable
ControlPrecedence/Tos:       0x20
BearerPrecedence/Tos:        0x40
Aal2 muxing status:          disable
Tftp Server Dn               TFTPDOMAIN
Aggregate Clipping           enable
Aggregate Svc Bandwidth      0


Note By default, CAC is enabled. For information on disabling CAC, see the cnfcac command description in Chapter 7, "CLI Commands."


Step 2 To configure card level CAC parameter values for voice activity detection (VAD) duty cycle and VAD tolerance, which are used in CAC algorithms, enter the cnfcacparams command.

PXM1E_SJ.1.28.VISM8.a > cnfcacparams <VAD_duty_cycle> <VAD_Tolerance>

Replace the above arguments with the values listed in Table 6-3. The following example shows the typical values for VAD duty cycle and VAD tolerance:

PXM1E_SJ.1.28.VISM8.a > cnfcacparams 61 100

Table 6-3 Parameters for cnfcacparams Command 

Parameter
Description

VADDutyCycle

VAD duty cycle is the ratio of speech and holdover duration to total duration expressed as a percentage.

Holdover is the period after silence begins and silence suppression is turned on. In VISM/VISM-PR, the holdover time is 250 ms.

A typical value for this parameter is 61 which means that 61% of the time is taken by speech and holdover. Range is 1-99. Default is 61.

VADTolerance

VAD tolerance is the expression for VAD "over-subscription drop ratio" where: tolerance = 10000 x over-subscription drop ratio (expressed as a percentage).

A typical value for VAD tolerance is 100. Some examples are:

10000 (tolerance) = 1% (over subscription drop ratio)

100 = 0.01% (Default)

10 = 0.001%

1 = 0.0001%

Range is 0-10000.


Step 3 To configure VAD tolerance and VAD duty cycle for a specific logical connection number (LCN) used for PVCs, enter the cnfconcacparams command.

PXM1E_SJ.1.28.VISM8.a > cnfconcacparams <LCN> <VADTolerance> <VADDutyCycle>

Replace <LCN> with the logical channel number, in the range 131-510. Replace <VADTolerance> and <VADDutyCycle> with the values listed in Table 6-3. The following example shows the typical values for VAD tolerance and VAD duty cycle on LCN 131:

PXM1E_SJ.1.28.VISM8.a > cnfconcacparams 131 100 61

Step 4 To specify card level default policies for a fax/modem carrier loss and a fax/modem CAC failure, enter the cnfvbdpol command.


Note This command is not applicable in the AAL1 switching mode.


PXM1E_SJ.1.28.VISM8.a > cnfvbdpol <sysCarrLossPol> <sysCacRejPol>

Replace the above arguments with the values listed in Table 6-4.

Table 6-4 Parameters for cnfvbdpol Command 

Parameter
Description

sysCarrLossPol

Card level carrier loss policy.

1 = Revert to the previous codec.

2 = Maintain the upspeed codec.

sysCacRejPol

Card level CAC reject policy.

1 = Delete the connection.

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



You have completed configuring CAC on your VISM/VISM-PR 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


Note This command is not available in the AAL2 trunking mode.


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


Note This command is not available in the AAL2 trunking mode.


Configuring the TDM Side

Perform the following tasks to configure the TDM side of your networking application:

1. Configuring T1 and E1 Lines

2. Placing T1 and E1 Lines In Service

3. Placing T1 and E1 Lines Out of Service

4. Configuring the PXM1 and VISM/VISM-PR Cards Clocking Source

5. Configuring the PXM1E or PXM45 Card as Clocking Source

6. Configuring DS0 Channels

7. Add DS0 Endpoints to Lines

8. Configuring TDM Side Signaling for Applications Using CCS

9. Configuring TDM Side Signaling for Applications Using CAS

Configuring T1 and E1 Lines

This section deals with the configuration of the eight physical T1/E1 ports on the VISM/VISM-PR 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/VISM-PR back card.

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


Note Configure the DS0s on a line after you add and configure the line.



Step 1 To add a line to your VISM/VISM-PR card, enter the addln command with the following argument.

mgx8850.1.12.VISM8.a > addln <line_number>

Replace <line_number> with a value in the range 1-8. This example shows adding line 1.

mgx8850.1.12.VISM8.a > addln 1

Step 2 To configure signaling on the line, enter the cnflnsig command with the following arguments:

mgx8850.1.12.VISM8.a > cnflnsig <line_number> <signaling_type> 

Replace <line_number> with the value of the line you added in Step 1.

Replace <signaling_type> with one of the following values:

1 = CAS

2 = CCS

3 = No signaling

This example shows configuring line 1 with CAS.

mgx8850.1.12.VISM8.a > cnflnsig 1 1

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



Step 3 To configure the parameters of the line you added, enter the cnfln command with the following arguments:

mgx8850.1.12.VISM8.a > cnfln <line_number> <line_code> <line_length> <clk_src> <line_type> 
<loopback_detection> [circuit_identifier]

Replace the above arguments with the values listed in Table 6-5 for the cnfln parameters. This example shows the recommended E1 parameters.

mgx8850.1.12.VISM8.a > cnfln 1 3 9 2 7 1

Table 6-5 Parameters for cnfln Command 

Parameter
Description

line_number

Line number in the range 1-8.

line_code

Line coding method.

2 = B8ZS (T1)

3 = HDB3 for E1 lines

4 = AMI for T1 or E1 lines

line_length

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 = T1 for 000-131 ft.

11 = T1 for 131-262 ft.

12 = T1 for 262-393 ft.

13 = T1 for 393-524 ft.

14 = T1 for 524-655 ft.

15 = T1 for 655 and greater ft.

clk_src

Clock source.

1 = Loop clock

2 = Local clock

line_type

Line type.

Use one of the following values for E1 lines:

1 = dsx1ESF

2 = dsx1D4

3 = E1

4 = E1CRC

5 = E1MF

6 = E1MFCRC

7 = E1 Clear

8 = E1Q50

9 = E1Q50CRC

loopback_detection

Loopback detection.

1 = Disabled

2 = Enabled (This value is not applicable to E1 lines.)

circuit_identifier

(Optional) Name of the circuit in ASCII format. Range is 1-64 characters.


Step 4 To configure a line for alarm condition handling, enter the cnfalm command.

PXM1E_SJ.1.28.VISM8.a > cnfalm -ds1 <LineNum> -red <RedSeverity> -rai <RAISeverity> -neu 
<NEAlarmUpcount> -ned <NEAlarmDncount> -net <NEAlarmThreshold> -feu <FEAlarmUpcount> -fed 
<FEAlarmDncount> -fet <FEAlarmThreshold>

Replace the above arguments with the values listed in Table 6-6.

Table 6-6 Parameters for cnfalm Command 

Parameter
Description

LineNum

Line number in the range 1-8.

RedSeverity

Red alarm severity level.

1 = Minor

2 = Major

RAISeverity

Remote alarm indicator severity level.

1 = Minor

2 = Major

NEAlarmUpcount

Near end alarm up count. Range is 1-65535 ms.

NEAlarmDncount

Near end alarm down count. Range is 1-65535 ms.

NEAlarmThreshold

Near end alarm threshold. Range is 1-65535 ms.

FEAlarmUpcount

Far end alarm upcount. Range is 1-65535 ms.

FEAlarmDncount

Far end alarm down count. Range is 1-65535 ms.

FEAlarmThreshold

Far end alarm threshold. Range is 1-65535 ms.


Step 5 To enable or disable trunk conditioning on a line, enter the cnflntrunkcond command.


Note This command is not applicable to the AAL1 switching and switched AAL2 SVC modes.


PXM1E_SJ.1.28.VISM8.a > cnflntrunkcond <line_number> <trunkCondType>

Replace <line_number> with a value in the range 1-8.

Replace <trunkCondType> with one of the following values:

1 = Enable

2 = Disable

If you enable trunk line conditioning, VISM/VISM-PR 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 To set a specified line to the local loopback state, enter the addlnloop command.

PXM1E_SJ.1.28.VISM8.a > addlnloop <line_number>

Replace <line_number> with the line in which you want the local loopback, in the range 1-8.

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


Note The VISM CLI does not have a command for setting a line to the remote loopback state. Use the cnfbert command on the PXM1, PXM1E, and PXM45 cards to set a line to the remote loopback state.


Step 7 To display the values of the line, enter the dspln command with the line_number (1) argument value.

mgx8850.1.12.VISM8.a > dspln 1

The following example shows some of the sample output from the dspln command:

LineNum:                   1
LineConnectorType:         RJ-48
LineEnable:                Modify
LineType:                  dsx1E1CLEAR
LineCoding:                dsx1HDB3
LineLength:                G.703 120 ohm
LineXmtClockSource:        LocalTiming
LineLoopbackCommand:       NoLoop
LineSendCode:              NoCode
LineUsedTimeslotsBitMap:   0xfffffffe
LineLoopbackCodeDetection: codeDetectDisabled
LineSignalingType:         CCS
LineCcsChannels:           0x0
LineTrunkConditioning:     disable
CircuitIdentifier:         
TxDigitOrder:              aniThenDnis
TonePlanRegion:            
TonePlanVersion:           0
RingingTO:                 180
RingBackTO:                180
BusyTO:                    30
Type <CR> to continue, Q<CR> to stop:
ReorderTO:                 30
DialTO:                    16
StutterDialTO:             16
OffHookAlertTO:            5
RemoteRingbackMethod:      proxy
LineNumOfValidEntries: 8

Placing T1 and E1 Lines In Service

To place a T1 or E1 line in service, enter the cnflnis command with the <line_number> in the range 1-8.


Note This command is not applicable to VoIP trunking/AAL2 trunking and AAL2 trunking modes.


Placing T1 and E1 Lines Out of Service

To place a T1 or E1 line out of service, enter the cnflnoos command.

PXM1E_SJ.1.28.VISM8.a > cnflnoos <line_number> <shutdown_method>

Replace <line_number> with a value in the range 1-8.

Replace <shutdown_method> with one of the following values:

2 = Forceful shutdown (non-graceful)

3 = Graceful shutdown


Note This command is not applicable to VoIP trunking/AAL2 trunking and AAL2 trunking modes.


Configuring the PXM1 and VISM/VISM-PR Cards Clocking Source

Complete the following steps to configure the clocking source on your PXM1 and VISM/VISM-PR cards.


Note See "VISM/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/VISM-PR cards.



Step 1 To determine the single clock source, examine the entire configuration of the MGX 8000 Series platform.

The type of equipment connected to the VISM/VISM-PR T1 or E1 lines might dictate this choice. If the selected clock source is from one of the VISM/VISM-PR T1 or E1 lines, that line must be connected to port 1 of the VISM/VISM-PR back card. For more information on VISM/VISM-PR back cards and port locations, see Figure 2-3 on page 2-4.

Step 2 To configure the PXM1 card clock source, change card (cc) to the active PXM1 card.

Step 3 Enter the cnfclksrc command.

M8850_R1.1.7.PXM.a > cnfclksrc <slot.port> <clktyp> [-bits e1|t1]
[-revertive <enable|disable>]

Replace <slot.port> with the following values:

slot = 7, 8 or 1, 2

port = 1-n


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


Replace <clktype> with one of the following values:

P = Primary

S = Secondary

T = Tertiary

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 PXM1 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 4 Change card (cc) to your VISM/VISM-PR card.

Step 5 To configure the clocking option defined in Step 3 on your VISM/VISM-PR card, enter the cnfln command.

PXM1E_SJ.1.28.VISM8.a > cnfln <line_number> <line_code> <line_length> <clk_src> 
<line_type> <loopback_detection> [circuit_identifier]


Note You must include all argument values when using the cnfln command; however, the <line_number> and <clk_src> are the only relevant arguments for configuring the clocking source on your VISM/VISM-PR cards.


Replace the above arguments with the values listed in Table 6-7 for the cnfln parameters.

Table 6-7 Parameters for cnfln Command 

Parameter
Description

line_number

Line number in the range 1-8.

line_code

Line coding method.

2 = B8ZS (T1)

3 = HDB3 for E1 lines

4 = AMI for T1 or E1 lines

line_length

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 = T1 for 000-131 ft.

11 = T1 for 131-262 ft.

12 = T1 for 262-393 ft.

13 = T1 for 393-524 ft.

14 = T1 for 524-655 ft.

15 = T1 for 655 and greater ft.

clk_src

Clock source.

1 = Loop clock—Clocking comes from the T1/E1 line.

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

2 = Local clock—Clocking comes from the PXM1 card.

Note If the clocking source to the VISM/VISM-PR cards is from the PXM card, you must configure all lines on all VISM/VISM-PR cards as local.

line_type

Line type.

Use one of the following values for E1 lines:

1 = dsx1ESF

2 = dsx1D4

3 = E1

4 = E1CRC

5 = E1MF

6 = E1MFCRC

7 = E1 Clear

8 = E1Q50

9 = E1Q50CRC

loopback_detection

Loopback detection.

1 = Disabled

2 = Enabled (This value is not applicable to E1 lines.)

circuit_identifier

(Optional) Name of the circuit in ASCII format. Range is 1-64 characters.


Step 6 To ensure that you configured your clocking source correctly, enter the dsplns command.


You have completed configuring the clocking source for your PXM1 and VISM/VISM-PR 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

See the "Related Documentation" section on page xxx 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/VISM-PR T1 or E1 lines.

Table 6-8 describes the VISM/VISM-PR DS0 density when the cards are used in combination with the supported codecs.

Table 6-8 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


To configure a DS0 channel, complete the following tasks:

1. Add DS0 endpoints to lines.

2. Configure CCS or CAS signaling.

Add DS0 Endpoints to Lines

Complete the following steps to add DS0 endpoints to lines:


Step 1 To add a DS0 to a line, enter the addendpt command.

Step 2 This step ensures that a call with a specified endpoint is tied to a specific line and channel.

PXM1E_SJ.1.28.VISM8.a > addendpt <endpt_num> <ds1_num> <ds0_num>

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


Replace the above arguments with the values listed in Table 6-9.

Table 6-9 Parameters for addendpt Command 

Parameter
Description

endpt_num

Endpoint number.

Template 1

1-145 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Template 2

1-192 for T1

1-248 for E1

Template 3

1-120 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Template 4

1-64 for VISM

1-144 for VISM-PR

Template 5

1-192 for VISM-PR T1

1-248 for VISM-PR E1

ds1_num

Physical line number in the range 1-8.

ds0_num

DS0 number to which the endpoints are added.

1-24 for T1 lines

1-31 for non-CAS E1 lines

1-15, 17-31 for CAS E1 lines

Note If the application requires CAS signaling, issue the cnflnsig command before adding the endpoints.

endpts_num

Quantity of endpoints added.

For Lossless compression use the following range for template 5: VISM-PR E1 1-248.


Step 3 To add multiple endpoints with one command, enter the addendpts command.

mgx8850.1.12.VISM8.a > addendpts <endpt_num> <ds1_num> <ds0_num> <endpts_num>

Replace the above arguments with the values listed in Table 6-10 for the addendpts parameters.

Table 6-10 Parameters for addendpts Command 

Parameter
Description

endpt_num

First endpoint number of a range of consecutive endpoints.

Template 1

1-145 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Template 2

1-192 for T1

1-248 for E1

Template 3

1-120 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Template 4

1-64 for VISM

1-144 for VISM-PR

Template 5

1-192 for VISM-PR T1

1-248 for VISM-PR E1

ds1_num

Physical line number in the range 1-8.

ds0_num

DS0 number to which the endpoints are added.

1-24 for T1 lines

1-31 for non-CAS E1 lines

1-15, 17-31 for CAS E1 lines

Note If the application requires CAS signaling, issue the cnflnsig command before adding the endpoints.

endpts_num

Quantity of endpoints added.

Template 1

1-145 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Template 2

1-192 for T1

1-248 for E1

Template 3

1-120 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Template 4

1-64 for VISM

1-144 for VISM-PR

Template 5

1-192 for VISM-PR T1

1-248 for VISM-PR E1


Step 4 To place a specific endpoint—and so a specific DS1/DS0—into the loopback state in the TDM direction, enter the addendptloop command.

PXM1E_SJ.1.28.VISM8.a > addendptloop <endpt_num>

Replace <endpt_num> with one of the following values:

Template 1

1-145 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Template 2

1-192 for T1

1-248 for E1

Template 3

1-120 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Template 4

1-64 for VISM

1-144 for VISM-PR

Template 5

1-192 for VISM-PR T1

1-248 for VISM-PR E1

Step 5 To place a specific DS1/DS0 into one of three loopback states, enter the cnfds0loop command.

PXM1E_SJ.1.28.VISM8.a > cnfds0loop <line_number> <ds0_number> <lineloopback_type>

Replace the above arguments with the values listed in Table 6-11.

Table 6-11 Parameters for cnfds0loop Command 

Parameter
Description

line_number

Line number. Range is 1-8.

ds0_number

DS0 number.

1-24 for T1 lines

1-31 for non-CAS E1 lines

1-15, 17-31 for CAS E1 lines

Note If the application requires CAS signaling, issue the cnflnsig command before adding the endpoints.

lineloopback_type

Type of loop on the line.

1 = No loop

2 = Remote loop

3 = Local loop


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/VISM-PR card. CCS signaling is used for the following operating modes:

VoIP trunking/AAL2 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 To add a CCS channel to your VISM/VISM-PR card, enter the addccs command.

PXM1E_SJ.1.28.VISM8.a > addccs <line_number> <ds0_number> <LCN>

Replace the above arguments with the values listed in Table 6-12 for the addccs command.

Table 6-12 Parameters for addccs Command 

Parameter
Description

line_number

Line number. Range is 1-8.

ds0_number

DS0 number.

1-24 = T1 lines

1-31 = E1 lines

LCN

Logical channel number of the CCS channel to be added. Range is 131-510.


If you are configuring CCS for the AAL2 trunking operating mode, the CCS configuration is complete. Proceed to the "Configuring Bearer Processing" section.

Before proceeding to Step 2, ensure that you add a session and a session set described in the "Configuring ISDN PRI Backhaul" section.

Step 2 To add an ISDN PRI channel on a DS1/DS0, enter the addlapd command.

PXM1E_SJ.1.28.VISM8.a > addlapd <line_number> <ds0_number> |<lapd_side> 
<lapd_application_type>|

Replace the above arguments with the values listed in Table 6-13 for the addlapd command.

Table 6-13 Parameters for addlapd Command 

Parameter
Description

line_number

Line number. Type the value used in Step 1.

ds0_number

DS0 number. Type the value used in Step 1.

1-24 = T1 lines

1-31 = E1 lines

|lapd_side|

(Optional) The side of the LAPD link. Values are

1 = Network (Default)

2 = User

|lapd_application_type|

(Optional) Application type of the LAPD ISDN D channel. Values are

1 = PRI (Default)

2 = GR-303 (not unsupported)


Step 3 To specify the LAPD stack type, enter the cnflapdtype command.

PXM1E_SJ.1.28.VISM8.a > cnflapdtype <line_number> <ds0_number> <lapd_type>

Replace the above arguments with the values listed in Table 6-14 for the cnflapdtype command.

Table 6-14 Parameters for cnflapdtype Command 

Parameter
Description

line_number

Line number. Type the value used in Step 1.

ds0_number

DS0 number. Type the value used in Step 1.

1-24 = T1 lines

1-31 = E1 lines

lapd_type

Type of LAPD stack to configure on the specified line and DS0. Values are

1 = CCITT

3 = ATT5ESSPRA

4 = ATT4ESS

6 = NTDMS100PRA

7 = VN2 or 3

8 = INSNet

9 = TR6MFC

10 = TR6PBX

12 = AUSP

13 = NIL

14 = SSETSI

15 = BC303TMC

16 = BC303CSC

17 = NTDMS250

18 = Bellcore

19 = NI2 (Default)


Step 4 To specify the LAPD window size, enter the cnflapdwinsize command.

PXM1E_SJ.1.28.VISM8.a > cnflapdwinsize <line_number> <ds0_number> <window_size>

Replace the above arguments with the values listed in Table 6-15 for the cnflapdwinsize command.

Table 6-15 Parameters for cnflapdwinsize Command 

Parameter
Description

line_number

Line number. Type the value used in Step 1.

ds0_number

DS0 number. Type the value used in Step 1.

1-24 = T1 lines

1-31 = E1 lines

window_size

Maximum number of outstanding (unacknowledged) I-frames that can be accumulated before sending an acknowledgment. Range is 1-127. Default is 7.



Step 5 To specify the maximum allowable frame retransmissions, enter the cnflapdretrans command.

PXM1E_SJ.1.28.VISM8.a > cnflapdretrans <line_number> <ds0_number> <N200>

Replace the above arguments with the values listed in Table 6-16 for the cnflapdretrans command.

Table 6-16 Parameters for cnflapdretrans Command 

Parameter
Description

line_number

Line number. Type the value used in Step 1.

ds0_number

DS0 number. Type the value used in Step 1.

1-24 = T1 lines

1-31 = E1 lines

N200

Maximum frame retransmissions. Range is 1-10. Default is 3.


Step 6 To specify the two LAPD timers, enter the cnflapdtimer command.

PXM1E_SJ.1.28.VISM8.a > cnflapdretrans <line_number> <ds0_number> <timer_T200> 
<timer_T203>

Replace the above arguments with the values listed in Table 6-17 for the cnflapdtimer command.

Table 6-17 Parameters for cnflapdtimer Command 

Parameter
Description

line_number

Line number. Type the value used in Step 1.

ds0_number

DS0 number. Type the value used in Step 1.

1-24 = T1 lines

1-31 = E1 lines

timer_T200

T200 timer. Time (defined in milliseconds) between frame transmission initiations. Ranges are

1000-1023000 for PRI—in increments of 50. Default is 1000.

100-350 for GR-303—in increments of 50. Default is 150.

Note This value must be less than the value you specify for the timer_T203 argument value.

timer_T203

T203 timer. Maximum time (defined in milliseconds) allowed without a frame being exchanged. Ranges are

1000-1023000 for PRI —in increments of 1000. Default is 10000.

10000-300000 for GR-303 —in increments of 10000. Default is 30000.

Note This value must be greater than the value you specify for the timer_T200 argument value.


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/AAL2 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.

VoIP and AAL1 SVC

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 To configure the source of CAS-related timer parameters for a specified endpoint, enter the cnfcasparamsource command.

PXM1E_SJ.1.28.VISM8.a > cnfcasparamsource <endpt_num> <ParamSource>

Replace the above arguments with the values listed in Table 6-18 for the cnfcasparamsource command.

Table 6-18 Parameters for cnfcasparamsource Command 

Parameter
Description

endpt_num

The endpoint number which is to be configured with the source location, identified by the ParamSource argument value. Ranges are:

For template number 1:

For VISM, from 1 to 145

For VISM-PR T1, from 1 to 192

For VISM-PR E1, from 1 to 248

For template number 2:

For VISM T1, from 1 to 192

For VISM E1, from 1 to 248

For template number 3:

For VISM, from 1 to 120

For VISM-PR T1, from 1 to 192

For VISM-PR E1, from 1 to 248

For template number 4:

For VISM, from 1 to 64

For VISM-PR, from 1 to 144

For template number 5:

For VISM-PR T1, from 1 to 192

For VISM-PR E1, from 1 to 248

ParamSource

CAS-related timer parameters source location. Values are

1 = CAS application file (Default)

2 = Current VISM MIB



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


Step 2 To specify the minimum time an on hook-pattern must be present to be recognized as an on-hook signal, enter the cnfcasonhooktime command.

PXM1E_SJ.1.28.VISM8.a > cnfcasonhooktime <endpt_num> <OnHookMinTime>

Replace the above arguments with the values listed in Table 6-19 for the cnfcasonhooktime command.

Table 6-19 Parameters for cnfcasonhooktime Command 

Parameter
Description

endpt_num

Type the value used in Step 1.

OnHookMinTime

On-hook time (defined in milliseconds). Range is 10-1000 ms. Default is 300 ms.


Step 3 To specify the minimum time an off-hook pattern must be present to be recognized as an off-hook signal, enter the cnfcasoffhooktime command.

PXM1E_SJ.1.28.VISM8.a > cnfcasoffhooktime <endpt_num> <OffHookMintime>

Replace the above arguments with the values listed in Table 6-20 for the cnfcasoffhooktime command.

Table 6-20 Parameters for cnfcasoffhooktime Command 

Parameter
Description

endpt_num

Type the value used in Step 1.

OffHookMintime

Off-hook time (defined in milliseconds). Range is 10-1000 ms. Default is 2- ms.


Step 4 To specify the minimum and maximum make times and the minimum break time, enter the cnfcaswinktime command.

PXM1E_SJ.1.28.VISM8.a > cnfcaswinktime <endpt_num> <WinkMinTime> <WinkMaxTime> 
<WinkBreakTime>

Replace the above arguments with the values listed in Table 6-21 for the cnfcaswinktime command.

Table 6-21 Parameters for cnfcaswinktime Command 

Parameter
Description

endpt_num

Type the value used in Step 1.

WinkMinTime

Minimum make duration time (defined in milliseconds) of the wink. Range is 10-1000 ms. Default is 100 ms.

WinkMaxTime

Maximum make duration time (defined in milliseconds) of the wink. Range is 10-3000 ms. Default is 1000 ms.

WinkBreakTime

Minimum break duration time (defined in milliseconds) of the wink. Range is 10-1000 ms. Default is 20 ms.


A wink begins with an on-hook pattern, goes to off-hook, and returns to on-hook. All three make and break duration time argument values must be observed for the signaling sequence to be recognized as a wink.

Step 5 To specify the glare time, enter the cnfcasglaretime command.

PXM1E_SJ.1.28.VISM8.a > cnfcasglaretime <endpt_num> <GlareTime>

Replace the above arguments with the values listed in Table 6-22 for the cnfcasglaretime command.

Table 6-22 Parameters for cnfcasglaretime Command 

Parameter
Description

endpt_num

Type the value used in Step 1.

GlareTime

Glare time (defined in milliseconds). Range is 10-1000 ms. Default is 500 ms.


Step 6 To specify the guard time, enter the cnfcasguardtime command.

PXM1E_SJ.1.28.VISM8.a > cnfcasguardtime <endpt_num> <GuardTime>

Replace the above arguments with the values listed in Table 6-23 for the cnfcasguardtime command.

Table 6-23 Parameters for cnfcasguardtime Command 

Parameter
Description

endpt_num

Type the value used in Step 1.

GuardTime

Guard time (defined in milliseconds). Range is 10-1000 ms. Default is 800 ms.


Step 7 To configure the CAS dial delay (wait time), enter the cnfcasdialdelay command.

PXM1E_SJ.1.28.VISM8.a > cnfcasdialdelay <endpt_num> <DialDelayTime>

Replace the above arguments with the values listed in Table 6-24 for the cnfcasdialdelaytime command.

Table 6-24 Parameters for cnfcasdialdelaytime Command 

Parameter
Description

endpt_num

Type the value used in Step 1.

DialDelayTime

Wait time (defined in milliseconds) for outpulsing digits to the PBX after sending an off-hook event. Range is 10-1000. Default is 500.


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.


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 To specify the idle and seized codes for one or more endpoints, enter the cnfcascode command.

PXM1E_SJ.1.28.VISM8.a > cnfcascode <endpt_num> <idle_code> <seized_code> |<endpts_num>|

Replace the above arguments with the values listed in Table 6-25 for the cnfcascode command.

Table 6-25 Parameters for cnfcascode Command 

Parameter
Description

endpt_num

Type the value used in Step 1.

Note If the second (optional) endpts_num argument is specified, this argument value is the first endpoint in a consecutive number of endpoints.

idle_code

The 4-bit idle code. Range is 0-15 and represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively. Bit 3 is the most significant.

seized_code

The 4-bit seized code. Range is 0-15 and represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively. Bit 3 is the most significant.

|endpts_num|

(Optional) The last endpoint in a consecutive range of endpoints. Ranges are

For template number 1:

1-145 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

For template number 2:

1-192 for T1

1-248 for E1

For template number 3:

1-120 for VISM

1-192 for VISM-PR T1

1-248 for VISM-PR E1

For template number 4:

1-64 for VISM

1-144 for VISM-PR

For template number 5:

1-192 for VISM-PR T1

1-248 for VISM-PR E1


Step 10 To configure a local CAS bit pattern for a T1 line and DS0, enter the cnfds0localcas command.

PXM1E_SJ.1.28.VISM8.a > cnfds0localcas <line_number> <ds0_number> <cas_value> 
<cas_bit_pattern>

Replace the above arguments with the values listed in Table 6-26 for the cnfds0localcas command.

Table 6-26 Parameters for cnfds0localcas Command 

Parameter
Description

line_number

T1 line number on which to configure a local CAS bit pattern. Range is 1-8.

ds0_number

DS0 number on which to configure a local CAS bit pattern. Range is 1-24 for T1 lines.

cas_value

Value to enable or disable the local CAS pattern indicated by the cas_bit_pattern argument. Values are

1 = Enable

2 = Disable

cas_bit_pattern

The local 4-bit pattern expressed as a number in the range from 1 (default) to 15. The value specifies, in binary, the value of the A, B, C, and D signaling bits.

Note If local CAS is enabled, this argument is mandatory.


The cnfds0localcas command is not applicable if you have one of the following conditions:

The line is E1 or not enabled.

The DS0 is in a remote loop state.

The line signaling type is CAS.

Step 11 To add a CAS variant to your VISM/VISM-PR card, enter the addcasvar command.


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.


PXM1E_SJ.1.28.VISM8.a > addcasvar <variant_name> <file_name> |<cas_var_source>|

Replace the above arguments with the values listed in Table 6-27 for the addcasvar command.

Table 6-27 Parameters for addcasvar Command 

Parameter
Description

variant_name

Name of the CAS variant; a text string of 1 to 64 alphanumeric characters.

file_name

Name of the file that contains the signal definition for the CAS variant.

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

For user-configured files, the range is 2-32 alphanumeric characters.

|cas_var_source|

(Optional) 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 = Internal—File location is user-configured (built-in).

3 = External—File resides on the TFTP server.


Step 12 To configure a CAS variant and CAS timing parameters for the variant added in Step 11, enter the cnfcasvar command.

PXM1E_SJ.1.28.VISM8.a > cnfcasvar <variant_name> <country_code> <Tring> <Tpart> <Tcrit> 
<TMF>

Replace the above arguments with the values listed in Table 6-28 for the cnfcasvar command.

Table 6-28 Parameters for cnfcasvar Command 

Parameter
Description

variant_name

Name of the CAS variant. Type the value used in Step 11

country_code

Country code of the variant. The value must be a two-character text string.

Tring

Ringing time (defined in seconds). Range is 10-600 secs.

Tpart

Partial dial time (defined in seconds). Range is 10-10000 secs—in increments of 10 secs.

Tcrit

Critical timing (defined in seconds). Range is 0-10000 secs—in increments of 10 secs.

TMF

Interdigit timeout value for MF digits (defined in seconds). Range is 1-10 secs.


Step 13 To associate an endpoint with a CAS variant, enter the cnfcasendpt command.

PXM1E_SJ.1.28.VISM8.a > cnfcasendpt <endpt_number> <casVariantName>

Replace the above arguments with the values listed in Table 6-29 for the cnfcasendpt command.

Table 6-29 Parameters for cnfcasendpt Command 

Parameter
Description

endpt_number

Type the value used in Step 9.

casVariantName

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. Configuring Codecs

2. Configuring ECAN

3. Configuring Jitter

4. Configuring PNNI for AAL1/AAL2 SVCs

Configuring Codecs

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


Step 1 To specify a codec template, enter the cnfcodectmpl command.

PXM1E_SJ.1.28.VISM8.a > cnfcodectmpl <template_number>

Replace <template_number> 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 limited to 145 DS0s for VISM and 248 DS0s for VISM-PR.

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 is template 1 with T.38 support added. Template 3 is limited to 120 DS0s for VISM and 248 for VISM-PR.

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 144 channels for VISM-PR.

5 = G.711u, G.711a, G.726-16K, G.726-24K, G.726-32K, G.726-40K, G.729a, and G.729ab and Lossless codecs

Step 2 To specify various codec parameters for use in the VoIP operating mode, enter the cnfcodecparams command.

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.

PXM1E_SJ.1.28.VISM8.a > cnfcodecparams <codecType> <pktPeriod> |<codecPreference> 
<codecString> <ianaCodecNum>|

Replace the above arguments with the values listed in Table 6-30 for the cnfcodecparams command.

Table 6-30 Parameters for cnfcodecparams Command 

Parameter
Description

codecType

Type of coding/decoding to be performed on the data stream. Values are

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

15 = Lossless (VAD must be off)

pktPeriod

Packetization period (defined in milliseconds). Values are

10 (Default for all codecs except G.723)

20

30 (Default for G.723)

40

60

|codecPreference|

(Optional) Preference level of the codec you identified with the codecType argument value. Values are

0 = Ignore preference

Note A preference value of 0 results in the codec being excluded from the list of supported codecs during codec negotiation via xGCP.

Range of 1 (highest) to 13 (lowest)

|codecString|

(Optional) The xGCP codec string. Range is 1-20 ASCII characters.

|ianaCodecNum|

(Optional) IANA registered codec type. Range is 0-96.


Step 3 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, enter the cnfcodecneg command.

PXM1E_SJ.1.28.VISM8.a > cnfcodecneg <codecNegOpt>

Replace <codecNegOpt> with one of the following priority values:

1 = Local connection option (LCO) list, remote Session Description Protocol (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 To enable (or disable) ECAN for a line, enter the cnfecanenable command.

PXM1E_SJ.1.28.VISM8.a > cnfecanenable <lineNum> <ECANEnable>

Replace <lineNum> with a value in the range 1-8.

Replace <ECANEnable> with one of the following values:

1 = Disable

2 = Enable


Step 2 To set the residual echo control, enter the cnfecanrec command.

PXM1E_SJ.1.28.VISM8.a >cnfecanrec <lineNum> <residualEchoControl>

Replace <lineNum> the value used in Step 1.

Replace <residualEchoControl> with one of the following values:

1 = Cancel only

2 = Suppress residual

4 = Comfort noise

Step 3 To specify the ECAN algorithm maximum tail length, enter the cnfecantail command.

PXM1E_SJ.1.28.VISM8.a >cnfecantail <lineNum> <maximumTail>

Replace <lineNum> the value used in Step 1.

Replace <maximumTail> with one of the following values:

24 ms

32 ms (Default)

48 ms

64 ms

80 ms

96 ms

112 ms

128 ms

Step 4 To specify the ECAN algorithm return echo loss applied by ECAN DSPs, in decibels, enter the cnferl command.

PXM1E_SJ.1.28.VISM8.a > cnferl <DB_loss>

Replace <DB_loss> with one of the following values:

1 = 0 dB

2 = -3 dB

3 = -6 dB (Default)

4 = -10 dB

Step 5 To specify the fax/modem upspeed connection admission control (CAC) failure and carrier loss policies for a channel, enter the cnfconvbdpol command.

PXM1E_SJ.1.28.VISM8.a > cnfconvbdpol <LCN> <CarrierLossPol> <CACRejPol>

Replace the above arguments with the values listed in Table 6-31 for the cnfconvbdpol command.

Table 6-31 Parameters for cnfconvbdpol Command 

Parameter
Description

LCN

Logical channel number (LCN) of the connection. Range is 131-510.

CarrierLossPol

Carrier loss policy. Values are

1 = Revert to the previous codec

2 = Maintain the upspeed codec

3 = Unspecified (Default)

CACRejPol

CAC rejection policy. Values are

1 = Delete the connection

2 = Maintain the connection

3 = Unspecified (Default)


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 To set the jitter mode, enter the cnfjtrmode command.

PXM1E_SJ.1.28.VISM8.a > cnfjtrmode <jtr_mode>

Replace <jtr_mode> with one of the following values:

1 = Fixed. Cisco recommends fixed mode if latency jitter is constant.

2 = Adaptive. Cisco recommends adaptive if latency jitter is variable.

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 To specify the starting buffer size, enter the cnfjtrinitdelay command.

PXM1E_SJ.1.28.VISM8.a > cnfjtrinitdelay <jtr_initdelay>

Replace <jtr_initdelay> with one of the following values:

For template numbers 1, 3, 4, and 5 range is 0-100 in increments of 10.

For template number 2, range is 0-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). See Chapter 7, "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 Cisco MGX 8230 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.

This section contains the following topics:

1. Configuring PVC Connections for All Operating Modes

2. Configuring VoIP Switching/Trunking Operating Mode Parameters

3. Configuring AAL2 Trunking Operating Mode Parameters

4. Configuring Switched AAL2 PVC Operating Mode Parameters

Configuring PVC Connections for All Operating Modes

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


Step 1 To add an ATM PVC between the VISM card and the MGX 8000 Series platform PXM card, enter the addcon command.

PXM1E_SJ.1.28.VISM8.a > addcon <localVCI> <preference> <pvcType> <application> <PCR> 
<mastership> |<remoteConnId> <serviceType> [<scr> <mbs>]|

Replace the above arguments with the values listed in Table 6-32 for the addcon command.

Table 6-32 Parameters for addcon Command 

Parameter
Description

localVCI

Local virtual channel identifier (VCI) to be used for the connection. Range is 131-510. The value you enter for this argument is also used as the LCN.

preference

Preference level of the local VCI.

1 = Primary

2 = Secondary

pvcType

AAL type of connection.

1 = AAL5

2 = AAL2

3 = AAL1

application

The connection's application. It can be one of the following values:

1 = Control

2 = Bearer

3 = Signaling

Note If the connection is used for bearer and signaling, specify 2 for bearer.

PCR

Peak cell rate (PCR) described in cells per second. Ranges are

1-96000 for AAL5 bearer

1-20000 for AAL5 control PVC

1-50000 for T1 AAL2 PVCs

1-60000 for E1 AAL2 PVCs

1-400 for signaling PVCs in AAL2 trunking mode

Note If the serviceType argument is variable bit rate (VBR), the PCR argument value must be 15 or greater.

mastership

Connection type.

1 = Master

2 = Slave (Default)

remoteConnId

(Optional) Remote connection identifier. Specify this argument with the following format: nodename.slot.port.vpi.vci

Note This argument is used only when the mastership argument is set to 1 (Master).

serviceType

(Optional) Service type. It can be one of the following values:

1 = Constant bit rate (CBR)

2 = Variable bit rate real time (rt-VBR)

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

4 = rt-VBR3

5 = rt-VBR2

6 = nrt-VBR2

7 = nrt-VBR3

Note Use value 7 for VISM-PR to RPM-PR connections.

|scr|

(Optional) Sustainable cell rate (SCR) defined in cells per second. Range is from 15 to the value you configured for the PCR argument value.

Note This argument value is required if the serviccType argument value is in the range 2-7.

|mbs|

(Optional) Maximum burst size (MBS)—maximum number of cells transmitted at the peak cell rate. Range is from 1 cell to 10 times the value you configured for the scr argument value.

Note This argument value is required if the serviceType argument value is in the range 2-7.


Step 2 If you need to refine the configuration parameters of the connection added in Step 1 and identify the connection by the logical channel number, enter the cnfcon command.

PXM1E_SJ.1.28.VISM8.a > cnfcon <LCN> <PCR> <service_type> |<SCR_ingress> <MBS_ingress>|

Replace the above arguments with the values listed in Table 6-33 for the cnfcon command.

Table 6-33 Parameters for cnfcon Command 

Parameter
Description

LCN

Type the value you entered for the localVCI argument in Step 1.

PCR

Peak cell rate (PCR) described in cells per second.

Note The PCR argument value cannot be changed if the calls or connections for signaling and control are active.

Ranges are

1-400 = Signaling PVCs in AAL2 trunking mode

1-20000 = AAL5 control PVC

1-50000 = T1 AAL2 bearer PVCs

1-60000 = E1 AAL2 bearer PVCs

1-96000 = AAL5 bearer PVC

Note If the service_type argument value is a variable bit rate (VBR), the PCR argument value must be 15 or greater.

service_type

Service type. Values are

1 = Constant bit rate (CBR)

2 = Variable bit rate real time—rt-VBR

3 = Variable bit rate non-real time—nrt-VBR

4 = rt-VBR3

5 = rt-VBR2

6 = nrt-VBR

7 = nrt-VBR

Note For VISM-PR to RPM-PR connections, use values 4-7.

|SCR_ingress|

(Optional) Sustainable cell rate (SCR). Range is from 15 to the value you configured for the PCR argument value.

Note This argument value is required if the service_type argument value is in the range 2-7.

|MBS_ingress|

(Optional) Maximum burst size (MBS)—maximum number of cells transmitted at the peak cell rate. Range is from 1 cell to 10 times the value you configured for the SCR_ingresse argument value.

Note This argument value is required if the service_type argument value is in the range 2-7.


Step 3 To set a loopback on a VISM/VISM-PR PVC with the loopback in the direction of cellbus, enter the addconloop command.

PXM1E_SJ.1.28.VISM8.a > addconloop <LCN>

Replace <LCN> with a value in the range 131-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 To configure primary and secondary PVCs to provide protection in the event of a PVC failure, enter the cnfconprotect command.

PXM1E_SJ.1.28.VISM8.a > cnfconprotect <LCN> <protection> <lock_state> <fallback_LCN>

Replace the above arguments with the values listed in Table 6-34 for the cnfconprotect command.

Table 6-34 Parameters for cnfconprotect Command 

Parameter
Description

LCN

Primary logical channel number of the connection (PVC). Range is 131-510.

protection

Value to enable or disable PVC protection.

1 = Protected

2 = Unprotected

lock_state

PVC lock state. Values are

1 = Unlock

2 = Lock

fallback_LCN

Secondary (fallback) logical channel number of the connection (PVC). Range is 131-510.


Step 2 To configure the type of service for both control and bearer IP packets, enter the cnfdeftos command.


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


PXM1E_SJ.1.28.VISM8.a > cnfdeftos <control_precedence> <control_tos> |<bearer_precedence> 
<bearer_tos>|

Replace the above arguments with the values listed in Table 6-35 for the cnfdeftos command.

Table 6-35 Parameters for cnfdeftos Command 

Parameter
Description

control_precedence

Control precedence. Range is 0-7 (both inclusive). Default is 3.

control_tos

Type of service for control packets. Values are

0 = Default

1

2

4

8

|bearer_precedence|

(Optional) Bearer precedence (conforms to RFC 791). Range is 0-7 (both inclusive). Default is 5.

Note The bearer_precedence argument is used during call setup in cases where values are not supplied by a call agent.

|bearer_tos|

(Optional) Type of service for bearer packets. Values are

0 = Default

1

2

4

8

Note The bearer_tos argument is used during call setup in cases where values are not supplied by a call agent.


Step 3 To configure the VoIP transportation characteristics across the network, enter the cnfvoiptransparams command.

PXM1E_SJ.1.28.VISM8.a > cnfvoiptransparams <DtmfRelay> <CasBits> |<EventNego> 
<EventNegoPolicy> <SIDPayloadType>|

Replace the above arguments with the values listed in Table 6-36 for the cnfvoiptransparams command.

Table 6-36 Parameters for cnfvoiptransparams Command 

Parameter
Description

DtmfRelay

Value to enable or disable DTMF tone transportation to the remote endpoint.

1 = On (Default)

2 = Off

Note The DtmfRelay argument value must be set to 1 (on) when you are using codecs other than G.711 and G.726.

CasBits

Value to enable or disable CAS signaling transportation to the remote endpoint.

1 = On

2 = Off (Default)

|EventNego|

(Optional) Value to enable or disable whether VISM should negotiate how to send events.

1 = On. (Default) Attempt to negotiate how to send events.

2 = Off. Do not attempt to negotiate how to send events.

|EventNegoPolicy|

(Optional) Event negotiation policy. Values are

1 = None. Call agent driven.

2 = Proprietary (Default). Call agent driven and VISM proprietary events.

3 = All. Call agent driven and all event codecs specified by VISM.

|SIDPayloadType|

(Optional) Service ID (SID) payload type. Range is 0-255. Default is 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 To add a channel identifier (CID) to an AAL2 PVC, enter the addcid command.

PXM1E_SJ.1.28.VISM8.a > addcid <endpt_num> <LCN> <cid_num> <codec_type> <profile_type> 
<profile_number> <voice_activity_detection> <vad_init_timer> <echo_cancellation> 
<triple_redundancy_protection> <cas_signaling_transport> <dtmf_tone_transport_as_AAL2> 
<ICS_enable> <pktPeriod>

Replace the above arguments with the values listed in Table 6-37 for the addcid command.

Table 6-37 Parameters for addcid Command 

Parameter
Description

endpt_num

Endpoint number which is to be related to the LCN/CID pair being added.

For template number 1:

For VISM, from 1 to 145

For VISM-PR T1, from 1 to 192

For VISM-PR E1, from 1 to 248

For template number 2:

For VISM T1, from 1 to 192

For VISM E1, from 1 to 248

For template number 3:

For VISM, from 1 to 120

For VISM-PR T1, from 1 to 192

For VISM-PR E1, from 1 to 248

For template number 4:

For VISM, from 1 to 64

For VISM-PR, from 1 to 144

For template number 5:

For VISM-PR T1, from 1 to 192

For VISM-PR E1, from 1 to 248

LCN

Logical channel number (LCN) of the LCN/CID pair. Range is 131-510.

cid_num

Channel identification number of the LCN/CID pair. Range is 8-255.

codec_type

Type of coding/decoding to be performed on the data stream.

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

15 = Lossless (VAD must be off when codec is Lossless)

|profile_type|

(Optional) Profile type to be used for the CID.

1 = International Telecommunication Union (ITU) I.366.2

3 = Custom

Note If profile_type and profile_number argument values are both 1, you cannot turn VAD on.

|profile_number|

(Optional) Number of the profile.

1 = ITU profile

2 = ITU profile

3 = ITU profile

7 = ITU profile

8 = ITU profile

12 = ITU profile

100 = Custom profile

101 = Custom profile

110 = Custom profile

200 = Custom profile

201 = Custom profile

210 = Custom profile

|voice_activity_detection|

(Optional) Value to enable or disable voice activity detection (VAD).

1 = On

2 = Off (Default)

Note If profile_type and profile_number argument values are both 1, you cannot turn VAD on.

|vad_init_timer|

(Optional) VAD initial (holdover) timer. Range is 250-65535 ms. Default is 250 ms.

|echo_cancellation|

(Optional) Value to enable or disable echo cancellation (ECAN).

1 = On (Default)

2 = Off

|triple_redundancy_
protection
|

(Optional) Value to enable or disable triple redundancy protection for type 3 packets.

1 = On

2 = Off

Note If you select 1 for this argument value, either the cas_signaling_transport or dtmf_tone_transport_as_AAL2 argument value must be set to 1 (on).

|cas_signaling_transport|

(Optional) Value to enable or disable channel associated signaling (CAS) transport as AAL2 type3 packets.

1 = On (Default)

2 = Off

This parameter does not affect any inbound signaling.

|dtmf_tone_transport_as_AAL2|

(Optional) Value to enable or disable DTMF tone transport as AAL2 type 3 packets. It can be one of the following values:

1 = On (Default)

2 = Off

Note The dtmf_tone_transport_as_AAL2 argument value must be set to 1 (on) when the codec_type is configured for codecs other than G.711 and G.726.

|ICS_enable|

(Optional) Value to enable or disable idle code suppression (ICS) for the CID.

1 = Enable

2 = Disable

|pktPeriod|

(Optional) Packetization period (defined in milliseconds). This parameter applies only to G.729a compression.

10 ms

20 ms

30 ms

Note The pktPeriod argument applies only to G.729a compression (codec_type argument value = 4). If you have selected any other compression value, ignore this argument.

The pktPeriod 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.


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

Step 2 To enable or disable subcell multiplexing, enter the cnfaal2subcellmuxing command.

PXM1E_SJ.1.28.VISM8.a > cnfaal2subcellmuxing <muxing status>

Replace <muxing status> 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.2.


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 To create a new VCCI with an associated logical channel number and a remote ATM address, enter the cnfconvcci command.

PXM1E_SJ.1.28.VISM8.a > cnfconvcci <lcn> <vcci> <farend_addr_type> |<farend_addr>|

Replace the above arguments with the values listed in Table 6-38 for the cnfconvcci command.

Table 6-38 Parameters for cnfconvcci Command 

Parameter
Description

lcn

Logical channel number of the connection. Range is 131-510.

vcci

VCCI number. Range is 0-65535.

farend_addr_type

Address type of the VCCI. Values are

1 = Not applicable

Note This address type disassociates a VCCI, far end address type, and far end address from an LCN.

2 = NSAP (20-byte hexadecimal address)

3 = E.164 (1-15-byte decimal address)

4 = Gateway ID (1-64-byte ASCII character address)

5 = Unspecified

|farend_addr|

(Optional) Far end IP address. This argument is optional if the farend_addr_type value is 1 or 5.

This argument is mandatory if the farend_addr_type value is 2, 3, or 4.

E.164 farend address —Numeric value. Range is 1-15 characters, each 0-9.

GW ID farend address—ASCII value. Range is 1-64 characters.

NSAP farend address—Value is 20 bytes binary (in hex) needs 40 hexadecimal (0 - 9, A - F) characters to be typed in.


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 Operating Mode Profile Table" section.


Modifying the AAL2 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 6-1 shows the default values for ITU profile type 1.

Example 6-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 6-39 describes the fields shown in the display.

Table 6-39 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 6-40. This table is a summary of the output from the dspaal2profile command.

Table 6-40 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

Custom

201

0-15

40

Lossless

Off

40

5

5

G.711u

5

Custom

210

0-7

8-15

8-15

8-15

40

40

20

20

G.711u

G.726-32

G.729a

G.729ab

Off

Off

Off

SID729

1

2

2

2

5

10

20

20

5

5

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 profile table is not mandatory. Proceed to the "Configuring AAL2 PVC Parameters" section if the values shown in Table 6-40 are correct for your application and configuration requirements.



Step 1 To specify the preference for a given profile during call setup profile negotiation, enter the cnfprofparams command.

PXM1E_SJ.1.28.VISM8.a > cnfprofparams <profileType> <profileNumber> <profilePreference>

Replace the above arguments with the values listed in Table 6-41 for the cnfprofparams command.

Table 6-41 Parameters for cnfprofparams Command 

Parameter
Description

profileType

Profile type to be used for the CID.

1 = International Telecommunication Union (ITU) I.366.2

3 = Custom

profileNumber

Number of the profile.

1 = ITU profile

2 = ITU profile

3 = ITU profile

7 = ITU profile

8 = ITU profile

12 = ITU profile

100 = Custom profile

101 = Custom profile

110 = Custom profile

200 = Custom profile

201 = Custom profile

210 = Custom profile

profilePreference

Profile preference. It can be one of the following values:

0 = No preference; exclude the profile from xGCP profile negotiation

1-11 where 1 is the highest preference (default) and 11 is the lowest preference


Step 2 To configure the voice profile element for a specified profile, enter the cnfprofelemvoice command.

PXM1E_SJ.1.28.VISM8.a > cnfprofelemvoice <profileType> <profileNumber> <voice_codec_type> 
<pktPeriod> <sid>

Replace the above arguments with the values listed in Table 6-42 for the cnfprofelemvoice command.

Table 6-42 Parameters for cnfprofelemvoice Command 

Parameter
Description

profileType

Profile type to be used for the CID.

1 = International Telecommunication Union (ITU) I.366.2

3 = Custom

profileNumber

Number of the profile.

1 = ITU profile

2 = ITU profile

3 = ITU profile

7 = ITU profile

8 = ITU profile

12 = ITU profile

100 = Custom profile

101 = Custom profile

110 = Custom profile

200 = Custom profile

201 = Custom profile

210 = Custom profile

voice_codec_type

Type of coding/decoding to be performed on the data stream.

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

15 = Lossless (VAD must be off)

pktPeriod

Voice packetization period (defined in milliseconds).

5

10

20

30

40

sid

Silence insertion descriptor (SID).

1 = VAD off

2 = VAD on

3 = SID generic

4 = SID 729

5 = SID 723


Step 3 To configure the voiceband data element for a specified profile, enter the cnfprofelemvbd command.

PXM1E_SJ.1.28.VISM8.a > cnfprofelemvbd <profileType> <profileNumber> <codecType> 
<pktPeriod>

Replace the above arguments with the values listed in Table 6-43 for the cnfprofelemvbd command.

Table 6-43 Parameters for cnfprofelemvbd Command 

Parameter
Description

profileType

Profile type to be used for the CID.

1 = International Telecommunication Union (ITU) I.366.2

3 = Custom

profileNumber

Number of the profile.

1 = ITU profile

2 = ITU profile

3 = ITU profile

7 = ITU profile

8 = ITU profile

12 = ITU profile

100 = Custom profile

101 = Custom profile

110 = Custom profile

200 = Custom profile

201 = Custom profile

210 = Custom profile

codecType

Type of coding/decoding to be performed on the data stream.

1 = G.711u

2 = G.711a

3 = G.726-32k

6 = Clear channel (VAD must be off)

7 = G.726-16k

8 = G.726-24k

9 = G.726-40k

11 = G.723.1-H

13 = G.723.1-L

14 = G.723.1a-L

15 = Lossless (VAD must be off)

pktPeriod

Voice packetization period (defined in milliseconds).

5

10

20

30

40


Step 4 To specify the priority preference order for the profile lists, enter the cnfprofneg command.

PXM1E_SJ.1.28.VISM8.a > cnfprofneg <profileNegotiationOption>

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.

Replace <profileNegotiationOption> with one of the following values:

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 To configure the holdover and maximum wait time arguments, enter the cnfaal2timerparams command.

PXM1E_SJ.1.28.VISM8.a > cnfaal2timerparams <VadTimer> <CidFillTimer>

Replace <VadTimer> with the VAD holdover time in the range 250-65535 ms. Default is 250 ms.

Replace <CidFillTimer> with the maximum wait time for cell content filling when the next packet is not ready. Range is 250-65535 ms. Default is 250 ms.

Step 2 To enable or disable three parameters regarding the transport of CAS signaling, enter the cnfaal2transparams command.

PXM1E_SJ.1.28.VISM8.a > cnfaal2transparams <DtmfRelay> <CasBits> <Type3Redundancy>

Replace the above arguments with the values listed in Table 6-44 for the cnfaal2transparams command.

Table 6-44 Parameters for cnfaal2transparams Command 

Parameter
Description

DtmfRelay

Value to enable or disable DTMF tone transport as AAL2 type 3 packets.

1 = On. DTMF relay using RFC 2833

2 = Off. DTMF pass through (Default)

Note The DtmfRelay argument value must be set to 1 (on) if you are using codecs other than G.711 and G.726.

CasBits

Value to enable or disable CAS bits transportation.

1 = On

2 = Off (Default)

Type3Redundancy

Value to enable or disable triple redundancy protection for type 3 packets.

1 = On (Default)

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 for xGCP protocols. 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 6-1).

Figure 6-1 VISM to Call Agent Communication

Physical connectivity is through a PVC on an MGX 8000 Series platform PXM card OC-3 port, to a router (in the IP Connectivity cloud in Figure 6-1), 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 6-1 shows a TFTP server which also has an IP connection to VISM.

Complete the following tasks to configure the call agent interface:

1. Configuring Domain Names and IP Addresses

2. Setting Up Call Agents and Protocols

3. Configuring Gateway Control Protocols

4. Configuring 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 To specify a domain name for the VISM card, enter the cnfvismdn command.

PXM1E_SJ.1.28.VISM8.a > cnfvismdn <domain_name>

Replace the domain_name argument value with a text string of up to 64 alphanumeric characters; spaces are not allowed. Default name is cisco.com as shown in the following example:

PXM1E_SJ.1.28.VISM8.a > cnfvismdn cisco.com

Step 2 To specify the IP address and a subnet mask for the VISM card, type the cnfvismip command.

PXM1E_SJ.1.28.VISM8.a > cnfvismip <vismIpAddr> <netMask> [vismBearerIpAddr bearerNetMask]

Replace the above arguments with the values listed in Table 6-45 for the cnfvismip command.

Table 6-45 Parameters for cnfvismip Command 

Parameter
Description

vismIpAddr

Control IP address, in dotted decimal format (nnn.nnn.nnn.nnn), of the current VISM card.

netMask

Control local network subnet mask, in dotted decimal format (nnn.nnn.nnn.nnn). The recommended value is 255.255.255.248.

|vismBearerIpAddr|

(Optional) Bearer IP address, in dotted decimal format (nnn.nnn.nnn.nnn).

|bearerNetMask|

(Optional) Bearer IP subnet mask, in dotted decimal format (nnn.nnn.nnn.nnn).


The following example shows the IP address and subnet mask configured for the VISM card and the output of the command.

PXM1E_SJ.1.28.VISM8.a > cnfvismip 172.29.52.003 255.255.255.248
Attaching network interface atm0... done.

Step 3 To set up the domain names and IP address for the call agent(s), enter the cnftftpdn command.

PXM1E_SJ.1.28.VISM8.a > cnftftpdn <domain_name>

Step 4 Replace the domain_name argument value with the domain name you entered in Step 1.


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.


PXM1E_SJ.1.28.VISM8.a > cnftftpdn cisco.com

Step 5 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 To add a domain name for a call agent, enter the adddn command.

PXM1E_SJ.1.28.VISM8.a > adddn <mg_domain_num> <mg_domain_name> |<Resolution_Type>|

Replace the above arguments with the values listed in Table 6-46 for the adddn command.

Table 6-46 Parameters for adddn Command 

Parameter
Description

mg_domain_num

Domain number used to identify the domain in the range 1-11.

mg_domain_name

Call agent name, which is a text string of 1 to 64 alphanumeric characters.

|Resolution_Type|

(Optional) Resolution type to configure for the specified domain name. It can be one of the following values:

1 = Internal only (Default). You must statically provision all IP addresses on the VISM card for the domain name. The VISM card does not resolve the domain name using an external domain name server (DNS).

2 = External only. The VISM card attempts to resolve the domain name using an external DNS. Statistically configured IP addresses for this domain name are not used.

3 = Internal first. The VISM card attempts to resolve the domain name using an external DNS. The VISM card uses the statistically provisioned IP addresses for this domain name before using IP addresses from external resolution.

4 = External first. The VISM card attempts to resolve the domain name using an external DNS. The VISM card uses IP addresses from external resolution before using the statistically provisioned IP addresses.


Step 2 If you are not using an external DNS to resolve domain names (Resolution_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 To add the IP address for the domain name you added in Step 1, enter the adddnip command.

PXM1E_SJ.1.28.VISM8.a > adddnip <Resolution_index> <domain_name> <IP_address> <preference>

Replace the above arguments with the values listed in Table 6-47 for the adddnip command.

Table 6-47 Parameters for adddnip Command 

Parameter
Description

Resolution_index

Resolution number of the domain name. Range is 1-88.

domain_name

Call agent name, which is a text string of 1 to 64 alphanumeric characters.

IP_address

IP address which corresponds to the domain_name argument value in the following format: nnn.nnn.nnn.nnn.

preference

IP address resolution preference order in the range from 1 (highest) to 8 (lowest).

Note The preference order must be unique for all IP addresses in the call agent name you specify with the domain_name argument.


Step 4 To add the MGC to a redundancy group, enter the addmgcgrpentry command.

PXM1E_SJ.1.28.VISM8.a > addmgcgrpentry <Red_Group_Num> <mgcRedGrpMgcNum> <mgcRedGrpPref>

Replace the above arguments with the values listed in Table 6-48 for the addmgcgrpentry command.

Table 6-48 Parameters for addmgcgrpentry Command 

Parameter
Description

Red_Group_Num

Call agent redundancy group number. Range is 1-8.

mgcRedGrpMgcNum

Call agent identification number. Range is 1-8.

mgcRedGrpPref

Call agent preference value—The preference of the MGC within the group. Range is 1 (highest) to 8 (lowest).

Default is 1.


Step 5 To change the parameters of the MGC group, enter the cnfmgcgrpparam command.


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


PXM1E_SJ.1.28.VISM8.a > cnfmgcgrpparam <Red_Group_Num> <mgcRedGrpStateChgNtfy> 
|<mgcRedGrpPriority>|

Replace the above arguments with the values listed in Table 6-49 for the cnfmgcgrpparam command.

Table 6-49 Parameters for cnfmgcgrpparam Command 

Parameter
Description

Red_Group_Num

Call agent redundancy group number. Range is 1-8.

mgcRedGrpStateChgNtfy

State change notification. This parameter determines if messages, such as RSIPs, are sent to notify the call agent of a VISM card state change.

1 = Enable (Default)

2 = Disable

mgcRedGrpPriority

(Optional) Call agent priority value. It can be one of the following:

0 = No gateway initiated requests or commands are sent.

Range is from 1 (highest) to 8 (lowest). Default is 1.


Step 6 To associate a call agent redundancy group with a gateway control protocol, enter the addmgcgrpprotocol command.

PXM1E_SJ.1.28.VISM8.a > addmgcgrpprotocol <Red_Group_Num> <protocol_number> 
|<Qrntn_Persist> <Qrntn_Def> <Sign_OnOff> <Prov_Resp> <RspAck_Attr> <Disc_Proc> 
<Cancel_Graceful>|

Replace the above arguments with the values listed in Table 6-50 for the addmgcgrpprotocol command.

Table 6-50 Parameters for addmgcgrpprotocol Command 

Parameter
Description

Red_Group_Num

Call agent redundancy group number. Range is 1-8.

protocol_number

Protocol number. Values are

1 = MGCP 0.1

2 = SGCP 1.1+

3 = SRCP 1.0.2

4 = SGCP 1.5

5 = MGCP 1.0

6 = TGCP 1.0

|Qrntn_Persist|

(Optional) Sets the quarantine handling method for persistent events. Values are

1 = Quarantine persistent events (Default)

2 = Do not quarantine persistent events

|Qrntn_Def|

(Optional) Sets the default quarantine handling method for each protocol. Values are

1 = Step, process (Default for MGCP 1.0 and TGCP 1.0)

2 = Step, discard (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

3 = Loop, process

4 = Loop, discard

Note Step means one notification command is generated per notification request. Loop means multiple notification commands are generated per notification request.

|Sign_OnOff|

(Optional) Value to delete events.

1 = Delete events from the previous list which are not present in the current list. (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

2 = Delete events from the previous list, only if the event is present in the current list with a hyphen (-) as the parameter. (Default for MGCP 1.0 and TGCP 1.0)

|Prov_Resp|

(Optional) Value to enable or disable the sending of a provisional response.

1 = On (Default for MGCP 1.0 and TGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

|RspAck_Attr|

(Optional) Value to enable or disable sending a response acknowledgment.

1 = On (Default for MGCP 1.0 and TGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

|Disc_Proc|

(Optional) Value to enable or disable the disconnect method, which indicates that the endpoint has become disconnected and is now trying to establish connectivity.

1 = On (Default for MGCP 1.0 and TGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)

|Cancel_Graceful|

(Optional) Value to enable or disable VISM cancelling a previously issued graceful restart in progress command.

1 = On (Default for MGCP 1.0 and TGCP 1.0)

2 = Off (Default for MGCP 0.1, SGCP 1.1+, SRCP 1.0.2, and SGCP 1.5)


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 To configure a port number for a particular call agent and protocol, enter the cnfxgcppeer command.

PXM1E_SJ.1.28.VISM8.a > cnfxgcppeer <mgcNumber> <protocolNumber> <UDP_port>

Replace the above arguments with the values listed in Table 6-51 for the cnfxgcppeer command.

Table 6-51 Parameters for cnfxgcppeer Command 

Parameter
Description

mgcNumber

A number by which the call agent is identified in the range 1-8.

protocolNumber

Protocol number. Values are

1 = MGCP 0.1

2 = SGCP 1.1+

4 = SGCP 1.5

5 = MGCP 1.0

6 = TGCP 1.0

UDP_port

UDP port number in the range 1025-65535. Default is 2427.


Step 2 To specify the maximum waiting time before a Restart in Progress (RSIP) message is sent to the call agent, enter the cnfxgcpmwd command.

PXM1E_SJ.1.28.VISM8.a > cnfxgcpmwd <timeout value>

Replace <timeout value> with the maximum wait time in the range 0-600000 ms. Default is 10000 ms.


Note The <timeout value> argument value sets the maximum wait time for the entire VISM card, not for a particular call agent.


Step 3 To specify the VISM minimum and maximum wait time and number of retries for a call agent message acknowledgment, enter the cnfxgcpretry command.

PXM1E_SJ.1.28.VISM8.a > cnfxgcpretry <minTimeout> <retryCount> <maxTimeout>

Replace the above arguments with the values listed in Table 6-52 for the cnfxgcpretry command.

Table 6-52 Parameters for cnfxgcpretry Command 

Parameter
Description

minTimeout

Minimum time (defined in milliseconds) VISM waits for an acknowledgment message from the call agent. Range is 1-100000 ms. Default is  500 ms.

retryCount

Number of times that a call agent retransmits an unacknowledged message before determining that VISM is unreachable. Range is 1-10. Default is 3.

maxTimeout

Maximum time (defined in milliseconds) VISM waits for an acknowledgment message from the call agent. Range is 0-100000 ms.


Step 4 To specify the type of bearer channel VISM uses, if one is not specified by the call agent in protocol local connection options, enter the cnfxgcpbt command.

PXM1E_SJ.1.28.VISM8.a > cnfxgcpbt <networkType> <vcType> |<connType>|

Replace the above arguments with the values listed in Table 6-53 for the cnfxgcpbt command.

Table 6-53 Parameters for cnfxgcpbt Command 

Parameter
Description

networkType

Network type. Values are

1 = IP

2 = ATM

vcType

Virtual circuit type. Values are

1 = Permanent virtual circuit (PVC)

2 = Switched virtual circuit (SVC)

|connType|

(Optional) Connection type. Values are

1 = ATM Adaptation Layer Type 1 (AAL1)

2 = ATM Adaptation Layer Type 2 (AAL2)

3 = Not applicable

Note You must select 3 (not applicable) if you selected a networkType argument value of 1 (IP).


Step 5 To designate xGCP events as persistent, enter the addxgcppersistevt command.


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



Note This command is not applicable for TGCP.


PXM1E_SJ.1.28.VISM8.a > addxgcppersistevt <index> <persistent_event>

Replace <index> with a package event number in the range 1-16.

Replace <persistent_event> with one of the following values:

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 To specify the SRCP parameters for communication between VISM and the call agent, enter the cnfsrcppeer command.

PXM1E_SJ.1.28.VISM8.a > cnfsrcppeer <peerId> <port>

Replace <peerId> with a (call agent) identification number in the range 1-8.

Replace <port> with the UDP port number in the range 1025-65535.


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


Step 7 To configure the SRCP heartbeat interval and maximum UDP size for a specified call agent redundancy group, enter the cnfsrcppeergrpparam command.

PXM1E_SJ.1.28.VISM8.a > cnfsrcppeergrpparam <Red_Group_Num> <Heart_geat_interval> 
<max_pdu>

Replace the above arguments with the values listed in Table 6-54 for the cnfsrcppeergrpparam command.

Table 6-54 Parameters for cnfsrcppeergrpparam Command 

Parameter
Description

Red_Group_Num

Call agent redundancy group number. Range is 1-8.

Heart_geat_interval

Interval between heartbeats (defined in milliseconds). Values are

0

Range 100-65535

max_pdu

Maximum allowable UDP size. Range is 4095-65535.


Step 8 To configure the minimum and maximum timeout periods, and retry attempts, for transmitting SRCP commands to the call agent, enter the cnfsrcpretry command.

PXM1E_SJ.1.28.VISM8.a > cnfsrcpretry <minTimeout> <retryCount> <maxTimeout>

Replace the above arguments with the values listed in Table 6-55 for the cnfsrcpretry command.

Table 6-55 Parameters for cnfsrcpretry Command 

Parameter
Description

minTimeout

Minimum SRCP timeout (defined in milliseconds). Range is 1-10000. Default is 500.

retryCount

Maximum number of SRCP retries. Range is 0-10. Default is 3.

maxTimeout

Maximum SRCP timeout (defined in milliseconds). Range is 1- 10000. Default is 500.


Step 9 To configure CO4 bearer continuity, enter the cnfco4timer command.

PXM1E_SJ.1.28.VISM8.a > cnfco4timer <timeout>

Replace <timeout> with a value in the range 50-10000 ms. Default is 1000 ms.

Step 10 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 Chapter 5, "VISM/VISM-PR 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 To create a session set, enter the addsesset command.

PXM1E_SJ.1.28.VISM8.a > addsesset <set_number> <fault_tolerant>

Replace <set_number> with a value in the range 1-16.

Note Only session set number 1 is supported.

Replace <fault_tolerant> with one of the following values:

1 = Fault tolerance

2 = No fault tolerance

Step 2 To create a session group for a session set and a call agent, enter the addsesgrp command.

PXM1E_SJ.1.28.VISM8.a > addsesgrp <group_number> <set_number> <mgc_name>

Replace the above arguments with the values listed in Table 6-56 for the addsesgrp command.

Table 6-56 Parameters for addsesgrp Command 

Parameter
Description

group_number

Identifying session group number in the range 1-16.

set_number

Set number in the range 1-8.

Note Only session set number 1 is supported.

mgc_name

Domain name of the call agent, a text string 1-64 alphanumeric characters.


Step 3 To create an ISDN PRI backhaul RUDP session within a specified group, enter the addses command.


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


PXM1E_SJ.1.28.VISM8.a > addses <session_number> <group_number> <priority> <local_port> 
<remote_port>

Replace the above arguments with the values listed in Table 6-57 for the addses command.

Table 6-57 Parameters for addses Command 

Parameter
Description

session_number

Identifying session number in the range 1-64.

Note Up to 64 sessions can be created in a session group.

group_number

Identifying session group number to which the session is added in the range 1-16.

Note Currently, only group 1 is supported.

priority

Priority level determines which session becomes active if a session fails within the same group. Range is 1 (highest) to 4 (lowest).

local_port

Local port number is the VISM port number used for the session. Range is 1124-49151.

remote_port

Remote port number is the call agent port number used for the session. Range is 1124-65535.


Step 4 To change the timeout period for sending out an acknowledgment and the maximum number of acknowledgments that can accumulated before sending them, enter the cnfsesack command.

PXM1E_SJ.1.28.VISM8.a > cnfsesack <session_num> <acknowledgement_timeout> 
<acknowledgement>

Replace the above arguments with the values listed in Table 6-58 for the cnfsesack command.

Table 6-58 Parameters for cnfsesack Command 

Parameter
Description

session_num

Identifying session number in the range 1-64.

acknowledgement_timeout

Timeout period (defined in milliseconds) to send an acknowledgment. Range is 100-65535 ms. Default is 300.

acknowledgement

Maximum number of acknowledgments that can be accumulated before sending an acknowledgment. Range is 0-255. Default is 3.


Step 5 To configure the maximum number of resets that VISM performs before a connection is reset, enter the cnfsesmaxreset command.

PXM1E_SJ.1.28.VISM8.a > cnfsesmaxreset <session_number> <resets>

Replace <session_number> with the value you entered for the session_num argument in Step 4.

Replace <resets> with the maximum number of resets that the VISM card performs before a connection is reset. Range is 0-255. Default is 5.

Step 6 To configure the maximum segment size VISM can receive after sending a SYN message, enter the cnfsesmaxseg command.

PXM1E_SJ.1.28.VISM8.a > cnfsesmaxseg <session_number> <segment_size>

Replace <session_number> with the value you entered in Step 4.

Replace <segment_size> with the maximum segment size, in octets, that can be received by a VISM card after sending a synchronize message. Range is 30-65535.

Step 7 To configure the maximum number of segments that can be sent without getting an acknowledgment for a specific RUDP session, enter the cnfsesmaxwindow command.

PXM1E_SJ.1.28.VISM8.a > cnfsesmaxwindow <session_number> <window_size>

Replace <session_number> with the value you entered in Step 4.

Replace <window_size> with a value in the range 1-64.

Step 8 To configure the amount of idle time before sending a null segment, enter the cnfsesnullsegtmout command.

PXM1E_SJ.1.28.VISM8.a > cnfsesnullsegtmout <session_number> <timeout>

Replace <session_number> with the value you entered in Step 4.

Replace <timeout> with the idle time before a null segment is sent. Range is 0-65535 ms. Default is 2000 ms.

Step 9 To configure the maximum number of out-of-sequence packets that will be accumulated before sending an EACK packet, enter the cnfsesoutofseq command.

PXM1E_SJ.1.28.VISM8.a > cnfsesoutofseq <session_number> <packets>

Replace <session_number> with the value you entered in Step 4.

Replace <packets> with the maximum number of out-of-sequence packets that can be accumulated before an EACK packet is transmitted. Range is 0-255.


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


Step 10 To configure the local (VISM end) and remote (call agent end) port numbers for a session number, enter the cnfsesport command.

PXM1E_SJ.1.28.VISM8.a > cnfsesport <session_number> <local_port> <remote_port>

Replace the above arguments with the values listed in Table 6-59 for the cnfsesport command.

Table 6-59 Parameters for cnfsesport Command 

Parameter
Description

session_number

Value you entered in Step 4.

local_port

Local port number. The VISM port number used for the session. Range is 1124-49151.

remote_port

Remote port number. The call agent port number used for the session. Range is 1124-65535.


Step 11 To configure the retransmission of unacknowledged packet timeout value and the maximum number of consecutive retransmission attempts before the connection is considered failed, enter the cnfsesretrans command.

PXM1E_SJ.1.28.VISM8.a > cnfsesretrans <session_number> <retransmit_timeout> 
<max_retransmits>

Replace the above arguments with the values listed in Table 6-60 for the cnfsesretrans command.

Table 6-60 Parameters for cnfsesretrans Command 

Parameter
Description

session_number

Value you entered in Step 4.

retransmit_timeout

Timeout period (defined in milliseconds) to send an acknowledgment. Range is 100-65535 ms. Default is 600 ms.

max_retransmits

Maximum number of retransmissions. Range is 0-255. Default is 3.


Step 12 To configure the amount of time VISM waits for the transfer state before executing an auto reset, enter the cnfsesstatetmout command.

PXM1E_SJ.1.28.VISM8.a > cnfsesstatetmout <session_number> <timeout>

Replace <session_number> with the value you entered in Step 4.

Replace <timeout> with the maximum number of milliseconds that VISM waits for a transfer state before executing an auto reset. Range is 0-65535. Default is 2000.

Step 13 To configure the maximum number of attempts to synchronize VISM with the call agent, enter the cnfsessyncatmps command.

PXM1E_SJ.1.28.VISM8.a > cnfsessyncatmps <session_number> <sync_attempts>

Replace <session_number> with the value you entered in Step 4.

Replace <sync_attempts> with the maximum number of attempts to synchronize with the call agent. Range is 1-32. Default is 5.

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 Chapter 7, "CLI Commands," to further configure your VISM cards, if necessary.

Additional VISM Features

The following features are available for users of VISM 3.2:

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

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

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

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 mu-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 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 out-pulsing 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 Features

You can configure different CAS packages on different endpoints. The following CAS features are supported in this release.

Programmable Tone Plans

You can 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.

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

Table 6-61 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).


You can 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.

Feature Group D

Feature Group D (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. 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 this release.

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

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 6-62 describes the configuration requirements for VISM/VISM-PR in combination with the MGX 8000 Series switches and supported processor modules.

Table 6-62 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


For information on installing and maintaining the PXM1, PXM1E, and PXM45 cards, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide Release 2 through 4.


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 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.2 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 G723 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 6-8 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 6-63 to configure the announcement file system feature.

Table 6-63 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 supports the following MGCP 1.0 features:

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 6-64 to configure the MGCP 1.0 feature.

Table 6-64 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.2 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 6-65 to configure the RSVP-based admission control feature.

Table 6-65 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 Features

The following features are supported with this release with 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 Processor Module 1E card (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 6-66 describes the VISM/VISM-PR DS0 density when the cards are used in combination with clear channel and the supported codecs.

Table 6-66 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.