|
|
Table Of Contents
Configuring VISM/VISM-PR Features
Using the Command Line Interface
VISM/VISM-PR Command Attributes
Connecting to Cisco MGX 8000 Series Platforms
Logging In to PXM and VISM/VISM-PR Cards
Logging Out of VISM/VISM-PR and PXM Cards
Initial Configuration of the VISM/VISM-PR Card
Configuring the ATM Network Side
Configuring the Call Agent Interface
Adjustable Music On-Hold Threshold
Configure PVC OAM Cell Parameters
PXM1E and PXM45 Card-Only Features
Call Agent-Controlled VoATM AAL1 and AAL2 SVC
AAL1 SVC-Based TDM Hairpinning
High Complexity Codec Support for VISM-PR—G.723.1
Call Agent-Controlled T.38 Fax
Additional Support for MGCP 1.0
CAS Immediate Start and Ground Start Glare Handling
MGX 8000 Series Implementation Features
Configuring VISM/VISM-PR Features
The command line interface (CLI) is a DOS-like interface used to configure VISM/VISM-PR cards. This chapter describes the following sections:
•
"Using the Command Line Interface" section
•
•
Using the Command Line Interface
CLI commands may be followed by a string of required or optional argument identifiers and argument values.
The entire string, from the command to the last argument value, is referred to as a command line. Spaces are used to separate all elements in a command line. Type the command, any necessary argument identifiers and argument values, then press Enter.
Note
For example, the Add Endpoint command, addendpt, adds an endpoint to VISM/VISM-PR and has three required arguments. An endpoint defines one end of a connection. The addendpt command format is as follows:
addendpt <endpt_num> <ds1_num> <ds0_num>
When you type a command, use argument values to represent the arguments. For example, to add an endpoint with number 10 on DS1 number 4 and DS0 number 3, the command line is as follows:
addendpt 10 4 3
Some commands require you to type an argument identifier before the argument value. For example, the Clear Alarm command, clralm, requires you to enter an identifier, -ds1, before the argument value. The clralm command format is as follows:
clralm -ds1 <LineNum>
To clear alarms on line 4, the command line is as follows:
clralm -ds1 4
VISM/VISM-PR Command Attributes
Use the information in Table 6-1 to determine the log file attributes, VISM/VISM-PR card state requirements for command use, and personnel privileges for all VISM/VISM-PR commands.
Table 6-1 VISM/VISM-PR Command Attributes—Log File, Card State, and Privilege Level
?1
No
All
All
add
Yes
Active
1
cc 1
Yes
All
All
chkflash 1
Yes
Active
1
clr
No
Active
1 to 5
cnf
Yes
Active
1
del
Yes
Active
1
dsp
No
Active
All
Help 1
No
All
All
pinglndsp 1
No
Active
All
tst
No
Active
All
version 1
No
Active
All
1 The text shown represents the complete CLI command name.
Note
Connecting to Cisco MGX 8000 Series Platforms
This section contains the following topics:
•
•
•
Overview
The VISM card operates in the following MGX 8000 Series platforms:
•
•
•
The VISM-PR card operates in the following MGX 8000 Series platforms:
•
•
•
•
•
Each platform contains a Processor Module (PXM) back card. Connect your CLI command administration terminal or workstation to the PXM back card control port—locally or remotely through a modem.
For more information about connecting to PXM1E or PXM45 cards, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide.
For more information about connecting to PXM1 cards, refer to the Cisco MGX 8850 Multiservice Switch Installation and Configuration Guide.
Note
Use any of the following devices to connect to a PXM back card:
•
•
•
Logging In to PXM and VISM/VISM-PR Cards
To log in to the PXM and VISM/VISM-PR cards, complete the following steps:
Note
Step 1
The login prompt is displayed:
Login:Step 2
Note
The password prompt is displayed:
password:Step 3
For security, the password is displayed as asterisks:
password: *****
Note
For PXM1E or PXM45 cards, the active PXM card is automatically displayed:
PXM1E_SJ.7.PXM.a >For PXM1 cards, the following prompt is displayed:
card number [7]:Step 4
NODENAME.1.7.PXM.a >
Step 5
A list of available card types and associated states is displayed for the MGX 8000 Series platform with which you are connected. The display is similar to the following for all of the PXM cards:
NODENAME.1.7.PXM.a > dspcdsSlot CardState CardType CardAlarm Redundancy---- ----------- -------- --------- -----------1.1 Empty Clear1.2 Active VISM-8T1 Clear1.3 Empty Clear1.4 Empty Clear1.5 Empty Clear1.6 Empty Clear1.7 Active PXM1-OC3 Minor1.8 Empty Clear1.9 Active VISM-8E1 Clear1.10 Empty Clear1.11 Active VISM-8T1 Clear1.12 Boot VISM-8T1 Clear1.13 Active VISM-8T1 Clear1.14 Active VISM-8E1 Clear1.15 Empty Clear1.16 Empty Clear1.17 Empty Clear1.18 Empty Clear1.19 Empty Clear1.20 Empty Clear1.21 Boot VISM-8T1 Clear1.22 Empty Clear1.25 Reserved VISM-8E1 Clear1.26 Empty Clear1.27 Empty Clear1.28 Active VISM-8E1 Clear1.29 Empty Clear1.30 Empty Clear1.31 Empty Clear1.32 Empty ClearNODENAME.1.7.PXM.a >Step 6
Step 7
The VISM/VISM-PR card prompt is displayed when you successfully log in to a VISM/VISM-PR card and has the following format:
NODENAME.1.9.VISM8.aThe VISM/VISM-PR card prompt contains the following data:
•
•
•
•
•
You have completed logging in to the PXM and VISM/VISM-PR cards and can now perform the mandatory initial VISM/VISM-PR card configuration.
Logging Out of VISM/VISM-PR and PXM Cards
To log out of the VISM/VISM-PR and PXM cards, enter one of the following commands:
•
•
Configuring the VISM/VISM-PR
The CLI allows you to configure all features and functions of VISM/VISM-PR.
Configure mandatory commands when you require argument values that are different from the default. Configure optional commands when necessary.
For a list of initial configuration commands for each operating mode, see Table 6-2.
Perform the following tasks with CLI commands to enable your VISM/VISM-PR card applications:
1.
3.
Note
4.
5.
Note
Table 6-2 Mandatory Initial VISM Configuration Command Sequence for All Operating Modes
VoIP Switching
cnfvismmode1
—
cnfvismip
—
addport
—
addrscprtn
—
adddn
—
adddnip
Use this command if you are not using an external DNS.
addmgc
—
addmgcgrpentry
—
cnfcac
—
addln
—
cnflnsig
—
addendpt
—
addcon
—
cnftftpdn
—
addcasvar
—
cnfcasendpt
—
addmgcgrpprotocol
—
cnfdnssrvr
Use this command if you are using an external DNS.
VoIP Trunking
cnfvismmode 1
—
addport
—
addrscprtn
—
addcon
—
cnfvismip
—
addln
—
cnflnsig
—
addendpt
—
addrtpcon
—
AAL2 Trunking
cnfvismmode 1
—
addport
—
addrscprtn
—
cnfcac
—
addln
—
cnflnsig
—
addendpt
—
addcon
—
addcid
—
addccs
—
AAL1 Switching
cnfvismmode 1
—
cnfvismip
—
addport
—
addrscprtn
—
addcon
—
adddn
—
adddnip
—
addmgc
—
addmgcgrpentry
—
addmgcgrpprotocol
—
cnfvismdn
—
addln
—
addendpt
—
Switched AAL2 SVC
cnfvismmode 1
—
cnfvismip
—
addport
—
addrscprtn
—
addcon
—
adddn
—
adddnip
—
addmgc
—
addmgcgrpentry
—
addmgcgrpprotocol
—
cnfvismdn
—
addln
—
addendpt
Switched AAL2 PVC
cnfvismmode 1
—
cnfvismip
—
addport
—
addrscprtn
—
addmgc
—
cnfcac
—
addln
—
cnflnsig
—
addendpt
—
addcon
—
adddn
—
cnftftpdn
—
addcasvar
—
cnfcasendpt
—
cnfconvcci
—
1 The cnfvismmode command may be mandatory or optional, depending upon the operating mode with which the VISM card is seen as displayed on your terminal. A VISM card that is not configured is initially displayed in the VoIP operating mode. Subsequent accesses to the VISM card result in the card being displayed in the VoIP operating mode or in the operating mode you have last configured for the card. If the card is displayed as being in the wrong operating mode, the cnfvismmode command is mandatory to change the operating mode. Use the dspvismparam command to verify the VISM card's current operating mode.
Initial Configuration of the VISM/VISM-PR Card
You must complete the following configuration tasks when you initially configure your VISM/VISM-PR card.
1.
3.
4.
5.
Configuring the Operating Mode
To configure the correct operating mode for your VISM/VISM-PR card, complete the following steps immediately after you apply power:
Step 1
PXM1E_SJ.1.28.VISM8.a > dspvismparamVISM mode: voipSwitching/voipTrunkingVISM features Bit Map: 0x5bcFunctionModuleType: VISM-PR-8T1CAC flag: enableDS0s available: 192Template number: 2Percent of functional DSPs: 100IP address: 172.29.52.229Subnet mask: 255.255.255.0Bearer IP address: 0.0.0.0Bearer Subnet mask: 0.0.0.0RTCP report interval: 5000 msecRTCP receive multiplier: 3RTP receive timer: disableControlPrecedence/Tos: 0x60BearerPrecedence/Tos: 0xa0Aal2 muxing status: disableTftp Server Dn cisco.comAggregate Clipping enableAggregate Svc Bandwidth 50Type <CR> to continue, Q<CR> to stop:
Note
Step 2
If the VISM/VISM-PR card operating mode displayed in Step 1 is not correct for your application, proceed to Step 3.
Step 3
PXM1E_SJ.1.28.VISM8.a > cnfvismmode <mode_number>Replace <mode_number> with one of the following values:
•
•
•
•
•
•
•
Step 4
WARNING: Available CLI Commands will be changed, do you want to proceed (Yes/No)? yA message about the number of available commands displays before the card returns the prompt. The following example shows the number of available commands for AAL2 trunking mode:
INFORMATION: The new 'aal2Trunking' mode has 188 CLI commands.You have completed configuring the operating mode for your VISM/VISM-PR card. Proceed to the "Allocating Resources" section.
Allocating Resources
To allocate resources—virtual ports, controller resources, and codec templates—to your VISM/VISM-PR card, complete the following steps.
Step 1
This command adds an ATM port on a VISM/VISM-PR card. This command does not have arguments. When you add the ATM port, the bandwidth, VPI range, and VCI range are determined.
The VPI range is a single VPI value, the slot ID. The added port is not detected by the controller until you create a resource partition (see Step 2).
Step 2
PXM1E_SJ.1.28.VISM8.a > addrscprtn <controller_id>Replace <controller_id> with a value 1.
Note
A port can be controlled by more than one controller (for example PNNI and PAR), but supports only one controller at a time. VISM/VISM-PR can create one resource partition for each controller in a non-overlapping way. The controller number you specify associates a resource partition to a controller. All resources of a port are associated with the resource partition you specify. When you add a resource partition, the associated controller detects the port as limited by the resource partition.
Step 3
PXM1E_SJ.1.28.VISM8.a > cnfcodectmpl <template_number>Replace <template_number> with one of the following values:
•
Note
•
•
Note
•
Note
•
Step 4
The card will be reset, do you want to proceed (Yes/No)? yThe card resets and returns the prompt.
Configuring Connection Admission Control
Complete the following steps, which allow you to:
•
•
Step 1
PXM1E_SJ.1.28.VISM8.a > dspvismparamVISM mode: aal2TrunkingVISM features Bit Map: 0x2b2FunctionModuleType: VISM-8T1CAC flag: enableDS0s available: 24Template number: 3Percent of functional DSPs: 100IP address: 11.11.11.1Subnet mask: 255.255.255.248Bearer IP address: 15.15.15.1Bearer Subnet mask: 255.255.255.248RTCP report interval: 5000 msecRTCP receive multiplier: 3RTP receive timer: disableControlPrecedence/Tos: 0x20BearerPrecedence/Tos: 0x40Aal2 muxing status: disableTftp Server Dn TFTPDOMAINAggregate Clipping enableAggregate Svc Bandwidth 0
Note
Step 2
PXM1E_SJ.1.28.VISM8.a > cnfcacparams <VAD_duty_cycle> <VAD_Tolerance>Replace the above arguments with the values listed in Table 6-3. The following example shows the typical values for VAD duty cycle and VAD tolerance:
PXM1E_SJ.1.28.VISM8.a > cnfcacparams 61 100
Step 3
PXM1E_SJ.1.28.VISM8.a > cnfconcacparams <LCN> <VADTolerance> <VADDutyCycle>Replace <LCN> with the logical channel number, in the range 131-510. Replace <VADTolerance> and <VADDutyCycle> with the values listed in Table 6-3. The following example shows the typical values for VAD tolerance and VAD duty cycle on LCN 131:
PXM1E_SJ.1.28.VISM8.a > cnfconcacparams 131 100 61
Step 4
Note
PXM1E_SJ.1.28.VISM8.a > cnfvbdpol <sysCarrLossPol> <sysCacRejPol>Replace the above arguments with the values listed in Table 6-4.
You have completed configuring CAC on your VISM/VISM-PR card. Proceed to the "Placing the VISM Card In Service" section
Placing the VISM Card In Service
Type the cnfgwis command and press Enter to place the VISM card in service. The VISM card prompt terminates with an a to indicate the in-service state:
NODENAME.1.9.VISM8.a
Note
Placing the VISM Card Out of Service
Type the cnfgwoos command, a oos-method argument value, and press Enter to place the VISM card out of service. Specify the oos-method argument with one of the following values:
•
•
The VISM card prompt terminates with an s to indicate the out-of-service (standby) state:
NODENAME.1.9.VISM8.s
Note
Configuring the TDM Side
Perform the following tasks to configure the TDM side of your networking application:
1.
2.
3.
4.
5.
8.
9.
Configuring T1 and E1 Lines
This section deals with the configuration of the eight physical T1/E1 ports on the VISM/VISM-PR back card or, if bulk distribution is used, the equivalent ports being fed from the Service Resource Module (SRM) card.
Complete the following steps to:
•
•
Note
Step 1
mgx8850.1.12.VISM8.a > addln <line_number>Replace <line_number> with a value in the range 1-8. This example shows adding line 1.
mgx8850.1.12.VISM8.a > addln 1Step 2
mgx8850.1.12.VISM8.a > cnflnsig <line_number> <signaling_type>Replace <line_number> with the value of the line you added in Step 1.
Replace <signaling_type> with one of the following values:
•
•
•
This example shows configuring line 1 with CAS.
mgx8850.1.12.VISM8.a > cnflnsig 1 1
Note
Step 3
mgx8850.1.12.VISM8.a > cnfln <line_number> <line_code> <line_length> <clk_src> <line_type> <loopback_detection> [circuit_identifier]Replace the above arguments with the values listed in Table 6-5 for the cnfln parameters. This example shows the recommended E1 parameters.
mgx8850.1.12.VISM8.a > cnfln 1 3 9 2 7 1
Step 4
PXM1E_SJ.1.28.VISM8.a > cnfalm -ds1 <LineNum> -red <RedSeverity> -rai <RAISeverity> -neu <NEAlarmUpcount> -ned <NEAlarmDncount> -net <NEAlarmThreshold> -feu <FEAlarmUpcount> -fed <FEAlarmDncount> -fet <FEAlarmThreshold>Replace the above arguments with the values listed in Table 6-6.
Step 5
Note
PXM1E_SJ.1.28.VISM8.a > cnflntrunkcond <line_number> <trunkCondType>Replace <line_number> with a value in the range 1-8.
Replace <trunkCondType> with one of the following values:
•
•
If you enable trunk line conditioning, VISM/VISM-PR conditions the affected DS0 when an alarm indication signal (AIS) is detected on the ATM side. Trunk line conditioning consists of transmitting an idle code pattern for 2.5 seconds followed by the seized code specified in the cnfcascode command.
Note
Step 6
PXM1E_SJ.1.28.VISM8.a > addlnloop <line_number>Replace <line_number> with the line in which you want the local loopback, in the range 1-8.
Use the dellnloop command to remove the local loopback state on a VISM/VISM-PR line.
Note
Step 7
mgx8850.1.12.VISM8.a > dspln 1The following example shows some of the sample output from the dspln command:
LineNum: 1LineConnectorType: RJ-48LineEnable: ModifyLineType: dsx1E1CLEARLineCoding: dsx1HDB3LineLength: G.703 120 ohmLineXmtClockSource: LocalTimingLineLoopbackCommand: NoLoopLineSendCode: NoCodeLineUsedTimeslotsBitMap: 0xfffffffeLineLoopbackCodeDetection: codeDetectDisabledLineSignalingType: CCSLineCcsChannels: 0x0LineTrunkConditioning: disableCircuitIdentifier:TxDigitOrder: aniThenDnisTonePlanRegion:TonePlanVersion: 0RingingTO: 180RingBackTO: 180BusyTO: 30Type <CR> to continue, Q<CR> to stop:ReorderTO: 30DialTO: 16StutterDialTO: 16OffHookAlertTO: 5RemoteRingbackMethod: proxyLineNumOfValidEntries: 8Placing T1 and E1 Lines In Service
To place a T1 or E1 line in service, enter the cnflnis command with the <line_number> in the range 1-8.
Note
Placing T1 and E1 Lines Out of Service
To place a T1 or E1 line out of service, enter the cnflnoos command.
PXM1E_SJ.1.28.VISM8.a > cnflnoos <line_number> <shutdown_method>Replace <line_number> with a value in the range 1-8.
Replace <shutdown_method> with one of the following values:
•
•
Note
Configuring the PXM1 and VISM/VISM-PR Cards Clocking Source
Complete the following steps to configure the clocking source on your PXM1 and VISM/VISM-PR cards.
Note
Step 1
The type of equipment connected to the VISM/VISM-PR T1 or E1 lines might dictate this choice. If the selected clock source is from one of the VISM/VISM-PR T1 or E1 lines, that line must be connected to port 1 of the VISM/VISM-PR back card. For more information on VISM/VISM-PR back cards and port locations, see Figure 2-3 on page 2-4.
Step 2
Step 3
M8850_R1.1.7.PXM.a > cnfclksrc <slot.port> <clktyp> [-bits e1|t1][-revertive <enable|disable>]Replace <slot.port> with the following values:
•
•
Note
Replace <clktype> with one of the following values:
–
–
–
–
Specify the cnfclksrc command argument values according to the following rules:
•
cnfclksrc 7.35 P
Note
•
cnfclksrc 7.n P
Note
•
•
cnfclksrc 7.X N
Note
•
cnfclksrc y.1 P
Note
Step 4
Step 5
PXM1E_SJ.1.28.VISM8.a > cnfln <line_number> <line_code> <line_length> <clk_src> <line_type> <loopback_detection> [circuit_identifier]
Note
Replace the above arguments with the values listed in Table 6-7 for the cnfln parameters.
Step 6
You have completed configuring the clocking source for your PXM1 and VISM/VISM-PR cards. Proceed to the "Configuring DS0 Channels" section.
Configuring the PXM1E or PXM45 Card as Clocking Source
Use the cnfncdpclksrc command to configure the PXM1E or PXM45 card as the primary clock source.
Use the following commands to display and verify your configuration:
•
•
See the "Related Documentation" section on page xxx for the appropriate document to use the commands in this section.
Configuring DS0 Channels
You are now ready to configure the 24 (T1) or 31 (E1) DS0 channels on the VISM/VISM-PR T1 or E1 lines.
Table 6-8 describes the VISM/VISM-PR DS0 density when the cards are used in combination with the supported codecs.
Table 6-8 VISM/VISM-PR DS0 Density with Codec Support
G.711
192
248
192
248
G.723
—
—
144
144
G.726
145
145
192
248
G.729
145
145
192
248
To configure a DS0 channel, complete the following tasks:
1.
2.
Add DS0 Endpoints to Lines
Complete the following steps to add DS0 endpoints to lines:
Step 1
Step 2
PXM1E_SJ.1.28.VISM8.a > addendpt <endpt_num> <ds1_num> <ds0_num>
Note
Replace the above arguments with the values listed in Table 6-9.
Step 3
mgx8850.1.12.VISM8.a > addendpts <endpt_num> <ds1_num> <ds0_num> <endpts_num>Replace the above arguments with the values listed in Table 6-10 for the addendpts parameters.
Step 4
PXM1E_SJ.1.28.VISM8.a > addendptloop <endpt_num>Replace <endpt_num> with one of the following values:
•
–
–
–
•
–
–
•
–
–
–
•
–
–
•
–
–
Step 5
PXM1E_SJ.1.28.VISM8.a > cnfds0loop <line_number> <ds0_number> <lineloopback_type>Replace the above arguments with the values listed in Table 6-11.
You have completed adding and configuring a DS1 line and DS0 endpoints. Proceed to one of the following sections:
•
•
Configuring TDM Side Signaling for Applications Using CCS
Note
CCS signaling uses a dedicated channel on a DS1 line to carry the signaling for the other channels on the line. You must identify the signaling channel to the VISM/VISM-PR card. CCS signaling is used for the following operating modes:
•
•
•
Complete the following steps to add and configure CCS signaling:
Step 1
PXM1E_SJ.1.28.VISM8.a > addccs <line_number> <ds0_number> <LCN>Replace the above arguments with the values listed in Table 6-12 for the addccs command.
If you are configuring CCS for the AAL2 trunking operating mode, the CCS configuration is complete. Proceed to the "Configuring Bearer Processing" section.
Before proceeding to Step 2, ensure that you add a session and a session set described in the "Configuring ISDN PRI Backhaul" section.
Step 2
PXM1E_SJ.1.28.VISM8.a > addlapd <line_number> <ds0_number> |<lapd_side> <lapd_application_type>|Replace the above arguments with the values listed in Table 6-13 for the addlapd command.
Table 6-13 Parameters for addlapd Command
line_number
Line number. Type the value used in Step 1.
ds0_number
DS0 number. Type the value used in Step 1.
•
•
|lapd_side|
(Optional) The side of the LAPD link. Values are
•
•
|lapd_application_type|
(Optional) Application type of the LAPD ISDN D channel. Values are
•
•
Step 3
PXM1E_SJ.1.28.VISM8.a > cnflapdtype <line_number> <ds0_number> <lapd_type>Replace the above arguments with the values listed in Table 6-14 for the cnflapdtype command.
Table 6-14 Parameters for cnflapdtype Command
line_number
Line number. Type the value used in Step 1.
ds0_number
DS0 number. Type the value used in Step 1.
•
•
lapd_type
Type of LAPD stack to configure on the specified line and DS0. Values are
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Step 4
PXM1E_SJ.1.28.VISM8.a > cnflapdwinsize <line_number> <ds0_number> <window_size>Replace the above arguments with the values listed in Table 6-15 for the cnflapdwinsize command.
Table 6-15 Parameters for cnflapdwinsize Command
line_number
Line number. Type the value used in Step 1.
ds0_number
DS0 number. Type the value used in Step 1.
•
•
window_size
Maximum number of outstanding (unacknowledged) I-frames that can be accumulated before sending an acknowledgment. Range is 1-127. Default is 7.
Step 5
PXM1E_SJ.1.28.VISM8.a > cnflapdretrans <line_number> <ds0_number> <N200>Replace the above arguments with the values listed in Table 6-16 for the cnflapdretrans command.
Table 6-16 Parameters for cnflapdretrans Command
line_number
Line number. Type the value used in Step 1.
ds0_number
DS0 number. Type the value used in Step 1.
•
•
N200
Maximum frame retransmissions. Range is 1-10. Default is 3.
Step 6
PXM1E_SJ.1.28.VISM8.a > cnflapdretrans <line_number> <ds0_number> <timer_T200> <timer_T203>Replace the above arguments with the values listed in Table 6-17 for the cnflapdtimer command.
Table 6-17 Parameters for cnflapdtimer Command
line_number
Line number. Type the value used in Step 1.
ds0_number
DS0 number. Type the value used in Step 1.
•
•
timer_T200
T200 timer. Time (defined in milliseconds) between frame transmission initiations. Ranges are
•
•
Note
timer_T203
T203 timer. Maximum time (defined in milliseconds) allowed without a frame being exchanged. Ranges are
•
•
Note
You have completed adding and configuring CCS. Proceed to the "Configuring Bearer Processing" section.
Configuring TDM Side Signaling for Applications Using CAS
Note
CAS signaling is used for the following operating modes:
•
•
•
•
•
Complete the following steps to add and configure CAS signaling.
Note
Step 1
PXM1E_SJ.1.28.VISM8.a > cnfcasparamsource <endpt_num> <ParamSource>Replace the above arguments with the values listed in Table 6-18 for the cnfcasparamsource command.
Note
Step 2
PXM1E_SJ.1.28.VISM8.a > cnfcasonhooktime <endpt_num> <OnHookMinTime>Replace the above arguments with the values listed in Table 6-19 for the cnfcasonhooktime command.
Table 6-19 Parameters for cnfcasonhooktime Command
endpt_num
Type the value used in Step 1.
OnHookMinTime
On-hook time (defined in milliseconds). Range is 10-1000 ms. Default is 300 ms.
Step 3
PXM1E_SJ.1.28.VISM8.a > cnfcasoffhooktime <endpt_num> <OffHookMintime>Replace the above arguments with the values listed in Table 6-20 for the cnfcasoffhooktime command.
Table 6-20 Parameters for cnfcasoffhooktime Command
endpt_num
Type the value used in Step 1.
OffHookMintime
Off-hook time (defined in milliseconds). Range is 10-1000 ms. Default is 2- ms.
Step 4
PXM1E_SJ.1.28.VISM8.a > cnfcaswinktime <endpt_num> <WinkMinTime> <WinkMaxTime> <WinkBreakTime>Replace the above arguments with the values listed in Table 6-21 for the cnfcaswinktime command.
Table 6-21 Parameters for cnfcaswinktime Command
endpt_num
Type the value used in Step 1.
WinkMinTime
Minimum make duration time (defined in milliseconds) of the wink. Range is 10-1000 ms. Default is 100 ms.
WinkMaxTime
Maximum make duration time (defined in milliseconds) of the wink. Range is 10-3000 ms. Default is 1000 ms.
WinkBreakTime
Minimum break duration time (defined in milliseconds) of the wink. Range is 10-1000 ms. Default is 20 ms.
A wink begins with an on-hook pattern, goes to off-hook, and returns to on-hook. All three make and break duration time argument values must be observed for the signaling sequence to be recognized as a wink.
Step 5
PXM1E_SJ.1.28.VISM8.a > cnfcasglaretime <endpt_num> <GlareTime>Replace the above arguments with the values listed in Table 6-22 for the cnfcasglaretime command.
Table 6-22 Parameters for cnfcasglaretime Command
endpt_num
Type the value used in Step 1.
GlareTime
Glare time (defined in milliseconds). Range is 10-1000 ms. Default is 500 ms.
Step 6
PXM1E_SJ.1.28.VISM8.a > cnfcasguardtime <endpt_num> <GuardTime>Replace the above arguments with the values listed in Table 6-23 for the cnfcasguardtime command.
Table 6-23 Parameters for cnfcasguardtime Command
endpt_num
Type the value used in Step 1.
GuardTime
Guard time (defined in milliseconds). Range is 10-1000 ms. Default is 800 ms.
Step 7
PXM1E_SJ.1.28.VISM8.a > cnfcasdialdelay <endpt_num> <DialDelayTime>Replace the above arguments with the values listed in Table 6-24 for the cnfcasdialdelaytime command.
Table 6-24 Parameters for cnfcasdialdelaytime Command
endpt_num
Type the value used in Step 1.
DialDelayTime
Wait time (defined in milliseconds) for outpulsing digits to the PBX after sending an off-hook event. Range is 10-1000. Default is 500.
Dial delay is the time that VISM waits before sending dialing digits after sending an off-hook event.
Note
Step 8
To configure CAS for the AAL2 trunking operating mode, proceed to Step 9.
Step 9
PXM1E_SJ.1.28.VISM8.a > cnfcascode <endpt_num> <idle_code> <seized_code> |<endpts_num>|Replace the above arguments with the values listed in Table 6-25 for the cnfcascode command.
Table 6-25 Parameters for cnfcascode Command
endpt_num
Type the value used in Step 1.
Note
idle_code
The 4-bit idle code. Range is 0-15 and represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively. Bit 3 is the most significant.
seized_code
The 4-bit seized code. Range is 0-15 and represents the four signaling bits—A, B, C, and D—in binary, as bits 3, 2, 1, and 0 respectively. Bit 3 is the most significant.
|endpts_num|
(Optional) The last endpoint in a consecutive range of endpoints. Ranges are
•
–
–
–
•
–
–
•
–
–
–
•
–
–
•
–
–
Step 10
PXM1E_SJ.1.28.VISM8.a > cnfds0localcas <line_number> <ds0_number> <cas_value> <cas_bit_pattern>Replace the above arguments with the values listed in Table 6-26 for the cnfds0localcas command.
The cnfds0localcas command is not applicable if you have one of the following conditions:
•
•
•
Step 11
Note
PXM1E_SJ.1.28.VISM8.a > addcasvar <variant_name> <file_name> |<cas_var_source>|Replace the above arguments with the values listed in Table 6-27 for the addcasvar command.
Step 12
PXM1E_SJ.1.28.VISM8.a > cnfcasvar <variant_name> <country_code> <Tring> <Tpart> <Tcrit> <TMF>Replace the above arguments with the values listed in Table 6-28 for the cnfcasvar command.
Table 6-28 Parameters for cnfcasvar Command
variant_name
Name of the CAS variant. Type the value used in Step 11
country_code
Country code of the variant. The value must be a two-character text string.
Tring
Ringing time (defined in seconds). Range is 10-600 secs.
Tpart
Partial dial time (defined in seconds). Range is 10-10000 secs—in increments of 10 secs.
Tcrit
Critical timing (defined in seconds). Range is 0-10000 secs—in increments of 10 secs.
TMF
Interdigit timeout value for MF digits (defined in seconds). Range is 1-10 secs.
Step 13
PXM1E_SJ.1.28.VISM8.a > cnfcasendpt <endpt_number> <casVariantName>Replace the above arguments with the values listed in Table 6-29 for the cnfcasendpt command.
Table 6-29 Parameters for cnfcasendpt Command
endpt_number
Type the value used in Step 9.
casVariantName
Type the value used in Step 11
You have completed adding and configuring CAS signaling. Proceed to the "Configuring Bearer Processing" section.
Configuring Bearer Processing
Processing of the bearer payload takes place either upon receipt of the payload from a T1 or E1 line or prior to transmission over a T1 or E1 line. You must complete the following tasks to configure bearer processing:
4.
Configuring Codecs
Complete the following steps to assign and configure a codec template:
Step 1
PXM1E_SJ.1.28.VISM8.a > cnfcodectmpl <template_number>Replace <template_number> with one of the following values:
•
Note
•
•
Note
•
Note
•
Step 2
The packetization period is defined in three separate commands depending upon the ATM method used:
•
•
•
•
PXM1E_SJ.1.28.VISM8.a > cnfcodecparams <codecType> <pktPeriod> |<codecPreference> <codecString> <ianaCodecNum>|Replace the above arguments with the values listed in Table 6-30 for the cnfcodecparams command.
Step 3
PXM1E_SJ.1.28.VISM8.a > cnfcodecneg <codecNegOpt>Replace <codecNegOpt> with one of the following priority values:
•
•
•
•
•
•
You have completed assigning and configuring the codec template. Proceed to the "Configuring ECAN" section.
Configuring ECAN
Complete the following steps to enable and configure echo cancellation (ECAN) on a line-by-line basis:
Step 1
PXM1E_SJ.1.28.VISM8.a > cnfecanenable <lineNum> <ECANEnable>Replace <lineNum> with a value in the range 1-8.
Replace <ECANEnable> with one of the following values:
•
•
Step 2
PXM1E_SJ.1.28.VISM8.a >cnfecanrec <lineNum> <residualEchoControl>Replace <lineNum> the value used in Step 1.
Replace <residualEchoControl> with one of the following values:
•
•
•
Step 3
PXM1E_SJ.1.28.VISM8.a >cnfecantail <lineNum> <maximumTail>Replace <lineNum> the value used in Step 1.
Replace <maximumTail> with one of the following values:
•
•
•
•
•
•
•
•
Step 4
PXM1E_SJ.1.28.VISM8.a > cnferl <DB_loss>Replace <DB_loss> with one of the following values:
•
•
•
•
Step 5
PXM1E_SJ.1.28.VISM8.a > cnfconvbdpol <LCN> <CarrierLossPol> <CACRejPol>Replace the above arguments with the values listed in Table 6-31 for the cnfconvbdpol command.
You have completed enabling and configuring ECAN on your lines. Proceed to the "Configuring Jitter" section.
Configuring Jitter
You can dejitter the voice payload to improve the quality of the egress voice stream.
Note
Complete the following steps to specify and configure jitter mode:
Step 1
PXM1E_SJ.1.28.VISM8.a > cnfjtrmode <jtr_mode>Replace <jtr_mode> with one of the following values:
•
•
Step 2
If you chose an adaptive buffer size in Step 1, proceed to Step 3.
Step 3
PXM1E_SJ.1.28.VISM8.a > cnfjtrinitdelay <jtr_initdelay>Replace <jtr_initdelay> with one of the following values:
•
•
You have completed configuring jitter. Proceed to the "Configuring the ATM Network Side" section.
Configuring PNNI for AAL1/AAL2 SVCs
Use the cnfpncon command to configure Private Network-to-Network Interface (PNNI) priority routing for AAL1/AAL2 switched virtual circuits (SVCs). See Chapter 7, "CLI Commands," for more information on using the cnfpncon command.
Configuring the ATM Network Side
Configuring the ATM network side consists of setting up ATM PVCs across the network and providing the mechanism by which calls are routed over the correct PVC. The PVC configuration depends on the VISM operating mode you require for your application.
•
•
Each PVC is set up as three segments consisting of two local segments and one network segment. The local segments are set up between the two VISM cards (one at the end of the PVC) and their respective PXM cards. The network segment is set up between the two PXM cards across the network. Refer to the Cisco MGX 8250 and Cisco MGX 8230 Installation and Configuration guides for more information.
In AAL2 trunking operating mode, you must bind endpoints to specific DS0s using the addendpoint(s) commands. You must also create CIDs (connection identifiers) for each PVC that binds the endpoints to the CID and a PVC. This ensures that calls arriving at a specific DS0 are automatically routed to the preconfigured CID and PVC over nailed-down trunks. There is no switched or call agent involvement.
•
Each PVC is set up as three segments consisting of two local segments and one network segment. The local segments are set up between the two VISM cards (one at the end of the PVC) and their respective PXM cards. The network segment is set up between the two PXM cards across the network. Refer to the Cisco MGX 8850 Release 1 installation and configuration guides for more information.
In switched AAL2 PVC operating mode, you must bind endpoints to specific DS0s using the addendpoint(s) commands. You must also create VCCIs (virtual circuit connection identifiers), which identify each PVC and associate each PVC with a specific remote ATM address. At call setup time, the call agent informs VISM which VCCI to use for the call and instructs VISM to set up a CID for transport across the VCCI. This ensures that the binding of a DS0 to a CID and PVC is dynamic by using of the called address.
This section contains the following topics:
1.
2.
3.
4.
Configuring PVC Connections for All Operating Modes
Complete the following steps to configure PVC connections for all operating modes:
Step 1
PXM1E_SJ.1.28.VISM8.a > addcon <localVCI> <preference> <pvcType> <application> <PCR> <mastership> |<remoteConnId> <serviceType> [<scr> <mbs>]|Replace the above arguments with the values listed in Table 6-32 for the addcon command.
Step 2
PXM1E_SJ.1.28.VISM8.a > cnfcon <LCN> <PCR> <service_type> |<SCR_ingress> <MBS_ingress>|Replace the above arguments with the values listed in Table 6-33 for the cnfcon command.
Table 6-33 Parameters for cnfcon Command
LCN
Type the value you entered for the localVCI argument in Step 1.
PCR
Peak cell rate (PCR) described in cells per second.
Note
Ranges are
•
•
•
•
•
Note
service_type
Service type. Values are
•
•
•
•
•
•
•
Note
|SCR_ingress|
(Optional) Sustainable cell rate (SCR). Range is from 15 to the value you configured for the PCR argument value.
Note
|MBS_ingress|
(Optional) Maximum burst size (MBS)—maximum number of cells transmitted at the peak cell rate. Range is from 1 cell to 10 times the value you configured for the SCR_ingresse argument value.
Note
Step 3
PXM1E_SJ.1.28.VISM8.a > addconloop <LCN>Replace <LCN> with a value in the range 131-510.
Note
You have completed configuring PVC connections. Proceed to one of the following sections, as appropriate:
•
•
•
Configuring VoIP Switching/Trunking Operating Mode Parameters
Complete the following steps to configure VoIP switching operating mode parameters:
Step 1
PXM1E_SJ.1.28.VISM8.a > cnfconprotect <LCN> <protection> <lock_state> <fallback_LCN>Replace the above arguments with the values listed in Table 6-34 for the cnfconprotect command.
Step 2
Note
PXM1E_SJ.1.28.VISM8.a > cnfdeftos <control_precedence> <control_tos> |<bearer_precedence> <bearer_tos>|Replace the above arguments with the values listed in Table 6-35 for the cnfdeftos command.
Step 3
PXM1E_SJ.1.28.VISM8.a > cnfvoiptransparams <DtmfRelay> <CasBits> |<EventNego> <EventNegoPolicy> <SIDPayloadType>|Replace the above arguments with the values listed in Table 6-36 for the cnfvoiptransparams command.
You have completed configuring the VoIP switching operating mode parameters. Proceed to the "Configuring the Call Agent Interface" section.
Configuring AAL2 Trunking Operating Mode Parameters
Complete the following steps to configure AAL2 trunking operating mode parameters:
Step 1
PXM1E_SJ.1.28.VISM8.a > addcid <endpt_num> <LCN> <cid_num> <codec_type> <profile_type> <profile_number> <voice_activity_detection> <vad_init_timer> <echo_cancellation> <triple_redundancy_protection> <cas_signaling_transport> <dtmf_tone_transport_as_AAL2> <ICS_enable> <pktPeriod>Replace the above arguments with the values listed in Table 6-37 for the addcid command.
Table 6-37 Parameters for addcid Command
endpt_num
Endpoint number which is to be related to the LCN/CID pair being added.
•
–
–
–
•
–
–
•
–
–
–
•
–
–
•
–
–
LCN
Logical channel number (LCN) of the LCN/CID pair. Range is 131-510.
cid_num
Channel identification number of the LCN/CID pair. Range is 8-255.
codec_type
Type of coding/decoding to be performed on the data stream.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
|profile_type|
(Optional) Profile type to be used for the CID.
•
•
Note
|profile_number|
(Optional) Number of the profile.
•
•
•
•
•
•
•
•
•
•
•
•
|voice_activity_detection|
(Optional) Value to enable or disable voice activity detection (VAD).
•
•
Note
|vad_init_timer|
(Optional) VAD initial (holdover) timer. Range is 250-65535 ms. Default is 250 ms.
|echo_cancellation|
(Optional) Value to enable or disable echo cancellation (ECAN).
•
•
|triple_redundancy_
protection|(Optional) Value to enable or disable triple redundancy protection for type 3 packets.
•
•
Note
|cas_signaling_transport|
(Optional) Value to enable or disable channel associated signaling (CAS) transport as AAL2 type3 packets.
•
•
This parameter does not affect any inbound signaling.
|dtmf_tone_transport_as_AAL2|
(Optional) Value to enable or disable DTMF tone transport as AAL2 type 3 packets. It can be one of the following values:
•
•
Note
|ICS_enable|
(Optional) Value to enable or disable idle code suppression (ICS) for the CID.
•
•
|pktPeriod|
(Optional) Packetization period (defined in milliseconds). This parameter applies only to G.729a compression.
•
•
•
Note
The pktPeriod argument requires you to configure packetization in the following ways for the other two operating modes:
•
•
The CID is a mechanism within AAL2 that allows multiple calls to be transported across a single AAL2 PVC. The addcid command binds an endpoint to a logical channel (PVC).
Step 2
PXM1E_SJ.1.28.VISM8.a > cnfaal2subcellmuxing <muxing status>Replace <muxing status> with one of the following values:
•
•
You have completed configuring the AAL2 trunking operating mode parameters.
Configuring Switched AAL2 PVC Operating Mode Parameters
Note
You must complete the following tasks to configure the switched AAL2 PVC operating mode parameters:
1.
2.
Note
3.
Configuring a Virtual Circuit Connection Identifier
Complete the following steps to configure a VCCI for the switched AAL2 PVC operating mode:
Step 1
PXM1E_SJ.1.28.VISM8.a > cnfconvcci <lcn> <vcci> <farend_addr_type> |<farend_addr>|Replace the above arguments with the values listed in Table 6-38 for the cnfconvcci command.
Step 2
You have completed configuring VCCIs for the switched AAL2 PVC operating mode. Proceed to the "Modifying the AAL2 Operating Mode Profile Table" section.
Modifying the AAL2 Operating Mode Profile Table
A profile table is associated with each AAL2 operating mode. This profile table specifies the encoding format, which tells the card how to interpret the packets.
You can use the dspaal2profile command to see the values for a profile type. Example 6-1 shows the default values for ITU profile type 1.
Example 6-1 Default Values for ITU Profile 1
nodename.1.28.VISM8.a > dspaal2profile 1 1UUI Packet Packet Seq. No.Codepoint Length Time IntervalRange (octets) Codec SID M (ms) (ms)0-15 40 PCMU No SID 1 5 50-15 40 PCMA No SID 1 5 5Table 6-39 describes the fields shown in the display.
VISM/VISM-PR creates the profile table with the defaults that are listed in Table 6-40. This table is a summary of the output from the dspaal2profile command.
Complete the following steps to assign a profile preference and to modify the packet period and SID values of the profile table, as necessary.
Note
Step 1
PXM1E_SJ.1.28.VISM8.a > cnfprofparams <profileType> <profileNumber> <profilePreference>Replace the above arguments with the values listed in Table 6-41 for the cnfprofparams command.
Step 2
PXM1E_SJ.1.28.VISM8.a > cnfprofelemvoice <profileType> <profileNumber> <voice_codec_type> <pktPeriod> <sid>Replace the above arguments with the values listed in Table 6-42 for the cnfprofelemvoice command.
Step 3
PXM1E_SJ.1.28.VISM8.a > cnfprofelemvbd <profileType> <profileNumber> <codecType> <pktPeriod>Replace the above arguments with the values listed in Table 6-43 for the cnfprofelemvbd command.
Step 4
PXM1E_SJ.1.28.VISM8.a > cnfprofneg <profileNegotiationOption>Profiles can be from the call agent local connection option (LCO) list, local MIB, or a list received from the remote gateway in the session descriptor protocol (SDP) data.
Replace <profileNegotiationOption> with one of the following values:
•
•
•
•
•
•
You have completed modifying the switched AAL2 PVC operating mode profile table. Proceed to the "Configuring AAL2 PVC Parameters" section.
Configuring AAL2 PVC Parameters
Complete the following steps to configure AAL2 PVC parameters:
Step 1
PXM1E_SJ.1.28.VISM8.a > cnfaal2timerparams <VadTimer> <CidFillTimer>Replace <VadTimer> with the VAD holdover time in the range 250-65535 ms. Default is 250 ms.
Replace <CidFillTimer> with the maximum wait time for cell content filling when the next packet is not ready. Range is 250-65535 ms. Default is 250 ms.
Step 2
PXM1E_SJ.1.28.VISM8.a > cnfaal2transparams <DtmfRelay> <CasBits> <Type3Redundancy>Replace the above arguments with the values listed in Table 6-44 for the cnfaal2transparams command.
You have completed configuring the switched AAL2 PVC operating mode parameters. Proceed to the "Configuring the Call Agent Interface" section.
Configuring the Call Agent Interface
Note
VISM can use one to eight call agents to accomplish the following:
•
•
•
VISM uses IP connectivity in order to communicate with the call agents (see Figure 6-1).
Figure 6-1 VISM to Call Agent Communication
Physical connectivity is through a PVC on an MGX 8000 Series platform PXM card OC-3 port, to a router (in the IP Connectivity cloud in Figure 6-1), and then to the call agents.
Logical IP connectivity is performed by resolving domain name and IP address associations. The associations are accomplished in the following ways:
•
•
Figure 6-1 shows a TFTP server which also has an IP connection to VISM.
Complete the following tasks to configure the call agent interface:
1.
2.
3.
4.
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
PXM1E_SJ.1.28.VISM8.a > cnfvismdn <domain_name>Replace the domain_name argument value with a text string of up to 64 alphanumeric characters; spaces are not allowed. Default name is cisco.com as shown in the following example:
PXM1E_SJ.1.28.VISM8.a > cnfvismdn cisco.com
Step 2
PXM1E_SJ.1.28.VISM8.a > cnfvismip <vismIpAddr> <netMask> [vismBearerIpAddr bearerNetMask]Replace the above arguments with the values listed in Table 6-45 for the cnfvismip command.
The following example shows the IP address and subnet mask configured for the VISM card and the output of the command.
PXM1E_SJ.1.28.VISM8.a > cnfvismip 172.29.52.003 255.255.255.248Attaching network interface atm0... done.Step 3
PXM1E_SJ.1.28.VISM8.a > cnftftpdn <domain_name>Step 4
Note
PXM1E_SJ.1.28.VISM8.a > cnftftpdn cisco.comStep 5
You have completed configuring domain names and IP addresses for VISM cards and call agents. Proceed to the "Setting Up Call Agents and Protocols" section.
Setting Up Call Agents and Protocols
Complete the following steps to set up call agents and media gateway control protocols:
Step 1
PXM1E_SJ.1.28.VISM8.a > adddn <mg_domain_num> <mg_domain_name> |<Resolution_Type>|Replace the above arguments with the values listed in Table 6-46 for the adddn command.
Step 2
If you are using an external DNS to resolve domain names, proceed to Step 3.
Step 3
PXM1E_SJ.1.28.VISM8.a > adddnip <Resolution_index> <domain_name> <IP_address> <preference>Replace the above arguments with the values listed in Table 6-47 for the adddnip command.
Step 4
PXM1E_SJ.1.28.VISM8.a > addmgcgrpentry <Red_Group_Num> <mgcRedGrpMgcNum> <mgcRedGrpPref>Replace the above arguments with the values listed in Table 6-48 for the addmgcgrpentry command.
Step 5
Note
PXM1E_SJ.1.28.VISM8.a > cnfmgcgrpparam <Red_Group_Num> <mgcRedGrpStateChgNtfy> |<mgcRedGrpPriority>|Replace the above arguments with the values listed in Table 6-49 for the cnfmgcgrpparam command.
Step 6
PXM1E_SJ.1.28.VISM8.a > addmgcgrpprotocol <Red_Group_Num> <protocol_number> |<Qrntn_Persist> <Qrntn_Def> <Sign_OnOff> <Prov_Resp> <RspAck_Attr> <Disc_Proc> <Cancel_Graceful>|Replace the above arguments with the values listed in Table 6-50 for the addmgcgrpprotocol command.
Step 7
You have completed setting up call agents and media gateway control protocols. Proceed to the "Configuring Gateway Control Protocols" section, if necessary.
Configuring Gateway Control Protocols
Complete the following steps to configure gateway control protocols.
Note
Step 1
PXM1E_SJ.1.28.VISM8.a > cnfxgcppeer <mgcNumber> <protocolNumber> <UDP_port>Replace the above arguments with the values listed in Table 6-51 for the cnfxgcppeer command.
Step 2
PXM1E_SJ.1.28.VISM8.a > cnfxgcpmwd <timeout value>Replace <timeout value> with the maximum wait time in the range 0-600000 ms. Default is 10000 ms.
Note
Step 3
PXM1E_SJ.1.28.VISM8.a > cnfxgcpretry <minTimeout> <retryCount> <maxTimeout>Replace the above arguments with the values listed in Table 6-52 for the cnfxgcpretry command.
Step 4
PXM1E_SJ.1.28.VISM8.a > cnfxgcpbt <networkType> <vcType> |<connType>|Replace the above arguments with the values listed in Table 6-53 for the cnfxgcpbt command.
Step 5
Note
Note
PXM1E_SJ.1.28.VISM8.a > addxgcppersistevt <index> <persistent_event>Replace <index> with a package event number in the range 1-16.
Replace <persistent_event> with one of the following values:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Step 6
PXM1E_SJ.1.28.VISM8.a > cnfsrcppeer <peerId> <port>Replace <peerId> with a (call agent) identification number in the range 1-8.
Replace <port> with the UDP port number in the range 1025-65535.
Note
Step 7
PXM1E_SJ.1.28.VISM8.a > cnfsrcppeergrpparam <Red_Group_Num> <Heart_geat_interval> <max_pdu>Replace the above arguments with the values listed in Table 6-54 for the cnfsrcppeergrpparam command.
Step 8
PXM1E_SJ.1.28.VISM8.a > cnfsrcpretry <minTimeout> <retryCount> <maxTimeout>Replace the above arguments with the values listed in Table 6-55 for the cnfsrcpretry command.
Step 9
PXM1E_SJ.1.28.VISM8.a > cnfco4timer <timeout>Replace <timeout> with a value in the range 50-10000 ms. Default is 1000 ms.
Step 10
Configuring ISDN PRI Backhaul
ISDN PRI backhaul configuration consists of setting up RUDP session structures:
•
•
•
A session group applies to a specified call agent and allows automatic switching to another session in the group if an active session fails. You can configure individual sessions when you have completed setting up the session sets and session groups. Refer to Chapter 5, "VISM/VISM-PR Functional Description," for more information on session structures.
Note
Complete the following steps to configure ISDN PRI backhaul:
Step 1
PXM1E_SJ.1.28.VISM8.a > addsesset <set_number> <fault_tolerant>Replace <set_number> with a value in the range 1-16.
Note
Replace <fault_tolerant> with one of the following values:
•
•
Step 2
PXM1E_SJ.1.28.VISM8.a > addsesgrp <group_number> <set_number> <mgc_name>Replace the above arguments with the values listed in Table 6-56 for the addsesgrp command.
Step 3
Note
PXM1E_SJ.1.28.VISM8.a > addses <session_number> <group_number> <priority> <local_port> <remote_port>Replace the above arguments with the values listed in Table 6-57 for the addses command.
Step 4
PXM1E_SJ.1.28.VISM8.a > cnfsesack <session_num> <acknowledgement_timeout> <acknowledgement>Replace the above arguments with the values listed in Table 6-58 for the cnfsesack command.
Step 5
PXM1E_SJ.1.28.VISM8.a > cnfsesmaxreset <session_number> <resets>Replace <session_number> with the value you entered for the session_num argument in Step 4.
Replace <resets> with the maximum number of resets that the VISM card performs before a connection is reset. Range is 0-255. Default is 5.
Step 6
PXM1E_SJ.1.28.VISM8.a > cnfsesmaxseg <session_number> <segment_size>Replace <session_number> with the value you entered in Step 4.
Replace <segment_size> with the maximum segment size, in octets, that can be received by a VISM card after sending a synchronize message. Range is 30-65535.
Step 7
PXM1E_SJ.1.28.VISM8.a > cnfsesmaxwindow <session_number> <window_size>Replace <session_number> with the value you entered in Step 4.
Replace <window_size> with a value in the range 1-64.
Step 8
PXM1E_SJ.1.28.VISM8.a > cnfsesnullsegtmout <session_number> <timeout>Replace <session_number> with the value you entered in Step 4.
Replace <timeout> with the idle time before a null segment is sent. Range is 0-65535 ms. Default is 2000 ms.
Step 9
PXM1E_SJ.1.28.VISM8.a > cnfsesoutofseq <session_number> <packets>Replace <session_number> with the value you entered in Step 4.
Replace <packets> with the maximum number of out-of-sequence packets that can be accumulated before an EACK packet is transmitted. Range is 0-255.
Note
Step 10
PXM1E_SJ.1.28.VISM8.a > cnfsesport <session_number> <local_port> <remote_port>Replace the above arguments with the values listed in Table 6-59 for the cnfsesport command.
Table 6-59 Parameters for cnfsesport Command
session_number
Value you entered in Step 4.
local_port
Local port number. The VISM port number used for the session. Range is 1124-49151.
remote_port
Remote port number. The call agent port number used for the session. Range is 1124-65535.
Step 11
PXM1E_SJ.1.28.VISM8.a > cnfsesretrans <session_number> <retransmit_timeout> <max_retransmits>Replace the above arguments with the values listed in Table 6-60 for the cnfsesretrans command.
Table 6-60 Parameters for cnfsesretrans Command
session_number
Value you entered in Step 4.
retransmit_timeout
Timeout period (defined in milliseconds) to send an acknowledgment. Range is 100-65535 ms. Default is 600 ms.
max_retransmits
Maximum number of retransmissions. Range is 0-255. Default is 3.
Step 12
PXM1E_SJ.1.28.VISM8.a > cnfsesstatetmout <session_number> <timeout>Replace <session_number> with the value you entered in Step 4.
Replace <timeout> with the maximum number of milliseconds that VISM waits for a transfer state before executing an auto reset. Range is 0-65535. Default is 2000.
Step 13
PXM1E_SJ.1.28.VISM8.a > cnfsessyncatmps <session_number> <sync_attempts>Replace <session_number> with the value you entered in Step 4.
Replace <sync_attempts> with the maximum number of attempts to synchronize with the call agent. Range is 1-32. Default is 5.
Step 14
You have completed configuring ISDN PRI backhaul.
The basic configuration of your VISM cards is complete. Use the configuration instructions in this chapter to reconfigure VISM for your application needs as they change. Use the commands described in Chapter 7, "CLI Commands," to further configure your VISM cards, if necessary.
Additional VISM Features
The following features are available for users of VISM 3.2:
•
Note
•
•
–
–
–
Note
•
–
–
•
–
–
–
•
•
–
–
•
•
•
•
•
•
•
•
•
•
•
–
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Mid-Call DTMF
The mid-call dual tone multifrequency (DTMF) feature enables the collection and notification of digits to the call agent following a call setup for an endpoint, and supports the out-pulsing of DTMF digits at a call agent's request. This feature is used for services that require two stage dialing, such as calling card applications.
Mid-call DTMF is supported for all the CAS variants, for DTMF mode only.
Configurable Jitter Buffer
The configurable jitter buffer feature provides configuration of jitter buffer mode and initial delay time on a codec basis. Fax, modem, and CCD calls have less packet loss with the addition of this feature.
Adjustable Gain
The adjustable gain feature allows you to adjust gain on a DS0 channel basis for both input and output signals. The adjustable gain can be set when there is active call going on at the DS0 channel, and at both bounded non-active and unbounded endpoints.
Adjustable Music On-Hold Threshold
The adjustable music on-hold threshold feature allows you to adjust the dB level, on a DS0 basis, of when DSPs interpret TDM side silence or voice.
CALEA
The Commission on Accreditation for Law Enforcement Act (CALEA) feature, used with VoIP applications, provides data (eavesdropping) about an intercepted subject (the user/subscriber) in two forms for both the receive and transmit directions:
•
•
The call identifying data (called number) is provided by call agents. The call content data (voice) is provided by the edge/access routers (7200, for example) and trunking gateways (MGX 8000 series platforms) in combination with VISM cards.
The VISM CALEA implementation supports the CALEA law intercept confirmation interface.
MGC Redundancy
The media gateway controller (MGC) redundancy feature provides redundancy for call agents on VI SM cards. You can associate one or more call agents as members of a redundancy group.
An MGC redundancy group consists of one or more MGCs (which are identified by their domain name). An MGC can be part of one redundancy group, although there can be multiple MGCs per redundancy group. At any given time, only one MGC in the redundant group is active.
This feature requires you to add more than one domain name and configure these as redundant call agents or the same logical MGC. Only the IP addresses corresponding to each physical entity are returned by the DNS server. In order to allow VISMs to traverse all the IP addresses, you must identify these physical entities as redundant call agents.
External DNS
The external domain name server (DNS) feature allows VISM to use an external DNS to resolve the IP address you configure. The domain names can be MGCs, call agents, or trivial file transfer protocol (TFTP) servers used for CAS file downloads. Resolution of IP addresses can be configured with the following methods:
•
•
•
•
2 IP Address Support
The 2 IP address allows you to add separate IP addresses for the control and data paths for VISM. This feature removes the restriction of control and data traffic going to two different domains.
VoIP Trunking
The Voice over IP (VoIP) trunking feature allows the VISM to connect to the PBX, or central office digital systems, using T1/E1 digital interfaces and converts the TDM bit stream into RTP packets, after ECAN and compression, and transports it over the IP network.
No call agent is required for setting up and tearing down calls. You must configure the DS0 circuits. The connection between VISM and the first router will be ATM after which it will be IP only. VISM and the router can have one or multiple PVCs to transport the data. You have the option to configure PVC for bearer or control. If the PVC is configured as bearer and no control PVC exists, then PRI signal traffic and bearer traffic will go through this PVC. If you configure separate PVCs for control and bearer, PRI signaling will go through control traffic only. You can modify some of the connection parameters after it is added.
CAS is transported to the far end using a Cisco proprietary format (not NSEs). PRI is transported over RUDP to the far end once the trunk is provisioned between the originating and terminating VISM.
PRI transport is handled in a way identical to PRI backhaul except that the PRI traffic is sent to remote gateway instead of a call agent. You can configure one line for PRI trunking and another line for PRI backhauling.
You must provision the LAPD trunk when using this feature. You must configure a line number, remote gateway IP address, local UDP port, and remote gateway UDP port, and then open a trunk. You must then configure the D-channel as a trunk or backhaul:
•
Note
•
T.38 Fax Relay
The ITU T.38 recommendation for fax relay feature assists fax transmission over IP networks. You must configure T.38 parameters—fax rate, information field size, data packet size, data redundancy, and NSF values—to use this feature.
Note
CAS Features
You can configure different CAS packages on different endpoints. The following CAS features are supported in this release.
Programmable Tone Plans
You can provision a tone plan in a CAS independent scenario so that any inband call progress tone can be played on any endpoint (CAS, CCS, or clear channel) when signaled by the call agent.
Table 6-61 contains the built-in (preconfigured) version 1 tone plans, which you cannot modify or remove from the system.
Table 6-61 Built-in (Preconfigured) Tone Plans
ITU1
Finland
Japan
Singapore
North America
France
Korea Republic
Slovakia
Argentina
Germany
Luxembourg
Slovenia
Australia
Greece
Malaysia
South Africa
Austria
Hong Kong
Mexico
Spain
Belgium
Hungary
Netherlands
Sweden
Brazil
Iceland
New Zealand
Switzerland
Canada
India
Norway
Taiwan
China
Indonesia
Philippines
Thailand
Cyprus
Ireland
Poland
Turkey
Czech Republic
Israel
Portugal
United Kingdom
Denmark
Italy
Russia
United States
1 ITU = International Telecommunications Union (formerly CCITT).
You can configure provisional tone plans if the built-in tone plans do not meet your application needs. Provisional tone plans are created by assigning new region/country, version, and file names, and configuring the following call progress tones:
•
•
•
•
•
•
Loop Start, DID, and Delay Dial
The exchange side (FXO) of the loop start protocol is implemented with this release. VISM can accept calls from, and terminate calls to, loop start PBXs. When a PBX sends a subscriber call to the gateway, it sends the loop close signal through the CAS signaling channel. To hang up, it sends the loop-open signal.
Direct inward dial enables a caller outside a company to call internal extensions without having to go through an operator or an attendant. VISM has this ability—it outpulses the digit stream handed down by the call agent.
Dial delay is an E&M signaling protocol similar to wink start. The originating VISM, on receiving a seize (AB=11) from the PBX, responds by sending the delay-dial (AB=11) signal back to the PBX. When the originating VISM is ready to collect the digits, it sends start-dial (AB=00) signal. This operation is symmetric. So the terminating VISM, on seizing a trunk, should receive AB=11 (as an acknowledgment that the trunk is operational). Subsequently when it receives the start signal (AB=00) from the connected PBX, it should outpulse the digits. The rest of the operation is similar to wink-start.
Feature Group D
Feature Group D (FGD) enables long distance calls through one of the following methods:
•
•
FGD supports the following protocols:
•
•
•
Configure Flash Hook and Glare Condition Attributes
You can configure both flash hook and glare condition attributes. Flash hook configuration allows you to modify the duration of a flash hook. Duration shorter or longer than that configured are interpreted as incoming calls and disconnects. Glare condition attribute configuration allows you to control the CAS direction—incoming, outgoing, or bidirectional—and the glare handling policy—controlling or releasing.
Configure ANI and DNIS Digit Order
You can configure the order in which a call agent sends automatic number identification (ANI) digits—the caller's number—and dial number identification service (DNIS) digits—the called number—to VISM during an outgoing Feature Group D (FGD) call for the endpoints of a specified VISM card line.
RFC 3064 Package Support
This release fully supports the following packages from RFC 3064:
•
•
•
•
•
RFC 2833 Support
Support for RFC 2833 enables VISM to support DTMF relay using named telephony events (NTEs), named signaling event (NSE) based relay, and Cisco-RTP based relay. For all other tones, VISM uses NSEs.
VISM Network Continuity Test
You can configure VISM network continuity testing with this release.
Configure PVC OAM Cell Parameters
This feature allows you to configure the transmitted and received permanent virtual circuit (PVC) Operations, Administration, and Maintenance (OAM) cell parameters—cell gap, recovery cell count, and unacknowledged cell count.
PXM1E and PXM45 Card-Only Features
You can use the VISM-PR card in combination with any of the following MGX 8000 Series switch Processor Module cards:
•
•
•
Table 6-62 describes the configuration requirements for VISM/VISM-PR in combination with the MGX 8000 Series switches and supported processor modules.
For information on installing and maintaining the PXM1, PXM1E, and PXM45 cards, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide Release 2 through 4.
Note
The VISM-PR card supports 144 channels when used with the G.723.1 codec. The VISM card does not support the G.723.1 codec.
The following VISM-PR features require either the PXM1E or PXM45 card and are not supported if you are using PXM1 cards in your MGX 8000 Series switch chassis:
•
•
•
Note
•
•
Call Agent-Controlled VoATM AAL1 and AAL2 SVC
The following operating modes are supported with software Release 3.2 for VISM/VISM-PR:
•
Note
•
Note
Use the cnfvismmode command to configure VISM operating modes.
Note
AAL1 SVC-Based TDM Hairpinning
VoAAL1 switched virtual circuit (SVC) operating mode is supported with the G.711 codec and clear channel. The AAL1 SVC operating mode supports TDM hairpinning.
Note
Use the cnfvismmode command to configure VISM operating modes.
Note
High Complexity Codec Support for VISM-PR—G.723.1
The VISM-PR card supports high complexity codec G.723.1 in template number 4. Template number 4 supports all the codecs in template number 3 and the following:
•
•
•
•
The G.723.1 codec, used in combination with the VISM-PR card, supports 144 channels. Refer to Table 6-8 for a description of VISM-PR DS0 density when the cards are used in combination with supported codecs.
Several CLI commands have been modified to allow you to use the G.723.1 codec and template number 4.
Note
Announcement File System
This release allows VISM to play prerecorded local announcements in switched VoIP connections. Under the control of a call agent, announcements can be played toward any IP endpoint or toward any VISM endpoint.
Up to 125 different announcements may be cached on the VISM card for immediate playout. A persistent announcement storage area exists in the packet network. Announcements are downloaded on demand from the announcement storage area and remain on the VISM card until they have reached expiry or are replaced. If the 125 announcement maximum is reached, subsequent requests for announcements not on the VISM card result in the replacement of "cached" announcements.
Announcements can be played over established connections in any VISM supported codec, but they must exist on the announcement file server in the desired encoding.
Note
VISM announcements require the support of the MGCP 0.1/1.0 call agent.
Announcement Timeouts
VISM uses a provisionable timeout value of 5 seconds. If an announcement cannot start playing within the timeout value of receiving the request, the action is canceled and, if requested by the call agent, an "of" event is reported. If the call agent specifies a timeout value in the request, this value will be ignored.
Announcement Direction
Announcements can be played toward the packet network or toward the TDM network (not both). The direction is determined by the notation of the MGCP S: line. Announcement direction examples:
S: a/ann(all-lines-busy.au)Explanation Indicates that all-lines-busy.au is to be played toward the TDM network.
S: a/ann@connid(all-lines-busy.au)Explanation Indicates that all-lines-busy.au is to be played toward the packet network.
Broadcast Announcements
VISM supports announcement requests for a single endpoint or connection. The request may only specify a single announcement to be played on a single endpoint in a single direction. Broadcast announcements are not supported.
Multiple Announcement Requests for the Same Endpoint
If an announcement is being played on an endpoint (in one direction) and a subsequent announcement request is received for the same endpoint (in the same direction), the playing announcement will continue and the new announcement request is ignored.
If an announcement is being played on an endpoint (in one direction) and a subsequent announcement request is received for the same endpoint (in the other direction), the playing announcement is stopped and the new announcement is then played. Events are not generated for the stopped announcement.
Announcement File Server
Announcements are contained in an announcement file server, which resides on an IP network reachable from the VISM using Trivial File Transfer Protocol (TFTP).
Announcement File Server Name
You can configure the announcement file server node name on the VISM the same way that you configure a node name for the TFTP server.
Announcement File Server Directory Structure
You may use any directory or path on the file server as the main directory for storing announcement files. If you do not provision an announcement path prefix on VISM, the main announcement file directory is the default TFTP directory on the server. If a path prefix is provisioned, this prefix is used as the main announcement directory. If the prefix is not absolute (does not begin with a forward slash (/)), the prefix is relative to the default TFTP directory.
You can configure codec subdirectories under the main announcement directory on the announcement file server. A codec subdirectory exists for each codec used for announcement files.The subdirectories may be one or more of the following:
•
•
•
•
•
•
•
•
•
•
When the call agent requests that an announcement is to be played toward the TDM network on an unconnected endpoint, you can specify the codec to be used.
Another level of directories might be configured to group announcement files by language. These directories would be specified by the call agent (or when provisioning the VISM) as part of the announcement file name. For example, the call agent might specify the announcement file name to be english/ann1.au. If the file was encoded in G.729a and the prefix was /tftpboot, the file would reside at /tftpboot/g729_a/english/ann1.au.
VISM Announcement Cache Management
VISM maintains an announcement cache in resident memory. When an announcement is requested to be played, it is retrieved from the announcement file server and placed in the on-board announcement cache. Subsequent requests for the same announcement do not require retrieval of the announcement file from the announcement file server.
Note
Announcement Expiry
You can provision an announcement aging policy. Once an announcement has aged (reached expiry) in the on-board cache, it is refreshed—retrieved again from the announcement file server. This provides you with the means to balance the cost of file server access with the time before an announcement changed on the file server is propagated to the VISM. In addition, you can delete dynamic files from the announcement cache at any time.
Permanent Announcements
You can provision permanent announcements for VISM. A permanent announcement is retrieved from the announcement file server and installed permanently in the VISM announcement file cache. Permanent announcements are excluded from aging (and being automatically refreshed) and excluded from being replaced if the announcement cache becomes full. Permanent announcements can only be removed from the cache explicitly by using a CLI command. If VISM is reset or fails over to a standby card, permanent announcements are retrieved as soon as the card becomes active. The announcement encoding must be specified when provisioning or deleting permanent announcements.
Use the CLI commands in Table 6-63 to configure the announcement file system feature.
Call Agent-Controlled T.38 Fax
The call agent-controlled T.38 fax feature is an additional operational mode for MGCP 1.0 to request T.38. This addition allows VISM to interoperate with H.323 and non-Cisco gateways, and is supported for VoIP calls. This feature is activated based on the fax tone and signaling carried with the call agent. The modified cnft38fxlco command allows you to configure the local connection option fax preamble response to off. All previous options are valid.
Additional Support for MGCP 1.0
This release supports the following MGCP 1.0 features:
•
–
–
–
•
–
–
–
–
–
–
–
Use the CLI commands in Table 6-64 to configure the MGCP 1.0 feature.
RSVP-Based Admission Control
Resource Reservation Protocol (RSVP)-based admission control signaling with MGCP is supported, which allows for quality VoIP connections. For the connections, the RSVP-MGCP interaction results in the following:
•
•
•
•
Note
In previous releases of VISM software, the following connection data is returned in response to the call agent initiated DLCX, and gateway initiated DLCX or AUCX commands:
•
•
•
•
VISM Release 3.2 provides the following additional connection data:
•
•
Note
•
Use the commands in Table 6-65 to configure the RSVP-based admission control feature.
Clock Slip Counters
The clock counter information feature allows you to clear the current frame slip counters for a specified VISM or VISM-PR card line and display the current frame slip counters for a specified VISM or VISM-PR card line. Use the new clrslipcnt and dspslipcnt to use this feature.
RTP Connection Statistics
Real-Time Transport Protocol (RTP) connection statistics are collected for individual endpoints and sent to the call agent. Use the new dsprtpconnstat command to display collected RTP connection statistics.
Jitter delay data collection at call completion is on a per call basis. Jitter delay data and number of packets sent and received, and number of octets sent and received, are reported to the call agent through MGCP.
CAS Immediate Start and Ground Start Glare Handling
CAS Immediate Start—The CAS variants immediate start and immediate start, multifrequency are supported. Use the addcasvar command to configure CAS variants.
Note
Ground Start Glare Handling—This release supports CAS glare condition handling according to RFC 3064. The VISM sends a NACK message in response to the call agent's request for ringing with error code 401 (off hook) in the event of a glare condition.
On receiving the request for ringing from call control, CAS transmits a seize signal to the PBX and starts the glare timer, returning a provisional response code to call control indicating that CAS is still processing the request. If the timer expires (normal case) or an incoming seizure is observed on the endpoint, CAS generates an asynchronous response code to call control that is comparable to an MGCP response code of 200 or 401, respectively.
Grooming for Local Traffic
VISM supports the call agent controlled grooming feature. Grooming allows VISM to avoid routing local traffic through the IP network. Voice packets from a local connection are switched locally in the ATM switch.
A call agent determines if a call needs to be setup as local. To set up a local call, the call agent selects an ATM connection over a VoIP connection. The VISM card, as a gateway, receives the connection request message from the call agent for an ATM connection. The VISM card allows VoIP calls and VoAAL1 SVC calls to coexist and allows provisioning of VoIP and ATM simultaneously.
To achieve this, VISM uses VoIP and Switched ATM AAL1 SVC as local switching mode. VISM receives an ATM AAL1 SVC call setup request from the call agent for local calls.
You must use the cnfvismmode command and select the VoIP and switched ATM AAL1 SVC operating mode to use the grooming feature. Using this mode does not change any other settings on your card. The type of connection for a call is determined by the connection request (CRCX) from the call agent or by the bearer type configuration.
MGX 8000 Series Implementation Features
The following features are supported with this release with implementation of your MGX 8000 Series switch:
•
•
•
•
•
Additional VBR Enhancements
Setting connections between a VISM-PR card and a RPM-PR card in your MGX 8000 Series switch chassis requires you to use the new VBR (NRT) 3 connection type. Use the modified addcon or cnfcon commands to configure this connection type. In addition, the following new connection service types can be configured with the modified commands in this release:
•
•
•
Expanded Clock Source Selection
This release supports an expanded clock source selection, which allows you to configure any VISM-PR card line as the clock source. You cannot delete a VISM-PR line that is configured as the clock source; you must configure a different line as the clock source and then you can delete the original clock source line. The previously released CLI commands allow you to use this feature.
Note
Private Network-to-Network Interface Priority Routing
This release supports the Private Network-to-Network Interface (PNNI) routing priority feature. This feature allows you to specify connections with a routing priority. The PNNI controller uses your configuration selections to route the higher priority connections before routing the lower priority connections. Use the cnfpncon command to configure a routing priority for a specified connection.
Note
Additional SPVC Connection Management Capabilities
Use the Processor Module 1E card (PXM1E) or the PXM 45 card in combination with the VISM-PR card in an MGX 8000 Series switch chassis to specify a connection up or down. Specifying a connection up allows you to direct traffic to the specified connection. Specifying a connection down allows you to prevent traffic from being directed to a specified connection. Use the upcon and dncon commands to use this feature.
Note
192 T1/248 E1 DS0 Support with High Complexity Codecs on VISM-PR
VISM-PR T1 lines support up to 192 DS0 channels and VISM-PR E1 lines support up to 248 DS0 channels, with clear channel and the following codec types:
•
•
•
•
Table 6-66 describes the VISM/VISM-PR DS0 density when the cards are used in combination with clear channel and the supported codecs.
Channel Alarm Enhancement
The channel alarm enhancement feature uses the modified dspconcnt command, which allows you to view the channel status bit map data.
VISM TDM Line Statistics Collection
This release allows you to configure VISM to collect Time Division Multiplex (TDM) line statistics. Use the dspalmcnt command to collect and display TDM line statistics. Use the cnfalmcnt command to configure the thresholds for TDM line statistics.
Posted: Thu Jun 10 16:51:38 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
