Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Limitations
Cisco TelePresence Video Communication Server Software Release Notes (X8.2.1)
Page 19 of 32
Limitations
Unsupported features (general)
n
DTLS is not supported through the VCS Control/VCS Expressway; attempts to make secure calls will fail
n
SIP Early Media
n
SIP KeyPad Markup Language (KPML)
n
Audio calls may be licensed as video calls in some circumstances. Calls that are strictly audio-ONLY
consume fewer licenses than video calls. However, when audio calls include non-audio channels, such as
the iX channel that enables ActiveControl, they are treated as video calls for licensing purposes.
consume fewer licenses than video calls. However, when audio calls include non-audio channels, such as
the iX channel that enables ActiveControl, they are treated as video calls for licensing purposes.
Unsupported Jabber features when using mobile and remote access
n
Directory access mechanisms other than UDS
n
Certificate provisioning to remote endpoints e.g. CAPF
n
File transfer (except when operating in hybrid Webex mode)
n
Deskphone control (QBE/CTI)
n
Additional mobility features including DVO-R, GSM handoff and session persistency
n
Self-care portal
n
Support for Jabber SDK
n
Shared lines are supported in a limited way. Multiple endpoints can share a line but in-call features (like
hold/resume) only work on the first endpoint that answers. Endpoints sharing the line may not correctly
recognise the state of the call.
hold/resume) only work on the first endpoint that answers. Endpoints sharing the line may not correctly
recognise the state of the call.
Unsupported features and limitations when using mobile and remote
access
access
n
Secure XMPP traffic between VCS Control and IM&P servers (XMPP traffic is secure between VCS
Control and VCS Expressway, and between VCS Expressway and remote endpoint)
Control and VCS Expressway, and between VCS Expressway and remote endpoint)
n
Endpoint management capability (SNMP, SSH/HTTP access)
n
Multi-domain and multi-customer support; each VCS deployment supports only one IM&P domain (even
though IM & Presence 10.0 or later supports multiple IM&P domains)
though IM & Presence 10.0 or later supports multiple IM&P domains)
n
Mobile and remote access functionality is not within the FIPS boundary
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
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
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)