Cisco Cisco Expressway Release Notes
Open issues
Cisco Expressway X8.1 Software Release Notes
Page 2 of 11
Open issues
The following issues apply to this version of Cisco Expressway.
Identifier
Description
CSCul93670
Symptom: Unified Communications services fail to start after a Expressway restart. Mobile and
remote systems will not be able to register to Unified CM or make calls. This is an occasional
issue.
remote systems will not be able to register to Unified CM or make calls. This is an occasional
issue.
Conditions: Restart (or reboot) a Expressway that has Mobile and remote access enabled.
Workaround: After a restart or reboot, wait 5 minutes and then go to
Status > Unified
Communications
in the web interface. If any of the services are in an error state, go to
Configuration > Unified Communications > Configuration
and disable and then re-enable the
Mobile and remote access feature.
CSCum90139 Symptoms: Expressway X8.1 uses the Ethernet 2 IP address for the media part in SDP rather
than the configured Static NAT IP address. This results in calls failing on the media part.
Conditions: Running Expressway X8.1 with Static NAT and encryption B2BUA enabled (a media
encryption policy other than Auto).
encryption policy other than Auto).
Workaround: Recommended configuration for Expressway-C with Expressway-E deployments
is to configure the same media encryption policy setting on the traversal client zone on
Expressway-C, the traversal server zone on Expressway-E, and every zone on Expressway-E,
and to only use static NAT on the Expressway-E. With this configuration the encryption B2BUA
will only be enabled on the Expressway-C.
is to configure the same media encryption policy setting on the traversal client zone on
Expressway-C, the traversal server zone on Expressway-E, and every zone on Expressway-E,
and to only use static NAT on the Expressway-E. With this configuration the encryption B2BUA
will only be enabled on the Expressway-C.
Table 1: Open issues
Limitations
Unsupported features (general)
n
Webex-enabled TelePresence
n
DTLS is not supported through the Expressway-C/Expressway-E; attempts to make secure calls will fail
n
SIP Early Media
n
SIP KeyPad Markup Language (KPML)
n
You should not configure an Expressway for SIP media encryption if that same Expressway is also
configured for static NAT. If you do so, the private IP address will be sent in the SDP rather than the static
NAT address and this will cause calls to fail.
Note that the recommended configuration for Expressway-C with Expressway-E deployments is to:
configured for static NAT. If you do so, the private IP address will be sent in the SDP rather than the static
NAT address and this will cause calls to fail.
Note that the recommended configuration for Expressway-C with Expressway-E deployments is to:
l
configure the same media encryption policy setting on the traversal client zone on Expressway-C, the
traversal server zone on Expressway-E, and every zone on Expressway-E
traversal server zone on Expressway-E, and every zone on Expressway-E
l
use static NAT on the Expressway-E only
With this configuration the encryption B2BUA will be enabled on the Expressway-C only.
Unsupported features and limitations when using mobile and remote
access
access
n
Secure XMPP traffic between Expressway-C and IM&P servers (XMPP traffic is secure between
Expressway-C and Expressway-E, and between Expressway-E and remote endpoint)
Expressway-C and Expressway-E, and between Expressway-E and remote endpoint)