Cisco Cisco Expressway Release Notes
Interoperability
Unified Communications Cisco Expressway Series Software Release Notes (X8.5.3)
Page 12 of 23
n
Phone security profile: If the phone security profile for any of these endpoints has TFTP Encrypted
Config checked, you will not be able to use the endpoint via Mobile and Remote Access. This is because
the MRA solution does not support devices interacting with CAPF (Certificate Authority Proxy Function).
Config checked, you will not be able to use the endpoint via Mobile and Remote Access. This is because
the MRA solution does not support devices interacting with CAPF (Certificate Authority Proxy Function).
n
Trust list: You cannot modify the root CA trust list on these endpoints. Make sure that the Expressway-
E's server certificate is signed by one of the CAs that the endpoints trust, and that the CA is trusted by the
Expressway-C and the Expressway-E.
E's server certificate is signed by one of the CAs that the endpoints trust, and that the CA is trusted by the
Expressway-C and the Expressway-E.
n
Bandwidth restrictions: The Maximum Session Bit Rate for Video Calls on the default region on
Cisco Unified Communications Manager is 384 kbps by default. The Default call bandwidth on
Expressway-C is also 384 kbps by default. These settings may be too low to deliver the expected video
quality for the DX Series.
Cisco Unified Communications Manager is 384 kbps by default. The Default call bandwidth on
Expressway-C is also 384 kbps by default. These settings may be too low to deliver the expected video
quality for the DX Series.
Interoperability
, where you
can also find interoperability test results for other Cisco TelePresence products.
Updating to X8.5.3
Upgrade instructions
When maintenance mode is enabled on an Expressway, existing calls passing through that Expressway
may be dropped. We recommended that you upgrade Expressway components while the system is inactive.
may be dropped. We recommended that you upgrade Expressway components while the system is inactive.
If you are upgrading an Expressway that uses clustering, you must follow the directions in Expressway
Cluster Creation and Maintenance Deployment Guide.
Cluster Creation and Maintenance Deployment Guide.
To upgrade a non-clustered Expressway:
1. Backup the Expressway (
Maintenance > Backup and restore
).
You should backup your system before upgrading. If you later need to downgrade to an earlier release you
will have to restore a backup made against that previous release.
will have to restore a backup made against that previous release.
2. Enable maintenance mode:
a. Go to
Maintenance > Maintenance mode
.
b. Set Maintenance mode to On.
c. Click Save and click OK on the confirmation dialog.
c. Click Save and click OK on the confirmation dialog.
3. Wait for all calls to clear (
Status > Calls
).
4. Upgrade and restart the Expressway (
Maintenance > Upgrade
).
The web browser interface may timeout during the restart process, after the progress bar has reached the
end. This may occur if the Expressway carries out a disk file system check – which it does approximately
once every 30 restarts.
end. This may occur if the Expressway carries out a disk file system check – which it does approximately
once every 30 restarts.
The upgrade is now complete and all Expressway configuration should be as expected.
Upgrading Expressway-C and Expressway-E systems connected over a traversal zone
We recommend that Expressway-C (traversal client) and Expressway-E (traversal server) systems that are
connected over a traversal zone both run the same software version.
connected over a traversal zone both run the same software version.