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.
: Update or Re-Invite messages received in the Default zone
This issue was seen when Expressway-C was working with Cisco Meeting Server, but it is not limited to those
conditions.
conditions.
Incoming messages can only be classified against the default zone or the collabedge zone when MRA is enabled.
Because of this issue, functionality that requires a manually configured zone for incoming messages cannot work
when MRA is enabled. The most notable case is when the registrar is enabled on the Expressway-C.
Because of this issue, functionality that requires a manually configured zone for incoming messages cannot work
when MRA is enabled. The most notable case is when the registrar is enabled on the Expressway-C.
There are two options to work around this issue:
■
Do not modify any parameters of the default zone when you are using both the registrar and MRA on the
Expressway-C.
Expressway-C.
■
Do not use MRA and the registrar together (if you need to manually configure your zones).
: 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.
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.
14
Cisco Expressway Series Release Notes
Open and Resolved Issues