Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Call processing
n
Improved interworking between VCS and Cisco Unified Communications Manager. VCS now always
stays in the call signaling route for calls to neighbor zones that are configured with the Cisco Unified
Communications Manager or the Infrastructure device zone profiles.
stays in the call signaling route for calls to neighbor zones that are configured with the Cisco Unified
Communications Manager or the Infrastructure device zone profiles.
Virtual appliance support
n
The VCS can run on VMware on Cisco UCS C200 M2 and UCS C210 M2 servers.
Other enhancements and usability improvements
n
Improved status reporting of NTP server synchronization.
n
The lower and upper source ports in the range used for sending DNS queries can now be configured on the
DNS
page.
n
Automatically uploaded CRL files are now included when checking the validity of client certificates on the
Client certificate testing
page.
n
System snapshot:
l
The snapshot process now runs in the background. This means you can navigate away from the
snapshot page and return to it later to download the generated snapshot file.
snapshot page and return to it later to download the generated snapshot file.
l
Snapshot filenames are distinct for each type of snapshot.
n
Default incident reporting server is now https://cc-reports.cisco.com/submitapplicationerror/
n
The VCS Starter Pack Express supports device provisioning for MX200 endpoints.
n
An optional free-form description of a B2BUA transcoder can be specified.
n
Alarms status page now shows when an alarm was first raised.
n
The VCS web interface now supports Internet Explorer 7, 8 or 9, Firefox 3 or later, or Chrome. Later
versions of these browsers may also work, but are not officially supported.
versions of these browsers may also work, but are not officially supported.
n
Session log in and log out entries in the Event Log now show the IP address of the source client.
X7
Device authentication using an Active Directory Service for Jabber Video endpoints
Device authentication can be performed using a direct connection between the VCS and an Active Directory
Service (ADS). This allows Jabber Video 4.2 (or later) endpoint users to use their Windows Active Directory
(AD) credentials to authenticate with the VCS.
Service (ADS). This allows Jabber Video 4.2 (or later) endpoint users to use their Windows Active Directory
(AD) credentials to authenticate with the VCS.
This means that Jabber Video users do not need a separate set of authentication credentials (username and
password) for their Jabber Video endpoint - instead they can use the same credentials for both Windows and
Jabber Video. See
password) for their Jabber Video endpoint - instead they can use the same credentials for both Windows and
Jabber Video. See
Previously this feature was only configurable via the CLI, from X7.0 it can be configured via the web
interface.
interface.
Shared cluster licenses
Call licenses are now shared across the entire VCS cluster.
Traversal and non-traversal call license option keys are still installed on each individual peer and are subject
to per-peer limits, but the licenses are available to all peers in the cluster. See
to per-peer limits, but the licenses are available to all peers in the cluster. See
identically on each cluster peer, as before.
Cisco TelePresence Video Communication Server Administrator Guide (X8.5)
Page 551 of 559
Reference material
Software version history