Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
■
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.
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 Endpoint Features When Using Mobile and Remote Access
Note:
This list contains known limitations and is not exhaustive. The MRA deployment does not necessarily support
pass through of line-side features provided by Cisco Unified Communications Manager. Absence of such items from
this list does not imply that they are supported.
this list does not imply that they are supported.
■
Calls to/from additional lines on IP phones and endpoints that support multiple lines; only the primary line is
supported via Mobile and Remote Access
supported via Mobile and Remote Access
■
Directory access mechanisms other than UDS
■
Certificate provisioning to remote endpoints e.g. CAPF
■
Features that rely on the SIP UPDATE method (
) will not work as expected because the Cisco VCS
does not support this method. For example, CUCM and endpoints use UPDATE to implement blind transfer,
which does not work correctly via MRA.
which does not work correctly via MRA.
■
Peer-to-peer file transfer when using IM and Presence Service and Jabber is unsupported via MRA
—
Managed File Transfer (MFT) with IM and Presence Service 10.5.2 (and later) and Jabber 10.6 (and later)
clients is supported via MRA
clients is supported via MRA
—
File transfer with WebEx Messenger Service and Cisco Jabber is supported via MRA
■
Deskphone control (QBE/CTI)
■
Additional mobility features including DVO-R, GSM handoff and session persistency
■
Hunt group/hunt pilot/hunt list
■
Self-care portal
■
Support for Jabber SDK
■
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 Cisco VCS Features and Limitations When Using Mobile and Remote
Access
Access
■
The Cisco VCS cannot be used for Jabber Guest when it is used for MRA.
■
The Cisco 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 Cisco VCS Control.
required, this must be configured on a stand-alone Cisco VCS Control.
■
Secure XMPP traffic between Cisco VCS Control and IM&P servers (XMPP traffic is secure between Cisco
VCS Control and Cisco VCS Expressway, and between Cisco VCS Expressway and remote endpoint).
VCS Control and Cisco VCS Expressway, and between Cisco VCS Expressway 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 Cisco VCS deployment supported only one IM&P domain (even though IM and Presence
Service 10.0 or later supports Multiple Presence Domains).
Service 10.0 or later supports Multiple Presence Domains).
—
As of X8.5, you can create multiple deployments on the Cisco VCS Control, but this feature is still limited to
one domain per deployment.
one 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.
■
Mobile and remote access functionality is not within the FIPS boundary.
■
NTLM authentication via the HTTP proxy.
7
Cisco TelePresence Video Communication Server Release Note