Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Resolved issues
Cisco TelePresence Video Communication Server Software Release Notes (X8.2)
Page 9 of 30
n
All references to OCS/Lync B2BUA have been renamed to refer to Lync B2BUA. The Enhanced OCS
Collaboration option key is now called Microsoft Interoperability.
Collaboration option key is now called Microsoft Interoperability.
n
References to 'Movi' have been changed to 'Jabber Video'.
n
The
FindMe configuration
page is now accessed directly under
Applications > FindMe
.
n
On the
Upgrade
page, the VCS platform component is now referred to as System platform.
n
The
Advanced account security
page is now called
Advanced security
and is accessed via
Maintenance > Advanced security
.
n
The
Local VCS inbound ports
page is now called
Local inbound ports
, and the
Local VCS outbound
ports
page is now called
Local outbound ports
.
n
The advanced zone configuration Empty INVITE allowed setting is now referred to as Send empty
INVITE for interworked calls.
INVITE for interworked calls.
n
The following settings have been removed from the
SIP configuration
page: Require UDP BFCP mode
and Require Duo Video mode. They existed to provide support for interoperability issues with old
versions of Cisco TelePresence MXP endpoints. These settings can still be configured via the CLI if
necessary.
versions of Cisco TelePresence MXP endpoints. These settings can still be configured via the CLI if
necessary.
n
The
Login account authentication configuration
page has been removed, and the Administrator
authentication source and FindMe authentication source settings are now on the
Login account
LDAP configuration
page.
n
The xConfiguration Interworking Require Invite Header Mode is now Off by default.
n
The Directory option has been removed from the list of restriction policies on the
Registration
configuration
page and the list of Call Policy modes on the
Call Policy configuration
page.
n
The DNS lookup tool includes Unified Communications SRV services.
Resolved issues
Resolved in X8.2
Identifier
Description
CSCum90139 Symptoms: VCS X8.1 uses the Ethernet 2 IP address for the media part in SDP rather than the
configured Static NAT IP address. This results in calls failing on the media part.
Conditions: Running VCS X8.1 with Static NAT and encryption B2BUA enabled (a media
encryption policy other than Auto).
encryption policy other than Auto).
Workaround: Recommended configuration for VCS Control with VCS Expressway deployments
is to configure the same media encryption policy setting on the traversal client zone on VCS
Control, the traversal server zone on VCS Expressway, and every zone and subzone on VCS
Expressway, and to only use static NAT on the VCS Expressway. With this configuration the
encryption B2BUA will only be enabled on the VCS Control.
is to configure the same media encryption policy setting on the traversal client zone on VCS
Control, the traversal server zone on VCS Expressway, and every zone and subzone on VCS
Expressway, and to only use static NAT on the VCS Expressway. With this configuration the
encryption B2BUA will only be enabled on the VCS Control.
Table 1: Issues resolved in X8.2