Guest

Cisco MGX 8880 Media Gateways

Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.6.00

  • Viewing Options

  • PDF (228.9 KB)
  • Feedback
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.6.00

Table Of Contents

Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.6.00

Contents

About This Release

New Features in Release 5.6.00

RTP Multiplexing

Usage Guidelines

DSP RAS and Memory Error Detection

Usage Guidelines

Support for Text Over IP

Usage Guidelines

T38-VBD Interworking for Fax Over IP

V23 Support with Increased Channel Density

Usage Guidelines

NSE Negotiation Based VXSM Up-speed

Firmware Images

Upgrading from an Earlier VXSM Release

Interrupted Procedure Recovery

Feature Clarifications

Call Rate Performance Support

Online Diagnostics Feature as Applied to VXSM

DSP Resources Under Mixed Codec Conditions

Restrictions

VXSM Management Information Base

Service Module Support by Platform

Compatibility

Caveats for VXSM Release 5.6.00

Open Caveats in Release 5.6.00

Resolved Caveats in Release 5.6.00

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.6.00


Revised: November 29, 2011, OL-23364-02

Contents

About This Release

New Features in Release 5.6.00

Firmware Images

Upgrading from an Earlier VXSM Release

Interrupted Procedure Recovery

Feature Clarifications

Call Rate Performance Support

Online Diagnostics Feature as Applied to VXSM

DSP Resources Under Mixed Codec Conditions

Restrictions

VXSM Management Information Base

Service Module Support by Platform

Compatibility

Caveats for VXSM Release 5.6.00

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

About This Release

The VXSM Release 5.6.00 follows VXSM Release 5.5.11. The resolved caveats for VXSM Release 5.6.00 are listed in Table 4.

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.6.00 and Cisco Voice Switch Services (VXSM) Command Reference, Release 5.6.00, both of which are available on cisco.com.

New Features in Release 5.6.00

Release 5.6.00 is a significant release with several major new software features over Release 5.5.11.

The new software features include:

RTP Multiplexing

DSP RAS and Memory Error Detection

Support for Text Over IP

T38-VBD Interworking for Fax Over IP

V23 Support with Increased Channel Density

NSE Negotiation Based VXSM Up-speed

RTP Multiplexing

RTP Multiplexing enables VXSM to optimize the use of IP bandwidth between two gateways. VXSM achieves this by reducing the RTP header size and multiplexing different RTP session's payloads into a single UDP payload. In RTP Multiplexing, the RTP sessions destined for a particular IP address are multiplexed into a single IP datagram. The following commands were added to support this feature:

cnfrtpmux

dsprtpmux

Usage Guidelines

Follow these guidelines when you configure the RTP Multiplexing:

To enable In Service upgrade, you have to configure the gateway to OOS.

RTP Multiplexing is supported only for the Tandem Gateway (TGW) codec template. Feature support is available only for G729 and G.723 codec families. It is not supported for Data and Fax/T.38 calls.

RTP Multiplexing is not applicable for SII and Calea calls. That is, these calls will not be multiplexed. However, MUX is supported on Calea images for normal voice calls.

RTP Multiplexing is supported only on an OC3 VXSM card.

VXSM will not initiate RTP Multiplexing on endpoints which have moved to voice mode after Modem/ Fax transmission.

VXSM will stop RTP Multiplexing for calls which are IP forwarded.

RTP Multiplexing is not supported for H.248 protocol in Release 5.6.00.

VXSM initiates RTP Multiplexing only if there are at least three calls having the same source IP and destination IP pair.

VXSM does not support multiplexing for intra-card calls even if IPs are different.

There is a DS0 density impact when RTP Multiplexing is enabled. The total DS0 capacity impact would be 384.

While VXSM is used for AAL2 trunking, if you want to run the RTP Multiplexing commands, you have to first delete all the CIDs.

If online or offline diagnostics is enabled on a VXSM card, you have to disable it before you run the RTP Multiplexing commands.

You have to delete SS7, LAPD, and CAS signaling links before you enable RTP Multiplexing.

DSP redownload must be disabled before enabling the RTP Multiplexing commands.

DSP RAS and Memory Error Detection

Before Release 5.6.00 (for MGCP protocol, it is before Release 5.5.11), when a DSP core fails in an active VXSM, the standby VXSM takes over the active card's role. If the DSP core fails in a standby VXSM, then it reboots the standby VXSM. In such a case, if the active VXSM also fails due to some reason, then there is a complete outage for 3 to 5 minutes. When a DSP core fails in a standalone VXSM, the failed DSP core is marked as a bad core, along with other sibling cores in the DSP chip. In such a case, the existing calls on the affected DSP chip are dropped and no new calls are allowed. In Release 5.6.00, these issues are resolved with the implementation of DSP RAS feature. The following commands were added to support this feature:

cnfDspRedownload

dspDspRedownload

Usage Guidelines

Follow these guidelines when you configure DSP RAS and Memory Error Detection:

VXSM drops T.38 calls when the DSP core where the calls reside fails (VXSM as active in redundant mode or in standalone mode). VXSM exhibits similar behavior if the card was switchover.

DSP-RAS cannot be enabled simultaneously with other new 5.6.00 feature RTP Multiplexing.

DSP-RAS feature is not supported on VXSM cards used as a Transcoding Gateway.

Support for Text Over IP

Text over IP (ToIP) is a means of providing a real-time text service that operates over IP-based networks. TTY text phones use ToIP for transmitting messages from one phone to another. VXSM supports Text Relay and TTY Upspeed for transmitting text characters using TTY phones. The following commands were added to support this feature:

cnfTextRelayprof

delTextRelayprof

Usage Guidelines

Follow these guidelines when you configure Text Relay:

VXSM Text Relay does not guarantee the support of third-party gateways.

Text Relay feature is supported only with the FMC template.

VXSM as an IP-IP gateway supports Text Relay feature only for transcoding and transparent IP-IP voice calls. Text Relay is not be supported in fast-routing mode.

T38-VBD Interworking for Fax Over IP

In Release 5.6.00, VXSM supports T38-VBD interworking for fax over IP. VXSM acts as a transcoding gateway and provides the interworking functionalities.

V23 Support with Increased Channel Density

With Release 5.6.00 and later versions, the channel capacity is increased to 30 channels when the V23 FSK detector is enabled.

Usage Guidelines

Follow these guidelines before you enable this feature:

Association between VXSM and CA should be Out of Service.

Delete all the CIDs if VXSM is used for AAL2 trunking.

Delete all LAPDs, SS7 links, and CAS endpoints.

Delete online or offline diagnostics for the particular VXSM slot.

V23 feature is supported only on the VXSM OC3 card.

V23 feature is supported only for H.248 Call Control protocol.

VXSM slot must be configured in H.248 protocols.

RTP Multiplexing must be disabled to enable V23 feature but vice versa is not true.

MIB support for V23 mode is supported only for the TGW and TGW2 templates.

NSE Negotiation Based VXSM Up-speed

From Release 5.6.00, in gateway controlled mode, VXSM upspeeds upon detecting the modem tones only when the NSE negotiation is successful in the Call Signaling. You can enable this feature by using the cnfNseNegoUpspeed command. This command is supported in both the xGCP and H.248 protocols.

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.

Both CALEA and Non-CALEA images 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 LI based on SII architecture for H.248, TGCP and MGCP protocols. The PktCable CALEA is supported only with MGCP and TGCP protocols.

VXSM supports four different Codec templates; Tandem Gateway (TGW), Tandem Gateway 2, Fixed Mobile Convergence (FMC), 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.4.21 or later.


Note VXSM supports upgrade of non-CALEA to CALEA firmware. But upgrade from CALEA to non-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.6.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.

Prior to upgrade, user should confirm that additional termtypes (other than the defaults) have not been configured for VXSM in H.248.


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

Call Rate Performance Support

VXSM OC3 Card supports the following call rates:

In MGCP, the maximum CPS supported is 60 (without signaling). If signaling (M3UA/IUA/RUDP) is configured, then the maximum supported CPS is 50.

In H.248, the maximum CPS supported is 85 (without signaling). If signaling (M3UA/IUA) is configured, then the maximum supported CPS is 50.

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
=====================================================================
                    DSP codec capacity usage
=====================================================================
 
   
Codec pool                Current utilized        Current available
                        capacity (#DSP chans)   capacity (#DSP chans)
==========              =====================   =====================
G711 family/HDLC            179                       7885             
G729/G726/T.38 family       0                         3919             
G723 family                 0                         2911 
 
   

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.

Restrictions

This section includes information about restrictions pertaining to performance and the recommended actions:

If the G.723 codec is not used as a voice codec, then disable all variants of the G.723 codec using the cnfcodecparam command.

If the G.723 codec is enabled but not used in voice calls, then ensure that the codec list is specified without the G.723 codec while creating a call. If no codec is specified while creating a call on VXSM, then the resources for the G.723 codec are reserved. This affects the normal resource allocation algorithm, which in turn results in anomalous behavior of VXSM.

VXSM Management Information Base

The VXSM Management Information Base (MIB) Version 5.6.00 is available to users with CCO accounts who can access the MIB and VXSM software on-line at: http://www.cisco.com/public/sw-center/index.shtml


Step 1 Log on to http://www.cisco.com/public/sw-center/index.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 5500) to display a list of downloadable files.

Step 4 Click on the desired file (for example, mgx8850-fw-5500.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 mgx8850rel5500mib.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.6.00 is supported only with PXM-45/B and 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.6.00

5.4.30

MGX-RPM-XF-512

12.4(15)T13

12.4(15)T9

CWM

16.0.00 patch 2

16.0.00 patch 2

CTM

9.2

9.2

VISM-PR

3.3.35.201

3.3.25

AXSM-16-T3/E3/B

5.6.00

5.4.30

AXSM-16-155-XG

5.6.00

5.4.30

AXSM-8-622-XG

5.6.00

5.4.30

MPSM-16-T1E1

5.6.00

5.4.30

MPSM-T3E3-155 (8850 only)

5.6.00

5.4.30

BTS

6.0

6.0

PGW

9.8

9.8

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.6.00 for VXSM.

Table 2 Software Images for Release 5.6.00 for VXSM 

Board Pair
Latest Boot Code Version
Minimum Boot Code Version
Firmware

MGX-VXSM-155, CALEA

vxsm_005.006.000.200_bt.fw

vxsm_005.004.021.200_bt.fw

vxsm_005.056.000.200.fw

MGX-VXSM-155, Non-CALEA

vxsm_005.006.000.200_bt.fw

vxsm_005.004.021.200_bt.fw

vxsm_005.006.000.200.fw

MGX-VXSM-T1E1, CALEA

vxsm_005.006.000.200_bt.fw

vxsm_005.004.021.200_bt.fw

vxsm_005.056.000.200.fw

MGX-VXSM-T1E1, Non-CALEA

vxsm_005.006.000.200_bt.fw

vxsm_005.004.021.200_bt.fw

vxsm_005.006.000.200.fw

MGX-VXSM-T3, CALEA

vxsm_005.006.000.200_bt.fw

vxsm_005.004.021.200_bt.fw

vxsm_005.056.000.200.fw

MGX-VXSM-T3, Non-CALEA

vxsm_005.006.000.200_bt.fw

vxsm_005.004.021.200_bt.fw

vxsm_005.006.000.200.fw


Caveats for VXSM Release 5.6.00

This section describes software caveats for Release 5.6.00.

Open Caveats in Release 5.6.00

Table 3 describes the open caveats in VXSM Release 5.6.00.

Table 3 Open Software Caveats for VXSM Release 5.6.00 

DDTS Issue
Description

CSCth61546

Headline: M3UA Load: Standby VXSM reboots when the same core is killed twice back- to-back.

Symptoms: Standby VXSM reboots when the same core is killed twice back- to-back.

Conditions: This issue is seen when the same core is killed twice 5-10 seconds after the re-download.

Workaround: None.

CSCth64133

Headline: Standby VXSM resets on first core kill with full DSP capacity of calls.

Symptoms: Standby VXSM resets on first core kill with full DSP capacity of calls.

Conditions: This issue is only seen when the card is at full capacity and 80 cps.

Workaround: None.

CSCth76631

Headline: When card goes to active-F state after a DSP crash, all calls are deleted.

Symptoms: All active calls on the card are deleted when a DSP crash happens on a standalone card.

Conditions: Card should be in standalone mode.

Workaround: Add VXSM redundancy baseline behavior.

CSCth79803

Headline: Standby VXSM card reloads unexpectedly.

Symptoms: Standby VXSM reboots with CRML-ERR: REDM error.

Conditions: While processing back to back Modify on standby VXSM under load conditions, when the DSP responses for the first modify is delayed, the second modify comes before that. This is a rare race condition.

Workaround: None.

CSCth87422

Headline: IUA-H.248: VXSM resets intermittently on high cps while killing a lapd core.

Symptoms: VXSM resets intermittently on high cps while killing a lapd core.

Conditions: This issue occurs intermittently on high cps after a DSP crash on a lapd core.

Workaround: None.

CSCti18177

Headline: The dspsctps command shows wrong MGC IP when two IPs are configured for a single active MGC.

Symptoms:  The dspsctps command shows wrong MGC IP when two IPs are configured for a single active MGC.

Conditions: Occurs when two IPs are configured under one MGC and one of the IP is in down state or does not exist actually.

Workaround: This is a display issue, hence collect the SCTP traces to verify the IPs.

CSCti27515

Headline: Standby VXSM reboots intermittently on mixed load after 48 hours.

Symptoms: Standby VXSM reboots intermittently on mixed load after 48 hours.

Conditions: Mixed load of FAX, VBD and Voice calls.

Workaround: None.


.

Resolved Caveats in Release 5.6.00

Table 4 describes the caveats resolved in VXSM Release 5.6.00.

Table 4 Resolved Software Caveats for VXSM Release 5.6.00

DDTS Issue
Description

CSCsz68941

Transcoding: 515, unsupported_Media_Type observed after reaching maximum capacity.

CSCta92871

Silent modification of local SDP when L and R SDPs not present in modify.

CSCta92898

VXSM does not come up with negotiated version after switchover.

CSCtc30560

V.23 FSK detection parameters change.

CSCsy70745

XGCP: Calls showing wrong codec pool after doing VXSM card switchover.

CSCtc61447

H.248: Ecan is enabled during call on clearmode.

CSCtd54868

H.248: Variant VAD behavior when midcall codec change done from AMR.

CSCtb88177

NSE dropped in Modify when payload 100 sent for G.729 and 101 for NSE.

CSCte10725

Wrong error message received on issuing dsph248calls for non-existing GW link id.

CSCte08939

No error returned when cnftermtype is done for non existing profile.

CSCte16743

H.248: invalid cac utilization when call moves from VBD to T38.

CSCtc05130

V21 is not notified after sw in case of back to back CA -T38 FAX.

CSCtd60280

MGCP: Call got deleted after switch over when TTYupscodec and vbdupscodec is same.

CSCtd74250

VXSM: false detection of Bell202 tone.

CSCte10343

NTE missing in response when modify is sent with only local descriptor.

CSCtd90796

Bearer fails while adding third RTP leg.

CSCte14919

TGCP: Gateway accepts config for unsupported codec as upscodec with cnfvbdprof.

CSCte16886

NSE is returned in audit response even when none is configured on transcoding gateway.

CSCte18857

G.711u is not accepted as upspeed codec in sdh mode.

CSCte27793

The cnftermtype command allows to configure non-existing event mapping.

CSCte19130

MGX 505: Unsupported remote connection descriptor error.

CSCte43403

CLI: Wrong information displayed with dspttyprof.

CSCte49683

TOIP: Wrong information displayed with dsptextrelayprof.

CSCte48530

G.711u configured as upscodec in vbdprof is not journelled on standby.

CSCte48863

dsph248call -term does not give error for wrong termination id.

CSCte43409

CLI: dspvbdprof showing wrong error message.

CSCte45562

Gateway does not send error reason with error code 515 for RQNT.

CSCte48914

NSE is missing in audit when done after MF is sent with only local descr.

CSCte48561

XGCP: DLCX is not processed if previous transaction response is pending.

CSCte48697

MGCP: 534 error returned if optional parameters of AMR not present in SDP.

CSCte52483

NSE is missing when modify is sent with only local descr and AnnexAB True.

CSCte11392

MGCP-NTE, NSE not returned in AUCX after switchover.

CSCte50370

MGCP: 402 error returned without text description.

CSCte74753

MGCP: 401 error returned without text description.

CSCtd45798

MGCP: Standby fails when requested events (R:) is sent in Modify.

CSCte18646

MGCP: Digits not generated when played as signal requests after VXSM SW.

CSCte45516

Improper VXSM behavior when detection for multiple digits sent in etd ev.

CSCte75562

Discrepancy in MDCX response (NTE not returned) after midcall codec change.

CSCte77785

No error reason for 410 while sending crcx in loop for wildcard char '$'.

CSCte52507

MGCP: Fax failed after cot event detection on endpoints.

CSCte54800

The dspconcacs command shows VAD calls when call is in T38 mode.

CSCte61639

GW does not send error reason wd error code 502.

CSCte90037

"Instruction Bound Exception" error message after executing CLI command.

CSCte10315

GW fails to switch to PCMU codec sent in modify during CA controlled VBD.

CSCte69093

MGCP: New CRCX is not NACKed, during previous DLCX processing.

CSCte83453

VXSM replies with "NTE" instead of "telephone-event" in rtpmap.

CSCtf19280

NTE missing in response when only local descriptor is sent after T38 FAX.

CSCte52538

Received same payload for NTE and NSE on sending same payload for CODEC and NSE.

CSCte97775

Wrong BAD dsp core count on successive dsp crashes in standalone VXSM.

CSCtf22055

VXSM return syntax error in reply of 901 if er=507 is sent in response.

CSCtf38982

MGCP: End point upspeeds to vbd with modem tone on nsenego failed.

CSCtf19631

MGCP exception caused card reload.

CSCtf22258

MGCP: Available signal capacity is 99% even if all the channels are used.

CSCtf24985

MGCP: VXSM is replying with NSE, even though MDFY is sent without NSE.

CSCte90086

GW respond with NSE on sending different NTE/CODEC payload in MDCX after S/W.

CSCte18735

MGCP: End point deleted on T38-fallback with none upscodec (cnfvbdprof).

CSCte49204

VXSM sending NSE 194 for CA controlled VBD.

CSCtf64336

Exception is observed when delvif is done for vif configured with cas.

CSCtc76345

VXSM failed to detect V.23 FSK signal.

CSCtf24943

506 observed when sessionID and version >32 character are sent in online remote.

CSCtf68924

500 observed when only RTP added with signal cg/rt played in FMC.

CSCtf47534

MGCP: GW does not re-transmit RSIPs in case of path fOOS.

CSCtf95327

MGCP: Call failed to downspeed during Ca control vbd call.

CSCte89932

XGCP: Midcall codec change to be always supported in Data Mode.

CSCtf89752

Mid call modify to ilbc mode 30 is unsuccessful.

CSCtg09018

MGCP: With Cacnt vbd call jitter mode is adaptive during data mode.

CSCtf45597

VXSM throws error while trying to re-config the vifterm in sonet mode.

CSCtg10764

VXSM crashes with exception on modifying Jitter value in Modify.

CSCtf35288

VXSM switchover due to DSP crash.

CSCtf95438

MGCP: Standby resets on sending 'invalid' mode in MDCX with r:cl.

CSCtg26770

Sending Modify in T38 causes hung termination.

CSCtf38932

H.248-SLT: VXSM failed with exception on issuing cnfh248oos 1 1.

CSCtf98136

Upgrade: V23 mode configuration gets lost during Calea to Calea upgrade.

CSCtg18876

Gather failures in Data mode should not be logged in crmlstats.

CSCtf68851

CRML's cmReq buffers exhausted due to SSRC collisions on 48E1T1 VXSMs.

CSCtg43310

Wrong Rx min Jitter in stats after on playing voice file after DTMF.

CSCtf89579

SS7 error generated on m3ua load with v23 enable on H.248.

CSCte49639

INTEROP: Association not coming in IS with PGW after issuing OOS and INS.

CSCtf51279

MGC handoff: H.248 - sctp closes on mgc switchback.

CSCtg37982

MGCP: 911 call is not cleared on deletion after NTFY rel(o) w/o ack.

CSCtg71195

Info about bitrate needs to be updated in FS when G723 is sent in Add.

CSCtg93463

911 test call failed.

CSCth13195

VXSM CPU spikes when using dsph248cnts -assoc command.

CSCtf38764

V21 Modem call failing due to ECAN divergence.

CSCtg31962

H.248: dsph248calls command takes wrong parameters and shows no error.

CSCth00777

Wrong jitter info returned in audit response after midcall codec change.

CSCtg78564

VXSM resets due to SSI-3-EXCEPTION.

CSCtf64566

H.248: Ecan is not journalled after switch over.

CSCth35846

TGCP: Standby card failed on loadrev (calea 5.55.10.200-->5.55.212.52A).

CSCtg10696

H.248: ecan enabled for CCD when sent in modify.

CSCth31330

Standby VXSM 5.5.10.200 rebooted after PGW did a failover.

CSCth35989

MGCP: Standby card failed on loadrev (5.4.21.200-->5.5.212.52A).

CSCtd54845

Hung connections detected after running mixed load.

CSCtd60216

904 observed when midcall mode change is done for codec AMR.

CSCtg93980

Standby reboots on sending T38 fax with voice codec modify.

CSCtf86862

MGX-SRT VXSM card get crashed in ToIP LOAD.

CSCth61486

CLI: VQM related CLIs getting enabled in MGCP AND TGCP.

CSCtf90557

DSM-ERR "DSP Chan not opened for processing cmd" observed on standby.

CSCtg89644

Standby reboots on sending Modify of CCD in data mode.

CSCth52130

H.248: T38 fallback to VBD not working if fallback modify contains NTE PT.

CSCtc56644

Bearer fails when third termination is added in same context.

CSCtc71568

CSCtb56008 fixed a lot of VBD buffer leaks but not all.

CSCth18642

MGCP: Blv calls not cleared on dlcx after 30 seconds of onhook from abacus.

CSCth50434

VXSM: Super G3 fax TDM via SIP-T to TDM.

CSCth64630

StandBy fails when G729AB modify is sent during FAX.

CSCth64603

Insufficient resources comes while playing fax with cngTone.

CSCth65360

The Semaphore was not being released after VXSM crash.

CSCta41674

All H.248 T.38 fax fail with internal gateway error.

CSCtb56008

VBD buffers in corner scenarios not being freed.

CSCtd19129

DTMFs not regenerated due to ill-digits.

CSCtf35799

MGCP: VXSM generated DLCX contains invalid(0) conn-id.

CSCta89596

After SIP-hold/resume or sip-hold/transfer loud clicks sent to TDM side.

CSCtf27033

T.30 CRP timer on VXSM is too low for multihop fax transmission.

CSCth80233

Standby reboots on sending the CA controlled fax with cng setting.

CSCth79572

Calls were getting removed from TGW on mid call codec change after S/W.

CSCth84630

Standby fails when midcall mode is done for AMR codec.

CSCtg48922

Echo canceler is not fully convergent in the beginning of the call.

CSCte54762

MGCP: Incorrect error message on playing the cot tone on a connection ID.

CSCth88588

DSP API errors in offline full diag test in TGCP-CABLE.

CSCth96815

Active and standby cards reboots at same time with T38 calls in MGCP-FMC.

CSCtc78687

VXSM crashes when invalid parameter is sent in topology descriptor.

CSCtf50832

Wrong active mgc address displayed in dsph248assoc, on mgc switchover.

CSCek70878

VXSM mgcgwdn mismatch results in COT failure.

CSCth65906

MGCP: NSE missing on codec change after switchover.

CSCta63529

VXSM M3UA associations never establish to Master (Active) PGW only.

CSCta89352

All PVCs went to vxsm state on vxsm due to QE chip in stuck state.

CSCtb09809

Overlapping transaction initiated by VXSM for single service change requirement.

CSCtc66969

XGCP: Disable Tone Detection on NSE negotiation failure on OEP.

CSCtd16081

VXSM sends incorrect reason, method in response of MGCIdToTry.

CSCtg21019

VXSM is not sending AIS alarms in case of down path.

CSCtg22200

Support for G.nX64,GnX64,G.Clear codec string in H.248.

CSCti07863

MGCP: Upgrade from 5.53.30.202 fails while RUDP session are down.

CSCte18646

MGCP: Digits not generated when played as signal requests after VXSM SW.

CSCte52507

MGCP: Fax failed after cot event detection on endpoints.

CSCtf22258

MGCP: Available signal capacity is 99% even if all the channels are used.


.

Related Documentation

The following documents contains information that may be useful to software Release 5.6.00 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 5.5

Cisco MGX 8880 Media Gateway, Release 5.5: A Guide to User Documentation.

Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.6.00

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