Cisco Cisco Expressway Release Notes
Management Suite Provisioning Extension which requires TMS 13.2.x. See Cisco TMS Provisioning Extension
Deployment Guide for instructions about how to migrate.
Deployment Guide for instructions about how to migrate.
Existing OCS Relay Deployments
Expressway X8.1 and later no longer supports OCS Relay integration with Microsoft Lync 2010 / OCS 2007 R2. If you
use OCS Relay you must migrate to using the Microsoft Interoperability B2BUA to route SIP calls between the
Expressway and Microsoft infrastructure. See Cisco VCS and Microsoft Infrastructure Deployment Guide for
information about this deployment.
use OCS Relay you must migrate to using the Microsoft Interoperability B2BUA to route SIP calls between the
Expressway and Microsoft infrastructure. See Cisco VCS and Microsoft Infrastructure Deployment Guide for
information about this deployment.
Upgrade Instructions
When maintenance mode is enabled on Expressway, existing calls passing through it may be dropped. We
recommend that you upgrade Expressway components while the system is inactive.
recommend that you upgrade Expressway components while the system is inactive.
If you are upgrading a clustered Expressway, you must follow the directions in Expressway Cluster Creation and
Maintenance Deployment Guide.
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.
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.
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.
Upgrade 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.
over a traversal zone both run the same software version.
However, we do support a traversal zone link from one Expressway system to another that is running the previous
major release of Expressway. This means that you do not have to simultaneously upgrade your Expressway-C and
Expressway-E systems.
major release of Expressway. This means that you do not have to simultaneously upgrade your Expressway-C and
Expressway-E systems.
Note that certain services (such as Mobile and Remote Access) require both the Expressway-C and Expressway-E
systems to be running the same software version.
systems to be running the same software version.
■
We strongly recommend installing a new server certificate if you are upgrading from any version of
Expressway released prior to X8.1.1.
Expressway released prior to X8.1.1.
17
Cisco Expressway Series Release Notes
Upgrading to X8.8.2