Cisco Cisco Expressway Release Notes
Changes and Minor Enhancements
■
Multistream support is disabled in this release, pending a complete implementation in a future release.
■
A new CLI command allows you to set the cipher suites used when the Expressway authenticates with the
AD domain for LDAP queries. The command is
AD domain for LDAP queries. The command is
xconfiguration Authentication ADS CipherSuite
.
■
A Hybrid Services menu item has been added to the Expressway-E, to support Expressway-based hybrid
services that are currently in development. The new menu item (Applications > Hybrid Services > Certificate
management) has no explicit purpose for X8.7.
services that are currently in development. The new menu item (Applications > Hybrid Services > Certificate
management) has no explicit purpose for X8.7.
■
A new system metric has been added to monitor each CPU core independently.
■
New parameters have been added to the .ova file so you can configure the VM's network properties when
deploying through vCenter.
deploying through vCenter.
.
There is a delay when you deploy virtual machines with pre-configured network parameters. The deployment
will take a few minutes longer than deploying the VM without pre-configured network parameters.
will take a few minutes longer than deploying the VM without pre-configured network parameters.
■
The Expressway deployment guide now warns against choosing a single NIC, static NAT deployment of the
Expressway-E. The preferred option for deploying the Expressway-E in the DMZ is to use both NICs.
Expressway-E. The preferred option for deploying the Expressway-E in the DMZ is to use both NICs.
Open and Resolved Issues
Follow the links below to read the most recent information about the open and resolved issues in this release.
■
■
■
Notable Issues in this Version
: MRA Phone Services Not Registering if incorrect Case used in UserID
Jabber fails to register for Unified CM phone services if the user enters their ID using a different case to the ID known
by UDS (User Data Service). Jabber still signs in if the correct user ID is given in the wrong case, but will not be able to
use phone services.
by UDS (User Data Service). Jabber still signs in if the correct user ID is given in the wrong case, but will not be able to
use phone services.
To avoid this issue, users should correctly case the user ID on first login. After the first successful login, an incorrectly
cased user ID does not prevent Jabber from using phone services.
cased user ID does not prevent Jabber from using phone services.
To recover from this issue, users should sign out and then reset Jabber.
: DTMF mid-call features not supported for Mobility-enabled Users
(This issue is present in Cisco Unified Communications Manager version 11.0)
For end users who have mobility enabled, DTMF-based mid-call features (for example, *81 - Hold, *83 - Resume) are
not supported, regardless of the DTMF Signaling Method setting for the SIP trunk. This issue is present for all SIP
trunks due to issues with SIP signaling and MTP allocation. There is no workaround for this issue.
not supported, regardless of the DTMF Signaling Method setting for the SIP trunk. This issue is present for all SIP
trunks due to issues with SIP signaling and MTP allocation. There is no workaround for this issue.
Note
: DTMF for User Controlled Voicemail avoidance and for navigating IVRs at the far-end are both supported.
: SDP Decode Fails when Trying to Split IM&P and Video From Lync
This issue in X8.6 and X8.7 prevents a previously published Lync federation deployment from working as it did in X8.5.
If you are using the affected deployment, we recommend that you do not upgrade yet.
If you are using the affected deployment, we recommend that you do not upgrade yet.
The affected deployment is documented in Appendix 1: Federation, of the X8.5 version of Microsoft Lync and Cisco
Expressway Deployment Guide, on the
Expressway Deployment Guide, on the
6
Cisco Expressway Release Note
Open and Resolved Issues