Cisco Cisco MGX 8880 Media Gateway

Page de 24
6
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.5.00.201
OL-18917-01
Firmware Images
Support for T38 fallback to PCMU/PCMA
This feature supports T38 fallback to PCMU/PCMA. MGC asks VXSM to move to T.38 mode and sends 
the same request to another end, for instance, a SIP end. Now, for some reasons, if the SIP end does not 
move to T.38, the MGC asks the VXSM to fallback to PCMU/PCMA so that it can still send the FAX.
Support for SMS Tone Detection
SMS detection feature adds support for SMS traffic delivery through the voice bandwidth of an 
established voice session. The following commands were added to support this feature:
cnfeventmapping - sms
dspeventmapping - sms
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.3.10 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.5.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.