|
|
Table Of Contents
Release Notes for Cisco Voice Interworking Service Module Release 3.0(0)
Hardware Introduced in Software Release 3.0(0) for VISM/VISM-PR
Software Features Introduced in Software Release 3.0(0) for VISM/VISM-PR
VISM Management Information Base
Software Release 3.0(0) for VISM/VISM-PR CLI Commands
Installation and Upgrade Procedures
VISM to VISM-PR Upgrade Procedure
VISM Firmware Download Procedure for PXM1
VISM Firmware Download Procedure for PXM1E and PXM45
Installing VISM Software Updates with PXM1 Cards
Installing VISM Software Updates with PXM1E or PXM45 Cards
VISM Boot Code Upgrade Procedure with PXM1 Cards
VISM Boot Code Upgrade Procedure with PXM1E and PXM45 Cards
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco Voice Interworking Service Module Release 3.0(0)
These release notes are part number OL-2523-01 Rev. B0, January 9, 2004.
The Cisco Voice Interworking Service Module (VISM) product is supported by MGX Voice Media Gateways. Refer to these release notes for Media Gateway and version level support guidelines.
The software Release 3.0(0) for VISM/VISM-PR is a major upgrade from the VISM Release 2.2(0). The new features in VISM Release 3.0(0) are described in the "VISM Features" section. The new, modified, and deprecated MIB objects and CLI commands are listed in the "Important Notes" section.
The software Release 3.0(0) for VISM/VISM-PR is supported by the Cisco VISM Installation and Configuration Guide Release 3.0, which is available on cisco.com
Contents
These release notes contain the following sections:
•
"Installation and Upgrade Procedures" section
•
•
•
•
•
VISM Features
This section describes the new hardware and the new software features introduced in software Release 3.0(0) for VISM/VISM-PR.
Hardware Introduced in Software Release 3.0(0) for VISM/VISM-PR
Software Release 3.0(0) for VISM/VISM-PR introduces a new card—VISM-PR. You can use the VISM-PR card in combination with any of the following MGX 8000 Series switch Processor Module cards:
•
•
•
Table 1 describes the configuration requirements for VISM/VISM-PR in combination with the MGX 8000 Series switches and supported processor modules.
Refer to the Cisco MGX 8850 Hardware Installation Guide, Release 3 for information on installing and maintaining the PXM1, PXM1E, and PXM45 cards.
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 software Release 3.0(0) for VISM/VISM-PR features require either the PXM1E or PXM45 card and are not supported if you are using PXM1 cards in your MGX 8000 Series switch chassis:
•
•
•
Note
•
•
See the "Software Features Introduced in Software Release 3.0(0) for VISM/VISM-PR" section for more information on these features. Refer to the Cisco VISM Installation and Configuration Guide for more information on VISM and VISM-PR card installation procedures.
Software Features Introduced in Software Release 3.0(0) for VISM/VISM-PR
New and modified CLI commands allow you to use the following software Release 3.0(0) for VISM/VISM-PR features in their indicated application modes:
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
–
–
–
–
Note
Call Agent-Controlled VoATM AAL1 and AAL2 SVC
The following operating modes are supported with software Release 3.0(0) 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 high complexity codec G.723.1 is introduced with this release. The VISM-PR card supports this codec in the newly introduced 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 2 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. See Table 4 for a complete list of modified commands for this release.
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 following new CLI commands 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 expands the support for the Media Gateway Control Protocol (MGCP) 1.0, which was introduced in VISM 2.2. The following are implemented for the MGCP 1.0 feature support:
•
–
–
–
•
–
–
–
–
–
–
–
Use the following new CLI commands to configure the MGCP 1.0 feature:
•
•
Use the following new CLI command to display the MGCP 1.0 feature:
•
You can also use the following modified commands to configure the MGCP 1.0 feature:
•
•
•
RSVP-Based Admission Control
This release introduces Resource Reservation Protocol (RSVP)-based admission control signaling with MGCP to allow 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.0(0) provides the following additional connection data:
•
•
Note
•
Use the following new commands to configure the RSVP-based admission control feature:
•
•
See Table 3 for a complete list of new commands introduced with this release.
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—This release supports the CAS variants immediate start and immediate start, multifrequency. 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
This release of VISM supports the grooming feature controlled by the call agent. 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 set up as local. To set up a local call, the call agent selects an ATM connection over a VoIP connection. The VISM card, as a gateway, receives the connection request message from the call agent for an ATM connection. The VISM card allows VoIP calls and VoAAL1 SVC calls to coexist and allows provisioning of VoIP and ATM simultaneously.
To achieve this, VISM uses VoIP and Switched ATM AAL1 SVC as local switching mode. VISM receives an ATM AAL1 SVC call setup request from the call agent for local calls.
You must use the cnfvismmode command and select the VoIP and switched ATM AAL1 SVC operating mode to use the grooming feature. Using this mode does not change any other settings on your card. The type of connection for a call is determined by the connection request (CRCX) from the call agent or by the bearer type configuration.
MGX 8000 Series Implementation Enhancements
The following enhancements are supported with this release with additional implementation of your MGX 8000 Series switch:
•
•
•
•
•
Additional VBR Enhancements
Setting connections between a VISM-PR card and an 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
An expanded clock source selection 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
The Private Network-to-Network Interface (PNNI) routing priority 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 PXM45 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 2 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
You can 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.
Important Notes
This section describes the following elements of software Release 3.0(0) for VISM/VISM-PR:
•
•
•
VISM Management Information Base
The VISM Management Information Base (MIB) Version 0.0.30 is provided with the delivery of software Release 3.0(0) for VISM/VISM-PR, which bundles with the Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 software and is located on the Web at the following location:
http://www.cisco.com/kobayashi/sw-center/beta/
When the selected FW *.tar file or FW*.zip file is downloaded, untar or unzip the file and you will find all the latest MIBs bundled with this release.
The MIB is in standard ASN.1 form and can be compiled with most standards-based MIB compilers. Refer to the MIB release notes on CCO.
MIB Changes for Software Release 3.0(0) for VISM/VISM-PR
This section describes new, modified, and deprecated MIB objects, and new and modified traps for software Release 3.0(0) for VISM/VISM-PR.
New MIB Objects
The following MIB objects are added for software Release 3.0(0) for VISM/VISM-PR:
•
–
–
–
–
–
–
•
–
–
–
–
–
•
–
–
–
–
•
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
•
–
–
–
–
–
–
–
•
–
–
–
•
–
•
–
Modified MIB Objects
The following MIB objects are modified for software Release 3.0(0) for VISM/VISM-PR:
•
–
•
–
•
–
–
•
–
•
–
–
–
–
–
–
•
–
–
–
•
–
–
–
•
–
–
•
–
•
–
–
–
–
–
•
–
–
•
–
•
–
•
–
–
–
•
–
–
–
–
•
–
•
–
•
–
•
–
•
–
•
–
•
–
–
•
–
–
•
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
–
–
–
–
–
–
–
•
–
•
–
•
–
–
•
–
–
•
–
•
–
•
–
•
–
–
•
–
–
•
–
–
•
–
–
•
–
Deprecated MIB Objects
The following MIB objects are deprecated from software Release 3.0(0) for VISM/VISM-PR:
•
–
–
New Traps
The following traps are added for software Release 3.0(0) for VISM/VISM-PR:
•
Uses varbind: vismTrapIntIndex1, cwAnnFileName, cwAnnFileCodec, and cwAnnFileStatus
•
Uses varbind: vismTrapIntIndex1, cwAnnFileName, cwAnnFileCodec, and cwAnnFileStatus
•
Uses varbind: vismTrapIntIndex1, cwAnnFileName, cwAnnFileCodec, and cwAnnFileStatus
•
Uses Added varbind: vismTrapIntIndex1
•
Uses varbind: intSrvFlowStatus, svpSessionDestAddr, rsvpResvFwdStatus, rsvpResvStatus, rsvpSenderStatus
•
Uses varbind: intSrvFlowStatus, svpSessionDestAddr, rsvpResvFwdStatus, rsvpResvStatus, rsvpSenderStatus
•
Uses varbind: vismTrapIntIndex1
•
Uses varbind: vismTrapIntIndex1
•
Uses varbind: vismTrapIntIndex1
•
Uses Added varbind: vismTrapIntIndex1
•
First time using an existing trap. Added varbind: vismChanStatusBitMap. Uses varbind: genericLineNum, vismCnfChanNum, vismChanRowStatus, and vismChanStatusBitMap.
Modified Traps
The following traps are modified for software Release 3.0(0) for VISM/VISM-PR:
•
Added varbind: vismRtpLcn
•
Added varbind: vismRtpLcn
•
Added varbind: vismRtpLcn and vismRtpFailReason
•
Added varbind: vismAal2CidFailReason
•
First time using an existing trap. Added varbind: vismChanStatusBitMap. Uses varbind: genericLineNum, vismCnfChanNum, vismChanPortNum, and vismChanStatusBitMap.
•
