Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Planned changes for future releases
Cisco TelePresence Video Communication Server X8.1 Software Release Notes
Page 13 of 25
n
The VCS Control 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 VCS Control
required, this must be configured on a stand-alone VCS Control
n
NTLM authentication via the HTTP proxy
n
XMPP federation managed directly by VCS Expressway (note that remote client access via VCS for
XMPP inter domain federation managed by CUP is supported)
XMPP inter domain federation managed by CUP is supported)
n
Maintenance mode; if a VCS Control or VCS Expressway is placed into maintenance mode, any existing
calls passing through that VCS will be dropped
calls passing through that VCS will be dropped
n
The VCS Expressway must not have TURN services enabled
n
The VCS Expressway 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 VCS appliances or equivalent VM)
as VCS appliances or equivalent VM)
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 VCS Expressway server certificate. Future
endpoint client software releases will support the use of SRVName SAN entries when validating the VCS
Expressway 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 VCS Expressway server certificate. Future
endpoint client software releases will support the use of SRVName SAN entries when validating the VCS
Expressway 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 VCS CSR tool will be updated in a future release to support the SRVName and XMPPAddress formats
in the relevant SAN fields.
in the relevant SAN fields.
Note that there are no current limitations on installing VCS server certificates that contain SAN SRVName
and XMPPAddress entries.
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.