Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
■
xConfiguration SystemUnit Password
■
xConfiguration SystemUnit StrictPassword
■
xConfiguration TimeZone Name
X7.1
Cisco TMS Provisioning Extension support
VCS X7.1 supports the Provisioning Extension mode introduced into Cisco TMS v13.2.
In X7.0 and earlier, the provisioning, FindMe and phone book services on the VCS were provided by the legacy TMS
Agent module. From X7.1, the new Provisioning Extension services mechanism supports large-scale deployments
and provides a more flexible upgrade path for both VCS and Cisco TMS.
Agent module. From X7.1, the new Provisioning Extension services mechanism supports large-scale deployments
and provides a more flexible upgrade path for both VCS and Cisco TMS.
You are recommended to switch from using the TMS Agent legacy mode to the new Provisioning Extension mode as
soon as is practicable.
soon as is practicable.
Call processing
■
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.
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
■
The VCS can run on VMware on Cisco UCS C200 M2 and UCS C210 M2 servers.
Other enhancements and usability improvements
■
Improved status reporting of NTP server synchronization.
■
The lower and upper source ports in the range used for sending DNS queries can now be configured on the
DNS page.
DNS page.
■
Automatically uploaded CRL files are now included when checking the validity of client certificates on the
Client certificate testing page.
Client certificate testing page.
■
System snapshot:
—
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.
page and return to it later to download the generated snapshot file.
—
Snapshot filenames are distinct for each type of snapshot.
■
Default incident reporting server is now https://cc-reports.cisco.com/submitapplicationerror/
■
The VCS Starter Pack Express supports device provisioning for MX200 endpoints.
■
An optional free-form description of a B2BUA transcoder can be specified.
■
Alarms status page now shows when an alarm was first raised.
■
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.
these browsers may also work, but are not officially supported.
■
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.
(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
for more information.
511
Cisco TelePresence Video Communication Server Administrator Guide