Cisco Cisco Expressway Release Notes
Unsupported Expressway Features and Limitations When Using Mobile and Remote
Access
Access
■
The Expressway cannot be used for Jabber Guest when it is used for MRA.
■
The Expressway-C used for Mobile and Remote Access cannot also be used as a Lync 2013 gateway (if
required, this must be configured on a stand-alone Expressway-C).
required, this must be configured on a stand-alone Expressway-C).
■
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).
C and Expressway-E, and between Expressway-E and remote endpoint).
■
Endpoint management capability (SNMP, SSH/HTTP access).
■
Multi-domain and multi-customer support is limited as follows:
—
Prior to X8.5, each Expressway deployment supported only one IM&P domain (even though IM and
Presence Service 10.0 or later supports Multiple Presence Domains).
Presence Service 10.0 or later supports Multiple Presence Domains).
—
As of X8.5, you can create multiple deployments on the Expressway-C, but this feature is still limited to one
domain per deployment.
domain per deployment.
—
As of X8.5.1, a deployment can have Multiple Presence Domains. This feature is in preview, and we
currently recommend that you do not exceed 50 domains.
currently recommend that you do not exceed 50 domains.
■
NTLM authentication via the HTTP proxy.
■
Maintenance mode; if the Expressway-C or the Expressway-E is placed into maintenance mode, any existing
calls passing through that Expressway will be dropped.
calls passing through that Expressway will be dropped.
■
The Expressway-E must not have TURN services enabled.
■
Deployments on Large VM servers are limited to 2500 proxied registrations to Unified CM (the same limit as
Small / Medium VM servers).
Small / Medium VM servers).
Interoperability
, where you can
also find interoperability test results for other Cisco TelePresence products.
Upgrading to X8.7.2
Prerequisites and Software Dependencies
Hybrid Services
Your Management Connector must be up to date before you upgrade your Expressway. You must authorize and
accept any upgrades advertised by the Cisco Collaboration Cloud before attempting to upgrade.
accept any upgrades advertised by the Cisco Collaboration Cloud before attempting to upgrade.
Note:
X8.7.1 is now the minimum version required for Hybrid Services. If you are using Hybrid Services with X8.7, you
must upgrade to X8.7.1.
Existing TMS Agent (Legacy Mode) Provisioning Deployments
Expressway X8.1 and later no longer supports TMS Agent (legacy mode) provisioning. Before you upgrade to X8 or
later, if you are using TMS Agent (legacy mode) for provisioning you must first migrate to Cisco TelePresence
Management Suite Provisioning Extension which requires TMS 13.2.x. See Cisco TMS Provisioning Extension
Deployment Guide for instructions about how to migrate.
later, if you are using TMS Agent (legacy mode) for provisioning you must first migrate to Cisco TelePresence
Management Suite Provisioning Extension which requires TMS 13.2.x. See Cisco TMS Provisioning Extension
Deployment Guide for instructions about how to migrate.
Existing OCS Relay Deployments
Expressway X8.1 and later no longer supports OCS Relay integration with Microsoft Lync 2010 / OCS 2007 R2. If you
use OCS Relay you must migrate to using the Microsoft Lync B2BUA to route SIP calls between the Expressway and a
use OCS Relay you must migrate to using the Microsoft Lync B2BUA to route SIP calls between the Expressway and a
8
Cisco Expressway Release Note
Interoperability