Guest

Cisco MGX 8880 Media Gateways

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

  • Viewing Options

  • PDF (213.7 KB)
  • Feedback
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.6.10

Table Of Contents

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

Contents

About This Release

New Features in Release 5.6.10

Multiple Bearer IP Pool

Usage Guidelines

Support for Alternative Codec String

Hold Tone During Warm Transfer

Increased Announcement IDs on VXSM

Ignoring Unsupported Parameters in SDP

Preference for Codec Negotiation

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

VXSM Management Information Base

Service Module Support by Platform

Compatibility

Caveats for VXSM Release 5.6.10

Open Caveats in Release 5.6.10

Resolved Caveats in Release 5.6.10

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


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


Revised: March 29, 2011, OL-23364-03

Contents

About This Release

New Features in Release 5.6.10

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

VXSM Management Information Base

Service Module Support by Platform

Compatibility

Caveats for VXSM Release 5.6.10

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

About This Release

The VXSM Release 5.6.10 follows VXSM Release 5.6.00. The resolved caveats for VXSM Release 5.6.10 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.10 and Cisco Voice Switch Services (VXSM) Command Reference, Release 5.6.10, both of which are available on cisco.com.

New Features in Release 5.6.10

Release 5.6.10 is a maintenance release with several major new software features over Release 5.6.00.

The new software features include:

Multiple Bearer IP Pool

Support for Alternative Codec String

Hold Tone During Warm Transfer

Increased Announcement IDs on VXSM

Ignoring Unsupported Parameters in SDP

Preference for Codec Negotiation

Multiple Bearer IP Pool

The Multiple Bearer IP Pool feature allows interworking between two or more gateways residing on different private networks. VXSM acts as an interconnect gateway and provides different set of IP addresses for each private network based on a pre-defined rule on the call agent (PGW).

Release 5.6.10 and later releases support this feature.

Usage Guidelines

Follow these guidelines when you configure a multiple bearer IP pool on VXSM:

Supported on all codec templates for the H248 protocol.

Supports all card types such as T1, E1, OC3, and so on.

Supports a maximum eight of bearer pools.

Supports minimum zero and a maximum of eight bearer IPs in each pool.

VXSM shall support two new packages vpnd and evpnd while creating pdn termination.

Pools can be shared across different Virtual Media Gateways (VMG).

The default pool name is networkA.

For Multiple Bearer IP Pool feature, the following commands were added:

addBearerPool

Adds bearer pools.

cnfBearerPool

Configures the bearer pools.

delBearerPool

Deletes a bearer pool.

dspBearerPools

Displays all the bearer pools added on a gateway.

cnfBearerIPPool

Configures the IPs in a bearer pool.

dspBearerIPPools

Displays all the IPs configured under a bearer pool.


Support for Alternative Codec String

Release 5.6.10 introduces support for alternate strings for existing codecs. Presently VXSM supports only standard codec strings such as PCMU, G.711u, and so on. This feature enables VXSM to use the alternate strings in addition to the existing standard strings. The following call control protocols support this feature:

H.248

MGCP

The feature supports these codec templates:

TGW and Wireline: Supports G.711, G.723, G.723.1a, G.726, G.729, G.729A, and Clear Channel.

Cable: Supports G.711 and iLBC.

TGW2: Supports G.711, G.726, G.729A, iLBC, and Clear Channel.

FMC: Supports G.711, G.726, G.729A, AMR-NB, GSM-EFR, and Clear Channel.

For the Support for Alternative Codec String feature, the following commands were added:

cnfcodecstring

Specifies the alternate codec strings for VXSM.

dspcodecstring

Displays the alternate codec strings for a specific adaptation type and codec.


Hold Tone During Warm Transfer

This enhancement introduces a new type of hold tone during a warm transfer. The new tone is played during the warm transfer period. Only MGCP protocol supports this enhancement.

For the Hold Tone During Warm Transfer feature, the following commands were modified:

cnfvifccode

Configures a specific country code in a voice interface.

dspvifccode

Displays country code configured for a specified Voice Interface.

dspvifccodes

Displays country code configured for all the Voice Interface.


Increased Announcement IDs on VXSM

Release 5.6.10 increases the announcement identifiers on the VXSM from 1024 to 9924. Only H.248 protocol supports this enhancement.

For the Increased Announcement IDs on VXSM feature, the following commands were modified:

cnfannfile

Configures Announcement File.

dspannfile

Displays the configuration parameters for a specified announcement file.

dspannfiles

Displays the configuration parameters for a all the announcement files.


Ignoring Unsupported Parameters in SDP

Effective this release, when VXSM receives any unsupported parameters in a Session Description Protocol (SDP) for a codec, it ignores the unsupported attributes and does not consider that particular codec for negotiation. This prevents VXSM from rejecting the whole SDP. If a single codec is received in the m-line, and the SDP validation fails, the VXSM does not acknowledge that request. Only H.248 protocol supports this enhancement.

Also note that when VXSM receives multiple SDPs in the local descriptor with the first one with media type as VIDEO and subsequent one with media type as AUDIO, VXSM will ignore the first SDP and process the second SDP instead of returning any error, because VXSM does not support media type VIDEO. This will also apply if a single SDP is received with multiple m lines, with first one with media type as Video and subsequent one with media type as Audio. Here also, VXSM will ignore the m lines with media type VIDEO and process the first m line found with media type as AUDIO.

Preference for Codec Negotiation

This enhancement allows a user to specify the codec negotiation preference to either remote or local code. Only H.248 protocol supports this enhancement.

For Preference for Codec Negotiation feature, the following commands were added:

cnfCodecNegoPreference

Sets the codec negotiation preference.

dspCodecNegoPreference

Displays the codec negotiation preference.


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.5.00 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.10, 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.

VXSM Management Information Base

The VXSM Management Information Base (MIB) Version 5.6.10 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.10 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.10

5.5.0

MGX-RPM-XF-512

12.4(15)T14

12.4(24)T5

12.4(15)T9

CWM

NA

NA

CTM

9.2 patch 460

9.2 patch 460

VISM-PR

3.3.35.203

3.3.25

AXSM-16-T3/E3/B

5.6.00

5.4.30

AXSM-16-155-XG

5.6.01

5.4.30

AXSM-8-622-XG

5.6.01

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(1)S12P12

9.8

Cisco 2600 Series Routers

c2600-ipvoice-mz.123-9.14.T

c2600-ipvoice-mz.123-9.14.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.14.T

c3725-ipvoice-mz,123-9.14.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.10 for VXSM.

Table 2 Software Images for Release 5.6.10 for VXSM 

Board Pair
Latest Boot Code Version
Minimum Boot Code Version
Firmware

MGX-VXSM-155, CALEA

vxsm_005.006.010.200_bt.fw

vxsm_005.005.000.200_bt.fw

vxsm_005.056.010.200.fw

MGX-VXSM-155, Non-CALEA

vxsm_005.006.010.200_bt.fw

vxsm_005.005.000.200_bt.fw

vxsm_005.006.010.200.fw

MGX-VXSM-T1E1, CALEA

vxsm_005.006.010.200_bt.fw

vxsm_005.005.000.200_bt.fw

vxsm_005.056.010.200.fw

MGX-VXSM-T1E1, Non-CALEA

vxsm_005.006.010.200_bt.fw

vxsm_005.005.000.200_bt.fw

vxsm_005.006.010.200.fw

MGX-VXSM-T3, CALEA

vxsm_005.006.010.200_bt.fw

vxsm_005.005.000.200_bt.fw

vxsm_005.056.010.200.fw

MGX-VXSM-T3, Non-CALEA

vxsm_005.006.010.200_bt.fw

vxsm_005.005.000.200_bt.fw

vxsm_005.006.010.200.fw


Caveats for VXSM Release 5.6.10

This section describes software caveats for Release 5.6.10.

Open Caveats in Release 5.6.10

Table 3 describes the open caveats in VXSM Release 5.6.10.

Table 3 Open Software Caveats for VXSM Release 5.6.10 

DDTS Issue
Description

CSCtn73173

Headline: VXSM shows incorrect "Current utilized capacity (#DSP chans)" in the dspdspc output.

Symptoms: V23 mode enabled and transcoding call scenario.

Conditions: With long duration midcall codec change load(from G.729a to G.726).

Workaround: None.


.

Resolved Caveats in Release 5.6.10

Table 4 describes the caveats resolved in VXSM Release 5.6.10.

Table 4 Resolved Software Caveats for VXSM Release 5.6.10

DDTS Issue
Description

CSCti46140

VXSM gives preference to L list over Remote list in Codec negotiation.

CSCti46266

Context ID is not present while returning error 433 "term id alredy in C".

CSCti52290

Multhom: Exception observed on a specific multihoming scenario.

CSCti57042

Multhom: SW Error observed at vxsm on vxsm switch-over in specific scenario.

CSCti58826

HungCcbs are observed on IUA-Mix load.

CSCti62044

Multhom: PGW subtract some termination after PGW switch over.

CSCti67373

VXSM does not shows Active MGC in dsph248assoc when assoc is "inservice".

CSCti69720

Unknown emergency calls on VXSM lines.

CSCti90324

Upgrade fails on VXSM calea from 5.53 to 5.55.11.

CSCtj21642

VXSM: Echo heard in the call due to difference in input and output Sign.

CSCtj32836

RTP-MUX: MUX not getting disabled after running specific call.

CSCtj58789

H248: Memory leaks observed under a particular call flow.

CSCtj58902

SDP-Nego: Discrepancy in dspcodecnegoprefrence and cnfcodecnegoprefrence.

CSCtj59192

Context ID is not present while returning error 433 in hairpin call.

CSCtj61504

Cannot add more than 9927 announcement files.

CSCtj64019

RTP-MUX: printf statement observed on enabling MUX.

CSCtj70175

SDPnego: dspcoedcnego and cnfcodecnego should display the same options.

CSCtj72749

Jitter values changing after mid-call codec change during modem upspeed.

CSCtj74349

Getting Printf (xlat_tlv_to_shadow()) M3UA Load.

CSCtj74841

dspquerydspstats CLI is not working with termId option.

CSCtj81968

VXSM reboots on loading the image.

CSCtj82161

904 termination malfunctioning observed on transcoding gateway.

CSCtj94721

VAD is getting enabled after mid-call codec change during modem upspeed.

CSCtk00201

904 observed when fallback is done to voice codec.

CSCtk02646

"Instruction Bound Exception" occurred on VXSM.

CSCtk15444

MGCP: GW notifies with operation complete after core kill if RAS enabled.

CSCtk18117

MGCP: CodecStr:GW returns wrong sequence if multiple strings given in LCO.

CSCtk18791

CAS DS0 stuck in Remotely Blocked State.

CSCtk31785

Add is not nacked if vrfname and local IP mismatch.

CSCtk34226

Call is not getting downspeeded once upspeeded on detecting CNG/CED tone.

CSCtk34417

Standby vxsm reboots on adding bearerconip.

CSCtk35807

MGCP: discrepancy in default value configuration with dspcasgencfg.

CSCtk54104

Insufficient resources observed while sending Add after reset.

CSCtk54105

H248: Exception observed with invalid vrf_name on mdcx.

CSCtk56346

StandBy VXSM goes to FAILED/ACTIVE state.

CSCtk61885

Card reboot due to modify subtract came with 1 ms.

CSCtk62201

MGCP: GW does not allow ecan modification after downspeed.

CSCtk95018

dspcodecnego gives wrong default value after upgrade from 5.6(0.200).

CSCtl01267

Missing O and S lines from OGW's SDP.

CSCtl03807

Resource dealloc error observed on switchover of transcoding GW.

CSCtl08078

H248: CDBs are not being freed which results in command failures.

CSCtl19980

MPSM reset: Card reset on LowLayerDown.

CSCtl21935

Standby VXSM goes to failed or active state with change in DNS entry.

CSCtl22673

Enabling Stats while configuring or adding new connection is not working.

CSCtl22897

Exception occur on transcoding gateway.

CSCtl41969

MUX not getting disabled after call forwarding.

CSCtl44489

Incorrect logs on PXM when switchside link comes up before timer expiry.

CSCtl48520

ECAN mismatch after downspeed when Ecan:off is sent during upspeed.

CSCtl50182

RTP MUX gets enabled in FMC template.

CSCtl52274

Hung ccb observed after giving invalid port.

CSCtl52635

GW reject modify when Fax is passing with upspeed codec as none.

CSCtl55013

Fmtp line dropped in running specific call flow.

CSCtl55836

Error not received if unsupported value (any-amit) given for mode.

CSCtl57547

Periodic false dtmf detection.

CSCtl57864

clrchancnt cli does not work after enabling stats for UBR connection.

CSCtl70378

VXSM nacks the add command when video line is sent with v=0 delimiter.

CSCtl72173

Large ANI causes CAS state machine to hang.

CSCtl73108

VXSM nacks Add Request in a particular call flow.

CSCtl73358

VXSM does not nack the add with single codec having unsupported parameter.

CSCtl82868

E911:GW generates error in logs if sending digits more than ANI length.

CSCtl88987

Abandoned call scenario produces call failures.

CSCtl96780

Internal gateway error observed when dd/std event is played.

CSCtl99506

Standby card reboots when modify of upspeed codecs is sent.

CSCtl99904

CDB not getting freed in a mdfy with unsupported codec after T38 modify.

CSCtn02351

Permanent announcement files are not being downloaded after switchover.

CSCtn10334

Dynamic memory leak in H.248.

CSCtn10942

Wrong error message generate on multiple signal played in RQNT.

CSCtn11185

Payload negotiation not happening in a particular scenario.

CSCtn18915

On adding more than 2 RTP terminations to a context gateway returns 510.

CSCtn22634

Exception occurred when tty is configured during transcoding calls

CSCtn25514

FIPC-5-EPHNDLRFAIL error comes after addred in MGCP &TGCP.

CSCtn25683

Printfs are getting generated when call is established in G.723 H.

CSCtn31671

H248 codec negotiation feature clis are visible and configurable in MGCP.

CSCtn31836

Wrong error message while sending unsupported parameter in fmtp line.

CSCtn39108

Standby VXSM resets on RPM switchover.

CSCtn45629

BearerPool: Invalid ip address returned for ConfigIpAddress in trap 62013.

CSCtn48953

VXSM card resets after 10 hrs with mid-call codec change load.

CSCtn48982

VXSM resets with RTP-MUX load when onlinediag is enabled.

CSCtn49165

Codec negotiation not happening when multiple SDPs are given in Remote.

CSCtn52065

Text Over IP MIBS are missing in Config Upload File.

CSCtn70605

Bearer IP does not change in T.38 modify in active card after switchover.

CSCtn89776

VXSM is replying with 515 instead of 510 when no DSP resources are left.

CSCtn89277

Able to add textrelayprofile with duplicate payload type.

CSCtn77016

VXSM card resets with midcall codec change load when V23 is enabled.

CSCtn80574

Standby VXSM reboots after runrev from 5.6(0.200)-5.6(8.110)A in RTP-MUX.

CSCtn49598

SNMP error messages are not understandable for 5.6 and 5.6.10 features.

CSCtn64618

Wrong default value for CodecNegotiationPreference in VXSM OC3/T1E1.

CSCtn67231

Default leading space for alternate Codec String.


.

Related Documentation

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