Cisco Voice Switch Service Module (VXSM) Configuration Guide Release 5.4 - Configuring VoIP Switching Applications [Cisco MGX 8880 Media Gateways]

Table Of Contents

Configuring VoIP Switching Applications

Quick Start Procedure

Configuring the PXM-45 Card

Configuring AXSM or RPM-XF

AXSM Card Configuration

Configuring RPM-XF Cards

Creating a PNNI Resource Partition

Creating an ATM Subinterface

Creating a Gigabit Ethernet Interface

Configuring VXSM Cards

Configuring the TDM Interface

Identifying Voice Circuits

Voice Interfaces

Configuring TDM Lines

Setting Up VXSM Connections

Configuring MGC Interfaces for Call Control

Gateways Using H.248 MGC Protocol

Setting Up H.248 MGCs and MGC Groups

Configuring H.248 Protocol

Configuring MGC H.248 Profile

Configuring H.248 Congestion and Overload

Configuring H.248 Transparent RTP IP-IP Connections

Gateways Using XGCP MGC Protocol

Setting Up XGCP Media Gateway Controllers and Media Gateway Controller Groups

XGCP Protocol Configuration

Configuring an MGC XGCP Profile

Configuring CALEA

Configuring MGC Redundancy

Configuring Backhaul

Configuring the MGC Link

Configuring RUDP (for PRI only)

Configuring H.248 over SCTP (for PRI and DPNSS)

Configuring the TDM Network Link

Configuring LAPD

Configuring DPNSS

Configuring E911 Emergency Services

Configuring Bearer and Signaling Security Features

Setting Up Security Policies

Configuring Phase 2 Signaling Security

Configuring Phase 2 Signaling Security

Configuring Bearer Security

Enable Security Features

Configuring More Features

Configuring VoIP Switching Applications

You can configure a Cisco MGX 8850 or 8880 switch equipped with VXSMs that functions as a media gateway to meet the requirements of many applications. In VoIP switching applications, the voice TDM interface, the packet network interface, and the interface to a call agent require configuration. The switching application uses VXSM cards, the PXM-45 card, and either the AXSM or the RPM-XF cards.

The interface to the packet network can be either:

•VoIP over Ethernet—An RPM-XF card is used, or

•VoIP over ATM—An AXSM card is used

These cards function together and must be configured accordingly.

VoIP switching configuration consists of the following tasks.

1. Initial PXM-45 card configuration to configure the gateway as a whole.

2. AXSM or RPM-XF card configuration to set up the interface to the VoIP/ATM or VoIP/Ethernet network.

3. VXSM card configuration to set up the TDM interface and to make the connection between the TDM and network interfaces.

4. Media Gateway Controller and associated protocol configuration to set up the interface between the gateway and the gateway controller.

Note A VXSM card supports three media gateway control protocols but only one at a time. The user must choose between either H.248, MGCP, or TGCP. The choice is made by executing the setrev command on the PXM. In this command, the user specifies the VXSM card (by slot number) and selects the MGCP protocol as one of the parameters. The effect of this command is to load a firmware image in the VXSM card with the "not selected" protocol commands disabled. Note that the CALEA images do not support H.248.

Quick Start Procedure

Table 3-1 shows an overview of tasks and commands required to set up the media gateway for VoIP switching application. In addition, the same procedure is presented later in this chapter in greater detail. For details on the commands used in this procedure, refer to the Cisco Voice Switch Service Module (VXSM) Command Reference.

Note VXSM does not support both AXSM and RPM-XF packet network interfaces on the same card. The following procedure is for gateways using either an RPM-XF or an AXSM card as the interface to the network. Use the RPM-XF or AXSM commands as appropriate for your application.

However, AXSM and RPM-XF cards can be configured in the same media gateway provided they are used on separate VXSM cards.

Table 3-1 Configuration for VoIP

Card Type

Major Task

Subtask/Commands

PXM-45

Basic gateway setup

Basic PXM-45 setup commands

cnfname
cnfdate
cnftmzn
cnftmznmgt
cnftime
addcontroller
ipifconfig
addsct

PXM-45

Select MGCP protocol

setrev

AXSM for VoIP over ATM

or

RPM-XP for VoIP over Ethernet

Set up interface to network using either the AXSM or RPM-XF cards

If using RPM-XF

RPM-XF Setup Commands

Logon

enable
password
config terminal

Create PNNI partition

interface switch1
switch partition
ingress_percentage-bandwidth
egress-percentage-bandwidth
vci
vpi
connection-limit
end

Create ATM subinterface

interface
ip
pvc
vbr_nrt
encapsulation
exit-vc

Create Gigabit Ethernet interface

interface gigabitethernet
ip address
negotiationauto
no shutdown
copy

VXSM

Setup VXSM card

Create VXSM resource partition
addrscprtn

Bring up VXSM Lines
upln
uppath -sts -ds1 (OC-3 only)

Config Voice Interfaces
addvif
cnfpath -sts -payload (OC-3 only)

AXSM or RPM-XF

Create slave end of each connection at RPM-XF or AXSM: one for bearer and one for control. This task can be repeated for up to 8 bearer connections.

If using RPM-XF, setup slave end on RPM-XF

switch connection
rmbs
rpcr
rscr
cpmm-id
pcr
csr

VXSM

Create master end of connections on VXSM: one for bearer and one for control. This task can be repeated for each of the slaves configured in the previous step.

VXSM connection command

addcon

VXSM

Assign an IP address on VXSM for each connection.

addconip

VXSM

Configure MGC Interface on VXSM

If MGC protocol is H.248

Configure MGC

addmgcdn
cnfmgc
addmgcip
addmgcgrpmgc

Configure H.248 Protocol

cnfprotocolport
addh248assoc
cnfh248rootpkg
cnfh248param
cnfh248mg
addh248prof
cnfh248nameschema

Configure VIF termination

addvif (if not already done)
cnfvifterm
addviftermtype

VXSM

Bring gateway into service

cnfh248is

Configuring the PXM-45 Card

Log on to the PXM-45 card and perform the following steps to configure the PXM-45 card for VoIP using the VXSM. The PXM-45 has a large number of commands. These steps deal only with the minimum commands required to set up the MGX 8850 as media gateway.

Step 1 Use the cnfname command to give the MGX 8850 a node name.
unknown.7.PXM.a > cnfname <node name> 
Enter up to 32 characters for the new node name, (node name is case-sensitive).

For example:
unknown.7.PXM.a > cnfname gateway1 
After the user responds Yes to a confirmation request, the name is changed to gateway1

Step 2 Use the cnfdate command to set the date.
gateway1.7.PXM.a > cnfdate <mm/dd/yyyy>
Step 3 Use the cnftmzn command to set the time zone.
geteway1.7.PXM.a > cnftmzn <timezone>
Step 4 Use the cnftmzngmt command to set an offset if an offset from GMT is to be used.
geteway1.7.PXM.a > cnftmznmgt <timeoffsetGMT>			Offset can be from -12 to +12.
Step 5 Use the cnftime command to enter the time.
geteway1.7.PXM.a > cnftime <hh:mm:ss>
Step 6 Use the addcontroller command to add a PNNI controller to the PXM card
geteway1.7.PXM.a > addcontroller <cntrlrId> i <cntrlrType> <slot> [cntrlrName
cntrlrId is the controller ID, enter 2 to specify a PNNI controller.

"i" stands for internal

cntrlrType is the controller type, enter 2 to specify a PNNI controller type.

slot is the PXM-45 slot in the MGX 8850, enter 7 or 8 as appropriate.

cntrlrName is an optional controller name, enter a text name is desired.

Step 7 Use the ipifconfig command to specify a LAN IP address for the node.
geteway1.7.PXM.a > ipifconfig lnPci0 <IP_Addr>[<netmask <Mask>]
Specify the values for the IP address and its associated netmask.

Step 8 Setup a Service Class Template (SCT) for the AXSM card. The SCT file name has the following format:
AXSM_SCT.CARD.2.V1

The SCT file must have been ftp'd to the node's PXM-45 disk in the C:SCT/TEMP directory

Use the dspsctchksum command to display the checksum value of the file. Note the value of checksum

Note A Service Class Template (SCT) is a collection of ATM configuration parameter settings that are stored in a single file and can be applied to multiple lines or ports. SCT files include the following types of configuration data:

General link parameters
COSB (Class of Service Buffers) parameters
Virtual circuit threshold parameters
COSB threshold parameters

Step 9 Use the addsct to move the file to the F:SCT/AXSM directory on the PXM-45 disk. This has the effect of installing the SCT.
geteway1.10.AXSM.a > addsct <card type> <sct type> <sct ID> <Maj ver> <chksum>
cardtype is the card whose SCT you want to make available to the card by installing the SCT in the appropriate directory. Enter 1 for AXSM

scttype identifies either a port-level or a card-level SCT. Enter 2 for card level.

SCT ID refers to a specific service class template. The SCT is either provided by Cisco or created through CWM. Possible IDs are, Cisco-provided: 1-100 and User-created: 101-255. The default SCT ID is 0.

Maj ver is the major version number of the file. This number is assigned by Cisco.

checksum is the checksum for the file. Use the value obtained from the dspsctchksum command. The value is also published in the relevant release notes.

Step 10 Repeat Steps 8 and 9 for the port SCT to be used by the PXM-45. In the addsct command, specify 1 (port level) for the scttype parameter.

Step 11 Select the media gateway controller protocol for the card. Use the setrev command and select either H.248 or TGCP. This command force loads the image to the VXSM with only the selected MGCP commands enabled.

Configuring AXSM or RPM-XF

The following procedure configures the gateway's interface to the packet network. Use the AXSM card configuration procedure if the interface to the network is ATM. Use the RPM-XF card configuration procedure if the interface to the network is Ethernet.

AXSM Card Configuration

Log on to the AXSM card and perform the following steps to configure the AXSM card for VoIP/ATM using the VXSM. The AXSM has a large number of commands. These steps deal only with the minimum commands required to setup the MGX 8880 as a media gateway.

Step 1 Use the upln command to bring up the AXSM lines to be used by the gateway. This command establishes minimal connectivity over the line.
geteway1.10.AXSM.a > upln <bay.line> 
For bay, enter 1 if the line on the back card is in the upper bay and enter 2 if it is in the lower bay. For line, enter the back card port number to which the line is connected.

Step 2 Use the cnfln command to configure a SONET lines.
geteway1.10.AXSM.a > cnfln -sonet <bay.line> -slt <LineType> -clk <clock source> 
Enter the bay and line of the line being configured (see upln above). For LineType, enter 1 for SONET or 2 for SDH. For clockSource, enter 1 to use a clock received over the line from a remote node or 2 (the default) to use the local timing defined for the local node.

Step 3 Use the addport command to enable ATM communications over the line.
geteway1.10.AXSM.a > addport <ifNum> <bay.line> <guaranteedRate> <maxRate> <sctID> 
<ifType> 
For ifNum, enter a number from 1 to 60 to identify this interface. The interface number must be unique on the card to which it is assigned. For UNI and NNI ports, you can assign one logical interface per line.

For guaranteedRate and maxRate, enter an OC3 value in the range of 50 to 353207 cells per second.

For ifType, enter 1 for UNI, 2 for NNI

When AXSM is connected to an ATM router (ATM end devices), UNI is used. When AXSM is connected to core ATM NW devices, NNI is used

Step 4 Use the addpart command to create resource partition on the AXSM card. This command automatically creates a controller partition on the AXSM card. This command should be executed for each port that uses the controller.
geteway1.10.AXSM.a > addpart <ifNum> <partId> <ctrlrId> <egrminbw> <egrmaxbw> <ingminbw> 
<ingmaxbw> <minVpi> <maxVpi> <minVci> <maxVci> <minConns> <maxConns>
For ifNum, enter the port number. For partId, enter 1 for PNNI. For cntrlid, enter 2 for PNNI.

The remaining parameters are used to specify maximum and minimum values for vpi/vci, bandwidth, connections, etc., see the Cisco MGX 8850 (PXM45 and PXM1E) Command Reference, Release 5 for details.

Configuring RPM-XF Cards

The object of RPM-XF card configuration is to:

•Create a PNNI resource partition

•Create an ATM subinterface

•Create a gigabit Ethernet interface

Creating a PNNI Resource Partition

Perform the following steps to create a PNNI resource partition for the RPM-XF.

Step 1 Use the cc command to switch to the RPM-XF card.

Step 2 Enter the enable command and password for the router.
Router>enable
Password: 
Step 3 Enter the config terminal command.
Router#config terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#
Step 4 Enter the interface command
Router(config)#interface Switch1
Step 5 Enter the switch partition command.
(config-if)# switch partition {vcc | vpc} <partId> <ctrlrId> 
For partId the range is 1 to 10; 1 is reserved for PNNI. Enter 1.

For ctrlrId, the range is 2to 255; 2 is reserved for PNNI. Enter 2.

Thus: (config-if)# switch partition 1 2

Step 6 Enter the ingress-percentage-bandwidth command at the swpart prompt to specify the minimum and maximum ingress percentage bandwidth.
(config-if-swpart)# ingress-percentage-bandwidth <ingMinPctBw> <ingMaxPctBw> 
For example, (config-if-swpart)#ingress-percentage-bandwidth 10 100

Step 7 Enter the egress-percentage-bandwidth command to specify the minimum and maximum egress percentage bandwidth.
(config-if-swpart)# egress-percentage-bandwidth <egrMinPctBw> <egrMaxPctBw> 
For example, (config-if-swpart)# egress-percentage-bandwidth 10 100

Step 8 Enter the vpi command to specify the minimum and maximum vpi.
(config-if-swpart)# vpi <min_vpi> <max_vpi> 
For example, (config-if-swpart)# vpi 20 240

Step 9 Enter the vci command to specify the minimum and maximum vci.
(config-if-swpart)# vci <min_vci> <max_vci>
For example, (config-if-swpart)# vci 50 65535

Step 10 Enter the connection-limit command to specify the minimum and maximum connection limits.
(config-if-swpart)# connection-limit <mincon><maxcon>
For example, (config-if-swpart)# connection-limit 1000 8000

Creating an ATM Subinterface

Perform the following steps to create an ATM subinterface. This procedure is in preparation for creating the master end of the connection to the VXSM card.

Step 1 Set up a switch subinterface

a. Enter the interface command.
Router(config)# interface switch 1<subinterface> <multipoint | point-to-point | mpls | 
tag-switching> 
Specify 1 for subinterface and point-to-point for the type of interface.

For example,

Router(config)#interface switch 1.1 point-to-point

b. Enter the ip command to add an IP address to the subinterface.
Router(config-subif)# ip address
 <ip_addr> <subnet_mask> 
Enter the IP address for the subinterface and a mask of 255.255.255.0. The IP address should be the same as that used when setting up the slave end of the connection on the VXSM.

The following example adds IP address 1.1.1.1 to subinterface 1 and defines the network mask as 255.255.255.0

c. Enter the pvc command to add a PVC to the subinterface.
Router(config-subif)# pvc 
<vpi>/<vci> 
Note The VPI and VCI values you enter for the PVC must be within the ranges set for the PNNI controller when the PNNI partition was defined for the switch interface.

After you enter this command, the switch enters virtual circuit configuration mode for this PVC.

d. Specify the PVC variable bit rate parameters.
Router(config-if-atm-vc)# vbr-nrt pcr scr mbs
Enter values for PCR and SCR in kbps and MBS in cells.

e. Specify type of encapsulation to IP over AAL5.
Router(configu-if-atm-vc)#encapsulation aal5mux ip
f. When you have finished configuring the PVC, enter the exit-vc command to return to subinterface configuration mode.
Router(config-if-atm-vc)#exit-vc
Creating a Gigabit Ethernet Interface

Perform the following steps to configure the RPM-XF gigabit Ethernet interface to the network.

Step 1 At the Router> prompt enter the enable command and enter your password at the prompt. The router will enter the privileged EXEC mode.

Step 2 Use the config -t command to change to global configuration mode.
Router#config -t
Step 3 At the global configuration prompt, specify the new interface to configure by entering the interface gigabitethernet command
Router(config)# interface gigabitethernet <bay/port> 
For example, Router(config)# interface gigabitethernet 1/0

Step 4 Assign an IP address and a subnet mask to the interface with the ip address command.
Router(config-if)# ip address <ip address><netmask>
For example, Router(config-if)# ip address 192.168.255.255 255.255.255.0

Step 5 Modify the MGX-1GE back card configuration.

a. Use the negotiation auto command to permit negotiation of the flow control parameter.

b. In configuration mode, use the loopback command to configure loopback testing

Step 6 Enter the no shutdown command to enable the interface.
Router(config-if)# no shutdown
Step 7 When all of the configuration subcommands are complete, press Cntl-Z to exit configuration mode.

Step 8 Write the new configuration to memory.
Router# copy running-config startup-config
The system displays an OK message when the configuration is stored.

Configuring VXSM Cards

Log on to the VXSM card and perform the following procedures to configure the VXSM card for VoIP. The VXSM card has a large number of commands. These steps deal only with the minimum commands required to set up the MGX 8880 as a media gateway for a VoIP switching application. Setting up other VoIP features such as CALEA, Bearer and Signaling Security, and Redundancy are included later in this chapter.

Depending upon the application, VXSM accesses the network either through RPM or AXSM cards. This is accomplished through PVC connections created between the VXSM and its network cards.

In switching applications, two connections types need to be made. The first type is a bearer connection for voice traffic over the packet network, up to eight such PVCs can be configured. The second type is a control connection for control messages to and from the media gateway controller (call agent), only one control connection per VXSM card can be configured.

Configuring the TDM Interface

Identifying Voice Circuits

The OC-3, 48 T1/E1, and 6 T3/E3 versions of the VXSM cards, support a variety of multiplexing schemes for interfacing to voice circuits. These schemes fall into four major categories:

•Multiplexing under the OC-3 standards.

•Multiplexing under the SDH (Synchronous Digital Hierarchy) standards.

•Multiplexing under the T1 and E1 standards.

•Multiplexing under the T3 and E3 standards (T3 only in Release 5.2).

Many of the VXSM commands require the user to specify a line, a single voice circuit, or a group of voice circuits. The following paragraphs describe how these items are specified for the different multiplexing schemes.

OC-3 Systems

Specifying a DS0 stream from the highly multiplexed bit stream of OC3 is performed using the relationships (paths) shown in Figure 3-1.

Figure 3-1 OC-3 Hierarchical Relationship

The bit stream interfaces with VXSM via one of the four physical lines in the OC3 back card. This interface is usually in the upper bay (but, when a redundant back card is used and is active, it is in the lower bay).

For a particular line, the OC3 stream consists of three paths and, depending upon the format, a path consists of either 7 virtual tributary groups (vtg) or 28 DS1s. A vtg can be further divided into either four virtual tributaries (version 1.5) or three virtual tributaries (version 2.0). The DS1 and the virtual tributaries (vt) consist of 24 T1 DS0s for T1 or 31 DS0s for E1.

As shown in the diagram, the relationship between DS0s and physical ports can take one of three paths. The paths are common between the physical line and STS-1 level. From the STS-1 level to the DS0, one of three paths can be taken.

The path that a particular DS1/DS0 will use can be configured by the user with the -payload parameter in the cnfpath -sts command. This parameter can be set to:

•3 = ds3 (not applicable to SDH interface)—The path is carrying a DS3 payload.

•4 = vt15vc11—The path is carrying a SONET-VT1.5/SDH-VC11 payload.

•5 = vt20vc12—The path is carrying a SONET-VT2/SDH-VC12 payload.

Note The vt1.5 path and the vt2.0 path also support SDH-VC11 and SDH-VC12 interfaces respectively.

Using the system described above, DS1 paths in VXSM commands are formatted as follows:

•SONET path payload type VT1.5 or VT2.0

The DS1 is specified as: bay.line.path.vtg.vt

bay = 1 (upper bay)
line = the line number on the associated OC-3 card in the range 1 to 4.
path = the path of the virtual tributary in the range 1 to 3.
vtg = the virtual tributary groups applicable to the connection in the range 1 to 7.
vt = virtual tributaries in the range 1 to 4 for vt1.5 or 1 to 3 for vt2.0.

Caution The combination of seven vtgs and four vts allows the specification of one of up to 28 DS1s. Be aware that VXSM supports two schemes for mapping a DS1 to a vtg/vt combination. These schemes are known as standard and Titan and are described in VTG/VT to DS1 Mapping.
vtg = the virtual tributary group.
vt = virtual tributary

•SONET path payload type is ds3.

The DS1 is specified as: bay.line.path.ds1

bay = upper of lower bay of the VXSM backcard.
line = the line number on the associated OC-3 card in the range 1 to 4.
path = the SONET (STS-1) path payload type as ds3 in the range 1 to 3.
ds1 = the ds1 channel within the ds3 interface in the range 1 to 28.

SDH Systems

The VXSM- 155 card supports voice circuits that are multiplexed according to the Synchronous Digital Hierarchy (SDH) standard. Each OC- 3 line presents the data stream as a 155.52 Mbps Synchronous Transport Module (STM-1).

Figure 3-2 shows the multiplexing paths between STM-1 at the physical line and the T1 or E1 voice circuits.

Figure 3-2 SDH Hierarchical Relationships

When using the SDH interface, the user must configure the path using the cnfpath -sts command. The format of this command is:

cnfpath -sts <bay.line.path> [-payload <Path Payload>] [-tm <Tributary Mapping Type>]
[-tg <Tributary Grouping>] [-txtrace <Transmit Trace>] [-extrace <Expect Trace>]
<bay.line.path>, specifies the bay (1 = upper), the physical line number on the back card, the path number between the STM and the AU (1, 2, or 3 for AU-3, 1 for AU-4)

-payload <Path Payload>, specifies the TU/VC combination (TU-11/VC-11 for T1 or TU-12/VC-12 for E1).

-tm<Tributary Mapping Type>, specifies the mapping mode, 1 = asynchronous mode or 2 = byteSynchronous mode.

-tg <Tributary Grouping>, specifies the tributary grouping This is a choice between AU-3 or AU-4 (the default).

2 = au3Grouping—Applicable to SDH interfaces: STM1, -AU-3, -TUG-2, -TU-12, -VC12 or STM1, -AU-3, -TUG-2, -TU-11, -VC11.
3 = au4Grouping—Applicable to SDH interfaces: STM1, -AU-4, -TUG-3, -TUG-2, -TU-12, -VC12 or STM1, -AU-4, -TUG-3, -TUG-2, -TU-11, -VC11.

T1/E1 Systems

In T1/E1 systems, the front card supports up to 48 T1 or E1 lines. The back card supports up to 24 T1 or E1 lines. Depending upon the number of lines to be supported, one or two half high back cards are configured using 1 front card; one in the upper or lower bay and the other (if configured) in the remaining open bay.

A physical line or a DS1 service is specified simply as:
bay.line

where:
bay = 1 or 2—1 for the upper bay, 2 for the lower bay.

line = 1 - 24, The physical T1 line on the back card in the range 1 to 24.

If the command requires the interface to be further specified down to the DS0 level, the DS0 is specified as:
bay.line ds0grp

where:

ds0grp = 0 - 23 or 30 — The DS0 group in the range of 0 to 23 for T1 or 0 to 30 for E1.

T3/E3 Systems

In T3/E3 systems, the front card supports up to 6 T3 or E3 lines. The back card supports up to 3 T3 or E3 lines. Depending upon the number of lines to be supported, one or two half height back cards are configured with a single front card; one in the upper or lower bay and other (if configured) in the remaining open bay.

A DS1 is specified simply as:
bay.line.path

where:
bay = 1 or 2—1 for the upper bay, 2 for the lower bay.

line = 1 - 3—The physical T3 line on the back card in the range 1 to 3

path = 1 - 28—The DS1 circuit in the T3 line in the range of 1 to 28

If the command requires the interface to be specified down to the DS0 level, the DS0 is specified as:
bay.line.path ds0grp

where:

ds0grp = 0 - 23 or 30 — The DS0 group in the range of 0 to 23 for T1 or 0 to 30 for E1.

Note The VXSM T3/E3 card set is designed to support both T3 and E3 applications. However, in Release 5.2 only T3 services are supported.

Voice Interfaces

A voice interface (VIF) is a user configurable set of parameters that is applied to a group of DS0s within a DS1. The configuration settings of the VIF are used by the digital signal processors (DSPs) to determine how a voice payload is to be processed by VXSM. This is particularly true when the VXSM is operating in VoIP Switching mode.

A voice interface is created using the addvif command. With this command the user specifies a VIF number (DS0 group number) and its associated DS1, in addition, the type of signaling, the type of service (H.248 switching, trunking). Other bearer channel parameters such as echo cancellation and voice activity detection, are also specified, using cnfvifec, cnfvifvad, and other commands as listed below. These parameters are contained within a vif which, when the VIF is added, are assigned default values.

Once a VIF is created, its parameters can be discovered using the dspvif command. There are also display and configure commands for the user to see and configure the various parameters

To create and configure a VIF perform the following steps.

Step 1 Use the dspvifs command to check that the VIF exists. If it does not, use the addvif command to create the VIF.

Step 2 For a particular DS1, use one of the display VIF commands to display its associated VIF parameter values. Determine which parameter (if any) need to be modified.

dspvif [<bay.line.path.vtg.vt >] | [<bay.line.path.ds1>] <ds0GroupId> for OC-3

dspvif <bay.line> <ds0GroupId> for 48 T1/E1

dspvif <bay.line.ds1> <Ds0GrpIndex> for T3

dspvifvad <bay.line.path.vtg.vt > | <bay.line.path.ds1> <ds0GroupId> for OC-3

dspvifterms

dspvifterm [< bay.line.path.vtg.vt >] | [<bay.line.path.ds1>] <ds0GroupId> for OC-3

dspvifterm <bay.line> <ds0GroupId> for 48 T1/E1

dspvifterm <bay.line.ds1> <Ds0GrpCfgIndex> for T3

dspvifparam <bay.line> <ds0GroupId> for 48 T1/E1

dspvifparams

dspvifparam <bay.line.ds1> <Ds0GrpCfgIndex> for T3

dspviftoneplan <bay.line> <ds0GroupId> for 48 T1/E1

dspviftoneplan<bay.line> <ds0GroupId> for 48 T1/E1

dspviftoneplan <bay.line.ds1> <Ds0GrpCfgIndex> for T3

dspviftoneplans

dspvifgainattn <bay.line.path.vtg.vt> | <bay.line.path.ds1> <ds0GroupId> for OC-3

dspvifgainattns for OC-3

dspviftd <bay.line.path.vtg.vt> | <bay.line.path.ds1> <ds0GroupId> for OC-3

dspviftds for OC-3

Step 3 Use any of the following configure vif commands to modify VIF parameters.

H.248 Commands

cnfvifec<bay.line.path.vtg.vt > | <bay.line.path.ds1> <ds0GroupId> <EchoCancelEnable>
<EchoCancelCoverage> <Repetition>

cnfvifeventmapping <bay.line.path.vtg.vt> | <bay.line.path.ds1> <ds0GroupId> <EventMappingIndex>

cnfvifgainattn<bay.line.path.vtg.vt> | <bay.line.path.ds1> <ds0GroupId><InputGain><outputAttn><repetition>

cnfviftd <bay.line.path.vtg.vt> | <bay.line.path.ds1> <ds0GroupId><InitDigitTimeout><InterDigitTimeout><repetition>c

cnfvifparam <specified ds1> <ds0GroupId> <NoiseRegEnable> <NonLinearProcEnable> <MusicOnHoldThreshold> <ModemPassThru> <UpspeedCodec> <Repetition>

cnfvifterm <specified ds1> <ds0GroupId> <gatewayLinkId> <packageIds> <profileId>

cnfviftoneplan <specified ds1> < ds0GroupId> <tonePlanId>

cnfvifvad<bay.line.path.vtg.vt > | <bay.line.path.ds1> <ccasGrpCfgIndex> <VAD> <VadTimer>
<Repetition>

TGCP Commands

cnfvifec <bay.line.path.vtg.vt > | <bay.line.path.ds1> <ds0GroupId> <EchoCancelEnable>
<EchoCancelCoverage> <Repetition>

cnfvifeventmapping <bay.line.path.vtg.vt> | <bay.line.path.ds1> <ds0GroupId> <EventMappingIndex>

cnfvifgainattn<bay.line.path.vtg.vt> | <bay.line.path.ds1> <ds0GroupId><InputGain> <outputAttn><repetition>

cnfvifparam<specified ds1> <ds0GroupId> <NoiseRegEnable> <NonLinearProcEnable> <MusicOnHoldThreshold> <Repetition>

cnfviftd <bay.line.path.vtg.vt> | <bay.line.path.ds1> <ds0GroupId><InitDigitTimeout><InterDigitTimeout><repetition>(Only applicable when service is xgcp)

cnfvifvad<bay.line.path.vtg.vt > | <bay.line.path.ds1> <ccasGrpCfgIndex> <VAD> <VadTimer>
<Repetition>

cnfvifxgcpprof<bay.line.path.vtg.vt > | <bay.line.path.ds1> <sd0GroupId> <XgcpProfileIndex>
<Repetition>

See the chapters entitled VXSM Commands for a description of the commands listed in steps 2 and 3.

Configuring TDM Lines

Use the following steps to configure the TDM lines on the VXSM.

Step 1 Use the upln command to bring up a VXSM line.
upln <bay.line>
For bay, enter 1 for upper bay or 2 for upper bay.

For line, enter a value in the range 1 - 4 for OC-3, 1 - 24 for 48T1/E1, 1 - 3 for T3.

Step 2 For OC-3 cards, use the uppath command to specify the STS-1 path within the OC-3
uppath -sts<bay.line.path>
For bay, enter 1 for upper bay or 2 for lower bay.

For line, enter a value between 1 and 4 to indicate the physical OC-3 interface on the back card.

For path, enter a value between 1 and 3 to indicate the DS3 path within the OC-3 interface.

Step 3 For OC-3 cards, use the -payload parameter in the cnfpath -sts command to specify the ds1 path with the OC-3. The choices are ds3, vt1.5, and vt2.0.
cnfpath -sts<bay.line.path>[-payload <PathPayload>][-tm <TributaryMappingType>][-tg 
<TributaryGroupingType>][-txtrace <PathTraceToTransmit>][-exptrace <PathTraceToExpect]
<bay.line.path>

bay: 1

line: 1 - 4

path: 1 - 3 or 1 (AU4 only)

[-payload <PathPayload>]

3 - ds3

4 - vt15vc11

5 - vt20vc12

[-tm <TributaryMappingType>]

1 - asynchronous

2 - byteSynchronous (NA for ds3)

[-tg <TributaryGroupingType>]

1 - not Applicable (Sonet)

2 - au3Grouping (SDH)

3 - au4Grouping (SDH)

[-txtrace <PathTraceToTransmit>]

trace-string: size 16(SDH) or 64(Sonet)

[-exptrace <PathTraceToExpect]

trace-string: size 16(SDH) or 64(Sonet)

Step 4 For OC-3 cards, use the uppath command to specify the DS1 path within the DS3
uppath -ds1<bay.line.path.vtg/ds3.vt/ds1>
For bay, enter 1 for upper bay or 2 for upper bay.

For line, enter a value between 1 and 4 to indicate the physical OC-3 interface on the back card.

For path, enter a value between 1 and 3 to indicate the DS3 path within the OC-3 interface.
Step 5 Use the appropriate addvif command to add a voice interface for a DS0 group within a DS1.

For OC-3 use, addvif <bay.line.path.vtg.vt> | <bay.line.path.ds1> <Ds0GrpIndex> <Ds0BitMap> <ServiceType> <Repetition>

For T1/E1 use, addvif <bay.line> <ds0GrpIndex> <ds0ChannelBitMap> <ServiceType> <Repetition>

For T3 use, addvif <bay.line.ds1> <ds0GrpIndex> <ds0ChannelBitMap> <ServiceType> <Repetition>

LineNum for OC-3—(bay.line.path.vtg.vt or bay.line.path.ds1)

bay {1 - upper}

line (range=1º4)

path (range=1º3)

vtg (range=1º7)

vt (range=1º4)(ds1) (range=1º3)(e1)

ds1 (range=1º28)

LineNum for T1/E1—(bay.line)

bay {1 - upper, 2 - lower}

line (range=1º24)

LineNum for T3—(bay.line.ds1)

bay {1 - upper, 2 - lower}

line (range=1º3)

ds1 (range=1º28)

Ds0GrpIndex—DS0 group index

T1: (range=0º23)

E1: (range=0º30)

Ds0BitMap—DS0 channel number

For trunking Service or DS0Xconn: single bit input

For H248: multiple bits input (1-24 or 1, 5, 10-20)

T1: 1,2,3,º24

E1: 1,2,3,º31

ServiceType—service type

For H.248 Protocol, 8 = Trunking, 9 = H248, 10 =DS0Xconn

For xGCP protocol, 8 = Trunking, 10 = DS0Xconn, 11 = xGCP

BulkProvisionNumber—bulk provisioning number

Single DS0 configuration (range=1º8064(O-C3)/1152(T1)/1488(E1))(default=1)

Multiple DS0 configuration (range=1º336(OC-3)/48(T1E1))(default=1)

Setting Up VXSM Connections

Creating a VXSM Resource Partition

Step 1 Use the addrscprtn command to create a resource partition for the VXSM card.
geteway1.5.VXSM.a > addrscprtn <ifNum> <partId> <ctrlrId> <egrminbw> <egrmaxbw> <ingminbw> 
<ingmaxbw> <minVpi> <maxVpi> <minVci> <maxVci> <minConns> <maxConns> 
For ifNum, enter 1 for port number. For partId, enter 1 for PNNI. For cntrlid, enter 2 for PNNI.

The remaining parameters are used to specify maximum and minimum values for vpi/vci, bandwidth, connections, etc., see the Cisco VXSM Command Reference, Release 5.3 for details.

Creating Slave End Connection on RPM or AXSM Card

Step 2 For RPM Configurations Only
For each connection, specify the slave end on the RPM-XF card and the master end on the VXSM card.

a. On the RPM-XF card, enter the interface command
Router(config)#interface Switch1
b. On the RPM-XF card, enter the switch connection command to define the slave connection endpoint.
Router(config-subif)# switch connection vcc <localVPI> <localVCI> master remote raddr 
<ATMaddr> <remoteVPI> <remoteVCI> 
Omit the <ATMaddr> <remoteVPI> <remoteVCI> parameters

The following example creates a master connection for the PVC labeled VPI 0, VCI 2001:
Router(config-subif)#switch connection vcc 0 2001 master remote 
c. After you create the slave connection endpoint, the RPM-XF enters the switch connection configuration mode and displays the following prompt:
Router(config-if-swconn)# 
On the RPM-XF card configure the switch connection using the switch connection configuration commands.
Router(config-if-swconn)rmbs 1024
Router(config-if-swconn)rpcr 860000
Router(config-if-swconn)rscr 860000
Router(config-if-swconn)cpmm-id 9
Router(config-if-swconn)pcr 860000
Router(config-if-swconn)csr 860000
Note This is the only time that you can configure the switch connection. If you need to change the configuration later, delete the subinterface and recreate the connection.

d. To display the ATM address assigned to the slave connection, switch to the active PXM45 card and enter the dspcon command to display connection information. For example, if the RPM-XF is in slot 9
Router#cc 7
(session redirected)
dspcon 9.1.2.2 0 2000
Port                   Vpi Vci                         Owner      State 
-------------------------------------------------------------------------
Local  9:-1.1:-1       0.2000                          SLAVE      FAIL 
       Address: 47.00918100000000036b5e2bb2.000001074b01.00
Remote Routed          0.0                             MASTER      --       
       Address: 00.000000000000000000000000.000000000000.00
-------------------- Provisioning Parameters -------------------- 
Connection Type: VCC          Cast Type: Point-to-Point      
Service Category: UBR         Conformance: UBR.1     
Bearer Class: BCOB-X    
Last Fail Cause: N/A                              Attempts: 0
Continuity Check: Disabled    Frame Discard: Disabled 
L-Utils: 0     R-Utils: 0     Max Cost: 0     Routing Cost: 0
OAM Segment Ep: Enabled 
---------- Traffic Parameters ----------
Tx PCR:  353208         Rx PCR:  353208    
Tx CDV:  N/A            Rx CDV:  N/A       
Tx CTD:  N/A            Rx CTD:  N/A       
The slave endpoint ATM address appears below the Local port identification. Note this value because this is the address you need to enter when you create a master connection endpoint at the VXSM card. The connection state is FAIL because the master endpoint has not been created.

e. Repeat Step 2 until all the bearer (up to 8) and the one control slave ends have been configured.

Step 3 For AXSM Configurations Only
Create PVC connections between VXSM and AXSM.
For each connection, the user needs to specify the slave end on the AXSM card and the master end on the VXSM.

Log on to the AXSM and use the addcon command to configure the slave end point for establishing a PVC between the VXSM and AXSM. Repeat this command for up to 8 bearer PVCs and 1 control PVC

a. addcon <ifNum> <vpi> <vci> <service type> <mastership>
[-casttype <value>] [-slave <NSAP.vpi.vci>] [-lpcr <local PCR>] [-rpcr <remote PCR>] 
[-lscr <local SCR>] [-rscr <remote SCR>] [-lmbs <local MBS>] [-rmbs <remote MBS>] 
[-cdvt <local CDVT>] [-lcdv <local maxCDV>] [-rcdv <remote maxCDV>] [-lctd <local 
maxCTD>] [-rctd <remote maxCTD>] [-cc <OAM
CC Cnfg>] [-stat <Stats Cnfg>] [-frame <frame discard>] 
[-mc <maximum cost>] [-lputil <local util>] [-rputil <remote util>] [-slavepersflag 
<slavepers>] [-rtngprio <routingPriority>] [-prefrte
<preferredRouteId>] [-directrte <directRoute>] 
For ifNum specify 1 as the interface number. For VPI and VCI, specify values in the ranges 0 to 255 and 0 to 65535 respectively. For service type, specify 1 (constant bit rate).

For pvc type, specify 1 (AAL5) for a control connection or a bearer connection.

For appication specify 1 for a control connection or 2 for a bearer connection.

For mastership specify 2 for False (slave).

Omit the -slave parameter. The gateway will assign a value and display it as NSAP.VPI.VCI. The user should note the value and use it when adding the master end of the connection on the VXSM.

Of the remaining optional parameters, enter values or accept the defaults. See the CLI chapter for details.

b. Repeat Step 3 until all the bearer (up to 8) and the one control slave ends have been configured.

Creating Master End Connections on VXSM Card

Step 4 Log on to the VXSM card

a. Use the addcon command to configure the master end point for establishing a PVC between the VXSM and RPM or AXSM.
addcon <ifNum> <vpi> <vci> <serviceType> <pvcType> <application> <mastership>  
[-slave <NSAP.vpi.vci>] [-lpcr <local PCR>] [-rpcr <remote PCR>] [-lscr <local SCR>]  
[-rscr <remote PCR>] [-lmbs <local MBS>]º
For ifNum specify 1 as the interface number. For VPI and VCI, specify values in the ranges 0 to 255 and 0 to 65535 respectively. For service type, specify 1 (constant bit rate).

For pvc type, specify 1 (AAL5) for a control connection or a bearer connection.

For appication specify 1 for a control connection or 2 for a bearer connection.

For mastership specify 1 for True (master).

For the -slave parameter, enter the NSAP.VPI.VCI that was noted when configuring the slave end of the connection.

Of the remaining optional parameters, enter values or accept the defaults. These parameters are best set from the master end. See the VXSM Command Reference for details.

b. Repeat step 4 for each bearer and control PVC configured in the previous step (step 2 or step 3).

Note PVC connections must be configured such that Connection Admission Control (CAC) mastership/slave follows that of the Connection Mastership/Slave.

Assigning IP Addresses

Step 5 For each connection (control and bearer), there must be an IP address assigned.

a. Use the addconip command to assign IP addresses to the VXSM connections.
addconip<IpIndex><PortNum><Vpi><Vci><IpAddr> 
<PrefixLength><defaultGwIp> 
For IpIndex assign a number in the range 1 to 16. Usually the user would assign 1 to the first IP address being assigned, 2 for the next and so on.

For PortNum, enter the value of 1.

For VPI and VCI, enter the values for the connection for which an IP address is being assigned.

For IPAddr, assign an IP address for the connection.

For PrefixLength, enter the length of the IP prefix.

For DefaultGwIp, specify whether this is to be the default gateway. Enter 1 for yes, or 2 for no.

b. Repeat step 5 for each bearer and control connection that was configured in step 4.

Configuring MGC Interfaces for Call Control

Perform one of the following procedures below to configure the interface between the Media Gateway (MG) and the Media Gateway Controller (MGC). VXSM supports the ITU H.248 and the xGCP protocols, select the procedure that applies to you application.

For each protocol type, the procedure consists of two basic phases. The first phase sets up MGCs and MGC Groups. The second phase configures the protocol and protocol profile details that are used for the VXSM and the MGC to communicate.

Note XGCP is a generic term for a family of similar MGC protocols. The protocols in the family are:

Simple Gateway Controller Protocol (SGCP)
Media Gateway Controller Protocol (MGCP)
Trunking Gateway Controller Protocol (TGCP).

Gateways Using H.248 MGC Protocol

Setting Up H.248 MGCs and MGC Groups

The following procedure establishes Media Gateway Controller and Media Gateway Controller Group identities, properties, and relationships. Because H.248 applications support up to 12 virtual media gateways (VGWs), this procedure supports the configuration of multiple MGC Groups associated with one physical VXSM board.

Step 1 Determine the number of VGWs, MGCs, and MGC Groups to be setup. Determine their relationships. The rules are:

•A VXSM card can have up to 12 VGWs (it must have at least one)

•There must one, and only one, associated MGC Group for each VGW

•Each MGC Group can up to 4 MGCs (it must have at least one)

Figure 3-3 shows a sample arrangement is which VXSM is partitioned into 4 virtual media gateways with 4 corresponding media gateway groups.

Figure 3-3 MGC, MGC Group, and VMG Arrangement—Example

Step 2 Provide a domain name for the MGC, and specify how it is to be resolved.

a. Use the addmgcdn command to add am MGC domain name.
addmgcdn <MGC Index> <Domain Name>
For MGC Index, enter an integer in the range 1 to 4 to identify the MGC within a group.

For Domain Name, enter and name up to 64 characters.

b. Use the cnfmgc command to specify the resolution method for the MGC domain name.