Cisco Cisco Expressway Release Notes
■
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.
See
Cisco Expressway Virtual Machine Installation Guide on the
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.
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.
See
Cisco Expressway Basic Configuration Deployment Guide on the
.
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
: 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.
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.
: Jabber Guest has one-way audio/video when Expressway is upgraded to X8.6.1 or later
An incompatibility between current versions of Jabber Guest server and Expressway X8.6.1 results in the Jabber Guest
client not decoding media from Jabber Guest server. The incompatibility exists in the negotiation of secure media
(SRTP/SRTCP).
client not decoding media from Jabber Guest server. The incompatibility exists in the negotiation of secure media
(SRTP/SRTCP).
The incompatibility will be addressed by Expressway X8.7 (this version) and a future Jabber Guest Server release (the
current target is Jabber Guest Server 10.6.9, at time of writing). We recommend upgrading Jabber Guest Server (when
the new version is available) to resolve this issue.
current target is Jabber Guest Server 10.6.9, at time of writing). We recommend upgrading Jabber Guest Server (when
the new version is available) to resolve this issue.
In the meanwhile, you could choose one of the following workarounds, depending on which has least impact for your
deployment:
deployment:
■
Workaround: Downgrade Expressway to your previous working version, or postpone upgrading Expressway until
the issue is resolved.
the issue is resolved.
Impact: You do not benefit from fixes and features in X8.6.1 or X8.7.
■
Workaround: Disable SRTP on Jabber Guest Server, which will allow RTP flow between the Jabber Guest client
and Expressway-E.
and Expressway-E.
Impact: Unencrypted media flows in the public internet, between web client and Expressway-E. We do not
recommend this option.
recommend this option.
: 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.
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
5
Cisco Expressway Release Note