Cisco Cisco Expressway Release Notes
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
: Rich Media Session license is not consumed by Single NIC Expressway-E hosting Jabber Guest
service
Changes to the licensing model in X8.8 release have revealed an issue with licensing of the Jabber Guest service on
the Expressway-E server. When the Expressway pair is part of the "Single NIC" Jabber Guest deployment, the
Expressway-E should count one RMS license for each Jabber Guest call, but it does not.
the Expressway-E server. When the Expressway pair is part of the "Single NIC" Jabber Guest deployment, the
Expressway-E should count one RMS license for each Jabber Guest call, but it does not.
This issue could cause confusion about the server's load because the usage appears low, even when the server is
processing multiple calls. We recommend the Dual NIC Jabber Guest deployment.
processing multiple calls. We recommend the Dual NIC Jabber Guest deployment.
If you are using the single NIC deployment, make sure your Expressway-E is correctly licensed to ensure continuity of
service when upgrading in future.
service when upgrading in future.
: Calls to/from Skype for Business Android v6.4.0.5 fail due to ICE (internal/external)
Skype for Business for Android version 6.4.0.5 cannot make or receive calls with standards-based endpoints (via
Expressway configured for Microsoft interoperability) when the calls have both audio and video streams.
Expressway configured for Microsoft interoperability) when the calls have both audio and video streams.
You can work around this issue in one of these ways:
■
Using Skype for Business for Android 6.4.0.5 (or later): Make or answer calls as audio-only, and then add
video after the audio call is established.
video after the audio call is established.
■
Use an earlier release of Skype for Business for Android: For example, versions 6.0.0.8, 6.2.0.3, or 6.3.0.2 do
not have this issue. Note that these versions are no longer available through the official channels.
not have this issue. Note that these versions are no longer available through the official channels.
Limitations
Unsupported Features (General)
■
DTLS is not supported through the Expressway-C/Expressway-E. SRTP is used to secure calls instead;
attempts to make DTLS calls will fail.
attempts to make DTLS calls will fail.
■
SIP UPDATE method. Features that rely on the SIP UPDATE method (
) will not work as expected
because the Expressway does not support this method.
■
Audio calls may be licensed as video calls in some circumstances. Calls that are strictly audio-ONLY consume
fewer licenses than video calls. However, when audio calls include non-audio channels, such as the iX
channel that enables ActiveControl, they are treated as video calls for licensing purposes.
fewer licenses than video calls. However, when audio calls include non-audio channels, such as the iX
channel that enables ActiveControl, they are treated as video calls for licensing purposes.
Unsupported Endpoint Features When Using Mobile and Remote Access
Note:
This list contains known limitations and is not exhaustive. The MRA deployment does not necessarily support
pass through of line-side features provided by Cisco Unified Communications Manager. Absence of such items from
this list does not imply that they are supported.
this list does not imply that they are supported.
13
Cisco Expressway Series Release Notes
Open and Resolved Issues