Cisco TelePresence Administrator's Manual page 312

Consistent create and modify behavior for configuration items: for configuration where multiple items
n
can be defined (for example, Allow List patterns, search rules and so on) the create and modify behavior
has been made consistent so that you are always returned to the summary list page after saving your
changes.
Additionally, new search rules, subzone membership rules, subzones and zones are all created in a single
step. Previously you had to specify some of the configuration values when creating the item, and then
return to the edit page to specify the remainder of the values.
"Please select" in drop-down fields: when creating configuration items some of the default values
n
presented in drop-down selection fields have been replaced with a "please select" value. This helps prevent
potentially undesirable default values being selected by mistake.
Improved filtering options for Event Log and Configuration Log: advanced filtering options let you
n
include or exclude specific words or phrases when filtering the view of the Event Log and the Configuration
Log.
OCS Relay status: colored status icons make the difference between the online and offline OCS Relay
n
status more distinct.
Configuration warnings: more warnings are raised for common misconfiguration scenarios, for example
n
if a clustered VCS has H.323 disabled, or if default links are not present.
FindMe™ / User Policy option key
The User Policy option key has been renamed as the FindMe™ option key.
n
"FindMe accounts" and "FindMe groups" are now referred to as "user accounts" and "user groups"
n
respectively.
Subzone registration policies
In addition to using Allow Lists and Deny Lists, registrations can be controlled at the subzone level. Each
n
subzone can be configured to allow or deny registrations assigned to it via the subzone membership rules.
Up to 3000 subzone membership rules (previously 2000) can be configured across all subzones.
n
Zone configuration
TLS authentication: the VCS can perform certificate verification of neighbor zones when communicating
n
over TLS. Mutual authentication can be performed with neighbor VCSs.
TLS default transport type: TLS is the default SIP transport type when setting up new neighbor, traversal
n
client and traversal server zones.
SIP authentication trust: the VCS can be configured to trust incoming SIP messages from specified
n
neighbor zones, rather than challenge them. This applies even if device authentication is enabled on the
VCS.
Accept proxied registrations: controls whether proxied SIP registrations routed through a neighbor,
n
traversal client or traversal server zone are accepted.
Nortel Communication Server 1000 zone profile: the VCS can automatically configure the settings
n
required for connections to a Nortel Communication Server 1000.
Separate authentication credentials per traversal client zone: each traversal client zone specifies its
n
own username and password for authentication with the traversal server. This allows a traversal client
VCS to connect to one or more service providers. Note that the existing Outbound connection
credentials username and password are still used for connections to all other (non traversal server)
external systems.
Conference Factory generated alias ranges
Cisco VCS Administrator Guide (X7.1)
Reference material
Page 312 of 479