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.
VISM Features 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.
VISM Features • Private Network-to-Network Interface Priority Routing • Additional SPVC Connection Management Capabilities See the “Software Features Introduced in Software Release 3.0(0) for VISM/VISM-PR” section on page 3 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.
VISM Features Call Agent-Controlled VoATM AAL1 and AAL2 SVC The following operating modes are supported with software Release 3.0(0) for VISM/VISM-PR: • VoAAL1 switched virtual circuit (SVC), supported with the G.711 codec and clear channel. Note • Note VAD is not supported in combination with AAL1 SVCs. VoAAL2 SVC, supported with the G.711, G.726, G.729a, G.729ab, and G723 codecs and ITU profiles 1, 2, 3, 7, 8, and custom profiles 100, 101, 110, and 200.
VISM Features 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 The G.723.1 codecs are not supported for VISM cards. Announcement File System This release allows VISM to play prerecorded local announcements in switched VoIP connections. Under the control of a call agent, announcements can be played toward any IP endpoint or toward any VISM endpoint.
VISM Features 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.
VISM Features VISM Announcement Cache Management VISM maintains an announcement cache in resident memory. When an announcement is requested to be played, it is retrieved from the announcement file server and placed in the on-board announcement cache. Subsequent requests for the same announcement do not require retrieval of the announcement file from the announcement file server. Note An announcement in one encoding is a different file than the same announcement in a different encoding.
VISM Features • dspannprefcodec • dspannreqtimeout 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.
VISM Features 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 • Establish or originate unidirectional resource reservation for sending voice packets for connections established and controlled by MGCP.
VISM Features 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.
VISM Features 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 • Expanded Clock Source Selection • Private Network-to-Network Interface Priority Routing • Additional SPVC Connection Management Capabilities • 192 T1/248 E1 DS0 Support with High Complexity Codecs on VISM-PR • Channel Alarm Enhancement • VISM TDM Line Statistics Collection Additional
VISM Features 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.
Important Notes Important Notes This section describes the following elements of software Release 3.0(0) for VISM/VISM-PR: • “VISM Management Information Base” section on page 13 • “Software Release 3.
Important Notes – cwAnnFileCodec – cwAnnRowStatus • MIB objects contained in rsvpGenObjects: – rsvpSessionNewIndex – rsvpBadPackets – rsvpResvNewIndex – rsvpResvFwdNewIndex • MIB objects contained in rsvpSessionTable: – rsvpSessionNumber – rsvpSessionType – rsvpSessionDestAddr – rsvpSessionDestAddrLength – rsvpSessionProtocol – rsvpSessionPort – rsvpSessionSenders – rsvpSessionReceivers – rsvpSessionRequests • MIB objects contained in rsvpSenderTable: – rsvpSenderNumber – rsvpSenderType – rsvpSenderDe
Important Notes – rsvpSenderLastChange – rsvpSenderPolicy – rsvpSenderAdspecBreak – rsvpSenderAdspecHopCount – rsvpSenderAdspecPathBw – rsvpSenderAdspecMinLatency – rsvpSenderAdspecMtu – rsvpSenderAdspecGuaranteedSvc – rsvpSenderAdspecGuaranteedBreak – rsvpSenderAdspecGuaranteedCtot – rsvpSenderAdspecGuaranteedDtot – rsvpSenderAdspecGuaranteedCsum – rsvpSenderAdspecGuaranteedDsum – rsvpSenderAdspecGuaranteedHopCount – rsvpSenderAdspecGuaranteedPathBw – rsvpSenderAdspecGuaranteedMinLatency – rsvpSenderAdspe
Important Notes – rsvpResvHopLih – rsvpResvInterface – rsvpResvService – rsvpResvTSpecRate – rsvpResvTSpecPeakRate – rsvpResvTSpecBurst – rsvpResvTSpecMinTU – rsvpResvTSpecMaxTU – rsvpResvRSpecRate – rsvpResvRSpecSlack – rsvpResvInterval – rsvpResvScope – rsvpResvShared – rsvpResvExplicit – rsvpResvRSVPHop – rsvpResvLastChange – rsvpResvPolicy – rsvpResvStatus – rsvpResvTTL – rsvpResvFlowId • MIB objects contained in rsvpResvFwdTable: – rsvpResvFwdNumber – rsvpResvFwdType – rsvpResvFwdDestAddr – rsvpResvF
Important Notes – rsvpResvFwdTSpecMaxTU – rsvpResvFwdRSpecRate – rsvpResvFwdRSpecSlack – rsvpResvFwdInterval – rsvpResvFwdScope – rsvpResvFwdShared – rsvpResvFwdExplicit – rsvpResvFwdRSVPHop – rsvpResvFwdLastChange – rsvpResvFwdPolicy – rsvpResvFwdStatus – rsvpResvFwdTTL – rsvpResvFwdFlowId • MIB objects contained in rsvpIfTable: – rsvpIfUdpNbrs – rsvpIfIpNbrs – rsvpIfNbrs – rsvpIfEnabled – rsvpIfUdpRequired – rsvpIfRefreshBlockadeMultiple – rsvpIfRefreshMultiple – rsvpIfTTL – rsvpIfRefreshInterval – rsvp
Important Notes • MIB objects contained in vismXgcpEnhancementObjects: – vismXgcpRestartInProgressTdinit – vismXgcpRestartInProgressTdmin – vismXgcpRestartInProgressTdmax • MIB object contained in vismChanApplication: – vismConnAdminStatus • MIB object contained in vismChanStateGrpTable: – vismChanStatusBitMap Modified MIB Objects The following MIB objects are modified for software Release 3.
Important Notes • MIB object modified in vismAal2CidCnfTable: – vismAal2CidCodecType • MIB objects modified in aal2ProfilesGrpTable: – aal2ProfileType – aal2ProfileNumber – aal2ProfilePreference – aal2ProfileVoiceCodec – aal2ProfileVoiceVAD • MIB objects modified in vismRtpConnGrpTable: – vismRtpLcn – vismRtpFailReason • MIB object modified in vismAal2CidCnfTable: – vismAal2CidFailReason • MIB object modified in vismTrapObjGrp: – vismConfigChangeTypeBitMap • MIB objects modified in vismAal2CidCn
Important Notes • MIB objects modified in vismTonePlanTable: – tonePlanEntryStatus – tonePlanProvisionFlag • MIB objects modified in t38FaxRelayGrpTable: – t38FxLCO – t38Redundancy • MIB objects modified in inFlow: – lastSequenceNumber – shelfNodeName – shelfNum – moduleSlotNumber – moduleTrapAlarmSeverity – functionModuleType – genericTimeStamp – intSrvFlowStatus – rsvpSessionDestAddr – rsvpResvFwdStatus – rsvpResvStatus – rsvpSenderStatus • MIB objects modified in lostFlow: – lastSequenceNumber –
Important Notes • MIB objects modified in ciscoWanVismSrcpCapabilityV2R00: – srcpConfigurationGroup3 – srcpStatisticsGroup2 • MIB objects modified in ciscoWanVismSrcpCapabilityV2R0: – srcpConfigurationGroup3 – srcpStatisticsGroup2 • MIB object modified in the file vismCardSpecific.
Important Notes • cwAnnFileLoadComplete Uses varbind: vismTrapIntIndex1, cwAnnFileName, cwAnnFileCodec, and cwAnnFileStatus • cwAnnFileLoadFailed Uses varbind: vismTrapIntIndex1, cwAnnFileName, cwAnnFileCodec, and cwAnnFileStatus • cwAnnFileDeleted Uses Added varbind: vismTrapIntIndex1 • newFlow Uses varbind: intSrvFlowStatus, svpSessionDestAddr, rsvpResvFwdStatus, rsvpResvStatus, rsvpSenderStatus • lostFlow Uses varbind: intSrvFlowStatus, svpSessionDestAddr, rsvpResvFwdStatus, rsvpResvStatus, rsv
Important Notes • trapVismChanFailed First time using an existing trap. Added varbind: vismChanStatusBitMap. Uses varbind: genericLineNum, vismCnfChanNum, vismChanPortNum, and vismChanStatusBitMap. • trapVismConUp First time using an existing trap. Added varbind: vismChanStatusBitMap. Uses varbind: genericLineNum, vismCnfChanNum, vismChanRowStatus, and vismChanStatusBitMap. Software Release 3.0(0) for VISM/VISM-PR CLI Commands Software Release 3.
Important Notes Table 3 New CLI Commands for Software Release 3.0(0) for VISM/VISM-PR (continued) Command Description delannpermanent Deletes a permanent announcement file and its associated codec type from the announcement file server. dncon Configures a specified connection down, preventing traffic from being passed to it. dspannagetime Displays the time that a nonpermanent announcement is to remain valid after it is placed into the VISM announcement cache.
Important Notes Table 4 describes the modified CLI commands contained in software Release 3.0(0) for VISM/VISM-PR. Table 4 Modified CLI Commands for Software Release 3.0(0) for VISM/VISM-PR Command Name addcid Adds an AAL2 CID on a VISM card. addcon Adds a PVC connection between a VISM card and any SM or PXM card. addendpt Adds an endpoint on a VISM card. addendptloop Places an endpoint in a loopback condition in the TDM direction.
Important Notes Table 4 Modified CLI Commands for Software Release 3.0(0) for VISM/VISM-PR (continued) Command Name cnfjtrinitdelay Configures the jitter buffer size. cnfpncon Sets priority routing for a specified connection. cnfprofelemvbd Configures the VBD profile element for a profile. cnfprofelemvoice Configures the voice profile element for a profile. cnfprofparams Configures a profile preference. cnfrtpcon Modifies an existing static RTP VoIP trunking connection.
Important Notes VISM Redundancy Table 5 lists the support level for 1:N Service Module Redundancy (N = 1 through 11). Table 5 Note Service Module Redundancy Front Card Model Number Redundancy Support MGX-VISM-8T1 1:N redundancy (bulk mode support for T1 lines only). MGX-VISM-8E1 1:N redundancy (bulk mode support for E1 lines only). MGX-VISM-PR-8T1 1:N redundancy (bulk mode support for T1 lines only). MGX-VISM-PR-8E1 1:N redundancy (bulk mode support for E1 lines only).
Important Notes Table 6 VISM Software Interoperability (continued) Product CW2000 Name Latest Firmware Min. Firmware AXSM-16-T3/E3 AXSM-16-T3/E3 3.0.0 3.0.0 AXSM-16-T3/E3/B AXSM-16-T3/E3/B 3.0.0 3.0.0 AXSM-16-T3E3-E AXSM-16-T3E3-E 3.0.0 3.0.0 AXSM-2-622-E AXSM-2-622-E 3.0.0 3.0.0 AXSM-32-T1E1-E AXSM-32-T1E1-E 3.0.0 3.0.0 AXSM-4-622 AXSM-4-622 3.0.0 3.0.0 AXSM-4-622/B AXSM-4-622/B 3.0.0 3.0.0 AXSM-8-155-E AXSM-8-155-E 3.0.0 3.0.0 BPX/IGX BPX/IGX 9.3.40 9.2.
Important Notes Table 6 VISM Software Interoperability (continued) Product CW2000 Name Latest Firmware Min. Firmware PXM45 3.0.0 3.0.0 RPM RPM 12.2(8)T4 12.2(8)T4 RPM IOS RPM IOS 12.2(8)T4 — RPM/B RPM/B 12.2(8)T4 12.2(8)T4 RPM-PR RPM-PR 12.2(8)T4 12.2(8)T4 SES SES 3.0.00 1.0.16 PXM45 2 1. CWM Release 10.4 does not support all of the new MIBs listed in the “VISM Management Information Base” section on page 13. 2. This card is not compatible with VISM cards.
Installation and Upgrade Procedures Note Loading this release of the backup bootcode is required for existing VISM cards not using this new release. Limitations and Restrictions The following limitations and restrictions are valid for software Release 3.0(0) for VISM/VISM-PR: • The switched AAL2 PVC operating mode is not supported for VISM Release 3.0(0). • Software Release 3.0(0) for VISM/VISM-PR requires you to use 64 Mb VISM cards or VISM-PR cards exclusively.
Installation and Upgrade Procedures VISM to VISM-PR Upgrade Procedure Software Release 3.0(0) for VISM/VISM-PR introduces the new VISM-PR card. Complete the following steps to gracefully upgrade from VISM cards to VISM-PR cards. You must ensure that the VISM and VISM-PR software versions are the same—ensure that you have the version with Commission on Accreditation for Law Enforcement Agencies (CALEA), if you use the CALEA feature. The following versions of VISM software Release 3.
Installation and Upgrade Procedures Step 4 Execute the PXM newrev command: newrev sm where: SM slot# is the slot number of the standby VISM-PR-1 card and new-rev is the filename of the new firmware. This command causes the VISM-PR-1 to become the active VISM running the new-rev firmware. The previously active VISM-PR-2 changes to a “standby” state and is still running the old-rev firmware. The primary and secondary firmware switches with the new-rev becoming the primary firmware.
Installation and Upgrade Procedures b. put POPEYE@SM_1_.FW quit Note Step 3 Do not enter two put commands in the same TFTP session. Proceed to the “Installing VISM Software Updates with PXM1 Cards” section on page 33 to install the download. VISM Firmware Download Procedure for PXM1E and PXM45 Step 1 Access the image on the Cisco Website in order to download the image.
Installation and Upgrade Procedures Initial Conditions The following initial conditions are required before the graceful upgrade procedure can be started: • The MGX 8000 Series shelf must be configured with at least two VISM cards in a redundant configuration (refer to the add redundancy, addred, command in the MGX 8850, MGX 8250, and MGX 8230 command references for more information). • The VISM cards must be running VISM 2.0 and be configured to the desired configuration. • The software Release 3.
Installation and Upgrade Procedures Step 4 Execute the PXM newrev command: newrev sm where: SM slot# is the slot number of the VISM 2 and new-rev is the filename of the new firmware. This command causes the VISM 2 to become the active VISM running the new-rev firmware. The previously active VISM 1 changes to a “hold” state and is still running the old-rev firmware. The primary and secondary firmware switches with the new-rev becoming the primary firmware.
Installation and Upgrade Procedures Step 5 Use the runrev sm-primary-slot-num new-rev command to execute the download. Step 6 Use the commitrev sm-primary-slot-num new-rev command to commit the new download to the VISM/VISM-PR card. You have completed the steps. Proceed to the VISM Boot Code Upgrade Procedure with PXM1E and PXM45 Cards, page 37. VISM Boot Code Upgrade Procedure with PXM1 Cards There is a new backup boot code change from VISM Release 2.2(0) to software Release 3.0(0) for VISM/VISM-PR.
Installation and Upgrade Procedures VISM Boot Code Upgrade Procedure with PXM1E and PXM45 Cards There is a new backup boot code change from VISM Release 2.2(0) to software Release 3.0(0) for VISM/VISM-PR. Complete the following steps to upgrade the new backup boot code when you are using PXM1E or PXM45 cards in your MGX 8000 Series chassis: Step 1 Complete the steps in the VISM Firmware Download Procedure for PXM1E and PXM45, page 33. Step 2 Log on to the PXM1E or PXM45 card.
Caveats Step 4 Execute the PXM restoresmcnf command: restoresmcnf -f -s where: The filename is the name of the old configuration file that was saved while the old-rev firmware was running. The file can be found in the C:CNF directory on the MGX shelf. The SM slot# is the slot number of the VISM card to be downgraded. The VISM card will be reset again. When the card comes active, it will have the old-rev firmware running and will have the old configuration.
Caveats Table 11 Resolved Caveats for Software Release 3.0(0) for VISM/VISM-PR (continued) DDTs Issue Description CSCdv25846 Title: Codec negotiation fails when certain specific strings are configured as codec names. Description: VISM rejects the call with the "admission failed to identify admitted codec" error message when the codec string has a specific parameter. Workaround: You should not use the following codec names in the cnfcodecparams CLI command: CSCdw89042 • G.729 • G.729-cisco • G.
Caveats Open Caveats Table 12 describes possible unexpected behavior by software Release 3.0(0) for VISM/VISM-PR. Table 12 Open Caveats for Software Release 3.0(0) for VISM/VISM-PR DDTs Issue Description CSCds66369 Title: VISM telnet sessions lock, unable to cc to card until reset. Description: The VISM card allows up to two sessions. Both of these sessions have become locked, which prevents the user from being able to use the cc command to access the card.
Related Documentation Related Documentation The following documents contain information that may be useful to software Release 3.0(0) for VISM/VISM-PR: • Cisco VISM Installation and Configuration Guide, Release 3.
Documentation Feedback Documentation Feedback You can submit e-mail comments about technical documentation to bug-doc@cisco.com. You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address: Cisco Systems Attn: Customer Document Ordering 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments.
Obtaining Additional Publications and Information For a complete listing of Cisco TAC contacts, go to this URL: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml TAC Case Priority Definitions To ensure that all cases are reported in a standard format, Cisco has established case priority definitions. Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Obtaining Additional Publications and Information • Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL: http://www.cisco.com/ipj • Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL: http://www.cisco.com/en/US/learning/index.
