VOIP Switching

Table Of Contents

VoIP Switching Mode

Configuring the Operating Mode

Configuring the ATM Network Side

Configuring PVC Connections

Connection CAC Configuration

Configuring the Call Agent Interface

Configuring Domain Names and IP Addresses

Setting Up Call Agents and Protocols

Configuring Gateway Control Protocol Port

Configuring ISDN PRI Backhaul

Configuring TDM Side Signaling for Applications That Use CCS

Adding DS0 Endpoints to Lines

Configuring TDM Side Signaling for Applications That Use CAS

Placing Gateway Out and In Service

Sample Configuration

VoIP Switching Mode

This section contains the following tasks for configuring the VISM/VISM-PR card for VoIP switching:

• Configuring the Operating Mode

• Configuring the ATM Network Side

• Configuring the Call Agent Interface

• Configuring TDM Side Signaling for Applications That Use CCS

• Adding DS0 Endpoints to Lines

• Configuring TDM Side Signaling for Applications That Use CAS

• Placing Gateway Out and In Service

Sample VoIP switching configurations are shown in the "Sample Configuration" section.

Configuring the Operating Mode

To configure your VISM/VISM-PR card for the VoIP switching mode, complete the following steps:

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

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

Replace <mode_number> with value of 1.

•1 = VoIP switching/VoIP trunking (default)

•2 = AAL2 trunking

•3 = AAL1 switching

•7 = Switched AAL2 SVC

•8 = Switched AAL2 PVC

•9 = VoIP and AAL1 SVC

•10 = VoIP trunking and AAL2 trunking

Step 2 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 the VoIP switching mode:

INFORMATION: The new 'voipSwitching' mode has 355 CLI commands.

Step 3 To display the current VISM/VISM-PR operating mode, enter the dspvismparam command.

nodename.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: 10.31.19.99
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 TFTPDOMAIN
Aggregate Clipping enable
Aggregate Svc Bandwidth 0

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

Codec negotiation option 1
Profile negotiation option 1
VAD Duty Cycle 61
VAD Tolerance 100
VISM Initiated NW COT Off
VISM CO4 Timer 1000 msec
CALEA flag disable
SupportdModuleType: VISM-PR-8T1.
VismNSAP: 47009181000000000142265b99000001079bff00

Configuring the ATM Network Side

Configuring the ATM network side consists of setting up ATM permanent virtual connections (PVCs) across the network and providing the mechanism by which calls are routed over the correct PVC.

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

Use the following guidelines when you set up the ATM side in the VoIP switching mode.

•The master and slave connection base parameters, PCR, SCR, and MBS values must match.

If these values do not match, PXM1E and PXM45 cards display an error. PXM1 cards do not display an error.

•If the connections are through a physical loopback on a PXM line, make sure that the VPI and VCI values are the same on both ends of the loopback.

Complete the following tasks to configure the ATM side:

• Configuring PVC Connections

• Connection CAC Configuration

Configuring PVC Connections

The VoIP switching mode has the following two types of PVCs:

•Bearer PVCs—Support both bearer data and control data.

•Control PVCs—Support only control data.

VISM/VISM-PR can have two different connection configurations:

1. One bearer PVC

2. Separate bearer and control PVCs

Complete the following steps to configure PVC connections:

Note You must add the slave connection first before adding the master connection. Retain the remote connection ID to use when setting up the master connection.

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

nodename.1.28.VISM8.a > addcon <localVCI> <preference> <pvcType> <application> <PCR> <mastership> |<remoteConnId> <serviceType> <scr> <mbs> <priority> <prefrte> <direct>|

Replace the above arguments with the values listed in Table 7-1.

Table 7-1 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

Note If you have two PVCs for redundancy, one PVC is primary; one PVC is secondary.

pvcType

AAL type of connection.

•1 = AAL5 (For signaling and bearer trunking)

•2 = AAL2

•3 = AAL1

application

The connection's application.

•1 = Control—Use this option for the control channel if you have separate control and bearer PVCs.

•2 = Bearer—Use this option if you have one PVC for both bearer and control data going over this PVC. Or, use this option for the bearer PVC when you are using separate control and bearer PVCs.

•3 = Signaling

PCR

Peak cell rate (PCR) measured 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.

For PXM1 connections, specify this argument with the following format: nodename.slot.port.vpi.vci

For PXM1E/PXM45, specify this argument with the following format: Nsapaddr.Vpi.Vci

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

|serviceType|

(Optional) Service type is 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.

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

|mbs|

(Optional) Maximum burst size (MBS) is the 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.

|priority|

(Optional) Route priority. Priority number is assigned to the PVC during configuration of the connection.

Range is 1-15. Default is 8.

A value of 1 indicates highest priority, and a value of 15 indicates the lowest priority.

Note This parameter is applicable only to VISM-PR cards.

|prefrte|

(Optional) Unique identifier of the preferred route to which this connection is associated.

Range is 0-65535. Default is 0.

When the specified route identifier is 0, the connection is not associated with a preferred route. This parameter is not applicable to the slave end of an SPVC connection.

Note This parameter is applicable only to VISM-PR cards.

|direct|

(Optional) Parameter to specify whether or not the associated preferred route is the only permissible route for the connection to take.

•1 = Yes—The connection is not allowed to pick an alternate route. This option is not applicable when a preferred route is not specified.

•2 = No (default)—The connection is allowed to try another route if the preferred route is unavailable.

If the directed preferred route is unavailable, the connection fails.

Note This parameter is applicable only to VISM-PR cards.

Step 2 If you need to refine the configuration parameters of the connection added in Step 1, enter the cnfcon command.

nodename.1.28.VISM8.a > cnfcon <LCN> <PCR> <service_type> |<SCR_ingress> <MBS_ingress> <priority> <prefrte> <direct>|

Replace the above arguments with the values listed in Table 7-2.

Table 7-2 Parameters for cnfcon Command

Parameter

Description

LCN

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

PCR

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 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 one of the values 4-7.

|SCR_ingress|

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

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

|MBS_ingress|

(Optional) 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_ingress argument.

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

|priority|

(Optional) Route priority is the priority number assigned to the PVC during configuration of the connection.

Range is 1-15. Default is 8.

A value of 1 indicates highest priority, and a value of 15 indicates the lowest priority.

Note This parameter is applicable only to VISM-PR cards.

|prefrte|

(Optional) Unique identifier of the preferred route to which this connection is associated.

Range is 0-65535. Default is 0.

When the specified route identifier is 0, the connection is not associated with a preferred route. This parameter is not applicable to the slave end of an SPVC connection.

Note This parameter is applicable only to VISM-PR cards.

|direct|

(Optional) Parameter to specify whether or not the associated preferred route is the only permissible route for the connection to take.

•1 = Yes—The connection is not allowed to pick an alternate route. This option is not applicable when a preferred route is not specified.

•2 = No (Default)—The connection is allowed to try another alternate route if the preferred route is unavailable.

If the directed preferred route is unavailable, the connection is failed.

Note This parameter is applicable only to VISM-PR cards.

Step 3 To configure primary and secondary PVCs to provide protection in the event of a PVC failure, enter the cnfconprotect command.

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

Replace the above arguments with the values listed in Table 7-3.

Table 7-3 Parameters for cnfconprotect Command

Parameter

Description

LCN

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

protection

Value you can use 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 4 To display the details of the connection, enter the dspcon command.

nodename.1.11.VISM8.a > dspcon <LCN>

Replace the <LCN> argument with a value in the range 131-510.

The following example shows sample configuration for a bearer PVC in VoIP switching mode.

mgxa-pxm1e.1.30.VISM8.a > dspcon 132

ChanNum: 132
ChanRowStatus: Mod
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 us
ChanPortNum: 255
ChanPvcType: AAL5
ChanConnectionType: PVC
ChanLocalVpi: 30
ChanLocalVci: 132
ChanLocalNSAP: 470091810000000007856e136300000107f3ff00
ChanRemoteVpi: 104
ChanRemoteVci: 131
ChanRemoteNSAP: 470091810000000007856e1363000001073b0400
ChanMastership: Master
ChanVpcFlag: Vcc
ChanConnServiceType: CBR
ChanRoutingPriority: 8
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction

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

ChanConnPCR: 58000
ChanConnPercentUtil: 100
ChanPreference: 1
ChanRemotePCR: 58000
ChanRemotePercentUtil: 100
ChanProtection: unprotected
ChanActivityState: unknown
ChanLockingState: unlock
ChanApplication: bearer
ChanServiceType: cbr
ChanScrIngress: 58000
ChanMbsIngress: 58000
ChanVCCI: 0
ChanFarEndAddrType: notapplicable
ChanFarEndE164Addr: 0
ChanFarEndGWIDAddr: .
ChanFarEndNSAPAddr: NULL NSAP
ChanAdminStatus: Up
ChanReroute: False
ChanPrefRouteId: 0
ChanDirectRoute: False

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

ChanUserPcrNumber: User BW Off
ChanUserMinPCRBW: 10
ChanUserMaxPCRBW: 58000
ChanUserMaxScrBW: 0
ChanUserMaxMbsBW: 0

ChanNumNextAvailable: 133

The following example shows sample configuration for a control PVC in VoIP switching mode.

nodename.1.30.VISM8.a > dspcon 131

ChanNum: 131
ChanRowStatus: Mod
ChanLocalRemoteLpbkState: Disabled
ChanTestType: TestOff
ChanTestState: NotInProgress
ChanRTDresult: 65535 us
ChanPortNum: 255
ChanPvcType: AAL5
ChanConnectionType: PVC
ChanLocalVpi: 30
ChanLocalVci: 131
ChanLocalNSAP: 470091810000000007856e136300000107f3ff00
ChanRemoteVpi: 104
ChanRemoteVci: 130
ChanRemoteNSAP: 470091810000000007856e1363000001073b0400
ChanMastership: Master
ChanVpcFlag: Vcc
ChanConnServiceType: CBR
ChanRoutingPriority: 8
ChanMaxCost: 2147483647
ChanRestrictTrunkType: No Restriction

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

ChanConnPCR: 1000
ChanConnPercentUtil: 100
ChanPreference: 1
ChanRemotePCR: 1000
ChanRemotePercentUtil: 100
ChanProtection: unprotected
ChanActivityState: unknown
ChanLockingState: unlock
ChanApplication: control
ChanServiceType: cbr
ChanScrIngress: 1000
ChanMbsIngress: 1000
ChanVCCI: 0
ChanFarEndAddrType: notapplicable
ChanFarEndE164Addr: 0
ChanFarEndGWIDAddr: .
ChanFarEndNSAPAddr: NULL NSAP
ChanAdminStatus: Up
ChanReroute: False
ChanPrefRouteId: 0
ChanDirectRoute: False
Type <CR> to continue, Q<CR> to stop:

ChanUserPcrNumber: User BW Off
ChanUserMinPCRBW: 10
ChanUserMaxPCRBW: 0
ChanUserMaxScrBW: 0
ChanUserMaxMbsBW: 0

ChanNumNextAvailable: 133

Step 5 To verify the integrity or continuity of a connection, enter the tstcon command.

nodename.1.11.VISM8.a > tstcon

The following example shows a connection test for LCN 131.

nodename.1.11.VISM8.a > tstcon 131
test type is..... 1

TestCon in progress.

TestCon Passed.

Connection CAC Configuration

Note CAC must be enabled on the card.

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

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

Replace the above arguments with the values listed in Table 7-4 for the cnfconcacparams command.

Table 7-4 Parameters for cnfconcacparams Command

Parameter

Description

LCN

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

VADTolerance

VAD tolerance—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 10. Some examples are:

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

•100 = 0.01%

•10 = 0.001%

•1 = 0.0001%

Range is 0-10000. Default is 100.

VADDutyCycle

VAD duty cycle—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, 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.

Configuring the Call Agent Interface

Note The CLI call agent configuration commands are used for the VoIP switching mode only for xGCP protocols.

VISM/VISM-PR can use one to eight call agents to accomplish the following actions:

•Receive backhauled signaling

•Perform call setup

•Perform call teardown

VISM/VISM-PR uses IP connectivity to communicate with the call agents (see Figure 7-1).

Figure 7-1 VISM to Call Agent Communication

Physical connectivity is through a PVC on an MGX 8000 Series platform PXM port, to a router (in the IP Connectivity cloud in Figure 7-1) or directly through an RPM card, and then to the call agents.

Logical IP connectivity is achieved 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 7-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 Protocol Port

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.

nodename.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. The default name is cisco.com, as shown in the following example:

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

nodename.1.28.VISM8.a > cnfvismip <vismIpAddr> <netMask> |<vismBearerIpAddr> <bearerNetMask>|

Replace the above arguments with the values listed in Table 7-5.

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

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

Setting Up Call Agents and Protocols

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

Step 1 To configure the domain name server for the external domain name resolution, enter the cnfdnssrvr command.

nodename.1.28.VISM8.a > cnfdnssrvr <extDnsSrvrDn>

Replace the <extDnsSrvrDn> argument with 1-64 characters.

To remove a DNS server name, set the <extDnsSrvrDn> argument to NULL.

Step 2 To add a domain name for a call agent, enter the adddn command.

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

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

Table 7-6 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. Use 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. Statically 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 statically provisioned IP addresses for this domain name before using IP addresses obtained through 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 statically provisioned IP addresses.

Step 3 If you are not using Resolution_Type = 2 to resolve domain names (in Step 2), proceed to Step 4.

If you are using Resolution_Type = 2 to resolve domain names, proceed to Step 5.

Step 4 To add the IP address for the domain name you added in Step 2, enter the adddnip command.

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

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

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

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

preference

An 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 5 To add the call agent/media gateway controller (MGC) domain name, enter the addmgc command.

nodename.1.28.VISM8.a > addmgc <mgcNumber> <DomainName>
Replace the <mgcNumber> argument with a value in the range 1-8.

Replace the <DomainName> argument with a character string up to 64 characters.

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

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

Replace the above arguments with the values listed in Table 7-8.

Table 7-8 Parameters for addmgcgrpentry Command

Parameter

Description

Red_Group_Num

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

mgcRedGrpMgcNum

Call agent redundancy group 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 7 To change the parameters of the MGC group, enter the cnfmgcgrpparam command.

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

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

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

Table 7-9 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 8 To associate a call agent redundancy group with a gateway control protocol, enter the addmgcgrpprotocol command.

nodename.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 7-10.

Table 7-10 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 you can use 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 you can use 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 you can use to enable or disable the disconnect method. If this value is 1, 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 you can use to cancel 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 9 Repeat Step 1 through Step 8 for each call agent that you need to make active in your application.

Configuring Gateway Control Protocol Port

Complete the following steps to configure a gateway control protocol port.

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 from the default argument values.

Step 1 To configure a port number for a particular call agent and protocol, enter the cnfxgcppeer command.

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

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

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

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

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

Replace the above arguments with the values listed in Table 7-12.

Table 7-12 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) that 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.

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

Replace the above arguments with the values listed in Table 7-13.

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

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

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

nodename.1.28.VISM8.a > cnfsrcppeergrpparam <Red_Group_Num> <Heart_beat_interval> <max_pdu>

Replace the above arguments with the values listed in Table 7-14.

Table 7-14 Parameters for cnfsrcppeergrpparam Command

Parameter

Description

Red_Group_Num

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

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

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

Replace the above arguments with the values listed in Table 7-15.

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

Configuring ISDN PRI Backhaul

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

ISDN PRI backhaul configuration consists of setting up three types of 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. For more information on session structures, see Chapter 2, "VISM/VISM-PR Functional Description."

Complete the following steps to configure ISDN PRI backhaul:

Step 1 To create a session set, enter the addsesset command.

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

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

Replace the above arguments with the values listed in Table 7-16.

Table 7-16 Parameters for addsesgrp Command

Parameter

Description

group_number

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 of 1 to 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.

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

Replace the above arguments with the values listed in Table 7-17.

Table 7-17 Parameters for addses Command

Parameter

Description

session_number

Session number in the range 1-64.

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

group_number

The number of a session group to which the session is added. The range is 1-16.

Note Currently, only group 1 is supported.

priority

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

local_port

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

remote_port

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

Configuring TDM Side Signaling for Applications That Use CCS

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

Common channel signaling (CCS) 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.

Complete the following steps to add and configure CCS:

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

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

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

Replace the above arguments with the values listed in Table 7-18.

Table 7-18 Parameters for addlapd Command

Parameter

Description

line_number

Line number. Range is 1-8.

ds0_number

DS0 number.

•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 2 To specify the LAPD stack type, enter the cnflapdtype command.

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

Replace the above arguments with the values listed in Table 7-19.

Table 7-19 Parameters for cnflapdtype Command

Parameter

Description

line_number

Line number. Range is 1-8.

ds0_number

DS0 number.

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

Adding DS0 Endpoints to Lines

The number of DS0s you can add depends on the template that you are using.

Complete the following steps to add DS0 endpoints to lines:

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

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

Replace the above arguments with the values listed in Table 7-20.

Table 7-20 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

Starting physical line number in the range 1-8.

ds0_num

Starting DS0 number from which the endpoints are added.

•1-24 for T1 lines

•1-31 for non-CAS E1 lines

•1-15 and 17-31 for CAS E1 lines

For VISM E1 cards, 16 is pre-allocated as the CAS channel.

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

endpts_num

Number of endpoints to add.

•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 2 To add a single DS0 to a line, enter the addendpt command.

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

Replace the above arguments with the values listed in Table 7-20.

Step 3 To validate the endpoints that you added, enter the dspendpts command.

nodename.1.28.VISM8.a > dspendpts

EndptNum Ena/Speed
-------- --- -----
1 act/ 64k
2 act/ 64k
3 act/ 64k
4 act/ 64k
5 act/ 64k
6 act/ 64k
7 act/ 64k
8 act/ 64k
9 act/ 64k
10 act/ 64k
11 act/ 64k
12 act/ 64k
13 act/ 64k
14 act/ 64k
15 act/ 64k
16 act/ 64k
17 act/ 64k
18 act/ 64k
19 act/ 64k
20 act/ 64k

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

Configuring TDM Side Signaling for Applications That Use CAS

Complete the following steps to add and configure CAS:

Note CAS is not supported on VISM/VISM-PR E1 lines in VoIP switching.

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

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

Replace the above arguments with the values listed in Table 7-21.

Table 7-21 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 = endpoints connected to an end office

•fgd_ea_outgoing.o = endpoints connected to an access carrier

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

•loop_start.o = loop start

•delay_did_dod.o = dial delay, dual tone multifrequency (DTMF)

•delay_did_dod_mf.o = dial delay, multifrequency (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 a TFTP domain is configured, the location is the TFTP server. If the file location is not found on 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 2 To configure a CAS variant and CAS timing parameters for the variant added in Step 1, enter the cnfcasvar command.

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

Replace the above arguments with the values listed in Table 7-22.

Table 7-22 Parameters for cnfcasvar Command

Parameter

Description

variant_name

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

country_code

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

Tring

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

Tpart

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

Tcrit

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

TMF

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

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

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

Replace the above arguments with the values listed in Table 7-23.

Table 7-23 Parameters for cnfcasendpt Command

Parameter

Description

endpt_number

Type the value used in Step 1.

casVariantName

Type the value used in Step 1.

Placing Gateway Out and In Service

To establish communication with the call agent, take the gateway out of service and then establish service.

Step 1 To place the card out of service, enter the cnfgwoos command.

nodename.1.28.VISM8.a > cnfgwoos <shutdown_method>

Replace the <shutdown_method> argument with one of the following values:

•2 = Forceful. Existing connections are deleted and the VISM/VISM-PR card transitions to the "commandedOutOfService" state. New connection requests are rejected.

•3 = Graceful. Existing connections are not released and allowed to terminate naturally. Immediately after this command is executed, the VISM/VISM-PR card transitions to the "pendingOutOfService state". New connection requests are rejected. The VISM/VISM-PR card transitions to the `commandedOutOfService' state only when all ongoing connections are deleted by the call agent.

The VISM card prompt terminates with an s, indicating the out-of-service (standby) state.

nodename.1.28.VISM8.s >

Step 2 To place card in service, enter the cnfgwis command.

nodename.1.28.VISM8.s > cnfgwis

The VISM card prompt terminates with an a, indicating the in-service state.

nodename.1.28.VISM8.a >

Sample Configuration

The following steps shows examples of initial card configuration for VoIP switching in template 1 with CCS.

1. Set the VISM/VISM-PR mode to VoIP switching and codec template to 1.

cnfvismmode 1
cnfcodectmpl 1

Note When you make changes to the codec template, the VISM/VISM-PR card resets.

2. Add a resource partition to communicate to the PXM card.

addport
addrscprtn 2

3. Set the domain name and IP address for the VISM/VISM-PR card.

cnfvismdn mgxb-v30.cisco.com
cnfvismip 10.20.30.99 255.255.255.0 10.20.31.99 255.255.255.0

4. Add the line interfaces 1-8.

addln 1
addln 2
addln 3
addln 4
addln 5
addln 6
addln 7
addln 8

5. Set the line signaling to CCS on each line.

cnflnsig 1 2
cnflnsig 2 2
cnflnsig 3 2
cnflnsig 4 2
cnflnsig 5 2
cnflnsig 6 2
cnflnsig 7 2
cnflnsig 8 2

6. Set the domain name and IP address for the call agent.

adddn 1 mga-SOLSYS1CA.sol.cisco.com
adddnip "1 mga-SOLSYS1CA.sol.cisco.com 10.1.3.25 1"
adddnip "2 mga-SOLSYS1CA.sol.cisco.com 10.1.5.25 2"

7. Set the media gateway controller (call agent) for the VISM/VISM-PR.

addmgc "1 mga-SOLSYS1CA.sol.cisco.com"

8. Set the MGC Protocol to the media gateway controller, and designate the port number to communicate to the call agent.

addmgcgrpentry 1 1 1
addmgcgrpprotocol 1 5
cnfxgcppeer 1 5 2427

9. Add the session set, session group, and sessions to the call agent for PRI backhaul.

addsesset 1 1
addsesgrp 1 1 mga-SOLSYS1CA.sol.cisco.com
addses 1 1 1 9011 9011
addses 2 1 2 9012 9012

10. Set the LAPD to the 24^th DS0 on each line.

addlapd 1 24
addlapd 2 24
addlapd 3 24
addlapd 4 24
addlapd 5 24
addlapd 6 24
addlapd 7 24
addlapd 8 24

11. Add the endpoints for a T1 in CCS. The value of 184 is derived from total of 192 available DS0s minus the CCS channels (1 per line).

addendpts 1 1 1 184

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 Note If you have two PVCs for redundancy, one PVC is primary; one PVC is secondary.
pvcType	AAL type of connection. •1 = AAL5 (For signaling and bearer trunking) •2 = AAL2 •3 = AAL1
application	The connection's application. •1 = Control—Use this option for the control channel if you have separate control and bearer PVCs. •2 = Bearer—Use this option if you have one PVC for both bearer and control data going over this PVC. Or, use this option for the bearer PVC when you are using separate control and bearer PVCs. •3 = Signaling
PCR	Peak cell rate (PCR) measured 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. For PXM1 connections, specify this argument with the following format: nodename.slot.port.vpi.vci For PXM1E/PXM45, specify this argument with the following format: Nsapaddr.Vpi.Vci Note This argument is used only when the mastership argument is set to 1 (Master).
\|serviceType\|	(Optional) Service type is 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. Note This argument value is required if the serviceType argument value is in the range 2-7.
\|mbs\|	(Optional) Maximum burst size (MBS) is the 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.
\|priority\|	(Optional) Route priority. Priority number is assigned to the PVC during configuration of the connection. Range is 1-15. Default is 8. A value of 1 indicates highest priority, and a value of 15 indicates the lowest priority. Note This parameter is applicable only to VISM-PR cards.
\|prefrte\|	(Optional) Unique identifier of the preferred route to which this connection is associated. Range is 0-65535. Default is 0. When the specified route identifier is 0, the connection is not associated with a preferred route. This parameter is not applicable to the slave end of an SPVC connection. Note This parameter is applicable only to VISM-PR cards.
\|direct\|	(Optional) Parameter to specify whether or not the associated preferred route is the only permissible route for the connection to take. •1 = Yes—The connection is not allowed to pick an alternate route. This option is not applicable when a preferred route is not specified. •2 = No (default)—The connection is allowed to try another route if the preferred route is unavailable. If the directed preferred route is unavailable, the connection fails. Note This parameter is applicable only to VISM-PR cards.

Parameter	Description
LCN	Type the value you entered for the localVCI argument in Step 1.
PCR	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 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 one of the values 4-7.
\|SCR_ingress\|	(Optional) SCR. Range is from 15 to the value you configured for the PCR argument. Note This argument value is required if the service_type argument value is in the range 2-7.
\|MBS_ingress\|	(Optional) 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_ingress argument. Note This argument value is required if the service_type argument value is in the range 2-7.
\|priority\|	(Optional) Route priority is the priority number assigned to the PVC during configuration of the connection. Range is 1-15. Default is 8. A value of 1 indicates highest priority, and a value of 15 indicates the lowest priority. Note This parameter is applicable only to VISM-PR cards.
\|prefrte\|	(Optional) Unique identifier of the preferred route to which this connection is associated. Range is 0-65535. Default is 0. When the specified route identifier is 0, the connection is not associated with a preferred route. This parameter is not applicable to the slave end of an SPVC connection. Note This parameter is applicable only to VISM-PR cards.
\|direct\|	(Optional) Parameter to specify whether or not the associated preferred route is the only permissible route for the connection to take. •1 = Yes—The connection is not allowed to pick an alternate route. This option is not applicable when a preferred route is not specified. •2 = No (Default)—The connection is allowed to try another alternate route if the preferred route is unavailable. If the directed preferred route is unavailable, the connection is failed. Note This parameter is applicable only to VISM-PR cards.

Parameter	Description
LCN	Primary logical channel number of the connection (PVC). Range is 131-510.
protection	Value you can use 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.

Parameter	Description
LCN	Logical channel number (LCN) of the connection. Range is 131-510.
VADTolerance	VAD tolerance—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 10. Some examples are: •10000 (tolerance) = 1% (over subscription drop ratio) •100 = 0.01% •10 = 0.001% •1 = 0.0001% Range is 0-10000. Default is 100.
VADDutyCycle	VAD duty cycle—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, 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.

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

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. Use 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. Statically 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 statically provisioned IP addresses for this domain name before using IP addresses obtained through 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 statically provisioned IP addresses.

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	An IP address that corresponds to the domain_name argument value in the following format: nnn.nnn.nnn.nnn.
preference	An 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.

Parameter	Description
Red_Group_Num	Call agent redundancy group number. Range is 1-8.
mgcRedGrpMgcNum	Call agent redundancy group 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.

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.

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 you can use 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 you can use 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 you can use to enable or disable the disconnect method. If this value is 1, 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 you can use to cancel 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)

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.

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) that VISM waits for an acknowledgment message from the call agent. Range is 0-100000 ms.

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

Parameter	Description
Red_Group_Num	Call agent redundancy group number. Range is 1-8.
Heart_beat_interval	Interval between heartbeats (defined in milliseconds). Values are •0 •Range 100-65535
max_pdu	Maximum allowable UDP size. Range is 4095-65535.

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.

Parameter	Description
group_number	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 of 1 to 64 alphanumeric characters.

Parameter	Description
session_number	Session number in the range 1-64. Note Up to 64 sessions can be created in a session group.
group_number	The number of a session group to which the session is added. The range is 1-16. Note Currently, only group 1 is supported.
priority	The priority level determines which session becomes active if a session fails within the same group. Range is 1 (highest) to 4 (lowest).
local_port	The local port number is the VISM port number used for the session. Range is 1124-49151.
remote_port	The remote port number is the call agent port number used for the session. Range is 1124-65535.

Parameter	Description
line_number	Line number. Range is 1-8.
ds0_number	DS0 number. •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)

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	Starting physical line number in the range 1-8.
ds0_num	Starting DS0 number from which the endpoints are added. •1-24 for T1 lines •1-31 for non-CAS E1 lines •1-15 and 17-31 for CAS E1 lines For VISM E1 cards, 16 is pre-allocated as the CAS channel. Note If the application requires CAS, issue the cnflnsig command before adding the endpoints.
endpts_num	Number of endpoints to add. •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

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 = endpoints connected to an end office •fgd_ea_outgoing.o = endpoints connected to an access carrier •fgd_os_e911.o = endpoints connected to FDG OSS (Feature group D operator services system) •loop_start.o = loop start •delay_did_dod.o = dial delay, dual tone multifrequency (DTMF) •delay_did_dod_mf.o = dial delay, multifrequency (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 a TFTP domain is configured, the location is the TFTP server. If the file location is not found on 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.

Parameter	Description
variant_name	Name of the CAS variant. Type the value used in Step 1.
country_code	Country code of the variant. The value must be a 2-character text string.
Tring	Ringing time (defined in seconds). Range is 10-600 sec.
Tpart	Partial dial time (defined in seconds). Range is 10-10000 sec—in increments of 10 sec.
Tcrit	Critical timing (defined in seconds). Range is 0-10000 sec—in increments of 10 sec.
TMF	Interdigit timeout value for MF digits (defined in seconds). Range is 1-10 sec.

Parameter	Description
endpt_number	Type the value used in Step 1.
casVariantName	Type the value used in Step 1.