Table Of Contents
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.3.30
Contents
About This Release
Firmware Images
Upgrading from an Earlier VXSM Release
Interrupted Procedure Recovery
VXSM Management Information Base
Service Module Support By Platform
Compatibility
Caveats for VXSM Release 5.3.00
Open Caveats in Release 5.3.30.200
Open Caveats in Release 5.3.10.201
Removed Caveats in Release 5.3.10.201
Resolved Caveats in Release 5.3.30.200
Resolved Caveats in Release 5.3.10.201
Related Documentation
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.3.30
Revised: May 22, 2008, OL-11295-03
Contents
About This Release
Firmware Images
Upgrading from an Earlier VXSM Release
Interrupted Procedure Recovery
VXSM Management Information Base
Service Module Support By Platform
Compatibility
Caveats for VXSM Release 5.3.00
Open Caveats in Release 5.3.30.200
Open Caveats in Release 5.3.10.201
Removed Caveats in Release 5.3.10.201
Resolved Caveats in Release 5.3.30.200
Resolved Caveats in Release 5.3.10.201
Related Documentation
Obtaining Documentation, Obtaining Support, and Security Guidelines
About This Release
The VXSM Release 5.3.30.200 follows VXSM patch Release 5.3.10.201. For information about resolved anomalies in this release, see Table 6.
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.
The VXSM software release notes are supported by the Cisco Voice Switch Services (VXSM) Configuration Guide, Release 5.3 and the Cisco Voice Switch Services (VXSM) Command Reference, Release 5.3, both of which are available on cisco.com.
Firmware Images
For each VXSM card type (OC-3, T1/E1, or T3), two firmware images are available, namely, Non-CALEA and CALEA. At order time, the user must specify whether a Non-CALEA or CALEA image is required.
The Non-CALEA image supports three Media Gateway Call Control (MGC) protocols, namely, H.248, MGCP, and TGCP. However, the image supports only one protocol at a time. The user must choose between the H.248, MGCP, and TGCP versions 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.
Upgrading from an Earlier VXSM Release
VXSM can be gracefully upgraded (configuration is preserved) from any VXSM Release 5.2.x.x (or later) so long as the original and the upgraded images are of the same version (for example Non-CALEA, TGCP to Non-CALEA, TGCP). When loading or upgrading a boot or runtime image to a VXSM card, users must observe the following caution.
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
VXSM Management Information Base
The VXSM Management Information Base (MIB) Version 5.3 is available by request through your Cisco VXSM product marketing representative.
Alternatively, users with CCO accounts can access the MIB and VXSM software on-line at:
http://www.cisco.com/public/sw-center/sw-wan.shtml
The procedure is:
Step 1 Log on to http://www.cisco.com/public/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 5300) to display a list of downloadable files.
Step 4 Click on the desired file (for example, mgx8850-fw-5300.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 mgx8850rel5300mib.tar).
Step 9 Untar the MIB file to display its contents.
Service Module Support By Platform
Service Module
|
MGX8880
|
MGX8850
|
PXM45/C
|
PXM1
|
PXM45/A
|
PXM45/B
|
PXM45/C
|
PXM1E
|
MGX-RPM-XF-512
|
Yes
|
|
|
Yes
|
Yes
|
|
VISM-PR
|
Yes
|
Yes
|
|
Yes
|
Yes
|
Yes
|
AXSM-1-2488/B
|
Yes
|
|
|
Yes
|
Yes
|
|
AXSM-16-155/B
|
Yes
|
|
|
Yes
|
Yes
|
|
AXSM-4-622/B
|
Yes
|
|
|
Yes
|
Yes
|
|
AXSM-16-T3/E3/B
|
Yes
|
|
|
Yes
|
Yes
|
|
AXSM-32-T1E1-E
|
Yes
|
|
|
Yes
|
Yes
|
|
MGX-VXSM-155
|
Yes
|
|
|
Yes
|
Yes
|
|
MGX-VXSM-T1E1
|
Yes
|
|
|
Yes
|
Yes
|
|
MGX-VXSM-T3
|
Yes
|
|
|
Yes
|
Yes
|
|
MPSM-T3E3-155
|
|
|
|
Yes
|
Yes
|
Yes
|
RCON-1TO5-8850
|
Yes
|
|
|
|
|
|
Compatibility
Note VXSM Release 5.3.30.200 is supported only with PXM-45.
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.3.10.201
|
5.3.10.201
|
MGX-RPM-XF-512
|
12.4(6)T10
|
12.4(6)T1
|
CWM
|
15.4
|
15.1.50P1
|
CTM
|
8.5
|
7.0
|
VISM-PR
|
3.3.30
|
3.3.25
|
AXSM-1-2488/B
|
5.3.10.200
|
5.3.10.200
|
AXSM-16-155/B
|
5.3.10.200
|
5.3.10.200
|
AXSM-4-622/B
|
5.3.10.200
|
5.3.10.200
|
AXSM-16-T3/E3/B
|
5.3.10.200
|
5.3.10.200
|
AXSM-32-T1E1-E
|
5.3.10.200
|
5.3.10.200
|
AXSM-XG OC3
|
5.3.10.200
|
5.3.10.200
|
MPSM-T3E3-155
|
5.3.10.200
|
5.3.10.200
|
BTS
|
5.0(1)V05
|
4.5
|
PGW
|
9.7.3
|
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.3.30.200 for VXSM.
Table 2 Software Images for Release 5.3.30.200 for VXSM
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
MGX-VXSM-155, CALEA
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.053.030.200.fw
|
MGX-VXSM-155, Non-CALEA
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.003.030.200.fw
|
MGX-VXSM-T1E1, CALEA
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.053.030.200.fw
|
MGX-VXSM-T1E1, Non-CALEA
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.003.030.200.fw
|
MGX-VXSM-T3, CALEA
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.053.030.200.fw
|
MGX-VXSM-T3, Non-CALEA
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.003.030.200_bt.fw
|
vxsm_005.003.030.200.fw
|
Caveats for VXSM Release 5.3.00
This section describes software caveats for the various versions of Release5.3.00.
Open Caveats in Release 5.3.30.200
Table 4 describes the open caveats in VXSM Release 5.3.30.200.
Table 3 Open Software Caveats in VXSM Release 5.3.30.200
DDTS Issue
|
Description
|
CSCsq00049
|
Headline: VXSM Card goes to Active-F state due to DSP Fail Non-Fatal Major Error.
Symptom: VXSM Card goes to Active-F state due to DSP Fail Non-Fatal Major Error.
Conditions: Due to DSP Fail Non-Fatal Major Error, VXSM goes to Active-F state. The reason for DSP Failure is not known.
Workaround: None.
|
CSCsj41671
|
Headline: MGCP VoIP: TTY upspeed occurs with wrong encoding type.
Symptom: When bringing up a TTY call, the upspeed occurs but the codec being used for the upspeed is incorrect. It uses G711u in E1 mode while it should use G711A, thus impacting the quality of the call.
Conditions: Not Known. It occurs intermittently.
Workaround: Configure the upspeed codec to some other upspeed codec say G.726. Again configure the upspeed codec as G711a. Subsequent upspeeds will work fine.
|
CSCsm07555
|
Headline: When inact timer sets to 0 then call returns to voice for HS modulation.
Symptom: When inact timer value sets to 0 then endpoints downspeeds to voice mode when high speed modulation is run.
Conditions: Set the inactivity time out value to zero in cnfvbdprof.
Workaround: None.
|
CSCsk94294
|
Headline: IUA-SLT: Fax failure at high T.38 traffic around 10% of total VXSM cap.
Symptom: T.38 Fax failures with channel exceptions.
Conditions: The failure is only seen under high ratio (>10%) of T.38 calls.
Workaround: None.
|
Open Caveats in Release 5.3.10.201
Table 4 describes the open caveats in VXSM Release 5.3.10.201.
Table 4 Open Software Caveats in VXSM Release 5.3.10.201
DDTS Issue
|
Description
|
CSCek72659
|
Headline: Low priority RUDP session remains In service.
Symptom: In a Backhaul session group, containing two or more RUDP sessions, the lower priority session becomes in service.
Conditions: This may happen when call agent switch over is done or a call agent is restarted.
Workaround: Delete and add the RUDP sessions in the session group on VXSM.
|
CSCek54023
|
Headline: DSP exception while running the mix codec calls.
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.
|
Removed Caveats in Release 5.3.10.201
Table 5 lists caveats that were listed as open in Release 5.3.10.201 but have been removed because they are unreproducible or otherwise invalid.
Table 5 Removed Software Caveats for VXSM Release 5.3.10.201
DDTS Issue
|
Description
|
CSCek50487
|
t38 call doesn't downspeed if midcall mdcx is sent
|
CSCek33012
|
VQM RFC 3611 Dup pkts (1 in 100) cause incorrect loss rate 99.6%
|
CSCek40572
|
Fax upspeed fails after modifying H248 call to a new codec
|
CSCek53995
|
db missing dsp info after upgrade from 2.5 to 2.5mr
|
Resolved Caveats in Release 5.3.30.200
Table 6 describes the caveats that are resolved in VXSM Release 5.3.30.200.
Table 6 Resolved Software Caveats in VXSM Release 5.3.30.200
DDTS Issue
|
Description
|
CSCsq1654
|
COT Tone not detected if RQNT is sent with R:Co1
|
CSCsq06487
|
Illegal Vif Size being sent to DSP API for G.729a/G.729ab codec
|
CSCso89302
|
IUA-SLT:MEGA-1-INNSUFT_RESOURC PXM logs observed during VXSM switch.
|
CSCso71748
|
Bearer channel contention between LAPD and BLV channel during INIT time.
|
CSCso83202
|
Fax pass through does not work due to early detection of CNG tone.
|
CSCso92744
|
MGCP: Tones should be programmed at DSP based on eventmapping config.
|
CSCso94679
|
xGCP: Remote descriptor not returned in AUCX response after switchover.
|
CSCso85969
|
cnfpathoos not logged in PXM log and endpoints in forcedOOS but call the goes through.
|
CSCso89555
|
VXSM returns 500 Error when RTP stats requested in T.38 mode.
|
CSCek59299
|
cnfvicas does take the default value for cas profile
|
CSCso64336
|
FAX/MODEM upspeed fails on midcall codec change followed by VXSM s/w.
|
CSCso37667
|
CACing is not proper after VXSM downspeed in CA controlled T38.
|
CSCso14820
|
XGCP:Standby fails on switchover with 8K subscriber and mid-call modify.
|
CSCso52286
|
[H.248]VXSM does not notify ANS on detecting CED after 1300 Hz tone.
|
CSCsk58269
|
VXSM active card resets due to memory leak in MGCP application.
|
CSCsl41112
|
TGCP-CALEA:Wrong Counters Increm for CALEA calls after switchover.
|
CSCso46707
|
Not able to delete VIF when ss7link is configured on first DS0 and VIF on second.
|
CSCso57402
|
RSIP-restart not received after small duration line alarm clears on E1.
|
CSCso39934
|
mgcDirectOOS Assoc goes to inservice state after switchover
|
CSCso53222
|
High Call Failures with one AESS Signaling enabled on trunks and COT sent.
|
CSCso59549
|
IUA-MGCP SLT: IUA chunks failures observed in voice+fax+modem load.
|
CSCsm27343
|
XGCP:Multiple Modify over 60 cps results in failure of standby card.
|
CSCsl58624
|
Resource Deallocation observed when CA contr. Fax is sent with RV ON
|
CSCso40195
|
VAD mismatch after VXSM downspeeds in a CA T38 call- remote port change
|
CSCso47028
|
LAPD: The parameter name of a stat is wrong in CLI.
|
CSCso34779
|
500 observed when Remote contains rtpmap for the static payload type.
|
CSCso17523
|
CAS digit power levels are incorrect.
|
CSCsm30992
|
Wrong Media Type for call on sending mdcx after t38 fallback
|
CSCsm66311
|
Notify entity remain 0.0.0.0 even after configuring MGC (cnfxgcpmgcgrp)
|
CSCsm14555
|
DSPAPI Related PXM Logs Error/Warning Cleaning and Addition.
|
CSCsm52388
|
VXSM resets with DC heartbeat fail Fatal along with BCDRV Error message
|
CSCsm04560
|
DPVC PXM logs correction and Enhancements of debug shellConns for DPVC
|
CSCsm96820
|
H.248: Incorrect CAC utilization for ClearChannel codec on sending FAX
|
CSCsj96729
|
Transcoding: Event Buffer Functionality is not working
|
CSCsk96065
|
DCAP Software Exception: Vector 768 EPC: 0x00010890 ADDR: 0x00e04cc0.
|
CSCsm09963
|
During ss7 link addition error capture in dsplog file
|
CSCsm34288
|
Setting prof value to 0 for CLI "addss7linkset" leads to VXSM crash
|
CSCsm31117
|
Vad is not updated during a midcall codec change
|
CSCso04391
|
Standby goes to failed state after mid-call codec change
|
CSCsm12337
|
IUA-H248:StandBy VXSM fails while adding redundancy with mix load
|
CSCsm12135
|
H248SLT:Standby goes to Failed when redundancy is added on a active call.
|
CSCek66529
|
M3UA-SLT:Instruction Bound Exception observed while adding ss7link
|
CSCso17254
|
Improper initialization of channel_state in API modify channel.
|
CSCsm82730
|
M3UA-SLT:StandBy goes into Failed state if reset issued in Init state.
|
CSCsl02645
|
DSP crash due to wrong value of vif size(pkt period) for G.729 & G.711
|
CSCsk84152
|
H248:Tones should be programmed at DSP based on eventmapping config
|
CSCsm07005
|
MGCP: CNG Tone should be linked to CED and V21Tone
|
CSCsj93041
|
H.248-VAD mismatch in both the endpoints in attached call flow
|
CSCsm50246
|
VXSM not accepting silenceSupp:off when event descriptor is applied.
|
CSCsm96582
|
Crash Observed while executing COT: Task: 0x87ef72a0 MEGACO MCC
|
CSCsm04542
|
Wrong PVC state replication after vxsm switchover when dpvc timer= 12000
|
CSCsl11653
|
Megaco PPC observed on applying events after switchover on TranscodingGW
|
CSCsl80823
|
Standby Fails with tDspApi Exception
|
CSCsm07737
|
AnnexA for G723:Call is not established according to codec in SDP
|
CSCsm45644
|
MG does not upspeed after VXSM switchover for CA controlled T38
|
CSCsl89676
|
M3UA: Unable to add links in linkset during load conditions.
|
CSCsm87178
|
500 Internal Gateway error returned for ptime not present in Local
|
CSCsm68945
|
MegacoPPC exception on sending different payloadtype in L&R of Modify
|
CSCsm87531
|
False Confirmed TTY Detection seen at 5.3.10.207
|
CSCsm07681
|
H248 MG gives Unsupported media type for IPIP call with G729A & RV=0ff
|
CSCsm23206
|
H248:-Hung RTP termination exists on STANDBY card.
|
CSCsm55027
|
A delay of 1 is observed in 902 SVC during VXSm switchover for ETSI profile
|
CSCsm45885
|
AUCX is not publishing Calea parameters
|
CSCsm75783
|
Voice drop for Initial 4-8 Seconds seen on a customer deployment
|
CSCsm04072
|
When CA ack with ver=3 then after switchover MG is not coming in service
|
CSCsm61275
|
VXSM DSP failure triggers VXSM switchover
|
CSCsl87977
|
AnnexAB:VAD is OFF even when AnnexB is implicit in G729 name string
|
CSCsl87344
|
AnnexB:VAD parameter different at two endpoints of same call with G729codec
|
CSCsm04236
|
Corruption in irm database when dncon-upcon is done and dpvc timer is -1
|
CSCsl93607
|
Task tDspApi gives an exception while playing announcement with RV on
|
CSCsm57394
|
VXSM remains in OOS state, when it receives unauthorized messages
|
CSCsm04364
|
Error message 210 is not received when calea call sent on nonCalea image
|
CSCsm04483
|
No error message received if es-cci/es-ccd/port is missing
|
CSCsm04420
|
Error 211 not received for calea call established for low bandwidth
|
CSCsm04380
|
Error 213 not received when calea enabled in MDCX, in case of delay
|
CSCsl87097
|
AnnexAB:VAD incorrect in dumpCcb for G729/G723 calls due to s:<on/off>
|
CSCsm12464
|
One-way Voice Path when CLEARCHANNEL is used as mid-call codec
|
CSCsk17259
|
Transcoding:Data Bound Exception when New EventBuffer descriptor is sent
|
CSCsl56709
|
435 observed when switchover an switchback is done with RV ON
|
CSCsi58210
|
Upspeed is not happening in AAL2 after changing vbd codec by cnfcid
|
CSCsi46857
|
DS3 Alarms are not logged in PXM log when payload of OC3 line is DS3
|
CSCsk94545
|
IUA-MGCP SLT: VXSM goes into Failed state while changing upspeed codec.
|
CSCsk21076
|
Remote absent on one of the IP legs, when Relay set to false
|
CSCsj60070
|
Incorrect ttycodec selected for E1 mode when adding new tty profile
|
CSCsk76180
|
Incorrect display of dspcodeccnts for EFR after VXSM switchover
|
CSCsj97117
|
H248:Incorrect vbd codec selected for E1 mode on adding new vbd profile
|
CSCsk44560
|
After switchover bearer is successful even topology is isolate.
|
CSCsk98413
|
GW is not sending NTFY to MGC with observed event {ctyp/dtone{dtt=CNG}}.
|
CSCsk43122
|
Even after SC (restart) rejection the assoc with SBC is UP.
|
CSCsk04438
|
Problem while forced H248oos: Failed to modify H248 association!
|
CSCsk22938
|
Context Audit on Emergency for Emergency call is not working correctly
|
CSCsj48391
|
H.248 - MG gives 515 error for iLBC when RV is off
|
CSCsj68164
|
dspcodeccnt counter clears after VXSM switchover
|
CSCsl55325
|
Error: Exceed maximum PVC! occurs when add connection IP for the 4th Co
|
CSCsj03370
|
VXSM switches during call waiting scenario.
|
CSCsm25925
|
H248: SC with reason 901 should be sent on redirection before registration
|
CSCsl39311
|
Display Daughter Card's SRR registers during DCAP Exception
|
CSCsl37094
|
Standby goes to failed state in mid-call codec change with ecan ON.
|
CSCsl76488
|
M3UA-MGCP:Card went into FAILED State after inhibiting ss7links & reset.
|
CSCsl54242
|
Standby goes to Failed state with tDspApi Instr. Bound Exception
|
Resolved Caveats in Release 5.3.10.201
Table 7 describes the caveats that are resolved in VXSM Release 5.3.10.201.
Table 7 Resolved Software Caveats in VXSM Release 5.3.10.201
DDTS Issue
|
Description
|
CSCek70797
|
Fax fails on T.38 devices when call starts at G729
|
CSCek71988
|
Offline diagnostics of DSP fails
|
CSCek70797
|
Fax fails on T.38 devices when call starts at G729
|
CSCek70878
|
VXSM mgcgwdn mismatch results in COT failure
|
CSCek70228
|
H.248:Hung RTP terminations due to res dealloc failures in CRML
|
CSCek70227
|
H.248:Megaco PPC task suspended when stuck in a for loop.
|
CSCek70118
|
VXSM H.248 returns Pending transactions
|
CSCek70226
|
H.248:Out of resource error due to CDB leak.
|
CSCek70116
|
VXSM sends incorrect H.248 error code 500 when no termination matches
|
CSCek67800
|
H248:Restart SC should be sent on redirection before registration
|
CSCsh15755
|
SS7 trunks stay at TERM_ACTIVE_IDLE after TGCP OC3 VXSM cnfgwoos
|
CSCek69459
|
MGCP T.38:Upspeed fails when remote port changes during T.38 switch
|
CSCek68407
|
cant cnfgwdn or adddnsdn after upgrade to 5.3(10.200)
|
CSCek60744
|
Calls not cleared in MG while H248 Midcall Codec change call rate test
|
CSCek68398
|
H248:CED not re-enabled on 1300Hz detection (during V.90 ups)
|
CSCek68160
|
DSP Knob cnfdsp -ec does not work
|
CSCek68159
|
Default PLC config does not take effect during call-setup
|
CSCek54391
|
cnfvifparam NonLinearProcess 2 disable does not work
|
CSCuk61637
|
VXSM stays in service after an Unauthorized message from CA
|
CSCek65372
|
VXSM OC-3 TGCP could not handle RQNT with cot
|
CSCek63961
|
T.38 with fallback to G.711
|
CSCek66095
|
Modify command failure from CRML is returned as success to MGC.
|
CSCuk61635
|
VXSM replies with Internal Gw error to a Modify in a T38 call
|
CSCek65910
|
Standby Card resets frequently
|
CSCek65479
|
VXSM failure in response to resource allocation request
|
CSCek64573
|
VXSM cli stops working after adding 1st session grp when 2nd exists
|
CSCek64524
|
VXSM gives err-442 when Term-desc is not at first pos in Media desc
|
CSCek65232
|
Cisco MGX did not recover from call server sequential restart
|
CSCek63961
|
T.38 with fallback to G.711
|
CSCek62444
|
SDP Attribute X- Parsing
|
CSCek56163
|
Toolkit Crash during Mem Free
|
CSCek60782
|
SDP Parameters String Copy Corrections
|
CSCek61398
|
VXSM crashes when SDP contains long strings
|
CSCek60782
|
SDP Parameters String Copy Corrections
|
CSCek61398
|
VXSM crashes when SDP contains long strings
|
CSCek60782
|
SDP Parameters String Copy Corrections
|
CSCek59917
|
Toolkit Memory Corruption with SDP Parameters > 10 bytes
|
CSCek61396
|
VXSM Crashes with audit on RTP in Null Context
|
CSCek61259
|
Double free in tVsi slave
|
CSCek60782
|
SDP Parameters String Copy Corrections
|
CSCek60784
|
Remove 435 Error Code
|
CSCek59071
|
Progress Tone modification for German Ring back tone cadence.
|
CSCek57817
|
VXSM rejected call with 400 msg (due to resource leak from hairpin?)
|
CSCek58493
|
Compare strings failed because of null string pointers
|
CSCek55569
|
Standby card recreate failed by NULL ldibptr
|
CSCek58229
|
154 bytes of a-X-cluster causes PPC exception
|
CSCei56675
|
Need to interop with linksys ATAs using odd RTP port numbers
|
CSCek57550
|
cnfgwoos failed to clean up dangling call legs
|
CSCek54040
|
Mix codec calls with COT enabled on BTS caused vxsm VTSP crash
|
CSCek56325
|
VXSM should ignore unsupported codec
|
CSCek57181
|
increase TM_MM_BUFF_NT_ADDR buffer from 2 to 20 bytes
|
CSCek52060
|
dsm debugging logging support
|
CSCek55130
|
enhancement to store the MB & dcap exception in BRAM
|
CSCek52060
|
dsm debugging logging support
|
CSCek55130
|
enhancement to store the MB & dcap exception in BRAM
|
CSCek53543
|
Dual PVC failure will not recover if failure threshold is 2
|
CSCek38528
|
enable card switch-over if IOS tasks crash
|
CSCek56341
|
Need to hung CCB detection task in standby VXSM
|
CSCek56159
|
RTP terms left hanging on standby even after deleting the call
|
CSCek56719
|
RQNT followed by mid-call codec change and subsequent call fails
|
CSCek54076
|
Adding tone-gen on/off response time stats to DSPAPI perf suite
|
CSCek53969
|
DSM rejects some DSP responses with no pending requests error
|
CSCek55602
|
Mem Leak in MGCP app
|
CSCek55865
|
Time duration too long (~48hrs) for audit on NULL context
|
CSCek54219
|
Double open in standby VXSM
|
CSCek52935
|
VXSM intermittently uses G723 resources instead of specified G711
|
CSCek54902
|
CCAPI memory leak when handling disconnect timeout
|
CSCek54911
|
Standby card crashes with DSP channel exception
|
CSCek52788
|
Inconsistent severity and huge amount of H248 log messages
|
CSCek54015
|
Memory leak in DSPAPI buffers on the daughter card
|
CSCek52027
|
semGive error in PXM log
|
CSCek52788
|
Inconsistent severity and huge amount of H248 log messages
|
CSCek27498
|
After switchover
|
CSCek52939
|
Long delay in pipc processing when other cards are reset
|
CSCek14798
|
Sub all/double ADD on actv results in stby recreate failure
|
Table 8 describes the caveats that were opened after Release 5.3.10.200, but are now resolved in VXSM Release 5.3.10.201.
Table 8 Resolved Software Caveats for VXSM Release 5.3.10.201
DDTS Issue
|
Description
|
CSCek41878
|
VXSM returns 500 error for Add command after many TDMHP calls w/ecan
|
CSCek45680
|
Long response delay for Subtract command
|
CSCek46762
|
NTE payload advertisement needs to have the full fmtp range
|
CSCek49354
|
VXSM DS0 in PN state when ADD+AV+AV sent within microsec
|
CSCek50798
|
SUB+AV(root)+AV(all) sent to same DS0 within microsec->wrong AV
|
.
Related Documentation
The following documents contains information that may be useful to software Release 5.3 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.3: A Guide to User Documentation.
•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.3.10
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
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo 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. (0805R)
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.
© 2008 Cisco Systems, Inc. All rights reserved.
Feedback
