Table Of Contents
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.4.00
Contents
About This Release
New Feature in Release 5.4.00.201
DTMF Squelching
For H.248
For XGCP
New Features in Release 5.4.00.200
Call Rate Performance Uplift
SNMPv3
V.110 Support for AAL2 Trunking Applications
Unique Virtual Gateway Domain Name for H.248
ptime Support for H.248
Firmware Images
Upgrading from an Earlier VXSM Release
Interrupted Procedure Recovery
Feature Clarifications
Online Diagnostics Feature as Applied to VXSM
DSP Resources Under Mixed Codec Conditions
VXSM Management Information Base
Service Module Support by Platform
Compatibility
Caveats for VXSM Release 5.4.00
Open Caveats in Release 5.4.00.201
Open Caveats in Release 5.4.00.200
Resolved Caveats in Release 5.4.00.201
Removed Caveats in Release 5.4.00.200
Resolved Caveats in Release 5.4.00.200
Related Documentation
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.4.00
Revised: September 26, 2007, OL-10897-01
Contents
The content of this document is arranged into the following major sections:
About This Release
New Feature in Release 5.4.00.201
DTMF Squelching
New Features in Release 5.4.00.200
Call Rate Performance Uplift
SNMPv3
V.110 Support for AAL2 Trunking Applications
Unique Virtual Gateway Domain Name for H.248
ptime Support for H.248
Firmware Images
Upgrading from an Earlier VXSM Release
Interrupted Procedure Recovery
Feature Clarifications
Online Diagnostics Feature as Applied to VXSM
DSP Resources Under Mixed Codec Conditions
VXSM Management Information Base
Service Module Support by Platform
Compatibility
Caveats for VXSM Release 5.4.00
Related Documentation
Obtaining Documentation, Obtaining Support, and Security Guidelines
About This Release
Version .201 of Release 5.4.00 is a patch releasefor VXSM that introduces a new feature (see DTMF Squelching). The resolved caveats for Versions .201 are listed in Table 5.
The VXSM Release 5.4.00 follows VXSM Release 5.3.10. The resolved caveats for VXSM Release 5.4.00 are listed in Table 5.
The Voice Switch Service Module (VXSM) product is supported by the MGX 8880 Media Gateway and the MGX 8850 Multiservice Switch. Refer to their respective release notes for platform and version level support guidelines.
Note 
To verify that you have the latest version of Cisco IOS required to support the new features included in this release, please check Cisco IOS availability status at Cisco.com.
The VXSM software release notes are supported by Cisco Voice Switch Services (VXSM) Configuration Guide, Release 5.4 and Cisco Voice Switch Services (VXSM) Command Reference, Release 5.4, both of which are available on cisco.com.
New Feature in Release 5.4.00.201
DTMF Squelching
This release contains the enhancements to completely squelch DTMF digits. This feature can be provisioned using the CLI commands shown below.
Note These CLI commands are not new for this release. They already exist in the product.
For H.248
Syntax Description
cnfh248profdtmf <Index> <DigitOnDuration> <DtmfPauseDuration> <DetectLongDigitDuration> <SuppressBearerDigit>
Option SuppressBearerDigit should be set to 1 to enable DTMF squelching.
For XGCP
Syntax Description
cnfxgcpprofdtmf <ProfileIndex> <SuppressBearerDigit>
Option SuppressBearerDigit should be set to 1 to enable DTMF squelching.
New Features in Release 5.4.00.200
Release 5.4.00 is a significant release with several major new software features over Release 5.3.10.
This release has no new VXSM hardware features.
The new software features include:
•Call Rate Performance Uplift
•SNMPv3
•V.110 Support for AAL2 Trunking Applications
•Unique Virtual Gateway Domain Name for H.248
•ptime Support for H.248
Call Rate Performance Uplift
VXSM 5.4.00 now supports a call rate of 85 CPS.
SNMPv3
Simple Network Management Protocol Version 3 (SNMPv3) is an standards-based protocol for network management. SNMPv3 provides secure access to devices using a combination of authentication and encryption of packets over the network. This assures that data can be collected securely from SNMP devices and that configuration messages cannot be viewed or altered.
The security features provided in SNMPv3 are:
•Message integrity—Ensuring that a packet has not been tampered with in-transit.
•Authentication—Determining that the message is from a valid source.
•Encryption—Scrambling the contents of a packet to prevent it from being seen by an unauthorized source.
V.110 Support for AAL2 Trunking Applications
VXSM supports the detection and handling of V.110 traffic used for modem and fax devices on mobile networks. This feature is used in conjunction with the AAL2 Trunking function. Upon detection of a V.110 bit pattern, VXSM provides a Clear Channel circuit for the duration of the V.110 (data) session.
The V.110 feature adds the following commands:
cnfeventmapping -v110 Configure V.110 events mapping
dspeventmapping -v110 Display V.110 events mapping
addccdprof Add clear channel data profile
cnfccdprof Configure clear channel data profile
delccdprof Delete clear channel data profile
dspccdprof Display clear channel data profile
dspccdprofs Display clear channel data profiles
Unique Virtual Gateway Domain Name for H.248
For H.248 applications, a VXSM card has the capability of being partitioned into a number of virtual media gateways (VMGs); where each VMG is a logical entity residing within a physical VXSM card. This feature permits each virtual gateway to be assigned its own unique domain name.
The Unique Virtual Gateway Domain Name feature modifies the following commands:
addh248assoc Add H.248 association
cnfh248mg Configure H.248 media gateway
dsph248assoc List configuration of H.248 Association
dsph248mg List configuration of H.248 Gateway
ptime Support for H.248
The ptime (packet period) attribute is defined in RFC 2327 as "the length of time in milliseconds represented by the media in a packet." ptime specifies the packet period for a codec, and maxptime specifies the maximum packet period.
The ptime and maxptime attributes are optional SDP attributes that can be sent down by the MGC in the local or remote descriptor SDP.
In release earlier than 5.4.00, the values of ptime and maxptime were ignored and the values configured on the platform were used.
Firmware Images
For each VXSM card type (OC-3/STM-1, T1/E1, or T3), two firmware images are available, namely, Non-CALEA and CALEA. When placing an order, the user must specify whether a Non-CALEA or CALEA image is required.
The Non-CALEA image supports three Media Gateway Control protocols, namely, H.248, MGCP, and TGCP. However, VXSM supports only one protocol at a time. The user must choose between the H.248, MGCP, and TGCP protocols when the image is first loaded from the PXM using the setrev command.
The CALEA image supports TGCP and MGCP only. The protocol must be explicitly selected when the image is loaded from the PXM using the setrev command.
VXSM supports two different codec templates; "TGW/wireline" and "Cable." The Cable template can be used only in conjunction with TGCP.
Upgrading from an Earlier VXSM Release
VXSM can be gracefully upgraded (configuration is preserved) from VXSM Release 5.2.10 or later so long as the original and the upgraded images are both either CALEA or Non-CALEA.
Note Upgrading from CALEA to Non-CALEA, or Non-CALEA to CALEA, is NOT supported.
When loading or upgrading a boot or runtime image to a VXSM card, users must observe the following caution:
Caution If an H.248 association is active with SrvChgProfile (used in service change message) as BT_TGW in 5.3.x.x release, after graceful upgrade to 5.4.00, the association will continue to use BT_TGW, but new association(s) cannot be added with SrvChgProfile as BT_TGW.
From the 5.4.00 release onward, the BT_TGW SrvChgProfile is no longer available. All new associations must be added using either etsi_tgw or CISCO_TGW.
Warning Many of the commands involved in loading or upgrading boot and runtime images can take several minutes to execute completely. If the user resets or otherwise disturbs the VXSM card during a loading or upgrading process, the card can easily be damaged even to the extent that it must be returned to the factory for repair.
In particular:
Do not reset VXSM or PXM cards manually or through commands such as resetcd or resetsys
Do not save all MGX configurations with commands such as saveallcnfs.
Do not toggle primary/secondary cards through commands such as switchredcd, delred
Do not change the name of software image before or during the upgrade
Do not change any configuration of active primary card during the upgrade
THE REAPPEARANCE OF THE COMMAND PROMPT AFTER A COMMAND IS ENTERED DOES NOT INDICATE THAT THE IMAGE LOAD OR UPGRADE HAS BEEN COMPLETED.
After the execution of the burnboot, clrsmcnf, loadrev, or setrev commands, the user must execute either a dspcds or dsprev command periodically to verify that the state of the VXSM card being loaded or upgraded is either Active, Standby, or Failed.
ONLY WHEN THE CARD IS DISPLAYED TO BE IN ONE OF THESE STATES IS IT SAFE TO GO TO THE NEXT STEP.
If the upgrade procedure is interrupted for reasons outside the control of the user (for example, a power outage), see "Interrupted Procedure Recovery" below for instructions.
Interrupted Procedure Recovery
In the event that a VXSM software upgrade procedure is interrupted (for example, power outage), and both Primary and Secondary are stuck in 'Failed-U' state, perform the following procedure
Step 1 Execute the abortrev command:
abortrev <PrimarySlot> <NewImageRevision>
Step 2 If the primary VXSM becomes "Failed/Active" (out of Failed-U/Active"), then execute the resetcd command
resetcd <PrimarySlot>
Step 3 If the secondary VXSM becomes "Failed/Active" (out of Failed-U/Active"), then execute the resetcd command:
resetcd <SecondarySlot>
Step 4 Both primary and secondary VXSM cards should now have their original SW image and original DB
Feature Clarifications
Online Diagnostics Feature as Applied to VXSM
The online diagnostics feature as implemented on the PXM45 card is supported on VXSM. When enabled, using the PXM45 cnfdiag command, this feature performs non-intrusive diagnostics tests that use four of the VXSM G711 DSP resources.
If the user executes the VXSM dspdspcodecpools command, the resulting display shows the four G711 DSP resources being used (for diagnostics) and subtracts them from the remaining available codecs (see example below).
mgx.3.VXSM.a > dspdspcodecpools
=====================================================================
=====================================================================
Codec pool Current utilized Current available
capacity (#DSP chans) capacity (#DSP chans)
========== ===================== =====================
G711 family/HDLC 179 7885
G729/G726/T.38 family 0 3919
In this example, 175 G711 calls have been established along with four G711 resources used for diagnostics.
The online diagnostics feature does not reduce the maximum number of 8064 G711 DSP resources available for calls on the VXSM card. If the number of call requests on the VXSM is sufficiently high, the online diagnostic feature is disabled automatically and the four codecs are made available for active calls.
DSP Resources Under Mixed Codec Conditions
When the same codec is used to setup calls on the gateway the available DSP resources will be fully utilized. However when different codecs are used to setup calls the amount of utilizable DSP resources may be limited in certain cases due to resource fragmentation.
Fragmentation is said to have occurred when the available capacities on two different DSP resources have enough available capacity to support a call of a particular codec type but cannot support that codec type individually.
Consider two DSP resources whose available capacity is 1 unit each making the total available capacity 2 units. However a codec that requires 2 units cannot be supported in the system because the available capacities have been fragmented across the individual DSP resources.
The DSP allocation algorithm on VXSM does make an attempt to smooth the effects of fragmentation. Fragmentation can happen because the pattern of future calls cannot be predicted beforehand.
VXSM Management Information Base
The VXSM Management Information Base (MIB) Version 5.4 is available to users with CCO accounts who can access the MIB and VXSM software on-line at: http://www.cisco.com/kobayashi/sw-center/sw-wan.shtml
Step 1 Log on to http://www.cisco.com/kobayashi/sw-center/sw-wan.shtml
Step 2 Locate the VXSM platform (either VXSM 8880 or VXSM 8850) and click the down arrow to expand the "Select Release Level" drop down menu.
Step 3 Select the desired MIB release level (for example, Release 5400) to display a list of downloadable files.
Step 4 Click on the desired file (for example, mgx8850-fw-5400.tar).
Step 5 Read the license agreement and, if approved, click Accept.
Step 6 In the Software Download dialog box, click on Download: filename (where filename is the name of the file selected for download). This step starts the download procedure.
Step 7 Follow the normal file download procedure for your computer.
Step 8 When the file has been downloaded, untar or unzip the downloaded file. The MIB file is included in the downloaded file and is listed as a tar file (for example mgx8850rel5400mib.tar).
Step 9 Untar the MIB file to display its contents.
Service Module Support by Platform
Service Module
|
MGX8880
|
MGX8850
|
PXM45/C
|
PXM1
|
PXM45/B
|
PXM45/C
|
PXM1E
|
MGX-RPM-XF-512
|
Yes
|
|
Yes
|
Yes
|
No
|
MGX-RPM-PR-512
|
Yes
|
|
Yes
|
Yes
|
Yes
|
VISM-PR-8T1
|
Yes
|
Yes
|
Yes
|
Yes
|
Yes
|
VISM-PR-8E1
|
Yes
|
Yes
|
Yes
|
Yes
|
Yes
|
AXSM-1-2488/B
|
Yes
|
|
Yes
|
Yes
|
|
AXSM-16-T3/E3/B
|
Yes
|
|
Yes
|
Yes
|
|
AXSM-16-155-XG
|
Yes
|
|
Yes
|
Yes
|
|
AXSM-8-622-XG
|
Yes
|
|
Yes
|
Yes
|
|
MGX-VXSM-155
|
Yes
|
|
No
|
Yes
|
|
MGX-VXSM-T1E1
|
Yes
|
|
No
|
Yes
|
|
MGX-VXSM-T3
|
Yes
|
|
No
|
Yes
|
|
MPSM-T3E3-155
|
No
|
|
Yes
|
Yes
|
Yes
|
MPSM-16-T1E1
|
Yes
|
|
Yes
|
Yes
|
Yes
|
RCON-1TO5-8850
|
Yes
|
|
|
Yes
|
|
Compatibility
Note VXSM Release 5.4.00 is supported only with PXM-45/C.
VXSM software interoperability with the MGX 8880 Media Gateway or the Cisco MGX 8850 (PXM45) Multiservice Switch platform software is listed in Table 1.
Table 1 VXSM Software Interoperability
Product
|
Latest Firmware
|
Min. Firmware
|
PXM45
|
5.4.00.202
|
5.4.00.202
|
MGX-RPM-XF-512
|
12.4(15)T1
|
12.4(6)T1
|
CWM
|
15.4.00
|
15.4.00
|
CTM
|
8.0
|
8.0
|
VISM-PR
|
3.3.30
|
3.3.30
|
AXSM-16-T3/E3/B
|
5.4.00
|
5.4.00
|
AXSM-16-155-XG
|
5.4.00
|
5.4.00
|
AXSM-8-622-XG
|
5.4.00
|
5.4.00
|
MPSM-16-T1E1
|
5.4.00
|
5.4.00
|
MPSM-T3E3-155 (8850 only)
|
5.4.00
|
5.4.00
|
BTS
|
4.5
|
4.4
|
PGW
|
9.5.2
|
9.5.2
|
Cisco 2600 Series Routers
|
c2600-ipvoice-mz.123-9.13.T
|
c2600-ipvoice-mz.123-9.13.T
|
Cisco 2600 for use as an
IP Transfer Point
|
c2600-itp-mz.122-21.SW bin
|
c2600-itp-mz.122-21.SW bin
|
Cisco 3700 Series Routers
|
c3725-ipvoice-mz,123-9.13.T
|
c3725-ipvoice-mz,123-9.13.T
|
Cisco ATA 188
|
3.2.0 for SIP/MGCP/H323
|
3.2.0 for SIP/MGCP/H323
|
Linksys PAP2 Phone Adapter
|
Version 2.0.6 (LS)
|
Version 2.0.6 (LS)
|
Linksys RT31 Router
|
Version 1.27.01
|
Version 1.27.01
|
Sipura 2100 ATA
|
Version 3.2.3
|
Version 3.2.3
|
Table 2 describes the software images available for Release 5.4.00 for VXSM.
Table 2 Software Images for Release 5.4.00 for VXSM
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
MGX-VXSM-155, CALEA
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.054.000.201.fw
|
MGX-VXSM-155, Non-CALEA
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.004.000.201.fw
|
MGX-VXSM-T1E1, CALEA
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.054.000.201.fw
|
MGX-VXSM-T1E1, Non-CALEA
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.004.000.201.fw
|
MGX-VXSM-T3, CALEA
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.054.000.201.fw
|
MGX-VXSM-T3, Non-CALEA
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.004.000.201_bt.fw
|
vxsm_005.004.000.201.fw
|
Caveats for VXSM Release 5.4.00
This section describes software caveats for the various versions of Release 5.4.00.
Open Caveats in Release 5.4.00.201
Table 3 Open Software Caveats in VXSM Release 5.4.00.201
DDTS Issue
|
Description
|
CSCek54023
|
Headline: DSP exception while running the mix codec codecs with COT enabled
Symptom: Call setup or call modification failure is seen on calls that are affected by this non-fatal error. This error also results in associated PXM logs indicating a DSP Channel EXCEPTION.
Conditions: This issue was seen twice in an overnight run with a single codec of G.711. There is no permanent damage at the card level due to this error. The error only affects single calls. Subsequent calls on the same TDM endpoint will be unaffected by the previous occurrence of this error.
Workaround: None.
|
CSCek62859
|
Headline: Hung CCB conn even after gwfOOS and inservice
Symptoms: Hung CCBs.
Conditions: Configure VXSM for basic VOIP call, Send CRCX with signal request IT/rt, The call is dropped with error code 404 No bandwidth resource. On checking dspxgcpendptcons * it shows no current calls. In active ccb it shows a tone and no calls can be made on that end point. Tried to do a cnfgwoos 2 (forced) but activeCcbs still shows the same state.
Workaround: None.
|
CSCek65811
|
Headline: cnfgwis gives error message when the GW is in forced OOSstate already
Symptoms: cnfgwis command fails to bring VXSM Gateway state back to in-service.
Conditions: cnfgwis command fails after cnfgwoos command execution with error "Out of service operation is going on, wait for a while."
Workaround: VXSM card reset.
|
CSCek69535
|
Headline: hung calls in midcall codec chng when no bearer channel available
Symptoms: When near to maximum capacity call is made and codec is modified to a different codec family, few modify failures happen.
Conditions: When channel capacity required for new codec is more than the previous one and the DSP core, where the channel was allocated is full then modify doesn't happen successfully. This happens even if some channels in other DSP core are free.
Workaround: None.
|
CSCsj03370
|
Headline: VXSM switches on executing the attached call waiting scenario
Symptoms: The VXSM card in H248 call control protocol mode switches to standby in a call waiting scenario where first user reverts back to the second user after attending a waiting call from third user. The executed call flow is not supported by VXSM.
Conditions: When the first user reverts back to second user after attending a waiting call then VXSM switches to standby card.
Workaround: None.
|
CSCsk13959
|
Headline: Tone detection disabled after midcall codec change from PCMU to G729a
Symptoms: Fax Modem call not working after midcall codec change from PCMU to G729a.
Conditions: No Upspeed after midcall codec change in a voice call from PCMU to G729a.
Workaround: None.
|
.
Open Caveats in Release 5.4.00.200
Table 4 Open Software Caveats in VXSM Release 5.4.00.200
DDTS Issue
|
Description
|
CSCek70423
|
Headline: Unable to add LAPD on 1 T1(Rest all 335 LAPDs are added).
Symptoms: addlapd returns error "ERR: DS0 already in use by B-Channel" while DS0 is free.
Condition: This problem happens when LAPDs are added on active card, but one LAPD in sequence is missed out to add (LAPD on DS1 1-3 is added, then LAPD for DS1 5-6 is added and 4th DS1 is free). If switchover happens at this time then LAPD on 4th DS1 will not be allowed to add and will return above error.
Workaround: LAPDs should be added sequentially.
|
CSCek69535
|
Headline: hung calls in midcall codec chng when no bearer channel available.
Symptom: When channel capacity required for new codec is more than the previous one and the dsp core, where the channel was allocated is full then modify doesn't happen successfully. This happens even if some channels in other DSP core are free.
Condition: When near to maximum capacity call is made and codec is modified to a different codec family, few modify failures happen.
Workaround: None.
|
CSCek65811
|
Headline: cnfgwis gives error message when the GW is already in forced OOSstate.
Symptom: cnfgwis command fails after cnfgwoos command execution with error "Out of service operation is going on, wait for a while."
Condition: cnfgwis command fails to bring VXSM Gateway state back to in-service.
Workaround: VXSM card reset.
|
CSCek62958
|
Headline: IUA-SLT: Dsperrs observed stating invalid chunk data ptr.
Symptom: During high cps i.e 35cps Dsperrs observed stating invalid chunk data ptr.
Condition: When IUA is tested at high cps with mix traffic of voice + fax + modem at that time dsperrs are observed.
Workaround: None.
|
CSCek70878
|
Headline: VXSM mgcgwdn mismatch results in COT failure.
Symptom: VXSM COT tests fail 100% of the time, however bearer path is not impacted.
Condition: Extra processing when mgc domain name is not case-matched with what is configured in BTS emulates COT failure.
Workaround: Configure VXSM with exact gateway domain name found in /etc/hosts. Alternatively, configure dns on the VXSM with adddnsdn command.
|
CSCek70226
|
Headline: H.248:Out of resource error due to CDB leak.
Symptom: Commands rejected with "out of resources" error and same is loggin in dsplog alongwith "operation failed" errors in dsplog.
Condition: CDB are not freed in case of encode failures.
Workaround: None.
|
CSCek70118
|
Headline: VXSM H.248 returns Pending transactions.
Symptom: In H.248 Media gateway configuration VXSM replies with pending transactions to call agent commands. The pending transaction replies are followed by a final response containing error code 510 "Insufficient_resources."
Condition: This problem would be seen if two consecutive transactions are sent to media gateway for a same termination without waiting for a response for the first transaction. Both the transactions will be successful. But the third and subsequent transactions on this termination ID will get pending replies from gateway.
Workaround: Wait for reply of first transaction before sending next transaction to media gateway on the same termination ID.
|
CSCek70227
|
Headline: H.248:Megaco PPC task suspended when stuck in a for loop.
Symptom: Megaco PPC task suspended.
Condition: Megaco PPC task stuck in a for loop.
Workaround: None.
|
CSCek54023
|
Headline: DSP exception while running the mix codec codecs with COT enabled.
Symptom: Call setup or call modification failure is seen on calls that are affected by this non-fatal error. This error also results in associated PXM logs indicating a DSP Channel EXCEPTION.
Condition: This issue was seen twice in an overnight run with a single codec of G.711. There is no permanent damage at the card level due to this error. The error only affects single calls. Subsequent calls on the same TDM endpoint will be unaffected by the previous occurrence of this error.
Workaround: There is no workaround for this problem at this time. It has not been completely ascertained whether the issue does not occur with COT disabled or with single codecs.
|
CSCek62859
|
Headline: Hung CCB conn even after gwfOOS and inservice.
Symptom:
Condition:
Workaround:
|
CSCek67800
|
Headline: H248:Restart SC should be sent on redirection before registration.
Symptom: ServiceChange with method handoff.
Condition: MgcIdToTry with new MGC address received in response to initial serviceChange with method restart.
Workaround: None. This will redirect to new MGC but only issue is an unnecessary audit procedure shall be initiated by new MGC.
|
CSCek70228
|
Headline: H.248:Hung RTP terminations due to res dealloc failures in CRML.
Symptom: Hung CCBs for RTP termination in CRML and cmrlstats shows resource dealloc error for the same.
Condition: Moderate call rate.
Workaround: None.
|
CSCek70797
|
Headline: Fax fails on T.38 devices when call starts at G729.
Symptom: Fax fails on T.38 devices when call starts at g.729. The T.38 exchange looks OK on the SIP side, but the MGX never switches over to T.38 packets. The problem is that when an outbound T.38 call starts on g.729 codec, the PGW/MGX re-sends the T.38 INVITE and all looks OK, however no T.38 packets ever come from the MGX.
Condition: When PP Control is disabled on VXSM and Basic T.38 fax call fails when voice call starts with g.729 codec.
Workaround: Enable pp control in vbd profile using Cli cnfvbdprof 1 -ppcontrol 1
|
.
Resolved Caveats in Release 5.4.00.201
Table 5 Resolved Anomalies in Release 5.4.00.201
Anomaly ID
|
Description
|
CSCek55569
|
Standby card recreate failed by NULL ldibptr
|
CSCsj73803
|
VXSM is rejecting the MDCX containing SDP with the following attributes
|
CSCsj47252
|
VXSM crashes on Load for PCMU calls in MGCP
|
CSCek62958
|
IUA-SLT: Dsperrs observed stating invalid chunk data ptr.
|
CSCsj83896
|
malformed REL_CON in response to REL_REQ in IUA
|
CSCsj65154
|
Standby reboots after failure in Mod operation (without an Add operation)
|
CSCsj58344
|
Fine Tune Lower and upper limits for callsetupResouce
|
CSCsj47830
|
Connection Id not cleaned up on standby after call gets deleted
|
CSCsj37922
|
GW controlled fax in H248 with OGW set to VBD and TGW set to fax fails
|
CSCsj23389
|
Memory Leaks in VXSM during M3UA load
|
CSCek66089
|
M3UA-SLT: Observed invalid chunk data ptr in dsperrs.
|
CSCsj02353
|
G.729 calls fails on enabling AnnexABsdp
|
CSCsi73479
|
Successful Graceful OOS followed by Forced OOS hangs H.248 Assoc
|
CSCsj21826
|
Subtract cmd with RTP/* results in Internal Gateway Error ( 500 )
|
CSCsi96344
|
DSP crash due to misconfiguration with 40 ms pkt size forG711u CSCsj10767
|
CSCsj02348
|
Standby Failure during the incremental sync
|
CSCsi68488
|
MGCP: 1% call failures during 8cps with codec change from g729ab to g711u
|
CSCek70423
|
Unable to add lapd on 1 T1(Rest all 335 lapds are added)
|
CSCsi86301
|
VXSM does not send DLCX on RTCP timeout if some evt/sig exists on endpt
|
CSCsi98033
|
TTY tone should be programmed on DSP depending on the event mapping
|
CSCsi58250
|
VXSM is not changing remote end port on getting T.38 modify msg in H248
|
CSCsi96310
|
CRML-1-REDM_DELCON_FAIL Memory Full
|
CSCsi75071
|
Hung SCN termination due to Exception in dil_open_channel
|
CSCek70228
|
H.248:Hung RTP terminations due to res dealloc failures in CRML
|
CSCsi55192
|
rtpmap not supported for Static payload types
|
CSCek72659
|
Low priority RUDP session remains In service
|
CSCsi34955
|
Rudp Sessions Grp Status is in the NONE state
|
CSCek72659
|
Low priority RUDP session remains In service
|
CSCek70227
|
H.248:Megaco PPC task suspended when stuck in a for loop.
|
CSCek70226
|
H.248:Out of resource error due to CDB leak.
|
CSCsi51255
|
Tones detection not getting enabled in TDM hairpin call.
|
CSCek70118
|
VXSM H.248 returns Pending transactions
|
CSCek70116
|
VXSM sends incorrect H.248 error code 500 when no termination matches
|
CSCsi49015
|
Allow 1st character as digit in domain name configuration
|
CSCek73769
|
Ringback Tone for US is not working.
|
CSCek73413
|
No endoints registered... prints on console periodically.
|
CSCek70797
|
Fax fails on T.38 devices when call starts at G729
|
CSCek70878
|
VXSM mgcgwdn mismatch results in COT failure
|
CSCek67800
|
H248:Restart SC shud be sent on redirection before registration
|
Removed Caveats in Release 5.4.00.200
Table 6 lists caveats that were listed as open in Release 5.3.10 but have been removed because they are unreproducible or otherwise invalid.
Table 6 Caveats Removed in Release 5.4.00.200
DDTS Issue
|
Description
|
CSCek40572
|
Fax upspeed fails after modifying H248 call to a new codec.
|
CSCek33012
|
VQM RFC 3611 Dup pkts (1 in 100) cause incorrect loss rate 99.6%.
|
CSCek50487
|
T.38 call doesn't downspeed if midcall mdcx is sent.
|
CSCek53995
|
DB missing dsp info after upgrade from 2.5 to 2.5mr.
|
.
Resolved Caveats in Release 5.4.00.200
Table 7 describes the caveats that were open following in Release 5.3.10 but are now resolved in VXSM Release 5.4.00.200.
Table 7 Software Caveats Resolved in VXSM Release 5.4.00.200
DDTS Issue
|
Description
|
CSCek38528
|
Enable card switch-over if IOS tasks crash
|
CSCek52027
|
semGive error in PXM log, VXSM resets after 2-3 days
|
CSCek52788
|
Inconsistent severity and huge amount of H248 log messages
|
CSCek52935
|
VXSM intermittently uses G723 resources instead of specified G711
|
CSCek53543
|
Dual PVC failure will not recover if failure threshold is 2
|
CSCek53969
|
DSM rejects some DSP responses with no pending requests error
|
CSCek54015
|
Memory leak in DSPAPI buffers on the daughtercard
|
CSCek54040
|
Mix codec calls with COT enabled on BTS caused vxsm VTSP crash
|
CSCek54219
|
Double open in standby VXSM
|
CSCek54902
|
CCAPI memory leak when handling disconnect timeout
|
CSCek54911
|
Standby card crashes with DSP channel exception
|
CSCek55602
|
Mem Leak in MGCP app
|
CSCek55865
|
Time duration too long (~48hrs) for audit on NULL context
|
CSCek56159
|
RTP terms left hanging on standby even after deleting the call
|
CSCek56325
|
VXSM should ignore unsupported codec
|
CSCek56719
|
RQNT followed by mid-call codec change and subsequent call fails
|
CSCek57181
|
increase TM_MM_BUFF_NT_ADDR buffer from 2 to 20 bytes
|
CSCek57550
|
cnfgwoos failed to clean up dangling call legs
|
CSCek55569
|
Standby card recreate failed by NULL ldibptr
|
CSCek58229
|
154 bytes of a-X-cluster causes PPC exception
|
CSCek58493
|
Compare strings failed because of null string pointers
|
CSCek65232
|
Cisco MGX did not recover from call server sequential restart
|
CSCek60744
|
Calls not cleared in MG while H248 Midcall Codec Chg call rate test
|
CSCek65479
|
failure in response to resource allocation request, SCN termination
|
CSCek65910
|
Standby Card resets frequently
|
CSCuk61635
|
VXSM replies with Internal Gw error to a Modify in a T38 Call
|
CSCek63961
|
T.38 with fallback to G.711
|
CSCuk61637
|
VXSM stays in service after an Unauthorized message from CA
|
CSCek64524
|
VXSM gives err-442 when Term-desc is not at first pos in Media desc
|
CSCek64573
|
VXSM cli stops working after adding 1st session grp when 2nd exists
|
CSCek66095
|
Modify command failure from CRML is returned as success to MGC
|
CSCek65372
|
VXSM OC-3 TGCP could not handle RQNT with cot
|
CSCek68159
|
Default PLC config does not take effect during call-setup
|
CSCek68160
|
DSP Knob cnfdsp -ec does not work
|
CSCek68398
|
H248:CED not re-enabled on 1300Hz detection (during V.90 ups)
|
CSCek68407
|
cant cnfgwdn or adddnsdn after upgrade to 5.3(10.200)
|
CSCek69459
|
MGCP T.38:Upspeed fails when remote port changesduring T.38 switch
|
Related Documentation
The following documents contains information that may be useful to software Release 5.4 for VXSM:
•Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide, Releases 2 Through 5.3
•Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5.2
•Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4
•Cisco MGX 8880 Media Gateway, Release 5.4: A Guide to User Documentation.
•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.4
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
