Cisco Cisco Expressway Release Notes
Planned changes for future releases
Cisco Expressway X8.1 Software Release Notes
Page 3 of 11
n
Calls involving secure endpoints remotely registered to Unified CM via Expressway may end up with a
portion of the call using non-secure media; these portions will only ever be on sections of the call that are on
premises (between the Expressway-C and endpoints registered locally to Unified CM), never on the public
Internet
portion of the call using non-secure media; these portions will only ever be on sections of the call that are on
premises (between the Expressway-C and endpoints registered locally to Unified CM), never on the public
Internet
n
Endpoint management capability (SNMP, SSH/HTTP access)
n
Multi-domain and multi-customer support; each Expressway deployment supports only one IM&P domain
(even though IM & Presence 10.0 or later supports multiple IM&P domains)
(even though IM & Presence 10.0 or later supports multiple IM&P domains)
n
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
n
NTLM authentication via the HTTP proxy
n
XMPP federation managed directly by Expressway-E (note that remote client access via Expressway for
XMPP inter domain federation managed by CUP is supported)
XMPP inter domain federation managed by CUP is supported)
n
Maintenance mode; if an Expressway-C or 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
n
The Expressway-E must not have TURN services enabled
n
The Expressway-E DNS hostname must not contain underscore characters (it can only contain letters,
digits and hyphens)
digits and hyphens)
n
Deployments on Large VM servers are limited to 2500 proxied registrations to Unified CM (the same limit
as Small / Medium VM servers)
as Small / Medium VM servers)
Planned changes for future releases
Support for SRVName and XMPPAddress subject alternate name (SAN) entries in the Certificate
Signing Request (CSR) tool
Signing Request (CSR) tool
Mobile and remote access deployments currently require all of the root domains which have been configured
for Unified Communications to be included as SANs in the Expressway-E server certificate. Future endpoint
client software releases will support the use of SRVName SAN entries when validating the Expressway-E
server certificate. This means that it will no longer be necessary to include root domain names as SAN DNS
entries.
for Unified Communications to be included as SANs in the Expressway-E server certificate. Future endpoint
client software releases will support the use of SRVName SAN entries when validating the Expressway-E
server certificate. This means that it will no longer be necessary to include root domain names as SAN DNS
entries.
XMPP Federation will also require domains and identities to be included in the SAN for secure TLS
connections. Its format can be either DNS or XMPPAddress.
connections. Its format can be either DNS or XMPPAddress.
The Expressway CSR tool will be updated in a future release to support the SRVName and XMPPAddress
formats in the relevant SAN fields.
formats in the relevant SAN fields.
Note that there are no current limitations on installing Expressway server certificates that contain SAN
SRVName and XMPPAddress entries.
SRVName and XMPPAddress entries.
For more information, see:
n
RFC4985: SRVName
n
RFC3920 section 5.1.1: XMPPAddress
Interoperability
, where you
can also find interoperability test results for other Cisco TelePresence products.