Cisco VCS Administrator Guide X8 7

Cisco TelePresence Video Communication
Server
Administrator Guide
Last Updated: February 2016
Software version: X8.7
Cisco Systems, Inc. www.cisco.com

Introduction
This section provides an overview of the Cisco TelePresence Video Communication Server.
About the Cisco TelePresence Video Communication Server (VCS) 2

About This Guide 8
Whats New in This Version? 13
About the Cisco TelePresence Video Communication Server (VCS)

The Cisco TelePresence Video Communication Server (VCS) software simplifies session management and control of
telepresence conferences. It provides flexible and extensible conferencing applications, enabling organizations to
benefit from increased employee productivity and enhanced communication with partners and customers.
The VCS delivers exceptional scalability and resiliency, secure communications, and simplified large-scale
provisioning and network administration in conjunction with Cisco TelePresence Management Suite (Cisco TMS).
The VCS interworks transparently with Cisco Unified Communications Manager (Unified CM), bringing rich
telepresence services to organizations with Unified CM. It also offers interoperability with third-party unified
communications, IP telephony networks, and voice-over-IP (VoIP) systems.
The VCS supports on-premises and cloud applications and is available as a dedicated appliance or as a virtualized
application on VMware, with additional support for Cisco Unified Computing System (Cisco UCS) platforms.
You can deploy the VCS as the VCS Control for use within an enterprise and as the VCS Expressway for business-to-
business and remote and mobile worker external communication. An alternative solution, suited to small to medium-
sized businesses (SMBs), is the VCS Starter Pack Express.
Optional packages that you can deploy include FindMe, Device Provisioning, and Advanced Networking (VCS
Expressway only).

2
Cisco TelePresence Video Communication Server Administrator Guide
3
Cisco TelePresence Video Communication ServerAdministrator Guide
VCS Base Applications

The VCS is available with alternative base applications as described below.
VCS Control
VCS Control delivers any-to-any enterprise wide conference and session management and interworking capabilities.
It extends the reach of telepresence conferences by enabling interworking between Session Initiation Protocol (SIP)-
and H.323-compliant endpoints, interworking with third-party endpoints; it integrates with Unified CM and supports
third-party IP private branch exchange (IP PBX) solutions. VCS Control implements the tools required for creative
session management, including definition of aspects such as routing, dial plans, and bandwidth usage, while
allowing organizations to define call-management applications, customized to their requirements.
VCS Expressway
The VCS Expressway deployed with the VCS Control enables smooth video communications easily and securely
outside the enterprise. It enables business-to-business video collaboration, improves the productivity of remote and
home-based workers, and enables service providers to provide video communications to customers. The application
performs securely through standards-based and secure firewall traversal for all SIP and H.323 devices. As a result,
organizations benefit from increased employee productivity and enhanced communication with partners and
customers.
It uses an intelligent framework that allows endpoints behind firewalls to discover paths through which they can pass
media, verify peer-to-peer connectivity through each of these paths, and then select the optimum media connection
path, eliminating the need to reconfigure enterprise firewalls.
The VCS Expressway is built for high reliability and scalability, supporting multivendor firewalls, and it can traverse
any number of firewalls regardless of SIP or H.323 protocol.
Standard Features
The primary purpose of the VCS is to provides secure firewall traversal and session-based access to Cisco Unified
Communications Manager for remote workers, without the need for a separate VPN client.
The VCS has the following standard features:
Provides secure firewall traversal and session-based access to Cisco Unified Communications Manager for
remote workers, without the need for a separate VPN client
2500 endpoint registrations on a standard Small/Medium system and 5000 registrations on a Large system
SIP Proxy/Registrar
SIP Presence Server
SIP Presence User Agent
SIP and H.323 support, including SIP / H.323 interworking
IPv4 and IPv6 support, including IPv4 / IPv6 interworking
H.323 gatekeeper
QoS tagging
Bandwidth management on both a per-call and a total usage basis, configurable separately for calls within
the local subzones and to external systems and zones
Automatic downspeeding option for calls that exceed the available bandwidth
URI and ENUM dialing via DNS, enabling global connectivity
Up to 500 non-traversal calls
Up to 100 traversal calls on a standard Small/Medium system and 500 traversal calls on a Large system
1000 external zones with up to 2000 matches
4
1000 subzones and supporting up to 3000 membership rules

Flexible zone configuration with prefix, suffix and regex support
Can function as a standalone VCS or be neighbored with other systems such as other VCSs, gatekeepers and
SIP proxies
Can be clustered with up to 6 VCSs to provide n+1 redundancy, and up to 4 x individual capacity.
Intelligent Route Director for single number dialing and network failover facilities
Optional endpoint authentication (including AD authentication for Jabber Video clients)
Control over which endpoints are allowed to register
Call Policy (also known as Administrator Policy) including support for CPL
Support for external policy servers
Can be managed with Cisco TelePresence Management Suite (Cisco TMS) 13.2 or later
AD authentication for administrators of the VCS
Pre-configured defaults for:
Cisco Unified Communications Manager neighbor zones
Cisco TelePresence Advanced Media Gateway
Nortel Communication Server neighbor zones
Embedded setup wizard using a serial port for initial configuration
System administration using a web interface or RS-232, SSH, and HTTPS
Intrusion protection
Optional Features
Some VCS features are available by the purchase and installation of the appropriate option key:
FindMe
FindMe is a unique industry solution that gives individual video users a single alias on which they can be contacted
regardless of location. Users have the ability to log on to a web-based interface and control where and how they are
contacted. The FindMe feature also includes support for Microsoft Lync 2010/2013, which enables FindMe aliases to
register as Lync clients, and for Lync clients to view the presence status of FindMe aliases.
5
Device Provisioning
The Device Provisioning option key allows VCS to provision endpoints with configuration information on request and
to supply endpoints with phone book information. (Endpoints including Jabber Video, E20, and the EX and MX Series
can request to be provisioned.) All configuration and phone book information is managed in Cisco TMS. The data is
then transferred to the VCS, from where it is distributed to endpoint clients through the Provisioning Server running on
the VCS.
See TMS provisioning and Cisco TMS Provisioning Extension Deployment Guide for more information about how to
configure provisioning.
SIP to Microsoft Lync 2010 / 2013 Interoperability

The Microsoft Lync back-to-back user agent (Lync B2BUA) on the VCS can be used to route SIP calls between the
VCS and a Microsoft Lync Server. It provides interworking between Microsoft ICE (used by Lync clients) and media for
communications with standard video endpoints.
The Microsoft Interoperability option key is required for all types of communication with Lync 2013.
Advanced Networking
The Advanced Networking option enables the LAN 2 Ethernet port on the VCS Expressway, allowing you to have a
secondary IP address for your VCS. This option also includes support for deployments where the VCS Expressway is
located behind a static NAT device, allowing it to have separate public and private IP addresses.
This configuration is intended for deployments where the VCS Expressway is located in a DMZ between two separate
firewalls on separate network segments.
Appliance and Virtual Machine Options

The VCS supports on-premises and cloud applications and is available as a dedicated appliance or as a virtualized
application on VMware, with additional support for Cisco Unified Computing System (Cisco UCS) platforms.
See Performance Capabilities, page 336 for information about the capabilities of each type of appliance or virtual
machine.
Virtual Machine Options

The VCS has 3 virtualized application deployment types:
Small (for BE 6000 platform)

Medium (standard installation)
Large (extra performance and scalability capabilities)
See VCS on Virtual Machine Installation Guide on the VCS Install Guides page for more information.
6
CESeries Appliances
The VCS is available as a dedicated CESeries appliance based on UCShardware, as follows:which is based on a
UCS C220 M3L:
CE500 appliance: used for standard installations. Based on a UCS C220 M3L and is equivalent to a Medium
VM
CE1000 appliance: offers extra performance and scalability capabilities. Based on a UCS C220 M3L and is
equivalent to a Large VM
CE1100 appliance:a new platform introduced to fit the UCSM4 chassis. Based on a UCSC220 M4L, replaces
the CE500 and CE1000. The CE1100 appliance operates as a medium capacity or large capacity VCS,
depending on whether you install 1 Gbps or 10 Gbps NICs.
See the CE Series appliance installation guides for more information.
Legacy Appliance
The VCS was also previously available on a legacy hardware appliance. Legacy appliances can be identified as
having an LCD panel, keypad and a black faceplate. Their serial numbers start with 52A.
Legacy appliances have the equivalent capabilities of a standard Medium VM or CE500 appliance.
Installation and initial configuration instructions for the VCS legacy appliance are contained in VCS Getting Started
Guide.
Software Versions Supported by Hardware Platforms

Table 1 VCS Software Versions Supported by Platform
Platform name Serial Numbers Scope of software version support
VCS appliance (1st generation) 52A##### All features in versions up to and

including X8.6.1
Critical fixes only in X8.7.n*
Small VM (OVA) (Auto-generated) X8.1 onwards
Medium VM (OVA) (Auto-generated) X8.1 onwards
Large VM (OVA) (Auto-generated) X8.1 onwards
CE500 (VCS pre-installed on UCS C220 52C##### X8.1.1 onwards

M3L)
CE1000 (VCS pre-installed on UCS 52B##### X8.1.1 onwards

C220 M3L)
CE1100 (VCS pre-installed on UCS 52D##### X8.6.1 onwards

C220 M4L)
* As of 12th September 2015, we are not obliged to release new software for this platform (see End-of-Life
Announcement). X8.6.1 is the last version on which you will receive support for all the features included in the
software. However, we may encourage you to upgrade to later releases to address critical issues (for example,
security vulnerabilities). In this case, we will notsupport any of the newer features in those releases on these legacy
platforms. Ask your Cisco representative about migrating to a newer platform.
7
About This Guide

This guide has been divided into several sections, providing conceptual, configuration and reference information
about the various features and capabilities of the VCS. It describes a fully equipped version of the VCS. Your version
may not have all the described extensions installed.
Most configuration tasks on the VCS can be performed by using either the web interface or a command line interface
(CLI). This guide mainly describes how to use the web interface. Some VCS features are only available through the
CLI and these are described as appropriate, including the relevant CLI command.
In this guide, instructions for performing a task using the web interface are shown in the format Menu > Submenu
followed by the Name of the page that you will be taken to.
Where command line interface (CLI) commands are included, they are shown in the format:
xConfiguration <Element> <SubElement>
xCommand <Command>
Related Documentation
See Related Documentation, page 514 for a full list of documents and web sites referenced in this guide.
Training
Training is available online and at our training locations. For more information on all the training we provide and
where our training offices are located, visit www.cisco.com/go/telepresencetraining.
Glossary
A glossary of TelePresence terms is available at: https://tp-tools-web01.cisco.com/start/glossary/.
Accessibility Notice
Cisco is committed to designing and delivering accessible products and technologies.
The Voluntary Product Accessibility Template (VPAT) for Cisco TelePresence Video Communication Server is
available here:
http://www.cisco.com/web/about/responsibility/accessibility/legal_regulatory/vpats.html#telepresence
You can find more information about accessibility here:
www.cisco.com/web/about/responsibility/accessibility/index.html
8
Using the Web Interface

System configuration is normally carried out through the web interface.
To use the web interface:
1. Open a browser window and in the address bar type either:

the IP address of the system
the FQDN of the system
2. Click Administrator Login.
(This step only applies if you are using "standalone FindMe" i.e. FindMe without Cisco TMSPE.)
3. Enter a valid administrator Username and Password and click Login (see the user accounts section for
details on setting up administrator accounts). You are presented with the Overview page.
Note that when logging in using the VCS web interface, you may receive a warning message regarding the VCS's
security certificate. This can safely be ignored.
A command line interface is also available.
Required fields
All mandatory fields on web pages are indicated by a red star .
Supported browsers
The VCS web interface is designed for use with Internet Explorer 8 or 9 (not in compatibility mode), Firefox 3 or later,
or Chrome. Later versions of Internet Explorer may also work, but are not officially supported. It may work with Opera
and Safari, but you could encounter unexpected behavior.
JavaScript and cookies must be enabled to use the VCS web interface.
9
Using the Command Line Interface (CLI)

The VCS can be configured through a web interface or via a command line interface (CLI).
The CLI is available by default over SSH and through the serial port. These settings are controlled on the System
administration page.
To use the CLI:
1. Start an SSH session.

2. Enter the IP address or FQDN of the VCS.
3. Log in with a username of admin and your system password.
4. You can now start using the CLI by typing the appropriate commands.
Command Types
Commands are divided into the following groups:
xStatus: these commands return information about the current status of the system. Information such as
current calls and registrations is available through this command group. See Command Reference xStatus,
page 483 for a full list of xStatus commands.
xConfiguration: these commands allow you to add and edit single items of data such as IP address and zones.
See Command Reference xConfiguration, page 400 for a full list of xConfiguration commands.
xCommand: these commands allow you to add and configure items and obtain information. See Command
Reference xCommand, page 459 for a full list of xCommand commands.
xHistory: these commands provide historical information about calls and registrations.
xFeedback: these commands provide information about events as they happen, such as calls and registrations.
Note that:
Typing an xConfiguration path into the CLI returns a list of values currently configured for that element (and
sub-elements where applicable).
Typing an xConfiguration path into the CLI followed by a ? returns information about the usage for that
element and sub-elements.
Typing an xCommand command into the CLI with or without a ? returns information about the usage of that
command.
10
Web Page Features and Layout

This section describes the features that can be found on the VCS web interface pages.
Figure 1 Example list page
Figure 2 Example configuration page
The elements included in the example web pages shown here are described in the table below.
Page Description
element
Page name Every page shows the page name and the menu path to that page. Each part of the menu
and location path is a link; clicking on any of the higher level menu items takes you to that page.
System This icon appears on the top right corner of every page when there is a system alarm in
alarm place. Click on this icon to go to the Alarms page which gives information about the alarm
and its suggested resolution.
Help This icon appears on the top right corner of every page. Clicking on this icon opens a new
browser window with help specific to the page you are viewing. It gives an overview of the
purpose of the page, and introduces any concepts configured from the page.
Log out This icon appears on the top right corner of every page. Clicking on this icon ends your
administrator session.
11
Page Description
element
Field level An information box appears on the configuration pages whenever you either click on the
information Information icon or click inside a field. This box gives you information about the particular
field, including where applicable the valid ranges and default value. To close the
information box, click on the X at its top right corner.
Information The VCS provides you with feedback in certain situations, for example when settings have
bar been saved or when you need to take further action. This feedback is given in a yellow
information bar at the top of the page.
Sorting Click on column headings to sort the information in ascending and descending order.
columns
Select All Use these buttons to select and unselect all items in the list.
and Unselect
All
Mandatory Indicates an input field that must be completed.

field
Peer- When a VCS is part of a cluster, most items of configuration are applied to all peers in a
specific cluster. However, items indicated with a must be specified separately on each cluster
configuration peer.
item
System The name of the user currently logged in and their access privileges, the system name (or
Information LAN 1 IPv4 address if no system name is configured), local system time, currently selected
language, serial number and VCS software version are shown at the bottom of the page.
Note that you cannot change configuration settings if your administrator account has read-only privileges.
12
Whats New in This Version?

The new features introduced in this release of VCS software are listed below.
Table 2 Feature History by Release Number
Feature / change X8.7
Dial via Office-Reverse (DVO-R) Supported
Lync Screen Sharing Through a Gateway Cluster Supported
Mobile and Remote Access with Cisco IPPhone 78/8800 Series Supported
Hybrid Services and Expressway/VCS Rebranding Supported
Hosting on VMWare vSphere 6.0 Supported
Keyword Filter for Syslog Output Supported
Changes and Minor Enhancements Supported
Dial via Office-Reverse Through MRA

Your mobile workers need the same high quality, security and reliability that they experience when placing calls in the
office. You can assure them of just that when you enable the Dial via Office-Reverse (DVO-R) feature and they are
using Cisco Jabber on a dual-mode mobile device. DVO-R routes Cisco Jabber calls through the enterprise
automatically.
DVO-R handles call signaling and voice media separately. All call signaling, including the signaling for Mobile and
Remote Access on VCS, traverses the IP connection between the client and Cisco Unified Communications Manager.
Voice media traverses the cellular interface and hairpins at the enterprise Public Switched Telephone Network
(PSTN) gateway.
Moving audio to the cellular interface ensures high-quality calls and securely maintained audio even when the IP
connection is lost.
You can configure DVO-R so that, when a user makes a call, the return call from Cisco Unified Communications
Manager goes to either:
The users Mobile Identity (mobile number).

An Alternate Number for the user (such as a hotel room).
This feature is dependent on the following versions of related systems:
Cisco Unified Communications Manager 11.0(1) or later

Cisco Jabber 11.1 or later
You can read more about how this feature works in the Mobile and Remote Access through VCS Deployment Guide
on the VCS Configuration Guides page.
Lync Screen Sharing Through a Gateway Cluster
Transcoding of Lync screen sharing was introduced in X8.6.
X8.7 extends this feature to work on a cluster of Gateway VCS peers, so that a greater number of screen sharing
sessions can be simultaneously transcoded.
You must configure the Lync B2BUA and the related transcoding parameters on the master peer. The number of
transcoding sessions you enter is the per peer number.
The transcoding capacity of the cluster is approximately the number of sessions you choose multiplied by the number
of peers, up to a maximum multiple of 4x.
13
For example, consider a cluster of four large VMs. If you set Maximum RDP transcode sessions to 20, then the
cluster would provide up to 80 simultaneous screen shares.
To configure your Cisco Collaboration environment to interoperate with Microsoft Lync, see the Microsoft Lync and
Cisco VCS Deployment Guide on the VCS Configuration Guides page.
Mobile and Remote Access with Cisco IPPhone 78/8800 Series
Mobile and Remote Access is now officially supported with the Cisco IPPhone 78/8800 Series, when the phones are
running firmware version 11.0(1) or later. We recommend VCS X8.7 or later for use with these phones.
Cisco IP Phone 8800 Series

MRAis officially supported with the Cisco DXSeries endpoints running firmware version 10.2.4(99) or later. This
support was announced with VCS version X8.6.
Cisco DX650
Cisco DX80
Cisco DX70
When deploying DXSeries or IPPhone 78/8800 Series endpoints to register with Cisco Unified Communications
Manager via Mobile and Remote Access, you need to be aware of the following:
Phone security profile: If the phone security profile for any of these endpoints has TFTPEncrypted Config
checked, you will not be able to use the endpoint via Mobile and Remote Access. This is because the
MRAsolution does not support devices interacting with CAPF(Certificate Authority Proxy Function).
Trust list: You cannot modify the root CAtrust list on these endpoints. Make sure that the VCS Expressway's
server certificate is signed by one of the CAs that the endpoints trust, and that the CA is trusted by the VCS
Control and the VCS Expressway.
Bandwidth restrictions: The Maximum Session Bit Rate for Video Calls on the default region on Cisco
Unified Communications Manager is 384 kbps by default. The Default call bandwidth on VCS Control is also
384 kbps by default. These settings may be too low to deliver the expected video quality for the DXSeries.
Hybrid Services and Expressway/VCSRebranding
We have changed some terminology in this release:
Expressway/VCS base
In previous versions of the Cisco Expressway Series and the Cisco TelePresence Video Communication
Server, the software was always branded as "VCSControl" before you activated it with a release key.
In X8.7, the product is now called "Expressway/VCSbase" when it is in this pre-activation state, which
shows that it can be activated as an Expressway or as a VCS.
These changes prepare us for a future release that will change the user experience of defining the purpose of
your VCS.
Hybrid Services
Version X8.6.1 included support for a feature called "Cloud Extensions". That feature has been renamed to
"Hybrid Services" in the UI, documentation, and Cloud Collaboration Management.
Hybrid Services is a group name for a family of user services that are delivered in part by the Cisco
Collaboration Cloud and in part by your on-premises equipment.
The Expressway/VCSbase does not need a release key to register for Hybrid Services. After you register the
Expressway/VCSbase, it will be branded "Cisco Expressway base". You don't need to apply a release key for
subsequent upgrades.
Note:For these reasons, we are requiring new Hybrid Services customers to use version X8.7. If you are using X8.6.1
for Hybrid Services, we strongly recommend upgrading to X8.7.
14
Hosting on VMWare vSphere 6.0

VCS virtual machines can now run on VMware vSphere version 6.0. Please be aware that we have noticed a known
issue in ESXi 6.0 during our testing. We recommend that you read http://kb.vmware.com/kb/2124669 before you
upgrade.
You can install new VCS OVAs on the ESXi 6.0 host, or you can migrate existing VMs. If you migrate a virtual VCS to a
different host, you must shut it down before you move it.
See the Cisco VCS Virtual Machine Installation Guide on the VCS Install and Upgrade Guides page.
Note:The virtual VCS now has virtual hardware version 8. This means that new installations of virtual VCS require
ESXi 5.0 or later, and will not run on ESX/ESXi 4.x or earlier.
Keyword Filter for Syslog Output
You can now use keywords to filter the logs that VCS sends to each remote syslog host. You can enter comma
delimited words or phrases, and the syslog daemon will only forward log messages that match at least one of those
keywords.
The keyword filter gives you more control over the types of messages that are published. You may only be interested
in some types of messages, or you may not be allowed to send potentially sensitive information over the channel to
the syslog server.
The user interface has also been improved as part of this change. In addition to the new keyword filter field, we've
added more granular control over the message format and transport connection. Previously, these options were
grouped into a "Mode" field and you could not configure them unless you chose the "Custom" mode.
Changes and Minor Enhancements
Multistream support is disabled in this release, pending a complete implementation in a future release.
Anew CLIcommand allows you to set the cipher suites used when the VCS authenticates with the ADdomain
for LDAPqueries. The command is xconfiguration Authentication ADS CipherSuite.
A Hybrid Services menu item has been added to the VCS Expressway, to support VCS-based hybrid services
that are currently in development. The new menu item (Applications >Hybrid Services >Certificate
management) has no explicit purpose for X8.7.
Anew system metric has been added to monitor each CPUcore independently.
New parameters have been added to the .ova file so you can configure the VM's network properties when
deploying through vCenter.
See Cisco VCS Virtual Machine Installation Guide on the VCS installation guides page.
There is a delay when you deploy virtual machines with pre-configured network parameters. The deployment
will take a few minutes longer than deploying the VMwithout pre-configured network parameters.
The VCS deployment guide now warns against choosing a single NIC, static NAT deployment of the VCS
Expressway. The preferred option for deploying the VCS Expressway in the DMZis to use both NICs.
See Cisco TelePresence VCS Basic Configuration (Control with Expressway) Deployment Guide on the VCS
configuration guides page.
15
Network and System Settings
This section describes network services and settings related options that appear under the System menu of the web
interface. These options enable you to configure the VCS in relation to the network in which it is located, for example
its IP settings, firewall rules, intrusion protection and the external services used by the VCS (for example DNS, NTP
and SNMP).
Network Settings 16
Intrusion Protection 21
Network Services 26
Configuring External Manager Settings 34
Configuring TMS Provisioning Extension services 34
Network Settings
Configuring Ethernet Settings

Use the Ethernet page (System > Network interfaces >Ethernet) to configure the speed of the connections between
the VCS and the Ethernet networks to which it is connected. The speed and duplex mode must be the same at both
ends of the connection. If you installed the Advanced Networking option, you can configure the speed and duplex
mode for each Ethernet port.
The default Speed is Auto, which means that the VCS and the connected switch will automatically negotiate the
speed and duplex mode.
Note: We recommend Auto unless the connected switch is unable to auto-negotiate. A mismatch in speed/duplex
mode between the two ends of the connection will cause packet loss and could make the system inaccessible.
Configuring IP Settings
The IP page (System > Network interfaces >IP) is used to configure the IP protocols and network interface settings
of the VCS.
IP Protocol Configuration
You can configure whether the VCS uses IPv4, IPv6 or Both protocols. The default is Both.
IPv4: it only accepts registrations from endpoints using an IPv4 address, and only takes calls between two
endpoints communicating via IPv4. It communicates with other systems via IPv4 only.
IPv6: it only accepts registrations from endpoints using an IPv6 address, and only takes calls between two
endpoints communicating via IPv6. It communicates with other systems via IPv6 only.
Both: it accepts registrations from endpoints using either an IPv4 or IPv6 address, and takes calls using either
protocol. If a call is between an IPv4-only and an IPv6-only endpoint, the VCS acts as an IPv4 to IPv6
gateway. It communicates with other systems via either protocol.
Some endpoints support both IPv4 and IPv6, however an endpoint can use only one protocol when registering with
the VCS. Which protocol it uses is determined by the format used to specify the IP address of the VCS on the
16
endpoint. After the endpoint has registered using either IPv4 or IPv6, the VCS only sends calls to it using this
addressing scheme. Calls made to that endpoint from another device using the other addressing scheme are
converted (gatewayed) by the VCS.
All IPv6 addresses configured on the VCS are treated as having a /64 network prefix length.
IPv4 to IPv6 Interworking
The VCS can act as a gateway for calls between IPv4 and IPv6 devices. To enable this feature, select an IP protocol
of Both. Calls for which the VCS is acting as an IPv4 to IPv6 gateway are traversal calls and require a traversal call
license.
IPGateways
You can set the default IPv4 gateway and IPv6 gateway used by the VCS. These are the gateways to which IP
requests are sent for IP addresses that do not fall within the VCSs local subnet.
The default IPv4 gateway is 127.0.0.1, which should be changed during the commissioning process.
The IPv6 gateway, if entered, must be a static global IPv6 address. It cannot be a link-local or a stateless
auto-configuration (SLAAC) IPv6 address.
LAN Configuration
LAN 1 is the primary network port on the VCS. You can configure the IPv4 address and subnet mask, the IPv6
address and the Maximum transmission unit (MTU) for this port.
The VCS is shipped with a default IP address of 192.168.0.100 (for both LAN ports). This lets you connect the
VCS to your network and access it via the default address so that you can configure it remotely.
The IPv6 address, if entered, must be a static global IPv6 address. It cannot be a link-local or a stateless
auto-configuration (SLAAC) IPv6 address.
If you have Advanced Networking installed, you can also configure these options for the LAN 2 port.
The Maximum transmission unit (MTU) defaults to 1500 bytes.
About Advanced Networking

The Advanced Networking option key enables the LAN 2 port on a VCS for both management and call signaling. This
allows you to have a second IP address for your VCS. The option key also enables static NAT functionality on a VCS
Expressway.
Configuring Dual Network Interfaces
Dual network interfaces are intended for deployments where the VCS Expressway is located in a DMZ between two
separate firewalls on separate network segments. In such deployments, routers prevent devices on the internal
network from being able to route IP traffic to the public internet, and instead the traffic must pass through an
application proxy such as the VCS Expressway.
To enable the use of dual network interfaces:
1. Ensure that the Advanced Networking option key is installed on the VCS Expressway.
2. Set Use dual network interfaces to Yes.
3. Set ExternalLAN interface to LAN2.
LAN 2 should be used as the public interface of the VCS Expressway (if the VCS Expressway is ever clustered,
LAN 1 must be used for clustering, and the clustering interface must not be mapped through a NAT).
This setting also determines the port from which TURN server relay allocations are made.
Note that:
17
You should configure the LAN 1 port and restart the VCS before configuring the LAN 2 port.
The LAN 1 and LAN 2 interfaces must be on different, non-overlapping subnets.
If you have Advanced Networking enabled but only want to configure one of the Ethernet ports, you must use
LAN 1.
If the VCS Expressway is in the DMZ, the outside IP address of the VCS Expressway must be a public IP
address, or if static NAT mode is enabled, the static NAT address must be publicly accessible.
The VCS Expressway may also be used to traverse internal firewalls within an enterprise. In this case the
"public" IP address may not be publicly accessible, but is an IP address accessible to other parts of the
enterprise.
If you need to change the IPaddresses on one or both interfaces, you can do it via the UIor the CLI. You can
change both at the same time if required, and the new addresses take effect after a restart.
Configuring Static NAT
You can deploy the VCS Expressway behind a static NAT device, allowing it to have separate public and private IP
addresses. This feature is intended for use in deployments where the VCS Expressway is located in a DMZ, and has
the Advanced Networking feature enabled.
In these deployments, the externally-facing LAN port has static NAT enabled in order to use both a private and public
IPv4 address; the internally facing LAN port does not have static NAT enabled and uses a single IPv4 (or IPv6)
address.
In such a deployment, traversal clients should be configured to use the internally-facing IP address of the VCS
Expressway.
To enable the use of a static NAT:
1. Ensure that the Advanced Networking option key is installed.

2. For the externally-facing LAN port:
a. In the IPv4 address field, enter the VCS Expressway's private IP address.
b. Set IPv4 static NAT mode to On.
c. In the IPv4 static NAT address field, enter the VCS Expressway's public IP address - this is the IP address
of the outside of the NAT.
Note:The combination of having static NATmode on and having the B2BUA engaged to do media
encryption/decryption can cause the firewall outside the VCS Expressway to mistrust packets originating from the
VCS Expressway. You can work around this by configuring the firewall to allow NATreflection. If your firewall cannot
allow this, you must configure the traversal path such that the B2BUAon the VCS Expressway is not engaged.
Configuring DNS Settings

The DNS page (System > DNS) is used to configure the VCS's DNS servers and DNS settings.
Configuring the System Host Name and Domain Name

The System host name defines the DNS host name that this VCS is known by.
It must be unique for each peer in a cluster.

It is used to identify the VCS on a remote log server (a default name of "TANDBERG" is used if the System
host name is not specified).
The Domain name is used when attempting to resolve unqualified server addresses (for example ldapserver). It is
appended to the unqualified server address before the query is sent to the DNS server. If the server address is fully
qualified (for example ldapserver.mydomain.com) or is in the form of an IP address, the domain name is not appended
to the server address before querying the DNS server.
It applies to the following configuration settings in the VCS:
18
LDAP server
NTP server
External Manager server
Remote logging server
You are recommended to use an IP address or FQDN (Fully Qualified Domain Name) for all server addresses.
Note that the FQDN of the VCS is the System host name plus the Domain name.
Impact on SIP messaging
The System host name and Domain name are also used to identify references to this VCS in SIP messaging, where
an endpoint has configured the VCS as its SIP proxy in the form of an FQDN (as opposed to an IP address, which is
not recommended).
In this case the VCS may, for example, reject an INVITE request if the FQDN configured on the endpoint does not
match the System host name and Domain name configured on the VCS. (Note that this check occurs because the
SIP proxy FQDN is included in the route header of the SIP request sent by the endpoint to the VCS.)
DNS requests
By default, DNS requests use a random port from within the system's ephemeral port range.
If required, you can specify a custom port range instead by setting DNSrequests port range to Use a custom port
range and then defining the DNS requests port range start and DNS requests port range end fields. Note that
setting a small source port range will increase your vulnerability to DNS spoofing attacks.
Configuring DNS Server Addresses

You must specify at least one DNS server to be queried for address resolution if you want to:
Use FQDNs (Fully Qualified Domain Names) instead of IP addresses when specifying external addresses (for
example for LDAP and NTP servers, neighbor zones and peers).
Use features such as URI dialing or ENUM dialing.
Default DNS servers
You can specify up to 5 default DNS servers.
The VCS only queries one server at a time; if that server is not available the VCS will try another server from
the list.
The order that the servers are specified is not significant; the VCS attempts to favor servers that were last
known to be available.
Per-domain DNS servers
In addition to the 5 default DNS servers, you can specify 5 additional explicit DNS servers for specified domains. This
can be useful in deployments where specific domain hierarchies need to be routed to their explicit authorities.
For each additional per-domain DNS server address you can specify up to 2 Domain names. Any DNS queries under
those domains are forwarded to the specified DNS server instead of the default DNS servers.
You can specify redundant per-domain servers by adding an additional per-domain DNS server address and
associating it with the same Domain names. In this scenario, DNS requests for those domains will be sent in parallel
to both DNS servers.
Tip: you can also use the DNS lookup tool (Maintenance > Tools > Network utilities > DNS lookup) to check which
domain name server (DNS server) is responding to a request for a particular hostname.
19
Caching DNSRecords
To improve performance, DNS lookups may be cached. This cache is flushed automatically whenever the DNS
configuration is changed.
You can also force the cache to be flushed by clicking Flush DNS cache.
Configuring Quality of Service Settings

The Quality of Service (QoS) page (System > Quality of Service) is used to configure QoS options for outbound
traffic from the VCS.
This allows the network administrator to tag all signaling and media packets flowing through the VCS with one
specific QoS tag and hence provide the ability to prioritize video traffic over normal data traffic. Management traffic,
for example SNMP messages, is not tagged.
Supported mechanisms
The VCS supports the DiffServ (Differentiated Services) mechanism which puts the specified Tag value in the TOS
(Type Of Service) field of the IPv4 header or TC (Traffic Class) field of the IPv6 header.
Static Routes
You can define static routes from the VCS to an IPv4 or IPv6 address range. Go to System >Network interfaces
>Static routes.
On this page you can view, add, and delete static routes.
Static routes are sometimes required when using the Advanced Networking option and deploying the VCS in a DMZ.
They may also be required in other complex network deployments.
To add a static route:
1. Enter the base destination address of the new static route from this VCS
For example, enter 203.0.113.0 or 2001:db8::
2. Enter the prefix length that defines the range
Extending the example, you could enter 24 to define the IPv4 range 203.0.113.0 - 203.0.113.255, or 32 to
define the IPv6 range 2001:db8:: to 2001:db8:ffff:ffff:ffff:ffff:ffff:ffff.
The address range field shows the range calculated by the VCS from the IPaddress and Prefix length.
3. Enter the IPaddress of the gateway for your new route
4. Select an ethernet interface for your new route
This option is only available if the second ethernet interface is enabled. Select LAN1 or LAN2 to force the
route via that interface, or select Auto to allow the VCS to make this route on either interface.
5. Click Create route
The new static route is listed in the table. You can delete routes from this table if necessary.
Notes
IP routes can also be configured using the CLI, using xCommand RouteAdd and the xConfiguration IPRoute
commands.
You can configure routes for up to 50 network and host combinations.
Do not configure IP routes by logging in as root and using ip route statements.
20
Intrusion Protection
Configuring Firewall Rules

Firewall rules provide the ability to configure IP table rules to control access to the VCS at the IP level. On the VCS,
these rules have been classified into groups and are applied in the following order:
Dynamic system rules: these rules ensure that all established connections/sessions are maintained. They also
include any rules that have been inserted by the automated detection feature as it blocks specific addresses.
Finally, it includes a rule to allow access from the loopback interface.
Non-configurable application rules: this incorporates all necessary application-specific rules, for example to
allow SNMP traffic and H.323 gatekeeper discovery.
User-configurable rules: this incorporates all of the manually configured firewall rules (as described in this
section) that refine and typically restrict what can access the VCS. There is a final rule in this group that
allows all traffic destined for the VCS LAN 1 interface (and the LAN 2 interface if the Advanced Networking
option key is installed).
There is also a final, non-configurable rule that drops any broadcast or multicast traffic that has not already been
specifically allowed or denied by the previous rules.
By default any traffic that is destined for the specific IP address of the VCS is allowed access, but that traffic will be
dropped if the VCS is not explicitly listening for it. You have to actively configure extra rules to lock down the system
to your specifications.
Note that return traffic from outbound connections is always accepted.
User-configured rules
The user-configured rules are typically used to restrict what can access the VCS. You can:
Specify the source IP address subnet from which to allow or deny traffic.
Choose whether to drop or reject denied traffic.
Configure well known services such as SSH, HTTP/HTTPS or specify customized rules based on transport
protocols and port ranges.
Configure different rules for the LAN 1 and LAN 2 interfaces (if the Advanced Networking option key is
installed), although note that you cannot configure specific destination addresses such as a multicast
address.
Specify the priority order in which the rules are applied.
Setting Up and Activating Firewall Rules

The Firewall rules configuration page is used to set up and activate a new set of firewall rules.
The set of rules shown will initially be a copy of the current active rules. (On a system where no firewall rules have
previously been defined, the list will be empty.) If you have a lot of rules you can use the Filter options to limit the set
of rules displayed. Note that the built-in rules are not shown in this list.
You can then change the set of firewall rules by adding new rules, or by modifying or deleting any existing rules. Any
changes made at this stage to the current active rules are held in a pending state. When you have completed making
all the necessary changes you can activate the new rules, replacing the previous set.
21
To set up and activate new rules:
1. Go to System >Protection > Firewall rules > Configuration.

2. Make your changes by adding new rules, or by modifying or deleting any existing rules as required.
You can change the order of the rules by using the up/down arrows and to swap the priorities of adjacent
rules.
New or modified rules are shown as Pending (in the State column).
Deleted rules are shown as Pending delete.
3. When you have finished configuring the new set of firewall rules, click Activate firewall rules.
4. Confirm that you want to activate the new rules. This will replace the existing set of active rules with the set
you have just configured.
After confirming that you want to activate the new rules, they are validated and any errors reported.
5. If there are no errors, the new rules are temporarily activated and you are taken to the Firewall rules
confirmation page.
You now have 15 seconds to confirm that you want to keep the new rules:
Click Accept changes to permanently apply the rules.
If the 15 seconds time limit expires or you click Rollback changes, the previous rules are reinstated and you
are taken back to the configuration page.
The automatic rollback mechanism provided by the 15 seconds time limit ensures that the client system that
activated the changes is still able to access the system after the new rules have been applied. If the client
system is unable to confirm the changes (because it can no longer access the web interface) then the
rollback will ensure that its ability to access the system is reinstated.
When configuring firewall rules, you also have the option to Revert all changes. This discards all pending changes
and resets the working copy of the rules to match the current active rules.
Rule settings
The configurable options for each rule are:
Field Description Usage tips
Priority The order in which the The rules with the highest priority (1, then 2, then 3 and so on) are
firewall rules are applied. applied first.
Firewall rules must have unique priorities. Rule activation will fail if
there are multiple rules with the same priority.
Interface The LAN interface on which This only applies if the Advanced Networking option key is installed.
you want to control access.
IPaddress These two fields together The Address range field shows the range of IP addresses to which
and Prefix determine the range of IP the rule applies, based on the combination of the IP address and
length addresses to which the rule Prefix length.
applies.
The prefix length range is 0-32 for an IPv4 address, and 0-128 for an
IPv6 address.
Service Choose the service to which Note that if the destination port of a service is subsequently
the rule applies, or choose reconfigured on the VCS, for example from 80 to 8080, any firewall
Custom to specify your own rules containing the old port number will not be automatically
transport type and port updated.
ranges.
Transport The transport protocol to Only applies if specifying a Custom service.

which the rule applies.
22
Start and The port range to which the Only applies if specifying a UDP or TCP Custom service.
end port rule applies.
Action The action to take against Dropping the traffic means that potential attackers are not provided
any IP traffic that matches with information as to which device is filtering the packets or why.
the rule.
For deployments in a secure environment, you may want to configure
Allow: Accept the traffic. a set of low priority rules (for example, priority 50000) that deny
access to all services and then configure higher priority rules (for
Drop: Drop the traffic example, priority 20) that selectively allow access for specific IP
without any response to the addresses.
sender.
Reject: Reject the traffic

with an 'unreachable'
response.
Description An optional free-form If you have a lot of rules you can use the Filter by description options
description of the firewall to find related sets of rules.
rule.
Current Active Firewall Rules

The Current active firewall rules page (System >Protection >Firewall rules > Current active rules) shows the user-
configured firewall rules that are currently in place on the system. There is also a set of built-in rules that are not
shown in this list.
If you want to change the rules you must go to the Firewall rules configuration page from where you can set up and
activate a new set of rules.
Configuring Automated Intrusion Protection

The automated protection service can be used to detect and block malicious traffic and to help protect the VCS from
dictionary-based attempts to breach login security.
It works by parsing the system log files to detect repeated failures to access specific service categories, such as SIP,
SSH and web/HTTPS access. When the number of failures within a specified time window reaches the configured
threshold, the source host address (the intruder) and destination port are blocked for a specified period of time. The
host address is automatically unblocked after that time period so as not to lock out any genuine hosts that may have
been temporarily misconfigured.
You can configure ranges of addresses that are exempted from one or more categories (see Configuring Exemptions,
page 25 below).
Automated protection should be used in combination with the firewall rules feature - use automated protection to
dynamically detect and temporarily block specific threats, and use firewall rules to permanently block a range of
known host addresses.
About protection categories
The set of available protection categories on your VCS are pre-configured according to the software version that is
running. You can enable, disable or configure each category, but you cannot add additional categories.
The rules by which specific log file messages are associated with each category are also pre-configured and cannot
be altered. You can view example log file entries that would be treated as an access failure/intrusion within a
particular category by going to System > Protection >Automated detection > Configuration and clicking on the
name of the category. The examples are displayed above the Status section at the bottom of the page.
23
Enabling Automated Protection

To enable intrusion protection on your VCS:
1. Go to System >Administration.
2. Set Automated protection service to On.
3. Click Save.
4. You must then ensure that the required protection categories are enabled and configured, and that any
required exemptions are specified, as described below.
All protection categories are disabled by default.
Configuring Protection Categories

The Automated detection overview page (System > Protection >Automated detection > Configuration) is used to
enable and configure the VCS's protection categories, and to view current activity.
The page displays a summary of all available categories, showing:
Status: this indicates if the category is configured to be On or Off. When On, it additionally indicates the state
of the category: this is normally Active, but may temporarily display Initializing or Shutting down when a
category has just been enabled or disabled. Check the alarms if it displays Failed.)
Currently blocked: the number of addresses currently being blocked for this category.
Total failures: the total number of failed attempts to access the services associated with this category.
Total blocks: the total number of times that a block has been triggered. Note that:
The Total blocks will typically be less than the Total failures (unless the Trigger level is set to 1).
The same address can be blocked and released several times per category, with each occurrence counting
as a separate block.
Exemptions: the number of addresses that are configured as exempt from this category.
From this page, you can also view any currently blocked addresses or any exemptions that apply to a particular
category.
Enabling and disabling categories
To enable or disable one or more protection categories:
1. Go to System > Protection >Automated detection > Configuration.

2. Select the check box alongside the categories you want to enable or disable.
3. Click Enable or Disable as appropriate.
Configuring a category's blocking rules
To configure a category's specific blocking rules:

2. Click on the name of the category you want to configure.
You are taken to the configuration page for that category.
24
3. Configure the category as required:

State: whether protection for that category is enabled or disabled.
Description: a free-form description of the category.
Trigger level and Detection window: these settings combine to define the blocking threshold for the
category. They specify the number of failed access attempts that must occur before the block is triggered,
and the time window in which those failures must occur.
Block duration: the period of time for which the block will remain in place.
4. Click Save.
Configuring Exemptions
The Automated detection exemptions page (System > Protection >Automated detection > Exemptions) is used to
configure any IP addresses that are to be exempted always from one or more protection categories.
To configure exempted addresses:
1. Go to System > Protection >Automated detection > Exemptions.

2. Click on the Address you want to configure, or click New to specify a new address.
3. Enter the Address and Prefix length to define the range of IPv4 addresses you want to exempt.
4. Select the categories from which the address is to be exempted.
5. Click Add address.
Note that if you exempt an address that is currently blocked, it will remain blocked until its block duration expires
(unless you unblock it manually via the Blocked addresses page).
Managing Blocked Addresses

The Blocked addresses page (System > Protection >Automated detection > Blocked addresses) is used to
manage the addresses that are currently blocked by the automated protection service:
It shows all currently blocked addresses and from which categories those addresses have been blocked.
You can unblock an address, or unblock an address and at the same time add it to the exemption list. Note
that if you want to permanently block an address, you must add it to the set of configured firewall rules.
If you access this page via the links on the Automated detection overview page it is filtered according to your chosen
category. It also shows the amount of time left before an address is unblocked from that category.
Investigating Access Failures and Intrusions

If you need to investigate specific access failures or intrusion attempts, you can review all the relevant triggering log
messages associated with each category. To do this:

2. Click on the name of the category you want to investigate.
3. Click View all matching intrusion protection triggers for this category.
The system will display all the relevant events for that category. You can then search through the list of
triggering events for the relevant event details such as a user name, address or alias.
Automated Protection Service and Clustered Systems

When the automated protection service is enabled in a clustered system:
Each peer maintains its own count of connection failures and the trigger threshold must be reached on each
peer for the intruder's address to be blocked by that peer.
25
Addresses are blocked against only the peer on which the access failures occurred. This means that if an
address is blocked against one peer it may still be able to attempt to access another peer (from which it may
too become blocked).
A blocked address can only be unblocked for the current peer. If an address is blocked by another peer, you
must log in to that peer and then unblock it.
Category settings and the exemption list are applied across the cluster.
The statistics displayed on the Automated detection overview page are for the current peer only.
Additional Information
When a host address is blocked and tries to access the system, the request is dropped (the host receives no
response).
A host address can be blocked simultaneously for multiple categories, but may not necessarily be blocked by
all categories. Those blocks may also expire at different times.
When an address is unblocked (either manually or after its block duration expires), it has to fail again for the
full number of times as specified by the category's trigger level before it will be blocked for a second time by
that category.
A category is reset whenever it is enabled. All categories are reset if the system is restarted or if the
automated protection service is enabled at the system level. When a category is reset:
Any currently blocked addresses are unblocked.
Its running totals of failures and blocks are reset to zero.
You can view all Event Log entries associated with the automated protection service by clicking View all
intrusion protection events on the Automated detection overview page.
Network Services
Configuring System Name and Access Settings

The System administration page (System > Administration) is used to configure the name of the VCS and the
means by which it is accessed by administrators.
System Settings
System name
The System name is used to identify the VCS. It appears in various places in the web interface, and in the display on
the front panel of the unit (so that you can identify it when it is in a rack with other systems). The System name is also
used by Cisco TMS.
We recommend that you give the VCS a name that allows you to easily and uniquely identify it.
Ephemeral port range
You can specify the Ephemeral port range start and end values. This defines the port range to use for ephemeral
outbound connections not otherwise constrained by VCS call processing.
The default range of 30000 35999 applies to new installations of X8.1 or later; the previous default range of 40000
49999 still applies to earlier releases that have upgraded to X8.1.
Administration Access Settings

While you can administer the VCS via a PC connected directly to the unit via a serial cable, you may want to access
the system remotely over IP. You can do this using either the web interface (via HTTPS) or through a command line
interface (via SSH).
The configurable options are:
26
Services
Serial port / Whether the system can be accessed Serial port / console access is always enabled for one
console locally via either the serial port (for a minute following a restart, even if it is normally disabled.
physical system) or VMware console
(for a virtual machine). Default is On.
SSH service Whether the VCS can be accessed via

SSH and SCP. Default is On.
Web interface Whether the VCS can be accessed via Cisco TMS accesses the VCS via the web server. If
(over HTTPS) the web interface. Default is On. HTTPS mode is turned off, Cisco TMS will not be able to
access it.
Session limits
Session time The number of minutes that an

out administration session (serial port,
HTTPS or SSH) or a FindMe session
may be inactive before the session is
timed out. Default is 30 minutes.
Per-account The number of concurrent sessions This includes web, SSH and serial sessions. Session
session limit that each individual administrator limits are not enforced on FindMe accounts or the root
account is allowed on each VCS. account.
A value of 0 turns session limits off.
System The maximum number of concurrent This includes web, SSH and serial sessions. Session
session limit administrator sessions allowed on limits are not enforced on FindMe accounts or the root
each VCS. account; however active root account sessions do count
towards the total number of current administrator
sessions.
A value of 0 turns session limits off.
System protection
Automated Whether the automated protection After enabling the service you must go and configure the
protection service is active. Default is Off. specific protection categories.
service
Automatic Controls how management systems You must restart the system for any changes to take
discovery such as Cisco TMS can discover this effect.
protection VCS.
Off: automatic discovery is allowed.
On: Cisco TMS has to be manually

configured to discover this VCS and
must provide administrator account
credentials.
Default is Off.
Web server configuration
Redirect HTTP Determines whether HTTP requests are HTTPS must also be enabled for access via HTTP to
requests to redirected to the HTTPS port. Default is function.
HTTPS On.
27
HTTP Strict Determines whether web browsers are See below for more information about HSTS.
Transport instructed to only ever use a secure
Security connection to access this server.
(HSTS) Enabling this feature gives added
protection against man-in-the-middle
(MITM) attacks.
On: the Strict-Transport-Security

header is sent with all responses from
the web server, with a 1 year expiry
time.
Off: the Strict-Transport-Security

header is not sent, and browsers work
as normal.
Default is On.
Client Controls the level of security required Important:

certificate- to allow client systems (typically web
based browsers) to communicate with the Enabling Certificate validation means that your browser
security VCS over HTTPS. (the client system) can use the VCS web interface only if
it has a valid (in date and not revoked by a CRL) client
Not required: the client system does certificate that is signed by a CA in the VCS's trusted CA
not have to present any form of certificate list.
certificate.
Ensure yourbrowser hasa valid client certificate before
Certificate validation: the client system enabling this feature. The procedure for uploading a
must present a valid certificate that certificate to your browser may vary depending on the
has been signed by a trusted browser type and you mayneed to restart your browser
certificate authority (CA). Note that a for the certificate to take effect.
restart is required if you are changing
from Not required to Certificate You can upload CA certificates on the Managing the
validation. Trusted CA Certificate List, page 282 page, and test
client certificates on the Testing Client Certificates,
Certificate-based authentication: the page 290 page.
client system must present a valid
certificate that has been signed by a Enabling Certificate-based authentication means that
trusted CA and contains the client's the standard login mechanism is no longer available.
authentication credentials. You can log in only if your browser certificate is valid and
the credentials it provides have the appropriate
Default: Not required authorization levels. You can configure how the VCS
extracts credentials from the browser certificate on the
Certificate-based authentication configuration page.
This setting does not affect client verification of the

VCS's server certificate.
28
Certificate Specifies whether HTTPS client Only applies if Client certificate-based security is
revocation list certificates are checked against enabled.
(CRL) certificate revocation lists (CRLs).
checking
None: no CRL checking is performed.
Peer: only the CRL associated with the

CA that issued the client's certificate is
checked.
All: all CRLs in the trusted certificate

chain of the CA that issued the client's
certificate are checked.
Default: All
CRL Controls the revocation checking Only applies if Client certificate-based security is
inaccessibility behavior if the revocation status enabled.
fallback cannot be established, for example if
behavior the revocation source cannot be
contacted.
Treat as revoked: treat the certificate

as revoked (and thus do not allow the
TLS connection).
Treat as not revoked: treat the

certificate as not revoked.
Default: Treat as not revoked
By default, access via HTTPS and SSH is enabled. For optimum security, disable HTTPS and SSH and use the serial
port to manage the system. Because access to the serial port allows the password to be reset, we recommend that
you install the VCS in a physically secure environment.
HTTP Strict Transport Security (HSTS)

HTTP Strict Transport Security (HSTS) provides a mechanism where a web server forces a web browser to
communicate with it using secure connections only.
As of August 2014, this mechanism is supported by the following browsers:
Chrome, versions 4.0.211.0 and later

Firefox, versions 4 and later
When HSTS is enabled, a browser that supports HSTS will:
Automatically turn any insecure links to the website into secure links (for example, http://example.com/page/
is modified to https://example.com/page/ before accessing the server).
Only allow access to the server if the connection is secure (for example, the server's TLS certificate is valid,
trusted and not expired).
Browsers that do not support HSTS will ignore the Strict-Transport-Security header and work as before. They will still
be able to access the server.
Compliant browsers only respect Strict-Transport-Security headers if they access the server through its fully qualified
name (rather than its IP address).
29
VCS Front Panel (legacy appliances only)

The LCD panel on the front of legacy (non-CE Series) VCS appliances unit has a rotating display of the VCS's system
name, IP addresses, alarms, and the number of current traversal calls, non-traversal calls and registrations.
To control the display of status items:
ENTER stops the display from automatically rotating through the status items. This is useful if you need to
review all of the alarms or read a long IPv6 address. Press ENTER again to resume the rotating display.
UP/DOWN displays the previous or next status item.
You can configure the front panel to hide this identifying information, if required for security reasons for example, by
using the CLI command xConfiguration Administration LCDPanel Mode. If the mode is set to Off the front panel only
displays "Cisco".
Configuring SNMP Settings

The SNMP page (System > SNMP) is used to configure the VCS's SNMP settings.
Tools such as Cisco TelePresence Management Suite (Cisco TMS) or HP OpenView may act as SNMP Network
Management Systems (NMS). They allow you to monitor your network devices, including the VCS, for conditions that
might require administrative attention.
The VCS supports the most basic MIB-II tree (.1.3.6.1.2.1) as defined in RFC 1213.
The information made available by the VCS includes the following:
system uptime
system name
location
contact
interfaces
disk space, memory, and other machine-specific statistics
By default, SNMP is Disabled, therefore to allow the VCS to be monitored by an SNMP NMS (including Cisco TMS),
you must select an alternative SNMP mode. The configurable options are:
SNMPmode Controls the level of SNMP support. If you want to use secure SNMPv3 but you also
use Cisco TMS as your external manager, you
Disabled: no SNMP support. must select v3 plus TMS support.
v3 secure SNMP: supports authentication
and encryption.
v3 plus TMS support: secure SNMPv3 plus

non-secure access to OID 1.3.6.1.2.1.1.2.0
only.
v2c: non-secure community-based SNMP.
Description Custom description of the system as viewed When you leave this field empty, the system uses
by SNMP. The default is to have no custom its default SNMPdescription.
description (empty field).
Community The VCS's SNMP community name. Only applies when using v2c or v3 plus TMS
name support.
The default is public.
30
System The name of the person who can be The System contact and Location are used for
contact contacted regarding issues with the VCS. reference purposes by administrators when
following up on queries.
The default is Administrator.
Location Specifies the physical location of the VCS.
Username The VCS's SNMP username, used to identify Only applies when using v3 secure SNMP or v3
this SNMP agent to the SNMP manager. plus TMS support
v3 Authentication settings (only applicable to SNMPv3)
Authentication Enables or disables SNMPv3 authentication.

mode
Type The algorithm used to hash authentication

credentials.
SHA: Secure Hash Algorithm.
MD5: Message-Digest algorithm 5.
The default is SHA.
Password The password used to encrypt authentication Must be at least 8 characters.

credentials.
v3 Privacy settings (only applicable to SNMPv3)
Privacy mode Enables or disables SNMPv3 encryption.
Type The security model used to encrypt

messages.
DES: Data Encryption Standard 56-bit

encryption.
AES: Advanced Encryption Standard 128-bit

encryption.
If available, the default and recommended

setting is AES.
Password The password used to encrypt messages. Must be at least 8 characters.
The VCS does not support SNMP traps or SNMP sets, therefore it cannot be managed via SNMP.
Note: SNMP is disabled by default, because of the potentially sensitive nature of the information involved. Do not
enable SNMP on a VCS on the public internet or in any other environment where you do not want to expose internal
system information.
Configuring Time Settings

The Time page (System > Time) is used to configure the VCS's NTP servers and to specify the local time zone.
An NTP server is a remote server with which the VCS synchronizes in order to ensure its time is accurate. The NTP
server provides the VCS with UTC time.
Accurate time is necessary for correct system operation.
31
Configuring the NTP Servers

To configure the VCS with one or more NTP servers to be used when synchronizing system time, enter the Address
of up to five servers in one of the following formats, depending on the system's DNS settings (you can check these
settings on the DNS page, System > DNS):
if there are no DNS servers configured, you must use an IP address for the NTP server
if there are one or more DNS servers configured, you can use an FQDN or IP address for the NTP server
if there is a DNS Domain name configured in addition to one or more DNS servers, you can use the server
name, FQDN or IP address for the NTP server
Three of the Address fields default to NTP servers provided by Cisco.
You can configure the Authentication method used by the VCS when connecting to an NTP server. Use one of the
following options for each NTP server connection:
Authentication Description
method
Disabled No authentication is used.
Symmetric key Symmetric key authentication. When using this method a Key ID, Hash method and Pass phrase
must be specified. The values entered here must match exactly the equivalent settings on the
NTPserver. You can use the same symmetric key settings across multiple NTP servers. However,
if you want to configure each server with a different pass phrase, you must also ensure that each
server has a unique key ID.
Private key Private key authentication. This method uses an automatically generated private key with which to
authenticate messages sent to the NTP server.
Displaying NTPstatus information

The synchronization status between the NTP server and the VCS is shown in the Status area as follows:
Starting: the NTPservice is starting.

Synchronized: the VCS has successfully obtained accurate system time from an NTP server.
Unsynchronized: the VCS is unable to obtain accurate system time from an NTP server.
Down: the VCS's NTP client is not running.
Reject: the NTPservice is not accepting NTPresponses.
Note that updates may take a few minutes to be displayed in the status table.
Other status information available includes:
Field Description
NTP server The actual NTP server that has responded to the request. This may be different to the NTP server
in the NTP server address field.
Condition Gives a relative ranking of each NTP server. All servers that are providing accurate time are given
a status of Candidate; of those, the server that the VCS considers to be providing the most
accurate time and is therefore using shows a status of sys.peer.
Flash A code giving information about the server's status. 00 ok means there are no issues. See the
Flash Status Word Reference Table, page 488 for a complete list of codes.
Authentication Indicates the status of the current authentication method. One of ok, bad or none. none is
specified when the Authentication method is Disabled.
32
Field Description
Event Shows the last event as determined by NTP (for example reachable or sys.peer)
Reachability Indicates the results of the 8 most recent contact attempts between the VCS and the NTP server,
with a tick indicating success and a cross indicating failure. The result of the most recent attempt
is shown on the far right.
Each time the NTP configuration is changed, the NTP client is restarted and the Reachability field
will revert to all crosses apart from the far right indicator which will show the result of the first
connection attempt after the restart. However, the NTP server may have remained contactable
during the restart process.
Offset The difference between the NTP server's time and the VCS's time.
Delay The network delay between the NTP server and the VCS.
Stratum The degree of separation between the VCS and a reference clock. 1 indicates that the NTP server
is a reference clock.
Ref ID A code identifying the reference clock.
Ref time The last time that the NTP server communicated with the reference clock.
For definitions of the remaining fields on this page, and for further information about NTP, see Network Time Protocol
website.
VCS Time Display and Time Zone

Local time is used throughout the web interface. It is shown in the system information bar at the bottom of the screen
and is used to set the timestamp that appears at the start of each line in the Event Log.
Note that UTC timestamps are included at the end of each entry in the Event Log.
Internally, the VCS maintains its system time in UTC. It is based on the VCS's operating system time, which is
synchronized using an NTP server if one is configured. If no NTP servers are configured, the VCS uses its own
operating system time to determine the time and date.
Specifying your local Time zone lets the VCS determine the local time where the system is located. It does this by
offsetting UTC time by the number of hours (or fractions of hours) associated with the selected time zone. It also
adjusts the local time to account for summer time (also known as daylight saving time) when appropriate.
Configuring the Login Page

The Login page configuration page (System > Login page) is used to specify a message and image to appear on the
login page for both users and administrators.
The Welcome message title and text will appear to administrators when attempting to log in using the CLI, and to
FindMe users and administrators when attempting to log in using the web interface.
You can upload an image that will appear above the welcome message on the login page when using the web
interface.
Supported image file formats are JPG, GIF and PNG.

Images larger than 200x200 pixels will be scaled down.
If the VCS is using the TMS Provisioning Extension services to provide FindMe account data, then users log into their
FindMe accounts through Cisco TMS, not through VCS.
Note that this feature is not configurable using the CLI.
33
Configuring External Manager Settings

The External manager page (System > External manager) is used to configure the VCS's connection to an external
management system.
An external manager is a remote system, such as the Cisco TelePresence Management Suite (Cisco TMS), used to
monitor events occurring on the VCS, for example call attempts, connections and disconnections, and as a place for
where the VCS can send alarm information. The use of an external manager is optional.
Address To use an external manager, If you are using Cisco TMS as your external manager, use the default
and path you must configure the VCS path of tms/public/external/management/
with the IP address or host SystemManagementService.asmx.
name and path of the external
manager to be used.
Protocol Determines whether

communications with the
external manager are over
HTTP or HTTPS. The default
is HTTPS.
Certificate Controls whether the If you enable verification, you must also add the certificate of the
verification certificate presented by the issuer of the external manager's certificate to the file containing the
mode external manager is verified. VCS's trusted CA certificates. This is done from the Managing the
Trusted CA Certificate List, page 282 page (Maintenance > Security
certificates > Trusted CA certificate).
Note that:
the VCS will continue to operate without loss of service if its connection to Cisco TMS fails. This applies even
if the VCSs are clustered. No specific actions are required as the VCS and Cisco TMS will automatically start
communicating with each other again after the connection is re-established.
Cisco TMS identifies the VCS as a "TANDBERG VCS".
Configuring TMS Provisioning Extension services

Cisco TMSPE services are hosted on Cisco TMS. They provide the user, device and phone book data that is used by
the VCS's Provisioning Server to service provisioning requests from endpoint devices. They also provide the VCS with
the FindMe account configuration data that it uses to provide FindMe services.
The TMS Provisioning Extension services page (System > TMS Provisioning Extension services) is used to
configure how the VCS connects to the Cisco TMSPE services. We recommend that you use Cisco TMS to make any
changes to the Cisco TMSPE services' configuration settings. Any changes made to the settings via this page will not
be applied within Cisco TMS.
The FindMe service can only be configured if the FindMe option key is installed, and the Users, Phone books and
Devices services can only be configured if the Device Provisioning option key is installed.
Default connection configuration
This section specifies default connection settings for accessing the Cisco TMSPE services. Each specific service
can choose to use these default settings or, alternatively, specify its own connection settings, for example if a
different Cisco TMSPE server is being used for each service.
34
Server address The IP address or Fully Qualified

Domain Name (FQDN) of the
service.
Destination port The listening port on the Cisco

TMSPE service. Default is 443.
Encryption The encryption to use for the A TLS connection is recommended.

connection to the Cisco TMSPE
service.
Off: no encryption is used.
TLS: TLS encryption is used.
Default is TLS.
Verify certificate Controls whether the certificate If you enable verification:

presented by the Cisco TMSPE
service is verified against the IIS (on the Cisco TMSPE server) must be installed
VCS's current trusted CA list and, with a signed certificate and be set to enforce SSL
if loaded, the revocation list. connections.
Default is Yes.
You must add the certificate of the issuer of the
Cisco TMSPE server's certificate to the file
containing the VCS's trusted CA certificates. This
is done from the Managing the Trusted CA
Certificate List, page 282 page (Maintenance >
Security certificates > Trusted CA certificate).
Check certificate Controls whether the hostname If enabled, the certificate hostname (also known as the
hostname contained within the certificate Common Name) must match the specified Server
presented by the Cisco TMSPE address. If the server address is an IP address, the
service is verified by the VCS. required hostname is obtained via a DNS lookup.
Default is Yes.
This only applies if Verify certificate is Yes.
Base group The ID used to identify this VCS (or The TMS administrator will supply this value.
VCS cluster) with the Cisco
TMSPE service. The Base group ID used by the Devices service must be
explicitly specified as it is normally different from that
used by the other services.
Authentication The username and corresponding If TLS encryption is not enabled, the authentication
username and password used by the VCS to password is sent in the clear.
password authenticate itself with the Cisco
TMSPE service.
Service-specific configuration
You can specify the connection details for each of the Cisco TMSPE services: Users, FindMe, Phone books and
Devices.
Connect to this Controls whether the VCS If enabled, the status of the connection is shown to the
service connects to the Cisco TMSPE right of the field; this can be either Checking, Active or
service. Default is No. Failed. Click details to view full status information.
35
Polling interval The frequency with which the VCS You can request an immediate update of all services by
checks the Cisco TMSPE service clicking Check for updates at the bottom of the page.
for updates. Defaults are:
FindMe: 2 minutes
Users: 2 minutes
Phone books: 1 day
The Device service polling interval

is set to 30 seconds and cannot be
modified.
Use the default Controls whether the service uses If No is selected, an additional set of connection
connection the default connection configuration parameters will appear. You can then
configuration configuration for Cisco TMSPE specify alternative connection details for the service that
services. Default is Yes. will override those specified in the Default connection
configuration section.
A full and immediate resynchronization of all data between the VCS and Cisco TMS can be triggered at any time by
clicking Perform full synchronization (at the bottom of the of the TMS Provisioning Extension services page). Note
that this will result in a temporary (a few seconds) lack of service on the VCS while the data is deleted and fully
refreshed. If you only need to ensure that all of the latest updates within Cisco TMS have been supplied to the VCS
then click Check for updates instead.
Further status information
The menu options under Status > Applications > TMS Provisioning Extension services provide full status
information about the Cisco TMSPE services, including:
the status of the connection between the VCS and the Cisco TMSPE services
views of the user, FindMe and phone book data supplied by the Cisco TMSPE services
a summary of the requests received from endpoint devices and the number of provisioning licenses being
consumed
the status of the devices that are making provisioning requests to the VCS's Provisioning Server
36
37
Firewall Traversal
This section describes how to configure your VCS Control and VCS Expressway in order to traverse firewalls.
About Firewall Traversal 38

Configuring a Traversal Client and Server 41
Configuring Ports for Firewall Traversal 42
Firewall Traversal and Authentication 46
Configuring Expressway and Traversal Endpoint Communications 46
About ICE and TURN Services 47
About Firewall Traversal

The purpose of a firewall is to control the IP traffic entering your network. Firewalls will generally block unsolicited
incoming requests, meaning that any calls originating from outside your network will be prevented. However, firewalls
can be configured to allow outgoing requests to certain trusted destinations, and to allow responses from those
destinations. This principle is used by Cisco's Expressway technology to enable secure traversal of any firewall.
The Expressway Solution

The Expressway solution consists of:
AVCS Expressway located outside the firewall on the public network or in the DMZ, which acts as the firewall
traversal server.
A VCS Control or other traversal-enabled endpoint located in a private network, which acts as the firewall
traversal client.
The two systems work together to create an environment where all connections between the two are outbound, i.e.
established from the client to the server, and thus able to successfully traverse the firewall.
We recommend that both the VCS Expressway and the VCS Control run the same software version.
How Does it Work?

The traversal client constantly maintains a connection via the firewall to a designated port on the traversal server.
This connection is kept alive by the client sending packets at regular intervals to the server. When the traversal server
receives an incoming call for the traversal client, it uses this existing connection to send an incoming call request to
the client. The client then initiates the necessary outbound connections required for the call media and/or signaling.
This process ensures that from the firewalls point of view, all connections are initiated from the traversal client inside
the firewall out to the traversal server.
For firewall traversal to function correctly, the VCS Expressway must have one traversal server zone configured on it
for each client system that is connecting to it (this does not include traversal-enabled endpoints which register
directly with the VCS Expressway; the settings for these connections are configured in a different way). Likewise,
each VCS client must have one traversal client zone configured on it for each server that it is connecting to.
38
The ports and protocols configured for each pair of client-server zones must be the same. See the Configuring a
Traversal Client and Server, page 41 for a summary of the required configuration on each system. Because the VCS
Expressway listens for connections from the client on a specific port, you are recommended to create the traversal
server zone on the VCS Expressway before you create the traversal client zone on the VCS Control.
Note that the traversal client and the traversal server must both be VCS systems (neither can be a Cisco Expressway).
Endpoint Traversal Technology Requirements

The "far end" (at home or at a hotel, for example) endpoint requirements to support firewall traversal are summarized
below:
For H.323, the endpoint needs to support Assent or H460.18 and H460.19.
For SIP, the endpoint just needs to support standard SIP.
Registration messages will keep the "far end" firewall ports open for VCS to send messages to that
endpoint. The VCS waits for media from the endpoint behind the firewall, before returning media to it on
that same port the endpoint does have to support media transmission and reception on the same port.
The VCS also supports SIP outbound, which is an alternative method of keeping firewalls open without the
overhead of using the full registration message.
SIP and H.323 endpoints can register to the VCS Expressway or they can just send calls to the VCS
Expressway as the local "DMZ" firewall has relevant ports open to allow communication to the VCS
Expressway over SIP and H.323 ports.
Endpoints can also use ICE to find the optimal (in their view of what optimal is) path for media communications
between themselves. Media can be sent directly from endpoint to endpoint, from endpoint via the outside IP address
of the destination firewall to the destination endpoint, or from the endpoint via a TURN server to destination endpoint.
The VCS supports ICE for calls where the VCS does not have to traverse media (for example if there is no
IPv4/IPv6 conversion or SIP / H.323 conversion required); typically this means 2 endpoints which are able to
support ICE, directly communicating to a VCS Expressway cluster.
The VCS Expressway has its own built-in TURN server to support ICE-enabled endpoints.
H.323 Firewall Traversal Protocols

The VCS supports two different firewall traversal protocols for H.323: Assent and H.460.18/H.460.19.
Assent is Ciscos proprietary protocol.

H.460.18 and H.460.19 are ITU standards which define protocols for the firewall traversal of signaling and
media respectively. These standards are based on the original Assent protocol.
A traversal server and traversal client must use the same protocol in order to communicate. The two protocols each
use a different range of ports.
SIP Firewall Traversal Protocols

The VCS supports the Assent protocol for SIP firewall traversal of media.
The signaling is traversed through a TCP/TLS connection established from the client to the server.
Media Demultiplexing
The VCS Expressway uses media demultiplexing in the following call scenarios:
Any H.323 or SIP call leg to/from a VCS Control through a traversal zone configured to use Assent.
Any H.323 call leg to/from a VCS Control through a traversal server zone configured to use H460.19 in
demultiplexing mode
H.323 call legs between a VCS Expressway and an Assent or H.460.19 enabled endpoint
39
The VCS Expressway uses non-demultiplexed media for call legs directly to/from SIP endpoints (that is endpoints
which do not support Assent or H.460.19), or if the traversal server zone is not configured to use H.460.19 in
demultiplexing mode.
Media demultiplexing ports on the VCS Expressway are allocated from the general range of traversal media ports.
This applies to all RTP/RTCP media, regardless of whether it is H.323 or SIP. On new installations of X8.1 or later, the
default media traversal port range is 36000 to 59999, and is set on the VCS Control (Configuration >Local Zones
>Traversal Subzone). In Large VCS Expressway systems the first 12 ports in the range 36000 to 36011 by default
are always reserved for multiplexed traffic. The VCS Expressway listens on these ports. You cannot configure a
distinct range of demultiplex listening ports on Large systems: they always use the first 6 pairs in the media port
range. On Small/Medium systems you can explicitly specify which 2 ports listen for multiplexed RTP/RTCP traffic, on
the VCS Expressway (Configuration > Traversal >Ports). On upgrades to X8.2 or later, the VCS Control retains the
media traversal port range from the previous version (could be 50000 - 54999 or 36000 - 59999, depending on source
version). The VCS Expressway retains the previously configured demultiplexing pair (either 2776 & 2777 or 50000 &
50001 by default, depending on upgrade path) and the switch Use configured demultiplexing ports is set to Yes. If
you do not want to use a particular pair of ports, switch Use configured demultiplexing ports to No, then the VCS
Expressway will listen on the first pair of ports in the media traversal port range (36000 and 36001 by default). In this
case, we recommend that you close the previously configured ports after you configure the firewall for the new ports.
For example, in a SIP call from within an enterprise to an endpoint at home through a VCS Control/VCS Expressway
pair, the only demultiplexing that would occur would be on the VCS Expressway ports facing the VCS Control:
Enterprise VCS Control VCS Expressway Home

endpoint endpoint
Non- Non- Demuxed Non-

demuxed demuxed demuxed
RTP ports 36002 36004 36000 36002
RTCP ports 36003 36005 36001 36003
However, an H.323 call from within an enterprise to an Assent capable H.323 endpoint at home through the same
VCS Control/VCS Expressway would perform demultiplexing on both sides of the VCS Expressway:
Enterprise VCS Control VCS Expressway Home

endpoint endpoint
Non- Non- Demuxed Demuxed

demuxed demuxed
RTP ports 36002 36004 36000 36000
RTCP ports 36003 36005 36001 36001
If the VCS Expressway has Advanced Networking, it will still use the same port numbers as described above, but they
will be assigned to the internal and external IP addresses.
Firewall Traversal Configuration Overview

This section provides an overview to how the VCS can act as a traversal server or as a traversal client.
VCS as a Firewall Traversal Client

The VCS can act as a firewall traversal client on behalf of SIP and H.323 endpoints registered to it, and any systems
that are neighbored with it. To act as a firewall traversal client, the VCS must be configured with information about
the systems that will act as its firewall traversal server.
You do this by adding a traversal client zone on the VCS client (Configuration > Zones >Zones) and configuring it
with the details of the traversal server. See Configuring Traversal Client Zones, page 146 for more information. You
can create more than one traversal client zone if you want to connect to multiple traversal servers.
Note that:
40
In most cases, you will use a VCS Control as a firewall traversal client. However, a VCS Expressway can also
act as a firewall traversal client.
The firewall traversal server used by the VCS client must be a VCS Expressway.
VCS as a Firewall Traversal Server

The VCS Expressway has all the functionality of a VCS Control (including being able to act as a firewall traversal
client). However, its main feature is that it can act as a firewall traversal server for other Cisco systems and any
traversal-enabled endpoints that are registered directly to it. It can also provide TURN relay services to ICE-enabled
endpoints.
Configuring Traversal Server Zones
For the VCS Expressway to act as a firewall traversal server for Cisco systems, you must create a traversal server
zone on the VCS Expressway (Configuration > Zones > Zones) and configure it with the details of the traversal client.
See Configuring Traversal Server Zones, page 149 for more information.
You must create a separate traversal server zone for every system that is its traversal client.
Configuring Other Traversal Server Features
For the VCS Expressway to act as a firewall traversal server for traversal-enabled endpoints (such as Cisco
MXP endpoints and any other endpoints that support the ITU H.460.18 and H.460.19 standards), no additional
configuration is required. See Configuring Expressway and Traversal Endpoint Communications, page 46 for
more information.
To enable TURN relay services and find out more about ICE, see About ICE and TURN Services, page 47.
To reconfigure the default ports used by the VCS Expressway, see Configuring Ports for Firewall Traversal,
page 42.
Firewall Traversal and Advanced Networking
The Advanced Networking option key enables the LAN 2 interface on the VCS Expressway (the option is not available
on a VCS Control). The LAN 2 interface is used in situations where the VCS Expressway is located in a DMZ that
consists of two separate networks - an inner DMZ and an outer DMZ - and your network is configured to prevent
direct communication between the two.
With the LAN 2 interface enabled, you can configure the VCS with two separate IP addresses, one for each network
in the DMZ. Your VCS then acts as a proxy server between the two networks, allowing calls to pass between the
internal and outer firewalls that make up your DMZ.
When Advanced Networking is enabled, all ports configured on the VCS, including those relating to firewall traversal,
apply to both IP addresses; you cannot configure ports separately for each IP address.
Configuring a Traversal Client and Server

The basic steps in configuring a traversal client and server are as follows:
Step Description
On the VCS Expressway, create a traversal server zone (this represents the incoming connection from the
VCS Control). In the Username field, enter the VCS Controls authentication username.
On the VCS Expressway, add the VCS Controls authentication username and password as credentials into
the local authentication database.
On the VCS Control, create a traversal client zone (this represents the connection to the VCS Expressway).
41
Step Description
Enter the same authentication Username and Password as specified on the VCS Expressway.
Configure all the modes and ports in the H.323 and SIP protocol sections to match identically those of the
traversal server zone on the VCS Expressway.
Enter the VCS Expressways IP address or FQDN in the Peer 1 address field.
Configuring Ports for Firewall Traversal

Ports play a vital part in firewall traversal configuration. The correct ports must be set on the VCS Expressway,
traversal client and firewall in order for connections to be permitted.
Ports are initially configured on the VCS Expressway by the VCS Expressway administrator. The firewall administrator
and the traversal client administrator should then be notified of the ports, and they must configure their systems to
connect to these specific ports on the server. The only port configuration required on the traversal client is the range
of ports it uses for outgoing connections; the firewall administrator may need to know this information so that if
necessary they can configure the firewall to allow outgoing connections from those ports.
42
The Port Usage, page 304 pages (under Maintenance > Tools > Port usage) list all the IP ports that are being used on
the VCS, both inbound and outbound. This information can be provided to your firewall administrator so that the
firewall can be configured appropriately.
The Expressway solution works as follows:
1. Each traversal client connects via the firewall to a unique port on the VCS Expressway.
2. The server identifies each client by the port on which it receives the connection, and the authentication
credentials provided by the client.
3. After the connection has been established, the client regularly sends a probe to the VCS Expressway to keep
the connection alive.
4. When the VCS Expressway receives an incoming call for the client, it uses this initial connection to send an
incoming call request to the client.
5. The client then initiates one or more outbound connections. The destination ports used for these connections
differ for signaling and/or media, and depend on the protocol being used (see the following sections for more
details).
Configuring the Firewall

For Expressway firewall traversal to function correctly, your firewall must be configured to:
allow initial outbound traffic from the client to the ports being used by the VCS Expressway
allow return traffic from those ports on the VCS Expressway back to the originating client
Note: we recommend that you turn off any H.323 and SIP protocol support on the firewall: these are not needed in
conjunction with the Expressway solution and may interfere with its operation.
Configuring Traversal Server Ports

The VCS Expressway has specific listening ports used for firewall traversal. Rules must be set on your firewall to allow
connections to these ports. In most cases the default ports should be used. However, you have the option to change
these ports if necessary by going to the Ports page (Configuration > Traversal > Ports).
The configurable ports for signaling are:
H.323 Assent call signaling port; default is 2776

H.323 H.460.18 call signaling port; default is 2777
RTP and RTCP Media Demultiplexing Ports

The port configuration options depend upon the type of appliance or VM:
Small/Medium systems: 1 pair of RTP and RTCP media demultiplexing ports are used. They can either be
explicitly specified or they can be allocated from the start of the general range of traversal media ports.
Large systems: 6 pairs of RTP and RTCP media demultiplexing ports are used. They are always allocated from
the start of the traversal media ports range.
Configuring Ports for Connections From Traversal Clients

Each traversal server zone specifies an H.323 port and a SIP port to use for the initial connection from the client. Each
time you configure a new traversal server zone on the VCS Expressway, you are allocated default port numbers for
these connections:
43
H.323 ports start at UDP/6001 and increment by 1 for every new traversal server zone.
SIP ports start at TCP/7001 and increment by 1 for every new traversal server zone.
You can change these default ports if necessary but you must ensure that the ports are unique for each traversal
server zone. After the H.323 and SIP ports have been set on the VCS Expressway, matching ports must be configured
on the corresponding traversal client. Note that:
The default port used for the initial connections from MXP endpoints is the same as that used for standard RAS
messages, that is UDP/1719. While you can change this port on the VCS Expressway, most endpoints will not
support connections to ports other than UDP/1719, therefore we recommend that you leave this as the
default.
You must allow outbound connections through your firewall to each of the unique SIP and H.323 ports that are
configured on each of the VCS Expressways traversal server zones.
The following table shows the default ports used for connections to the VCS Expressway.
Table 3 Default traversal port connections
Protocol Call signaling Media
Assent UDP/1719: listening The RTP and RTCP media demultiplexing ports in Large system are always
port for RAS allocated from the start of the general range of traversal media ports
messages (UDP/36000-36011*). In Small/Medium systems the media demultiplexing
ports can either be explicitly specified or they can be allocated from the
TCP/2776: listening start of the traversal media ports range.
port for H.225 and
H.245 protocols
H.460.18/19 UDP/1719: listening The RTP and RTCP media demultiplexing ports in Large systems are always
port for RAS allocated from the start of the general range of traversal media ports
messages (UDP/36000-36011*). In Small/Medium systems the media demultiplexing
ports can either be explicitly specified or they can be allocated from the
TCP/1720: listening start of the traversal media ports range.
port for H.225
protocol RTP and RTCP media non-demultiplexing ports are allocated from the
remainder of the traversal media ports range: UDP/36002-59999*.
TCP/2777: listening
port for H.245
protocol
SIP SIP call signaling Where the traversal client is a VCS, SIP media uses Assent to traverse the
uses the same port as firewall.
used by the initial
connection between
the client and server.
* On new installations of X8.1 or later, the default media traversal port range is 36000 to 59999, and is set on the VCS
Control (Configuration >Local Zones >Traversal Subzone). In Large VCS Expressway systems the first 12 ports in
the range 36000 to 36011 by default are always reserved for multiplexed traffic. The VCS Expressway listens on
these ports. You cannot configure a distinct range of demultiplex listening ports on Large systems: they always use
the first 6 pairs in the media port range. On Small/Medium systems you can explicitly specify which 2 ports listen for
multiplexed RTP/RTCP traffic, on the VCS Expressway (Configuration > Traversal >Ports). On upgrades to X8.2 or
later, the VCS Control retains the media traversal port range from the previous version (could be 50000 - 54999 or
36000 - 59999, depending on source version). The VCS Expressway retains the previously configured demultiplexing
pair (either 2776 & 2777 or 50000 & 50001 by default, depending on upgrade path) and the switch Use configured
demultiplexing ports is set to Yes. If you do not want to use a particular pair of ports, switch Use configured
demultiplexing ports to No, then the VCS Expressway will listen on the first pair of ports in the media traversal port
range (36000 and 36001 by default). In this case, we recommend that you close the previously configured ports after
you configure the firewall for the new ports.
44
The call signaling ports are configured via Configuration > Traversal > Ports. The traversal media port range is
configured via Configuration > Local Zone > Traversal Subzone.
If your VCS Expressway does not have any endpoints registering directly with it, and it is not part of a cluster, then
UDP/1719 is not required. You therefore do not need to allow outbound connections to this port through the firewall
between the VCS Control and VCS Expressway.
Configuring TURN Ports

The VCS Expressway can be enabled to provide TURN services (Traversal Using Relays around NAT) which can be
used by ICE-enabled SIP endpoints.
The ports used by these services are configurable via Configuration > Traversal > TURN.
The ICE clients on each of the SIP endpoints must be able to discover these ports, either by using SRV records in DNS
or by direct configuration.
Configuring Ports for Connections Out to the Public Internet

In situations where the VCS Expressway is attempting to connect to an endpoint on the public internet, you will not
know the exact ports on the endpoint to which the connection will be made. This is because the ports to be used are
determined by the endpoint and advised to the VCS Expressway only after the server has located the endpoint on the
public internet. This may cause problems if your VCS Expressway is located within a DMZ (where there is a firewall
between the VCS Expressway and the public internet) as you will not be able to specify in advance any rules that will
allow you to connect out to the endpoints ports.
You can however specify the ports on the VCS Expressway that are used for calls to and from endpoints on the public
internet so that your firewall administrator can allow connections via these ports. The ports that can be configured for
this purpose are:
Table 4 Port connections out to the public internet
H.323 SIP TURN
TCP/1720: signaling TCP/5061: signaling UDP/3478 (default): TURN services **
UDP/1719: signaling UDP/5060 (default): signaling UDP/24000-29999 (default range):

media **
UDP/36000-59999: media* UDP/36000-59999: media*
TCP/15000-19999: signaling TCP: a temporary port in the range

25000-29999 is allocated
** On Large systems you can configure a range of TURN request listening ports. The default range is 3478 3483.
The default TURN relay media port range of 24000 29999 applies to new installations of X8.1 or later. The previous
default range of 60000 61799 still applies to earlier releases that have upgraded to X8.1.
45
Firewall Traversal and Authentication

The VCS Expressway allows only authenticated client systems to use it as a traversal server.
Upon receiving the initial connection request from the traversal client, the VCS Expressway asks the client to
authenticate itself by providing its authentication credentials. The VCS Expressway then looks up the clients
credentials in its own authentication database. If a match is found, the VCS Expressway accepts the request from the
client.
The settings used for authentication depend on the type of traversal client:
Traversal client VCS Expressway traversal server
VCS Control (or VCS Expressway) The traversal server zone for the VCS client must be
configured with the client's authentication Username. This is
The VCS client provides its Username and set on the VCS Expressway by using Configuration > Zones >
Password. These are set on the traversal client Zones > Edit zone, in the Connection credentials section.
zone by using Configuration > Zones > Zones >
Edit zone, in the Connection credentials section. There must also be an entry in the VCS Expressways
authentication database with the corresponding client
username and password.
Endpoint There must be an entry in the VCS Expressways

authentication database with the corresponding client
The endpoint client provides its Authentication ID username and password.
and Authentication Password.
Note that all VCS traversal clients must authenticate with the VCS Expressway, even if the VCS Expressway is not
using device authentication for endpoint clients.
Authentication and NTP

All VCS traversal clients that support H.323 must authenticate with the VCS Expressway. The authentication process
makes use of timestamps and requires that each system uses an accurate system time. The system time on a VCS is
provided by a remote NTP server. Therefore, for firewall traversal to work, all systems involved must be configured
with details of an NTP server.
Configuring Expressway and Traversal Endpoint Communications

Traversal-enabled H.323 endpoints can register directly with the VCS Expressway and use it for firewall traversal.
The Locally registered endpoints page (Configuration > Traversal > Locally registered endpoints) allows you to
configure the way in which the VCS Expressway and traversal-enabled endpoints communicate.
The options available are:
Field Description
H.323 Assent Determines whether or not H.323 calls using Assent mode for firewall traversal are allowed.
mode
H.460.18 mode Determines whether or not H.323 calls using H.460.18/19 mode for firewall traversal are allowed.
H.460.19 Determines whether the VCS Expressway operates in demultiplexing mode for calls from locally
demux mode registered endpoints.
On: uses the media demultiplexing ports for all calls.
Off: each call uses a separate pair of ports for media.
46
Field Description
H.323 Determines which protocol the VCS Expressway uses if an endpoint supports both Assent and
preference H.460.18.
UDP probe The frequency (in seconds) with which locally registered endpoints send a UDP probe to the VCS
retry interval Expressway.
UDP probe The number of times locally registered endpoints attempt to send a UDP probe to the VCS
retry count Expressway.
UDP probe The interval (in seconds) with which locally registered endpoints send a UDP probe to the VCS
keep alive Expressway after a call is established, in order to keep the firewalls NAT bindings open.
interval
TCP probe The frequency (in seconds) with which locally registered endpoints send a TCP probe to the VCS
retry interval Expressway.
TCP probe The number of times locally registered endpoints attempt to send a TCP probe to the VCS
retry count Expressway.
TCP probe The interval (in seconds) with which locally registered endpoints send a TCP probe to the VCS
keep alive Expressway after a call is established, in order to keep the firewalls NAT bindings open.
interval
About ICE and TURN Services
About ICE
ICE (Interactive Connectivity Establishment) provides a mechanism for SIP client NAT traversal. ICE is not a protocol,
but a framework which pulls together a number of different techniques such as TURN and STUN.
It allows endpoints (clients) residing behind NAT devices to discover paths through which they can pass media, verify
peer-to-peer connectivity via each of these paths and then select the optimum media connection path. The available
paths typically depend on any inbound and outbound connection restrictions that have been configured on the NAT
device. Such behavior is described in RFC 4787.
An example usage of ICE is two home workers communicating via the internet. If the two endpoints can communicate
via ICE the VCS Expressway may (depending on how the NAT devices are configured) only need to take the signaling
and not take the media (and is therefore a non-traversal call). If the initiating ICE client attempts to call a non-ICE
client, the call set-up process reverts to a conventional SIP call requiring NAT traversal via media latching where the
VCS also takes the media and thus requires a traversal license.
For more information about ICE, see RFC 5245.
About TURN
TURN (Traversal Using Relays around NAT) services are relay extensions to the STUN network protocol that enable a
SIP or H.323 client to communicate via UDP or TCP from behind a NAT device.
For more information about TURN see RFC 5766, and for detailed information about the base STUN protocol, see RFC
5389.
Each ICE client requests the TURN server to allocate relays for the media components of the call. A relay is required
for each component in the media stream between each client.
After the relays are allocated, each ICE client has 3 potential connection paths (addresses) through which it can send
and receive media:
its host address which is behind the NAT device (and thus not reachable from endpoints on the other side of
the NAT)
47
its publicly-accessible address on the NAT device

a relay address on the TURN server
The endpoints then decide, by performing connectivity checks through ICE, how they are going to communicate.
Depending upon how the NAT devices are configured, the endpoints may be able to communicate between their
public-facing addresses on the NAT devices or they may have to relay the media via the TURN server. If both
endpoints are behind the same NAT device they can send media directly between themselves using their internal host
addresses.
After the media route has been selected, the TURN relay allocations are released if the chosen connection paths do
not involve routing via the TURN server. Note that the signaling always goes via the VCS, regardless of the final media
communication path chosen by the endpoints.
Capabilities and limitations
Small/Medium systems support up to 1800 relay allocations. This is typically enough to support 100 calls but
does depend on the network topology and the number of media stream components used for the call (for
example, some calls may use Duo Video, or other calls might be audio only).
A Large system supports up to 6000 relays, spread evenly across 6 ports where each port is limited to handling
1000 relays. This limit is not strictly enforced, so we recommend adding an SRVrecord for each port to enable
round robin.
Clustered VCSs: if the requested TURN server's relays are fully allocated the server will respond to the
requesting client with the details of an alternative server in the cluster (the TURN server currently with the
most available resources).
The VCS's TURN services are supported over single and dual network interfaces (via the Advanced
Networking option). For dual network interfaces, the TURN server listens on both interfaces but relays are
allocated only on the VCS's externally facing LAN interface.
Media negotiation may fail when VCS Control version X7.2 (or newer) TURNclient negotiates with VCS
Expressway version X7.1 TURNserver. Because the more recent client version can support IPv6 TURN, it adds
a new attribute in the request to the server (irrespective of whether the request is for IPv4 or IPv6 TURN). The
X7.1 TURNserver does not understand the new attribute.
You can work around this issue by upgrading the VCS Expressway to version X7.2 or newer, preferably the
same version as on the VCS Control. We recommend that you maintain the same software versions on the
VCS Control and VCS Expressway.
Microsoft ICE (which is not standards-based) is not supported by the VCS Expressway's TURN server; to
enable communications between the VCS and Microsoft Lync clients that are registered through a Microsoft
Edge Server you need to use the B2BUA for Microsoft Lync.
The TURN server does not support bandwidth requests. Traversal zone bandwidth limits do not apply.
The VCS Expressway TURN server supports TURN media over TCP and UDP. Configuration of the supported
protocols is available only through the CLI command xConfiguration Traversal Server TURN ProtocolMode.
The VCS Expressway TURN server supports UDPrelays over TCP; it does not currently support TCPrelays.
Configuring TURN Services

TURN relay services are only available on the VCS Expressway. To use TURN services you need the TURN Relay
option key (this controls the number of TURN relays that can be simultaneously allocated by the TURNserver).
The TURN page (Configuration > Traversal > TURN) is used to configure the VCS Expressway's TURN settings. If you
are configuring your VCS Expressway for delegated credential checking you can also determine, via the
Authentication realm, the traversal zone through which credential checking of TURN server requests is delegated.
48
TURN Determines whether the VCS offers TURN services to

services traversal clients.
TURN The listening port for TURN requests. The default is To allow endpoints such as Jabber
requests port 3478. Video to discover TURN services, you
need to set up DNS SRV records for _
On Large systems you can configure a range of TURN turn._udp. and _turn._tcp (either for
request listening ports. The default range is 3478 3483. the single port, or range of ports as
appropriate).
If you need to change the Turn

requests port (or range, for Large
systems) while the Turn services are
already On:
1. Change Turn services to

Offand Save
2. Edit the port number/range
3. Change Turn services to
Onand Save
This is because changes to the port

numbers do not come into effect until
the TURN services are restarted.
Delegated Controls whether the credential checking of TURN See delegated credential checking for
credential server requests is delegated, via a traversal zone, to more information.
checking another VCS. The associated Authentication realm
determines which traversal zone is used.
Off: use the relevant credential checking mechanisms

(local database or H.350 directory via LDAP) on the VCS
performing the authentication challenge.
On: delegate the credential checking to a traversal

client.
The default is Off.
Authentication This is the realm sent by the server in its authentication When Delegated credential checking
realm challenges. is Off, ensure that the client's
credentials are stored in the relevant
When Delegated credential checking is Off, this device authentication database.
is a free-form text field.
When Delegated credential checking is On, you
choose from the set of configured SIP domains.
The chosen domain also determines the traversal
zone through which credential checking is
delegated.
Media port The lower and upper port in the range used for the
range start / allocation of TURN relays.
end
The default TURN relay media port range of 24000
29999 applies to new installations of X8.1 or later. The
previous default range of 60000 61799 still applies to
earlier releases that have upgraded to X8.1.
49
TURN server status

A summary of the TURNserver status is displayed at the bottom of the TURN page. When the TURNserver is active,
the summary also displays the number of active TURN clients and the number of active relays.
Click on the active relay links to access the TURN relay usage page, which lists all the currently active TURN relays
on the VCS. You can also review further details of each TURN relay including permissions, channel bindings and
counters.
50
51
Unified Communications
This section describes how to configure the VCS Control and VCS Expressway for Unified Communications
functionality, a core part of the Cisco Collaboration Edge Architecture:
Unified Communications Prerequisites 52

Mobile and Remote Access 57
External XMPP Federation 73
Jabber Guest Services Overview 85
Unified Communications Prerequisites
Configuring a Secure Traversal Zone Connection for Unified Communications

To support Unified Communications features (such as mobile and remote access or Jabber Guest), there must be a
Unified Communications traversal zone connection between the VCS Control and the VCS Expressway. This involves:
Installing suitable security certificates on the VCS Control and the VCS Expressway.
Configuring a Unified Communications traversal zone between the VCS Control and the VCS Expressway
Note: You should configure only one Unified Communications traversal zone per VCS.
Installing VCS Security Certificates

You must set up trust between the VCS Control and the VCS Expressway:
1. Install a suitable server certificate on both the VCS Control and the VCS Expressway.
The certificate must include the Client Authentication extension. The system will not allow you to upload a
server certificate without this extension when Unified Communications features have been enabled.
The VCS includes a built-in mechanism to generate a certificate signing request (CSR) and is the
recommended method for generating a CSR:
Ensure that the CA that signs the request does not strip out the client authentication extension.
The generated CSR includes the client authentication request and any relevant subject alternate names
for the Unified Communications features that have been enabled (see Server Certificate Requirements
for Unified Communications, page 54 if appropriate).
To generate a CSR and /or to upload a server certificate to the VCS, go to Maintenance > Security
certificates > Server certificate. You must restart the VCS for the new server certificate to take effect.
52
2. Install on both VCSs the trusted Certificate Authority (CA) certificates of the authority that signed the VCS's
server certificates.
There are additional trust requirements, depending on the Unified Communications features being deployed.
For mobile and remote access deployments:
The VCS Control must trust the Unified CM and IM&P tomcat certificate.
If appropriate, both the VCS Control and the VCS Expressway must trust the authority that signed the
endpoints' certificates.
For Jabber Guest deployments:
When the Jabber Guest server is installed, it uses a self-signed certificate by default. However, you can
install a certificate that is signed by a trusted certificate authority. You must install on the VCS Control
either the self-signed certificate of the Jabber Guest server, or the trusted CA certificates of the authority
that signed the Jabber Guest server's certificate.
To upload trusted Certificate Authority (CA) certificates to the VCS, go to Maintenance > Security certificates
> Trusted CA certificate. You must restart the VCS for the new trusted CA certificate to take effect.
See Certificate Creation and Use With VCS Deployment Guide for full information about how to create and upload the
VCSs server certificate and how to upload a list of trusted certificate authorities.
Configuring Encrypted VCS Traversal Zones

To support Unified Communications features via a secure traversal zone connection between the VCS Control and
the VCS Expressway:
The VCS Control and VCS Expressway must be configured with a zone of type Unified Communications
traversal. This automatically configures an appropriate traversal zone (a traversal client zone when selected
on a VCS Control, or a traversal server zone when selected on a VCS Expressway) that uses SIP TLS with TLS
verify mode set to On, and Media encryption mode set to Force encrypted.
Both VCSs must trust each other's server certificate. As each VCS acts both as a client and as a server you
must ensure that each VCSs certificate is valid both as a client and as a server.
If an H.323 or a non-encrypted connection is also required, a separate pair of traversal zones must be
configured.
To set up a secure traversal zone, configure your VCS Control and VCS Expressway as follows:
1. Go to Configuration > Zones > Zones.

2. Click New.
53
3. Configure the fields as follows (leave all other fields with default values):
VCS Control VCS Expressway
Name "Traversal zone" for example "Traversal zone" for example
Type Unified Communications Unified Communications traversal

traversal
Connection credentials section
Username "exampleauth" for example "exampleauth" for example
Password "ex4mpl3.c0m" for example Click Add/Edit local authentication database,

then in the popup dialog click New and enter
the Name ("exampleauth") and Password
("ex4mpl3.c0m") and click Create credential.
SIP section
Port 7001 7001
TLS verify subject name Not applicable Enter the name to look for in the traversal
client's certificate (must be in either the
Subject Common Name or the Subject
Alternative Name attributes). If there is a
cluster of traversal clients, specify the cluster
name here and ensure that it is included in
each client's certificate.
Authentication section
Authentication policy Do not check credentials Do not check credentials
Location section
Peer 1 address Enter the FQDN of the VCS Not applicable

Expressway.
Note that if you use an IP

address (not recommended),
that address must be present
in the VCS Expressway server
certificate.
Peer 2...6 address Enter the FQDNs of additional Not applicable

peers if it is a cluster of VCS
Expressways.
4. Click Create zone.
Server Certificate Requirements for Unified Communications
Cisco Unified Communications Manager Certificates

The two Cisco Unified Communications Manager certificates that are significant for Mobile and Remote Access are
the CallManager certificate and the tomcat certificate. These are automatically installed on the Cisco Unified
Communications Manager and by default they are self-signed and have the same common name (CN).
We recommend using CA-signed certificates for best end-to-end security between external endpoints and internal
endpoints. However, if you do use self-signed certificates, the two certificates must have different common names.
This is because the VCS does not allow two self-signed certificates with the same CN. If the CallManager and
54
tomcat self-signed certs have the same CNin the VCS's trusted CAlist, then it can only trust one of them. This means
that either secure HTTPor secure SIP,between VCS Control and Cisco Unified Communications Manager, will fail.
Also, when generating tomcat certificate signing requests for any products within the Cisco Collaboration Systems
Release 10.5.2, you need to be aware of CSCus47235. You need to work around this issue to ensure that the
FQDNsof the nodes are in the certificates as Subject Alternative Names. The VCS X8.5.2 Release Notes have the
details of the workarounds.
VCS Certificates
The VCS certificate signing request (CSR) tool prompts for and incorporates the relevant subject alternate name
(SAN) entries as appropriate for the Unified Communications features that are supported on that VCS.
The following table shows which CSR alternative name elements apply to which Unified Communications features:
Add these items as Subject When generating a CSRfor these purposes
Alternative Names Mobile and Remote Jabber Business to

XMPP Federation
Access Guest Business Calls
Unified CM registrations domains Required on VCS

Expressway only
XMPP federation domains Required on VCS

Expressway only
IM and Presence chat node
aliases Required
(federated group chat)
Unified CM phone security profile Required on VCS

names Control only
Note:
You may need to produce a new server certificate for the VCS Control if chat node aliases are added or
renamed, when IM and Presence nodes are added or renamed, or when new TLS phone security profiles are
added.
You must produce a new VCS Expressway certificate if new chat node aliases are added to the system, or if
the Unified CM or XMPP federation domains are modified.
You must restart the VCS for any new uploaded server certificate to take effect.
More details about the individual feature requirements per VCS Control / VCS Expressway are described below.
VCS Control server certificate requirements
The VCS Control server certificate needs to include the following elements in its list of subject alternate names:
Unified CM phone security profile names: the names of the Phone Security Profiles in Unified CM that are
configured for encrypted TLS and are used for devices requiring remote access. Use the FQDNformat and
separate multiple entries with commas.
Having the secure phone profiles as alternative names means that Unified CM can communicate via TLS with
the VCS Control when it is forwarding messages from devices that use those profiles.
55
IM and Presence chat node aliases (federated group chat): the Chat Node Aliases (e.g.
chatroom1.example.com) that are configured on the IM and Presence servers. These are required only for
Unified Communications XMPP federation deployments that intend to support group chat over TLS with
federated contacts.
The VCS Control automatically includes the chat node aliases in the CSR, providing it has discovered a set of
IM&P servers.
We recommend that you use DNSformat for the chat node aliases when generating the CSR. You must
include the same chat node aliases in the VCS Expressway server certificate's alternative names.
Figure 3 Entering subject alternative names for security profiles and chat node aliases on the VCS
Control's CSRgenerator
VCS Expressway server certificate requirements

The VCS Expressway server certificate needs to include the following elements in its list of subject alternate names:
Unified CM registrations domains: all of the domains which are configured on the VCS Control for Unified
CM registrations. They are required for secure communications between endpoint devices and VCS
Expressway.
Select the DNSformat and manually specify the required FQDNs. Separate the FQDNs by commas if you need
multiple domains. You may select CollabEdgeDNS format instead, which simply adds the prefix collab-edge.
to the domain that you enter. This format is recommended if you do not want to include your top level domain
as a SAN (see example in following screenshot).
XMPP federation domains: the domains used for point-to-point XMPP federation. These are configured on
the IM&P servers and should also be configured on the VCS Control as domains for XMPP federation.
multiple domains. Do not use the XMPPAddress format as it may not be supported by your CA, and may be
discontinued in future versions of the VCS software.
IM and Presence chat node aliases (federated group chat): the same set of Chat Node Aliases as entered
on the VCS Control's certificate. They are only required for voice and presence deployments which will
support group chat over TLS with federated contacts.
Note that you can copy the list of chat node aliases from the equivalent Generate CSR page on the VCS
Control.
56
Figure 4 Entering subject alternative names for Unified CMregistration domains, XMPPfederation
domains, and chat node aliases, on the VCS Expressway's CSRgenerator
See Certificate Creation and Use With VCS Deployment Guide for full information about how to create and upload the
VCSs server certificate and how to upload a list of trusted certificate authorities.
Mobile and Remote Access

This section describes how to configure your VCS to support Unified Communications Mobile and Remote Access
(MRA).
Mobile and Remote Access Overview

Cisco Unified Communications mobile and remote access is a core part of the Cisco CollaborationEdge Architecture.
It allows endpoints such as Cisco Jabber to have their registration, call control, provisioning, messaging and
presence services provided by Cisco Unified Communications Manager (Unified CM) when the endpoint is not within
the enterprise network. The VCS provides secure firewall traversal and line-side support for Unified CM registrations.
The overall solution provides:
Off-premises access: a consistent experience outside the network for Jabber and EX/MX/SX Series clients
Security: secure business-to-business communications
Cloud services: enterprise grade flexibility and scalable solutions providing rich WebEx integration and
Service Provider offerings
Gateway and interoperability services: media and signaling normalization, and support for non-standard
endpoints
Figure 5 Unified Communications: mobile and remote access
57
Note that third-party SIP or H.323 devices can register to the VCS Control and, if necessary, interoperate with Unified
CM-registered devices over a SIP trunk.
Figure 6 Typical call flow: signaling and media paths
Unified CM provides call control for both mobile and on-premises endpoints.
Signaling traverses the Expressway solution between the mobile endpoint and Unified CM.
Media traverses the Expressway solution and is relayed between endpoints directly; all media is encrypted
between the VCS Control and the mobile endpoint.
Deployment Scope
The following major VCS-based deployments are mutually exclusive. They cannot be implemented together on the
same VCS (or traversal pair):
Mobile and Remote Access

Microsoft Lync Interoperability
Jabber Guest
Jabber Client Connectivity Without VPN

The mobile and remote access solution supports a hybrid on-premises and cloud-based service model, providing a
consistent experience inside and outside the enterprise. It provides a secure connection for Jabber application traffic
without having to connect to the corporate network over a VPN. It is a device and operating system agnostic solution
for Cisco Jabber clients on Windows, Mac, iOS and Android platforms.
It allows Jabber clients that are outside the enterprise to:
use instant messaging and presence services

make voice and video calls
search the corporate directory
share content
launch a web conference
access visual voicemail
Note that Jabber Web and Cisco Jabber Video for TelePresence (Jabber Video) are not supported.
58
Configuring Mobile and Remote Access on VCS

This section describes the steps required to enable and configure mobile and remote access features on VCS Control
and VCS Expressway, and how to discover the Unified CM servers and IM&P servers used by the service.
Installing VCS Security Certificates and Setting Up a Secure Traversal Zone

To support Unified Communications features (such as mobile and remote access or Jabber Guest), there must be a
Unified Communications traversal zone connection between the VCS Control and the VCS Expressway. This involves:
Installing suitable security certificates on the VCS Control and the VCS Expressway.
Configuring a Unified Communications traversal zone between the VCS Control and the VCS Expressway
For information about how to do this, see:
Configuring a Secure Traversal Zone Connection for Unified Communications, page 52 (if your system does
not already have a secure traversal zone in place)
Server Certificate Requirements for Unified Communications, page 54
Note that if XMPP federation is to be used, the IM&P servers need to be discovered on the VCS Control for all the
relevant information to be available when generating certificate signing requests.
Setting Up the VCS Control

This section describes the configuration steps required on the VCS Control.
Configuring DNS and NTP Settings
Check and configure the basic system settings on VCS:
1. Ensure that System host name and Domain name are specified (System > DNS).
2. Ensure that local DNS servers are specified (System > DNS).
3. Ensure that all VCS systems are synchronized to a reliable NTP service (System > Time). Use an
Authentication method in accordance with your local policy.
If you have a cluster of VCSs you must do this for every peer.
Enabling the VCS Control for Mobile and Remote Access
To enable mobile and remote access functionality:
1. Go to Configuration > Unified Communications >Configuration.

2. Set Unified Communications mode to Mobile and remote access.
3. Click Save.
Note that you must select Mobile and remote access before you can configure the relevant domains and traversal
zones.
Configuring the domains to route to Unified CM
You must configure the domains for which registration, call control, provisioning, messaging and presence services
are to be routed to Unified CM.
1. On VCS Control, go to Configuration > Domains.

2. Select the domains (or create a new domain, if not already configured) for which services are to be routed to
Unified CM.
59
3. For each domain, turn On the services for that domain that VCS is to support. The available services are:
SIP registrations and provisioning on VCS: the VCS is authoritative for this SIP domain. The VCS acts as a
SIP registrar and Presence Server for the domain, and accepts registration requests for any SIP endpoints
attempting to register with an alias that includes this domain. The default is On.
SIP registrations and provisioning on Unified CM: Endpoint registration, call control and provisioning for
this SIP domain is serviced by Unified CM. The VCS acts as a Unified Communications gateway to provide
secure firewall traversal and line-side support for Unified CM registrations. The default is Off.
IM and Presence Service: Instant messaging and presence services for this SIP domain are provided by the
Unified CM IM and Presence service. The default is Off.
XMPPfederation: Enables XMPPfederation between this domain and partner domains. The default is Off.
Deployment: Associates the domain with the selected deployment, if there are multiple deployments. This
setting is absent if there is only one deployment (there is always at least one).
Turn On all of the applicable services for each domain. For example, the same domain may be used by
endpoints such as Jabber or EXSeries devices that require line-side Unified Communications support, and by
other endpoints such as third-party SIP or H.323 devices that require VCS support. (In this scenario, the
signaling messages sent from the endpoint indicate whether line-side unified communications or VCS support
is required.)
Discovering Unified Communications Servers and Services

The VCS Control must be configured with the address details of the Unified Communications services/nodes that are
going to provide registration, call control, provisioning, voicemail, messaging, and presence services to MRAusers.
IMand Presence Service configuration is not required if you're deploying the hybrid model, as these services are
provided by the WebEx cloud.
Note: The connections configured in this procedure are static. You must refresh the configuration on the VCS Control
after you reconfigure or upgrade any of the discovered Unified Communications nodes. For more details, see Why
Should IRefresh the Discovered Nodes?, page 63
Go to Configuration >Unified Communications ><UCserver type> and click Refresh servers.
Trusting the Certificates Presented to the VCS Control
If TLSverify mode is On when discovering UnifiedCommunications services, then you must configure the VCS
Control to trust the certificates presented by the IMand Presence Service nodes and Unified CM servers.
1. Determine the relevant CA certificates to upload:

If the servers' tomcat and CallManager certificates are CA-signed, the VCS Control's trusted CA list must
include the root CA of the certificate issuer.
If the servers are using self-signed certificates, the VCS Control's trusted CA list must include the self-
signed certificates from all discovered IMand Presence Service nodes, Cisco Unity Connection servers,
and Unified CM servers.
2. Upload the required certificates to the VCS Control (Maintenance > Security certificates > Trusted CA
certificate).
3. Restart the VCS Control (Maintenance > Restart options).
Discovering IMand Presence Service Nodes
1. On VCS Control, go to Configuration > Unified Communications >IMand Presence Service nodes.
The page lists any IMand Presence Service nodes that have already been discovered.
60
2. Add the details of an IMand Presence Service database publisher node:

a. Click New.
b. Enter the address of the IMand Presence Service database publisher node.
You can enter an FQDN or an IP address, but we recommend using the FQDN when TLS verify mode is
On.
c. Enter the Username and Password of an account that can access this server.
Note: These credentials are stored permanently in the VCS database. The corresponding IMand Presence
Service user must have the Standard AXL API Access role.
d. [Recommended] Leave TLSverify mode switched On to ensure VCS verifies the node's tomcat certificate
(for XMPP-related communications).
e. [Optional] Select which deployment this node/cluster will belong to.
The Deployment field does not show if you have not created multiple deployments. All nodes belong to the
default deployment if you choose not to use multiple deployments.
f. Click Add address.
If you enabled TLSverify mode, then the VCS tests whether a secure connection can be established. It
does this so you can find any TLS configuration errors before it continues the discovery process.
If the secure connection test was successful, or if you did not enable TLSverify mode, then the system
attempts to contact the publisher and retrieve details of its associated nodes.
Note: The status of the discovered node will be Inactive unless a valid traversal zone connection exists
between the VCS Control and the VCS Expressway (may not yet be configured).
3. Repeat the discovery procedure for other IMand Presence Service nodes/clusters, if required.
4. Click Refresh servers to refresh all the node details after configuring multiple publisher addresses.
Discovering Unified CM Servers
1. On VCS Control, go to Configuration > Unified Communications >Unified CMservers.

The page lists any Unified CM nodes that have already been discovered.
61
2. Add the details of a Unified CM publisher node:

a. Click New.
b. Enter the Unified CM publisher address.
On.
Note: These credentials are stored permanently in the VCS database. The corresponding Unified CM user
must have the Standard AXL API Access role.
d. [Recommended] Leave TLSverify mode switched On to ensure VCS verifies the node's certificates.
The Unified CM node presents its tomcat certificate for AXL and UDS queries, and its CallManager
certificate for subsequent SIP traffic. If the Unified CM server is using self-signed certificates, the VCS
Control's trusted CA list must include a copy of the tomcat certificate and the CallManager certificate from
every Unified CM server.
3. Repeat the discovery procedure for other Unified CM nodes/clusters, if required.
Discovering Cisco Unity Connection Servers
1. On VCS Control, go to Configuration > Unified Communications >UnityConnection servers.

The page lists any Cisco Unity Connection nodes that have already been discovered.
2. Add the details of a Cisco Unity Connection publisher node:
a. Click New.
b. Enter the Unity Connection address.
On.
Note: These credentials are stored permanently in the VCS database.
d. [Recommended] Leave TLSverify mode switched On to ensure VCS verifies the node's tomcat
certificate.
62
3. Repeat the discovery procedure for other Cisco Unity Connection nodes/clusters, if required.
Automatically Generated Zones and Search Rules
VCS Control automatically generates non-configurable neighbor zones between itself and each discovered Unified
CM node. A TCP zone is always created, and a TLS zone is created also if the Unified CM node is configured with a
Cluster Security Mode (System > Enterprise Parameters > Security Parameters) of 1 (Mixed) (so that it can support
devices provisioned with secure profiles). The TLS zone is configured with its TLS verify mode set to On if the Unified
CM discovery had TLS verify mode enabled. This means that the VCS Control will verify the CallManager certificate
for subsequent SIP communications. Each zone is created with a name in the format 'CEtcp-<node name>' or 'CEtls-
<node name>'.
A non-configurable search rule, following the same naming convention, is also created automatically for each zone.
The rules are created with a priority of 45. If the Unified CM node that is targeted by the search rule has a long name,
the search rule will use a regex for its address pattern match.
Note that load balancing is managed by Unified CM when it passes routing information back to the registering
endpoints.
Why Should IRefresh the Discovered Nodes?
When the VCS Control "discovers" a Unified Communications node, it establishes a connection to read the
information required to create zones and search rules to proxy requests originating from outside of the network in
towards that node.
This configuration information is static. That is, the VCS only reads it when you manually initiate discovery of a new
node, or when you refresh the configuration of previously discovered nodes. If any related configuration has changed
on a node after you discover it, the mismatch between the new configuration and what the VCS Control knows of that
node will probably cause some kind of failure.
The information that the VCS Control reads from the Unified Communications node is different for each node type and
its role. The following list contains examples of UCconfiguration that you can expect to require a refresh from the
VCS. The list is not exhaustive; if you suspect that a configuration change on a node is affecting MRAservices, you
should refresh those nodes to eliminate one known source of potential problems.
Changing cluster (e.g. adding or removing a node)

Changing security parameters (e.g. Enabling Mixed Mode)
Changing connection sockets (e.g. SIP port configuration)
Changing TFTP server configuration
Upgrading the software on the node
Configuring the HTTP Server Allow List (Whitelist) on VCS Control

Jabber client endpoints may need to access additional web services inside the enterprise. This requires an "allow
list" of servers to be configured to which the VCS will grant access for HTTP traffic originating from outside the
enterprise.
The features and services that may be required, and would need whitelisting, include:
Visual Voicemail
Jabber Update Server
Custom HTML tabs / icons
Directory Photo Host
Advanced File Transfer (AFT)
Problem Report Tool server
63
Note: In order for the AFT feature to work across VCS you must ensure that all Unified CM IM and Presence Service
nodes, across all Unified CM IM and Presence Service clusters, have been added to the whitelist either manually or
automatically.
To configure the set of addresses to which HTTP access will be allowed:
1. On VCS Control, go to Configuration > Unified Communications > Configuration.

2. Click HTTP server allow list.
3. Configure the hostnames or IP addresses of any HTTP servers that external Jabber clients are allowed to
access.
Access is granted if the server portion of the client-supplied URI matches one of the names entered here, or if
it resolves via DNS lookup to a specified IP address.
VCS Control automatically whitelists the IP addresses of all discovered Unified CM nodes (that are running the
CallManager and TFTP service), IMand Presence Service nodes, and Cisco Unity Connection nodes. These entries
cannot be deleted. They are displayed in the Auto-configured allow list section of the HTTP server allow list page.
Setting Up the VCS Expressway

This section describes the configuration steps required on the VCS Expressway.
Configuring DNS and NTP Settings
Check and configure the basic system settings on VCS:
1. Ensure that System host name and Domain name are specified (System > DNS).
2. Ensure that public DNS servers are specified (System > DNS).
3. Ensure that all VCS systems are synchronized to a reliable NTP service (System > Time). Use an
Authentication method in accordance with your local policy.
If you have a cluster of VCSs you must do this for every peer.
Note:The combination of <System host name>.<Domain name> is the FQDN of this VCS Expressway. Ensure that
this FQDN is resolvable in public DNS.
If you have a cluster of VCS Expressways, you must ensure that the Domain name is identical on each peer, and it is
case-sensitive.
Enabling the VCS Expressway for Mobile and Remote Access
To enable mobile and remote access functionality:
1. Go to Configuration > Unified Communications >Configuration.

2. Set Unified Communications mode to Mobile and remote access.
3. Click Save.
Ensuring That TURN Services Are Disabled on VCS Expressway
You must ensure that TURN services are disabled on the VCS Expressway used for mobile and remote access.
1. Go to Configuration > Traversal > TURN.

2. Ensure that TURN services are Off.
64
Using Deployments to Partition Unified Communications Services

Adeployment is an abstract boundary used to enclose a domain and one or more Unified Communications service
providers, such as Unified CM, Cisco Unity Connection, and IMand Presence Service nodes.
The purpose of multiple deployments is to partition the Unified Communications services available to mobile and
remote access (MRA) users. This enables different subsets of MRAusers to access different sets of services over the
same VCS pair. We recommend that you do not exceed 10 deployments.
For example, consider an implementation of two sets of Unified Communications infrastructure to provide a live
MRAenvironment and a staging environment, respectively. This implementation might also require an isolated
environment for sensitive communications.
Figure 7 Multiple deployments to partition Unified Communications services accessed from outside the
network
Deployments and their associated domains and services are configured on the VCS Control.
There is one primary deployment, called "Default deployment" unless you rename it, that automatically encloses all
domains and services until you create and populate additional deployments. This primary deployment cannot be
deleted, even if it is renamed or has no members.
To partition the services that you provide via mobile and remote access, create as many deployments as you need,
associate a different domain with each, and then associate the required Unified Communications resources with
each deployment.
You cannot associate one domain with more than one deployment. Similarly, each Unified Communications node may
only be associated with one deployment.
To create a new deployment:
1. Log in to the VCS Control.

2. Go to Configuration >Unified Communications > Deployments and click New.
3. Give the deployment a name and click Create deployment.
The new deployment is listed on the Deployments page and is available to select when editing domains or
UCservices.
65
To associate a domain with a deployment:
1. Go to Configuration >Domains.
The domains and their associated services are listed here. The deployment column shows where the listed
domains are associated.
2. Click the domain name, or create a new domain (see Configuring Domains, page 97).
3. In the Deployment field, select the deployment which will enclose this domain.
4. Click Save.
To associate a Unified CM or other server/service with the deployment:
1. Go to Configuration >Unified Communications > and then Unified CMservers, or IMand Presence Service
nodes, or Unity Connection servers.
Any previously discovered service nodes of the selected type are listed here. The deployment column shows
where the listed nodes are associated.
If the list is not properly populated, see Discovering Unified Communications Servers and Services, page 60.
2. Click the server / service node name.
3. In the Deployment field, select which deployment will enclose this server / service node.
4. Click Save.
Note: When you save this change, the VCS Control refreshes the connection to the node, which may
temporarily disrupt the service to the connected users.
5. Repeat for any other Unified Communications services that will belong to the deployment.
Single Sign-On (SSO) over the Collaboration Edge

Use this feature to enable single sign-on for endpoints accessing Unified Communications services from outside the
network. Single sign-on over the edge relies on the secure traversal capabilities of the VCS pair at the edge, and trust
relationships between the internal service providers and the externally resolvable identity provider (IdP).
The endpoints do not need to connect via VPN; they use one identity and one authentication mechanism to access
multiple Unified Communications services. Authentication is owned by the IdP, and there is no authentication at the
VCS, nor at the internal Unified CM services.
Supported endpoints

Supported Unified Communications services

Cisco Unity Connection 10.5(2) or later
Cisco Unified Communications Manager IMand Presence Service 10.5(2) or later
Other internal web servers, for example intranet
How it works
Cisco Jabber determines whether it is inside the organization's network before it requests a Unified Communications
service. If it is outside the network, then it requests the service from the VCS Expressway on the edge of the network.
If single sign-on is enabled at the edge, the VCS Expressway redirects Jabber to the IdP with a signed request to
authenticate the user.
The IdP challenges the client to identify itself. When this identity is authenticated, the IdPredirects Jabber's service
request back to the VCS Expressway with a signed assertion that the identity is authentic.
66
The VCS Expressway trusts the IdP, so it passes the request to the appropriate service inside the network. The Unified
Communications service trusts the IdPand the VCS Expressway, so it provides the service to the Jabber client.
Figure 8 Single sign-on for on-premises UCservices
Single Sign-On Prerequisites

On the VCS pair:
AVCS Expressway and a VCS Control are configured to work together at your network edge.
AUnified Communications traversal zone is configured between the VCS Control and the VCS Expressway.
The SIPdomain that will be accessed via SSOis configured on the VCS Control.
The VCS Control is in Mobile and remote access mode and has discovered the required Unified CM resources.
The hostnames of the required Unified CM resources are added to the HTTP server allow list on the VCS
Control.
If you are using multiple deployments, the Unified CM resources that will be accessed by SSOare in the same
deployment as the domain that will be called from Jabber clients.
On the Cisco Jabber clients:
Clients are configured to request the internal services using the correct domain names / SIPURIs / Chat
aliases.
The default browser can resolve the VCS Expressway and the IdP.
On the Identity Provider:
The domain that is on the IdPcertificate must be published in the DNSso that clients can resolve the IdP.
Selecting an Identity Provider (IdP)
Cisco Collaboration solutions use SAML 2.0 (Security Assertion Markup Language) to enable SSO (single sign-on) for
clients consuming Unified Communications services.
SAML-based SSO is an option for authenticating UC service requests originating from inside the enterprise network,
and it is now extended to clients requesting UC services from outside via Mobile and Remote Access (MRA).
If you choose SAML-based SSO for your environment, note the following:
67
SAML 2.0 is not compatible with SAML 1.1 and you must select an IdP that uses the SAML 2.0 standard.
SAML-based identity management is implemented in different ways by vendors in the computing and
networking industry, and there are no widely accepted regulations for compliance to the SAML standards.
The configuration of and policies governing your selected IdP are outside the scope of Cisco TAC (Technical
Assistance Center) support. Please use your relationship and support contract with your IdP Vendor to assist
in configuring the IDP properly. Cisco cannot accept responsibility for any errors, limitations, or specific
configuration of the IdP.
Although Cisco Collaboration infrastructure may prove to be compatible with other IdPs claiming SAML 2.0
compliance, only the following IdPs have been tested with Cisco Collaboration solutions:
OpenAM 10.0.1
Active Directory Federation Services 2.0 (AD FS 2.0)
PingFederate 6.10.0.4
High Level Task List
1. Configure a synchronizable relationship between the identity provider and your on-premises directory such
that authentication can securely be owned by the IdP. See Directory Integration and Identity Management in
the Cisco Collaboration System 10.x Solution Reference Network Designs (SRND) document.
2. Export SAMLmetadata file from the IdP. Check the documentation on your identity provider for the procedure.
For example, see Enable SAML SSO through the OpenAM IdP in the SAML SSO Deployment Guide for Cisco
Unified Communications Applications.
3. Import the SAMLmetadata file from the IdPto the Unified CM servers and Cisco Unity Connection servers that
will be accessed by single sign-on. See the Unified Communications documentation or help for more details.
4. Export the SAMLmetadata files from the Unified CM servers and Cisco Unity Connection servers. For example,
see High-Level Circle of Trust Setup in the SAML SSO Deployment Guide for Cisco Unified Communications
Applications.
5. Create the Identity Provider on the VCS Control, by importing the SAMLmetadata file from the IdP.
6. Associate the IdP with SIPdomain(s) on the VCS Control.
7. Export the SAMLmetadata file(s) from the (master) VCS Control; ensure that it includes the externally
resolvable address of the (master) VCS Expressway.
The SAMLmetadata file from the VCS Control contains the X.509 certificate for signing and encrypting SAML
interchanges between the edge and the IdP, and the binding(s) that the IdP needs to redirect clients to the
VCS Expressway (peers).
8. Import the SAMLmetadata files from the Unified CM servers and Cisco Unity Connection servers to the IdP. An
example using OpenAMis in the SAML SSO Deployment Guide for Cisco Unified Communications
Applications.
9. Similarly, import the SAMLmetadata file from the VCS Control to the IdP. See your IdP documentation for
details.
10. Turn on SSOat the edge (on the VCS Control and the VCS Expressway).
Importing the SAMLMetadata from the IdP
1. On the VCS Control, go to Configuration >Unified Communications >Identity providers (IdP).

You only need to do this on the master peer of the cluster.
2. Click Import new IdP from SAML.
3. Use the Import SAMLfile control to locate the SAMLmetadata file from the IdP.
68
4. Set the Digest to the required SHA hash algorithm.

The VCS uses this digest for signing SAML authentication requests for clients to present to the IdP. The
signing algorithm must match the one expected by the IdP for verifying SAML authentication request
signatures.
5. Click Upload.
The VCS Control can now authenticate the IdP's communications and encrypt SAMLcommunications to the
IdP.
Note: You can change the signing algorithm after you have imported the metadata, by going to Configuration
>Unified Communications >Identity Providers (IdP), locating your IdProw then, in the Actions column,
clicking Configure Digest).
Associating Domains with an IdP

You need to associate a domain with an IdPif you want the MRAusers of that domain to authenticate via the IdP. The
IdPadds no value until you associate at least one domain with it.
There is a many-to-one relationship between domains and IdPs. A single IdPcan be used for multiple domains, but
you may associate just one IdP with each domain.
On the VCS Control:
1. Open the IdP list (Configuration >Unified Communications > Identity providers (IdP)) and verify that your IdP
is in the list.
The IdPs are listed by their entity IDs. The associated domains for each are shown next to the ID.
2. Click Associate domains in the row for your IdP.
This shows a list of all the domains on this VCS Control. There are checkmarks next to domains that are
already associated with this IdP. It also shows the IdP entity IDs if there are different IdPs associated with
other domains in the list.
3. Check the boxes next to the domains you want to associate with this IdP.
If you see (Transfer) next to the checkbox, checking it will break the domain's existing association and
associate it with this IdP.
4. Click Save.
The selected domains are associated with this IdP.
Exporting the SAMLMetadata from the VCS Control
Note:The VCS Control must have a valid connection to the VCS Expressway before you can export the VCS Control's
SAMLmetadata.
1. Go to Configuration >Unified Communications >Export SAML data.

This page lists the connected VCS Expressway, or all the VCS Expressway peers if it's a cluster. These are
listed because data about them is included in the SAML metadata for the VCS Control.
2. [Conditional] If you have configured multiple deployments, you must select a deployment before you can
export the SAMLmetadata.
3. Click Download or Download all.
The page also lists all the VCS Control peers, and you can download SAMLmetadata for each one, or export
them all in a .zip file.
4. Copy the resulting file(s) to a secure location that you can access when you need to import SAMLmetadata to
the IdP.
69
Configuring IDPs
This topic covers any known additional configurations that are required when using a particular IDPfor SSOover
MRA.
These configuration procedures are required in addition to the prerequisites and high level tasks already mentioned,
some of which are outside of the document's scope.
Active Directory Federation Services 2.0
After creating Relying Party Trusts for the VCS Expressways, you must set some properties of each entity, to ensure
that AD FS formulates the SAMLresponses as VCS Expressway expects them.
You also need to add a claim rule, for each relying party trust, that sets the uid attribute of the SAMLresponse to the
ADattribute value that users are authenticating with.
These procedures were verified on AD FS2.0, although the same configuration is required if you are using AD FS3.0.
You need to:
Sign the whole response (message and assertion)

Add a claim rule to send identity as uid attribute
To sign the whole response:
In Windows PowerShell, repeat the following command for each VCS Expressway's <EntityName>:
Set-ADFSRelyingPartyTrust -TargetName "<EntityName>" -SAMLResponseSignature MessageAndAssertion
To add a claim rule for each Relying Party Trust:
1. Open the Edit Claims Rule dialog, and create a new claim rule that sends ADattributes as claims
2. Select the ADattribute to match the one that identify the SSOusers to the internal systems, typically email or
SAMAccountName
3. Enter uid as the Outgoing Claim Type
Enabling Single Sign-On at the Edge

On the VCS Control:
1. Go to Configuration >Unified Communications >Configuration

2. Locate Single Sign-on support and select On
3. Click Save
[Optional] Extend the time-to-live of SIPauthorization tokens, by entering a number of seconds for SIP token extra
time-to-live (in seconds). This setting gives users a short window in which they can still accept calls after their
credentials expire, but you should balance this convenience against the increased security exposure.
On the VCS Expressway:
1. Go to Configuration >Unified Communications >Configuration

2. Locate Single Sign-on support and select On
3. Click Save
[Optional] Choose how the VCS Expressway reacts to /get_edge_sso requests by selecting whether or not the VCS
Control should check the home nodes.
The /get_edge_sso request from the client asks whether the client may try to authenticate the user by SSO. In this
request, the client provides an identity of the user that the VCS Control can use to find the user's home cluster:
70
The default option is Yes to Check for internal SSOavailability:

The VCS Expressway passes the request to the VCS Control. The VCS Control uses a round-robin algorithm to
select a Unified CM node, and makes a UDSquery for the supplied identity against that node. The Unified CM
determines which node is the user's home node, and whether it is capable of doing SSOfor the user, and then
tells the VCS Control the outcome. The VCS Control then tells the VCS Expressway which responds true or
false to the client.
If you select No to Check for internal SSOavailability:
The VCS Expressway always responds true to /get_edge_sso requests. It does not make the inwards request to
the user's home Unified CM, and thus cannot know whether SSOis really available there.
When the client receives a true response from VCS Expressway, it will try to /get_edge_config via SSO. If it gets
false, it will try /get_edge_config using whatever credentials it has - credentials which are independent from the
identity managed by UDSinside the enterprise. If it gets true and SSOis not actually enabled on the user's home
node, then /get_edge_config will fail and the client will not try the other authentication option.
The option you should choose depends entirely on your implementation. If you have a homogenous environment, in
which all Unified CM nodes are capable of SSO, you can reduce response time and overall network traffic by
selecting No. By contrast, if you want clients to use either mode of getting the edge configuration - during rollout or
because you cannot guarantee that SSOis available on all nodes - you should select Yes.
Checking the Status of Unified Communications Services

You can check the status of the Unified Communications services on both VCS Control and VCS Expressway.
1. Go to Status > Unified Communications.

2. Review the list and status of domains, zones and (VCS Control only) Unified CM and IM&P servers.
Any configuration errors will be listed along with links to the relevant configuration page from where you can
address the issue.
Mobile and Remote Access Port Reference

This section summarizes the ports that could potentially be used between your internal network (where the VCS
Control is located) and the DMZ (where the VCS Expressway is located) and between the DMZ and the public
internet.
Outbound from VCS Control (private) to VCS Expressway (DMZ)
Purpose Protocol VCS Control (source) VCS Expressway (listening)
XMPP (IM and Presence) TCP Ephemeral port 7400
SSH (HTTP/S tunnels) TCP Ephemeral port 2222
Traversal zone SIP signaling TLS 25000 to 29999 7001
Traversal zone SIP media UDP 36000 to 59999* 36000 (RTP), 36001
(RTCP) (defaults)
(for small/medium systems on X8.1 or
later) 2776 (RTP), 2777 (RTCP)
(old defaults*)
Traversal zone SIPmedia UDP 36000 to 59999* 36000 to 36011 (6 pairs of

RTPand RTCPports for
(for large systems) multiplexed media
traversal)
71
Outbound from VCS Expressway (DMZ) to public internet
Purpose Protocol VCS Expressway (source) Internet endpoint

(listening)
SIP media UDP 36002 to 59999 or >= 1024
36012 to 59999
SIP signaling TLS 25000 to 29999 >= 1024
Inbound from public internet to VCS Expressway (DMZ)
Purpose Protocol Internet endpoint (source) VCS Expressway (listening)
XMPP (IM and Presence) TCP >= 1024 5222
HTTP proxy (UDS) TCP >= 1024 8443
Media UDP >= 1024 36002 to 59999 or
36012 to 59999*

SIP signaling TLS >= 1024 5061
HTTPS (only required for external TCP >= 1024 443

administrative access, which is
strongly discouraged)
From VCS Control to Internal Infrastructure and Endpoints
Purpose Protocol VCS Control (source) Internal Device Port/Range
XMPP (IM and Presence) TCP Ephemeral port 7400 (IM and Presence)
HTTP proxy (UDS) TCP Ephemeral port 8443 (Unified CM)
HTTP proxy (SOAP) TCP Ephemeral port 8443 (IMand Presence

Service)
HTTP (configuration file retrieval) TCP Ephemeral port 6970 (Unified CM)
CUC (voicemail) TCP Ephemeral port 443 (Unity Connection)
Message Waiting Indicator (MWI) from TCP Ephemeral port 7080 (Unity Connection)
Unity Connection
Media UDP 36000 to 59999* >= 1024 (Media recipient

eg. endpoint)
SIPsignaling TCP 25000 to 29999 5060 (Unified CM)
Secure SIP signaling TLS 25000 to 29999 5061 (Unified CM)
72
Note that:
Ports 8191/8192 TCP and 8883/8884 TCP are used internally within the VCS Control and the VCS Expressway
applications. Therefore these ports must not be allocated for any other purpose. The VCS Expressway listens
externally on port 8883; therefore we recommend that you create custom firewall rules on the external LAN
interface to drop TCP traffic on that port.
The VCS Expressway listens on port 2222 for SSH tunnel traffic. The only legitimate sender of such traffic is
the VCS Control (cluster). Therefore we recommend that you create the following firewall rules for the SSH
tunnels service:
one or more rules to allow all of the VCS Control peer addresses (via the internal LAN interface, if
appropriate)
followed by a lower priority (higher number) rule that drops all traffic for the SSH tunnels service (on the
internal LAN interface if appropriate, and if so, another rule to drop all traffic on the external interface)
External XMPP Federation

This section describes how to configure your VCS to support external XMPP federation.
Deploying VCS for External XMPP Federation

External XMPP federation enables users registered to Unified CM IM & Presence to communicate via the VCS
Expressway with users from a different XMPP deployment.
The following diagram shows how XMPP messages are routed from your on-premises IM&Presence server via the
VCS Control and VCS Expressway CollaborationEdge solution to the federated XMPP server. It also shows the ports
and connections that are used as the messages traverse DMZ firewalls.
Supported Systems
VCS Expressway supports XMPP federation with:

Cisco Unified Communications Manager IMand Presence Service 9.1.1 or later
Cisco Webex Connect Release 6.x
other XMPP standards-compliant servers
73
VCS Expressway does not support XMPP address translation (of email addresses, for example). External
systems must federate with the Jabber IDs that are native to Unified CM IM & Presence.
You can make the user's Unified CM IM&PJabber ID resemble the user's email address, so that the federated
partner can use email addresses for federation, by:
setting the Unified CMLDAPattribute for User ID to be the user's sAMAccountName

setting the Unified CM IM&Ppresence domain to be the same as the email domain
Simultaneous internal federation managed by Unified CM IM&P and external federation managed by VCS is
not supported. If only internal federation is required then you must use Interdomain Federation on Unified CM
IM&P. The available federation deployment configuration options are:
External federation only (managed by VCS)
Internal federation only (managed by Unified CM IM&P)
Internal and external federation managed by Unified CM IM&P, but requires configuring your firewall to
allow inbound connections
For more information see Interdomain Federation for IM and Presence Service on Cisco Unified
Communications Manager.
For information about configuring your system for external XMPP federation, see:
Configuring VCS for External XMPP Federation, page 74

DNS SRV Records for XMPP Federation, page 80
Port Usage for XMPPFederation, page 81
Checking XMPP Federation Status, page 81
Troubleshooting External XMPP Federation, page 82
Configuring VCS for External XMPP Federation

This section takes you through the steps required to configure your VCS for external XMPP federation.
Prerequisites
Ensure that you are running the following software versions:
VCS X8.2 or later

Unified CM IM & Presence 9.1.1 or later
Note that XMPPfederation can only be supported on a single VCS cluster.
Before configuring your VCS system for external XMPPfederation:
Ensure that Interdomain XMPPFederation has been disabled on Unified CM IM and Presence:
Go to Cisco Unified CM IM and Presence Administration > Presence > Inter Domain Federation > XMPP
Federation > Settings and ensure that XMPP Federation Node Status is set to Off.
You must disable Interdomain Federation on Unified CM IM&P before enabling XMPP federation on VCS.
74
A VCS Control (cluster) and VCS Expressway (cluster) have been configured for Mobile and Remote Access to
Unified Communications services, as described in Mobile and Remote Access via Cisco VCS Deployment
Guide. If only XMPP federation is required (video calls and remote registration to Unified CM are not required),
the following items do not have to be configured:
domains that support SIP registrations and provisioning on Unified CM or that support IM and Presence
services on Unified CM
Unified CM servers (you must still configure the IM&P servers)
HTTP server allow list
Note that federated communications are available to both on-premises clients (connected directly to Unified
CM IM&P) and off-premises clients (connected to Unified CM IM&P via mobile and remote access).
If you intend to use both TLS and group chat, the VCS Control and VCS Expressway server certificates must
include in their list of subject alternate names (using either XMPPAddress or DNS formats) the Chat Node
Aliases that are configured on the IM&P servers. Note that the VCS Control automatically includes the chat
node aliases in its certificate signing requests (CSRs), providing it has discovered a set of IM&P servers. When
generating CSRs for the VCS Expressway we recommend that you copy-paste the chat node aliases from the
equivalent Generate CSR page on the VCS Control.
See Server Certificate Requirements for Unified Communications, page 54 for more information.
Configuring Local Domains for XMPP Federation on VCS Control

You must configure your local domain names for which you want to provide XMPP federated services.
1. On VCS Control, go to Configuration > Domains.

2. Click New (or click View/Edit if the required domain already exists).
3. Enter your local Domain name to be federated.
4. Set XMPP federation to On.
5. Click Save.
6. Repeat for any other local domains requiring federation.
Configuring VCS Expressway for XMPP Federation

We recommend that XMPP federation configuration changes are made 'out of hours'. Enabling XMPP federation will
restart the XCP router on all VCS Expressway systems within the cluster. This will temporarily interrupt any existing
mobile and remote access IM&P client sessions. Depending on the number of clients, full client reconnection may
take several minutes. (See Impact of Configuration Changes on a Live System, page 83 for more information.)
1. On VCS Expressway, go to Configuration > Unified Communications.

2. Set XMPP federation support to On.
When you apply this change, you may need to restart the XCPRouters on the IM&Pserver(s). The other
75
settings on this page will not require a restart.
76
3. Configure the remaining fields as follows:
Use static Indicates whether a controlled list of static routes are used to locate the federated XMPP
routes domains and chat node aliases, rather than DNS lookups. See Configuring How XMPP Servers
for Federated Domains and Chat Node Aliases Are Located, page 78 below.
Dialback Enter the dialback secret to use for identity verification with federated XMPP servers. If you
secret have multiple VCS Expressway systems in the same deployment, they must all be configured
with the same dialback secret.
For more information about server dialback, see http://xmpp.org/extensions/xep-0220.html.
Security Indicates if a TLS connection to federated XMPP servers is required, preferred or not required.
mode
TLS required: the system guarantees a secure (encrypted) connection with the foreign
domain.
TLS optional: the system attempts to establish a TLS connection with the foreign domain. If it
fails to establish a TLS connection, it reverts to TCP.
No TLS: the system will not establish a TLS connection with the foreign domain. It uses a non-
encrypted connection to federate with the foreign domain.
In all cases, server dialback is used to verify the identity of the foreign server. The foreign
server must be configured to use server dialback. Note that SASL External is not a supported
configuration on the local server. Foreign servers may be configured to use SASL, but SASL
exchanges will not be supported by the local server.
The default, and recommended setting, is TLS required.
Require Controls whether the certificate presented by the external client is verified against the VCS's
client-side current trusted CA list and, if loaded, the revocation list.
security
certificates This setting does not apply if Security mode is No TLS.
Note that the federated domain name and any chat node aliases must be present in the
certificate's subject alternate name, regardless of this setting.
Privacy Controls whether restrictions are applied to the set of federated domains and chat node
mode aliases.
Off: No restrictions are applied.
Allow list: Federation is allowed only with the domains and chat node aliases specified in the
allow list.
Deny list: Federation is allowed with any domain or chat node alias except for those specified
in the deny list.
Note that any domains or chat node aliases that are configured as static routes are included
automatically in the allow list.
The default is Allow list.
See Configuring the Allow and Deny Lists for Federated Domains and Chat Node Aliases,
page 79 below.
77
4. Click Save
Your changes are applied. If you toggled XMPP federation support, you will be required to confirm that you
want to restart the XCProuter on the VCS Control.
You may also need to restart the Unified CM IM&P XCP router services that are connected to the associated
VCS Control.
5. Log on to each IM and Presence server to check for notifications that you need to restart the XCPRouters. If
you do need to restart them:
a. In Cisco Unified IM and Presence Serviceability, go to Tools > Control Center - Network Services.
b. Scroll down to the IMand Presence Services section and select Cisco XCPRouter.
c. Click Restart.
This causes a restart of all XCP services on the IM and Presence Service.
The service restart may take several minutes.
d. Repeat on each IM and Presence server.
You could use the utils service CLI option (accessed via the Cisco Unified IM and Presence Operating
System) to restart the services instead.
Configuring How XMPP Servers for Federated Domains and Chat Node Aliases Are Located
You can use DNS lookups to locate the XMPP servers for federated domains and chat node aliases, or you can
configure the addresses of specific XMPP servers.
To use DNS lookups:
1. On VCS Expressway, go to Configuration >Unified Communications.

2. Set Use static routes to Off.
3. Click Save.
78
Note that all XMPP federated partners must publish in DNS the addresses of their XMPP servers as described in DNS
SRV Records for XMPP Federation, page 80.
To use static routes:
1. If you want to use static routes for group chat, you must contact the partners with whom you are federating to
get a list of their chat node aliases.
2. On VCS Expressway, go to Configuration >Unified Communications.
3. Set Use static routes to On and click Save.
4. Click Configure static routes for federated XMPP domains.
5. On the Federated static routes page, click New.
6. Enter the details of the static route:
Domain The federated XMPP domain or chat node alias.
Address The IP address or Fully Qualified Domain Name (FQDN) of an XMPP server for this federated
domain or chat node alias.
7. Click Save.
8. Add as many additional static routes as required.
You can specify additional routes to alternative addresses for the same domain or chat node alias (all routes
have an equal priority).
Note that:
If there are no static routes defined for a federated domain or chat node alias, the system will use DNS
instead.
If static routes are defined for the federated domain or chat node alias, but the remote system cannot be
contacted over those routes, the system will not fall back to DNS.
If Privacy mode is set to Allow list and Use static routes is On, any domains (or chat node aliases) that are
configured as static routes are included automatically in the allow list.
Configuring the Allow and Deny Lists for Federated Domains and Chat Node Aliases
The allow and deny lists are used to control restrictions to the set of federated domains and chat node aliases. If
Privacy mode is set to Allow list or Deny list, you must add the domains and chat node aliases with which you want to
allow or deny federated connections.
This function manages restrictions at the domain / chat node alias level. Individual user-based privacy is controlled by
each client / end-user.
The allow list and deny list modes are mutually exclusive. Adomain/alias cannot be allowed and denied at the same
time.
When federation is first enabled, Privacy mode is set to Allow list by default. In effect this puts the system in a
'lockdown' mode you will not be allowed to connect with any federated domains or chat node aliases until you
either add them to the allow list, configure static routes, or change the Privacy mode setting.
1. On VCS Expressway, go to Configuration > Unified Communications.

2. Set Privacy mode as appropriate:
Off: No restrictions are applied.
Allow list: Federation is allowed only with the domains and chat node aliases specified in the allow list.
Deny list: Federation is allowed with any domain or chat node alias except for those specified in the deny
list.
3. Click Save.
79
4. To manage the domains and chat node aliases in the allow or deny lists, click either Federation allow list or
Federation deny list as appropriate.
In the resulting page you can add, modify or delete the items in the allow/deny list. Wildcards or regexes are
not allowed in the names; it must be an exact match.
All domains and chat node aliases that are configured as static routes are included automatically in the allow list.
DNS SRV Records for XMPP Federation

If federating parties are not using static routes to access federated XMPP services, suitable DNS SRV records must
be published.
_xmpp-server Records
You must publish an _xmpp-server DNS SRV record in DNS for your local domain so that remote enterprises can
access your federated XMPP services. For example:
Domain Service Protocol Priority Weight Port Target host
example.com xmpp-server tcp 0 0 5269 vcse.example.com
Similarly, to allow federating parties to discover a particular XMPP federated domain (if they are not using static
routes), the federated enterprise must publish an _xmpp-server DNS SRV record in its public DNS server. For example:
federated.com xmpp-server tcp 0 0 5269 xmppserver.federated.com
All enterprises must publish the service on port 5269. The published FQDNs must also be resolvable in DNS to an IP
address.
Group Chat
If you configure the Group Chat feature on a Unified CM IM&P server in an XMPP federation deployment, you must
publish DNSSRV records for the federated chat node aliases.
To allow IM and Presence Service to discover a particular XMPP federated chat node alias, the federated enterprise
must publish an _xmpp-server DNS SRV record in its public DNS server. Similarly, IM and Presence Service must
publish the same DNS SRV record in DNS for its domain. For example:
chatroom1.example.com xmpp-server tcp 0 0 5269 vcse.example.com
Both enterprises must publish the service on port 5269. The published FQDN must also be resolvable to an IP address
in DNS.
Alternatively, to use group chat aliases on federated servers, you can configure static routes on the VCS Expressway
(Configuration >Unified Communications >Federated static routes) for each chat node alias.
Note that:
The chat node aliases are configured on Unified CM IM&P Administration (Messaging > Group Chat Server
Alias Mapping).
Internal users do not need to use DNS to discover chat nodes; they get the chat room details from their local
IM&P servers.
See Chat configuration on IM and Presence for more information about point-to-point instant messaging and group
chat.
80
Port Usage for XMPPFederation

This section summarizes the firewall ports that need to be opened for XMPPfederation.
XMPP TCP Ephemeral port 7400
Purpose Protocol VCS Expressway (source) Federated XMPP server

(listening)
Purpose Protocol Federated XMPP server VCS Expressway (listening)

(source)
From VCS Control to IM and Presence Server
Purpose Protocol VCS Control (source) IM and Presence Server(listening)
Checking XMPP Federation Status

XMPP federation status information is available on the VCS Expressway only.
You can go to Status > Unified Communications to check the primary status of the XMPP federation service.
Normally, XMPP Federation should be Active.
If there are problems with the service, such as connectivity issues with the VCS Control, the status will show as
Inactive. In this case, you should also review the Unified Communications status page on the associated VCS Control
for more guidance as to what is causing the problem.
Viewing Federated Connections

To view the current federated connections being managed by the VCS Expressway:
1. On the VCS Expressway, go to Status > Unified Communications.

2. Click View federated connections in the Advanced status information section.
This shows all the current connections passing through that VCS Expressway.
It displays the IP Address of the client, and the Direction (Incoming or Outgoing) of the communication.
Connections are closed after 10 minutes of inactivity.
Note that in clustered systems:
An aggregated view is not displayed; only connections routed through the current peer are displayed.
In 2-way connections, the inbound and outbound communications may be managed by different peers.
81
Troubleshooting External XMPP Federation

This section describes how to troubleshoot your external XMPP federation deployment and describes the impact of
making configuration changes on a live system.
Checking the Basic Status of Your System

If you encounter issues with the XMPP federation status service, you should first check the Status >Unified
Communications page on both the VCS Control and the VCS Expressway.
This will highlight any basic connection or configuration problems and provide information and links to help correct
the problem.
General Configuration Checklist

Ensure that the following VCS configuration items have been specified correctly:
Port 5269 is open in both directions between the internet and VCS Expressway in the DMZ.
DNS settings: host name, domain name and default DNS server (System >DNS).
An accessible NTP server (System >Time).
An active Unified Communications traversal zone on the VCS Control and its associated VCS Expressway
(Status >Zones).
Unified Communications mode is set to Mobile and remote access on both the VCS Control and the VCS
Expressway (Configuration > Unified Communications > Configuration).
XMPP federation support is On on the VCS Expressway (Configuration > Unified Communications >
Configuration).
If static routes are enabled, ensure that the appropriate routes for the federated XMPP domains have been
added to the VCS Expressway (Configuration > Unified Communications > Federated static routes).
At least one domain is configured on the VCS Control with XMPP federation set to On (Configuration
>Domains).
IM &Presence servers have been discovered on the VCS Controland have an active status (Configuration >
Unified Communications >IM and Presence servers).
Discovery, Connectivity and Firewall Issues
If using DNSlookup, check that _xmpp-server public DNS records exist for the domains and chat node aliases
of all federated parties, and that they use port 5269.
Check that port 5269 is open in both directions between the internet and VCS Expressway in the DMZ.
If the VCS Control cannot connect to XCP on the VCS Expressway remote host:
Check that the firewall has not blocked port 7400.
If the VCS Expressway is running dual network interfaces, ensure that the traversal zone on the VCS
Control is connected to the internally-facing interface on the VCS Expressway.
Be aware that inbound and outbound connections can be routed through different cluster peers.
Certificates and Secure TLS Connections

If you have configured secure TLS connections, ensure that:
Valid server certificates are installed, they are in date and not revoked.
Both the remote and local server certificates must contain a valid domain in the Subject Alternative Name
(SAN). This applies even if Require client-side security certificates is disabled.
82
If Require client-side security certificates is enabled, ensure that the server certificate is signed by a CA and
is not locally signed.
Certificate Authority (CA) certificates are installed.
If you are using group chat over TLS, ensure that the VCS Control and VCS Expressway server certificates
include in their list of subject alternate names (using either XMPPAddress or DNS formats) all of the Chat Node
Aliases that are configured on the IM and Presence servers.
Ensure that compatible security settings (TLS required, optional, no TLS) exist on your system and the remote
federated system.
See Server Certificate Requirements for Unified Communications, page 54 for more information.
Checking the Event Log

Check the Event Log on the VCS Expressway for XMPP events.
Events related to XMPP federation are tagged with Module="XMPPFederation". There are no XMPP-related logs on the
VCS Control.
Performing Diagnostic Logging

When performing diagnostic logging (Maintenance > Diagnostics > Diagnostic logging), set the
develop.xcp.federation support log ( Maintenance > Diagnostics > Advanced > Support Log configuration) to
debug level.
Disabling Interdomain XMPPFederation on Unified CM IM&P

You must not enable both Interdomain XMPPFederation on Unified CM IM&P and XMPP federation on VCS
Expressway. One symptom of this incorrect configuration is that some users will have one-way federation.
If Interdomain Federation is enabled on Unified CM IM&P, perform the following operations in exactly the order shown:
1. Disable Interdomain Federation on the IM&P servers:

a. Go to Cisco Unified CM IM and Presence Administration > Presence > Inter Domain Federation > XMPP
Federation > Settings.
b. Set XMPP Federation Node Status to Off.
2. Refresh the set of discovered IM&P servers on VCS Control.
3. Restart all of the Unified CM IM&P XCP Router services that are connected to that VCS Control.
Impact of Configuration Changes on a Live System

In general, we recommend that XMPP federation configuration changes are made 'out of hours'. This section
describes the impact that configuration changes will have on current clients using XMPP federation and any Jabber
clients using mobile and remote access.
VCS Control Configuration Changes
Domains
Any domain configuration changes, when one or more existing domains are configured for IM and Presence services
on Unified CM or XMPP Federation will result in an automatic restart of the XCP router on both VCS Control and VCS
Expressway.
The end-user impact is temporary loss of federation and any Jabber clients using mobile and remote access will be
temporarily disconnected. The clients will automatically reconnect after a short period.
83
Unified Communications mode

Setting the Unified Communications mode to Off or to Jabber Guest services will stop the the XCP router on both
This will remove the VCS Expressway XMPP federation node from all discovered IM&P servers. A notification
will appear on the IM&P administration interface to restart the XCP router on all affected IM&P nodes.
The end-user impact is that all IM&Psessions will be disconnected. That is, there is a loss of federation,
IM&Psessions over mobile and remote access will be disconnected, and sessions directly homed on the
IM&Pnode will be dropped. When the XCP router is restarted on each IM&P node, all XCP functionality on that
node will be disrupted.
Discovered IM & Presence Servers
Adding or deleting an IM & Presence publisher will require a restart of the XCP router on each IM & Presence node
associated with that publisher only if XMPP Federation is enabled.
This will cause a restart of the XCP router on VCS Control.

The end-user impact should be minimal. They will be unable to send or receive IM & Presence updates for a
few seconds.
VCS Expressway Configuration Changes
Unified Communications mode

Setting the Unified Communications mode to Off or to Jabber Guest services will stop the the XCP router on both
This will remove the VCS Expressway XMPP federation node from all discovered IM&P servers. A notification
will appear on the IM&P administration interface to restart the XCP router on all affected IM&P nodes.
Note that turning the Unified Communications Mode back to On will reinsert the XMPP federation node and have the
same impact on the IM&P servers.
XMPP federation support
Changing the XMPP federation support setting will restart the VCS Expressway XCP router.
This will result in the addition/removal of the VCS Expressway XMPP federation node from all discovered IM &
Presence servers. A notification will appear on the IM&P administration interface to restart the XCP router on
all affected IM&P nodes.
Other XMPP federation settings
Changing any of the other XMPP federation settings, such as static routes, security and privacy settings, or the
allow/deny lists, will only result in a restart of the XMPP Federation Connection Manager service on the VCS
Expressway.
End-users may notice a temporary disruption to federation; any mobile and remote access IM&P sessions will remain
connected.
84
Client Reconnection Times After Loss of Service
The time taken for a client to reconnect to the XMPP service depends on the re-login limits specified in the Cisco
Server Recovery Manager service parameters on the IM&P server.
See the High Availability Client Login Profiles section in Configuration and Administration of IM and Presence Service
on Cisco Unified Communications Manager for the IM&P version that you are running.
Temporary or Partial Loss of IM and Presence Service Federation

XMPP federation for IM and Presence Service via VCS relies on a persistent TCP connection to the federated server.
If a federated server becomes unavailable due to a graceful shutdown, VCS will immediately seek to reestablish a
connection with the federated server or with another server advertised by the federated partner.
If, however, the federated server fails abruptly, it can take up to 15 minutes for VCS to discover the TCP connection
outage and attempt reconnection. During this time, a partial or full loss of IM and Presence Service connectivity with
the federated partner may occur.
Jabber Guest Services Overview

Cisco Jabber Guest is a consumer to business (C2B) solution that extends the reach of Cisco's enterprise telephony
to people outside of a corporate firewall who do not have phones registered with Cisco Unified Communications
Manager.
It allows an external user to click on a hyperlink (in an email or a web page) that will download and install (on first use)
an H.264 plugin into the user's browser. It then uses http-based call control to "dial" a URL to place a call to a
predefined destination inside the enterprise. The user is not required to open an account, create a password, or
otherwise authenticate.
To enable the call to be placed, it uses the Expressway solution (a secure traversal zone between the VCS Control
and VCS Expressway) as a Unified Communications gateway to traverse the firewall between the Jabber Guest client
in the internet and the Jabber Guest servers inside the enterprise to reach the destination user agent (endpoint).
Figure 9 Jabber Guest Components
Information Scope
In versions X8.6 and earlier, all VCS configuration required for deployment with Jabber Guest was contained in the
Administrator Guide. From X8.7 onwards, that information is kept in a separate deployment guide. You can read more
detailed information about Jabber Guest in the following documents:
Cisco TelePresence VCSwith Jabber Guest Deployment Guide, at the VCS Configuration Guides page.
Cisco Jabber Guest Server Installation and Configuration Guide, for your version, at the Jabber Guest
Insallation and Upgrade Guides page.
85
Cisco Jabber Guest Administration Guide, for your version, at Jabber Guest Maintain and Operate Guides
page.
Cisco Jabber Guest Release Notes, for your version, at the Jabber Guest Release Notes page.
86
87
Protocols
This section provides information about how to configure the VCS to support the SIP and H.323 protocols.
About H.323 88
Configuring H.323 89
About SIP 90
Configuring SIP 93
Configuring Domains 97
Configuring SIP and H.323 Interworking 98
About H.323
The VCS supports the H.323 protocol: it is an H.323 gatekeeper.
It can also provide interworking between H.323 and SIP, translating between the two protocols to enable endpoints
that only support one of these protocols to call each other. In order to support H.323, the H.323 mode must be
enabled.
Using the VCS as an H.323 Gatekeeper

As an H.323 gatekeeper, the VCS accepts registrations from H.323 endpoints and provides call control functions such
as address translation and admission control.
To enable the VCS as an H.323 gatekeeper, you must ensure that H.323 mode is set to On (Configuration > Protocols
> H.323).
Note that this is the default setting, so the VCS will work as an H.323 gatekeeper "out of the box", without any other
special configuration.
H.323 Endpoint Registration

H.323 endpoints in your network must register with the VCS in order to use it as their gatekeeper.
There are two ways an H.323 endpoint can locate a VCS with which to register: manually or automatically. The option
is configured on the endpoint itself under the Gatekeeper Discovery setting (consult your endpoint manual for how to
access this setting).
If the mode is set to automatic, the endpoint will try to register with any VCS it can find. It does this by sending
out a Gatekeeper Discovery Request, to which eligible VCSs will respond.
If the mode is set to manual, you must specify the IP address of the VCS with which you want your endpoint to
register, and the endpoint will attempt to register with that VCS only.
Preventing Automatic H.323 Registrations

You can prevent H.323 endpoints being able to register automatically with the VCS by disabling Auto Discovery on
the VCS (Configuration > Protocols > H.323).
88
Registration Refresh
The H.323 Time to live setting controls the frequency of H.323 endpoint registration refresh. The refresh frequency
increases when the time to live is decreased. When you have many H.323 endpoints, be careful not to set the TTLtoo
low, because a flood of registration requests will unnecessarily impact the VCS performance.
Configuring H.323
The H.323 page (Configuration > Protocols > H.323) is used to configure the H.323 settings on the VCS, including:
whether H.323is enabled or not

H.323 gatekeeper settings
whether to insert the prefix of the ISDN gateway into the caller's E.164 number presented on the destination
endpoint
H.323 mode Enables or disables H.323 on

the VCS. H.323 support is On
by default.
Registration The listening port for H.323 The default VCS configuration uses standard port numbers so you
UDP port UDP registrations. Default is can use H.323 services out of the box without having to first set
1719. these up.
Call The listening port for H.323

signaling call signaling. Default is 1720.
TCP port
Call Specifies the lower port in the The call signaling port range must be great enough to support all the
signaling range used by H.323 calls required concurrent calls.
port range after they are established.
start and Default is 15000.
end
Registration Determines how the system An H.323 endpoint may attempt to register with the VCS using an
conflict behaves if an endpoint alias that has already been registered on the VCS from another IP
mode attempts to register an alias address. The reasons for this could include:
currently registered from
another IP address. Two endpoints at different IP addresses are attempting to
register using the same alias.
Reject: denies the new
registration. This is the A single endpoint has previously registered using a particular
default. alias. The IP address allocated to the endpoint then changes,
and the endpoint attempts to re-register using the same
Overwrite: deletes the original alias.
registration and replaces it
with the new registration. Reject is useful if your priority is to prevent two users registering with
the same alias. Overwrite is useful if your network is such that
endpoints are often allocated new IP addresses, because it will
prevent unwanted registration rejections.
Note that in a cluster a registration conflict is only detected if the

registration requests are received by the same peer.
89
Time to live The interval (in seconds) at Some older endpoints do not support the ability to periodically re-
which an H.323 endpoint register with the system. In this case, and in any other situation
must re-register with the VCS where the system has not had a confirmation from the endpoint
in order to confirm that it is within the specified period, it will send an IRQ to the endpoint to
still functioning. Default is verify that it is still functioning.
1800.
Note:By reducing the registration time to live too much, you risk
flooding the VCS with registration requests, which will severely
impact performance. This impact is proportional to the number of
endpoints, so you should balance the need for occasional quick
failover against the need for continuous good performance.
Call time to The interval (in seconds) at If the endpoint does not respond, the call will be disconnected.
live which the VCS polls the
endpoints in a call to verify The system polls endpoints in a call regardless of whether the call
that they are still in the call. type is traversal or non-traversal.
Default is 120.
Auto Determines whether it will To prevent H.323 endpoints being able to register automatically with
discover respond to Gatekeeper the VCS, set Auto discover to Off. This means that endpoints can
Discovery Requests sent out only register with the VCS if their Gatekeeper Discovery setting is
by endpoints. The default is Manual and they have been configured with the VCSs IP address.
On.
Caller ID Specifies whether the prefix Including the prefix allows the recipient to directly return the call.
of the ISDN gateway is
inserted into the caller's
E.164 number presented on
the destination endpoint.
About SIP
The VCS supports the SIP protocol. It can act as a SIP registrar, SIP proxy and as a SIP Presence Server.
The VCS can provide interworking between SIP and H.323, translating between the two protocols to enable
endpoints that only support one of these protocols to call each other.
To support SIP:
SIP mode must be enabled.

At least one of the SIP transport protocols (UDP, TCP or TLS) must be active. Note that the use of UDP is not
recommended for video as SIP message sizes are frequently larger than a single UDP packet.
VCS as a SIP Registrar

For a SIP endpoint to be contactable via its alias, it must register its Address of Record (AOR) and its location with a
SIP registrar. The SIP registrar maintains a record of the endpoints details against the endpoints AOR. The AOR is
the alias through which the endpoint can be contacted; it is a SIPURI and always takes the form username@domain.
When a call is received for that AOR, the SIP registrar refers to the record to find its corresponding endpoint. (Note
that the same AOR can be used by more than one SIP endpoint at the same time, although to ensure that all
endpoints are found they must all register with the same VCS or VCS cluster.)
A SIP registrar only accepts registrations for domains for which it is authoritative. The VCS can act as a SIP registrar
for up to 200 domains. To make the VCS act as a SIP registrar, you must configure it with the SIP domains for which it
will be authoritative . It will then handle registration requests for any endpoints attempting to register against that
domain. Note that the VCS will also accept registration requests where the domain portion of the AOR is either the
90
FQDN or the IP address of the VCS. Whether or not the VCS accepts a registration request depends on its registration
control settings.
In a Unified Communications deployment, endpoint registration for SIP devices may be provided by Unified CM. In this
scenario, the VCS provides secure firewall traversal and line-side support for Unified CM registrations. When
configuring a domain, you can select whether Cisco Unified Communications Manager or VCS provides registration
and provisioning services for the domain.
SIP endpoint registration
There are two ways a SIP endpoint can locate a registrar with which to register: manually or automatically. The option
is configured on the endpoint itself under the SIP Server Discovery option (consult your endpoint user guide for how
to access this setting; it may also be referred to as Proxy Discovery).
If the Server Discovery mode is set to automatic, the endpoint will send a REGISTER message to the SIP
server that is authoritative for the domain with which the endpoint is attempting to register. For example, if an
endpoint is attempting to register with a URI of [email protected], the request will be sent to the registrar
authoritative for the domain example.com. The endpoint can discover the appropriate server through a variety of
methods including DHCP, DNS or provisioning, depending upon how the video communications network has
been implemented.
If the Server Discovery mode is set to manual, the user must specify the IP address or FQDN of the registrar
(VCS or VCS cluster) with which they want to register, and the endpoint will attempt to register with that
registrar only.
The VCS is a SIP server and a SIP registrar.
If an endpoint is registered to the VCS, the VCS will be able to forward inbound calls to that endpoint.
If the VCS is not configured with any SIP domains, the VCS will act as a SIP server. It may proxy registration
requests to another registrar, depending upon the SIP registration proxy mode setting.
Registration refresh intervals
Depending on the typical level of active registrations on your system, you may want to configure the Standard
registration refresh strategy to Variable and set the refresh intervals as follows:
Active registrations Minimum refresh interval Maximum refresh interval
1100 45 60
101500 150 200
5011000 300 400
10001500 450 800
1500+ 750 1000
Note:If you have a mix of H.323 and SIP endpoints, be aware that H.323 registration requests and SIP registration
requests can both impair performance of the VCS if it receives too many. See H.323 registration time to live.
If you want to ensure registration resiliency, use SIP outbound registrations as described below.
SIP registration resiliency
The VCS supports multiple client-initiated connections (also referred to as "SIP Outbound") as outlined in RFC 5626.
This allows SIP endpoints that support RFC 5626 to be simultaneously registered to multiple VCS cluster peers. This
provides extra resiliency: if the endpoint loses its connection to one cluster peer it will still be able to receive calls via
one of its other registration connections.
VCS as a SIP Proxy Server

The VCS acts as a SIP proxy server when SIP mode is enabled. The role of a proxy server is to forward requests (such
as REGISTER and INVITE) from endpoints or other proxy servers on to further proxy servers or to the destination
91
endpoint.
The VCS's behavior as a SIP proxy server is determined by:
the SIP registration proxy mode setting

the presence of Route Set information in the request header
whether the proxy server from which the request was received is a neighbor of the VCS
A Route Set specifies the path to take when requests are proxied between an endpoint and its registrar. For example,
when a REGISTER request is proxied by the VCS, it adds a path header component to the request. This signals that
calls to that endpoint should be routed through the VCS. This is usually required in situations where firewalls exist
and the signaling must follow a specified path to successfully traverse the firewall. For more information about path
headers, see RFC 3327.
When the VCS proxies a request that contains Route Set information, it forwards it directly to the URI specified in the
path. Any call processing rules configured on the VCS are bypassed. This may present a security risk if the
information in the Route Set cannot be trusted. For this reason, you can configure how the VCS proxies requests that
contain Route Sets by setting the SIP registration proxy mode as follows:
Off: requests containing Route Sets are rejected. This setting provides the highest level of security.
Proxy to known only: requests containing Route Sets are proxied only if the request was received from a
known zone.
Proxy to any: requests containing Route Sets are always proxied.
In all cases, requests that do not have Route Sets are proxied as normal in accordance with existing call processing
rules. This setting only applies to dialog-forming requests, such as INVITE and SUBSCRIBE. Other requests, such as
NOTIFY, are always proxied regardless of this setting.
Proxying Registration Requests

If the VCS receives a registration request for a domain for which it is not acting as a Registrar (the VCS does not have
that SIP domain configured), then the VCS may proxy the registration request onwards. This depends on the SIP
registration proxy mode setting, as follows:
Off: the VCS does not proxy any registration requests. They are rejected with a 403 Forbidden message.
Proxy to known only: the VCS proxies the request in accordance with existing call processing rules, but only to
known neighbor, traversal client and traversal server zones.
Proxy to any: this is the same as Proxy to known only but for all zone types i.e. it also includes ENUM and DNS
zones.
If your network is set up to proxy registration requests, we recommend that you disable GRUU on the VCS systems
that are acting as a Registrar for those proxied requests. If GRUU is left enabled, Presence may not work properly for
the proxy registered endpoints.
GRUU can only be disabled via the CLI (xConfiguration SIP GRUU Mode: Off).
Accepting proxied registration requests
If the VCS receives a proxied registration request, in addition to the VCS's standard registration controls, you can also
control whether the VCS accepts the registration depending upon the zone through which the request was received.
You do this through the Accept proxied registrations setting when configuring a zone.
Proxied registrations are classified as belonging to the zone they were last proxied from. This is different from non-
proxied registration requests which are assigned to a subzone within the VCS.
VCS as a SIP Presence Server

The VCS supports the SIP-based SIMPLE protocol. It can act as a Presence Server and Presence User Agent for any
of the SIP domains for which it is authoritative. For full information on how to enable and use the VCS as a SIP
Presence server, see the Presence section.
92
Configuring SIP
The SIP page (Configuration > Protocols > SIP) is used to configure the SIP settings on the VCS, including:
SIP functionality and SIP-specific transport modes and ports

certificate revocation checking modes for TLS connections
registration controls for standard and outbound registrations
authentication controls for delegated credential checking
SIP Functionality and SIP-Specific Transport Modes and Ports

This section contains the basic settings for enabling SIP functionality and for configuring the various SIP-specific
transport modes and ports. The configurable options are:
SIP mode Enables and disables SIP functionality (SIP registrar and This mode must be enabled to use
SIP proxy services) on the VCS. Default is On. either the Presence Server or the
Presence User Agent.
SIP protocols The VCS supports SIP over UDP, TCP and TLS transport At least one of the transport protocol
and ports protocols. Use the Mode and Port settings for each modes must be On to enable SIP
protocol to configure whether or not incoming and functionality.
outgoing connections using that protocol are supported,
and if so, the ports on which the VCS listens for such
connections.
The default modes and ports are:
UDP mode Off, port 5060

TCP mode On, port 5060
TLS mode On, port 5061
Mutual TLSmode Off, port 5062
TCP outbound The range of ports the VCS uses when TCP and TLS The range must be sufficient to
port start / connections are established. The default range is 25000 to support all required concurrent
end 29999. connections.
Session The maximum time allowed between session refresh For further information see the
refresh requests for SIP calls. Default is 1800 seconds. definition of Session-Expires in RFC
interval 4028.
Minimum The minimum value the VCS will negotiate for the session For further information see the
session refresh interval for SIP calls. Default is 500 seconds. definition of Min-SE header in RFC
refresh 4028.
interval
TLS The timeout period for TLS socket handshake. Default is 5 You may want to increase this value
handshake seconds. if TLS server certificate validation is
timeout slow (e.g. if OCSP servers do not
provide timely responses) and thus
cause connection attempts to
timeout.
93
Certificate Revocation Checking Modes

This section controls the certificate revocation checking modes for SIP TLS connections. The configurable options
are:
Certificate Controls whether revocation checking is performed for We recommend that revocation
revocation certificates exchanged during SIP TLS connection checking is enabled.
checking establishment.
mode
Use OCSP Controls whether the Online Certificate Status Protocol To use OCSP, the X.509 certificate
(OCSP) may be used to perform certificate revocation to be checked must contain an
checking. OCSP responder URI.
Use CRLs Controls whether Certificate Revocation Lists (CRLs) are CRLs can be used if the certificate
used to perform certificate revocation checking. does not support OCSP.
CRLs can be loaded manually onto

the VCS, downloaded automatically
from preconfigured URIs (see
Managing Certificate Revocation
Lists (CRLs), page 286), or
downloaded automatically from a
CRL distribution point (CDP) URI
contained in the X.509 certificate.
Allow CRL Controls whether the download of CRLs from the CDP URIs
downloads contained in X.509 certificates is allowed.
from CDPs
Fallback Controls the revocation checking behavior if the revocation Treat as not revoked ensures that
behavior status cannot be established, for example if the revocation your system continues to operate in
source cannot be contacted. a normal manner if the revocation
source cannot be contacted,
Treat as revoked: treat the certificate as revoked (and thus however it does potentially mean
do not allow the TLS connection). that revoked certificates will be
accepted.
Treat as not revoked: treat the certificate as not revoked.
Registration Controls
This section contains the registration controls for standard and outbound SIP registrations. The configurable options
are:
94
Standard The method used to generate the SIP registration expiry The Maximum setting uses the
registration period (the period within which a SIP endpoint must re- requested value providing it is within
refresh register to prevent its registration expiring) for standard the specified maximum and
strategy registrations. minimum ranges.
Maximum: uses the lesser of the configured Maximum The Variable setting calculates a
refresh value and the value requested in the registration. random refresh period for each
registration (and re-registration)
Variable: generates a random value between the request in an attempt to continually
configured Minimum refresh value and the lesser of the spread the load. The VCS never
configured Maximum refresh value and the value returns a value higher than what
requested in the registration. was requested.
The default is Maximum. This applies only to endpoints
registered with the VCS. It does not
apply to endpoints whose
registrations are proxied through the
VCS.
Standard The minimum allowed value for a SIP registration refresh See Registration refresh intervals,
registration period for standard registrations. Requests for a value page 91
refresh lower than this will result in the registration being rejected
minimum with a 423 Interval Too Brief response. The default is 45
seconds.
Standard The maximum allowed value for a SIP registration refresh

registration period for standard registrations. Requests for a value
refresh greater than this will result in a lower value being returned
maximum (calculated according to the Standard registration
refresh strategy). The default is 60 seconds.
Outbound The method used to generate the SIP registration expiry These options work in the same
registration period for outbound registrations. manner as for the Standard
refresh registration refresh strategy.
strategy Maximum: uses the lesser of the configured Maximum
refresh value and the value requested in the registration. However, outbound registrations
allow a much higher maximum value
Variable: generates a random value between the than standard registrations. This is
configured Minimum refresh value and the lesser of the because standard registrations use
configured Maximum refresh value and the value the re-registration mechanism to
requested in the registration. keep their connection to the server
alive. With outbound registrations
The default is Variable. the keep-alive process is handled by
a separate, less resource-intensive
process, meaning that re-
registrations (which are more
resource-intensive) can be less
frequent.
Outbound The minimum allowed value for a SIP registration refresh

registration period for outbound registrations. Requests for a value
refresh lower than this will result in the registration being rejected
minimum with a 423 Interval Too Brief response. The default is 600
seconds.
95
Outbound The maximum allowed value for a SIP registration refresh

registration period for an outbound registration. Requests for a value
refresh greater than this will result in a lower value being returned
maximum (calculated according to the Outbound registration
refresh strategy). The default is 3600 seconds.
SIP Specifies how proxied registrations and requests See Proxying Registration Requests,
registration containing Route Sets are handled when the VCS receives page 92 for more information.
proxy mode a registration request for a domain for which it is not acting
as a Registrar.
Off: registration requests are not proxied (but are still

permitted locally if the VCS is authoritative as a Registrar
for that domain). Requests with existing Route Sets are
rejected.
Proxy to known only: registration requests are proxied in

accordance with existing call processing rules, but only to
known neighbor, traversal client and traversal server
zones. Requests containing Route Sets are proxied only if
they were received from a known zone.
Proxy to any: registration requests are proxied in

accordance with existing call processing rules to all known
zones. Requests containing Route Sets are always
proxied.
The default is Off.
Authentication Controls
This section contains the device authentication controls for enabling delegated credential checking. The
configurable options are:
Delegated Controls whether the credential checking of SIP messages Note that delegated credential
credential is delegated, via a traversal zone, to another VCS. checking must be enabled on both
checking the traversal server and the traversal
Off: use the relevant credential checking mechanisms client.
(local database, Active Directory Service or H.350
directory via LDAP) on the VCS performing the See delegated credential checking
authentication challenge. for more information.
On: delegate the credential checking to a traversal client.
The default is Off.
Advanced SIP Settings

SDP max size Specifies the maximum size of SDP payload that can be
handled by the VCS (in bytes)
Default is 32768 bytes.
96
SIPTCPconnect Specifies the maximum number of seconds to wait for an You can reduce this to speed up
timeout outgoing SIP TCP connection to be established. the time between attempting a
broken route (eg. unavailable
Default is 10 seconds. onward SIPproxy peer) and failing
over to a good one.
Be careful in high latency networks

that you leave enough time for the
connection to establish.
Configuring Domains
The Domains page (Configuration > Domains) lists the SIP domains managed by this VCS.
A domain name can comprise multiple levels. Each level's name can only contain letters, digits and hyphens, with
each level separated by a period (dot). A level name cannot start or end with a hyphen, and the final level name must
start with a letter. An example valid domain name is 100.example-name.com.
Note that values shown in the Index column correspond to the numeric elements of the %localdomain1%,
%localdomain2%, . . . %localdomain200% pattern matching variables.
You can configure up to 200 domains.
Configuring the Supported Services for Unified Communications (VCS Control Only)
When the VCS Control has been enabled for Unified Communications mobile and remote access, you must select the
services that each domain will support. The options are:
SIP registrations and provisioning on VCS: the VCS is authoritative for this SIP domain. The VCS acts as a
SIP registrar and Presence Server for the domain, and accepts registration requests for any SIP endpoints
attempting to register with an alias that includes this domain. The default is On.
SIP registrations and provisioning on Unified CM: Endpoint registration, call control and provisioning for this
SIP domain is serviced by Unified CM. The VCS acts as a Unified Communications gateway to provide secure
firewall traversal and line-side support for Unified CM registrations. The default is Off.
IM and Presence Service: Instant messaging and presence services for this SIP domain are provided by the
Unified CM IM and Presence service. The default is Off.
XMPPfederation: Enables XMPPfederation between this domain and partner domains. The default is Off.
Deployment: Associates the domain with the selected deployment, if there are multiple deployments. This
setting is absent if there is only one deployment (there is always at least one).
Any domain configuration changes, when one or more existing domains are configured for IM and Presence services
on Unified CM or XMPP Federation will result in an automatic restart of the XCP router on both VCS Control and VCS
Expressway.
The end-user impact is temporary loss of federation and any Jabber clients using mobile and remote access will be
temporarily disconnected. The clients will automatically reconnect after a short period.
Configuring Delegated Credential Checking (VCS Expressway Only)

If you have enabled delegated credential checking (Configuration > Protocols > SIP), you need to specify the
traversal zone to use when delegating credential checks for SIP messages for this domain. This only applies to the
SIP domains for which VCS is acting as the service provider and SIP registrar.
You can specify a different zone for each SIP domain, if required.
Choose Do not delegate if you want to continue to use this VCS Expressway to perform the credential checking.
97
Testing the credential checking service

To verify whether the VCS to which credential checking has been delegated is able to receive messages and perform
the relevant authentication checks:
1. Go to Configuration > Domains.

2. Select the relevant domains.
3. Click Test credential checking service.
The system displays a Results section and reports whether the receiving VCS can be reached over the
traversal zone and, additionally, if it is able to perform credential checking for both NTLM and SIP digest type
challenges.
If you are not using NTLM authentication in your video network, and thus the receiving VCS is not configured
with a connection to an Active Directory Service, then the NTLM check will be expected to fail.
Configuring SIP and H.323 Interworking

The Interworking page (Configuration > Protocols > Interworking) lets you configure whether or not the VCS acts as
a gateway between SIP and H.323 calls. The translation of calls from one protocol to the other is known as
interworking.
By default, the VCS acts as a SIPH.323 and H.323SIP gateway but only if at least one of the endpoints that are
involved in the call is locally registered. You can change this setting so that the VCS acts as a SIPH.323 gateway
regardless of whether the endpoints involved are locally registered. You also have the option to disable interworking
completely.
The options for the H.323 <-> SIP interworking mode are:
Off: the VCS does not act as a SIPH.323 gateway.

Registered only: the VCS acts as a SIPH.323 gateway but only if at least one of the endpoints is locally
registered.
On: the VCS acts as a SIPH.323 gateway regardless of whether the endpoints are locally registered.
You are recommended to leave this setting as Registered only (where calls are interworked only if at least one of the
endpoints is locally registered). Unless your network is correctly configured, setting it to On (where all calls can be
interworked) may result in unnecessary interworking, for example where a call between two H.323 endpoints is made
over SIP, or vice versa.
Calls for which the VCS acts as a SIP to H.323 gateway are traversal calls. The VCS always takes the media for SIP
H.323 interworked calls so that it can independently negotiate payload types on the SIP and H.323 sides and VCS will
re-write these as the media passes.
Also in a SIP SDP negotiation, multiple codec capabilities can be agreed (more than one video codec can be
accepted) and the SIP device is at liberty to change the codec it uses at any time within the call. If this happens,
because VCS is in the media path it will close and open logical channels to the H.323 device as the media changes
(as required) so that media is passed correctly.
Searching by protocol
When searching a zone, the VCS first performs the search using the protocol of the incoming call. If the search is
unsuccessful the VCS may then search the zone again using the alternative protocol, depending on where the search
came from and the Interworking mode. Note that the zone must also be configured with the relevant protocols
enabled (SIP and H.323 are enabled on a zone by default).
If the request has come from a neighboring system and Interworking mode is set to Registered only, the VCS
searches the Local Zone using both protocols, and all other zones using the native protocol only (because it
will interwork the call only if one of the endpoints is locally registered).
If Interworking mode is set to On, or the request has come from a locally registered endpoint, the VCS
searches the Local Zone and all external zones using both protocols.
98
Enabling SIP endpoints to dial H.323 numbers

SIP endpoints can only make calls in the form of URIs such as name@domain. If the caller does not specify a domain
when placing the call, the SIP endpoint automatically appends its own domain to the number that is dialed.
So if you dial 123 from a SIP endpoint, the search will be placed for 123@domain. If the H.323 endpoint being dialed is
just registered as 123, the VCS will not be able to locate the alias 123@domain and the call will fail. The solutions are to
either:
Ensure all your endpoints, both H.323 and SIP, register with an alias in the form name@domain.
Create a pre-search transform on the VCS that strips the @domain portion of the alias for those URIs that are in
the form of number@domain.
See the pre-search transforms section for information about how to configure pre-search transforms, and the
stripping @domain for dialing to H.323 numbers section for an example of how to do this.
Interworking DTMFsignals
For SIPcalls, the VCS implements RFC2833 for DTMFsignaling in RTP payloads.
For H.323 calls, the VCS implements H.245 UserInputIndication for DTMFsignaling.
When the VCS is interworking a call between SIPand H.323, it also interworks the DTMFsignaling, but only between
RFC2833 signaling and H.245 UserInputIndications.
99
Registration Control
This section provides information about the pages that appear under the Configuration > Registration menu.
About Registrations 100

About Allow and Deny Lists 103
Configuring Registration Policy to Use an External Service 105
About Registrations
For an endpoint to use the VCS as its H.323 gatekeeper or SIP registrar, the endpoint must first register with the VCS.
The VCS can be configured to control which devices are allowed to register with it by using the following
mechanisms:
a device authentication process based on the username and password supplied by the endpoint
a registration restriction policy that uses either Allow Lists or Deny Lists or an external policy service to specify
which aliases can and cannot register with the VCS
restrictions based on IP addresses and subnet ranges through the specification of subzone membership rules
and subzone registration policies
You can use these mechanisms together. For example, you can use authentication to verify an endpoints identity
from a corporate directory, and registration restriction to control which of those authenticated endpoints may register
with a particular VCS.
You can also control some protocol-specific behavior, including:
the Registration conflict mode and Auto discover settings for H.323 registrations
the SIP registration proxy mode for SIPregistrations
For specific information about how registrations are managed across peers in a cluster, see the Sharing Registrations
Across Peers, page 167 section.
In a Unified Communications deployment, endpoint registration for SIP devices may be provided by Unified CM. In this
scenario, the VCS provides secure firewall traversal and line-side support for Unified CM registrations. When
configuring a domain, you can select whether Cisco Unified Communications Manager or VCS provides registration
and provisioning services for the domain.
Finding a VCS With Which to Register

Before an endpoint can register with a VCS, it must determine which VCS it can or should be registering with. This
setting is configured on the endpoint, and the process is different for SIP and H.323.
Registrations on a VCS Expressway

If a traversal-enabled endpoint registers directly with a VCS Expressway, the VCS Expressway will provide the same
services to that endpoint as a VCS Control, with the addition of firewall traversal. Traversal-enabled endpoints
include all Cisco TelePresence Expressway endpoints and third-party endpoints which support the ITU H.460.18
and H.460.19 standards.
100
Endpoints that are not traversal-enabled can still register with a VCS Expressway, but they may not be able to make
or receive calls through the firewall successfully. This will depend on a number of factors:
whether the endpoint is using SIP or H.323

the endpoints position in relation to the firewall
whether there is a NAT in use
whether the endpoint is using a public IP address
For example, if an endpoint is behind a NAT or firewall, it may not be able to receive incoming calls and may not be
able to receive media for calls it has initiated. SIP endpoints can also work behind a NAT but can only receive video if
they send it as well.
To ensure firewall traversal will work successfully for H.323 endpoints behind a NAT, the endpoint must be traversal-
enabled.
MCU, Gateway and Content Server Registration

H.323 systems such as gateways, MCUs and Content Servers can also register with a VCS. They are known as locally
registered services. These systems are configured with their own prefix, which they provide to the VCS when
registering. The VCS will then know to route all calls that begin with that prefix to the gateway, MCU or Content
Server as appropriate. These prefixes can also be used to control registrations.
SIP devices cannot register prefixes. If your dial plan dictates that a SIP device should be reached via a particular
prefix, then you should add the device as a neighbor zone with an associated search rule using a pattern match equal
to the prefix to be used.
Note that the Cisco TelePresence MPS 200 and MPS 800, and the Cisco TelePresence Content Server both support
Expressway. They can therefore register directly with a VCS Expressway for firewall traversal.
Configuring Registration Restriction Policy

The Registration configuration page (Configuration > Registration > Configuration) is used to control how the VCS
manages its registrations.
The Restriction policy option specifies the policy to use when determining which endpoints may register with the
VCS. The options are:
None: any endpoint may register.

Allow List: only those endpoints with an alias that matches an entry in the Allow List may register.
Deny List: all endpoints may register, unless they match an entry on the Deny List.
Policy service: only endpoints that register with details allowed by the external policy service may register.
The default is None.
If you use an Allow List or Deny List, you must also go to the appropriate Registration Allow List or Registration Deny
List configuration page to create the list.
The Policy service option is used if you want to refer all registration restriction policy decisions out to an external
service. If you select this option an extra set of configuration fields appear so that you can specify the connection
details of the external service. See Configuring Registration Policy to Use an External Service, page 105.
Registering Aliases
After the device authentication process (if required) has been completed, the endpoint will then attempt to register its
aliases with the VCS.
H.323
When registering, the H.323 endpoint presents the VCS with one or more of the following:
101
one or more H.323 IDs

one or more E.164 aliases
one or more URIs
Users of other registered endpoints can then call the endpoint by dialing any of these aliases.
You are recommended to register your H.323 endpoints using a URI. This facilitates interworking between SIP
and H.323, as SIP endpoints register using a URI as standard.
You are recommended to not use aliases that reveal sensitive information. Due to the nature of H.323, call
setup information is exchanged in an unencrypted form.
SIP
When registering, the SIP endpoint presents the VCS with its contact address (IP address) and logical address
(Address of Record). The logical address is considered to be its alias, and will generally be in the form of a URI.
H.350 directory authentication and registrations
If the VCS is using an H.350 directory service to authenticate registration requests, the Source of aliases for
registration setting is used to determine which aliases the endpoint is allowed to attempt to register with. See Using
an H.350 Directory Service Lookup via LDAP, page 126 for more information.
Attempts to register using an existing alias
An endpoint may attempt to register with the VCS using an alias that is already registered to the system. How this is
managed depends on how the VCS is configured and whether the endpoint is SIP or H.323.
H.323: an H.323 endpoint may attempt to register with the VCS using an alias that has already been registered
on the VCS from another IP address. You can control how the VCS behaves in this situation by configuring the
Registration conflict mode, on the H.323 page (Configuration > Protocols > H.323).
SIP: a SIP endpoint will always be allowed to register using an alias that is already in use from another IP
address. When a call is received for this alias, all endpoints registered using that alias will be called
simultaneously. This SIP feature is known as forking.
Blocking registrations
If you have configured the VCS to use a Deny List, you will have an option to block the registration. This will add all
the aliases used by that endpoint to the Deny List.
Removing existing registrations
After a restriction policy has been activated, it controls all registration requests from that point forward. However, any
existing registrations may remain in place, even if the new list would otherwise block them. Therefore, you are
recommended to manually remove all existing unwanted registrations after you have implemented a restriction policy.
To manually remove a registration, go to Status > Registrations > By device, select the registrations you want to
remove, and click Unregister.
If the registered device is in an active call and its registration is removed (or expires), the effect on the call is
dependent on the protocol:
H.323: the call is taken down.

SIP: the call stays up by default. This SIP behavior can be changed but only via the CLI by using the command
xConfiguration SIP Registration Call Remove.
Re-registrations
All endpoints must periodically re-register with the VCS in order to keep their registration active. If you do not
manually delete the registration, the registration could be removed when the endpoint attempts to re-register, but this
depends on the protocol being used by the endpoint:
102
H.323 endpoints may use "light" re-registrations which do not contain all the aliases presented in the initial
registration, so the re-registration may not get filtered by the restriction policy. If this is the case, the
registration will not expire at the end of the registration timeout period and must be removed manually.
SIP re-registrations contain the same information as the initial registrations so will be filtered by the restriction
policy. This means that, after the list has been activated, all SIP registrations will disappear at the end of their
registration timeout period.
The frequency of re-registrations is determined by the Registration controls setting for SIP (Configuration >
Protocols > SIP) and the Time to live setting for H.323 (Configuration > Protocols > H.323).
Note:By reducing the registration time to live too much, you risk flooding the VCS with registration requests, which
will severely impact performance. This impact is proportional to the number of endpoints, so you should balance the
need for occasional quick failover against the need for continuous good performance.
About Allow and Deny Lists

When an endpoint attempts to register with the VCS it presents a list of aliases. One of the methods provided by the
VCS to control which endpoints are allowed to register is to set the Restriction policy (on the Configuring
Registration Restriction Policy, page 101 page) to Allow List or Deny List and then to include any one of the
endpoints aliases on the Allow List or the Deny List as appropriate. Each list can contain up to 2,500 entries.
When an endpoint attempts to register, each of its aliases is compared with the patterns in the relevant list to see if it
matches. Only one of the aliases needs to appear in the Allow List or the Deny List for the registration to be allowed or
denied.
For example, if the Restriction policy is set to Deny List and an endpoint attempts to register using three aliases, one
of which matches a pattern on the Deny List, that endpoints registration will be denied. Likewise, if the Restriction
policy is set to Allow List, only one of the endpoints aliases needs to match a pattern on the Allow List for it to be
allowed to register using all its aliases.
Allow Lists and Deny Lists are mutually exclusive: only one may be in use at any given time. You can also control
registrations at the subzone level. Each subzone's registration policy can be configured to allow or deny registrations
assigned to it via the subzone membership rules.
Configuring the Registration Allow List

The Registration Allow List page (Configuration > Registration > Allow List) shows the endpoint aliases and alias
patterns that are allowed to register with the VCS. Only one of an endpoint's aliases needs to match an entry in the
Allow Listfor the registration to be allowed.
To use the Allow List, you must select a Restriction policy of Allow List on the Registration configuration page.
Description An optional free-form description

of the entry.
103
Pattern The way in which the Pattern You can test whether a pattern matches a particular alias by
type string must match the alias. using the Check pattern tool (Maintenance > Tools > Check
Options are: pattern).
Exact: the alias must match the

pattern string exactly.
Prefix: the alias must begin with

the pattern string.
Suffix: the alias must end with the

pattern string.
Regex: the pattern string is a

regular expression.
Pattern The pattern against which an alias

string is compared.
Configuring the Registration Deny List

The Registration Deny List page (Configuration > Registration > Deny List)shows the endpoint aliases and alias
patterns that are not allowed to register with the VCS. Only one of an endpoint's aliases needs to match an entry in
the Deny Listfor the registration to be denied.
To use the Deny List, you must select a Restriction policy of Deny List on the Registration configuration page.
Description An optional free-form description

of the entry.
Pattern The way in which the Pattern You can test whether a pattern matches a particular alias by
type string must match the alias. using the Check pattern tool (Maintenance > Tools > Check
Options are: pattern).
Exact: the alias must match the

pattern string exactly.
Prefix: the alias must begin with

the pattern string.
Suffix: the alias must end with the

pattern string.
Regex: the pattern string is a

regular expression.
Pattern The pattern against which an alias

string is compared.
104
Configuring Registration Policy to Use an External Service

To configure Registration Policy to refer all registration restriction policy decisions out to an external service:
1. Go to Configuration > Registration > Configuration.

2. Select a Restriction policy of Policy service.
3. Configure the fields as follows:
Protocol The protocol used to connect to the policy The VCS automatically supports HTTP to
service. HTTPS redirection when communicating
with the policy service server.
The default is HTTPS.
Certificate When connecting over HTTPS, this setting The VCSs root CA certificates are loaded
verification controls whether the certificate presented by via (Maintenance > Security certificates
mode the policy server is verified. > Trusted CA certificate).
If On, for the VCS to connect to a policy server

over HTTPS, the VCS must have a root CA
certificate loaded that authorizes that servers
server certificate. Also the certificate's Subject
Common Name or Subject Alternative Name
must match one of the Server address fields
below.
HTTPS Enable this option if you want to protect Go to Maintenance > Security
certificate certificate checking using CRLs and you have certificates > CRL management to
revocation manually loaded CRL files, or you have enabled configure how the VCS uploads CRL files.
list (CRL) automatic CRL updates.
checking
Server Enter the IP address or Fully Qualified Domain If an FQDN is specified, ensure that the
address 1 - 3 Name (FQDN) of the server hosting the service. VCS has an appropriate DNS
You can specify a port by appending :<port> configuration that allows the FQDN to be
to the address. resolved.
For resiliency, up to three server

addresses can be supplied.
Path Enter the URL of the service on the server.
Status path The Status path identifies the path from where The policy server must supply return
the VCS can obtain the status of the remote status information, see Policy Server
service. Status and Resiliency, page 323.
The default is status.
Username The username used by the VCS to log in and

query the service.
Password The password used by the VCS to log in and The maximum plaintext length is 30
query the service. characters (which is subsequently
encrypted).
105
Default CPL This is the fallback CPL used by the VCS if the You can change it, for example, to
service is not available. redirect to an answer service or recorded
message.
For more information, see Default CPL for

Policy Services, page 487.
4. Click Save.
The VCS should connect to the policy service server and start using the service for Registration Policy
decisions.
Any connection problems will be reported on this page. Check the Status area at the bottom of the page and
check for additional information messages against the Server address fields.
106
107
Device Authentication
This section provides information about the VCS's authentication policy and the pages that appear under the
Configuration > Authentication menu.
About Device Authentication 108

Authenticating with External Systems 134
About Device Authentication

Device authentication is the verification of the credentials of an incoming request to the Cisco TelePresence Video
Communication Server (VCS) from a device or external system. It is used so that certain functionality may be reserved
for known and trusted users, for example the publishing of presence status, collection of provisioning data, or the
ability to use resources that cost money like ISDN gateway calling.
When device authentication is enabled on a VCS, any device that attempts to communicate with the VCS is
challenged to present its credentials (typically based on a username and password). The VCS will then verify those
credentials, or have them verified, according to the authentication method, and then accept or reject the message
accordingly.
VCS authentication policy can be configured separately for each zone and subzone. This means that both
authenticated and unauthenticated devices could be allowed to register to, and communicate with, the same VCS if
required. Subsequent call routing decisions can then be configured with different rules based upon whether a device
is authenticated or not.
The VCS attempts to verify the credentials presented to it by first checking against its on-box local database of
usernames and passwords. The local database also includes checking against credentials supplied by Cisco TMS if
your system is using device provisioning. If the username is not found in the local database, the VCS may then
attempt to verify the credentials via a real-time LDAP connection to an external H.350 directory service. The directory
service, if configured, must have an H.350 directory schema for either a Microsoft Active Directory LDAP server or an
OpenLDAP server.
You can also configure a VCS Expressway so that the credential checking of SIP messages is delegated, via a
traversal zone, to another VCS.
Along with one of the above methods, for those devices that support NTLM challenges, the VCS can alternatively
verify credentials via direct access to an Active Directory server using a Kerberos connection.
The various VCS authentication entry points and credential checking methods are shown below:
108
Unified Communications mobile and remote access devices

You do not have to make any explicit configuration on the VCS regarding the authentication of devices that are
registering to Unified CM via the VCS. The VCS automatically handles the authentication of these devices against its
home Unified CM cluster.
Configuring VCS Authentication Policy

Authentication policy is applied by the VCS at the zone and subzone levels. It controls how the VCS challenges
incoming messages (for provisioning, registration, presence, phone books and calls) from that zone or subzone and
whether those messages are rejected, treated as authenticated, or treated as unauthenticated within the VCS.
Each zone and subzone can set its Authentication policy to either Check credentials, Do not check credentials, or
Treat as authenticated.
Registration authentication is controlled by the Default Subzone (or relevant alternative subzone)
configuration.
Initial provisioning subscription request authentication is controlled by the Default Zone configuration.
Call, presence, and phone book request authentication is controlled by the Default Subzone (or relevant
alternative subzone) if the endpoint is registered, or by the Default Zone if the endpoint is not registered.
Note that the exact authentication policy behavior depends on whether the messages are H.323 messages, SIP
messages received from local domains, or SIP messages received from non-local domains. See Authentication Policy
Configuration Options, page 111 for a full description of the various authentication policy behaviors.
Zone-level authentication policy
Authentication policy is selectively configurable for different zone types, based on whether they receive messaging:
The Default Zone, Neighbor zones, traversal client zones, traversal server zones and Unified Communications
traversal zones all allow configuration of authentication policy
DNS and ENUM zones do not receive messaging and so have no authentication policy configuration.
To edit a zone's Authentication policy, go to Configuration > Zones >Zones and click the name of the zone. The
policy is set to Do not check credentials by default when you create a new zone.
109
Subzone-level authentication policy

Authentication policy is configurable for the Default Subzone and any other configured subzone.
To configure a subzone's Authentication policy, go to Configuration > Local Zone > Subzones, then click View/Edit
or the name of the subzone. The policy is set to Do not check credentials by default when a new subzone is created.
Provisioning and device authentication
The Provisioning Server requires that any provisioning or phone book requests it receives have already been
authenticated at the zone or subzone point of entry into the VCS. The Provisioning Server does not do its own
authentication challenge and will reject any unauthenticated messages.
See Device Provisioning and Authentication Policy, page 118 for more information.
Presence and device authentication
The Presence Server accepts presence PUBLISH messages only if they have already been authenticated:
The authentication of presence messages by the VCS is controlled by the authentication policy setting on the
Default Subzone (or relevant alternative subzone) if the endpoint is registered (which is the usual case), or by
the authentication policy setting on the Default Zone if the endpoint is not registered.
The relevant Authentication policy must be set to either Check credentials or Treat as authenticated,
otherwise PUBLISH messages will fail, meaning that endpoints will not be able to publish their presence
status.
See Presence and Authentication Policy, page 120 for more information.
Controlling System Behavior for Authenticated and Non-authenticated Devices

How calls and other messaging from authenticated and non-authenticated devices are handled depends on how
search rules, external policy services and CPL are configured.
Search rules
When configuring a search rule, use the Request must be authenticated attribute to specify whether the search rule
applies only to authenticated search requests or to all requests.
External policy services
External policy services are typically used in deployments where policy decisions are managed through an external,
centralized service rather than by configuring policy rules on the VCS itself. You can configure the VCS to use policy
services in the following areas:
Registration Policy
Search rules (dial plan)
Call Policy
User Policy (FindMe)
When the VCS uses a policy service it sends information about the call or registration request to the service in a
POST message using a set of name-value pair parameters. Those parameters include information about whether the
request has come from an authenticated source or not.
More information about policy services, including example CPL, can be found in External Policy on VCS Deployment
Guide.
CPL
If you are using the Call Policy rules generator on the VCS, source matches are carried out against authenticated
sources. To specify a match against an unauthenticated source, just use a blank field. (If a source is not
authenticated, its value cannot be trusted).
If you use uploaded, handcrafted local CPL to manage your Call Policy, you are recommended to make your CPL
explicit as to whether it is looking at the authenticated or unauthenticated origin.
110
If CPL is required to look at the unauthenticated origin (for example, when checking non-authenticated
callers) the CPL must use unauthenticated-origin. (However, if the user is unauthenticated, they can call
themselves whatever they like; this field does not verify the caller.)
To check the authenticated origin (only available for authenticated or treat as authenticated devices) the
CPL should use authenticated-origin.
Note that due to the complexity of writing CPL scripts, you are recommended to use an external policy service
instead.
Authentication Policy Configuration Options

Authentication policy behavior varies for H.323 messages, SIP messages received from local domains and SIP
messages from non-local domains.
The primary authentication policy configuration options and their associated behavior are as follows:
Check credentials: verify the credentials using the relevant authentication method. Note that in some
scenarios, messages are not challenged, see below.
Do not check credentials: do not verify the credentials and allow the message to be processed.
Treat as authenticated: do not verify the credentials and allow the message to be processed as if it is has
been authenticated. This option can be used to cater for endpoints from third-party suppliers that do not
support authentication within their registration mechanism. Note that in some scenarios, messages are
allowed but will still be treated as though they are unauthenticated, see below.
The following tables summarize the policy behavior when applied at the zone and subzone level, and how it varies
depending on the message protocol.
Zone-Level Authentication Policy

Authentication policy is selectively configurable for different zone types, based on whether they receive messaging:
The Default Zone, Neighbor zones, traversal client zones, traversal server zones and Unified Communications
traversal zones all allow configuration of authentication policy
DNS and ENUM zones do not receive messaging and so have no authentication policy configuration.
To edit a zone's Authentication policy, go to Configuration > Zones >Zones and click the name of the zone. The
policy is set to Do not check credentials by default when you create a new zone.
The behavior varies for H.323 and SIP messages as shown in the tables below:
H.323
Policy Behavior
Check Messages are classified as either authenticated or unauthenticated depending on whether any
credentials credentials in the message can be verified against the authentication database.
If no credentials are supplied, the message is always classified as unauthenticated.
Do not check Message credentials are not checked and all messages are classified as unauthenticated.
credentials
Treat as Message credentials are not checked and all messages are classified as authenticated.
authenticated
SIP
The behavior for SIP messages at the zone level depends upon the SIP authentication trust mode setting (meaning
whether the VCS trusts any pre-existing authenticated indicators - known as P-Asserted-Identity headers - within
the received message) and whether the message was received from a local domain (a domain for which the VCS is
authoritative) or a non-local domain.
111
Policy Trust In local domain Outside local domain
Check Off Messages are challenged for Messages are not challenged for
credentials authentication. authentication.
Messages that fail authentication are All messages are classified as

rejected. unauthenticated.
Messages that pass authentication are Any existing P-Asserted-Identity headers

classified as authenticated and a P- are removed.
Asserted-Identity header is inserted into the
message.
On Messages with an existing P-Asserted- Messages are not challenged for

Identity header are classified as authentication.
authenticated, without further challenge.
The P-Asserted-Identity header is passed Messages with an existing P-Asserted-
on unchanged (keeping the originator's Identity header are classified as
asserted ID). authenticated, and the header is passed
on unchanged.
Messages without an existing P-Asserted-
Identity header are challenged. If Messages without an existing P-Asserted-
authentication passes, the message is Identity header are classified as
classified as authenticated and a P- unauthenticated.
Asserted-Identity header is inserted into the
message. If authentication fails, the
message is rejected.
Do not check Off Messages are not challenged for Messages are not challenged for
credentials authentication. authentication.
All messages are classified as All messages are classified as

unauthenticated. unauthenticated.
Any existing P-Asserted-Identity headers Any existing P-Asserted-Identity headers

are removed. are removed.
On Messages are not challenged for Messages are not challenged for
authentication. authentication.
Messages with an existing P-Asserted- Messages with an existing P-Asserted-

Identity header are classified as Identity header are classified as
authenticated, and the header is passed on authenticated, and the header is passed
unchanged. on unchanged.
Messages without an existing P-Asserted- Messages without an existing P-Asserted-

Identity header are classified as Identity header are classified as
unauthenticated. unauthenticated.
Treat as Off Messages are not challenged for Messages are not challenged for
authenticated authentication. authentication.
All messages are classified as All messages are classified as

authenticated. unauthenticated.
Any existing P-Asserted-Identity header is Any existing P-Asserted-Identity headers

removed and a new one containing the are removed.
VCS's originator ID is inserted into the
message.
112
Policy Trust In local domain Outside local domain
On Messages are not challenged for Messages are not challenged for
authentication. authentication.
All messages are classified as Messages with an existing P-Asserted-

authenticated. Identity header are classified as
authenticated, and the header is passed
Messages with an existing P-Asserted- on unchanged.
Identity header are passed on unchanged.
Messages without an existing P-Asserted- Messages without an existing P-Asserted-
Identity header have one inserted. Identity header are classified as
unauthenticated.
Subzone-Level Authentication Policy

Authentication policy is configurable for the Default Subzone and any other configured subzone.
To configure a subzone's Authentication policy, go to Configuration > Local Zone > Subzones, then click View/Edit
or the name of the subzone. The policy is set to Do not check credentials by default when a new subzone is created.
The behavior varies for H.323 and SIP messages as shown in the tables below:
H.323
Policy Behavior
Check Messages are classified as either authenticated or unauthenticated depending on whether any
credentials credentials in the message can be verified against the authentication database. Messages that
pass authentication are classified as authenticated.
If no credentials are supplied, the message is always classified as unauthenticated.
Note that unauthenticated registration requests are rejected.
Do not check Message credentials are not checked and all messages are classified as unauthenticated.
credentials
Treat as Message credentials are not checked and all messages are classified as authenticated.
authenticated
SIP
The behavior for SIP messages depends upon whether the message was received from a local domain (a domain for
which the VCS is authoritative) or a non-local domain.
Policy In local domain Outside local domain
Check Messages are challenged for authentication and those that pass SIP messages received from
credentials are classified as authenticated. non-local domains are all
treated in the same manner,
Messages (including registration requests) that fail authentication regardless of the subzone's
are rejected. Authentication policy setting:
Do not check Messages are not challenged for authentication. Messages are not challenged
credentials for authentication.
All messages are classified as unauthenticated.
All messages are classified as
Treat as Messages are not challenged for authentication. unauthenticated.
authenticated
All messages are classified as authenticated.
113
SIP Authentication Trust

If the VCS is configured to use device authentication it will authenticate incoming SIP registration and INVITE
requests. If the VCS then forwards the request on to a neighbor zone such as another VCS, that receiving system will
also authenticate the request. In this scenario the message has to be authenticated at every hop.
To simplify this so that a devices credentials only have to be authenticated once (at the first hop), and to reduce the
number of SIP messages in your network, you can configure neighbor zones to use the Authentication trust mode
setting.
This is then used in conjunction with the zone's authentication policy to control whether pre-authenticated SIP
messages received from that zone are trusted and are subsequently treated as authenticated or unauthenticated
within the VCS. Pre-authenticated SIP requests are identified by the presence of a P-Asserted-Identity field in the
SIP message header as defined by RFC 3325.
The Authentication trust mode settings are:
On: pre-authenticated messages are trusted without further challenge and subsequently treated as
authenticated within the VCS. Unauthenticated messages are challenged if the Authentication policy is set to
Check credentials.
Off: any existing authenticated indicators (the P-Asserted-Identity header) are removed from the message.
Messages from a local domain are challenged if the Authentication policy is set to Check credentials.
Note:
We recommend that you enable authentication trust only if the neighbor zone is part of a network of trusted
SIP servers.
Authentication trust is automatically implied between traversal server and traversal client zones.
114
Configuring Delegated Credential Checking (SIP Only)

By default, the VCS uses the relevant credential checking mechanisms (local database, Active Directory Service or
H.350 directory via LDAP) on the same VCS that is performing the authentication challenge.
Alternatively you can configure the VCS that is performing the authentication challenges to delegate the credential
checking of SIP messages, via a traversal zone, to another VCS (typically a VCS Control). Delegated credential
checking is useful in deployments where you want to allow devices to register on the VCS Expressway (so that, for
example, calls may be made without having to use a traversal license), but for security you want all communications
with authentication systems (such as an Active Directory server) to be performed inside the enterprise.
Credential checking for both SIP Digest and NTLM messages may be delegated.
All messages must be for locally-defined SIP domains. You can delegate credential checking to different
traversal clients on a per domain basis if required.
The following diagram shows how incoming SIP messages (calls, registrations and so on) are challenged by the VCS
Expressway, but the checking of the credentials presented in response to those challenges is delegated to the VCS
Control.
Configuring Your Video Communications Network for Delegated Credential Checking

Several configuration steps are involved, on both your VCS Expressway and your VCS Control, in setting up your
video network for delegated credential checking.
It is likely that much of this configuration, such as the set of local SIP domains, will already be in place, however the
sections below list all of the necessary configuration requirements.
VCS Expressway and VCS Control
There must be a secure traversal zone connection between the VCS Control and the VCS Expressway:
The VCS Control and VCS Expressway must be configured with a zone of type Unified Communications
traversal. This automatically configures an appropriate traversal zone (a traversal client zone when selected
on a VCS Control, or a traversal server zone when selected on a VCS Expressway) that uses SIP TLS with TLS
verify mode set to On, and Media encryption mode set to Force encrypted.
Both VCSs must trust each other's server certificate. As each VCS acts both as a client and as a server you
must ensure that each VCSs certificate is valid both as a client and as a server.
If an H.323 or a non-encrypted connection is also required, a separate pair of traversal zones must be
configured.
115
VCS Control
1. Configure SIP domains (Configuration > Domains).

It must be configured with all of the domains for which it will receive delegated authentication checks.
2. Configure the relevant authentication mechanisms (local database, Active Directory Service or H.350
directory via LDAP).
3. Enable Delegated credential checking (Configuration > Protocols > SIP).
4. Ensure that the traversal client zone is configured to Accept delegated credential checks.
VCS Expressway
1. Configure SIP domains (Configuration > Domains).

It must be configured with all of the domains for which it will delegate authentication checks.
2. For each domain, choose the traversal zone over which the credential checks are to be delegated.
3. If NTLM / Active Directory Service authentication is required, ensure that NTLM protocol challenges
(Configuration > Authentication > Devices > Active Directory Service) is set to Auto.
4. Enable Delegated credential checking on the SIP page (Configuration > Protocols > SIP).
5. Ensure that the relevant zone and subzone authentication policies are set to Check credentials.
Note that any H.323 messages that arrive at the zones or subzones that are now configured to Check
credentials will still have those credentials checked via the relevant mechanisms (such as the local database
or H.350 directory) on that local VCS and they will not be delegated.
6. If required as part of your dial plan, configure search rules that forward SIP call signaling messages to the
relevant traversal client zones.
(Note that no specific search rules are required to support the delegation of authentication messages to the
VCS Control.
The credential checking of authentication challenges made by the VCS Expressway should now be delegated
through the traversal zone to the VCS Control.
Testing the credential checking service
To verify whether the VCS to which credential checking has been delegated is able to receive messages and perform
the relevant authentication checks:
1. Go to Configuration > Domains.

2. Select the relevant domains.
3. Click Test credential checking service.
The system displays a Results section and reports whether the receiving VCS can be reached over the
traversal zone and, additionally, if it is able to perform credential checking for both NTLM and SIP digest type
challenges.
If you are not using NTLM authentication in your video network, and thus the receiving VCS is not configured
with a connection to an Active Directory Service, then the NTLM check will be expected to fail.
TURN services
If TURN services are enabled on the VCS Expressway and you also want to delegate the credential checking of TURN
server requests:
1. Go to Configuration > Traversal > TURN.

2. Set Delegated credential checking to On.
3. For the Authentication realm, choose from the set of configured SIP domains to determine the traversal zone
through which credential checking is delegated.
116
Additional information
The system clocks on the VCS Control and the VCS Expressway must be within 100 seconds of each other.
We recommend that all VCSs are configured to use a common NTPserver.
The VCS Expressway can still perform "local" non-delegated authentication for specific domains. If this is
required, ensure that:
Those domains have Traversal zone for delegated credential checking set to Do not delegate.
The relevant authentication mechanisms are configured on the VCS Expressway.
The VCS Control can still perform authentication in the normal manner, as well as providing a delegated
credential checking service for the VCS Expressway. Note that:
The NTLM protocol challenges setting on the VCS Control only applies if the VCS Control itself is making
an authentication challenge.
The authentication policy configuration on the traversal client on the VCS Control has no effect on the
delegated credential checking requests received by the VCS Control.
Enabling delegated credential checking does not affect any other message routing; there is no need to amend
any existing transforms, search rules and so on.
117
Device Provisioning and Authentication Policy

The following diagram shows the flow of provisioning messages from an endpoint to the Provisioning Server, together
with the credential checking processes:
The VCS must be configured with appropriate device authentication settings, otherwise provisioning-related
messages will be rejected:
Initial provisioning authentication (of a subscribe message) is controlled by the authentication policy setting
on the Default Zone. (The Default Zone is used as the device is not yet registered.)
The Default Zone and any traversal client zone's authentication policy must be set to either Check credentials
or Treat as authenticated, otherwise provisioning requests will fail.
The authentication of subsequent messages, including registration requests, phone book requests and call
signaling messages is controlled by the authentication policy setting on the Default Subzone (or relevant
alternative subzone) if the endpoint is registered (which is the usual case), or by the authentication policy
setting on the Default Zone if the endpoint is not registered.
The relevant authentication policy must be set to either Check credentials or Treat as authenticated,
otherwise phone book requests will fail.
In each case, the VCS performs its authentication checking against the appropriate credential store, according to
whichever authentication methods are configured. Note that if the VCS is using the local database, this will include
all credentials supplied by Cisco TMS.
For more information about provisioning configuration in general, see Cisco TMS Provisioning Extension Deployment
Guide.
118
VCS Starter Pack Express

The Provisioning Server on a VCS Starter Pack Express operates in the same manner as when using Cisco TMS
provisioning it does not challenge provisioning requests. It provisions devices only if the request has already been
authenticated by the VCS (at the zone or subzone entry point).
119
Presence and Authentication Policy

status.
The following diagram shows the flow of presence messages from an endpoint to the Presence Server:
In each case, the VCS performs its authentication checking against the appropriate credential store, according to
whichever authentication methods are configured. Note that if the VCS is using the local database, this will include
any credentials supplied by Cisco TMS.
120
Hierarchical Dial Plans and Authentication Policy

Hierarchical dial plan (directory VCS) deployments and device authentication
When introducing authentication into video networks which have a hierarchical dial plan with a directory VCS,
authentication problems can occur if:
any VCS in the network uses a different authentication database from any other VCS in the network, and
credential checking is enabled on the Default Zone of any VCS (as is needed, for example, when using Cisco
TMSPE), and
the directory VCS or any other VCS in a signaling path can optimize itself out of the call routing path
In such deployments, each VCS must be configured with a neighbor zone between itself and every other VCS in the
network. Each zone must be configured with an Authentication policy of Do not check credentials. (No search rules
are required for these neighbor zones; the zones purely provide a mechanism for trusting messages between VCSs.)
This is required because, otherwise, some messages such as SIP RE-INVITES, which are sent directly between VCSs
(due to optimal call routing), will be categorized as coming from the Default Zone. The VCS will then attempt to
authenticate the message and this may fail as it may not have the necessary credentials in its authentication
database. This means that the message will be rejected and the call may be dropped. However, if the node VCSs
have a neighbor zone relationship then the message will be identified as coming through that neighbor zone, the VCS
will not perform any credential checking (as the neighbor zone is set to Do not check credentials) and the message
will be accepted.
Deployments with multiple regional / subnetwork directory VCSs
If your deployment is segmented into multiple regional subnetworks, each with their own directory VCS, it is not
feasible (or recommended) to set up neighbor zones between each and every VCS across the entire network.
In this scenario you should configure each subnetwork as described above i.e. set up neighbor zones between each
of the VCSs managed by the same directory VCS and then configure the neighbor zones between each directory
VCS so that they stay in the call signaling path on calls crossing subnetworks between those directory VCSs. To do
this:
1. On the directory VCS, go to Configuration > Zones > Zones and then click on the relevant zone to the other
directory VCS.
2. On the Edit zones page, scroll down to the Advanced section and set Zone profile to Custom.
3. Set Call signaling routed mode to Always.
4. Click Save.
5. Repeat this for the equivalent zone definition on the other directory VCS, and then repeat the entire process
for any other zone configurations between any other directory VCSs.
Note: do not modify the directory VCSs primary Call signaling routed mode setting on the Calls page.
This means that the each directory VCS will stay in the call signaling path for calls that go between subnetworks.
Each directory VCS will still be able to optimize itself out of the call signaling path for calls entirely within each
subnetwork.
You must also ensure that you have sufficient call licenses (traversal and non-traversal) on each directory VCS to
handle those calls going between each subnetwork.
121
Practical Configuration of Authentication Policy

VCS Control
The table below contains practical guidelines for configuring authentication policy on a VCS Control.
Authentication point Guideline
Default Zone Use Check credentials.
Default Subzone Use Check credentials.
Specific local subzones For known local subnets, to avoid having to configure all local endpoints
with credentials, use Treat as authenticated.
Although this is a practical solution, we recommend that no Treat as

authenticated subzones are used, and that every endpoint is populated with
appropriate and unique credentials and that Check credentials is used.
Other subzones Use Check credentials.
Traversal zone Use Check credentials. Always check the credentials of requests coming
from the VCS Expressway.
Neighbor zone Use Do not check credentials and set SIP authentication trust mode to On.
VCS Expressway
Ideally, VCS Expressway authentication policy, should follow exactly the same guidelines as for the VCS Control.
However if AD Direct or H.350 access is required, many security policies will not allow a device in a DMZ access to
those resources. Practicality therefore recommends that authentication is left to the VCS Control. For SIP devices
you can use delegated credential checking; this allows SIP devices to register to the VCS Expressway but be
authenticated via a device authentication mechanism configured on the VCS Control.
You can also use registration allow and deny lists to limit what can register to the VCS Expressway. If it is required
that outbound calls may only be made by authenticated users, ensure that all call requests are routed to the VCS
Control and it only forwards requests back that it can authenticate.
Infrastructure devices
You are recommended to configure your VCS so that infrastructure products, such as MCUs, register to a dedicated
subzone with an authentication policy set to Treat as authenticated.
Configuring VCS Authentication Methods

The VCS supports 3 different methods of verifying authentication credentials:
against an on-box local database (which includes any Cisco TMS-supplied credentials)
via an LDAP connection to an external H.350 directory service
via direct access to an Active Directory server using a Kerberos connection (NTLM challenges only)
The VCS attempts to verify the credentials presented to it by first checking against its on-box local database of
usernames and passwords. The local database also includes checking against credentials supplied by Cisco TMS if
your system is using device provisioning. If the username is not found in the local database, the VCS may then
attempt to verify the credentials via a real-time LDAP connection to an external H.350 directory service. The directory
service, if configured, must have an H.350 directory schema for either a Microsoft Active Directory LDAP server or an
OpenLDAP server.
Along with one of the above methods, for those devices that support NTLM challenges, the VCS can alternatively
verify credentials via direct access to an Active Directory server using a Kerberos connection. The direct Active
Directory authentication via Kerberos method is only supported by a limited range of endpoints at the time of writing,
122
only Cisco Jabber for iPad and Jabber Video. If used, other non-supported endpoint devices will continue to
authenticate using one of the other two authentication methods.
Note that the VCS always challenges an endpoint with a standard Digest challenge. The VCS will additionally send
an NTLM challenge if the VCS has NTLM protocol challenges enabled and it recognizes that the endpoint supports
NTLM.
If the endpoint receives both challenges, it is the endpoint's decision as to whether to respond to the Digest challenge
or to the NTLM challenge. At the time of writing, all supported endpoints respond to an NTLM challenge in preference
to a Digest challenge.
The following diagram shows the process followed by the VCS when authenticating credentials:

Note that accurate timestamps play an important part in authentication of H.323 devices, helping to guard against
replay attacks. For this reason, if you are using device authentication with H.323 devices, both the VCS and the
endpoints must use an NTP server to synchronize their system time.
Authentication Mechanism
The authentication process uses a username and password-based challenge-response scheme to check a device's
credentials.
The actual mechanism used by the device to supply its credentials to the VCS depends on the protocol being used:
H.323: any necessary credentials are contained within the incoming request. (The VCS supports the ITU H.235
specification for authenticating the identity of H.323 network devices with which it communicates.)
SIP: credentials are not contained within the initial request. Instead the VCS sends a challenge back to the
sender that asks for its credentials. However, if a SIPmessage has already been authenticated (for example by
another VCS on a previous hop), that system may insert information into the SIP message to show that it has
been authenticated. You can control whether the VCS chooses to trust any authentication carried out at an
earlier stage by configuring a zone's SIP authentication trust setting.
Note that if the VCS is acting as a traversal server, you must ensure that each traversal clients authentication
credentials are entered into the selected database.
Endpoint Credentials Used for Authentication

An endpoint must supply the VCS with a username and password if it is required to authenticate with the VCS, for
example when attempting to register and the relevant subzone's Authentication policy is set to Check credentials.
123
For Cisco endpoints using H.323, the username is typically the endpoints Authentication ID; for Cisco endpoints
using SIP it is typically the endpoints Authentication username.
See the relevant endpoint manual for details about how to configure the endpoint's credentials.
124
Configuring Authentication to Use the Local Database

The local authentication database is included as part of your VCS system and does not require any specific
connectivity configuration. It is used to store user account authentication credentials. Each set of credentials
consists of a name and password.
The credentials in the local database can be used for device (SIP and H.323), traversal client and TURN client
authentication.
Adding credentials to the local database
To enter a set of device credentials:
1. Go to Configuration > Authentication > Devices > Local database and click New.
2. Enter the Name and Password that represent the devices credentials.
3. Click Create credential.
Note that the same credentials can be used by more than one device.
Credentials managed within Cisco TMS (for device provisioning)
When the VCS is using TMS Provisioning Extension services, the credentials supplied by the Users service are stored
in the local authentication database, along with any manually configured entries. The Source column identifies
whether the user account name is provided by TMS, or is a Local entry. Only Local entries can be edited.
Incorporating Cisco TMS credentials within the local database means that VCS can authenticate all messages (i.e.
not just provisioning requests) against the same set of credentials used within Cisco TMS.
Local database authentication in combination with H.350 directory authentication
You can configure the VCS to use both the local database and an H.350 directory.
If an H.350 directory is configured, the VCS will always attempt to verify any Digest credentials presented to it by first
checking against the local database before checking against the H.350 directory.
Local database authentication in combination with Active Directory (direct) authentication
If Active Directory (direct) authentication has been configured and NTLM protocol challenges is set to Auto, then
NTLM authentication challenges are offered to those devices that support NTLM.
NTLM challenges are offered in addition to the standard Digest challenge.

Endpoints that support NTLM will respond to the NTLM challenge in preference to the Digest challenge, and
the VCS will attempt to authenticate that NTLM response.
Starter Pack
If the Starter Pack option key is installed, the local authentication database will include a pre-configured set of
authentication credentials. To ensure correct operation of the TURN server in conjunction with the Starter Pack, do
not delete or modify the StarterPackTURNUser entry in the local authentication database.
All other credentials that are required to support Starter Pack provisioned devices have to be added manually for each
user account.
125
Using an H.350 Directory Service Lookup via LDAP

The Device authentication H.350 configuration page (Configuration > Authentication > Devices > H.350 directory
service) is used to configure a connection via LDAP to an H.350 directory service. An H.350 directory service lookup
can be used for authenticating any endpoint, SIP and H.323.
H.350 directory authentication and registration process
If the VCS is using an H.350 directory service to authenticate registration requests, the process is as follows:
1. The endpoint presents its username and authentication credentials to the VCS, and the aliases with which it
wants to register.
2. The VCS then determines which aliases the endpoint is allowed to attempt to register with, based on the
Source of aliases for registration setting. For H.323 endpoints, you can use this setting to override the
aliases presented by the endpoint with those in the H.350 directory, or you can use them in addition to the
endpoints aliases. For SIP endpoints, you can use this setting to reject a registration if the endpoints AOR
does not match that in the H.350 directory. The options are:
H.350 directory: for SIP registrations the AOR presented by the endpoint is registered providing it is listed in
the H.350 directory for the endpoint's username.
For H.323 registrations:
At least one of the aliases presented by the endpoint must be listed in the H.350 directory for that
endpoint's username. If none of the presented aliases are listed it is not allowed to register.
The endpoint will register with all of the aliases (up to a maximum of 20) listed in the H.350 directory.
Aliases presented by the endpoint that are not in the H.350 directory will not be registered.
If no aliases are listed in the H.350 directory, the endpoint will register with all the aliases it presented.
If no aliases are presented by the endpoint, it will register with all the aliases listed in the H.350 directory
for its username.
Combined: the aliases presented by the endpoint are used in addition to any listed in the H.350 directory for
the endpoints username. In other words, this is the same as for H.350 directory, except that if an endpoint
presents an alias that is not in the H.350 directory, it will be allowed to register with that alias.
Endpoint: the aliases presented by the endpoint are used; any in the H.350 directory are ignored. If no
aliases are presented by the endpoint, it is not allowed to register.
The default is H.350 directory.
Note that if the authentication policy is Do not check credentials or Treat as authenticated, then the Source of
aliases for registration setting is ignored and the aliases presented by the endpoint are used.
Configuring the LDAP server directory
The H.350 directory on the LDAP server should be configured to implement the ITU H.350 specification. It should store
credentials for devices with which the VCS communicates, and the aliases of endpoints that will register with the
VCS.
1. Download the required H.350 schemas from the VCS (Configuration > Authentication > Devices > H.350
directory schemas) and install them on the LDAP server.
2. Configure the directory with the aliases of endpoints that will register with the VCS.
See LDAP Server Configuration for Device Authentication, page 357 for instructions on configuring LDAP
servers.
Configuring the LDAP server settings
1. Go to Configuration > Authentication > Devices > H.350 directory service.
126
H.350 device Enables or disables the use of an H.350 The H.350 directory can be used in
authentication directory for device authentication. combination with other authentication
mechanisms.
Source of Determines how aliases are checked and See H.350 directory authentication and
aliases for registered. registration process above for a
registration description of each setting.
When Source of aliases for registration is

H.350 directory, MCUs are treated as a
special case. They register with the
presented aliases and ignore any aliases in
the H.350 directory. (This is to allow MCUs
to additively register aliases for
conferences.)
Server The IP address or FQDN (or server address, if The LDAP server must have the H.350
address a DNS Domain name has also been schemas installed.
configured) of the LDAP server.
If using TLS, the address entered here must
match the CN (common name) contained
within the certificate presented by the LDAP
server.
FQDN Defines how the LDAP Server address is DNSSRV lookups enable the VCS to
address resolved if it is specified as an FQDN. authenticate devices against multiple
resolution remote H.350 directory servers. This
Address record: DNS A or AAAA record provides a seamless redundancy
lookup. mechanism in the event of reachability
problems to an H.350 directory server.
SRV record: DNS SRV record lookup.
The SRV lookup is for either _ldap._tcp or _
The default is Address record. ldaps._tcp records, depending on whether
Encryption is enabled. If multiple servers are
Note:if you use SRVrecords, ensure that the returned, the priority and weight of each
records use the standard ports for LDAP. _
SRV record determines the order in which
ldap._tcp.<domain> must use 389 and _
the servers are used.
ldaps._tcp.<domain> must use 636. The VCS
does not support other port numbers for
LDAP.
Port The IP port of the LDAP server. Non-secure connections use 389 and
secure connections use 636.
Encryption Determines whether the connection to the When TLS is enabled, the LDAP servers
LDAP server is encrypted using Transport certificate must be signed by an authority
Layer Security (TLS). within the VCSs trusted CA certificates file.
TLS: uses TLS encryption for the connection Click Upload a CA certificate file for TLS
to the LDAP server. (in the Related tasks section) to go to the
Managing the Trusted CA Certificate List,
Off: no encryption is used. page 282 page.
The default is TLS.
127
Bind DN The user distinguished name used by the For example, uid=admin, ou=system
VCS when binding to the LDAP server.
Bind The password used by the VCS when

password binding to the LDAP server.
Base DN for The area of the directory on the LDAP server For example, ou=H350,dc=example,dc=com
devices to search for credential information. This
should be specified as the Distinguished
Name (DN) in the LDAP directory under
which the H.350 objects reside.
3. Click Save.
The current status of the connection to the specified LDAP server is displayed at the bottom of the page.
Using an H.350 Directory with Other Authentication Mechanisms

Local database authentication in combination with H.350 directory authentication
You can configure the VCS to use both the local database and an H.350 directory.
If an H.350 directory is configured, the VCS will always attempt to verify any Digest credentials presented to it by first
checking against the local database before checking against the H.350 directory.
H.350 directory service authentication in combination with Active Directory (direct) authentication
NTLM authentication challenges are offered to those devices that support NTLM. Devices that do not support NTLM
will continue to receive a standard Digest challenge.
128
Using Active Directory Database (Direct)

Active Directory database (direct) authentication uses NTLM protocol challenges and authenticates credentials via
direct access to an Active Directory server using a Kerberos connection.
It can be enabled at the same time as local database and H.350 directory service authentication. This is because
NTLM authentication is only supported by certain endpoints. Therefore, for example, you could use the Active
Directory (direct) server method for Jabber Video, and the local database or H.350 directory service authentication for
the other devices that do not support NTLM.
NTLM authentication challenges are offered to those devices that support NTLM. Devices that do not support NTLM
will continue to receive a standard Digest challenge.
Note that the VCS embeds NTLMv2 authentication protocol messages within standard SIP messages when
communicating with endpoint devices, and uses a secure RPC channel when communicating with the AD Domain
Controller. Users' Windows domain credentials and the AD domain administrator credentials are not stored on the
VCS.
Configuration Prerequisites
Active Directory
A username and password of an AD user account with either account operator or administrator access
rights must be available for the VCS to use for joining and leaving the domain.
Entries must exist in the Active Directory server for all devices that are to be authenticated through this
method. Each entry must have an associated password.
The device entries (in all domains) must be accessible by the user account that is used by VCS to join the
domain. If the VCS is in a domain that is part of a forest, and there is trust between domains in the forest, the
VCS can authenticate device entries from different domains providing the user account has appropriate rights
to authenticate devices against the other domains.
Kerberos Key Distribution Center
The KDC (Kerberos Key Distribution Center) server must be synchronized to a time server.
DNS server
If a DNS name or DNS SRV name is used to identify the AD servers, a DNS server must be configured with the relevant
details. (Note that the VCS must be configured to use a DNS server even if you are not using DNS / DNS SRV to
specify the AD servers.)
VCS
The VCS must be configured to use a DNS server (System > DNS).
The VCSs System host name (System > DNS) must be 15 or fewer characters long.
(Microsoft NetBIOS names are capped at 15 characters.)
When part of a cluster, ensure that each VCS peer has a unique System host name.
Ensure that an NTP server (System > Time) has been configured and is active.
If the connection is going to use TLS encryption, a valid CA certificate, private key and server certificate must
be uploaded to the VCS.
The VCS must be configured to challenge for authentication on the relevant zones and subzones:
The Default Zone (Configuration > Zones > Zones, then select Default Zone) must be configured with an
Authentication policy of Check credentials. This ensures that provisioning requests (and any call requests
from non-registered devices) are challenged.
The Default Subzone (Configuration > Local Zone > Default Subzone) or the relevant subzones - must be
configured with an Authentication policy of Check credentials. This ensures that registration, presence,
phone book and call requests from registered devices are challenged.
129
Setting up your authentication policy to check credentials will affect any device that sends provisioning,
registration, presence, phone book and call requests to the VCS.
Endpoint
The PC on which Jabber Video runs must use settings which match the settings of the AD server.
Configuring the Connection to Active Directory Service (ADS)

The Active Directory Service page (Configuration > Authentication > Devices > Active Directory Service) is used to
configure a connection to an Active Directory Service for device authentication of Jabber Video endpoints (version
4.2 or later).
Configuring the Active Directory Service Settings

To configure Active Directory (direct) and join the AD domain:
1. Go to Configuration > Authentication > Devices > Active Directory Service.

Connect to Enables or disables the connection between Turning Connect to Active Directory Service
Active the VCS and the Active Directory Service. to Off does not cause the VCS to leave the
Directory AD domain.
Service When the connection is enabled, the VCS
includes NTLM protocol challenges when
authenticating endpoints, according to the
NTLM protocol challenges setting.
NTLM Controls whether or not the VCS sends NTLM Normally, this should be set to Auto.
protocol protocol challenges (in addition to Digest
challenges challenges) when authenticating devices If you are migrating from an existing
over SIP. authentication mechanism to ADS then select
Off while the connection to the AD server is
Auto: the VCS decides, based on the device being configured; select Auto later, when you
type, whether to send NTLM challenges. have an active connection and are ready to
switch over to this authentication
Off: NTLM challenges are never sent. mechanism.
On: NTLM challenges are always sent. Never use On, as this will send NTLM
challenges to devices that may not support
The default is Auto. NTLM (and therefore they may crash or
otherwise misbehave).
The VCS must be connected to an Active

Directory Service to send NTLM challenges.
AD domain This must be the fully qualified domain name Typically the domain is the same as the DNS
(FQDN) of the AD domain that the VCS will name of the Kerberos server.
join. It must be entered in upper case, such
as, EXAMPLE.COM. Upper case entry is enforced due to case
sensitivity issues with Active Directory.
Short The short domain name used by the VCS It is also known as the NetBIOS domain
domain when it joins the AD domain. name.
name
130
NetBIOS By default the system uses the System host An override must be specified if the System
machine name as the NetBIOS machine name when host name exceeds 15 characters.
name joining the AD domain. If required, you can
(override) enter a different name here to override the
default name.
Secure Indicates if data transmitted from the VCS to You are recommended to use Auto.
channel an AD Domain Controller is sent over a secure
mode channel.
Auto: automatically adapts to the domain

controller's settings.
Enabled: always attempts to use a secure

channel.
Disabled: does not use a secure channel.
The default is Auto.
Encryption Sets the encryption to use for the LDAP If encryption is set to TLS, a valid CA
connection to the Active DirectoryService. certificate, private key and server certificate
must be uploaded to the VCS.
Click Upload a CA certificate file for TLS (in
TLS: TLS encryption is used. the Related tasks section) to go to the
Managing the Trusted CA Certificate List,
The default is TLS. page 282 page.
Clockskew The maximum allowed clockskew (in It should be kept in step with the clock skew
seconds) between the VCS and the KDC setting on the KDC.
before the Kerberos message is assumed to
be invalid. Ensure that VCS and KDC are synchronized
to time servers.
The default is 300 seconds.
Use DNS Yes is the recommended setting. This means

SRV lookup that VCS will use a DNS SRV lookup of the AD
to obtain domain to obtain the address details of the
Domain AD domain controllers.
Controller
addresses If the lookup cannot provide the addresses
then set this field to No and enter the IP
address of the primary Domain Controller into
the Address 1 field that will be displayed.
131
Use DNS Yes is the recommended setting. This means Typically, the KDC addresses are the same as
SRV lookup that VCS will use a DNS SRV lookup of the AD the Domain Controller addresses.
to obtain domain to obtain the address details of the
Kerberos Kerberos Key Distribution Center servers.
Key
Distribution If the lookup cannot provide the addresses
Center then set this field to No and enter the IP
addresses address of the primary Key Distribution Center
servers into the Address 1 field that will be
displayed. Typically, Port 1 can be left as its
default value of 88.
Username The AD domain administrator username and The domain administrator's credentials are
and password. The password is case sensitive. required only when you attempt to join a
Password domain. The VCS only needs to join the
domain once, after which the connection can
be enabled or disabled as required.
3. Click Save to store the configuration and join the AD domain.

The VCS should join the AD domain. If you receive an error message, check the following:
the configuration settings on this page, including the username and password
the VCSs CA certificate, private key and server certificate
the Status area at the bottom of the Active Directory Service page for more information about the status of
the connection to the AD domain
Note that:
The domain administrator username and password are not stored in VCS; they are only required to join an AD
domain (or to leave a domain).
The VCS only needs to join the AD domain once, even if the connection to the Active Directory Service is
disabled and turned back on again. The only time a join is needed again is if the VCS leaves the domain or
needs to join a different domain.
Adding non-primary Domain Controllers and Kerberos Key Distribution Center servers (optional)
This procedure is only required if you are not using DNS SRV lookups of the AD domain to obtain the address details
of the Domain Controller servers and the Kerberos Key Distribution Center servers.

2. Enter up to 4 further Domain Controller server addresses (up to 5 in total).
3. Enter up to 4 further Kerberos Key Distribution Center server addresses and port numbers (up to 5 in total).
4. Click Save.
5. If the VCS is part of a cluster, check that the configuration entered on the master peer has been replicated to
each other peer.
Clustered VCS Systems

In a clustered system, each VCS must join the AD domain separately. To do this:
On the master peer:
1. Follow the instructions as above to configure Active Directory (direct) and join the AD domain.
2. Ensure that the master peer has successfully joined the AD domain before continuing.
132
On each other peer in turn:

2. Check that the configuration entered on the master peer has been replicated to the current peer.
3. Enter the AD domain administrator Username and Password.
(These credentials are not stored by the VCS and so have to be entered each time.)
4. Click Save.
The VCS should join the AD domain. If you receive an error message, check the following:
the configuration settings on this page, including the username and password
the VCSs CA certificate, private key and server certificate (CA certificate information is not replicated
across cluster peers)
Enabling NTLM Authentication Challenges

When Active Directory details have been configured and the VCS has been joined into the AD domain, VCS can now
be configured to challenge Jabber Video (4.2 or later) with NTLM authentication challenges.

2. Ensure that NTLM protocol challenges is set to Auto.
Never use On, as this will send NTLM challenges to devices that may not support NTLM (and therefore they
may crash or otherwise misbehave).
3. Click Save if required.
4. If the VCS is part of a cluster, check that any configuration changes entered on the master peer have been
replicated to each other peer.
Configuring Jabber Video and Testing Active Directory Database (Direct) Authentication
We recommend that you use a Jabber Video configuration that already authenticates successfully using either
provisioning or VCS authentication. This means that Jabber Video's Advanced settings (Internal Server, External
Server and SIP Domain entries) are correctly configured.
1. Sign in to Jabber Video:

2. In the Username field, configure <AD Short Domain Name>\username
(this field is not case sensitive).
3. In the Password field, enter the password as configured in the Active Directory database for the chosen user.
4. Click Sign in.
A successful registration confirms that authentication of provisioning and registration of Jabber Video to VCS now
works using Active Directory database (direct) authentication.
Ports
See Device Authentication Port Reference, page 376 for a list of ports used when communicating with the AD system.
SPNEGO
SPNEGO (Simple and Protected GSSAPI Negotiation Mechanism) is a mechanism used by client applications when
they seek to authenticate with a remote server. It allows the client and server to identify which authentication
protocols they both support and decide which protocol to use.
By default the VCS uses SPNEGO when communicating with an AD Domain Controller. It can only be enabled or
disabled through the CLI by using the command xConfiguration Authentication ADS SPNEGO.
133
Authenticating with External Systems

The Outbound connection credentials page (Configuration > Authentication > Outbound connection credentials) is
used to configure a username and password that the VCS will use whenever it is required to authenticate with
external systems.
For example, when the VCS is forwarding an invite from an endpoint to another VCS, that other system may have
authentication enabled and will therefore require your local VCS to provide it with a username and password.
Note that these settings are not used by traversal client zones. Traversal clients, which must always authenticate
with traversal servers before they can connect, configure their connection credentials per traversal client zone.
134
135
Zones and Neighbors
This section describes how to configure zones and neighbors on the VCS (Configuration > Zones).
About your Video Communications Network 136

Structuring your Dial Plan 137
About Zones 138
Configuring Media Encryption Policy 139
Configuring ICE Messaging Support 140
About the Local Zone and Subzones 141
The Default Zone 142
Configuring Default Zone access rules 143
Configuring Zones 143
About your Video Communications Network

The most basic implementation of a video communications network is a single VCS connected to the internet with
one or more endpoints registered to it. However, depending on the size and complexity of your enterprise the VCS
may be part of a network of endpoints, other VCSs and other network infrastructure devices, with one or more
firewalls between it and the internet. In such situations you may want to apply restrictions to the amount of bandwidth
used by and between different parts of your network.
This section provides an overview of the different parts of the video communications network and the ways in which
they can be connected. This information should allow you to configure your VCS to best suit your own infrastructure.
Example network diagram
The diagram below shows the different components of a VCS (i.e. subzones and zones) and how they interrelate.
Using a VCS Control as the example Local Zone, it shows that it is made up of a number of subzones which are all
connected by links. The Local Zone is also connected to external VCSs and to the internet via different types of
zones.
All these components are described in more detail in the sections that follow.
136
Structuring your Dial Plan

As you start deploying more than one VCS, it is useful to neighbor the systems together so that they can query each
other about their registered endpoints. Before you start, you should consider how you will structure your dial plan.
This will determine the aliases assigned to the endpoints, and the way in which the VCSs are neighbored together.
The solution you choose will depend on the complexity of your system. Some possible options are described in the
following sections.
Flat Dial Plan

The simplest approach is to assign each endpoint a unique alias and divide the endpoint registrations between the
VCSs. Each VCS is then configured with all the other VCS as neighbor zones. When one VCS receives a call for an
endpoint which is not registered with it, it will send out a Location Request to all the other neighbor VCSs.
While conceptually simple, this sort of flat dial plan does not scale very well. Adding or moving a VCS requires
changing the configuration of every VCS, and one call attempt can result in a large number of location requests. This
option is therefore most suitable for a deployment with just one or two VCSs plus its peers.
Structured Dial Plan

An alternative deployment would use a structured dial plan where endpoints are assigned an alias based on the
system they are registering with.
If you are using E.164 aliases, each VCS would be assigned an area code. When the VCSs are neighbored together,
each neighbor zone would have an associated search rule configured with its corresponding area code as a prefix (a
Mode of Alias pattern match and a Pattern type of Prefix). That neighbor would then only be queried for calls to
numbers which begin with its prefix.
In a URI based dial plan, similar behavior may be obtained by configuring search rules for each neighbor with a suffix
to match the desired domain name.
It may be desirable to have endpoints register with just the subscriber number the last part of the E.164 number. In
that case, the search rule could be configured to strip prefixes before sending the query to that zone.
137
A structured dial plan minimizes the number of queries issued when a call is attempted. However, it still requires a
fully connected mesh of all VCSs in your deployment. A hierarchical dial plan can simplify this.
Hierarchical dial plan

In this type of structure one VCS is nominated as the central directory VCS for the deployment, and all other VCSs are
neighbored with it alone.
The directory VCS is configured with:
each VCS as a neighbor zone

search rules for each zone that have a Mode of Alias pattern match and the target VCS's prefix (as with the
structured dial plan) as the Pattern string
Each VCS is configured with:
the directory VCS as a neighbor zone

a search rule with a Mode of Any alias and a Target of the directory VCS
There is no need to neighbor every VCS with each other. Adding a new VCS now only requires changing
configuration on the new VCS and the directory VCS. However, note that it may be necessary to neighbor your VCSs
to each other if you are using device authentication see below for more information.
Also, failure of the directory VCS in this situation could cause significant disruption to communications.
Consideration should be given to the use of clustering for increased resilience.
H.323 calls and optimal call routing
For H.323 calls, if Optimal call routing is enabled you must ensure that all search rules are configured with a Source
of Any. If the Source is configured to All zones, H.323 calls will fail to connect. This is because the H.323 SETUP
message, having followed the optimized route established by the original LRQ or ARQ, will appear to the target VCS
as coming from an unknown zone. SIP calls, however, are successfully routed if the search rule Source is All zones
(because in SIP the search and call setup is combined into one message).
Hierarchical dial plan (directory VCS) deployments and device authentication
See Hierarchical Dial Plans and Authentication Policy, page 121 for important information about how to configure
your authentication policy within a hierarchical dial plan.
About Zones
A zone is a collection of endpoints, either all registered to a single system or located in a certain way such as via an
ENUM or DNS lookup. Zones are used to:
control through links whether calls can be made between your local subzones and these other zones
manage the bandwidth of calls between your local subzones and endpoints in other zones
search for aliases that are not registered locally
control the services available to endpoints within that zone by setting up its authentication policy
control the media encryption and ICE capabilities for SIP calls to and from a zone
You can configure up to 1000 zones. Each zone is configured as one of the following zone types:
Neighbor: a connection to a neighbor system of the local VCS.

Traversal client: the local VCS is a traversal client of the system being connected to, and there is a firewall
between the two.
Traversal server: the local VCS is a traversal server for the system being connected to, and there is a firewall
between the two.
ENUM: the zone contains endpoints discoverable by ENUM lookup.
138
DNS: the zone contains endpoints discoverable by DNS lookup.

Unified Communications traversal: a traversal client or traversal server zone used for Unified Communications
features such as mobile and remote access or Jabber Guest. Note that this zone type applies to the web
interface only; the underlying CLI configuration uses traversal client and traversal server zone types.
The VCS also has a pre-configured Default Zone.
See the Zone configuration section for information about the configuration options available for all zone types.
See the Configuring search and zone transform rules section for information about including zones as targets
for search rules.
Automatically generated neighbor zones
The VCS may automatically generate some non-configurable neighbor zones:
A VCS Control automatically generates neighbor zones between itself and each discovered Unified CM node
when the system is configured for mobile and remote access.
A VCS automatically generates a neighbor zone named "To Microsoft Lync server via B2BUA" when the Lync
B2BUA is enabled.
Configuring Media Encryption Policy

The media encryption policy settings allow you to selectively add or remove media encryption capabilities for SIP calls
flowing through the VCS. This allows you to configure your system so that, for example, all traffic arriving or leaving a
VCS Expressway from the public internet is encrypted, but is unencrypted when in your private network.
The policy is configured on a per zone/subzone basis and applies only to that leg of the call in/out of that
zone/subzone.
Encryption is applied to the SIP leg of the call, even if other legs are H.323.
Media encryption policy is configured through the Media encryption mode setting on each zone and subzone,
however the resulting encryption status of the call is also dependent on the encryption policy settings of the target
system (such as an endpoint or another VCS).
The encryption mode options are:
Force encrypted: all media to and from the zone/subzone must be encrypted. If the target system/endpoint is
configured to not use encryption, then the call will be dropped.
Force unencrypted: all media must be unencrypted. If the target system/endpoint is configured to use
encryption, then the call may be dropped; if it is configured to use Best effort then the call will fall back to
unencrypted media.
Best effort: use encryption if available, otherwise fall back to unencrypted media.
Auto: no specific media encryption policy is applied by the VCS. Media encryption is purely dependent on the
target system/endpoint requests. This is the default behavior and is equivalent to how the VCS operated
before this feature was introduced.
Encryption policy (any encryption setting other than Auto) is applied to a call by routing it through a back-to-back user
agent (B2BUA) hosted on the VCS.
When configuring your system to use media encryption you should note that:
Any zone with an encryption mode of Force encrypted or Force unencrypted must be configured as a SIP-only
zone (H.323 must be disabled on that zone).
TLS transport must be enabled if an encryption mode of Force encrypted or Best effort is required.
The call component routed through the B2BUA can be identified in the call history details as having a
component type of B2BUA.
139
As the B2BUA must take the media, each call is classified as a traversal call and thus consumes a traversal
call license.
There is a limit per VCS of 100 simultaneous calls (500 calls on Large systems) that can have a media
encryption policy applied.
The B2BUA can also be invoked when ICE messaging support is enabled.
Configuring the B2BUA for Media Encryption

The B2BUA used for encryption (and ICE support) is a different instance to the B2BUA used for Microsoft Lync
integration. Whereas the Lync B2BUA has to be manually configured and enabled, the B2BUA used for encryption is
automatically enabled whenever an encryption policy is applied.
Configuring ICE Messaging Support

The ICE support option is a per-zone and per-subzone configuration setting that controls how the VCS supports ICE
messages to and from SIP devices within that zone or subzone.
The behavior depends upon the configuration of the ICE support setting on the incoming (ingress) and outgoing
(egress) zone or subzone. When there is a mismatch of settings i.e. On on one side and Off on the other side, the VCS
invokes its back-to-back user agent (B2BUA) to perform ICE negotiation with the relevant host.
All zones and subzones have ICE support set to Off by default.
When the B2BUA performs ICE negotiation with a host, it can offer TURN relay candidate addresses. To do this, the
B2BUA must be configured with the addresses of the TURN servers to offer (via Applications > B2BUA > B2BUA
TURN servers).
The following matrix shows the VCS behavior for the different possible combinations of the ICE support setting when
handling a call between, for example, zone A and zone B:
ICE Zone A
support
setting Off On
Off Standard VCS proxying behavior. B2BUA is invoked.
B2BUA is not normally invoked (however, see the B2BUA includes ICE candidates in messages to
Zone note below regarding media encryption policy). hosts in Zone A.
B
On B2BUA is invoked. Standard VCS proxying behavior.
B2BUA includes ICE candidates in messages to B2BUA is not normally invoked (however, see the
hosts in Zone B. note below regarding media encryption policy).
Effect of media encryption policy when combined with ICE support

The VCS also invokes the B2BUA if it has to apply a media encryption policy (any encryption setting other than Auto).
This table shows the effect on ICE negotiation behavior depending on the ICE support and media encryption modes of
the ingress and egress zones or subzones:
ICE support Media encryption B2BUA Effect on ICE negotiation

mode invoked
Both zones / At least one zone / Yes The B2BUA will not perform any ICE negotiation with either
subzones = Off subzone is not Auto host.
Both zones / At least one zone / Yes The B2BUA will perform ICE negotiation with both hosts.
subzones = On subzone is not Auto
140
ICE support Media encryption B2BUA Effect on ICE negotiation

mode invoked
Both zones / Both zones / subzones No The VCS will not offer any TURN relay candidate addresses
subzones = On = Auto to either of the ICE capable hosts. However, note that each
host device may have already been provisioned with TURN
relay candidate addresses.
Note that:
B2BUA routed calls are identified in the call history by a component type of B2BUA.
A traversal call license is consumed when a call goes via the encryption B2BUA.
There is a limit of 100 concurrent calls (500 calls on Large systems) that can be routed via the B2BUA.
About the Local Zone and Subzones

The collection of all endpoints, gateways, MCUs and Content Servers registered with the VCS makes up its Local
Zone.
The Local Zone is divided into subzones. These include an automatically created Default Subzone and up to 1000
manually configurable subzones.
When an endpoint registers with the VCS it is allocated to an appropriate subzone based on subzone membership
rules. These rules specify the range of IP addresses or alias pattern matches for each subzone. If an endpoints IP
address or alias does not match any of the membership rules, it is assigned to the Default Subzone.
The Local Zone may be independent of network topology, and may comprise multiple network segments. The VCS
also has two special types of subzones:
the Traversal Subzone, which is always present

the Cluster Subzone, which is always present but only used when your VCS is part of a cluster
Bandwidth management
The Local Zones subzones are used for bandwidth management. After you have set up your subzones you can apply
bandwidth limits to:
individual calls between two endpoints within the subzone

individual calls between an endpoint within the subzone and another endpoint outside of the subzone
the total of calls to or from endpoints within the subzone
For full details of how to create and configure subzones, and apply bandwidth limitations to subzones including the
Default Subzone and Traversal Subzone, see the Bandwidth control section.
Registration, authentication and media encryption policies
In addition to bandwidth management, subzones are also used to control the VCS's registration, authentication and
media encryption policies.
See Configuring Subzones, page 218 for more information about how to configure these settings.
Local Zone searches
One of the functions of the VCS is to route a call received from a locally registered endpoint or external zone to its
appropriate destination. Calls are routed based on the address or alias of the destination endpoint.
The VCS searches for a destination endpoint in its Local Zone and its configured external zones. You can prioritize
the order in which these zones are searched, and filter the search requests sent to each zone, based on the address
or alias being searched for. This allows you to reduce the potential number of search requests sent to the Local Zone
and out to external zones, and speed up the search process.
141
For further information about how to configure search rules for the Local Zone, see the Configuring search and zone
transform rules section.
The Default Zone

The Default Zone represents any incoming calls from endpoints or other devices that are unregistered or not
recognized as belonging to the Local Zone or any of the existing configured zones.
The VCS comes pre-configured with the Default Zone and default links between it and both the Default Subzone and
the Traversal Subzone. Note that the Default Zone cannot be deleted.
Configuring the Default Zone

By configuring the Default Zone you can control how the VCS handles calls from unrecognized systems and
endpoints. To configure the Default Zone, go to Configuration >Zones >Zones and click on DefaultZone.
Authentication The Authentication policy See Authentication Policy Configuration Options, page 111 for
policy setting controls how the VCS more information.
challenges incoming messages
to the Default Zone.
Media The Media encryption mode See Configuring Media Encryption Policy, page 139 for more
encryption setting controls the media information.
mode encryption capabilities for SIP
calls flowing through the
Default Zone.
ICE support Controls whether ICE See Configuring ICE Messaging Support, page 140 for more
messages are supported by the information.
devices in this zone.
Use Default This controls whether access The default TLSport is 5061 and the default MTLSport is 5062.
Zone access rules are applied to external This setting does not affect other connections to the Default
rules on port systems that attempt to Zone (H.323 and SIPUDP/TCP).
connect to the VCS TLSport
via the Default Zone. TLSand MTLS: Access rules are enabled for Default Zone
connection attempts to the VCS TLSand MTLSports.
MTLSOnly: Access rules are disabled for Default Zone

connection attempts to the VCS TLSport. Access rules are
always enabled for Default Zone MTLSconnection attempts.
There are no access rules by default. You need to create rules

before any connection attempts influenced by this setting will be
allowed. See Configuring Default Zone access rules, page 143
for help on allowing matching systems to make TLS or
MTLSconnections.
Using Links and Pipes to Manage Access and Bandwidth

You can also manage calls from unrecognized systems and endpoints by configuring the links and pipes associated
with the Default Zone. For example, you can:
delete the default links to prevent any incoming calls from unrecognized endpoints
apply pipes to the default links to control the bandwidth consumed by incoming calls from unrecognized
endpoints
142
Configuring Default Zone access rules

Create Default Zone access rules (Configuration >Zones >Default Zone access rules) to control which external
systems are allowed to connect over SIPTLS to the VCS via the Default Zone.
For each rule, you specify a pattern to compare against the CN (and any SANs) in the certificates received from
external systems. You can then choose whether to allow or deny access to systems that present matching
certificates. Up to 10,000 rules can be configured.
The switch to control whether or not these rules are engaged on the default zone is on the Configuration >Zones >
Zones >DefaultZone page. See The Default Zone, page 142.
Table 5 Default Zone Access Rule Parameters
Name The name assigned to the rule.
Description An optional free-form description of the rule.
Priority Determines the order in which the rules are applied if the
certificate names match multiple rules. The rules with the
highest priority (1, then 2, then 3 and so on) are applied first.
Multiple rules with the same priority are applied in
configuration order.
Pattern The way in which the Pattern string must match the Subject You can test whether a pattern
type Common Name or any Subject Alternative Names contained matches a particular name by using
within the certificate. the Check pattern tool
(Maintenance > Tools > Check
Exact: the entire string must exactly match the name, pattern).
character for character.
Prefix: the string must appear at the beginning of the name.
Suffix: the string must appear at the end of the name.
Regex: treats the string as a regular expression.
Pattern The pattern against which the name is compared.

string
Action The action to take if the certificate matches this access rule.
Allow: allows the external system to connect via the Default

Zone.
Deny: rejects any connection requests received from the

external system.
State Indicates if the rule is enabled or not. Use this setting to test configuration
changes, or to temporarily disable
certain rules. Any disabled rules still
appear in the rules list but are
ignored.
Configuring Zones
The Zones page (Configuration > Zones > Zones) lists all the zones that have been configured on the VCS, and lets
you create, edit and delete zones.
It also displays the zone's H.323 or SIP connection status:
143
Off: the protocol is disabled at either the zone or system level

Active: the protocol is enabled for that zone and it has at least one active connection; if multiple connections
are configured and some of those connections have failed, the display indicates how many of the connections
are Active
On: applies to DNS and ENUM zones only and indicates that the protocol is enabled for that zone
Failed: the protocol is enabled for that zone but its connection has failed
Checking: the protocol is enabled for that zone and the system is currently trying to establish a connection
To neighbor with another system (such as another VCS or gatekeeper), create a connection over a firewall to a
traversal server or traversal client, or discover endpoints via an ENUM or DNS lookup, you must configure a zone on
the local VCS. The available zone types are:
Neighbor: connects the local VCS to a neighbor system

Traversal client: connects the local VCS to a traversal server
Traversal server: connects the local VCS Expressway to a traversal client
ENUM: enables ENUM dialing via the local VCS
DNS: enables the local VCS to locate endpoints and other systems by using DNS lookups
The zone type indicates the nature of the connection and determines which configuration options are available. For
traversal server zones, traversal client zones and neighbor zones this includes providing information about the
neighbor system such as its IP address and ports.
The VCS also has a pre-configured Default Zone. The Default Zone represents any incoming calls from endpoints or
other devices that are unregistered or not recognized as belonging to the Local Zone or any of the existing configured
zones.
Note that connections between the VCS and neighbor systems must be configured to use the same SIP transport
type, that is they must both be configured to use TLS or both be configured to use TCP. In software versions prior to
X5.1 a connection could be established if one system was configured to use TLS and the other used TCP. Any
connection failures due to transport type mismatches are recorded in the Event Log.
After creating a zone you would normally make it a target of at least one of your zone policy search rules
(Configuration > Dial plan > Search rules) otherwise search requests will not be sent to that zone.
Configuring Neighbor Zones

A neighbor zone could be a collection of endpoints registered to another system (such as another VCS), or it could be
a SIP device (for example Cisco Unified Communications Manager). The other system or SIP device is referred to as a
neighbor. Neighbors can be part of your own enterprise network, part of a separate network, or even standalone
systems.
You create a neighbor relationship with the other system by adding it as a neighbor zone on your local VCS. After you
have added it, you can:
query the neighbor about its endpoints

apply transforms to any requests before they are sent to the neighbor
control the bandwidth used for calls between your local VCS and the neighbor zone
Note that:
neighbor zone relationship definitions are one-way; adding a system as a neighbor to your VCS does not
automatically make your VCS a neighbor of that system
inbound calls from any configured neighbor are identified as coming from that neighbor
systems that are configured as cluster peers (formerly known as Alternates) must not be configured as
neighbors to each other
The configurable options for a neighbor zone are:
144
Configuration section:
Name The name acts as a unique identifier, allowing

you to distinguish between zones of the same
type.
Type The nature of the specified zone, in relation to After a zone has been created, the Type
the local VCS. Select Neighbor. cannot be changed.
Hop count The hop count is the number of times a request If the search request was received from another
will be forwarded to a neighbor gatekeeper or zone and already has a hop count assigned, the
proxy (see the Hop counts section for more lower of the two values is used.
information). This field specifies the hop count
to use when sending a search request to this
particular zone.
H.323 section:
Mode Determines whether H.323 calls are allowed to

and from the neighbor system.
Port The port on the neighbor system used for H.323 This must be the same port number as that
searches initiated from the local VCS. configured on the neighbor system as its H.323
UDP port. If the neighbor is another VCS, this is
the port found under Configuration > Protocols
> H.323 in the Registration UDP Port field.
SIP section:
Mode Determines whether SIP calls are allowed to and

from the neighbor system.
Port The port on the neighbor system used for This must be the same port number as that
outgoing SIP messages initiated from the local configured on the neighbor system as its SIP
VCS. TCP, SIP TLS or SIP UDP listening port
(depending on which SIP Transport mode is in
use).
Transport Determines which transport type is used for SIP

calls to and from the neighbor system. The
default is TLS.
TLS verify Controls whether the VCS performs X.509 If the neighbor system is another VCS, both
mode certificate checking against the neighbor system systems can verify each other's certificate
when communicating over TLS. (known as mutual authentication). See TLS
Certificate Verification of Neighbor Systems,
page 157 for more information.
Accept Controls whether proxied SIP registrations This setting only applies to registration requests
proxied routed through this zone are accepted. for a domain for which the VCS is acting as a
registrations Registrar. For requests for other domains the
SIP registration proxy mode setting applies.
See Proxying registration requests for more
information.
Media Controls the media encryption policy applied by See Configuring Media Encryption Policy, page
encryption the VCS for SIP calls (including interworked 139 for more information.
mode calls) to and from this zone.
145
ICE support Controls whether ICE messages are supported See Configuring ICE Messaging Support, page
by the devices in this zone. 140 for more information.
Authentication section:
Authentication Controls how the VCS authenticates incoming The behavior varies for H.323 messages, SIP
policy messages from this zone and whether they are messages that originate from a local domain
subsequently treated as authenticated, and SIP messages that originate from non-local
unauthenticated, or are rejected. domains. See Authentication Policy
Configuration Options, page 111 for more
information.
SIP Controls whether authenticated SIP messages See SIP Authentication Trust, page 114 for
authentication (ones containing a P-Asserted-Identity header) more information.
trust mode from this zone are trusted without further
challenge.
Location section:
Location The IP address or FQDN of the neighbor system. Calls to a VCS cluster are routed to whichever
Peer 1 to Peer peer in that neighboring cluster has the lowest
6 address Enter the addresses of additional peers if: resource usage. See Neighboring Between
VCS Clusters, page 170 for more information.
the neighbor is a VCS cluster, in which
case you must specify all of the peers in For connections to non-VCS systems, the VCS
the cluster uses a round-robin selection process to decide
which peer to contact if no resource usage
the neighbor is a resilient non-VCS information is available.
system, in which case you must enter the
addresses of all of the resilient elements
in that system
Advanced section:
Zone profile Determines how the zone's advanced settings See Zone Configuration: Advanced Settings,
are configured. page 153 for details on the advanced settings.
Default: uses the factory default profile. Only use the Custom profile to configure the
individual advanced settings on the advice of
Custom: allows you to configure each setting Cisco customer support.
individually.
See Cisco Unified Communications Manager
Alternatively. choose one of the preconfigured with VCS Deployment Guide for more
profiles to automatically use the appropriate information about the Cisco Unified
settings required for connections to that type of Communications Manager profiles.
system. The options include:
Cisco Unified Communications Manager

Cisco Unified Communications Manager
(8.6.1 or later)
Nortel Communication Server 1000
Infrastructure device (typically used for
non-gatekeeper devices such as an
MCU)
Configuring Traversal Client Zones

To traverse a firewall, the VCS must be connected with a traversal server (typically, a VCS Expressway).
146
In this situation your local VCS is a traversal client, so you create a connection with the traversal server by creating a
traversal client zone on your local VCS. You then configure the client zone with details of the corresponding zone on
the traversal server. (The traversal server must also be configured with details of the VCS client zone.)
After you have neighbored with the traversal server you can:
use the neighbor as a traversal server

query the traversal server about its endpoints
apply transforms to any queries before they are sent to the traversal server
control the bandwidth used for calls between your local VCS and the traversal server
For full details on how traversal client zones and traversal server zones work together to achieve firewall traversal,
see About Firewall Traversal, page 38.
An NTP server must be configured for traversal zones to work.
The configurable options for a traversal client zone are:
Name The name acts as a unique identifier, allowing you to

distinguish between zones of the same type.
Type The nature of the specified zone, in relation to the After a zone has been created, the
local VCS. Select Traversal client. Type cannot be changed.
Hop count The hop count is the number of times a request will If the search request was received from
be forwarded to a neighbor gatekeeper or proxy (see another zone and already has a hop
the Hop counts section for more information). This count assigned, the lower of the two
field specifies the hop count to use when sending a values is used.
search request to this particular zone.
Connection credentials section:
Username and Traversal clients must always authenticate with Multiple traversal client zones can be
Password traversal servers by providing their authentication configured, each with distinct
credentials. Each traversal client zone must specify a credentials, to connect to one or more
Username and Password to be used for service providers.
authentication with the traversal server.
H.323 section:
Mode Determines whether H.323 calls are allowed to and

from the traversal server.
Protocol Determines which of the two firewall traversal See Configuring Ports for Firewall
protocols (Assent or H.460.18) to use for calls to the Traversal, page 42 for more information.
traversal server.
Port The port on the traversal server to use for H.323 calls For firewall traversal to work via H.323,
to and from the local VCS. the traversal server must have a
traversal server zone configured on it to
represent this VCS, using this same port
number.
SIP section:

from the traversal server.
147
Port The port on the traversal server to use for SIP calls to For firewall traversal to work via SIP, the
and from the VCS. traversal server must have a traversal
server zone configured on it to
This must be different from the listening ports used represent this VCS, using this same
for incoming TCP, TLS and UDP SIP calls (typically transport type and port number.
5060 and 5061).
Unified Controls whether this traversal zone provides Unified If enabled, this zone must also be
Communications Communications services, such as mobile and configured to use TLS with TLS verify
services remote access. mode enabled.
This setting only applies when Unified

Communications mode is set to Mobile
and remote access.
Transport Determines which transport type is used for SIP calls

to and from the traversal server. The default is TLS.
TLS verify mode Controls X.509 certificate checking and mutual See TLS Certificate Verification of
authentication between this VCS and the traversal Neighbor Systems, page 157 for more
server when communicating over TLS. information.
Accept proxied Controls whether proxied SIP registrations routed This setting only applies to registration
registrations through this zone are accepted. requests for a domain for which the
VCS is acting as a Registrar. For
requests for other domains the SIP
registration proxy mode setting
applies. See Proxying registration
requests for more information.
Media Controls the media encryption policy applied by the See Configuring Media Encryption
encryption VCS for SIP calls (including interworked calls) to and Policy, page 139 for more information.
mode from this zone.
ICE support Controls whether ICE messages are supported by the See Configuring ICE Messaging
devices in this zone. Support, page 140 for more information.
Poison mode Determines if SIP requests sent to systems located

via this zone are "poisoned" such that if they are
received by this VCS again they will be rejected.
Authentication Controls how the VCS authenticates incoming See Authentication Policy Configuration
policy messages from this zone and whether they are Options, page 111 for more information.
subsequently treated as authenticated,
unauthenticated, or are rejected. The behavior varies
for H.323 messages, SIP messages that originate
from a local domain and SIP messages that originate
from non-local domains.
Accept Controls whether this zone accepts delegated See Configuring Delegated Credential
delegated authentication requests. Checking (SIP Only), page 115 for more
credential information.
checks
Client settings section:
148
Retry interval The interval in seconds with which a failed attempt to

establish a connection to the traversal server should
be retried.
Location section:
Peer 1 to Peer 6 The IP address or FQDN of the traversal server. See Neighboring Between VCS
address Clusters, page 170 for more
If the traversal server is a VCS Expressway cluster, information.
this should include all of its peers.
Configuring Traversal Server Zones

AVCS Expressway can act as a traversal server, providing firewall traversal on behalf of traversal clients (a VCS
Control).
For firewall traversal to work, the traversal server (VCS Expressway) must have a special type of two-way relationship
with each traversal client. To create this connection between a VCS Expressway and a VCS Control, see Configuring
a Traversal Client and Server, page 41. For full details on how traversal client zones and traversal server zones work
together to achieve firewall traversal, see About Firewall Traversal, page 38.
Note:You must synchronize with an NTP server to make sure that traversal zones to work.
After you have neighbored with the traversal client you can:
provide firewall traversal services to the traversal client

query the traversal client about its endpoints
apply transforms to any queries before they are sent to the traversal client
control the bandwidth used for calls between your local VCS and the traversal client
view zone status information, including the connection addresses
Note:Connection addresses listed in the status information may have been translated by a NAT element
between the traversal server zone and the originating device.
Table 6 Traversal server zone configuration reference

Type The nature of the specified zone, in relation to the After a zone has been created, the Type
local VCS. Select Traversal server. cannot be changed.
be forwarded to a neighbor gatekeeper or proxy (see another zone and already has a hop
the Hop counts section for more information). This count assigned, the lower of the two
field specifies the hop count to use when sending a values is used.
Connection credentials section:
149
Table 6 Traversal server zone configuration reference (continued)
Username Traversal clients must always authenticate with There must also be an entry in the VCS
traversal servers by providing their authentication Expressway's local authentication
credentials. database for the clients authentication
username and password. To check the
The authentication username is the name that the list of entries and add it if necessary, go
traversal client must provide to the VCS Expressway. to the Local authentication database
(It is configured as the connection credentials page. Either:
Username in its traversal client zone.)
click on the Add/Edit local
authentication database link
go to Configuration >
Authentication > Local database
H.323 section:
Mode Determines whether H.323 calls are allowed to and

from the traversal client.
Protocol Determines the protocol (Assent or H.460.18) to use See Configuring Ports for Firewall
to traverse the firewall/NAT. Traversal, page 42 for more information.
Port The port on the local VCS Expressway to use for

H.323 calls to and from the traversal client.
H.460.19 Determines whether or not the same two ports are

demultiplexing used for media by two or more calls.
mode
On: all calls from the traversal client use the same
two ports for media.
Off: each call from the traversal client uses a

separate pair of ports for media.
SIP section:

from the traversal client.
Port The port on the local VCS Expressway to use for SIP This must be different from the listening
calls to and from the traversal client. ports used for incoming TCP, TLS and
UDP SIP calls (typically 5060 and 5061).
Transport Determines which transport type is used for SIP calls

to and from the traversal client. The default is TLS.
Unified Controls whether this traversal zone provides Unified If enabled, this zone must also be
Communications Communications services, such as mobile and configured to use TLS with TLS verify
services remote access. mode enabled.
This setting only applies when Unified

Communications mode is set to Mobile
and remote access.
150
TLS verify mode Controls X.509 certificate checking and mutual If the traversal client is clustered, the
and subject authentication between this VCS and the traversal TLS verify subject name must be the
name client. FQDN of the cluster.
If TLS verify mode is enabled, a TLS verify subject See TLS Certificate Verification of
name must be specified. This is the certificate Neighbor Systems, page 157 for more
holder's name to look for in the traversal client's information.
X.509 certificate.
Accept proxied Controls whether proxied SIP registrations routed This setting only applies to registration
registrations through this zone are accepted. requests for a domain for which the VCS
is acting as a Registrar. For requests for
other domains the SIP Registration
Proxy Mode setting applies. See
Proxying registration requests for more
information.
Media Controls the media encryption policy applied by the See Configuring Media Encryption
encryption VCS for SIP calls (including interworked calls) to and Policy, page 139 for more information.
mode from this zone.
ICE support Controls whether ICE messages are supported by the See Configuring ICE Messaging
devices in this zone. Support, page 140 for more information.
Poison mode Determines if SIP requests sent to systems located

via this zone are "poisoned" such that if they are
received by this VCS again they will be rejected.
Authentication Controls how the VCS authenticates incoming See Authentication Policy Configuration
policy messages from this zone and whether they are Options, page 111 for more information.
subsequently treated as authenticated,
unauthenticated, or are rejected. The behavior
varies for H.323 messages, SIP messages that
originate from a local domain and SIP messages that
originate from non-local domains.
UDP / TCP probes section:
UDP retry The frequency (in seconds) with which the client The default UDP and TCP probe retry
interval sends a UDP probe to the VCS Expressway if a keep intervals are suitable for most situations.
alive confirmation has not been received. However, if you experience problems
with NAT bindings timing out, they may
need to be changed.
UDP retry count The number of times the client attempts to send a
UDP probe to the VCS Expressway during call setup.
UDP keep alive The interval (in seconds) with which the client sends
interval a UDP probe to the VCS Expressway after a call is
established, in order to keep the firewalls NAT
bindings open.
TCP retry The interval (in seconds) with which the traversal
interval client sends a TCP probe to the VCS Expressway if a
keep alive confirmation has not been received.
151
TCP retry count The number of times the client attempts to send a
TCP probe to the VCS Expressway during call setup.
TCP keep alive The interval (in seconds) with which the traversal
interval client sends a TCP probe to the VCS Expressway
when a call is in place, in order to maintain the
firewalls NAT bindings.
Configuring ENUM Zones

ENUM zones allow you to locate endpoints via an ENUM lookup. You can create one or more search rules for ENUM
zones based on the ENUM DNS suffix used and/or by pattern matching of the endpoints aliases.
After you have configured one or more ENUM zones, you can:
apply transforms to alias search requests directed to that group of endpoints

control the bandwidth used for calls between your local VCS and each group of ENUM endpoints
Full details of how to use and configure ENUM zones are given in the About ENUM Dialing, page 205 section.
The configurable options for an ENUM zone are:
Name The name acts as a unique identifier, allowing you to distinguish

between zones of the same type.
Type The nature of the specified zone, in relation to the local VCS. Select After a zone has been created, the
ENUM. Type cannot be changed.
Hop The hop count is the number of times a request will be forwarded to a If the search request was received
count neighbor gatekeeper or proxy (see the Hop counts section for more from another zone and already has
information). This field specifies the hop count to use when sending a hop count assigned, the lower of
a search request to this particular zone. the two values is used.
DNS The domain to be appended to the transformed E.164 number to

suffix create an ENUM domain for which this zone is queried.
H.323 Determines whether H.323 records are looked up for this zone.
mode
SIP Determines whether SIP records are looked up for this zone.
mode
Configuring DNS Zones

DNS zones allow you to locate endpoints via a DNS lookup. You can create one or more search rules for DNS zones
based on pattern matching of the endpoints aliases.
After you have configured one or more DNS zones, you can:
apply transforms to alias search requests directed to that group of endpoints

control the bandwidth used for calls between your local VCS and each group of DNS endpoints
See About URI Dialing, page 198 for more information on configuring and using DNS zones.
The configurable options for a DNS zone are:
152

Type The nature of the specified zone, in relation to the After a zone has been created, the Type
local VCS. Select DNS. cannot be changed.
be forwarded to a neighbor gatekeeper or proxy (see another zone and already has a hop count
the Hop counts section for more information). This assigned, the lower of the two values is used.
field specifies the hop count to use when sending a
H.323 Determines whether H.323 calls are allowed to

mode systems and endpoints located using DNS lookups
via this zone.
SIP mode Determines whether SIP calls are allowed to systems

and endpoints located using DNS lookups via this
zone.
TLS verify Controls whether the VCS performs X.509 certificate This setting only applies if the DNS lookup
mode and checking against the destination system server specifies TLS as the required protocol. If TLS
subject returned by the DNS lookup. is not required then the setting is ignored. See
name TLS Certificate Verification of Neighbor
If TLS verify mode is enabled, a TLS verify subject Systems, page 157 for more information.
name must be specified. This is the certificate
holder's name to look for in the destination system
server's X.509 certificate.
TLS verify The certificate holder's name to look for in the

subject destination system server's X.509 certificate (must
name be in either the Subject Common Name or the
Subject Alternative Name attributes).
Fallback The transport type to use for SIP calls from the DNS
transport zone, when DNS NAPTR records and SIP URI
protocol parameters do not provide the preferred transport
information.
The default is UDP (if enabled).
Media Controls the media encryption policy applied by the See Configuring Media Encryption Policy,
encryption VCS for SIP calls (including interworked calls) to the page 139 for more information.
mode internet.
ICE Controls whether ICE messages are supported by the See Configuring ICE Messaging Support, page
support devices in this zone. 140 for more information.
Zone Determines how the zone's advanced settings are See Zone Configuration: Advanced Settings,
profile configured. page 153 for details on the advanced settings.
Default: uses the factory default profile. Only use the Custom profile to configure the
individual advanced settings on the advice of
Custom: allows you to configure each setting Cisco customer support.
individually.
Zone Configuration: Advanced Settings

The table below describes the advanced zone configuration options for the Custom zone profile. Some of these
settings only apply to specific zone types.
153
Setting Description Default Zone types
Include Determines whether, if no NAPTR (SIP) or SRV (SIP and H.323) records Off DNS
address have been found for the dialed alias via this zone, the VCS will then
record query for A and AAAA DNS records before moving on to query lower
priority zones. If A and AAAA records exist at the same domain for
systems other than those that support SIP or H.323, this may result in the
VCS believing the search was successful and forwarding calls to this
zone, and the call will fail.
On: the VCS queries for A or AAAA records. If any are found, the VCS will
not then query any lower priority zones.
Off: the VCS will not query for A and AAAA records and instead will
continue with the search, querying the remaining lower priority zones.
Monitor peer Specifies whether the VCS monitors the status of the zone's peers. If Yes Neighbor
status enabled, H.323 LRQs and/or SIP OPTIONS are periodically sent to the
peers. If a peer fails to respond, that peer is marked as inactive. If all
peers fail to respond the zone is marked as inactive.
Call signaling Specifies how the VCS handles the signaling for calls to and from this Auto Neighbor
routed mode neighbor.
Auto: signaling is taken as determined by the Call signaling optimization

(Configuration > Call routing) configuration.
Always: signaling is always taken for calls to or from this neighbor,

regardless of the Call signaling optimization configuration.
Calls via traversal zones or the B2BUA always take the signaling.
Automatically Determines what happens when the VCS receives an H.323 search, Off Neighbor
respond to destined for this zone.
H.323
searches Off: an LRQ message is sent to the zone.
On: searches are responded to automatically, without being forwarded

to the zone.
Automatically Determines what happens when the VCS receives a SIP search that Off Neighbor
respond to originated as an H.323 search. DNS
SIP searches
Off: a SIP OPTIONS or SIP INFO message is sent.
On: searches are responded to automatically, without being forwarded.
This should normally be left as the default Off. However, some systems
do not accept SIP OPTIONS messages, so for these zones it must be set
to On. If you change this to On, you must also configure pattern matches
to ensure that only those searches that actually match endpoints in this
zone are responded to. If you do not, the search will not continue to
other lower-priority zones, and the call will be forwarded to this zone
even if it cannot support it.
154
Send empty Determines whether the VCS generates a SIP INVITE message with no On Neighbor
INVITE for SDP to send via this zone. INVITES with no SDP mean that the DNS
interworked destination device is asked to initiate the codec selection, and are used
calls when the call has been interworked locally from H.323.
On: SIP INVITEs with no SDP are generated.
Off: SIP INVITEs are generated and a pre-configured SDP is inserted

before the INVITEs are sent.
In most cases this option should normally be left as the default On.
However, some devices do not accept invites with no SDP, so for these
zones this should be set to Off.
Note that the settings for the pre-configured SDP are configurable via
the CLI using the xConfiguration Zones Zone [1..1000] [Neighbor/DNS]
Interworking SIP commands. They should only be changed on the
advice of Cisco customer support.
SIPparameter Determines whether the VCS's B2BUA preserves or rewrites the Off Neighbor
preservation parameters in SIP requests routed via this zone.
DNS
On preserves the SIP Request URI and Contact parameters of requests
routing between this zone and the B2BUA. UCTraversal
Off allows the B2BUA to rewrite the SIP Request URI and Contact Traversal
parameters of requests routing between this zone and the B2BUA, if Server
necessary.
Traversal
Default: Off Client
SIP poison On: SIP requests sent to systems located via this zone are "poisoned" Off Neighbor
mode such that if they are received by this VCS again they will be rejected. Traversal
client
Off: SIP requests sent out via this zone that are received by this VCS Traversal
again will not be rejected; they will be processed as normal. server
DNS
SIP Determines whether or not the VCS allows encrypted SIP calls on this Auto Neighbor
encryption zone.
mode
Auto: SIP calls are encrypted if a secure SIP transport (TLS) is used.
Microsoft: SIP calls are encrypted using MS-SRTP.
Off: SIP calls are never encrypted.
This option should normally be left as the default Auto.
SIP REFER Determines how SIP REFER requests are handled. Forward Neighbor
mode
Forward: SIP REFER requests are forwarded to the target.
Terminate: SIP REFER requests are terminated by the VCS.
SIP multipart Controls whether or not multipart MIME stripping is performed on Off Neighbor
MIME strip requests from this zone.
mode
This option should normally be left as the default Off.
155
SIP UPDATE Controls whether or not the VCS strips the UPDATE method from the Off Neighbor
strip mode Allow header of all requests and responses received from, and sent to,
this zone.
This option should normally be left as the default Off. However, some
systems do not support the UPDATE method in the Allow header, so for
these zones this should be set to On.
Interworking Determines how the VCS searches for SIP endpoints when interworking Options Neighbor
SIP search an H.323 call.
strategy
Options: the VCS sends an OPTIONS request.
Info: the VCS sends an INFO request.
This option should normally be left as the default Options. However,

some endpoints cannot respond to OPTIONS requests, so this must be
set to Info for such endpoints.
SIP Determines whether INVITE requests sent to this zone filter out Off Neighbor
UDP/BFCP UDP/BFCP. This option may be required to enable interoperability with DNS
filter mode SIP devices that do not support the UDP/BFCP protocol.
On: any media line referring to the UDP/BFCP protocol is replaced with
TCP/BFCP and disabled.
Off: INVITE requests are not modified.
SIP UDP/IX Determines whether INVITE requests sent to this zone filter out Off Neighbor
filter mode UDP/UDT/IX or UDP/DTLS/UDT/IX. This option may be required to enable DNS
interoperability with SIP devices that do not support the UDP/UDT/IX or
UDP/DTLS/UDT/IX protocol.
On: any media line referring to the UDP/UDT/IX or UDP/DTLS/UDT/IX

protocol is replaced with RTP/AVP and disabled.
We recommend that SIP UDP/IX filter mode is set to On for:
business-to-business calls routed through neighbor zones that

connect to external networks / non-Cisco infrastructure
calls that connect internally to Unified CM 8.x or earlier (use Off
for 9.x or later)
SIP record Controls whether the VCS uses its IP address or host name in the IP Neighbor
route address record-route or path headers of outgoing SIP requests to this zone. DNS
type
IP: uses the VCS's IP address.
Hostname: uses the VCS's System host name (if it is blank the IP
address is used instead).
SIP Proxy- A comma-separated list of option tags to search for and remove from None Neighbor
Require Proxy-Require headers in SIP requests received from this zone.
header strip
list
156
Zone Configuration: Pre-Configured Profile Settings

The table below shows the advanced zone configuration option settings that are automatically applied for each of the
pre-configured profiles.
Setting Cisco Unified Cisco Unified Nortel Infrastructure Default

Communications Communications Communication device
Manager Manager (8.6.1 Server 1000
or later)
Monitor peer status Yes Yes Yes No Yes
Call signaling routed mode Always Always Auto Always Auto
Automatically respond to Off Off Off On Off

H.323 searches
Automatically respond to SIP Off Off Off On Off

searches
Send empty INVITE for On On On On On

interworked calls
SIP poison mode Off Off Off Off Off
SIP encryption mode Auto Auto Auto Auto Auto
SIP REFER mode Forward Forward Forward Forward Forward
SIP multipart MIME strip mode Off Off Off Off Off
SIP UPDATE strip mode Off Off On Off Off
Interworking SIP search Options Options Options Options Options

strategy
SIP UDP/BFCP filter mode On Off Off Off Off
SIP UDP/IX filter mode On On On On Off
SIP record route address type IP IP IP IP IP
SIP Proxy-Require header strip <blank> <blank> "com.nortelnetw <blank> <blank>

list orks.firewall"
For more information about configuring a SIP trunk between VCS and Unified CM, see Cisco Unified Communications
Manager with VCS Deployment Guide.
TLS Certificate Verification of Neighbor Systems

When a SIP TLS connection is established between a VCS and a neighbor system, the VCS can be configured to
check the X.509 certificate of the neighbor system to verify its identity. You do this by configuring the zones TLS
verify mode setting.
If TLS verify mode is enabled, the neighbor system's FQDN or IP address, as specified in the Peer address field of
the zones configuration, is used to verify against the certificate holders name contained within the X.509 certificate
presented by that system. (The name has to be contained in either the Subject Common Name or the Subject
Alternative Name attributes of the certificate.) The certificate itself must also be valid and signed by a trusted
certificate authority.
Note that for traversal server and DNS zones, the FQDN or IP address of the connecting traversal client is not
configured, so the required certificate holders name is specified separately.
157
If the neighbor system is another VCS, or it is a traversal client / traversal server relationship, the two systems can be
configured to authenticate each others certificates. This is known as mutual authentication and in this case each
VCS acts both as a client and as a server and therefore you must ensure that each VCSs certificate is valid both as a
client and as a server.
See About Security Certificates, page 282 for more information about certificate verification and for instructions on
uploading the VCSs server certificate and uploading a list of trusted certificate authorities.
Configuring a Zone for Incoming Calls Only

To configure a zone so that it is never sent an alias search request (for example if you only want to receive incoming
calls from this zone), do not define any search rules that have that zone as its target.
In this scenario, when viewing the zone, you can ignore the warning indicating that search rules have not been
configured.
158
159
Clustering and Peers
This section describes how to set up a cluster of VCS peers. Clustering is used to increase the capacity of your VCS
deployment and to provide resiliency.
About Clusters 160

License Usage Within a Cluster 162
Managing Clusters and Peers 163
Troubleshooting cluster replication problems 170
About Clusters
A VCS can be part of a cluster of up to six VCSs. Each VCS in the cluster is a peer of every other VCS in the cluster.
When creating a cluster, you define a cluster name and nominate one peer as the master from which all relevant
configuration is replicated to the other peers in the cluster. Clusters are used to:
Increase the capacity of your VCS deployment compared with a single VCS.
Provide redundancy in the rare case that a VCS becomes inaccessible (for example, due to a network or
power outage) or while it is in maintenance mode (for example, during a software upgrade).
Peers share information with each other about their use of bandwidth, registrations, and user accounts. This allows
the cluster to act as one large VCS Local Zone as shown in the example below.
160
About the configuration master

All peers in a cluster must have identical configuration for subzones, zones, links, pipes, authentication, bandwidth
control and Call Policy. To achieve this, you define a cluster name and nominate one peer as the configuration
master. Any configuration changes made to the master peer are then automatically replicated across all the other
peers in the cluster.
You should only make configuration changes on the primary VCS.
Caution: Do not adjust any cluster-wide configuration until the cluster is stable with all peers running. Cluster
database replication will be negatively impacted if any peers are upgrading, restarting, or out of service when
you change the cluster's configuration.
Any changes made on other peers are not reflected across the cluster, and will be overwritten the next time the
primarys configuration is replicated across the peers. The only exceptions to this are some peer-specific
configuration items.
You may need to wait up to one minute before changes are updated across all peers in the cluster.
Secure communication between peers
The VCS uses IPsec (Internet Protocol Security) to enable secure communication between each cluster peer.
Authentication is carried out through the use of a pre-shared access key.
Each peer in the cluster must be individually configured with the IP address and associated access key of every other
peer in that cluster.
161
License Usage Within a Cluster

The following types of licenses are pooled for use by any peer in a cluster, irrespective of which peer the licenses are
installed on:
Traversal or non-traversal call licenses

TURNrelay licenses
You can cluster up to 6 VCS systems to increase capacity by a maximum factor of 4 (see Performance Capabilities,
page 336 for per peer capacity limits).
If a cluster peer becomes unavailable, the shareable licenses installed on that peer remain available to the rest of the
cluster peers for two weeks from the time the cluster lost contact with the peer. This will maintain the overall license
capacity of the cluster however, note that each peer is limited by its physical capacity. After this two week period,
the licenses associated with the unavailable peer are removed from the cluster. To maintain the same capacity for
your cluster, you should ensure that either the problem with the peer is resolved or new option keys are installed on
another peer in the cluster.
The maximum number of licenses that each VCS system can use depends on the type of appliance or VM:
Table 7 Maximum licenses that a peer can use
Small / Medium / CE500 / CE1100 Large / CE1000 / CE1100

systems systems
Traversal calls 150 500
Non-traversal 750 750

calls
Registrations 2500 5000
TURN relays * 1800 6000
CE1100 appliance can run with medium or large capacity, depending on whether it has 1Gbps or 10Gbps NICs
installed.
This is the maximum number of licenses the system can use. This limit specifically applies to the case where a peer
becomes unavailable and other peers must use its licenses to honor the cluster's overall capacity. This is not
intended as a production capcacity limit, only as a temporary measure to allow the affected peer to be returned to
normal service. We strongly discourage installing more than 100 licenses on any platform that has small or
medium capacity.
* On a Large system, the total TURN capacity of 6000 relays is spread evenly across 6 ports; each port is limited to
handling 1000 relays. On a Small/Medium system, there is a single TURN port that handles up to 1800 relays.
Note that each VCS comes pre-installed with 2,500 registration licenses, and that registration licenses are not
shared across a cluster.
You can see a summary of all of the call, registration and TURN relay licenses installed on each cluster peer by going
to the Option keys page and scrolling down to the Current licenses section.
Licenses Used in Intercluster Calls
This section describes the licenses used when endpoints are registered to different peers in the same cluster.
If the call media does not traverse the cluster peers:
A SIP call between the endpoints consumes two non-traversal call licenses (one on each node).
An H.323 call between the endpoints consumes one non-traversal license (on the node where the endpoint
that initiated the call is registered).
If the call media traverses the cluster peers, or if either endpoint is registered with ASSENTor H.460 capability:
162
A SIP call between the endpoints consumes two traversal call licenses (one on each node).
An H.323 call between the endpoints consumes two traversal call licenses (one on each node).
Capacity alarms are raised if either of the following usage thresholds are reached:
the number of concurrent traversal/non-traversal calls reaches 90% of the capacity of the cluster
the number of concurrent traversal/non-traversal calls on any one unit reaches 90% of the physical capacity
of the unit
Example deployment
If, for example, you want to deploy a resilient cluster that can handle up to 750 concurrent non-traversal calls and
250 concurrent traversal calls you could configure 4 peers as follows:
Peer 1 Peer 2 Peer 3 Peer 4 Total cluster

capacity
Non-traversal call licenses 250 250 250 0 750
Traversal call licenses 100 100 50 0 250
It would not matter to which peer an endpoint registers as the call licenses are shared across all of the peers. If any
one of the peers is temporarily taken out of service the full set of call licenses will remain available to the entire
cluster.
However, we recommend that, where possible, the number of licenses is configured evenly across all peers in the
cluster.
Managing Clusters and Peers
Setting Up a Cluster
Prerequisites
Before setting up a cluster of X8.7VCS peers or adding an X8.7VCS to a cluster, ensure that:
Platform and Software Versions Match
All clusters peers are running the same version of code. The only occasion where different peers are allowed
to run different versions of code is for the short period of time while a cluster is being upgraded from one
version of code to another, during which time the cluster will operate in a partitioned fashion.
Each peer is using a hardware platform (appliance or virtual machine) with equivalent capabilities; for
example, you can cluster peers that are running on standard appliances with peers running on 2 core Medium
VMs, but you cannot cluster a peer running on a standard appliance with peers running on 8 core Large VMs.
Network Conditions Are Met
Each peer has a different LAN configuration (a different IPv4 address and a different IPv6 address, where
enabled).
Each peer in a cluster is within a 15ms hop (30ms round trip delay) of each and every other VCS in or to be
added to the cluster.
Each peer in a cluster is directly routable to each and every other VCS in or to be added to the cluster. (There
must be no NAT between cluster peers if there is a firewall ensure that the required ports are opened.)
163
Basic Configuration Is Done
Each peer has a different system name.

All peers have the same set of option keys installed:
The number of call license keys may be different on different peers; all other license keys must be identical
on each peer.
The VCS must be restarted after installing some option keys in order to fully activate them.
H.323 mode is enabled on each peer (Configuration > Protocols > H.323, and for H.323 mode select On).
The cluster uses H.323 signaling between peers to determine the best route for calls, even if all endpoints are
SIPendpoints.
DNSConfiguration is Done
The DNS servers used by the VCS peers must support both forward and reverse DNS lookups of Cisco TMS
and all VCS peer addresses; the DNS servers must also provide address lookup for any other DNS functionality
required, such as:
NTP servers or the external manager if they configured using DNS names
Microsoft Lync Server FQDN lookup
LDAP server forward and reverse lookup (reverse lookups are frequently provided through PTR records)
Note: DNS server configuration does not replicate and you must configure the DNSserver address on each
peer.
A DNS SRV record is available for the cluster which contains A or AAAA records for each peer of the cluster.
This configuration is advised for video interoperability and business to business (B2B) video calling, but is not
required for Mobile and Remote Access.
(For MRA) Create a collab-edge SRVrecord for each peer in the VCS Expressway cluster
(For B2B only) The VCS Expressway cluster has a DNS SRV record that defines all cluster peers
TMSHas Been Configured (if necessary)
Cisco TMS, if used, is running version 13.2 or later (12.6 or later is permitted if you are not using Cisco TMS for
provisioning or FindMe).
If Cisco TMS is to be used for replicating FindMe and/or Provisioning data, ensure that Provisioning Extension
mode functionality has been enabled on Cisco TMS (see Cisco TMS Provisioning Extension Deployment Guide
for details).
Next Steps
To create your cluster you must first configure a primary peer and then add the other peers into the cluster one at a
time.
We recommend that you backup your VCS data before setting up a cluster.
See VCS Cluster Creation and Maintenance Deployment Guide on the VCS Configuration Guides page.
Maintaining a Cluster
The Clustering page (System > Clustering) lists the IP addresses of all the peers in the cluster, to which this VCS
belongs, and identifies the master peer.
Cluster name
The Cluster name is used to identify one cluster of VCSs from another. Set it to the fully qualified domain name
(FQDN) used in SRV records that address this VCS cluster, for example cluster1.example.com.
164
The FQDN can comprise multiple levels. Each level's name can only contain letters, digits and hyphens, with each
level separated by a period (dot). A level name cannot start or end with a hyphen, and the final level name must start
with a letter.
A cluster name is also required if FindMe is enabled.
Cluster pre-shared key
The VCS uses IPsec (Internet Protocol Security) to enable secure communication between each cluster peer.
The Cluster pre-shared key is the common IPsec access key used by each peer to access every other peer in the
cluster.
Note: each peer in the cluster must be configured with the same Cluster pre-shared key.
Setting configuration for the cluster
You should only make configuration changes on the primary VCS.
Caution: Do not adjust any cluster-wide configuration until the cluster is stable with all peers running. Cluster
database replication will be negatively impacted if any peers are upgrading, restarting, or out of service when
you change the cluster's configuration.
Any changes made on other peers are not reflected across the cluster, and will be overwritten the next time the
primarys configuration is replicated across the peers. The only exceptions to this are some peer-specific
configuration items.
You may need to wait up to one minute before changes are updated across all peers in the cluster.
Adding and Removing Peers From a Cluster

After a cluster has been set up you can add new peers to the cluster or remove peers from it.
Note that:
Systems that are configured as peers must not also be configured as neighbors to each other, and vice versa.
If peers are deployed on different LANs, there must be sufficient connectivity between the networks to ensure
a low degree of latency between the peers - a maximum delay of 15ms one way, 30ms round-trip.
Cluster peers can be in separate subnets. Peers communicate with each other using H.323 messaging, which
can be transmitted across subnet boundaries.
Deploying all peers in a cluster on the same LAN means they can be configured with the same routing
information such as local domain names and local domain subnet masks.
Changing the Master Peer

You should only need to change the Configuration master when:
the original master peer fails

you want to take the master VCS unit out of service
Note that if the master fails, the remaining peers will continue to function normally, except they are no longer able to
copy their configuration from the master so they may become out of sync with each other.
To change the master peer you must log in to every other VCS in the cluster and change the configuration master on
each peer:
1. Log in to the VCS and go to System >Clustering.

2. Change the Configuration master to the peer you want to set as the new master (the numbers match against
the Peer IP address fields underneath).
3. Click Save.
4. Repeat this for every peer in the cluster, ensuring that you select the same new master on each peer.
165
Note that during this process you may see alarms raised on some peers about inconsistent master peer configuration.
These alarms will be lowered when every peer in the cluster is configured with the new master.
Monitoring the Status of the Cluster

The status sections at the bottom of the Clustering page show you the current status of the cluster, and the time of
the previous and next synchronization.
Peer-Specific Items in Clustered Systems

Most items of configuration are applied via the primary peer to all peers in a cluster. However, the following items
(marked with a on the web interface) must be specified separately on each cluster peer.
Note: You should not modify configuration data that applies to all peers on any peer other than the primary peer. At
best it will result in the changes being overwritten from the primary; at worst it will cause cluster replication to fail.
Cluster configuration (System > Clustering)
The list of Peer IP addresses (including the peer's own IP address) that make up the cluster has to be specified on
each peer and they must be identical on each peer.
The Cluster name and Cluster pre-shared key have to be specified on each peer and must be identical for all peers.
Ethernet speed (System > Network interfaces >Ethernet)
The Ethernet speed is specific to each peer. Each peer may have slightly different requirements for the connection to
their Ethernet switch.
IP configuration (System > Network interfaces > IP)
LAN configuration is specific to each peer.
Each peer must have a different IPv4 address and a different IPv6 address.
IP gateway configuration is peer-specific. Each peer can use a different gateway.
Note that the IP protocol is applied to all peers, because each peer must support the same protocols.
IPstatic routes (System >Network interfaces >Static routes)
Any static routes you add are peer-specific and you may create different routes on different peers if required. If you
want all peers in the cluster to be able to use the same static route, you must create the route on each peer.
System name (System > Administration)
The System name must be different for each peer in the cluster.
DNS servers and DNS host name (System > DNS)
DNS servers are specific to each peer. Each peer can use a different set of DNS servers.
The System host name and Domain name are specific to each peer.
NTP servers and time zone (System > Time)
The NTP servers are specific to each peer. Each peer may use one or more different NTP servers.
The Time zone is specific to each peer. Each peer may have a different local time.
SNMP (System > SNMP)
SNMP settings are specific to each peer. They can be different for each peer.
Logging (Maintenance >Logging)
The Event Log and Configuration Log on each peer only report activity for that particular VCS. The Log level and the
list of Remote syslog servers are specific to each peer. We recommend that you set up a remote syslog server to
166
which the logs of all peers can be sent. This allows you to have a global view of activity across all peers in the cluster.
See the logging section for further details.
Security certificates (Maintenance >Security certificates)
The trusted CA certificate, server certificate and certificate revocation lists (CRLs) used by the VCS must be
uploaded individually per peer.
Administration access (System > Administration)
The following system administration access settings are specific to each peer:
Serial port / console

SSH service
Web interface (over HTTPS)
Redirect HTTP requests to HTTPS
Automated protection service
Option keys (Maintenance >Option keys)
Option keys are specific to each peer. Each peer must have an identical set of option keys installed, but you must
purchase these separately for each peer in the cluster. However, this does not apply to traversal call licenses, non-
traversal call licenses and TURN relay licenses; these licenses can be installed on any cluster peer and are available
for use by any peer in the cluster.
Active Directory Service (Configuration > Authentication > Devices > Active Directory Service)
When configuring the connection to an Active Directory Service for device authentication, the NetBIOS machine
name (override), and domain administrator Username and Password are specific to each peer.
Conference Factory template (Applications > Conference Factory)
The template used by the Conference Factory application to route calls to the MCU is peer-specific, as it must be
unique for each peer in the cluster.
VCS front panel display mode (configurable through CLI only)
The xConfiguration Administration LCDPanel Mode CLI setting is specific to each peer.
Sharing Registrations Across Peers

When a cluster peer receives a search request (such as an LRQ, ARQ or an INVITE), it checks its own and its peers'
registration lists before responding. This allows all endpoints in the cluster to be treated as if they were registered
with a single VCS.
Peers are periodically queried to ensure they are still functioning. To prevent delays during call setup, any
nonfunctioning peers do not receive LRQs.
H.323 registrations
All the peers in a cluster share responsibility for their H.323 endpoint community. When an H.323 endpoint registers
with one peer, it receives a registration response which contains a list of alternate gatekeepers, populated with a
randomly ordered list of the IP addresses of all the other peers in that cluster.
If the endpoint loses contact with the initial peer, it will seek to register with one of the other peers. The random
ordering of the list of alternate peers ensures that endpoints that can only store a single alternate peer will failover
evenly across the cluster.
When using a cluster, you may want to reduce the registration Time to live on all peers in the cluster from the default
30 minutes. This setting determines how often endpoints are required to re-register with their VCS, and reducing it
means that if a cluster peer is unavailable, the endpoint will failover more quickly to an available peer.
Note:By reducing the registration time to live too much, you risk flooding the VCS with registration requests, which
will severely impact performance. This impact is proportional to the number of endpoints, so you should balance the
need for occasional quick failover against the need for continuous good performance.
167
To change this setting, go to Configuration > Protocols > H.323 > Gatekeeper > Time to live.
SIP registrations
The VCS supports multiple client-initiated connections (also referred to as "SIP Outbound") as outlined in RFC 5626.
This allows SIP endpoints that support RFC 5626 to be simultaneously registered to multiple VCS cluster peers. This
provides extra resiliency: if the endpoint loses its connection to one cluster peer it will still be able to receive calls via
one of its other registration connections.
You can also use DNS round-robin techniques to implement a registration failover strategy. Some SIP UAs, such as
Jabber Video, can be configured with a SIP server address that is an FQDN. If the FQDN resolves to a round-robin
DNS record populated with the IP addresses of all the peers in the cluster, then this could allow the endpoint to re-
register with another peer if its connection to the original peer is lost.
Sharing Bandwidth Across Peers

When clustering has been configured, all peers share the bandwidth available to the cluster.
Peers must be configured identically for all aspects of bandwidth control including subzones, links and pipes.
Peers share their bandwidth usage information with all other peers in the cluster, so when one peer is
consuming part or all of the bandwidth available within or from a particular subzone, or on a particular pipe,
this bandwidth will not be available for other peers.
For general information on how the VCS manages bandwidth, see the bandwidth control section.
Cluster Upgrades, Backup and Restore

Upgrading a cluster
Backing up a cluster
The backup and restore process can be used to save and restore cluster configuration information.
The backup process saves all configuration information for the cluster, regardless of the VCS used to make the
backup.
Restoring a cluster
You cannot restore data to a VCS that is a part of a cluster.
To restore previously backed up cluster configuration data you must follow this process:
1. Remove the VCS peer from the cluster so that it becomes a standalone VCS.
2. Restore the configuration data to the standalone VCS.
3. Build a new cluster using the VCS that now has the restored data.
4. Take each of the other peers out of their previous cluster and add them to the new cluster. See Setting Up a
Cluster, page 163 for more information about adding and removing cluster peers.
Clustering and Presence

Clustering supports the use of Presence.
All peers in the cluster must have identical SIP domain, Presence Server and Presence User Agent (PUA)
configuration.
If peers in the cluster have the PUA enabled, each peer publishes information about its own local registrations.
This information is routed to a Presence Server authoritative for the clusters domain.
If peers have the Presence Server enabled, the Presence database is replicated across all peers in the cluster.
When viewing presence status on a peer in a cluster:
168
Publishers shows all presentities across the cluster for whom presence information is being published.
Presentities shows any presentity for whom a subscription request has been received on the local VCS only.
Subscribers shows each endpoint from which a subscription request has been received on the local VCS
only.
Clustering and Cisco TMS

Cisco TMS version 13.2 or later is mandatory if your cluster is configured to use FindMe or Device Provisioning. From
X8.1 onwards you must use Cisco TelePresence Management Suite Provisioning Extension.
Size limitations for clusters and provisioning
A VCS cluster of any size supports up to:
10,000 FindMe accounts

10,000 users for provisioning
200,000 phonebook entries
Note that:
Small/Medium systems can support up to 2,500 device registrations per peer, subject to a maximum of 10,000
registrations per cluster. Typically this means one device per FindMe account.
Large systems can support up to 5,000 device registrations per peer (with a maximum of 20,000 registrations
per cluster). However, you are still limited to 10,000 FindMe accounts/users and 10,000 provisioned devices
per cluster.
If you need to provision more than 10,000 devices, your network will require additional VCS clusters with an
appropriately designed and configured dial plan.
About the Cluster Subzone

When two or more VCSs are clustered together, a new subzone is created within the clusters Local Zone. This is the
Cluster Subzone (see the diagram in the About Clusters, page 160 section). Any calls between two peers in the
cluster will briefly pass via this subzone during call setup.
The Cluster Subzone is (like the Traversal Subzone) a virtual subzone used for call routing only, and endpoints cannot
register to this subzone. After a call has been established between two peers, the Cluster Subzone will no longer
appear in the call route and the call will appear as having come from (or being routed to) the Default Subzone.
The two situations in which a call will pass via the Cluster Subzone are:
Calls between two endpoints registered to different peers in the cluster.

For example, Endpoint A is registered in the Default Subzone to Peer 1. Endpoint B is also registered in the
Default Subzone, but to Peer 2. When A calls B, the call route is shown on Peer 1 as Default Subzone ->
Cluster Subzone, and on Peer 2 as Cluster Subzone -> Default Subzone.
Calls received from outside the cluster by one peer, for an endpoint registered to another peer.
For example, we have a single VCS for the Branch Office, which is neighbored to a cluster of 4 VCSs at the
Head Office. A user in the Branch Office calls Endpoint A in the Head Office. Endpoint A is registered in the
Default Subzone to Peer 1. The call is received by Peer 2, as it has the lowest resource usage at that moment.
Peer 2 then searches for Endpoint A within the clusters Local Zone, and finds that it is registered to Peer 1.
Peer 2 then forwards the call to Peer 1, which forwards it to Endpoint A. In this case, on Peer 2 the call route
will be shown as Branch Office -> Default Subzone -> Cluster Subzone, and on Peer 1 as Cluster Subzone -
> Default Subzone.
Note that if Call signaling optimization is set to On and the call is H.323, the call will not appear on Peer 2, and on
Peer 1 the route will be Branch Office > Default Subzone.
169
Neighboring Between VCS Clusters

You can neighbor your local VCS (or VCS cluster) to a remote VCS cluster; this remote cluster could be a neighbor,
traversal client, or traversal server to your local VCS. In this case, when a call is received on your local VCS and is
passed via the relevant zone to the remote cluster, it will be routed to whichever peer in that neighboring cluster has
the lowest resource usage. That peer will then forward the call as appropriate to one of its:
locally registered endpoints (if the endpoint is registered to that peer)

peers (if the endpoint is registered to another peer in that cluster)
external zones (if the endpoint has been located elsewhere)
Lowest resource usage is determined by comparing the number of available traversal calls (maximum - current use)
on the peers, and choosing the peer with the highest number. Peers that are in maintenance mode are not
considered.
When configuring a connection to a remote cluster, you create a single zone and configure it with details of all the
peers in the cluster. Adding this information to the zone ensures that the call is passed to that cluster regardless of
the status of the individual peers.
You also need to enter the IP address of all peers in the remote cluster when the connection is via a neighbor or
traversal client zone. You do not do this for traversal server zones, as these connections are not configured by
specifying the remote system's IP address.
Note: Systems that are configured as peers must not also be configured as neighbors to each other, and vice versa.
Neighboring your clusters
To neighbor your local VCS (or VCS cluster) to a remote VCS cluster, you create a single zone to represent the cluster
and configure it with the details of all the peers in that cluster:
1. On your local VCS (or, if the local VCS is a cluster, on the primary peer), create a zone of the appropriate type.
This zone will represent the connection to the cluster.
2. In the Location section, enter the IP address or FQDN of each peer in the remote cluster in the Peer 1 to Peer
6 address fields.
Note that:
Ideally you should use IP addresses in these fields. If you use FQDNs instead, each FQDN must be different
and must resolve to a single IP address for each peer.
The order in which the peers in the remote VCS cluster are listed here does not matter.
Whenever you add an extra VCS to a cluster (to increase capacity or improve redundancy, for example) you
will need to modify any VCSs which neighbor to that cluster to let them know about the new cluster peer.
Troubleshooting cluster replication problems

Cluster replication can fail for a variety of reasons. This section describes the most common problems and how to
resolve them. For more detailed information:
Some peers have a different master peer defined
1. For each peer in the cluster, go to the System > Clustering page.
2. Ensure each peer identifies the same Configuration master.
Unable to reach the cluster configuration master peer
The VCS operating as the master peer could be unreachable for many reasons, including:
170
network access problems

VCS unit is powered down
incorrectly configured IP addresses
incorrectly configured IPsec keys - ensure each peer is configured with the same Cluster pre-shared key
value
different software versions
"Manual synchronization of configuration is required" alarms are raised on peer VCSs
1. Log in to the peer as admin through the CLI (available by default over SSH and through the serial port).
2. Type xCommand ForceConfigUpdate.
This will delete the non-master VCS configuration and force it to update its configuration from the master VCS.
Caution: Never issue this command on the master VCS, otherwise all configuration for the cluster will be lost.
171
Dial Plan and Call Processing
This section provides information about the pages that appear under the Calls, Dial plan, Transforms and Call Policy
sub-menus of the Configuration menu. These pages are used to configure the way in which the VCS receives and
processes calls.
Call Routing Process 172

Configuring Hop Counts 174
Configuring Dial Plan Settings 175
About Transforms and Search Rules 176
Example Searches and Transforms 182
Configuring Search Rules to Use an External Service 190
About Call Policy 192
Supported Address Formats 196
Dialing by IP Address 197
About URI Dialing 198
About ENUM Dialing 205
Configuring DNS Servers for ENUM and URI Dialing 210
Configuring Call Routing and Signaling 210
Identifying Calls 211
Disconnecting Calls 212
Call Routing Process

One of the functions of the VCS is to route calls to their appropriate destination. It does this by processing incoming
search requests in order to locate the given target alias. These search requests are received from:
locally registered endpoints

neighboring systems, including neighbors, traversal clients and traversal servers
endpoints on the public internet
There are a number of steps involved in determining the destination of a call, and some of these steps can involve
transforming the alias or redirecting the call to other aliases.
It is important to understand the process before setting up your dial plan so you can avoid circular references, where
an alias is transformed from its original format to a different format, and then back to the original alias. The VCS is
able to detect circular references. If it identifies one it will terminate that branch of the search and return a policy
loop detected error message.
How the VCS determines the destination of a call
The process followed by the VCS when attempting to locate a destination endpoint is described below.
172
1. The caller enters into their endpoint the alias or address of the destination endpoint. This alias or address can
be in a number of different address formats.
2. The destination address is sent from the callers endpoint to its local VCS (the VCS to which it is registered).
3. Any pre-search transforms are applied to the alias.
4. Any Call Policy is applied to the (transformed) alias. If this results in one or more new target aliases, the
process starts again with the new aliases checked against the pre-search transforms.
5. Any User Policy (if FindMe is enabled) is applied to the alias. If the alias is a FindMe ID that resolves to one or
more new target aliases, the process starts again with all the resulting aliases checked against pre-search
transforms and Call Policy.
6. The VCS then searches for the alias according to its search rules:
Note:The VCS deliberately only searches for the first destination alias it reads from an H.323 Location
Request. In very rare cases, this can lead to calls not being routed as expected.
A matching rule may apply a zone transform to the alias before sending the query on to its Target. A Target
can be one of the following types:
Local Zone: the endpoints and devices registered to the VCS.
Neighbor zone: one of the VCS's configured external neighbor zones, or a DNS or ENUM lookup zone.
Policy service: an external service or application, such as a Cisco TelePresence Conductor. The service
will return some CPL which could, for example, specify the zone to which the call should be routed, or it
could specify a new destination alias.
7. If the search returns a new URI or alias (for example, due to a DNS or ENUM lookup, or the response from a
policy service), the process starts again: the new URI is checked against any pre-search transforms, Call
Policy and User Policy are applied and a new VCS search is performed.
8. If the alias is found within the Local Zone, in one of the external zones, or a routing destination is returned by
the policy service, the VCS attempts to place the call.
9. If the alias is not found, it responds with a message to say that the call has failed.

173
Configuring Hop Counts

Each search request is assigned a hop count value by the system that initiates the search. Every time the request is
forwarded to another neighbor gatekeeper or proxy, the hop count value is decreased by a value of 1. When the hop
count reaches 0, the request will not be forwarded on any further and the search will fail.
For search requests initiated by the local VCS, the hop count assigned to the request is configurable on a zone-by-
zone basis. The zones hop count applies to all search requests originating from the local VCS that are sent to that
zone.
Search requests received from another zone will already have a hop count assigned. When the request is
subsequently forwarded on to a neighbor zone, the lower of the two values (the original hop count or the hop count
configured for that zone) is used.
174
For H.323, the hop count only applies to search requests. For SIP, the hop count applies to all requests sent to a zone
(affecting the Max-Forwards field in the request).
The hop count value can be between 1 and 255. The default is 15.
Note: if your hop counts are set higher than necessary, you may risk introducing loops into your network. In these
situations a search request will be sent around the network until the hop count reaches 0, consuming resources
unnecessarily. This can be prevented by setting the Call loop detection mode to On.
When dialing by URI or ENUM, the hop count used is that for the associated DNS or ENUM zone via which the
destination endpoint (or intermediary SIP proxy or gatekeeper) was found.
Configuring hop counts for a zone
Hop counts are configured on a zone basis. To configure the hop count for a zone:
1. Go to the Zones page (Configuration > Zones > Zones).

2. Click on the name of the zone you want to configure. You are taken to the Edit zone page.
3. In the Configuration section, in the Hop count field, enter the hop count value you want to use for this zone.
For full details on other zone options, see the Configuring Zones, page 143 section.
Configuring Dial Plan Settings

The Dial plan configuration page (Configuration > Dial plan > Configuration) is used to configure how the VCS
routes calls in specific call scenarios.
Calls to Determines the way in which the VCS attempts to call systems This setting applies to the call's
unknown IP which are not registered with it or one of its neighbors. destination address prior to any
addresses zone transforms, but after any
Direct: allows an endpoint to make a call to an unknown IP pre-search transforms, Call
address without the VCS querying any neighbors. The call Policy or User Policy rules have
setup would occur just as it would if the far end were been applied.
registered directly to the local system.
In addition to controlling calls,
Indirect: upon receiving a call to an unknown IP address, the this setting also determines the
VCS will query its neighbors for the remote address and if behavior of provisioning and
permitted will route the call through the neighbor. presence messages to SIP
devices, as these messages are
Off: endpoints registered directly to the VCS may only call an routed to IP addresses.
IP address of a system also registered directly to that VCS.
See Dialing by IP Address, page
The default is Indirect. 197 for more information.
Fallback alias The alias to which incoming calls are placed for calls where If no fallback alias is configured,
the IP address or domain name of the VCS has been given but calls that do not specify an alias
no callee alias has been specified. will be disconnected. See below
for more information.
About the Fallback Alias

The VCS could receive a call that is destined for it but which does not specify an alias. This could be for one of the
following reasons:
175
the caller has dialed the IP address of the VCS directly

the caller has dialed a domain name belonging to the VCS (either one of its configured SIP domains, or any
domain that has an SRV record that points at the IP address of the VCS), without giving an alias as a prefix
Normally such calls would be disconnected. However, such calls will be routed to the Fallback alias if it is specified.
Note that some endpoints do not allow users to enter an alias and an IP address to which the call should be placed.
Example usage
You may want to configure your fallback alias to be that of your receptionist, so that all calls that do not specify an
alias are still answered personally and can then be redirected appropriately.
For example, Example Inc has the domain of example.com. The endpoint at reception has the alias
[email protected]. They configure their VCS with a fallback alias of [email protected]. This means that any
calls made directly to example.com (that is, without being prefixed by an alias), are forwarded to
[email protected], where the receptionist can answer the call and direct it appropriately.
About Transforms and Search Rules

The VCS can be configured to use transforms and search rules as a part of its call routing process.
Transforms
Transforms are used to modify the alias in a search request if it matches certain criteria. You can transform an alias
by removing or replacing its prefix, suffix, or the entire string, and by the use of regular expressions.
This transformation can be applied to the alias at two points in the routing process: as a pre-search transform, and as
a zone transform.
Pre-search transforms are applied before any Call Policy or User Policy are applied and before the search
process is performed (see About Pre-Search Transforms, page 177 for more details).
Zone transforms are applied during the search process by each individual search rule as required. After the
search rule has matched an alias they can be used to change the target alias before the search request is sent
to a target zone or policy service (see Search and Zone Transform Process, page 179 for more details).
Search rules
Search rules are used to route incoming search requests to the appropriate target zones (including the Local Zone) or
policy services.
The VCS's search rules are highly configurable. You can:
define alias, IP address and pattern matches to filter searches to specific zones or policy services
define the priority (order) in which the rules are applied and stop applying any lower-priority search rules after
a match is found; this lets you reduce the potential number of search requests sent out, and speed up the
search process
set up different rules according to the protocol (SIP or H.323) or the source of the query (such as the Local
Zone, or a specific zone or subzone)
limit the range of destinations or network services available to unauthenticated devices by making specific
search rules applicable to authenticated requests only
use zone transforms to modify an alias before the query is sent to a target zone or policy service
Note that multiple search rules can refer to the same target zone or policy service. This means that you can specify
different sets of search criteria and zone transforms for each zone or policy service.
The VCS uses the protocol (SIP or H.323) of the incoming call when searching a zone for a given alias. If the search is
unsuccessful the VCS may then search the same zone again using the alternative protocol, depending on where the
search came from and the Interworking mode (Configuration > Protocols > Interworking):
176
If the request has come from a neighboring system and Interworking mode is set to Registered only, the VCS
searches the Local Zone using both protocols, and all other zones using the native protocol only (because it
will interwork the call only if one of the endpoints is locally registered).
If Interworking mode is set to On, or the request has come from a locally registered endpoint, the VCS
searches the Local Zone and all external zones using both protocols.
About Pre-Search Transforms

The pre-search transform function allows you to modify the alias in an incoming search request. The transformation is
applied by the VCS before any Call Policy or User Policy is applied, and before any searches take place.
It applies to all incoming search requests received from locally registered endpoints, neighbor, traversal client
and traversal server zones, and endpoints on the public internet.
It does not apply to requests received from peers (which are configured identically and therefore will have
already applied the same transform).
Each pre-search transform defines a string against which an alias is compared, and the changes to make to the alias
if it matches that string.
After the alias has been transformed, it remains changed and all further call processing is applied to the new alias.
Pre-search transforms are not applied to GRQ or RRQ messages received from endpoints registering with the
VCS; endpoints will be registered with the aliases as presented in these messages.
All peers in a cluster should be configured identically, including any pre-search transforms. Each VCS treats
search requests from any of its peers as having come from its own Local Zone, and does not re-apply any pre-
search transforms on receipt of the request.
Pre-search transform process
Up to 100 pre-search transforms can be configured. Each transform must have a unique priority number between 1
and 65534.
Every incoming alias is compared with each transform in order of priority, starting with that closest to 1. If and when a
match is made, the transform is applied to the alias and no further pre-search checks and transformations of the new
alias will take place. The new alias is then used for the remainder of the call routing process.
Further transforms of the alias may take place during the remainder of the search process. This may be as a
result of Call Policy (also known as Administrator Policy) or User Policy (if FindMe is enabled). If this is the
case, the pre-search transforms are re-applied to the new alias.
If you add a new pre-search transform that has the same priority as an existing transform, all transforms with a
lower priority (those with a larger numerical value) will have their priority incremented by one, and the new
transform will be added with the specified priority. However, if there are not enough slots left to move all the
priorities down, you will get an error message.
Configuring Pre-Search Transforms

The Transforms page (Configuration > Dial plan > Transforms) lists all the pre-search transforms currently
configured on the VCS. It is used to create, edit, delete, enable and disable transforms.
Aliases are compared against each transform in order of Priority, until a transform is found where the alias matches
the Pattern in the manner specified by the pattern Type. The alias is then transformed according to the Pattern
behavior and Replace string rules before the search takes place (either locally or to external zones).
After the alias has been transformed, it remains changed. and all further call processing is applied to the new alias.
Note that transforms also apply to any Publication, Subscription or Notify URIs handled by the Presence Services, and
to any Unified Communications messages.
177
Priority The priority of the transform. Priority can be from 1

to 65534, with 1 being the highest priority.
Transforms are applied in order of priority, and the
priority must be unique for each transform.
Description An optional free-form description of the transform. The description appears as a tooltip if you
hover your mouse pointer over a transform in
the list.
Pattern type How the Pattern string must match the alias for You can test whether a pattern matches a
the rule to be applied. Options are: particular alias and is transformed in the
expected way by using the Check pattern
Exact: the entire string must exactly match the tool (Maintenance > Tools > Check pattern).
alias character for character.
Prefix: the string must appear at the beginning of

the alias.
Suffix: the string must appear at the end of the

alias.
Pattern string Specifies the pattern against which the alias is The VCS has a set of predefined pattern
compared. matching variables that can be used to
match against certain configuration
elements.
Pattern Specifies how the matched part of the alias is

behavior modified. Options are:
Strip: the matching prefix or suffix is removed.
Replace: the matching part of the alias is

substituted with the text in the Replace string.
Add Prefix: prepends the Additional text to the

alias.
Add Suffix: appends the Additional text to the

alias.
Replace string The string to substitute for the part of the alias that Only applies if the Pattern behavior is
matches the pattern. Replace.
You can use regular expressions.
Additional text The string to add as a prefix or suffix. Only applies if the Pattern behavior is Add
Prefix or Add Suffix.
State Indicates if the transform is enabled or not. Use this setting to test configuration
changes, or to temporarily disable certain
rules. Any disabled rules still appear in the
rules list but are ignored.
Click on the transform you want to configure (or click New to create a new transform, or click Delete to remove a
transform).
178
Search and Zone Transform Process

The search rules and zone transform process is applied after all pre-search transforms, Call Policy and User Policy
have been applied.
The process is as follows:
1. The VCS applies the search rules in priority order (all rules with a priority of 1 are processed first, then priority 2
and so on) to see if the given alias matches the rules criteria based on the Source of the query and the rule
Mode.
2. If the match is successful, any associated zone transform (where the Mode is Alias pattern match and the
Pattern behavior is Replace or Strip) is applied to the alias.
3. The search rule's Target zone or policy service is queried (with the revised alias if a zone transform has been
applied) using the same protocol (SIP or H.323) as the incoming call request. Note that if there are many
successful matches for multiple search rules at the same priority level, every applicable Target is queried.
If the alias is found, the call is forwarded to that zone. If the alias is found by more than one zone, the call is
forwarded to the zone that responds first.
If the alias is not found using the native protocol, the query is repeated using the interworked protocol,
depending on the interworking mode.
If the search returns a new URI or alias (for example, due to an ENUM lookup, or the response from a policy
service), the entire Call Routing Process, page 172 starts again
4. If the alias is not found, the search rules with the next highest priority are applied (go back to step 1) until:
the alias is found, or
all target zones and policy services associated with search rules that meet the specified criteria have been
queried, or
a search rule with a successful match has an On successful match setting of Stop searching
Note the difference between a successful match (where the alias matches the search rule criteria) and an alias being
found (where a query sent to a target zone is successful). The Stop searching option provides better control over the
network's signaling infrastructure. For example, if searches for a particular domain should always be routed to a
specific zone this option lets you make the search process more efficient and stop the VCS from searching any other
zones unnecessarily.
Configuring Search Rules

The Search rules page (Configuration > Dial plan > Search rules) is used to configure how the VCS routes incoming
search requests to the appropriate target zones (including the Local Zone) or policy services.
The page lists all the currently configured search rules and lets you create, edit, delete, enable and disable rules. You
can click on a column heading to sort the list, for example by Target or Priority. If you hover your mouse pointer over a
search rule, the rule description (if one has been defined) appears as a tooltip.
You can also copy and then edit any existing search rule by clicking Clone in the Actions column.
Up to 2000 search rules can be configured. Priority 1 search rules are applied first, followed by all priority 2 search
rules, and so on.
Rule name A descriptive name for the search rule.
Description An optional free-form description of the search The description appears as a tooltip if you
rule. hover your mouse pointer over a rule in the list.
179
Priority The order in the search process that this rule is The default configuration means that the Local
applied, when compared to the priority of the Zone is searched first for all aliases. If the alias
other search rules. All Priority 1 search rules are is not found locally, all neighbor, traversal
applied first, followed by all Priority 2 search client and traversal server zones are searched,
rules, and so on. More than one rule can be and if they cannot locate the alias the request
assigned the same priority, in which case any is sent to any DNS and ENUM zones.
matching target zones are queried
simultaneously. The default is 100.
Protocol The source protocol for which the rule applies.

The options are Any, H.323 or SIP.
Source The sources of the requests for which this rule Named sources creates the ability for search
applies. rules to be applied as dial plan policy for
specific subzones and zones.
Any: locally registered devices, neighbor or
traversal zones, and any non-registered devices.
All zones: locally registered devices plus

neighbor or traversal zones.
Local Zone: locally registered devices only.
Named: a specific source zone or subzone for

which the rule applies.
Source name The specific source zone or subzone for which Only applies if the Source is set to Named.
the rule applies. Choose from the Default Zone,
Default Subzone or any other configured zone or
subzone.
Request Specifies whether the search rule applies only to This can be used in conjunction with the VCS's
must be authenticated search requests. Authentication Policy to limit the set of services
authenticated available to unauthenticated devices.
Mode The method used to test if the alias applies to the

search rule.
Alias pattern match: the alias must match the

specified Pattern type and Pattern string.
Any alias: any alias (providing it is not an IP

address) is allowed.
Any IP Address: the alias must be an IP address.
Pattern type How the Pattern string must match the alias for Applies only if the Mode is Alias Pattern Match.
the rule to be applied. Options are:
You can test whether a pattern matches a
Exact: the entire string must exactly match the particular alias and is transformed in the
alias character for character. expected way by using the Check pattern tool
(Maintenance > Tools > Check pattern).
the alias.

alias.
180
Pattern string The pattern against which the alias is compared. Applies only if the Mode is Alias Pattern Match.
The VCS has a set of predefined pattern

matching variables that can be used to match
against certain configuration elements.
Pattern Determines whether the matched part of the Applies only if the Mode is Alias Pattern Match.
behavior alias is modified before being sent to the target
zone or policy service If you want to transform the alias before
applying search rules you must use pre-search
Leave: the alias is not modified. transforms.
Strip: the matching prefix or suffix is removed

from the alias.
Replace: the matching part of the alias is

substituted with the text in the Replace string.
Replace The string to substitute for the part of the alias Only applies if the Pattern behavior is Replace.
string that matches the pattern.
You can use regular expressions.
On Controls the ongoing search behavior if the alias If Stop is selected, any rules with the same
successful matches the search rule. priority level as this rule are still applied.
match
Continue: continue applying the remaining
search rules (in priority order) until the endpoint
identified by the alias is found.
Stop: do not apply any more search rules, even if

the endpoint identified by the alias is not found in
the target zone.
Target The zone or policy service to query if the alias You can configure external policy services to
matches the search rule. use as a target of search rules. This could be
used, for example, to call out to an external
service or application, such as a TelePresence
Conductor. The service will return some CPL
which could, for example, specify a new
destination alias which would start the search
process over again.
State Indicates if the search rule is enabled or not. Use this setting to test configuration changes,
or to temporarily disable certain rules. Any
disabled rules still appear in the rules list but
are ignored.
Click on the rule you want to configure (or click New to create a new rule, or click Delete to remove a rule).
Useful tools to assist in configuring search rules
You can test whether the VCS can find an endpoint identified by a given alias, without actually placing a call
to that endpoint, by using the Locate tool (Maintenance > Tools > Locate).
You can test whether a pattern matches a particular alias and is transformed in the expected way by using the
Check pattern tool (Maintenance > Tools > Check pattern).
181
Example Searches and Transforms

You can use pre-search transforms and search rules separately or together. You can also define multiple search rules
that use a combination of Any alias and Alias pattern match modes, and apply the same or different priorities to each
rule. This will give you a great deal of flexibility in determining if and when a target zone is queried and whether any
transforms are applied.
This section gives the following examples that demonstrate how you might use pre-search transforms and search
rules to solve specific use cases in your deployment:
Filter queries to a zone using the original alias

Always query a zone using the original alias
Always query a zone using a transformed alias
Query a zone using both the original and transformed alias
Query a zone using two or more different transformed aliases
Stripping the domain from an alias to allow dialing from SIP to H.323 numbers
Stripping the domain from an alias to allow dialing from SIP to H.323 IDs
Allow calls to IP addresses only if they come from known zones
Filter Queries to a Zone Without Transforming

You can filter the search requests sent to a zone so that it is only queried for aliases that match certain criteria. For
example, assume all endpoints in your regional sales office are registered to their local Cisco VCS with a suffix of
@sales.example.com. In this situation, it makes sense for your Head Office VCS to query the Sales Office VCS only
when it receives a search request for an alias with a suffix of @sales.example.com. Sending any other search requests
to this particular VCS would take up resources unnecessarily. It would also be wasteful of resources to send search
requests for aliases that match this pattern to any other zone (there may be other lower priority search rules defined
that would also apply to these aliases). In which case setting On successful match to Stop means that the VCS will
not apply any further (lower priority) search rules.
To achieve the example described above, on your Head Office VCS create a zone to represent the Sales Office VCS,
and from the Create search rule page (Configuration > Dial plan > Search rules > New) set up an associated search
rule as follows:
Field Value
Rule name Regional sales office
Description Calls to aliases with a suffix of @sales.example.com
Priority 100
Source Any
Request must be No
authenticated
Mode Alias pattern match
Pattern type Suffix
Pattern string @sales.example.com
Pattern behavior Leave
On successful match Stop
Target Sales office
State Enabled
182
Always Query a Zone With Original Alias (No Transforms)

To configure a zone so that it is always sent search requests using the original alias, from the Create search rule
page (Configuration > Dial plan > Search rules > New), set up a search rule for that zone with a Mode of Any alias:
Field Value
Rule name Always query with original alias
Description Send search requests using the original alias
Priority 100
Source Any
Request must be No
authenticated
Mode Any alias
On successful match Continue
Target Head office
State Enabled
Query a Zone for a Transformed Alias

Note that the Any alias mode does not support alias transforms. If you want to always query a zone using a different
alias to that received, you need to use a mode of Alias pattern match in combination with a regular expression.
You may want to configure your dial plan so that when a user dials an alias in the format [email protected] the VCS
queries the zone for [email protected] instead.
To achieve this, from the Create search rule page (Configuration > Dial plan > Search rules > New) set up a search
rule as follows:
Field Value
Rule name Transform to example.co.uk
Description Transform example.com to example.co.uk
Priority 100
Source Any
Request must be No
authenticated
Pattern type Suffix
Pattern string example.com
Pattern behavior Replace
Replace string example.co.uk
Target zone Head office
State Enabled
183
Query a Zone for Original and Transformed Alias

You may want to query a zone for the original alias at the same time as you query it for a transformed alias. To do this,
configure one search rule with a Mode of Any alias, and a second search rule with a Mode of Alias pattern match
along with details of the transform to be applied. Both searches must be given the same Priority level.
For example, you may want to query a neighbor zone for both a full URI and just the name (the URI with the domain
removed). To achieve this, on your local VCS from the Create search rule page (Configuration > Dial plan > Search
rules > New) set up two search rules as follows:
Rule #1
Field Value
Rule name Overseas office - original alias
Description Query overseas office with the original alias
Priority 100
Source Any
Request must be No
authenticated
Mode Any alias
Target zone Overseas office
State Enabled
Rule #2
Field Value
Rule name Overseas office - strip domain
Description Query overseas office with domain removed
Priority 100
Source Any
Request must be No
authenticated
Pattern type Suffix
Pattern string @example.com
Pattern behavior Strip
State Enabled
Query a Zone for Two or More Transformed Aliases

Zones are queried in order of priority of the search rules configured against them.
184
It is possible to configure multiple search rules for the same zone each with, for example, the same Priority and an
identical Pattern string to be matched, but with different replacement patterns. In this situation, the VCS queries that
zone for each of the new aliases simultaneously. (Any duplicate aliases produced by the transforms are removed prior
to the search requests being sent out.) If any of the new aliases are found by that zone, the call is forwarded to the
zone. It is then up to the controlling system to determine the alias to which the call will be forwarded.
For example, you may want to configure your dial plan so that when a user dials an alias in the format
[email protected]. the VCS queries the zone simultaneously for both [email protected] and [email protected].
To achieve this, from the Create search rule page (Configuration > Dial plan > Search rules > New) set up two
search rules as follows:
Rule #1
Field Value
Rule name Transform to example.co.uk
Description Transform example.com to example.co.uk
Priority 100
Source Any
Request must be No
authenticated
Pattern type Suffix
Replace string example.co.uk
State Enabled
Rule #2
Field Value
Rule name Transform to example.net
Description Transform example.com to example.net
Priority 100
Source Any
Request must be No
authenticated
Pattern type Suffix
185
Field Value
Replace string example.net
State Enabled
Stripping @domain for Dialing to H.323 Numbers

SIP endpoints can only make calls in the form of URIs - for example name@domain. If the caller does not specify a
domain when placing the call, the SIP endpoint automatically appends its own domain to the number that is dialed.
So if you dial 123 from a SIP endpoint, the search will be placed for 123@domain. If the H.323 endpoint being dialed is
registered as 123, the VCS will be unable to locate the alias 123@domain and the call will fail.
If you have a deployment that includes both SIP and H.323 endpoints that register using a number, you will need to
set up the following pre-search transform and local zone search rules. Together these will let users place calls from
both SIP and H.323 endpoints to H.323 endpoints registered using their H.323 E.164 number only.
Pre-Search Transform
On the Create transforms page (Configuration > Dial plan > Transforms > New):
Field Value
Priority 1
Description Take any number-only dial string and append @domain
Pattern type Regex
Pattern string (\d+)
Replace string \1@domain
State Enabled
This pre-search transform takes any number-only dial string (such as 123) and appends the domain used in endpoint
AORs and URIs in your deployment. This ensures that calls made by SIP and H.323 endpoints result in the same URI.
Local Zone Search Rules

On the Create search rule page (Configuration > Dial plan > Search rules > New), create two new search rules as
follows:
Rule #1
Field Value
Rule name Dialing H.323 numbers
Description Transform aliases in format number@domain to number
Priority 50
Source Any
186
Field Value
Request must be No
authenticated
Pattern type Regex
Pattern string (\d+)@domain
Replace string \1
Target zone Local Zone
State Enabled
Rule #2
Field Value
Rule name Dialing H.323 numbers
Description Place calls to number@domain with no alias transform
Priority 60
Source Any
Request must be No
authenticated
Pattern type Regex
Pattern string (\d+)@domain
State Enabled
These search rules ensure that both the E.164 number and full URI are searched for, so that endpoints can still be
reached whether they have registered with an H.323 number (123) or a full URI (123@domain).
The first search rule takes any aliases in the format number@domain and transforms them into the format number.
To ensure that any endpoints that have actually registered with an alias in the format number@domain can also
still be reached, the lower-priority second search rule places calls to number@domain without transforming the
alias.
Transforms for Alphanumeric H.323 ID Dial Strings

This example builds on the Stripping @domain for dialing to H.323 numbers example. That example caters for
number-only dial strings, however H.323 IDs do not have to be purely numeric; they can contain alphanumeric (letters
and digits) characters.
187
This example follows the same model as the example mentioned above a pre-search transform and two local zone
search rules to ensure that endpoints can be reached whether they have registered with an H.323 ID or a full URI
but uses a different regex (regular expression) that supports alphanumeric characters.
Pre-Search Transform
On the Create transforms page (Configuration > Dial plan > Transforms > New):
Field Value
Priority 1
Description Append @domain to any alphanumeric dial string
Pattern type Regex
Pattern string ([^@]*)
Replace string \1@domain
State Enabled
This pre-search transform takes any alphanumeric dial string (such as 123abc) and appends the domain used in your
deployment to ensure that calls made by SIP and H.323 endpoints result in the same URI.
Local Zone Search Rules

On the Create search rule page (Configuration > Dial plan > Search rules > New), create two new search rules as
follows:
Rule #1
Field Value
Rule name Dialing H.323 strings
Description Transform aliases in format string@domain to string
Priority 40
Source Any
Request must be No
authenticated
Pattern type Regex
Pattern string (.+)@domain
Replace string \1
State Enabled
Rule #2
188
Field Value
Rule name Dialing H.323 strings with domain
Description Place calls to string@domain with no alias transform
Priority 50
Source Any
Request must be No
authenticated
Pattern type Regex
Pattern string (.+)@domain
State Enabled
These search rules ensure that both the E.164 number and full URI are searched for, so that endpoints can still be
reached whether they have registered with an H.323 ID (123abc) or a full URI (123abc@domain).
The first search rule takes any aliases in the format string@domain and transforms them into the format string.
To ensure that any endpoints that have actually registered with an alias in the format string@domain can also
still be reached, the lower-priority second search rule places calls to string@domain without transforming the
alias.
Allowing Calls to IP Addresses Only if They Come From Known Zones

In addition to making calls to aliases, calls can be made to specified IP addresses. To pass on such calls to the
appropriate target zones you must set up search rules with a Mode of Any IP address. To provide extra security you
can set the rule's Source option to All zones. This means that the query is only sent to the target zone if it originated
from any configured zone or the Local Zone.
To achieve the example described above, from the Create search rule page (Configuration > Dial plan > Search
rules > New) set up a search rule as follows:
Field Value
Rule name IP addresses from known zones
Description Allow calls to IP addresses only from a known zone
Priority 100
Source All zones
Request must be No
authenticated
Mode Any IP address
State Enabled
189
Configuring Search Rules to Use an External Service

The configuration process to set up the VCS to use an external policy service for search rules (dial plan) is broken
down into the following steps:
Configure the policy service to be used by search rules.

Configure the relevant search rules to direct a search to the policy service.
Configuring a policy service to be used by search rules
1. Go to Configuration > Dial plan > Policy services.

2. Click New.
3. Configure the fields on the Create policy service page as follows:
Name The name of the policy service.
Description An optional free-form description of the policy The description appears as a tooltip if you
service. hover your mouse pointer over a policy
service in the list.

below.
checking

190

query the service.
encrypted).
message.

4. Click Create policy service.

Configuring a search rule to direct a search to the policy service
1. Go to Configuration > Dial plan > Search rules.

2. Click New.
191
3. Configure the fields on the Create search rule page as appropriate for the searches you want to direct to the
external policy server.
This example shows how to divert calls to aliases ending in .meet to the external policy server:
Rule name A short name that describes the rule.
Description A free-form description of the rule.
Priority As required, for example 10.
Protocol As required, for example Any.
Source As required, for example Any.
Request must be Configure this setting according to your authentication policy.

authenticated
Mode As required, for example Alias pattern match.
Pattern type As required, for example Regex.
Pattern string As required, for example.*\[email protected]
Pattern behavior As required, for example Leave.
On successful match As required.
Note that if Stop is selected the VCS will not process any further search rules for
the original alias, but will restart the full call processing sequence if any new
aliases are returned in the CPL.
Target Select the policy service that was created in the previous step.
State Enabled
To divert all searches to the policy server you could set up 2 search rules that both target the policy service:
The first search rule with a Mode of Any alias.

The second search rule with a Mode of Any IP address.
4. Click Create search rule.
The VCS will direct all searches that match the specified pattern to the policy service server.
Your search rules must be configured in such a way that they will result in a match for the initial alias, and then either
not match or not return a reject for any aliases to which the policy server has routed the call.
About Call Policy

You can set up rules to control which calls are allowed, which calls are rejected, and which calls are to be redirected
to a different destination. These rules are known as Call Policy (or Administrator Policy).
If Call Policy is enabled and has been configured, each time a call is made the VCS will execute the policy in order to
decide, based on the source and destination of the call, whether to:
proxy the call to its original destination

redirect the call to a different destination or set of destinations
reject the call
Note: when enabled, Call Policy is executed for all calls going through the VCS.
You should:
192
use Call Policy to determine which callers can make or receive calls via the VCS
use Registration restriction policy to determine which aliases can or cannot register with the VCS
Configuring Call Policy

The Call Policy configuration page (Configuration > Call Policy> Configuration) is used to configure the VCS's Call
Policy mode and to upload local policy files.
Call Policy Mode

The Call Policy mode controls from where the VCS obtains its Call Policy configuration. The options are:
Local CPL: uses locally-defined Call Policy.

Policy service: uses an external policy service.
Off: Call Policy is not in use.
Each of these options are described in more detail below:
Local CPL
The Local CPL option uses the Call Policy that is configured locally on the VCS. If you choose Local CPL you must
then either:
configure basic Call Policy through the Call Policy rules page (Configuration > Call Policy > Rules) note
that this only lets you allow or reject specified calls, or
upload a Call Policy file that contains CPL script; however, due to the complexity of writing CPL scripts you
are recommended to use an external policy service instead
Only one of these two methods can be used at any one time to specify Call Policy. If a CPL script has been uploaded,
this takes precedence and you will not be able to use the Call Policy rules page; to use the page you must first delete
the CPL script that has been uploaded.
If Local CPL is enabled but no policy is configured or uploaded, then a default policy is applied that allows all calls,
regardless of source or destination.
The Policy service option is used if you want to refer all Call Policy decisions out to an external service. If you select
this option an extra set of configuration fields appear so that you can specify the connection details of the external
service. See Configuring Call Policy to Use an External Service, page 195 .
Configuring Call Policy Rules Using the Web Interface

The Call Policy rules page (Configuration > Call Policy > Rules) lists the web-configured (rather than uploaded via a
CPL file) Call Policy rules currently in place and allows you to create, edit and delete rules. It provides a mechanism
to set up basic Call Policy rules without having to write and upload a CPL script.
You cannot use the Call Policy rules page to configure Call Policy if a CPL file is already in place. If this is the case,
on the Call Policy configuration page (Configuration > Call Policy > Configuration) you will have the option to Delete
uploaded file. Doing so will delete the existing Call Policy that was put in place using a CPL script, and enable use of
the Call Policy rules page for Call Policy configuration.
Each rule specifies the Action to take for all calls from a particular Source alias to a particular Destination alias. If you
have more than one rule, you can Rearrange the order of priority in which these rules are applied.
If rules are not configured, the default policy is to allow all calls, regardless of source or destination.
193
Source The alias or IP address that the calling endpoint used to identify itself when See About Device
pattern placing the call. If this field is blank, the policy rule applies to all incoming calls Authentication,
from unauthenticated users, meaning calls where the endpoint making the call page 108 for more
is not either: information.
locally registered and authenticated with the VCS, or This field supports
regular expressions.
registered and authenticated to a neighbor which in turn has
authenticated with the local VCS
Destination The alias or IP address that the endpoint dialed to make the call. This field supports
pattern regular expressions.
Action Whether or not a call that matches the source and destination is permitted.
Allow: if both the Source and Destination aliases match those listed, call
processing will continue.
Reject: if both the Source and Destination aliases match those listed, the call
will be rejected.
Rearrange Each combination of Source and Destination is compared, in the order shown
on the Call Policy rules page, with the details of the call being made until a
match is found, at which point the call policy is applied. To move a particular
item to higher or lower in the list, thus giving the rule a higher or lower priority,
click on the and icons respectively.
Click on the rule you want to configure (or click New to create a new rule, or click Delete to remove a rule).
Configuring Call Policy Using a CPL Script

You can use CPL scripts to configure advanced Call Policy. To do this, you must first create and save the CPL script
as a text file, after which you upload it to the VCS. However, due to the complexity of writing CPL scripts you are
recommended to use an external policy service instead.
For information on the CPL syntax and commands that are supported by the VCS, see the CPL Reference, page 347
section.
Viewing existing CPL script
To view the Call Policy that is currently in place as an XML-based CPL script, go to the Call Policy configuration page
(Configuration > Call Policy > Configuration) and click Show Call Policy file.
If Call Policy is configured to use a CPL script, this shows you the script that was uploaded.
If Call Policy is configured by the Call Policy rules page, this shows you the CPL version of those call policy
rules.
If Call Policy mode is On but a policy has not been configured, this shows you a default CPL script that allows
all calls.
You may want to view the file to take a backup copy of the Call Policy, or, if Call Policy has been configured using the
Call Policy rules page you could take a copy of this CPL file to use as a starting point for a more advanced CPL script.
If Call Policy has been configured using the Call Policy rules page and you download the CPL file and then upload it
back to the VCS without editing it, the VCS will recognize the file and automatically add each rule back into the Call
Policy rules page.
About CPL XSD files
The CPL script must be in a format supported by the VCS. The Call Policy configuration page allows you to download
the XML schemas which are used to check scripts that are uploaded to the VCS. You can use the XSD files to check
194
in advance that your CPL script is valid. Two download options are available:
Show CPL XSD file: displays in your browser the XML schema used for the CPL script.
Show CPL Extensions XSD file: displays in your browser the XML schema used for additional CPL elements
supported by the VCS.
Uploading a CPL script
To upload a new CPL file:
1. Go to Configuration > Call Policy > Configuration.

2. From the Policy files section, in the Select the new Call Policy file field, enter the file name or Browse to the
CPL script you want upload.
3. Click Upload file.
The VCS polls for CPL script changes every 5 seconds, so the VCS will almost immediately start using the updated
CPL script. CPL scripts cannot be uploaded using the command line interface.
Deleting an existing CPL script
If a CPL script has already been uploaded, a Delete uploaded file button will be visible. Click it to delete the file.
Configuring Call Policy to Use an External Service

To configure Call Policy to refer all policy decisions out to an external service:
1. Go to Configuration > Call policy > Configuration.

2. Select a Call Policy mode of Policy service.
3. Configure the fields that are presented as follows:

below.
checking
195


query the service.
encrypted).
message.

4. Click Save.
The VCS should connect to the policy service server and start using the service for Call Policy decisions.
Any connection problems will be reported on this page. Check the Status area at the bottom of the page and
check for additional information messages against the Server address fields.
Supported Address Formats

The destination address that is entered using the callers endpoint can take a number of different formats, and this
affects the specific process that the VCS follows when attempting to locate the destination endpoint. The address
formats supported by the VCS are:
IP address, for example 10.44.10.1 or 3ffe:80ee:3706::10:35

H.323 ID, for example john.smith or [email protected] (note that an H.323 ID can be in the form of a URI)
E.164 alias, for example 441189876432 or 6432
URI, for example [email protected]
ENUM, for example 441189876432 or 6432
Each of these address formats may require some configuration of the VCS in order for them to be supported. These
configuration requirements are described below.
Dialing by IP Address
Dialing by IP address is necessary when the destination endpoint is not registered with any system (such as a VCS or
other gatekeeper). See the Dialing by IP Address, page 197 section for more information.
196
Endpoints registered to a VCS Expressway

Calls made by dialing the IP address of an H.323 endpoint registered directly with a VCS Expressway are forced to
route through the VCS Expressway. The call will therefore be subject to any restrictions configured on that system.
Dialing by H.323 ID or E.164 Alias

No special configuration is required to place a call using an H.323 ID or E.164 alias.
The VCS follows the usual call routing process, applying any transforms and then searching the Local Zone and
external zones for the alias, according to the search rules.
Note that SIP endpoints always register using an AOR in the form of a URI. You are recommended to ensure that
H.323 endpoints also register with an H.323 ID in the form of a URI to facilitate interworking.
Dialing by H.323 or SIP URI

When a user places a call using URI dialing, they will typically dial [email protected].
If the destination endpoint is locally registered or registered to a neighbor system, no special configuration is required
for the call to be placed. The VCS follows the usual search process, applying any transforms and then searching the
Local Zone and external zones for the alias, according to the search rules.
If the destination endpoint is not locally registered, URI dialing may make use of DNS to locate the destination
endpoint. To support URI dialing via DNS, you must configure the VCS with at least one DNS server and at least one
DNS zone.
Full instructions on how to configure the VCS to support URI dialing via DNS (both outbound and inbound) are given in
the URI dialing section.
Dialing by ENUM
ENUM dialing allows an endpoint to be contacted by a caller dialing an E.164 number - a telephone number - even if
that endpoint has registered using a different format of alias. The E.164 number is converted into a URI by the DNS
system, and the rules for URI dialing are then followed to place the call.
The ENUM dialing facility allows you to retain the flexibility of URI dialing while having the simplicity of being called
using just a number - particularly important if any of your callers are restricted to dialing using a numeric keypad.
To support ENUM dialing on the VCS you must configure it with at least one DNS server and the appropriate ENUM
zones.
Full instructions on how to configure the VCS to support ENUM dialing (both outbound and inbound) are given in the
ENUM dialing section.
Dialing by IP Address
Dialing by IP address is necessary when the destination endpoint is not registered with any system.
If the destination endpoint is registered, it may be possible to call it using its IP address but the call may not succeed if
the endpoint is on a private network or behind a firewall. For this reason you are recommended to place calls to
registered endpoints via other address formats, such as its AOR or H.323 ID. Similarly, callers outside of your network
should not try to contact endpoints within your network via their IP addresses.
Calls to unknown IP addresses
Although the VCS supports dialing by IP address, it is sometimes undesirable for the VCS to be allowed to place a call
directly to an IP address that is not local. Instead, you may want a neighbor to place the call on behalf of the VCS, or
not allow such calls at all. The Calls to unknown IP addresses setting (on the Dial plan configuration page)
configures how the VCS handles calls made to IP addresses which are not on its local network, or registered with it or
one of its neighbors.
The VCS considers an IP address to be "known" if it either:
197
is the IP address of a locally registered endpoint

falls within the IP address range of one of the subzone membership rules configured on the VCS
The VCS will always attempt to place calls to known IP addresses (providing there is a search rule for Any IP Address
against the Local Zone).
All other IP addresses are considered to be "unknown" and are handled by the VCS according to the Calls to
Unknown IP addresses setting:
Direct: the VCS attempts to place the call directly to the unknown IP address without querying any neighbors.
Indirect: the VCS forwards the search request to its neighbors in accordance with its normal search process,
meaning any zones that are the target of search rules with an Any IP Address mode. If a match is found and
the neighbors configuration allows it to connect a call to that IP address, the VCS will pass the call to that
neighbor for completion.
Off: the VCS will not attempt to place the call, either directly or indirectly to any of its neighbors.
The default setting is Indirect.
This setting applies to the call's destination address prior to any zone transforms, but after any pre-search transforms,
Call Policy or User Policy rules have been applied.
Note that in addition to controlling calls, this setting also determines the behavior of provisioning and presence
messages to SIP devices, as these messages are routed to IP addresses.
Calling unregistered endpoints
An unregistered endpoint is any device that is not registered with an H.323 gatekeeper or SIP registrar. Although most
calls are made between endpoints that are registered with such systems, it is sometimes necessary to place a call to
an unregistered endpoint.
There are two ways to call to an unregistered endpoint:
by dialing its URI (this requires that the local VCS is configured to support URI dialing, and a DNS record exists
for that URI that resolves to the unregistered endpoint's IP address)
by dialing its IP address
Recommended configuration for firewall traversal
When a VCS Expressway is neighbored with a VCS Control for firewall traversal, you should typically set Calls to
unknown IP addresses to Indirect on the VCS Control and Direct on the VCS Expressway. When a caller inside the
firewall attempts to place a call to an IP address outside the firewall, it will be routed as follows:
1. The call will go from the endpoint to the VCS Control with which it is registered.
2. As the IP address being called is not registered to that VCS, and its Calls to unknown IP addresses setting is
Indirect, the VCS will not place the call directly. Instead, it will query its neighbor VCS Expressway to see if
that system is able to place the call on the VCS Controls behalf. Note that you need to configure a search rule
for Any IP Address against the traversal server zone.
3. The VCS Expressway receives the call and because its Calls to unknown IP addresses setting is Direct, it will
make the call directly to the called IP address.
About URI Dialing

A URI address typically takes the form [email protected], where name is the alias and example.com is the domain.
URI dialing can make use of DNS to enable endpoints registered with different systems to locate and call each other.
Without DNS, the endpoints would need to be registered to the same or neighbored systems in order to locate each
other.
198
URI Dialing Without DNS

Without the use of DNS, calls made by a locally registered endpoint using URI dialing will be placed only if the
destination endpoint is also locally registered, or is accessible via a neighbor system. This is because these endpoints
would be located using the search and zone transform process, rather than a DNS query.
If you want to use URI dialing from your network without the use of DNS, you would need to ensure that all the
systems in your network were connected to each other by neighbor relationships - either directly or indirectly. This
would ensure that any one system could locate an endpoint registered to itself or any another system, by searching
for the endpoint's URI.
This does not scale well as the number of systems grows. It is also not particularly practical, as it means that
endpoints within your network will not be able to dial endpoints registered to systems outside your network (for
example when placing calls to another company) if there is not already a neighbor relationship between the two
systems.
If a DNS zone and a DNS server have not been configured on the local VCS, calls to endpoints that are not registered
locally or to a neighbor system could still be placed if the local VCS is neighbored (either directly or indirectly) with
another VCS that has been configured for URI dialing via DNS. In this case, any URI-dialed calls that are picked up by
search rules that refer to that neighbor zone will go via that neighbor, which will perform the DNS lookup.
This configuration is useful if you want all URI dialing to be made via one particular system, such as a VCS
Expressway.
If you do not want to use DNS as part of URI dialing within your network, then no special configuration is required.
Endpoints will register with an alias in the form of a URI, and when calls are placed to that URI the VCS will query its
local zone and neighbors for that URI.
If the VCS does not have DNS configured and your network includes H.323 endpoints, then in order for these
endpoints to be reachable using URI dialing either:
the H.323 endpoints should register with the VCS using an address in the format of a URI
an appropriate transform should be written to convert URIs into the format used by the H.323 registrations. An
example would be a deployment where H.323 endpoints register with an alias, and incoming calls are made
to [email protected]. A local transform is then configured to strip the @domain, and the search is made locally
for alias. See Stripping @domain for Dialing to H.323 Numbers, page 186 for an example of how to do this.
SIP endpoints always register with an AOR in the form of a URI, so no special configuration is required.
URI Dialing With DNS

By using DNS as part of URI dialing, it is possible to find an endpoint even though it may be registered to an unknown
system. The VCS uses a DNS lookup to locate the domain in the URI address and then queries that domain for the
alias. See the URI Resolution Process Using DNS, page 200 section for more information.
URI dialing via DNS is enabled separately for outgoing and incoming calls.
Outgoing calls
To enable your VCS to locate endpoints using URI dialing via DNS, you must:
configure at least one DNS zone and an associated search rule

configure at least one DNS server
This is described in the URI Dialing via DNS for Outgoing Calls, page 201 section.
Incoming calls
To enable endpoints registered to your VCS to receive calls from non-locally registered endpoints using URI dialing
via DNS, you must:
ensure all endpoints are registered with an AOR (SIP) or H.323 ID in the form of a URI
configure appropriate DNS records, depending on the protocols and transport types you want to use
199
This is described in the URI Dialing via DNS for Incoming Calls, page 203 section.
Firewall traversal calls
To configure your system so that you can place and receive calls using URI dialing through a firewall, see the URI
Dialing and Firewall Traversal, page 205 section.
URI Resolution Process Using DNS

When the VCS attempts to locate a destination URI address using the DNS system, the general process is as follows:
H.323
1. The VCS sends a query to its DNS server for an SRV record for the domain in the URI. (If more than one DNS
server has been configured on the VCS, the query will be sent to all servers at the same time, and all
responses will be prioritized by the VCS with only the most relevant SRV record being used.) If available, this
SRV record returns information (such as the FQDN and listening port) about either the device itself or the
authoritative H.323 gatekeeper for that domain.
If the domain part of the URI address was resolved successfully using an H.323 Location SRV record (that
is, for _ h323ls) then the VCS will send an A/AAAA record query for each name record returned. These will
resolve to one or more IP addresses, and the VCS then sends, in priority order, an LRQ for the full URI to
those IP addresses.
If the domain part of the URI address was resolved using an H.323 Call Signaling SRV record (that is, for _
h323cs) then the VCS will send an A/AAAA record query for each name record returned. These will resolve
to one or more IP addresses, and the VCS then routes the call, in priority order to the IP addresses returned
in those records. (An exception to this is where the original dial string has a port specified - for example,
[email protected]:1719 - in which case the address returned is queried via an LRQ for the full URI address.)
2. If a relevant SRV record cannot be located:
If the Include address record setting for the DNS zone being queried is set to On, the system will fall back
to looking for an A or AAAA record for the domain in the URI. If such a record is found, the call will be routed
to that IP address and the search will terminate. Note that if the A and AAAA records that are found at this
domain are for systems other than those that support SIP or H.323, the VCS will still forward the call to this
zone, and the call will therefore fail. For this reason, you are recommended to use the default setting of Off.
If the Include address record setting for the DNS zone being queried is set to Off, the VCS will not query
for A and AAAA records and instead will continue with the search, querying the remaining lower priority
zones.
SIP
The VCS supports the SIP resolution process as outlined in RFC 3263. An example of how the VCS implements this
process is as follows:
1. The VCS sends a NAPTR query for the domain in the URI. If available, the result set of this query describes a
prioritized list of SRV records and transport protocols that should be used to contact that domain.
If no NAPTR records are present in DNS for this domain name then the VCS will use a default list of _sips._
tcp.<domain>, _sip._tcp.<domain> and _sip._udp.<domain> for that domain as if they had been returned from
the NAPTR query.
The VCS sends SRV queries for each result returned from the NAPTR record lookup. A prioritized list of
A/AAAA records returned is built.
The VCS sends an A/AAAA record query for each name record returned by the SRV record lookup.
The above steps will result in a tree of IP addresses, port and transport protocols to be used to contact the target
domain. The tree is sub-divided by NAPTR record priority and then by SRV record priority. When the tree of
locations is used, the searching process will stop on the first location to return a response that indicates that the
target destination has been contacted.
2. If the search process does not return a relevant SRV record:

If the Include address record setting for the DNS zone being queried is set to On, the system will fall back
to looking for an A or AAAA record for the domain in the URI. If such a record is found, the call will be routed
200
to that IP address and the search will terminate. Note that if the A and AAAA records that are found at this
domain are for systems other than those that support SIP or H.323, the VCS will still forward the call to this
zone, and the call will therefore fail. For this reason, you are recommended to use the default setting of Off.
If the Include address record setting for the DNS zone being queried is set to Off, the VCS will not query
for A and AAAA records and instead will continue with the search, querying the remaining lower priority
zones.
URI Dialing via DNS for Outgoing Calls

When a user places a call using URI dialing, they will typically dial an address in the form [email protected] from their
endpoint. Below is the process that is followed when a URI address is dialed from an endpoint registered with your
VCS, or received as a query from a neighbor system:
1. The VCS checks its search rules to see if any of them are configured with a Mode of either:
Any alias, or
Alias pattern match with a pattern that matches the URI address
2. The associated target zones are queried, in rule priority order, for the URI.
If one of the target zones is a DNS zone, the VCS attempts to locate the endpoint through a DNS lookup. It
does this by querying the DNS server configured on the VCS for the location of the domain as per the URI
resolution process via DNS. If the domain part of the URI address is resolved successfully the request is
forwarded to those addresses.
If one of the target zones is a neighbor, traversal client or traversal server zones, those zones are queried for
the URI. If that system supports URI dialing via DNS, it may route the call itself.
Adding and configuring DNS zones
To enable URI dialing via DNS, you must configure at least one DNS zone. To do this:

2. Click New. You are taken to the Create zone page.
3. Enter a Name for the zone and select a Type of DNS.
201
4. Configure the DNS zone settings as follows:
Field Guidelines
Hop When dialing by URI via DNS, the hop count used is that configured for the DNS zone associated
count with the search rule that matches the URI address (if this is lower than the hop count currently
assigned to the call).
If URI address isn't matched to a DNS zone, the query may be forwarded to a neighbor. In this
case, the hop count used will be that configured for the neighbor zone (if this is lower than the
hop count currently assigned to the call).
H.323 The H.323 and SIP sections allow you to filter calls to systems and endpoints located via this
and SIP zone, based on whether the call is located using SIP or H.323 SRV lookups.
modes
Include This setting determines whether, if no NAPTR (SIP) or SRV (SIP and H.323) records have been
address found for the dialed alias via this zone, the VCS will then query for A and AAAA DNS records
record before moving on to query lower priority zones.
You are recommended to use the default setting of Off, meaning that the VCS will not query for A
and AAAA records, and instead will continue with the search, querying the remaining lower
priority zones. This is because, unlike for NAPTR and SRV records, there is no guarantee that the
A/AAAA records will point to a system capable of processing the relevant SIP or H.323 messages
(LRQs, Setups, etc.) - the system may instead be a web server that processes http messages, or
a mail server that processes mail messages. If this setting is On, when a system is found using
A/AAAA lookup, the VCS will send the signaling to that destination and will not continue the
search process. If the system does not support SIP or H.323, the call will fail.
Zone For most deployments, this option should be left as Default.

profile

Configuring search rules for DNS zones
If you want your local VCS to use DNS to locate endpoints outside your network, you must:
configure the DNS servers used by the VCS for DNS queries
create a DNS zone and set up associated search rules that use the Pattern string and Pattern type fields to
define the aliases that will trigger a DNS query
For example, rules with:
a Pattern string of .*@.* and a Pattern type of Regex will query DNS for all aliases in the form of typical URI
addresses
a Pattern string of (?!.*@example.com$).* and a Pattern type of Regex will query DNS for all aliases in the
form of typical URI addresses except those for the domain example.com
To set up further filters, configure extra search rules that target the same DNS zone. You do not need to create new
DNS zones for each rule unless you want to filter based on the protocol (SIP or H.323) or use different hop counts.
Note: you are not recommended to configure search rules with a Mode of Any alias for DNS zones. This will result in
DNS always being queried for all aliases, including those that may be locally registered and those that are not in the
form of URI addresses.
202
URI Dialing via DNS for Incoming Calls

DNS record types
The ability of the VCS to receive incoming calls (and other messages, such as registrations) made using URI dialing
via DNS relies on the presence of DNS records for each domain the VCS is hosting.
These records can be of various types including:
A records, which provide the IPv4 address of the VCS

AAAA records, which provide the IPv6 address of the VCS
Service (SRV) records, which specify the FQDN of the VCS and the port on it to be queried for a particular
protocol and transport type.
NAPTR records, which specify SRV record and transport preferences for a SIP domain.
You must provide an SRV or NAPTR record for each combination of domain hosted and protocol and transport type
enabled on the VCS.
Incoming call process
When an incoming call has been placed using URI dialing via DNS, the VCS will have been located by the calling
system using one of the DNS record lookups described above. The VCS will receive the request containing the dialed
URI in the form [email protected]. This will appear as coming from the Default Zone. The VCS will then search for
the URI in accordance with its normal call routing process, applying any pre-search transforms, Call Policy and
FindMe policy, then searching its Local Zone and other configured zones, in order of search rule priority.
SRV record format
The format of SRV records is defined by RFC 2782 as:
_Service._Proto.Name TTL Class SRV Priority Weight Port Target
For the VCS, these are as follows:
_Service and _Proto will be different for H.323 and SIP, and will depend on the protocol and transport type
being used
Name is the domain in the URI that the VCS is hosting (such as example.com)
Port is the IP port on the VCS that has been configured to listen for that particular service and protocol
combination
Target is the FQDN of the VCS.
Configuring H.323 SRV Records

Annex O of ITU Specification: H.323 defines the procedures for using DNS to locate gatekeepers and endpoints and
for resolving H.323 URL aliases. It also defines parameters for use with the H.323 URL.
The VCS supports the location, call and registration service types of SRV record as defined by this Annex.
Location service SRV records
Location records are required for gatekeepers that route calls to the VCS. For each domain hosted by the VCS, you
should configure a location service SRV record as follows:
_Service is _h323ls
_Proto is _udp
Port is the port number that has been configured from Configuration > Protocols > H.323 as the Registration
UDP port
203
Call signaling SRV records

Call signaling SRV records (and A/AAAA records) are intended primarily for use by non-registered endpoints which
cannot participate in a location transaction, exchanging LRQ and LCF. For each domain hosted by the VCS, you
should configure a call signaling SRV record as follows:
_Service is _h323cs
_Proto is _tcp
Port is the port number that has been configured from Configuration > Protocols > H.323 as the Call signaling
TCP port.
Registration service SRV records
Registration records are used by devices attempting to register to the VCS. For each domain hosted by the VCS, you
should configure a registration service SRV record as follows:
_Service is _h323rs
_Proto is _udp
Port is the port number that has been configured from Configuration > Protocols > H.323 as the Registration
UDP port
Configuring SIP SRV Records

RFC 3263 describes the DNS procedures used to resolve a SIP URI into the IP address, port, and transport protocol of
the next hop to contact.
If you want the VCS to be contactable using SIP URI dialing, you should configure an SRV record for each SIP
transport protocol enabled on the VCS (that is, UDP, TCP or TLS) as follows:
Valid combinations of _Service and _Proto are:

_sips._tcp
_sip._tcp
_sip._udp (although not recommended)
Port is the IP port number that has been configured from Configuration > Protocols > SIP as the port for that
particular transport protocol.
_sip._udp is not recommended because SIP messages for video systems are too large to be carried on a packet
based (rather than stream based) transport. UDP is often used for audio only devices. Also, UDP tends to be spammed
more than TCP or TLS.
Example DNS Record Configuration

A company with the domain name example.com wants to enable incoming H.323 and SIP calls using URI addresses in
the format [email protected]. The VCS hosting the domain has the FQDN vcs.example.com.
Their DNS records would typically be as follows:
SRV record for _h323ls._udp.example.com returns vcs.example.com

SRV record for _h323cs._tcp.example.com returns vcs.example.com
SRV record for _h323rs._tcp.example.com returns vcs.example.com
NAPTR record for example.com returns
_sip._tcp.example.com and
_sips._tcp.example.com
SRV record for _sip._tcp.example.com returns vcs.example.com
SRV record for _sips._tcp.example.com returns vcs.example.com
204
A record for vcs.example.com returns the IPv4 address of the VCS

AAAA record for vcs.example.com returns the IPv6 address of the VCS
How you add the DNS records depends on the type of DNS server you are using. Instructions for setting up two
common DNS servers are given in the DNS Configuration Examples, page 362 section.
For locally registered H.323 endpoints to be reached using URI dialing, either:
the H.323 endpoints should register with the VCS using an address in the format of a URI
an appropriate transform should be written to convert URIs into the format used by the H.323 registrations. An
example would be a deployment where H.323 endpoints register with an alias, and incoming calls are made to
[email protected]. A local transform is then configured to strip the @domain, and the search is made locally
for alias. See Stripping @domain for Dialing to H.323 Numbers, page 186 for an example of how to do this.
SIP endpoints always register with an AOR in the form of a URI, so no special configuration is required.
Several mechanisms could have been used to locate the VCS. You may want to enable calls placed to user@<IP_
address> to be routed to an existing registration for [email protected]. In this case you would configure a pre-search
transform that would strip the IP_address suffix from the incoming URI and replace it with the suffix of example.com.
URI Dialing and Firewall Traversal

If URI dialing via DNS is being used in conjunction with firewall traversal, DNS zones should be configured on the VCS
Expressway and any VCSs on the public network only. VCSs behind the firewall should not have any DNS zones
configured. This will ensure that any outgoing URI calls made by endpoints registered with the VCS will be routed
through the VCS Expressway.
In addition, the DNS records for incoming calls should be configured with the address of the VCS Expressway as the
authoritative gatekeeper/proxy for the enterprise (the DNS Configuration Examples, page 362 section for more
information). This ensures that incoming calls placed using URI dialing enter the enterprise through the VCS
Expressway, allowing successful traversal of the firewall.
About ENUM Dialing

ENUM dialing allows an endpoint to be contacted by a caller dialing an E.164 number - a telephone number - even if
that endpoint has registered using a different format of alias.
Using ENUM dialing, when an E.164 number is dialed it is converted into a URI using information stored in DNS. The
VCS then attempts to find the endpoint based on the URI that has been returned.
The ENUM dialing facility allows you to retain the flexibility of URI dialing while having the simplicity of being called
using just a number - particularly important if any of your callers are restricted to dialing using a numeric keypad.
The VCS supports outward ENUM dialing by allowing you to configure ENUM zones on the VCS. When an ENUM zone
is queried, this triggers the VCS to transform the E.164 number that was dialed into an ENUM domain which is then
queried for using DNS.
Note: ENUM dialing relies on the presence of relevant DNS NAPTR records for the ENUM domain being queried. These
are the responsibility of the administrator of that domain.
ENUM Dialing Process

When the VCS attempts to locate a destination endpoint using ENUM, the general process is as follows:
1. The user dials the E.164 number from their endpoint.

2. The VCS converts the E.164 number into an ENUM domain as follows:
a. The digits are reversed and separated by a dot.
b. The name of the domain that is hosting the NAPTR records for that E.164 number is added as a suffix.
3. DNS is then queried for the resulting ENUM domain.
205
4. If a NAPTR record exists for that ENUM domain, this will advise how the number should be converted into one
(or possibly more) H.323/SIP URIs.
5. The VCS begins the search again, this time for the converted URI as per the URI dialing process. Note that this
is considered to be a completely new search, and so pre-search transforms and Call Policy will therefore
apply.
Enabling ENUM Dialing

ENUM dialing is enabled separately for incoming and outgoing calls.
Outgoing calls
To allow locally registered endpoints to dial out to other endpoints using ENUM, you must:
configure at least one ENUM zone, and

configure at least one DNS Server
This is described in the ENUM Dialing for Outgoing Calls, page 206 section.
Incoming calls
To enable endpoints in your enterprise to receive incoming calls from other endpoints via ENUM dialing, you must
configure a DNS NAPTR record mapping your endpoints E.164 numbers to their SIP/H.323 URIs. See the ENUM
dialing for incoming calls, page 209 section for instructions on how to do this.
Note: if an ENUM zone and a DNS server have not been configured on the local VCS, calls made using ENUM dialing
could still be placed if the local VCS is neighbored with another VCS that has been appropriately configured for
ENUM dialing. Any ENUM dialed calls will go via the neighbor. This configuration is useful if you want all ENUM dialing
from your enterprise to be configured on one particular system.
ENUM Dialing for Outgoing Calls

For a local endpoint to be able to dial another endpoint using ENUM via your VCS, the following conditions must be
met:
There must be a NAPTR record available in DNS that maps the called endpoints E.164 number to its URI. It is
the responsibility of the administrator of the enterprise to which the called endpoint belongs to provide this
record, and they will only make it available if they want the endpoints in their enterprise to be contactable via
ENUM dialing.
You must configure an ENUM zone on your local VCS. This ENUM zone must have a DNS Suffix that is the
same as the domain where the NAPTR record for the called endpoint is held.
You must configure your local VCS with the address of at least one DNS server that it can query for the NAPTR
record (and if necessary any resulting URI).
After the ENUM process has returned one or more URIs, a new search will begin for each of these URIs in accordance
with the URI dialing process. If the URIs belong to locally registered endpoints, no further configuration is required.
However, if one or more of the URIs are not locally registered, you may also need to configure a DNS zone if they are
to be located using a DNS lookup.
Calling process
The process below is followed when an ENUM (E.164) number is dialed from an endpoint registered with your VCS:
1. The user dials the E.164 number from their endpoint.

2. The VCS initiates a search for the E.164 number as dialed. It follows the usual call routing process.
206
3. After applying any pre-search transforms, the VCS checks its search rules to see if any of them are configured
with a Mode of either:
Any alias, or
Alias pattern match with a pattern that matches the E.164 number
4. The target zones associated with any matching search rules are queried in rule priority order.
If a target zone is a neighbor zone, the neighbor is queried for the E.164 number. If the neighbor supports
ENUM dialing, it may route the call itself.
If a target zone is an ENUM zone, the VCS attempts to locate the endpoint through ENUM. As and when
each ENUM zone configured on the VCS is queried, the E.164 number is transformed into an ENUM domain
as follows:
1. The digits are reversed and separated by a dot.
2. The DNS suffix configured for that ENUM zone is appended.
5. DNS is then queried for the resulting ENUM domain.
6. If the DNS server finds at that ENUM domain a NAPTR record that matches the transformed E.164 number (that
is, after it has been reversed and separated by a dot), it returns the associated URI to the VCS.
7. The VCS then initiates a new search for that URI (maintaining the existing hop count). The VCS starts at the
beginning of the search process (applying any pre-search transforms, then searching local and external zones
in priority order).From this point, as it is now searching for a SIP/H.323 URI, the process for URI dialing is
followed.
In this example, we want to call Fred at Example Corp. Freds endpoint is actually registered with the URI
[email protected], but to make it easier to contact him his system administrator has configured a DNS NAPTR record
mapping this alias to his E.164 number: +44123456789.
We know that the NAPTR record for example.com uses the DNS domain of e164.arpa.
1. We create an ENUM zone on our local VCS with a DNS suffix of e164.arpa.
2. We configure a search rule with a Pattern match mode of Any alias, and set the Target to the ENUM zone.
This means that ENUM will always be queried regardless of the format of the alias being searched for.
3. We dial 44123456789 from our endpoint.
4. The VCS initiates a search for a registration of 44123456789 and the search rule of Any alias means the ENUM
zone is queried. (Note that other higher priority searches could potentially match the number first.)
5. Because the zone being queried is an ENUM zone, the VCS is automatically triggered to transform the number
into an ENUM domain as follows:
a. The digits are reversed and separated by a dot: 9.8.7.6.5.4.3.2.1.4.4.
b. The DNS suffix configured for this ENUM zone, e164.arpa, is appended. This results in a transformed
domain of 9.8.7.6.5.4.3.2.1.4.4.e164.arpa.
6. DNS is then queried for that ENUM domain.
7. The DNS server finds the domain and returns the information in the associated NAPTR record. This tells the
VCS that the E.164 number we have dialed is mapped to the SIP URI of [email protected].
8. The VCS then starts another search, this time for [email protected]. From this point the process for URI dialing
is followed, and results in the call being forwarded to Freds endpoint.
Configuring Zones and Search Rules for ENUM Dialing

To support ENUM dialing, you must configure an ENUM zone and related search rules for each ENUM service used by
remote endpoints.
Adding and configuring ENUM zones
To set up an ENUM zone:
207

2. Click New. You are taken to the Create zone page.
3. Enter a Name for the zone and select a Type of ENUM.
4. Configure the ENUM zone settings as follows:
Field Guidelines
Hop count The hop count specified for an ENUM zone is applied in the same manner as hop counts for
other zone types. The currently applicable hop count is maintained when the VCS initiates a
new search process for the alias returned by the DNS lookup.
DNS suffix The suffix to append to a transformed E.164 number to create an ENUM host name. It
represents the DNS zone (in the domain name space) to be queried for a NAPTR record.
H.323 mode Controls if H.323 records are looked up for this zone.
SIP mode Controls if SIP records are looked up for this zone.

Note that:
Any number of ENUM zones may be configured on the VCS. You should configure at least one ENUM zone for
each DNS suffix that your endpoints may use.
Normal search rule pattern matching and prioritization rules apply to ENUM zones.
You must also configure the VCS with details of DNS servers to be used when searching for NAPTR records.
Configuring search rules for ENUM zones
If you want locally registered endpoints to be able to make ENUM calls via the VCS, then at a minimum you should
configure an ENUM zone and a related search rule with:
a DNS suffix of e164.arpa (the domain specified by the ENUM standard)

a related search rule with a Mode of Any alias
This results in DNS always being queried for all types of aliases, not just ENUMs. It also means that ENUM dialing will
only be successful if the enterprise being dialed uses the e164.arpa domain. To ensure successful ENUM dialing, you
must configure an ENUM zone for each domain that holds NAPTR records for endpoints that callers in your enterprise
might want to dial.
You can then set up search rules that filter the queries sent to each ENUM zone as follows:
use a Mode of Alias pattern match

use the Pattern string and Pattern type fields to define the aliases for each domain that will trigger an ENUM
lookup
For example, you want to enable ENUM dialing from your network to a remote office in the UK where the endpoints
E.164 numbers start with 44. You would configure an ENUM zone on your VCS, and then an associated search rule
with:
Mode of Alias pattern match

Pattern string of 44
Pattern type of Prefix
This results in an ENUM query being sent to that zone only when someone dials a number starting with 44.
208
Configuring transforms for ENUM zones

You can configure transforms for ENUM zones in the same way as any other zones (see the Search and Zone
Transform Process, page 179 section for full information).
Any ENUM zone transforms are applied before the number is converted to an ENUM domain.
For example, you want to enable ENUM dialing from your network to endpoints at a remote site using a prefix of 8
followed by the last 4 digits of the remote endpoints E.164 number. You would configure an ENUM zone on your VCS
and then an associated search rule with:
Mode of Alias pattern match

Pattern string of 8(\d{4})
Pattern type of Regex
Pattern behavior of Replace
Replace string of 44123123(\1)
With this configuration, it is the resulting string (44123123xxxx) that is converted into an ENUM domain and queried for
via DNS.
To verify you have configured your outward ENUM dialing correctly, use the Locate tool (Maintenance > Tools >
Locate) to try to resolve an E.164 alias.
ENUM dialing for incoming calls

For your locally registered endpoints to be reached using ENUM dialing, you must configure a DNS NAPTR record that
maps your endpoints E.164 numbers to their SIP/H.323 URIs. This record must be located at an appropriate DNS
domain where it can be found by any systems attempting to reach you by using ENUM dialing.
About DNS domains for ENUM
ENUM relies on the presence of NAPTR records to provide the mapping between E.164 numbers and their SIP/H.323
URIs.
RFC 3761, which is part of a suite of documents that define the ENUM standard, specifies that the domain for ENUM -
where the NAPTR records should be located for public ENUM deployments - is e164.arpa. However, use of this
domain requires that your E.164 numbers are assigned by an appropriate national regulatory body. Not all countries
are yet participating in ENUM, so you may want to use an alternative domain for your NAPTR records. This domain
could reside within your corporate network (for internal use of ENUM) or it could use a public ENUM database such as
http://www.e164.org.
Configuring DNS NAPTR records

ENUM relies on the presence of NAPTR records, as defined by RFC 2915. These are used to obtain an H.323 or SIP
URI from an E.164 number.
The record format that the VCS supports is:
order flag preference service regex replacement
where:
order and preference determine the order in which NAPTR records are processed. The record with the lowest
order is processed first, with those with the lowest preference being processed first in the case of matching
order.
flag determines the interpretation of the other fields in this record. Only the value u (indicating that this is a
terminal rule) is currently supported, and this is mandatory.
service states whether this record is intended to describe E.164 to URI conversion for H.323 or for SIP. Its
value must be either E2U+h323 or E2U+SIP.
regex is a regular expression that describes the conversion from the given E.164 number to an H.323 or SIP
209
URI.
replacement is not currently used by the VCS and should be set to . (the full stop character).
Non-terminal rules in ENUM are not currently supported by the VCS. For more information on these, see section 2.4.1
of RFC 3761.
For example, the record:
IN NAPTR 10 100 "u" "E2U+h323" "!^(.*)$!h323:\[email protected]!" .
would be interpreted as follows:
10 is the order
100 is the preference
u is the flag
E2U+h323 states that this record is for an H.323 URI
!^(.*)$!h323:\[email protected]! describes the conversion:
! is a field separator
the first field represents the string to be converted. In this example, ^(.*)$ represents the entire E.164
number
the second field represents the H.323 URI that will be generated. In this example, h323:\[email protected]
states that the E.164 number will be concatenated with @example.com. For example, 1234 will be mapped to
[email protected].
. shows that the replacement field has not been used.
Configuring DNS Servers for ENUM and URI Dialing

DNS servers are required to support ENUM and URI dialing:
ENUM dialing: to query for NAPTR records that map E.164 numbers to URIs
URI dialing: to look up endpoints that are not locally registered or cannot be accessed via neighbor systems
To configure the DNS servers used by the VCS for DNS queries:
1. Go to the DNS page (System > DNS).

2. Enter in the Address 1 to Address 5 fields the IP addresses of up to 5 DNS servers that the VCS will query
when attempting to locate a domain. These fields must use an IP address, not a FQDN.
Configuring Call Routing and Signaling

The Call routing page (Configuration > Call routing) is used to configure the VCS's call routing and signaling
functionality.
Call Signaling Optimization

Calls are made up of two components - signaling and media. For traversal calls, the VCS always handles both the
media and the signaling. For non-traversal calls, the VCS does not handle the media, and may or may not need to
handle the signaling.
The Call signaling optimization setting specifies whether the VCS removes itself, where it can, from the call
signaling path after the call has been set up. The options for this setting are:
Off: the VCS always handles the call signaling. The call consumes either a traversal call license or a local
(non-traversal) call license on the VCS.
210
On: the VCS handles the call signaling when the call is one of:
a traversal call
an H.323 call that has been modified by Call Policy or FindMe such that:
the call resolves to more than one alias
the source alias of the call has been modified to display the associated FindMe ID
the FindMe has a "no answer" or "busy" device configured
one of the endpoints in the call is locally registered
a SIP call where the incoming transport protocol (UDP, TCP, TLS) is different from the outgoing protocol
In all other cases the VCS removes itself from the call signaling path after the call has been set up. The VCS
does not consume a call license for any such calls, and the call signaling path is simplified. This setting is
useful in a hierarchical dial plan, when used on the directory VCS. In such deployments the directory VCS is
used to look up and locate endpoints and it does not have any endpoints registered directly to it.
Call Loop Detection Mode

Your dial plan or that of networks to which you are neighbored may be configured in such a way that there are
potential signaling loops. An example of this is a structured dial plan, where all systems are neighbored together in a
mesh. In such a configuration, if the hop counts are set too high, a single search request may be sent repeatedly
around the network until the hop count reaches 0, consuming resources unnecessarily.
The VCS can be configured to detect search loops within your network and terminate such searches through the Call
loop detection mode setting, thus saving network resources. The options for this setting are:
On: the VCS will fail any branch of a search that contains a loop, recording it as a level 2 "loop detected"
event. Two searches are considered to be a loop if they meet all of the following criteria:
have same call tag
are for the same destination alias
use the same protocol
originate from the same zone
Off: the VCS will not detect and fail search loops. You are recommended to use this setting only in advanced
deployments.
Identifying Calls
Each call that passes through the VCS is assigned a Call ID and a Call Serial Number. Calls also have a Call Tag
assigned if one does not already exist.
Call ID
The VCS assigns each call currently in progress a different Call ID. The Call ID numbers start at 1 and go up to the
maximum number of calls allowed on that system.
Each time a call is made, the VCS will assign that call the lowest available Call ID number. For example, if there is
already a call in progress with a Call ID of 1, the next call will be assigned a Call ID of 2. If Call 1 is then disconnected,
the third call to be made will be assigned a Call ID of 1.
The Call ID is not therefore a unique identifier: while no two calls in progress at the same time will have the same Call
ID, the same Call ID will be assigned to more than one call over time.
Note that the VCS web interface does not show the Call ID.
Call Serial Number
The VCS assigns a unique Call Serial Number to every call passing through it. No two calls on a VCS will ever have
the same Call Serial Number. A single call passing between two or more VCSs will be identified by a different Call
Serial Number on each system.
211
Call Tag
Call Tags are used to track calls passing through a number of VCSs. When the VCS receives a call, it checks to see if
there is a Call Tag already assigned to it. If so, the VCS will use the existing Call Tag; if not, it will assign a new Call
Tag to the call. This Call Tag is then included in the calls details when the call is forwarded on. A single call passing
between two or more VCSs will be assigned a different Call Serial Number each time it arrives at a VCS (including
one it has already passed through) but can be identified as the same call by use of the Call Tag. This is particularly
useful if you are using a remote syslog server to collate events across a number of VCSs in your network.
The Call Tag also helps identify loops in your network - it is used as part of the automatic call loop detection feature,
and you can also search the Event Log for all events relating to a single call tag. Loops occur when a query is sent to
a neighbor zone and passes through one or more systems before being routed back to the original VCS. In this
situation the outgoing and incoming query will have different Call Serial Numbers and may even be for different
destination aliases (depending on whether any transforms were applied). However, the call will still have the same
Call Tag.
Note: If a call passes through a system that is not a VCS or TelePresence Conductor then the Call Tag information will
be lost.
Identifying Calls in the CLI

To control a call using the CLI, you must reference the call using either its Call ID or Call Serial Number. These can be
obtained using the command:
xStatus Calls
This returns details of each call currently in progress in order of their Call ID. The second line of each entry lists the
Call Serial Number, and the third lists the Call Tag.
Disconnecting Calls
Disconnecting a call using the web interface
To disconnect one or more existing calls using the web interface:
1. Go to the Calls page (Status > Calls).

2. If you want to confirm the details of the call, including the Call Serial Number and Call Tag, click View. Click
the back button on your browser to return to the Calls page.
3. Select the box next to the calls you want to terminate and click Disconnect.
Note that if your VCS is part of a cluster you have to be logged into the peer through which the call is associated to be
able to disconnect the call.
Disconnecting a call using the CLI
To disconnect an existing call using the CLI, you must first obtain either the call ID number or the call serial number
(see Identifying Calls, page 211). Then use either one of the following commands as appropriate:
xCommand DisconnectCall Call: <ID number>

xCommand DisconnectCall CallSerialNumber: <serial number>
While it is quicker to use the call ID number to reference the call to be disconnected, there is a risk that in the
meantime the call has already been disconnected and the call ID assigned to a new call. For this reason, the VCS
also allows you to reference the call using the longer but unique call serial number.
Note that when disconnecting a call, only the call with that Call Serial Number is disconnected. Other calls with the
same Call Tag but a different Call Serial Number may not be affected.
Limitations when disconnecting SIP calls
Call disconnection works differently for H.323 and SIP calls due to differences in the way the protocols work.
For H.323 calls, and interworked calls, the Disconnect command actually disconnects the call.
212
For SIP calls, the Disconnect command causes the VCS to release all resources used for the call; the call will appear
as disconnected on the VCS. However, endpoints will still consider themselves to be in the call. SIP calls are peer-to-
peer, and as the VCS is a SIP proxy it has no authority over the endpoints. Releasing the resources on the VCS means
that the next time there is any signaling from the endpoint to the VCS, the VCS will respond with a '481
Call/Transaction Does Not Exist' causing the endpoint to clear the call.
Note that endpoints that support SIP session timers (see RFC 4028) have a call refresh timer which allows them to
detect a hung call (signaling lost between endpoints). The endpoints will release their resources after the next
session-timer message exchange.
213
Bandwidth Control
This section describes how to control the bandwidth that is used for calls within your Local Zone, as well as calls out
to other zones (Configuration > Local Zone and Configuration > Bandwidth).
About Bandwidth Control 214

Configuring Bandwidth Controls 215
About Subzones 216
Links and Pipes 222
Bandwidth Control Examples 225
About Bandwidth Control

The VCS allows you to control the amount of bandwidth used by endpoints on your network. This is done by grouping
endpoints into subzones, and then using links and pipes to apply limits to the bandwidth that can be used:
within each subzone

between a subzone and another subzone
between a subzone and a zone
Bandwidth limits may be set on a call-by-call basis and/or on a total concurrent usage basis. This flexibility allows
you to set appropriate bandwidth controls on individual components of your network.
Calls will fail if links are not configured correctly. You can check whether a call will succeed, and what bandwidth will
be allocated to it, using the command xCommand CheckBandwidth.
For specific information about how bandwidth is managed across peers in a cluster, see Sharing Bandwidth Across
Peers, page 168.
Example network deployment
The following diagram shows a typical network deployment:
a broadband LAN between the Enterprise and the internet, where high bandwidth calls are acceptable
a pipe to the internet (Pipe A) with restricted bandwidth
two satellite offices, Branch and Home, each with their own internet connections and restricted pipes
In this example each pool of endpoints has been assigned to a different subzone, so that suitable limitations can be
applied to the bandwidth used within and between each subzone based on the amount of bandwidth they have
available via their internet connections.
214
Configuring Bandwidth Controls

The Bandwidth configuration page (Configuration > Bandwidth > Configuration) is used to specify how the VCS
behaves in situations when it receives a call with no bandwidth specified, and when it receives a call that requests
more bandwidth than is currently available.
Default call The bandwidth to use for calls for which no bandwidth value Usually, when a call is initiated
bandwidth has been specified by the system that initiated the call. the endpoint will include in the
(kbps) request the amount of bandwidth
It also defines the minimum bandwidth to use on SIP to H.323 it wants to use.
interworked calls.
This value cannot be blank. The default value is 384kbps.
Downspeed Determines what happens if the per-call bandwidth

per call mode restrictions on a subzone or pipe mean that there is
insufficient bandwidth available to place a call at the
requested rate.
On: the call will be downspeeded.
Off: the call will not be placed.
Downspeed Determines what happens if the total bandwidth restrictions

total mode on a subzone or pipe mean that there is insufficient bandwidth
available to place a call at the requested rate.
On: the call will be downspeeded.
Off: the call will not be placed.
215
About Downspeeding
If bandwidth control is in use, there may be situations when there is insufficient bandwidth available to place a call at
the requested rate. By default (and assuming that there is some bandwidth still available) the VCS will still attempt to
connect the call, but at a reduced bandwidth this is known as downspeeding.
Downspeeding can be configured so that it is applied in either or both of the following scenarios:
when the requested bandwidth for the call exceeds the lowest per-call limit for the subzone or pipes
when placing the call at the requested bandwidth would mean that the total bandwidth limits for that subzone
or pipes would be exceeded
You can turn off downspeeding, in which case if there is insufficient bandwidth to place the call at the originally
requested rate, the call will not be placed at all. This could be used if, when your network is nearing capacity, you
would rather a call failed to connect at all than be connected at a lower than requested speed. In this situation
endpoint users will get one of the following messages, depending on the system that initiated the search:
"Exceeds Call Capacity"

"Gatekeeper Resources Unavailable"
About Subzones
The Local Zone is made up of subzones. Subzones are used to control the bandwidth used by various parts of your
network, and to control the VCS's registration, authentication and media encryption policies.
When an endpoint registers with the VCS it is allocated to an appropriate subzone, determined by subzone
membership rules based on endpoint IP address ranges or alias pattern matches.
You can create and configure subzones through the Subzones page (Configuration > Local Zone > Subzones).
Three special subzones the Default Subzone, the Traversal Subzone and the Cluster Subzone (only applies if the
VCS is in a cluster) are automatically created and cannot be deleted.
Default links between subzones
The VCS is shipped with the Default Subzone and Traversal Subzone (and Default Zone) already created, and with
links between them. If the VCS is added to a cluster then default links to the Cluster Subzone are also established
automatically. You can delete or amend these default links if you need to model restrictions of your network.
About the Traversal Subzone

The Traversal Subzone is a conceptual subzone. No endpoints can be registered to the Traversal Subzone; its sole
purpose is to control the bandwidth used by traversal calls.
The Traversal Subzone page (Configuration > Local Zone > Traversal Subzone) allows you to place bandwidth
restrictions on calls being handled by the Traversal Subzone and to configure the range of ports used for the media in
traversal calls.
Configuring Bandwidth Limitations

All traversal calls pass through the Traversal Subzone, so by applying bandwidth limitations to the Traversal Subzone
you can control how much processing of media the VCS will perform at any one time. These limitations can be
applied on a total concurrent usage basis, and on a per-call basis.
See Applying Bandwidth Limitations to Subzones, page 221 for more details.
Configuring the Traversal Subzone Ports

On Configuration > Local Zone > Traversal Subzone you can configure the range of ports used for media in traversal
calls.
216
What is a valid range to use?
You can define the media port range anywhere within the range 1024 to 65533. Traversal media port start must be
an even number and Traversal media port end must be an odd number, because ports are allocated in pairs and the
first port allocated in each pair is even.
How big should the range be?
Up to 48 ports could be required for a single traversal call, and you can have up to 100 concurrent traversal calls on a
small/medium system, or 500 concurrent traversal calls on a large system. The default range is thus 48*500 = 24000
ports.
If you want to reduce the range, be aware that the VCS will raise an alarm if the range is not big enough to meet the
nominal maximum of 48 ports per call for the licensed number of traversal calls. You may need to increase the range
again if you add new licenses.
Why are 48 ports required for each call?
The nominal maximum number of ports allocated per call = max number of ports per allocation *max number of
allocation instances. This is 8 *6 = 48, and those numbers are derived as follows:
Each call can have up to 5 types of media; video (RTP/RTCP), audio (RTP/RTCP), second/duo video (RTP/RTCP),
presentation (BFCP), and far end camera control (H.224). If all these media types are in the call, then the call requires
8 ports; 3 RTP/RTCP pairs, 1 for BFCP, and 1 for H.224.
Each call has at least two legs (inbound to VCS and outbound from VCS), requiring two instances of port allocation.
Afurther four instances of allocation are required if the call is routed via the B2BUA. In this case, ports are allocated
at the following points:
1. Inbound to the local proxy from the source

2. Outbound from the local proxy to the local B2BUA
3. Inbound to the local B2BUA from the local proxy
4. Outbound from the local B2BUAto the local proxy
5. Inbound to the local proxy from the local B2BUA
6. Outbound from the local proxy to the destination
Figure 10 Maximum port allocation for a media traversal call
In practice, you probably won't reach the maximum number of concurrent traversal calls, have them all routed through
the B2BUA, and have all the possible types of media in every call. However, we defined the default range to
accommodate this extreme case, and the VCS raises an alarm if the total port requirement could exceed the port
range you specify.
217
What is the default range?
On new installations of X8.1 or later, the default media traversal port range is 36000 to 59999, and is set on the VCS
Configuring the Default Subzone

The Default Subzone page (Configuration > Local Zone > Default Subzone) is used to place bandwidth restrictions
on calls involving endpoints in the Default Subzone, and to specify the Default Subzone's registration, authentication
and media encryption policies.
When an endpoint registers with the VCS, its IP address and alias is checked against the subzone membership rules
and it is assigned to the appropriate subzone. If no subzones have been created, or the endpoints IP address or alias
does not match any of the subzone membership rules, it is assigned to the Default Subzone (subject to the Default
Subzone's Registration policy and Authentication policy).
The use of a Default Subzone on its own (without any other manually created subzones) is suitable only if you have
uniform bandwidth available between all your endpoints. Note that if your Local Zone contains two or more different
networks with different bandwidth limitations, you should configure separate subzones for each different part of the
network.
Default Subzone configuration options
The Default Subzone can be configured in the same manner as any other manually created subzone.
Configuring Subzones
The Subzones page (Configuration > Local Zone > Subzones) lists all the subzones that have been configured on
the VCS, and allows you to create, edit and delete subzones. For each subzone, it shows how many membership
rules it has, how many devices are currently registered to it, and the current number of calls and bandwidth in use. Up
to 1000 subzones can be configured.
After configuring a subzone you should set up the Subzone membership rules which control which subzone an
endpoint device is assigned to when it registers with the VCS as opposed to defaulting to the Default Subzone.
218
Field / section Description
Registration When an endpoint registers with the VCS, its IP address and alias is checked against the subzone
policy membership rules and it is assigned to the appropriate subzone. If no subzones have been
created, or the endpoints IP address or alias does not match any of the subzone membership
rules, it is assigned to the Default Subzone.
In addition to using a registration restriction policy to control whether an endpoint can register with
the VCS, you can also configure a subzone's Registration policy as to whether it will accept
registrations assigned to it via the subzone membership rules.
This provides additional flexibility when defining your registration policy. For example you can:
Deny registrations based on IP address subnet. You can do this by creating a subzone with
associated membership rules based on an IP address subnet range, and then setting that
subzone to deny registrations.
Configure the Default Subzone to deny registrations. This would cause any registration
requests that do not match any of the subzone membership rules, and hence fall into the
Default Subzone, to be denied.
Note that registration requests have to fulfill any registration restriction policy rules before any
subzone membership and subzone registration policy rules are applied.
Authentication The Authentication policy setting controls how the VCS challenges incoming messages to the
policy Default Subzone. See Authentication Policy Configuration Options, page 111 for more information.
Media The Media encryption mode setting controls the media encryption capabilities for SIP calls
encryption flowing through the subzone. See Configuring Media Encryption Policy, page 139 for more
mode information.
Note that if H.323 is enabled and the subzone has a media encryption mode of Force encrypted or
Force unencrypted, any H.323 and SIP to H.323 interworked calls through this subzone will ignore
this mode.
ICE support Controls whether ICE messages are supported by the devices in this subzone.
for media
Bandwidth When configuring your subzones you can apply bandwidth limits to:
controls
individual calls between two endpoints within the subzone
individual calls between an endpoint within the subzone and another endpoint outside of
the subzone
the total of calls to or from endpoints within the subzone
See Applying Bandwidth Limitations to Subzones, page 221 for information about how bandwidth
limits are set and managed.
Configuring Subzone Membership Rules

The Subzone membership rules page (Configuration > Local Zone > Subzone membership rules) is used to
configure the rules that determine, based on the address of the device, to which subzone an endpoint is assigned
when it registers with the VCS.
The page lists all the subzone membership rules that have been configured on the VCS, and lets you create, edit,
delete, enable and disable rules. Rule properties include:
rule name and description

priority
219
the subnet or alias pattern matching configuration

the subzone to which endpoints whose addresses satisfy this rule are assigned
Note that if an endpoints IP address or registration alias does not match any of the membership rules, it is assigned to
the Default Subzone.
Up to 3000 subzone membership rules can be configured.
Rule name A descriptive name for the membership rule.
Description An optional free-form description of the rule. The description appears as a tooltip if you
hover your mouse pointer over a rule in the
list.
Priority The order in which the rules are applied (and thus The rules with the highest priority (1, then 2,
to which subzone the endpoint is assigned) if an then 3 and so on) are applied first. If multiple
endpoint's address satisfies multiple rules. Subnet rules have the same priority, the rule
with the largest prefix length is applied first.
Alias pattern match rules at the same priority
are searched in configuration order.
Type Determines how a device's address is checked: Pattern matching is useful, for example, for
home workers on dynamic IP addresses;
Subnet: assigns the device if its IP address falls rather than having to continually update the
within the configured IP address subnet. subnet to match what has been allocated,
you can match against their alias instead.
Alias pattern match: assigns the device if its alias
matches the configured pattern.
Subnet These two fields together determine the range of Applies only if the Type is Subnet.
address and IP addresses that will belong to this subzone.
Prefix length
The Address range field shows the range of IP
addresses to be allocated to this subzone, based
on the combination of the Subnet address and
Prefix length.
Pattern type How the Pattern string must match the alias for Applies only if the Type is Alias pattern
the rule to be applied. Options are: match.
Exact: the entire string must exactly match the


the alias.

alias.
Pattern string The pattern against which the alias is compared. Applies only if the Type is Alias pattern
match.
Target The subzone to which an endpoint is assigned if its

subzone address satisfies this rule.
220
Applying Bandwidth Limitations to Subzones

You can apply bandwidth limits to the Traversal Subzone as follows:
You can apply bandwidth limits to the Default Subzone, Traversal Subzone and all manually configured subzones.
The limits you can apply vary depending on the type of subzone, as follows:
Limitation Description Can be applied to
Total Limits the total concurrent bandwidth being used by all Default Subzone
endpoints in the subzone at any one time. In the case of the
Traversal Subzone, this is the maximum bandwidth available Traversal Subzone
for all concurrent traversal calls.
Manually configured subzones
Calls entirely Limits the bandwidth of any individual call between two Default Subzone
within... endpoints within the subzone.
Manually configured subzones
Calls into or Limits the bandwidth of any individual call between an Default Subzone
out of... endpoint in the subzone, and an endpoint in another subzone
or zone. Manually configured subzones
Calls handled The maximum bandwidth available to any individual traversal Traversal Subzone
by... call.
For all the above limitations, the Bandwidth restriction setting has the following effect:
No bandwidth: no bandwidth is allocated and therefore no calls can be made.

Limited: limits are applied. You must also enter a value in the corresponding bandwidth (kbps) field.
Unlimited: no restrictions are applied to the amount of bandwidth being used.
Use subzone bandwidth limits if you want to configure the bandwidth available between one specific subzone and all
other subzones or zones.
Use pipes if you want to configure the bandwidth available between one specific subzone and another specific
subzone or zone.
If your bandwidth configuration is such that multiple types of bandwidth restrictions are placed on a call (for example,
if there are subzone bandwidth limits and pipe limits), the lowest limit will always apply to that call.
How different bandwidth limitations are managed
In situations where there are differing bandwidth limitations applied to the same link, the lower limit will always be the
one used when routing the call and taking bandwidth limitations into account.
For example, Subzone A may have a per call inter bandwidth of 128. This means that any calls between Subzone A
and any other subzone or zone will be limited to 128kbps. However, Subzone A also has a link configured between it
and Subzone B. This link uses a pipe with a limit of 512kbps. In this situation, the lower limit of 128kbps will apply to
calls between the two, regardless of the larger capacity of the pipe.
In the reverse situation, where Subzone A has a per call inter bandwidth limit of 512kbps and a link to Subzone B with
a pipe of 128kbps, any calls between the two subzones will still be limited to 128kbps.
221
Bandwidth consumption of traversal calls

A non-traversal call between two endpoints within the same subzone would consume from that subzone the amount
of bandwidth of that call.
A traversal call between two endpoints within the same subzone must, like all traversal calls, pass through the
Traversal Subzone. This means that such calls consume an amount of bandwidth from the originating subzones total
concurrent allocation that is equal to twice the bandwidth of the call once for the call from the subzone to the
Traversal Subzone, and again for the call from the Traversal Subzone back to the originating subzone. In addition, as
this call passes through the Traversal Subzone, it will consume an amount of bandwidth from the Traversal Subzone
equal to that of the call.
Links and Pipes
Configuring Links
Links connect local subzones with other subzones and zones. For a call to take place, the endpoints involved must
each reside in subzones or zones that have a link between them. The link does not need to be direct; the two
endpoints may be linked via one or more intermediary subzones.
Links are used to calculate how a call is routed over the network and therefore which zones and subzones are
involved and how much bandwidth is available. If multiple routes are possible, your VCS will perform the bandwidth
calculations using the one with the fewest links.
The Links page (Configuration > Bandwidth > Links) lists all existing links and allows you to create, edit and delete
links.
The following information is displayed:
Field Description
Name The name of the link. Automatically created links have names based on the nodes that the link is
between.
Node 1 and The Traversal Subzone and the zone that the link is between.
Node 2
The two subzones, or one subzone and one zone, that the link is between.
Pipe 1 and Any pipes that have been used to apply bandwidth limitations to the link. See Applying Pipes to
Pipe 2 Links, page 224 for more information. Note that in order to apply a pipe, you must first have
created it via the Pipes page.
Calls Shows the total number of calls currently traversing the link.
Bandwidth Shows the total amount of bandwidth currently being consumed by all calls traversing the link.
used
You can configure up to 3000 links. Some links are created automatically when a subzone or zone is created.
Default Links
If a subzone has no links configured, then endpoints within the subzone are only able to call other endpoints within
the same subzone. For this reason, the VCS comes shipped with a set of pre-configured links and will also
automatically create new links each time you create a new subzone.
Pre-configured links
The VCS is shipped with the Default Subzone, Traversal Subzone and Default Zone already created, and with default
links pre-configured between them as follows: DefaultSZtoTraversalSZ, DefaultSZtoDefaultZ and
TraversalSZtoDefaultZ. If the VCS is in a cluster, an additional link, DefaultSZtoClusterSZ, between the Default
Subzone and the Cluster Subzone is also established.
222
You can edit any of these default links in the same way you would edit manually configured links. If any of these links
have been deleted you can re-create them, either:
manually through the web interface

automatically by using the CLI command xCommand DefaultLinksAdd
Automatically created links
Whenever a new subzone or zone is created, links are automatically created as follows:
New zone/subzone type Default links are created to...
Subzone Default Subzone and Traversal Subzone
Neighbor zone Default Subzone and Traversal Subzone
DNS zone Default Subzone and Traversal Subzone
ENUM zone Default Subzone and Traversal Subzone
Traversal client zone Traversal Subzone
Traversal server zone Traversal Subzone
Along with the pre-configured default links this ensures that, by default, any new subzone or zone has connectivity to
all other subzones and zones. You may rename, delete and amend any of these default links.
Note: calls will fail if links are not configured correctly. You can check whether a call will succeed, and what
bandwidth will be allocated to it, using the CLI command xCommand CheckBandwidth.
Configuring Pipes
Pipes are used to control the amount of bandwidth used on calls between specific subzones and zones. The limits
can be applied to the total concurrent bandwidth used at any one time, or to the bandwidth used by any individual
call.
To apply these limits, you must first create a pipe and configure it with the required bandwidth limitations. Then when
configuring links you assign the pipe to one or more links. Calls using the link will then have the pipes bandwidth
limitations applied to them. See Applying Pipes to Links, page 224 for more information.
The Pipes page (Configuration > Bandwidth > Pipes) lists all the pipes that have been configured on the VCS and
allows you to create, edit and delete pipes.
Field Description
Name The name of the pipe.
Total The upper limit on the total bandwidth used at any one time by all calls on all links to which this
bandwidth pipe is applied.
Per call The maximum bandwidth of any one call on the links to which this pipe is applied.
bandwidth
Calls Shows the total number of calls currently traversing all links to which the pipe is applied.
Bandwidth Shows the total amount of bandwidth currently being consumed by all calls traversing all links to
used which the pipe is applied.
You can configure up to 1000 pipes.

See Applying Bandwidth Limitations to Subzones, page 221 for more information about how the bandwidth limits are
set and managed.
223
Applying Pipes to Links

Pipes are used to restrict the bandwidth of a link. When a pipe is applied to a link, it restricts the bandwidth of calls
made between the two nodes of the link - the restrictions apply to calls in either direction. Normally a single pipe
would be applied to a single link. However, one or more pipes may be applied to one or more links, depending on how
you want to model your network.
One pipe, one link
Applying a single pipe to a single link is useful when you want to apply specific limits to calls between a subzone and
another specific subzone or zone.
One pipe, two or more links
Each pipe may be applied to multiple links. This is used to model the situation where one site communicates with
several other sites over the same broadband connection to the Internet. A pipe should be configured to represent the
broadband connection, and then applied to all the links. This allows you to configure the bandwidth options for calls
in and out of that site.
In the diagram below, Pipe A has been applied to two links: the link between the Default Subzone and the Home
Office subzone, and the link between the Default Subzone and the Branch Office subzone. In this case, Pipe A
represents the Head Offices broadband connection to the internet, and would have total and per-call restrictions
placed on it.
Two pipes, one link
Each link may have up to two pipes associated with it. This is used to model the situation where the two nodes of a
link are not directly connected, for example two sites that each have their own broadband connection to the Internet.
Each connection should have its own pipe, meaning that a link between the two nodes should be subject to the
bandwidth restrictions of both pipes.
In the diagram below, the link between the Default Subzone and the Home Office Subzone has two pipes associated
with it: Pipe A, which represents the Head Offices broadband connection to the internet, and Pipe B, which
represents the Home Offices dial-up connection to the internet. Each pipe would have bandwidth restrictions placed
on it to represent its maximum capacity, and a call placed via this link would have the lower of the two bandwidth
restrictions applied.
224
Bandwidth Control Examples

Without a Firewall
In the example below, there are three geographically separate offices: Head, Branch and Home. All endpoints in the
Head Office register with the VCS Control, as do those in the Branch and Home offices.
Each of the three offices is represented as a separate subzone on the VCS, with bandwidth configured according to
local policy.
The enterprises leased line connection to the Internet, and the DSL connections to the remote offices are modeled as
separate pipes.
There are no firewalls involved in this scenario, so direct links can be configured between each of the offices. Each
link is then assigned two pipes, representing the Internet connections of the offices at each end of the link.
In this scenario, a call placed between the Home Office and Branch Office will consume bandwidth from the Home
and Branch subzones and on the Home and Branch pipes (Pipe B and Pipe C). The Head Offices bandwidth budget
will be unaffected by the call.
With a Firewall
If the example deployment above is modified to include firewalls between the offices, we can use Ciscos Expressway
firewall traversal solution to maintain connectivity. We do this by adding a VCS Expressway outside the firewall on the
public internet, which will work in conjunction with the VCS Control and Home and Branch office endpoints to
traverse the firewalls.
In this example, shown below, the endpoints in the Head Office register with the VCS Control, while those in the
Branch and Home offices register with the VCS Expressway. The introduction of the firewalls means that there is no
longer any direct connectivity between the Branch and Home offices. All traffic must be routed through the VCS
Expressway. This is shown by the absence of a link between the Home and Branch subzones.
225
The VCS Expressway has subzones configured for the Home Office and Branch Office. These are linked to the VCS
Expressways Traversal Subzone, with pipes placed on each link. All calls from the VCS Expressway to the VCS
Control must go through the Traversal Subzone and will consume bandwidth from this subzone. Note also that calls
from the Home Office to the Branch Office must also go through the Traversal Subzone, and will also consume
bandwidth from this subzone as well as the Home and Branch subzones and Home Office, Branch Office and Head
Office pipes.
This example assumes that there is no bottleneck on the link between the VCS Expressway and the Head Office
network, so a pipe has not been placed on this link. If you want to limit the amount of traffic flowing through your
firewall, you could provision a pipe on this link.
Because the VCS Control is only managing endpoints on the Head Office LAN, its configuration is simpler. All of the
endpoints in the Head Office are assigned to the Default Subzone. This is linked to the Traversal Subzone, through
which all calls leaving the Head Office must pass.
226
227
Applications
This section provides information about each of the additional services that are available under the Applications
menu of the VCS.
Configuring Conference Factory 229

Presence 231
B2BUA (Back-to-Back User Agent) Overview 235
FindMe 244
Cisco TMS Provisioning 248
Hybrid Services and Connector Management 251
228
Configuring Conference Factory

The Conference Factory page (Applications > Conference Factory) allows you to enable and disable the
Conference Factory application, and configure the alias and template it uses.
The Conference Factory application allows the VCS to support the Multiway feature. Multiway enables endpoint
users to create a conference while in a call even if their endpoint does not have this functionality built in.
Multiway is supported in Cisco TelePresence endpoints including the E20 (software version TE1.0 or later) and MXP
range (software version F8.0 or later). Check with your Cisco representative for an up-to-date list of the Cisco
endpoints and infrastructure products that support Multiway.
Conference creation process
When the Multiway feature is activated from the endpoint:
1. The endpoint calls a pre-configured alias which routes to the Conference Factory on the VCS.
2. The VCS replies to the endpoint with the alias that the endpoint should use for the Multiway conference. This
alias will route to an MCU.
3. The endpoint then places the call to the MCU using the given alias, and informs the other participating
endpoints to do the same.
Mode Enables or disables the

Conference Factory application.
Alias The alias that will be dialed by the

endpoints when the Multiway
feature is activated. This must
also be configured on all
endpoints that may be used to
initiate the Multiway feature. An
example could be
[email protected].
Template The alias that the VCS tells the To ensure that each conference has a different alias, you should
endpoint to dial to create a use %% as a part of the template. The %% will be replaced by a
Multiway conference on the unique number each time the VCS receives a new conference
MCU. request.
Number The first and last numbers in the For example, your Template could be 563%%@example.com with a
range range that replaces %% in the range of 10 - 999. The first conference will use the alias
start / template used to generate a [email protected], the next conference will use
end conference alias. [email protected] and so on up to [email protected], after
which it will loop round and start again at [email protected].
(Note that the %% represents a fixed number of digits with leading
zeroes where required based upon the length of the upper range
limit.)
Note that:
You must use a different Template on each VCS in your network that has the Conference Factory application
enabled. If your VCS is part of a cluster, the Template must be different for each peer in the cluster.
The alias generated by the Template must be a fully-qualified SIP alias and must route to the MCU. The MCU
must be configured to process this alias. No other special configuration is required on the MCU in order to
support the Conference Factory application.
229
SIP mode must be set to On (Configuration > Protocols > SIP) for the Conference Factory application to
function. If you want to be able to initiate calls to the Conference Factory from H.323 endpoints, you must also
set H.323 mode to On (Configuration > Protocols > H.323), and ensure that H.323 <-> SIP interworking
mode is set to Registered only or On (Configuration > Protocols > Interworking).
See Cisco TelePresence Multiway Deployment Guide for full details on how to configure individual components of
your network (endpoints, MCUs and VCSs) in order to use Multiway in your deployment.
230
Presence
Presence is the ability of endpoints to provide information to other users about their current status - such as whether
they are offline, online, or in a call. Any entity which provides presence information, or about whom presence
information can be requested, is known as a presentity. Presentities publish information about their own presence
status, and also subscribe to the information being published by other presentities and FindMe users.
Endpoints that support presence, such as Jabber Video, can publish their own status information. The VCS can also
provide basic presence information on behalf of endpoints that do not support presence, including H.323 endpoints,
as long as they have registered with an alias in the form of a URI.
If FindMe is enabled, the VCS can also provide presence information about FindMe users by aggregating the
information provided by each presentity configured for that FindMe user.
The Presence application on the VCS supports the SIP-based SIMPLE standard and is made up of two separate
services. These are the Presence Server and the Presence User Agent (PUA). These services can be enabled and
disabled separately.
The Presence status pages provide information about the presentities who are providing presence information and
the users who are requesting presence information on others. The status pages are organized into:
Publishers
Presentities
Subscribers
Note that any one presentity can only subscribe to a maximum of 100 other presentities, and can only have a
maximum of 100 other presentities subscribed to it.
Presence is supported by clustering. For specific information about how Presence information is managed across
peers in a cluster, see Clustering and Presence, page 168.
Presence Server
The Presence Server application on the VCS is responsible for managing the presence information for all presentities
in the SIP domains for which the VCS is authoritative. The Presence Server can manage the presence information for
locally registered endpoints and presentities whose information has been received via a SIP proxy (such as another
VCS).
The Presence Server is made up of the following services, all of which are enabled (or disabled) simultaneously when
the Presence Server is enabled (or disabled):
Publication Manager: receives PUBLISH messages, which contain the status information about a presentity,
and writes this information to the Presence Database. PUBLISH messages are generated by presence-
enabled endpoints and by the Presence User Agent (PUA).
Subscription Manager: handles SUBSCRIBE messages, which request information about the status of a
presentity. Upon receipt of a SUBSCRIBE message, the Subscription Manager sends a request to the
Presentity Manager for information about that presentity, and forwards the information that is returned to the
subscriber. The Subscription Manager also receives notifications from the Presentity Manager when a
presentitys status has changed, and sends this information to all subscribers.
Presentity Manager: an interface to the Presence Database. It is used to support VCS features such as
FindMe and the PUA, where the presence information provided by a number of different devices must be
aggregated in order to provide an overall presence status for one particular presentity. When the Presentity
Manager receives a request from the subscription manager for information on a presentity, it queries the
Presence Database for all information available on all the endpoints associated with that particular presentity.
The Presentity Manager then aggregates this information to determine the presentitys current status, and
returns this to the Subscription Manager.
Presence Database: stores current presence information received in the form of PUBLISH messages. Also
sends NOTIFY messages to the Presentity Manager to inform it of any changes.
231
Presence and device authentication

status.
See Presence and Authentication Policy, page 120 for more information.
Presence User Agent (PUA)

Endpoints that do not support presence can have status published on their behalf by the VCS. The service that
publishes this information is called the Presence User Agent (PUA).
The PUA takes information from the local registration database and the call manager and determines, for each
endpoint that is currently locally registered, whether or not it is currently in a call. The PUA then provides this status
information via a PUBLISH message.
For the PUA to successfully provide presence information about a locally registered endpoint:
The endpoint must be registered with an alias in the form of a URI.

The domain part of the URI must be able to be routed to a SIP registrar that has a presence server enabled.
(This could be either the local Presence Server, if enabled, or another Presence Server on a remote system.)
When enabled, the PUA generates presence information for all endpoints registered to the VCS, including those
which already support presence. The status information provided by the PUA is either:
online (registered but not in a call)

in call (registered and currently in a call)
Aggregation of presence information
When enabled, the PUA generates presence information for all endpoints registered to the VCS, including those
which already support presence. However, endpoints that support presence may provide other, more detailed status,
for example away or do not disturb. For this reason, information provided by the PUA is used by the Presentity
Manager as follows:
Where presence information is provided by the PUA and one other source, the non-PUA presence information
will always be used in preference to the PUA presence information. This is because it is assumed that the
other source of information is the presentity itself, and this information is more accurate.
Where presence information is provided by the PUA and two or more other sources, the Presence Server will
aggregate the presence information from all presentities to give the "highest interest" information, e.g. online
rather than offline, and in call rather than away.
If no information is being published about an endpoint, either by the endpoint itself or by the PUA, the
endpoints status will be offline. If the PUA is enabled, the offline status indicates that the endpoint is not
currently registered.
FindMe presence
When the Presentity Manager receives a request for information about the presences of a FindMe alias, it looks up
the presence information for each endpoint that makes up that FindMe alias. It then aggregates this information as
follows:
If the FindMe alias is set to Individual mode, if any one of the endpoints making up that FindMe is in a call the
FindMe presentitys status will be reported as in call.
232
If the FindMe alias is set to Group mode, if any one of the endpoints is online (i.e. not in call or offline) then the
FindMe presentitys status will be reported as online.
Registration refresh period
The PUA will update and publish presence information on receipt of:
a registration request (for new registrations)

a registration refresh (for existing registrations)
a deregistration request
call setup and cleardown information
For non-traversal H.323 registrations the default registration refresh period is 30 minutes. This means that when the
PUA is enabled on a VCS with existing registrations, it may take up to 30 minutes before an H.323 registration refresh
is received and available presence information is published for that endpoint.
It also means that if an H.323 endpoint becomes unavailable without sending a deregistration message, it may take
up to 30 minutes for its status to change to offline. To ensure more timely publication of presence information for
H.323 endpoints, you should decrease the H.323 registration refresh period (using Configuration > Protocols > H.323
> Gatekeeper > Time to live).
The default registration refresh period for SIP is 60 seconds, so it will take no more than a minute for the PUA to
publish updated presence information on behalf of any SIP endpoints.
Configuring Presence
The Presence page (Applications > Presence) allows you to enable and configure Presence services on the VCS.
These services can be enabled and disabled separately from each other, depending on the nature of your
deployment. Both are disabled by default.
Note that SIP mode must be enabled for the Presence services to function.
Presence User Agent (PUA)

The PUA provides presence information on behalf of registered endpoints.
Enabled: if the PUA is enabled, it will publish presence information for all locally registered endpoints, whether
or not those endpoints are also publishing their own presence information. Information published by the PUA
will be routed to a Presence Server acting for the endpoints domain. This could be the local Presence Server,
or (if this is disabled) a Presence Server on another system that is authoritative for that domain.
Disabled: if the PUA is disabled, only those endpoints that support presence will publish presence information.
No information will be available for endpoints that do not support presence.
You can also configure the Default published status for registered endpoints. This is the presentity status
published by the Presence User Agent for registered endpoints when they are not "In-Call". The options are either
Online or Offline. Note that:
If this is set to Online, any permanently registered video endpoints and FindMe entries that include those
endpoints will appear as permanently "Online".
The status of non-registered endpoints always appears as "Offline".
"Online" status appears as "Available" in Lync clients.
Presence Server
The Presence Server manages the presence information for all presentities in the SIP domains for which the VCS is
authoritative.
233
Enabled: if the local Presence Server is enabled, it will process any PUBLISH messages intended for the SIP
domains for which the local VCS is authoritative. All other PUBLISH messages will be proxied on in
accordance with the VCSs SIP routing rules. Note that SIP routes are configured using the CLI only.
The Presence Server requires that any messages it receives have been pre-authenticated (the Presence
Server does not do its own authentication challenge).
You must ensure that the subzone through which PUBLISH messages are being received has its
Authentication policy is set to either Check credentials or Treat as authenticated, otherwise the messages
will be rejected.
Disabled: if the local Presence Server is disabled, the VCS will proxy on all PUBLISH messages to one or more
of its neighbor zones in accordance with its locally configured call routing rules. The local VCS will do this
regardless of whether or not it is authoritative for the presentitys domain. If one of these neighbors is
authoritative for the domain, and has a Presence Server enabled, then that neighbor will provide presence
information for the presentity.
Regardless of whether or not the Presence Server is enabled, the VCS will still continue to receive PUBLISH
messages if they are sent to it from any of the following sources:
locally registered endpoints that support presence

the local PUA (if enabled)
remote SIP Proxies
Note that Presence Server is automatically enabled when the Starter Pack option key is installed.
Recommendations
VCS Expressway and VCS Control: the recommended configuration for a VCS Expressway when acting as a
traversal server for a VCS Control is to enable the PUA and disable the Presence Server on the VCS
Expressway, and enable the Presence Server on the VCS Control. This will ensure that all PUBLISH messages
generated by the PUA are routed to the VCS Control.
VCS neighbors: if you have a deployment with two or more VCSs neighbored together, you are recommended
to enable only one presence server per domain. This will ensure a central source of information for all
presentities in your network.
VCS clusters: for information about how Presence works within a cluster, see Clustering and Presence, page
168.
Note: any defined transforms also apply to any Publication, Subscription or Notify URIs handled by the Presence
Services.
234
B2BUA (Back-to-Back User Agent) Overview

A B2BUA operates between both endpoints of a SIP call and divides the communication channel into two
independent call legs. Unlike a proxy server, the B2BUA maintains complete state for the calls it handles. Both legs of
the call are shown as separate calls on the Call status and Call history pages.
B2BUA instances are hosted on the VCS. They are used in the following scenarios:
to apply media encryption policy; this usage does not require any explicit B2BUA configuration
to support ICE messaging; the only B2BUA-related configuration required is to define the set of TURN servers
required to support ICE calls
to route SIP calls between the VCS and a Microsoft Edge Server; this requires the manual configuration of the
Microsoft Lync B2BUA and the set of TURN servers available for use by the B2BUA
Note:The B2BUAdoes not use or preserve DSCPinformation (Differentiated Services Code Point) from incoming
traffic. It does not apply DSCPinformation to outgoing traffic.
Configuring B2BUATURNServers
The B2BUA TURN servers page (Applications > B2BUA > B2BUA TURN servers) is used to configure the set of
TURN servers available for use by a B2BUA instance. The page lists all the currently configured TURN servers and lets
you create, edit and delete TURN servers.
The B2BUA chooses which TURN server to offer via random load-balancing between all of the available servers.
There is no limit to the number of servers that can be configured for the B2BUA to choose from.
To use these TURN servers with the Microsoft Lync B2BUA, you must enable Offer TURN services on the Lync
B2BUA configuration page. They are used automatically by the B2BUA instance used when ICE messaging is enabled
for a zone or subzone.
TURN server address The IP address of a TURN server to offer when The TURN server must be RFC 5245
establishing ICE calls (for example, with a compliant, for example a VCS
Microsoft Lync Edge server). Expressway TURN server.
TURN server port The listening port on the TURN server. Default
is 3478.
Description A free-form description of the TURN server.
TURN services The username and password that are required

username and to access the TURN server.
password
If the TURN server is running on a Large VCS Expressway, you can make use of its scaling capabilities by specifying
additional address/port combinations.
235
Microsoft Lync B2BUA

The Microsoft Lync back-to-back user agent (Lync B2BUA) on the VCS is used to route SIP calls between the VCS
and a Microsoft Lync Server.
It provides interworking between Microsoft ICE (used by Lync clients) and media for communications with standard
video endpoints. It also provides call hold, call transfer and Multiway support for calls with Lync clients, and can
share FindMe presence information with Lync.
Configuring the Lync B2BUA includes the following tasks:
Configuring and enabling the B2BUA for Microsoft Lync communications.

Configuring the external transcoders that may be used by the B2BUA and any policy rules used to control
routing through them (this is optional and are typically only used with Lync 2010).
Defining the B2BUA's trusted hosts the devices that may send signaling messages to the B2BUA.
Defining the set of TURN servers available for use by the B2BUA when establishing ICE calls.
Setting up search rules to route calls to the Lync domain via the B2BUA when the B2BUA is enabled a non-
configurable neighbor zone (named "To Microsoft Lync server via B2BUA") is automatically created; this
zone must be selected as the target zone of the search rules.
You may need to restart the Lync B2BUAservice before configuration changes take effect. A system alarm is raised if
a service restart is necessary.
Microsoft Lync 2010

The Microsoft Interoperability option key must be installed to enable encrypted calls to and from Microsoft Lync
2010 Server (for both native SIP calls and calls interworked from H.323). It is also required by the B2BUA when
establishing ICE calls to Lync 2010 clients.
The B2BUA can use the Cisco AM GW to transcode between standard codecs (such as H.264) and Microsoft RT
Video and RTAudio to allow high definition calls between Microsoft Lync 2010 clients and Cisco endpoints.
Microsoft Lync 2013

The B2BUA provides interworking between standard H.264 AVC and Lync 2013's H.264UC SVC codec. You can still
configure the B2BUA to use Cisco AM GW transcoders with Lync 2013, but it is not necessary and we recommend
that they are not deployed with Lync 2013.
Lync 2013 no longer supports H.263, so X8.1 or later software is required to interoperate successfully with Lync
2013. X7.2 or earlier software will work with Lync 2013 only if calls are routed through a Cisco AM GW transcoder.
The Microsoft Interoperability option key is required for all types of communication with Lync 2013.
Usage Features and Limitations
The Lync B2BUA has a maximum simultaneous call capability of 100 calls (for all system sizes, including Large
systems); however, calls that use transcoder resources count as 2 calls.
If a call is routed through the Lync B2BUA, the B2BUA always takes the media and always remains in the
signaling path. The call component that is routed through the B2BUA can be identified in the call history
details as having a component type of Microsoft Lync B2BUA.
The Lync B2BUA does not consume any call licenses in addition to the license required by the leg of the call
between the endpoint and the VCS.
If all configured external transcoders reach their capacity limits, any calls that would normally route via a
transcoder will not fail; the call will still connect as usual but will not be transcoded.
The Lync B2BUA supports multiple TURN servers. TURN servers are recommended for calls traversing a
Microsoft Lync Edge server.
236
Bandwidth controls can be applied to the leg of the call between the endpoint and the B2BUA, but cannot be
applied to the B2BUA to Microsoft Lync leg of the call. However, because the B2BUA forwards the media it
receives without any manipulation, any bandwidth controls you apply to the VCS to B2BUA leg will implicitly
apply to the B2BUA to Lync leg.
The non-configurable neighbor zone (named "To Microsoft Lync server via B2BUA") that connects the VCS
to the Lync B2BUA uses a special zone profile of Microsoft Lync this profile is only used by the Lync B2BUA
and cannot be selected against any manually configured zones.
For more information about configuring VCS and Microsoft Lync see:
Microsoft Lync B2BUA Port Reference, page 374

Microsoft Lync and VCS Deployment Guide
Microsoft Lync 2010, Cisco AM GW and VCS Deployment Guide
Configuring the Microsoft Lync B2BUA

The Microsoft Lync B2BUA configuration page (Applications > B2BUA > Microsoft Lync > Configuration) is used to
enable and configure the B2BUA's connection to Microsoft Lync devices.
Microsoft Lync Enables or disables the Microsoft Lync B2BUA.

B2BUA
Lync signaling The IP address or Fully Qualified Domain Name You must also configure the IP addresses
destination (FQDN) of the Hardware Load Balancer, Director of the trusted hosts. These are the Lync
address or Front End Processor to which the VCS sends devices that may send signaling messages
the signaling messages. to the VCS.
Lync signaling The IP port on the Hardware Load Balancer,

destination port Director or Front End Processor to which the VCS
sends the signaling messages. Default port is
5061.
Lync signaling The transport type used for connection to the

transport Microsoft Lync server. The default is TLS.
Capabilities section:
Register FindMe Controls whether to register FindMe users to the This feature only applies if FindMe is
users as clients Microsoft Lync server so that it can forward calls enabled.
on Lync to FindMe aliases and share FindMe presence
information. Default is Yes. Note that Lync only allows FindMe users to
register if the FindMe ID being registered is
a valid user in the Lync Active Directory (in
the same way that Lync users can only
register if they have a valid account
enabled in the Lync AD).
Lync domain The SIP domain in use on the Microsoft Lync Only FindMe names with this domain will be
server. This must be selected from one of the SIP registered to Lync.
domains already configured on the VCS.
Remote Desktop Protocol section:
237
Enable Controls whether the B2BUAoffers Remote You should enable this option if you want
RDPtranscoding Desktop Protocol transcoding. Lync users to be able to share their
for this B2BUA desktops or applications with other
This feature requires the Microsoft participants in a TelePresence Server
Interoperability option key. conference.
Default is No.
External transcoders section:
Enable external Controls whether calls may be routed through an You should enable this option if you need to
transcoders for external transcoder. use a transcoder such as the Cisco
this B2BUA TelePresence Advanced Media Gateway to
transcode between standard codecs (such
as H.264) and Microsoft RT Video and RT
Audio.
Port on B2BUA The IP port used on the B2BUA for All transcoder communications are carried
for transcoder communicating with the transcoders. Default is out over TLS.
communications 65080.
Use transcoder Specifies whether the transcoder policy rules are If Enable transcoders for this B2BUA is
policy rules used to control access to the transcoders. Yes, then all calls are routed via the
Default is No. transcoders by default.
If transcoder resources need to be reserved

for specific types of calls, you can use this
option to limit the types of calls that are
routed via the transcoders. Set this option
to Yes and then define the required policy
rules.
TURN section:
Offer TURN Controls whether the B2BUA offers TURN This is recommended for calls traversing a
services services. Default is No. Microsoft Lync Edge server.
To configure the associated TURNservers,

click Configure B2BUA TURN servers.
Advanced settings: you should only modify the advanced settings on the advice of Cisco customer support.
Encryption Controls how the B2BUA handles encrypted and A call via the B2BUA comprises two legs:
unencrypted call legs. one leg from the B2BUA to a standard video
endpoint, and one leg from the B2BUA to
Required: both legs of the call must be encrypted. the Lync client. Either leg of the call could
be encrypted or unencrypted.
Auto: encrypted and unencrypted combinations
are supported. A setting of Auto means that the call can be
established for any of the encrypted and
The default is Auto. unencrypted call leg combinations. Thus,
one leg of the call could be encrypted while
the other leg could be unencrypted.
238
B2BUA media The port range used by the B2BUA for handling Ensure that the port range does not overlap
port range media. Default range is 5600057000. with other port ranges used by this VCS or
start/end this VCS's TURN server.
You may need to increase this range if you

Enable RDPTranscoding for this B2BUA,
because desktop sharing increases the
number of media ports required per call.
Hop count Specifies the Max-Forwards value to use in SIP

messages. Default is 70.
Session refresh The maximum time allowed between session For further information see the definition of
interval refresh requests for SIP calls. Default is 1800 Session-Expires in RFC 4028.
seconds.
Minimum The minimum value the B2BUA will negotiate for For further information see the definition of
session refresh the session refresh interval for SIP calls. Default Min-SE header in RFC 4028.
interval is 500 seconds.
Port on B2BUA The port used on the B2BUA for communicating

for VCS with the VCS. Default is 65070.
communications
Port on B2BUA The port used on the B2BUA for call

for Lync call communications with the Microsoft Lync server.
communications Default is 65072.
RDP TCP port Defines the range of TCPports on which the Each simultaneous RDPtranscoding
range start / end B2BUAlistens for theRDPmedia from Lync. session created on the B2BUArequires a
Default is 6000 - 6099. receiving port. The range is limited to 100
as this is the maximum possible number of
Note:Save the page and restart the Lync simultaneous transcode sessions.
B2BUAservice to apply your changes.
RDP UDP port Defines the range of UDPports on which the Each simultaneous RDPtranscoding
range start / end B2BUAtransmits transcoded RDPmedia towards session created on the B2BUArequires a
the BFCPreceiver. Default is 6100 - 6199. port to send the resulting BFCPmedia to
the conference. The range is limited to 100
Note:Save the page and restart the Lync as this is the maximum possible number of
B2BUAservice to apply your changes. simultaneous transcode sessions.
239
Maximum RDP Limits the number of simultaneous Higher values will mean that more system
transcode RDPtranscoding sessions on this VCS. Default is resources can be consumed by RDP
sessions 10. transcoding, which could impact other
services. Maximum is 100.
Note:Save the page and restart the Lync
B2BUAservice to apply your changes.
Table 8 Recommended Number of Desktop

Transcode Sessions by Platform
On this Set Maximum RDP transcode

platform: sessions to:
1st 1
generation
VCS
appliance
CE500, 10
CE1100,
or Medium
OVA
CE1000, 20
CE1100,
or Large Note:This recommendation
OVA requires an active 10 Gbps
network connection.
Clusters Same as the individual platform

setting. The Maximum RDP
transcode sessions you enter on
the master applies to each peer in
the cluster.
The CE1100 appliance operates with Medium

capacity if you install 1 Gbps NICs, or with Large
capacity if you install 10 Gbps NICs.
Port on B2BUA The port used on the B2BUA for presence

for Lync communications with the Microsoft Lync server.
presence
communications Default is 10011.
Configuring the B2BUA's Trusted Hosts

The B2BUA trusted hosts page (Applications > B2BUA > Microsoft Lync > B2BUA trusted hosts) is used to specify
the devices that may send signaling messages to the Lync B2BUA.
The B2BUA only accepts messages from devices whose IP address is included in the list of trusted hosts.
Note that trusted host verification only applies to calls initiated by Lync that are inbound to the VCS video network. It
is not necessary to configure trusted hosts if calls are only ever to be initiated from the VCS video network.
The VCS has a limit of 25 trusted hosts. If there are more than 25 trusted hosts, the VCS raises an alarm. You can
work around this limit by adding another Gateway VCS,or by pointing some of the Lync servers to a Lync proxy and
then trusting the proxy instead.
240
Name An optional free-form description of the trusted The name is not used as part of the "trusted"
host device. criteria. It is provided only to help distinguish
between multiple devices, rather than having
to rely on their IP addresses.
IP address The IP address of the trusted host device.
Type The type of device that may send signaling

messages to the B2BUA.
Lync device: this includes Hardware Load

Balancers, Directors and Front End Processors
Transcoder: a transcoder device such as a Cisco

TelePresence Advanced Media Gateway
Configuring External Transcoder Policy Rules

The Microsoft Lync B2BUA transcoder policy rules page (Applications > B2BUA > Microsoft Lync > Transcoder
policy rules) is used to define the rules that control which Lync B2BUA calls are routed via a transcoder.
If Enable transcoders for this B2BUA (configured on the Microsoft Lync B2BUA configuration page) is Yes, then all
calls are routed via the transcoders by default. If transcoder resources need to be reserved for specific types of calls
then you can specify rules to limit the types of calls that are routed via the transcoders.
The rules on this page are only applied if Use transcoder policy rules (also configured on the Microsoft Lync
B2BUA configuration page) is set to Yes.
A rule is applied if it matches either the source or destination alias of a call.
If the aliases associated with a call do not match any of the policy rules, the call will be routed via the
transcoder. Therefore you may want to consider having a general low priority rule with a regex pattern match
for all aliases that denies transcoder resources, and then have more specific rules with a higher priority that
define the participants that are allowed to use the transcoder resources.
The page lists all the currently configured rules and lets you create, edit, delete, enable and disable rules. Note that
you can click on a column heading to sort the list, for example by Rule name or Priority.
Name The name assigned to the rule.
Description An optional free-form description of the rule. The description appears as a tooltip if you
hover your mouse pointer over a rule in the
list.
Priority Sets the order in which the rules are applied. The Multiple rules with the same priority are
rules with the highest priority (1, then 2, then 3 and applied in configuration order. For clarity you
so on) are applied first. are recommended to use unique priority
settings for each rule.
241
Pattern type The way in which the Pattern string must match You can test whether a pattern matches a
either the source or destination alias of the call. particular alias and is transformed in the
expected way by using the Check pattern
Exact: the entire string must exactly match the tool (Maintenance > Tools > Check pattern).

the alias.

alias.
Pattern string The pattern against which the alias is compared.
Action The action to take if the source or destination alias

of the call matches this policy rule.
Allow: the call can connect via the transcoder.
Deny: the call can connect but it will not use

transcoder resources.
Configuring External B2BUA Transcoders

Transcoders are used to convert digital media from one format to another. The only transcoder currently supported by
the Lync B2BUA is the Cisco TelePresence Advanced Media Gateway (Cisco AM GW).
The B2BUA can use the Cisco AM GW to transcode between standard codecs (such as H.264) and Microsoft RT
Video and RTAudio to allow high definition calls between Microsoft Lync clients and Cisco endpoints.
The Transcoders page (Applications >B2BUA > Microsoft Lync > Transcoders) is used to manage the set of
transcoders available to the B2BUA.
Multiple transcoders can be configured for load balancing purposes; the B2BUA automatically manages which
transcoder to use.
The status of each transcoder is shown, this includes:
whether the transcoder is accessible or not
the number of available connections; note that Cisco AM GW calls require 2 connections per call
You can use the B2BUA configuration page to control whether the B2BUA uses transcoder resources and
whether specific policy rules are used to filter which calls are allowed to be routed through the transcoders.
Note that the B2BUA can operate without any associated transcoders (calls will still connect but will not be
transcoded).
Name An optional free-form description of the

transcoder.
242
Address The IP address or Fully Qualified Domain Name If you have several transcoders you are
(FQDN) of the transcoder. recommended to either use their IP
addresses or to give each device a different
FQDN.
You may encounter problems if you use an

FQDN that resolves to multiple transcoders
(via DNS-based load balancing). This is
because the B2BUA will first use DNS to
discover the number of available ports on a
transcoder, and then use DNS again to route
a call to the transcoder. If the DNS lookup
can resolve to different transcoders there is
no guarantee that the call will be directed to
the same transcoder that provided the
resource information.
Port The listening port on the transcoder.
Restarting the B2BUA Service

The B2BUA service restart page (Applications > B2BUA > Microsoft Lync > B2BUA service restart) is used to
restart the Lync B2BUA service.
A restart is sometimes required to enable certain configuration changes to the B2BUA to take effect. A system alarm
will be raised if a service restart is necessary.
Note that this function only restarts the B2BUA service; it does not restart the VCS. However, restarting the service
will cause any active calls being managed by the B2BUA to be lost.
To restart the B2BUA service:
1. Go to Applications > B2BUA > Microsoft Lync > B2BUA service restart.
2. Check the number of active calls currently in place.
3. Click Restart service.
The service should restart after a few seconds. The status of the B2BUA service is displayed on the B2BUA
configuration page.
Clustered VCS systems
On a clustered VCS you have to restart the Lync B2BUA service on every peer. You are recommended to ensure the
service is configured and running correctly on the master peer before restarting the B2BUA service on the other peers.
243
FindMe
FindMe is a form of User Policy, which is the set of rules that determines what happens to a call for a particular user
or group when it is received by the VCS.
The FindMe feature lets you assign a single FindMe ID to individuals or teams in your enterprise. By logging into their
FindMe account, users can set up a list of locations such as "at home" or "in the office" and associate their devices
with those locations. They can then specify which devices are called when their FindMe ID is dialed, and what
happens if those devices are busy or go unanswered. Each user can specify up to 15 devices and 10 locations.
This means that potential callers can be given a single FindMe alias on which they can contact an individual or group
in your enterprise callers wont have to know details of all the devices on which that person or group might be
available.
To enable this feature you must purchase and install the FindMe option key. Standard operation is to use the VCS's
own FindMe manager. However, you can use an off-box FindMe manager; this feature is intended for future third-
party integration.
End-User FindMe Account Configuration

From VCS version X7.1, the way that users can configure their FindMe settings depends upon whether or not the VCS
is using Cisco TMS provisioning:
If Cisco TMS provisioning is enabled:

Users manage their FindMe settings by logging into their FindMe account via Cisco TMS.
User account and FindMe data is provided by Cisco TMS to VCS via the TMS Provisioning Extension
services.
If you are using FindMe without Cisco TMS (known as "standalone FindMe") then users manage their FindMe
settings by logging into their FindMe account via VCS.
See FindMe Deployment Guide for more details about setting up FindMe accounts.
How are Devices Specified?

When configuring their FindMe account, users are asked to specify the devices to which calls to their FindMe ID are
routed.
It is possible to specify aliases and even other FindMe IDs as one or more of the devices. However, care must be
taken in these situations to avoid circular configurations.
For this reason, we recommend that users specify the physical devices they want to ring when their FindMe ID is
called by entering the alias with which that device has registered.
Principal devices
A FindMe user's account should be configured with one or more principal devices. These are the main devices
associated with that account.
Users are not allowed to delete or change the address of their principal devices. This is to stop users from
unintentionally changing their basic FindMe configuration.
Principal devices are also used by the VCS to decide which FindMe ID to display as a Caller ID if the same device
address is associated with more than one FindMe ID. Only an administrator (and not FindMe users themselves) can
configure which of a FindMe user's devices are their principal devices.
FindMe Process Overview

When the VCS receives a call for a particular alias it applies its User Policy as follows:
244
It first checks to see if FindMe is enabled. If so, it checks if the alias is a FindMe ID, and, if it is, the call is
forwarded to the aliases associated with the active location for that user's FindMe configuration.
If FindMe is not enabled, or the alias is not a FindMe ID, the VCS continues to search for the alias in the usual
manner.
Note that User Policy is invoked after any Call Policy configured on the VCS has been applied. See Call Routing
Process, page 172 for more information.
Recommendations when Deploying FindMe

The FindMe ID should be in the form of a URI, and should be the individuals primary URI.
Endpoints should not register with an alias that is the same as an existing FindMe ID. You can prevent this by
including all FindMe IDs on the Deny List.
Example
Users at Example Corp. have a FindMe ID in the format [email protected]. Each of the users endpoints are
registered with a slightly different alias that identifies its physical location. For example their office endpoint is
registered with an alias in the format [email protected] and their home endpoint as
[email protected].
Both of these endpoints are included in the list of devices to ring when the FindMe ID is dialed. The alias
[email protected] is added to the Deny List, to prevent an individual endpoint registering with that alias.
Configuring FindMe
The FindMe configuration page (Applications > FindMe) is used to enable and configure FindMe User Policy.
Note that the FindMe configuration page can only be accessed if the FindMe option key is installed.
FindMe mode Determines whether or not FindMe is enabled, Call Policy is always applied regardless of the
and if a third-party manager is to be used. FindMe mode.
Off: disables FindMe. If you enable FindMe, you must ensure a

Cluster name is specified (you do this on the
On: enables FindMe and uses the VCSs local Clustering page).
FindMe manager.
Note that FindMe mode is automatically set to
Remote service: enables FindMe and uses a On when the Starter Pack option key is
FindMe manager located on an off-box system. installed.
This feature is intended for advanced
deployments with third-party integrators.
245
Caller ID Determines how the source of an incoming call Using FindMe ID means that if the recipient
is presented to the callee. subsequently returns that call, all the devices
associated with that FindMe account will be
Incoming ID: displays the address of the called. For H.323 calls placed through an ISDN
endpoint from which the call was placed. gateway, the E.164 phone number associated
with the FindMe account is signaled instead as
FindMe ID: displays the FindMe ID associated that is a more appropriate number to dial when
with the originating endpoint's address. returning the call. Note that the ISDN gateway
must be registered to the same VCS as the call
recipient.
The FindMe ID is only displayed if the source

endpoint has been authenticated (or treated as
authenticated). If it is not authenticated the
Incoming ID is displayed. See About Device
Authentication, page 108 for more details.
Restrict users Controls if users are restricted from adding, By default FindMe users are allowed to
from deleting or modifying their own devices. The configure further devices in addition to any
configuring default is Off. principal or provisioned devices assigned to
their devices them by the system administrator. This setting
can be used to stop users from adding their
own devices and restrict them to being able to
only maintain their locations and their
associated devices.
This setting only applies if you are using

FindMe without Cisco TMS (known as
"standalone FindMe").
Device Only applies when FindMe mode is On. It can be used to provide information about
creation how to format the device address or number,
message The text entered here is displayed to users when for example any dial prefixes that must be
they add a device to their FindMe configuration. included.
A limited set of HTML markup is supported in the An example message could be:
message which is previewed in the window at
the bottom of the page when you click Save. Phone numbers: use the prefix <b>9</b>
The following tags (without any attributes) are Endpoints: use the suffix
allowed: <b>@video.test.com</b>
b i tt big small strike s u em strong cite
dfn samp kbd var abbr acronym sub sup ins This setting only applies if you are using
del br FindMe without Cisco TMS (known as
"standalone FindMe").
<a href=> is also supported, but the URL can
only contain A-Z 0-9, dot, "?" "=" and "%";
note that the URL is relative to the current page
so you must prefix it with, for example, http:// if
you want to refer to an external site.
The following options apply when FindMe mode is Remote service:
Field Description
Protocol The protocol used to connect to the remote service.
Address The IP address or domain name of the remote service.
246
Field Description
Path The URL of the remote service.
Username The username used by the VCS to log in and query the remote service.
Password The password used by the VCS to log in and query the remote service.
If the Starter Pack option key is installed the Presence Server and FindMe are automatically enabled.
Management and Storage of FindMe Data

If you use FindMe without Cisco TMS (known as "standalone FindMe") or the Starter Pack option key is installed, the
VCSs local database is used to store FindMe data and share it across all peers in a cluster.
If you use FindMe and want to use Cisco TMS to manage your FindMe data, you must configure Cisco TMSPE
services to provide the VCS with FindMe data.
Note that if you have the Device Provisioning option key installed, you must use Cisco TMSPE services to obtain
FindMe configuration data from Cisco TMS.
247
Cisco TMS Provisioning

Cisco TMS provisioning is the mechanism through which the VCS and Cisco TMS share FindMe and device
provisioning data. The shared data includes:
user account, device and phone book data that is used by the VCS to service provisioning requests from
endpoint devices
FindMe account configuration data that is used by the VCS to provide FindMe services
The FindMe and Device Provisioning option keys must be installed on the VCS for it to provide FindMe and
provisioning services.
As from version X8.1, the VCS supports only the Cisco TelePresence Management Suite Provisioning Extension
(Cisco TMSPE) services to provide the VCS with provisioning and FindMe data. In this mode all provisioning and
FindMe data is managed and maintained exclusively within Cisco TMS.
Size limitations for clusters and provisioning
A VCS cluster of any size supports up to:
10,000 FindMe accounts

10,000 users for provisioning
200,000 phonebook entries
Note that:
Small/Medium systems can support up to 2,500 device registrations per peer, subject to a maximum of 10,000
registrations per cluster. Typically this means one device per FindMe account.
Large systems can support up to 5,000 device registrations per peer (with a maximum of 20,000 registrations
per cluster). However, you are still limited to 10,000 FindMe accounts/users and 10,000 provisioned devices
per cluster.
If you need to provision more than 10,000 devices, your network will require additional VCS clusters with an
appropriately designed and configured dial plan.
See Cisco TMS Provisioning Extension Deployment Guide for full information about how to configure provisioning in
Cisco TMS and VCS.
Cisco TMSPE services
When TMS provisioning is enabled, the VCS uses the following Cisco TMSPE services (which are hosted on Cisco
TMS) to provide the VCS (or VCS cluster) with provisioning and FindMe data:
Service Description
User The data provided by the User Preference service enables the VCS to configure a device with
Preference settings that pertain to a specific user (a user is essentially a SIP URI). Devices such as Jabber Video
are configured entirely using this service. This service also provides connection details to a
TURNserver (typically the VCS Expressway).
FindMe The FindMe service provides the details of users' FindMe accounts, in particular the locations and
devices associated with each FindMe ID. This allows the VCS to apply its User Policy, and to be able
to change a caller's source alias to its corresponding FindMe ID.
Phone The Phone books service provides the data that allows users to search for contacts within phone
books books. Access to phone books is controlled on a per user basis according to any access control lists
that have been defined (within Cisco TMS).
248
Service Description
Devices The Devices service exchanges provisioning licensing information between the VCS and Cisco TMS.
Information is exchanged every 30 seconds the VCS is provided with the current number of free
licenses available across the range of VCS clusters being managed by Cisco TMS, and the VCS
updates Cisco TMS with the status of provisioning licenses being used by this VCS (or VCS cluster).
If the Devices service is not active, the VCS's Provisioning Server will not be able to provision any
devices.
The current status of the services is displayed on the TMSProvisioning Extension service status page.
The VCS periodically polls the Cisco TMSPE services to ensure the data held on VCS is kept up to date. The
polling interval can be defined for each service. In typical deployments you are recommended to use the
default settings which provide frequent (every 2 minutes) updates to FindMe and user provisioning data, and
daily updates to phone book data.
If you have a cluster of VCSs, only one of the cluster peers maintains the physical connection to Cisco TMS.
The data obtained from Cisco TMS is then shared between other peers in the cluster through the VCS's cluster
replication mechanism.
A full and immediate resynchronization of all data between the VCS and Cisco TMS can be triggered at any
time by clicking Perform full synchronization (at the bottom of the of the TMS Provisioning Extension
services page). Note that this will result in a temporary (a few seconds) lack of service on the VCS while the
data is deleted and fully refreshed. If you only need to ensure that all of the latest updates within Cisco TMS
have been supplied to the VCS then click Check for updates instead.
You are recommended to use Cisco TMS to make any changes to the Cisco TMSPE services' configuration settings.
You can configure the services on the VCS through the TMSProvisioning Extension services page, but any changes
made to the settings via this page will not be applied within Cisco TMS.
Using FindMe without Cisco TMS
If you use FindMe without TMS (known as "standalone FindMe"), then all FindMe account information is stored and
managed locally on the VCS. See FindMe Deployment Guide for more information.
VCS Provisioning Server

The VCS Provisioning Server provides provisioning-related services to provisioned devices, using data supplied by
Cisco TMS through the Cisco TMS provisioning mechanism. The server only operates if the Device Provisioning
option key is installed.
Provisioning Server Status

Comprehensive status information can be found under the VCS's (Status > Applications >TMSProvisioning
Extension services) menu options.
Provisioning Licenses
There is a limit to the number of devices that can be provisioned concurrently by the Provisioning Server. VCS and
Cisco TMS manage the number of available provisioning licenses by exchanging information through the Cisco
TMSPE Devices service. If the Devices service is not active, the VCS's Provisioning Server will not be able to provision
any devices.
The VCS is provided with the current number of free licenses available across the range of VCS clusters being
managed by Cisco TMS, and the VCS updates Cisco TMS with the status of provisioning licenses being used by this
VCS (or VCS cluster). License limits can be managed at a per device type basis.
249
Go to Status > Applications >TMSProvisioning Extension services > Device requests to see a summary
status of the provisioning licenses that are available within your system.
Go to Status > Applications >TMSProvisioning Extension services > Provisioned device status to see a list
of all of the devices that have submitted provisioning requests to the Provisioning Server.
Note that some devices, including Jabber Video 4.x, do not inform the VCS when they sign out (unsubscribe) from
being provisioned. The VCS manages these devices by applying a 1 hour timeout interval before releasing the
license.
Provisioning and Device Authentication

See Device Provisioning and Authentication Policy, page 118 for more information.
250
Starter Pack Provisioning

The VCS's Starter Pack Provisioning Server provides basic device provisioning, including phone book support, for a
range of endpoint device types without the need for Cisco TMS.
The Starter Pack option key must be installed to use basic device provisioning. It cannot be used in combination with
device provisioning managed through TMS. Note that the Starter Pack option key is designed for single box
deployments and is only available as a pre-configured factory setting.
Starter Pack
The Starter Pack is suitable for small enterprises. It provides basic VCS functionality and includes Expressway and
FindMe functionality automatically.
The following license restrictions apply by default:
50 registrations
5 traversal calls (extra traversal call license option keys can be added if required)
900 TURN relays
Note that:
non-traversal calls are supported (a traversal license is used when one occurs)
the Starter Pack has a maximum limit of 25 calls
When the Starter Pack option key is installed the Presence Server and FindMe are automatically enabled.
Configuring Starter Pack Provisioning

The Provisioning page (Applications > Provisioning) is used to configure the VCS's Provisioning Server when the
VCS is running in Starter Pack mode.
The Starter Pack Provisioning Server provides basic device provisioning and is automatically enabled when the
Starter Pack option key is installed. It can be monitored on the Starter Pack status page.
Bandwidth limits
The Bandwidth limits section lists each supported device type and lets you choose whether or not to enable the
provisioning of bandwidth limits for that device. If you enable the bandwidth limits option for a device type you can
then configure the maximum incoming and outgoing bandwidth (in kbps) values to set on the provisioned devices.
ClearPath
The ClearPath section lists each supported device type and lets you choose whether or not to enable the provisioning
of ClearPath for that device.
Provisioning Users
To provision individual users, you must set up FindMe accounts. When you configure a FindMe account, you can
choose the devices to provision for that user. The FindMe account is also used to configure the user's FindMe
settings.
See VCS Starter Pack Express Deployment Guide for full details on setting up Starter Pack provisioning.
Hybrid Services and Connector Management

If you are already registered for Hybrid Services, visit the Hybrid Services help site to get more detailed and recent
information.
What are Hybrid Services and what do they do?
Cisco Hybrid Services empower cloud-based and premises-based solutions to deliver a more capable, better
251
integrated collaboration user experience.
Which services am Ientitled to use?
When you purchase Hybrid Services you get access to Cloud Collaboration Management an administrative
interface to the Cisco Collaboration Cloud. In Cloud Collaboration Management you can check your organization's
service entitlements and enable features for your users.
What software do Ineed?
The on-premises components of Hybrid Services are called "connectors", and the VCS software contains a
management connector to manage registration and other connectors.
The management connector is dormant until you register. When you register, the management connector is
automatically upgraded if a newer version is available.
The VCS then downloads any other connectors that you selected using Cloud Collaboration Management. They are
not started by default and you need to do some configuration before they'll work.
How do Iinstall, upgrade, or downgrade?
The connectors are not active by default, and will not do anything until you configure and start them. You can do this
on new UI pages that the connectors install on the VCS.
Connector upgrades are made available through Cloud Collaboration Management, and the management connector
will download the new versions to VCS when you have authorized the upgrade.
You can also deregister, which disconnects your VCS from Collaboration Cloud and removes all connectors and
related configuration.
Note:We do not normally advise downgrading VCS, although we try to ensure that the interface remains accessible if
you are forced to restore a previous version. However, we explicitly do not support a downgrade of the VCS software
from X8.6 versions while the VCS is registered for Hybrid Services. If you have to downgrade, you must deregister
from Hybrid Services before you downgrade.
Where can Iread more about Hybrid Services?
Hybrid Services are continuously developed and may be published more frequently than VCS. This means that
information about Hybrid Services is maintained on the Hybrid Services help site, and several VCS interface pages
link out to that site.
Connector Proxy
If you are already registered for Hybrid Services, visit the Hybrid Services help site to get more detailed and recent
information.
What is this proxy for?
Use the Applications >Hybrid Services>Connector Proxy page if this VCS needs a proxy to connect to the Cisco
Collaboration Cloud. This proxy is not used by the VCS for other purposes.
What kind of traffic goes through this proxy?
The proxy must be capable of handling outbound HTTPSand secure web socket connections. It must also allow
those connections to be initiated by the VCS using either basic authentication or no authentication.
What details do Ineed to configure the proxy?
You'll need the address of the proxy, the port it's listening on, and the basic authentication username and password
252
(if your proxy requires authentication).
Collaboration Cloud CARoot Certificates on VCS Expressway

The Cisco Collaboration Cloud CA root certificates are packaged in the VCS software and you can click Get
certificates to load them into the trusted CAlist. You can click Remove certificates to reverse this decision if
necessary.
The VCS Expressway needs to trust these CAs so that it can authenticate the server certificates from Collaboration
Cloud, to make the encrypted connections needed by some VCS-based hybrid services.
Note:The VCS Expressway cannot register for hybrid services. It must be connected by a secure traversal zone to the
VCS (or cluster) that is registered to the Collaboration Cloud.
Root certificates from the following CAs will be installed when you click Get certificates:
O=The Go Daddy Group, Inc., OU=Go Daddy Class 2 Certification Authority

O=QuoVadis Limited, CN=QuoVadis Root CA 2
O=VeriSign, Inc., OU=Class 3 Public Primary Certification Authority
You can verify that the certificates are installed, and manually maintain the trusted CAlist, on the Maintenance >
Security certificates >Trusted CAcertificate page. See Managing the Trusted CA Certificate List, page 282 for
more help.
253
User Accounts
This section provides information about how to configure administrator and FindMe user accounts, and how to display
the details of all active administrator and FindMe sessions.
About User Accounts 254

Configuring Password Security 256
Configuring Administrator Accounts 257
Configuring Remote Account Authentication Using LDAP 259
Configuring FindMe Accounts 265
Resetting Forgotten Passwords 267
Using the Root Account 269
Managing SSOtokens 269
About User Accounts

The VCS has two types of user account for normal operation:
Administrator accounts: used to configure the VCS.

FindMe accounts: used by individuals in an enterprise to configure their FindMe profile. They can also be used
to enable basic device provisioning when the Starter Pack option key is installed.
Note that FindMe account configuration via VCS does not apply if the VCS is using the TMS Provisioning Extension
services to provide FindMe data.
Account Authentication
Administrator and FindMe accounts must be authenticated before access is allowed to the VCS.
VCS can authenticate accounts either locally or against a remote directory service using LDAP (currently, only
Windows Active Directory is supported), or it can use a combination of local and remotely managed accounts. The
remote option allows administration groups to be set up in the directory service for all VCSs in an enterprise, removing
the need to have separate accounts on each VCS.
See Configuring Remote Account Authentication Using LDAP, page 259 and Authenticating VCS Accounts using
LDAP Deployment Guide for more information about setting up remote authentication.
If a remote source is used for either administrator or FindMe account authentication, you also need to configure the
VCS with:
appropriate LDAP server connection settings

administrator groups and/or FindMe groups that match the corresponding group names already set up in the
remote directory service to manage administrator and FindMe access to this VCS (see Configuring
Administrator Groups, page 263 and Configuring FindMe Groups, page 264)
The VCS can also be configured to use certificate-based authentication. This would typically be required if the VCS
was deployed in a highly-secure environment.
254
Account Types
Administrator accounts
Administrator accounts are used to configure the VCS.
The VCS has a default admin local administrator account with full read-write access. It can be used to access
the VCS using the web interface, the API interface or the CLI. Note that you cannot access the VCS via the
default admin account if a Remote only authentication source is in use.
You can add additional local administrator accounts which can be used to access the VCS using the web and
API interfaces only.
Remotely managed administrator accounts can be used to access the VCS using the web and API interfaces
only.
You can configure the complexity requirements for local administrator passwords on the Password security page
(Users > Password security). All passwords and usernames are case sensitive.
Note that:
The Configuration Log records all login attempts and configuration changes made using the web interface,
and can be used as an audit trail. This is particularly useful when you have multiple administrator accounts.
More than one administrator session can be running at the same time. These sessions could be using the web
interface, command line interface, or a mixture of both. This may cause confusion if each administrator
session attempts to modify the same configuration settings - changes made in one session will overwrite
changes made in another session.
You can configure account session limits and inactivity timeouts (see Configuring System Name and Access
Settings, page 26).
If the system is in advanced account security mode, a Login history page is displayed immediately after
logging in. It shows the recent activity of the currently logged in account.
See the Configuring Administrator Accounts, page 257 section for more information.
FindMe accounts
FindMe accounts are used by individuals in an enterprise to configure the devices and locations on which they can be
contacted through their FindMe ID.
Each FindMe account is accessed using a username and password.
If local FindMe account authentication is selected, each FindMe account must be created locally by the VCS
administrator.
If remote FindMe account authentication is selected, the VCS administrator must set up FindMe groups to
match the corresponding group names in the remote directory service. Note that only the username and
password details are managed remotely. All other properties of the FindMe account, such as the FindMe ID,
devices and locations are stored in the local VCS database.
See the Configuring FindMe Accounts, page 265 section for more information about defining FindMe account details
and their associated FindMe devices and locations, and for enabling basic Starter Pack provisioning.
We recommend that you use Cisco TMS if you need to provision a large number of FindMe accounts. See Cisco TMS
Provisioning Extension Deployment Guide for more details on configuring FindMe and user accounts.
Root account
The VCS provides a root account which can be used to log in to the VCS operating system. The root account should
not be used in normal operation, and in particular system configuration should not be conducted using this account.
Use the admin account instead.
See the Using the Root Account, page 269 section for more information.
Note: remember to change the passwords for the admin and root accounts from their default values.
255
Configuring Password Security

The Password security page (Users > Password security) controls whether or not local administrator account
passwords must meet a minimum level of complexity before they are accepted.
If Enforce strict passwords is set to On, all subsequently configured local administrator account passwords must
conform to the following rules for what constitutes a strict password.
If Enforce strict passwords is set to Off, no extra checks are made on local administrator account passwords.
Notes:
You can never set a blank password for any administrator account, regardless of this setting.
This setting affects only local administrator account passwords. It does not affect any other passwords used
on the VCS, such as in the local authentication database, LDAP server, external registration credentials, user
account passwords, or administrator account passwords stored on remote credential directories.
All passwords and usernames are case sensitive.
Non-configurable rules for strict passwords
The following password rules always apply when Enforce strict passwords is set to On. There is no way to configure
them:
Avoid multiple instances of the same characters (non-consecutive instances are checked)
Avoid three or more consecutive characters such as "abc" or "123"
Avoid dictionary words, or reversed dictionary words
Avoid palindromes, such as "risetovotesir"
Configurable rules for strict passwords
The following properties of the password policy can be configured:
Length must be at least 6 ASCIIcharacters, but can be up to 255 (default 15)

Number of numeric digits [0-9] may be between 0 and 255 (default 2)
Number of uppercase letters [A-Z] may be between 0 and 255 (default 2)
Number of lowercase letters [a-z] may be between 0 and 255 (default 2)
Number of special characters [printable characters from 7-bit ASCII,eg. (space), @, $ etc.)] may be between
0 and 255 (default 2)
Number of consecutive repeated characters allowed may be between 1 and 255 (the default 0 disables the
check, so consecutive repeated characters are allowed by default; set it to 1 to prevent a password from
containing any consecutive repeats)
The minimum number of character classes may be between 0 and 4 (the default 0 disables the check).
Character classes are digits, lowercase letters, uppercase letters, and special characters.
Note: You may experience precedence effects between the required number of character classes and the
number of characters per class.
For example, if you leave the default requirements of 2 characters of each class, there is an implied rule that 4
character classes are required. In this case, any setting of Minimum number of character classes is
irrelevant.
For another example, if you set the minimum number of character classes to 2, and set the minimum number of
characters required from each class to 0, then a password that contains characters from any two of the
classes will suffice (presuming it meets all the other criteria as well).
256
Configuring Administrator Accounts

The Administrator accounts page (Users > Administrator accounts) lists all the local administrator accounts on the
VCS.
In general, local administrator accounts are used to access the VCS on its web interface or API interface, but are not
permitted to access the CLI.
On this page you can:
Create a new administrator account

Change an administrator password
Change the access level of an account: Read-write, Read-only, or Auditor
Change the access scope of an account: Web access, APIaccess, or both
Delete, enable, or disable individual or multiple administrator accounts
Editing administrator account details
You can edit the details for the default administrator account and for additional local administrator accounts.
Go to Users >Administrator accounts. Under Actions for the relevant administrator account, click Edit user.
A new page is displayed, where you can edit all fields for the selected administrator account except for the password.
To change the password, see below.
About the "admin" account
This default local administrator account has full Read-write access and can access the VCS using the web UI, the
API interface, or the CLI. You can access the VCS via the admin account even if a Remote authentication source is in
use.
The username for this account is admin (all lower case) and the default password is TANDBERG (all upper case).
You cannot delete, rename, or disable admin and you cannot change its access level from Read-write, but you can
disable its web and API access.
You should change the password as soon as possible. Choose a strong password, particularly if administration over
IP is enabled.
If you forget the password for the admin account, you can log in as another administrator account with read-write
access and change the password for the admin account. If there are no other administrator accounts, or you have
forgotten those passwords as well, you can still reset the password for the admin account providing you have
physical access to the VCS. See Resetting Forgotten Passwords, page 267 for details.
Administrator account fields reference
Name The username for the administrator account. Some names such as "root" are reserved. Local
administrator account user names are case
sensitive.
257
Access The access level of the administrator account: The access permissions of the currently logged in
level user are shown in the system information bar at
Read-write: allows all configuration information the bottom of each web page.
to be viewed and changed. This provides the
same rights as the default admin account. The access level of the default admin account
cannot be changed from Read-write.
Read-only: allows status and configuration
information to be viewed only and not changed.
Some pages, such as the Upgrade page, are
blocked to read-only accounts.
Auditor: allows access to the Event Log,

Configuration Log, Network Log, Alarms and
Overview pages only .
Default: Read-write
Password The password that this administrator will use to All passwords on the VCS are encrypted, so you
log in to the VCS. only see placeholder characters here.
When entering passwords, the bar next to the

Password field changes color to indicate the
complexity of the password. You can configure
the complexity requirements for local
administrator passwords on the Password security
page (Users > Password security).
You cannot set blank passwords.
New Enter a new password for the account. This field only appears when you are changing a
password password.
Confirm Re-enter the password for the account. This field only appears when you create an
password account or when you change its password.
Web Select whether this account is allowed to log in

access to the system using the web interface.
Default: Yes
APIaccess Select whether this account is allowed to access This controls access to the XML and REST APIs by
the system's status and configuration using the systems such as Cisco TMS.
Application Programming Interface (API).
Default: Yes
State Select whether the account is Enabled or

Disabled. Disabled accounts are not allowed to
access the system.
Your Enter your own, current password here if the To improve security, the system requires that
current system requires you to authorize a change. administrators enter their own passwords when
password creating an account or changing a password.
Viewing Active Administrator Sessions

The Active administrator sessions page (Users > Active administrator sessions) lists all administrator accounts
that are currently logged in to this VCS.
258
It displays details of their session including their login time, session type, IP address and port, and when they last
accessed this VCS.
You can terminate active web sessions by selecting the required sessions and clicking Terminate session.
You may see many sessions listed on this page if a zero Session time out value is configured. This typically occurs if
an administrator ends their session by closing down their browser without first logging out of the VCS.
Login History
The Login history page is displayed immediately after logging in, when the system is in advanced account security
mode. It shows the recent activity of the currently logged in account.
This session
This section shows the login date and time of the currently logged in account, and the IP address from where the
login originated.
Previous sessions (for this account)
This section shows the date, time and source IP address of the last successful login for this account. If applicable it
also shows details of the last failed login attempt for this account, and the number of failed login attempts since the
last successful login.
Configuring Remote Account Authentication Using LDAP

The LDAP configuration page (Users > LDAPconfiguration) is used to configure an LDAP connection to a remote
directory service for administrator account authentication. It can also provide user account authentication if you are
using FindMe without Cisco TMS.
Remote account authentication: this section allows you to enable or disable the use of LDAP for remote account
authentication.
Administrator Defines where administrator login credentials are Both allows you to continue to use
authentication authenticated. locally-defined accounts. This is useful
source while troubleshooting any connection or
Local only: credentials are verified against a local authorization issues with the LDAP server.
database stored on the system.
You cannot log in using a locally-
Remote only: credentials are verified against an configured administrator account,
external credentials directory. including the default admin account, if
Remote only authentication is in use.
Both: credentials are verified first against a local Note: do not use Remote only if VCS is
database stored on the system, and then if no managed by Cisco TMS.
matching account is found the external credentials
directory is used instead.
The default is Local only.
259
FindMe Defines where FindMe account credentials are This option applies only if you are using
authentication authenticated: FindMe without Cisco TMS.
source
Remote: credentials are verified against an external
credentials directory (the VCS currently supports only
Windows Active Directory).
Local: credentials are verified against a local

database stored on the VCS.
The default is Local.
LDAP server configuration: this section specifies the connection details to the LDAP server.
FQDN Defines how the LDAP server address is resolved. The SRV lookup is for either _ldap._tcp or
address _ldaps._tcp records, depending on
resolution SRV record: DNS SRV record lookup. whether Encryption is enabled. If multiple
servers are returned, the priority and
Address record: DNS A or AAAA record lookup. weight of each SRV record determines the
order in which the servers are used.
IP address: entered directly as an IP address.
The default is Address record.
Note:if you use SRVrecords, ensure that the records

use the standard ports for LDAP. _ldap._tcp.<domain>
must use 389 and _ldaps._tcp.<domain> must use
636. The VCS does not support other port numbers for
LDAP.
Host name The way in which the server address is specified If using TLS, the address entered here
and Domain depends on the FQDN address resolution setting: must match the CN (common name)
contained within the certificate presented
or SRV record: only the Domain portion of the server by the LDAP server.
address is required.
Server
address Address record: enter the Host name and Domain.
These are then combined to provide the full server
address for the DNS address record lookup.
IP address: the Server address is entered directly as

an IP address.
Port The IP port to use on the LDAP server. Non-secure connections use 389 and
secure connections use 636.
Encryption Determines whether the connection to the LDAP When TLS is enabled, the LDAP servers
server is encrypted using Transport Layer Security certificate must be signed by an authority
(TLS). within the VCSs trusted CA certificates
file.
TLS: uses TLS encryption for the connection to the
LDAP server. Click Upload a CA certificate file for TLS
(in the Related tasks section) to go to the
Off: no encryption is used. Managing the Trusted CA Certificate List,
page 282 page.
The default is TLS.
260
Certificate Specifies whether certificate revocation lists (CRLs) If you are using revocation lists, any
revocation list are checked when forming a TLS connection with the required CRL data must also be included
(CRL) LDAP server. within the CA certificate file.
checking
Peer: only the CRL associated with the CA that issued

the LDAP server's certificate is checked.
All: all CRLs in the trusted certificate chain of the CA

that issued the LDAP server's certificate are checked.
The default is None.
Authentication configuration: this section specifies the VCS's authentication credentials to use when binding to
the LDAP server.
Bind DN The distinguished name (case insensitive) used by the Any special characters within a name
VCS when binding to the LDAP server. must be escaped with a backslash as per
the LDAP standard (RFC 4514). Do not
It is important to specify the DN in the order cn=, then escape the separator character between
ou=, then dc= names.
The bind account is usually a read-only

account with no special privileges.
Bind The password (case sensitive) used by the VCS when The maximum plaintext length is 60
password binding to the LDAP server. characters, which is then encrypted.
SASL The SASL (Simple Authentication and Security Layer) Enable Simple Authentication and
mechanism to use when binding to the LDAP server. Security Layer if it is company policy to do
so.
None: no mechanism is used.
DIGEST-MD5: the DIGEST-MD5 mechanism is used.
The default is DIGEST-MD5.
Bind Username of the account that the VCS will use to log Configure this to be the
username in to the LDAP server (case sensitive). sAMAccountName; Security Access
Manager Account Name (in AD this is the
Only required if SASL is enabled. accounts user logon name).
Directory configuration: this section specifies the base distinguished names to use when searching for account
and group names.
Base DN for The ou= and dc= definition of the Distinguished Name This is for authentication of both
accounts where a search for user accounts should start in the administrator login and user login
database structure (case insensitive). requests.
It is important to specify the DN in the order ou=, then The Base DN for accounts and groups
dc= must be at or below the dc level (include
all dc= values and ou= values if
necessary). LDAP authentication does not
look into sub dc accounts, only lower ou=
and cn= levels.
261
Base DN for The ou= and dc= definition of the Distinguished Name This is for authorization of an
groups where a search for groups should start in the authenticated user to log in as an
database structure (case insensitive). administrator or to log in to a user
account.
It is important to specify the DN in the order ou=, then If no Base DN for groups is specified,
dc= then the Base DN for accounts will be
used for both groups and accounts.
Checking the LDAP Server Connection Status

The status of the connection to LDAP server is displayed at the bottom of the page.
State = Active
No error messages are displayed.
State = Failed
The following error messages may be displayed:
Error message Reason / resolution
DNS unable to do reverse lookup Reverse DNS lookup is required for SASL authentication.
DNS unable to resolve LDAP server Check that a valid DNS server is configured, and check the spelling of the
address LDAP server address.
Failed to connect to LDAP server. Check that the LDAP server details are correct.
Check server address and port
Failed to setup TLS connection. CA certificate, private key and server certificate are required for TLS.
Check your CA certificate
Failure connecting to server. Returned Other non-specific problem.

code<return code>
Invalid Base DN for accounts Check Base DN for accounts; the current value does not describe a valid
part of the LDAP directory.
Invalid server name or DNS failure DNS resolution of the LDAP server name is failing.
Invalid bind credentials Check Bind DN and Bind password, this error can also be displayed if
SASL is set to DIGEST-MD5 when it should be set to None.
Invalid bind DN Check Bind DN; the current value does not describe a valid account in the
LDAP director.
This failed state may be wrongly reported if the Bind DN is 74 or more

characters in length. To check whether there is a real failure or not, set up
an administrator group on the VCS using a valid group name. If VCS
reports saved then there is not a problem (the VCS checks that it can
find the group specified). If it reports that the group cannot be found then
either the Bind DN is wrong, the group is wrong or one of the other
configuration items may be wrong.
There is no CA certificate installed CA certificate, private key and server certificate are required for TLS.
Unable to get configuration LDAP server information may be missing or incorrect.
262
Configuring Administrator Groups

The Administrator groups page (Users > Administrator groups) lists all the administrator groups that have been
configured on the VCS, and lets you add, edit and delete groups.
Administrator groups only apply if remote account authentication is enabled.
When you log in to the VCS web interface, your credentials are authenticated against the remote directory service
and you are assigned the access rightsassociatedwith the group to which you belong. If the administratoraccount
belongs to more than one group, thehighest level permission is assigned.
Name The name of the administrator group. The group names defined in the VCS must
match the group namesthat have been set up
It cannot contain any of the following characters: in theremote directory serviceto manage
administrator access to this VCS.
/\[]:;|=,+*?><@"
Access The access level given to members of the administrator If an administrator belongs to more than one
level group: group, it is assigned the highest level
permission for each of the access settings
Read-write: allows all configuration information to be across all of the groups to which it belongs
viewed and changed. This provides the same rights as (any groups in a disabled state are ignored).
the default admin account. See Determining the access level for accounts
that belong in multiple groups, page 263
Read-only: allows status and configuration information below for more information.
to be viewed only and not changed. Some pages, such
as the Upgrade page, are blocked to read-only
accounts.
Auditor: allows access to the Event Log, Configuration

Log, Network Log, Alarms and Overview pages only .
None: no access is allowed.
Default: Read-write
Web Determines whether members of this group are allowed

access to log in to the system using the web interface.
Default: Yes
API Determines whether members of this group are allowed This controls access to the XML and REST
access to access the system's status and configuration using APIs by systems such as Cisco TMS.
the Application Programming Interface (API).
Default: Yes
State Indicates if the group is enabled or disabled. Access will If an administrator account belongs to more
be denied to members of disabled groups. than one administrator group with a
combination of both Enabled and Disabled
states, their access will be Enabled.
Determining the access level for accounts that belong in multiple groups
If an administrator belongs to groups with different levels of access, the highest level of access is granted. Any
groups in a disabled state are ignored.
263
For example, if the following groups were configured:
Group name Access level Web access API access
Administrators Read-write - -
Region A Read-only Yes -
Region B Read-only - Yes
Region C Read-only Yes Yes
The following table shows examples of the access permissions that would be granted for accounts that belong in one
or more of those groups:
Groups belonged to Access permissions granted
Administrators and Region A read-write access to the web interface but no API access
Administrators and Region B read-write access to the API interface, but no web interface access
Administrators and Region C read-write access to the web and API interfaces
Region A only read-only access to the web interface and no API access
Configuring FindMe Groups

The FindMe groups page (Users > FindMe groups) lists all the FindMe groups that have been configured on the
VCS, and lets you add, edit and delete groups.
Note that this page does not apply if the VCS is using TMS Provisioning Extension services to provide FindMe account
data; in this case, FindMe accounts are maintained through Cisco TMS.
FindMe groups are only active when remote FindMe authentication is enabled.
FindMe groups determine which access rights members of the group have after they have been successfully
authenticated to use the VCS.
When a FindMe user logs in to the VCS their credentials are authenticated against the remote directory service and
they are assigned the access rightsassociatedwith the group to which that user belongs. If the useraccount belongs
to more than one group, thehighest level permission is assigned.
Name The name of the FindMe group. The group names defined in the VCS must match the group
namesthat have been set up in theremote directory service to
It cannot contain any of the following manage FindMe accounts.
characters:
/\[]:;|=,+*?><@"
264
State Indicates if the group is enabled or

disabled.
Enabled: users can view and modify

their personal FindMe details, devices
and locations.
Disabled: users are not allowed to log

in to their account.
Default: Enabled
Configuring FindMe Accounts

The FindMe accounts page (Users > FindMe accounts) lists all the FindMe accounts that have been configured on
the VCS, and lets you add, edit and delete accounts.
FindMe accounts are used by individuals in an enterprise to configure the devices and locations on which they can be
contacted through their FindMe ID. Each FindMe account is accessed using a username and password.
If local FindMe account authentication is selected, each FindMe account must be created locally by the VCS
administrator.
If remote FindMe account authentication is selected, the VCS administrator must set up FindMe groups to
match the corresponding group names in the remote directory service.
Filtering the view
The Filter section lets you filter the set of records. Enter the word or phrase you want to search for and click Filter.
Only those records that contain the word or phrase you entered are shown.
Configuring an account
Click New to set up a new account, or click View/Edit (or the username) to edit an existing FindMe account.
The configurable options for a FindMe account are:
Username The account name. It is used (along If remote authentication is enabled, the username defined in
with a password) by the user to log in the VCS must match the username set up in the remote
to the VCS and configure their FindMe directory service.
details. The username cannot be
changed after the account has been
created.
Display A free-form display name for the user The Display name is used in phone books and as the caller
name (rather than the user's Username or display name in SIP calls.
FindMe ID).
Phone The numeric caller ID presented when To allow call return, this number could be configured to route
number making an outbound call through an to the associated FindMe ID by mapping incoming numbers to
ISDN gateway. the FindMe ID using ENUM, search rules or CPL. See FindMe
Deployment Guide for more information.
265
FindMe ID The FindMe alias the dialable The FindMe ID can be any string of up to 60 characters.
address by which the user can be However, not all endpoints are able to dial aliases with spaces
contacted. or other non-alphanumeric characters so we recommend that
these are not used in your FindMe IDs.
Principal The address or alias of the user's first After the account has been created any non-principal devices
device principal device. An administrator (or (including any devices added by FindMe users themselves)
address FindMe users themselves) can add can be set as principal devices. This has the effect of
more endpoint addresses after an stopping the user from being able to delete that device. To do
account has been created. this, click Edit principal devices from the Edit FindMe
account page.
If the Starter Pack option key is installed, there is a separate

section for specifying the user's principal devices (see below).
Password The password to be used, along with FindMe users can change their password after they have
the Username, when logging into this logged in. Note that passwords are case sensitive, and that
account. the password fields are not shown if remote authentication is
enabled.
You must confirm any new or modified
password.
FindMe Specifies if the account is for an If the Starter Pack option key is installed all FindMe IDs are
type individual person or a group of people, created as Individual accounts.
and affects how calls are diverted
when endpoints in the user's primary
list are busy.
Individual: calls immediately divert if

any primary endpoint is busy.
Group of people: calls immediately

divert only if all primary endpoints are
busy.
You can control general FindMe behavior, including whether users are allowed to add their own devices, on the
Configuring FindMe, page 245 page.
Principal devices (Starter Pack)
The Principal devices section is used to specify the principal devices that are associated with the FindMe profile and
to enable provisioning for those devices. This section only displays if the Starter Pack option key is installed.
Principal devices are devices assigned to the profile by the system administrator and cannot be deleted by the
FindMe user. Note that users can add other, non-principal, devices to their FindMe profiles.
To assign a principal device, select On for the relevant device type. The page will then display the URI that will be
assigned for that user and device type. You can assign as many devices as required.
The device URI is based on a combination of the Username, FindMe ID and device type. It takes the format
<username>.<device type>@<domain portion of FindMe ID>.
For example, if the Username is Alice.Smith and the FindMe ID is [email protected], then the URI for an E20 device
would be [email protected].
Each selected device is automatically provisioned (with bandwidth limits and phone book information, for
example) when that device registers to the VCS.
You can specify an additional principal device by setting Other device to On and then specifying the required
URI of the device. If required, you can add further non-principal devices by clicking Edit user from the Edit
FindMe account page.
266
Note that the VCS only sends provisioning information to the pre-configured device types (Jabber Video, E20 and so
on). Other principal devices added by the administrator or any other devices added by the FindMe user are not
provisioned by the VCS.
If your system's authentication policy is configured to check credentials, then authentication credentials for the
provisioned devices must be set up in the relevant credential store (typically the local database). The credential name
must be the same as account username and the credential password must be the same as the password configured
on the provisioned devices. See About Device Authentication, page 108 for more information.
Note: all device address URIs are converted to lower case.
Configuring a FindMe Account's Principal Devices

The Edit principal devices page (Users > FindMe accounts, click View/Edit or the username to open the Edit
FindMe account page, and then click Edit principal devices) is used to configure which of the user's devices are
their principal devices associated with their FindMe ID.
Users are not allowed to delete or change the address of their principal devices; they can only change the Device
name. This is to stop users from unintentionally changing their basic FindMe configuration. Principal devices are also
used by the VCS to decide which FindMe name to display as a Caller ID if the same device address is associated with
more than one account.
The page lists all of the devices currently associated with the selected user. The Principal device column indicates
each device's current status as a principal device or not.
To set devices as a principal device, select the box next to the required devices and click Set as principal
device.
To set devices so they are no longer principal devices, select the required devices and click Unset as
principal device.
Note that only an administrator (and not users themselves) can configure which of a user's devices are their principal
devices.
Active FindMe Sessions

The Active FindMe sessions page (Users > Active FindMe sessions) lists all FindMe accounts that are currently
logged in to this VCS.
It displays details of their session including their login time, IP address and port, and when they last accessed this
VCS.
You can terminate active web sessions by selecting the required sessions and clicking Terminate session.
You may see many sessions listed on this page if a zero Session time out value is configured. This typically occurs if a
user ends their session by closing down their browser without first logging out of the VCS.
Resetting Forgotten Passwords

You can reset any account password by logging in to the VCS as the default admin account or as any other
administrator account that has read-write access. If this is not possible you can reset the admin or root password via
the console.
Changing an Administrator Account Password via GUI

You can change the password for the default administrator account and for additional local administrator accounts.
267
Go to Users >Administrator accounts. Under Actions for the relevant administrator account, click Change
password.
A new page is displayed, where you can change the password for the selected administrator. Enter the new
password and confirm it. You must also enter the password for the administrator account with which you are
currently logged in to authorize the password change.
Resetting Root or Admin Password via Serial Connection

On a hardware VCS, reset the admin or root password as follows:
1. Connect a PC to the VCS using the serial cable as per the instructions in VCS Getting Started Guide. Serial
port / console access is always enabled for one minute following a restart, even if it is normally disabled.
2. Restart the VCS.
3. Log in from the PC with the username pwrec. No password is required.
4. If the administrator account authentication source is set to Remote, you are given the option to change the
setting to Both; this will allow local administrator accounts to access the system.
5. Select the account (root or admin) whose password you want to change.
6. You will be prompted for a new password.
The pwrec account is only active for one minute following a restart. After that time you will have to restart the system
again to change the password.
Resetting Root or Admin Password via vSphere

If you have forgotten the password for either an administrator account or the root account and you are using a VM
(VirtualMachine) VCS, you can reset it using the following procedure:
1. Open the vSphere client.

2. Click on the link Launch Console.
2. Reboot the VCS.
3. In the vSphere console log in with the username pwrec. No password is required.
4. When prompted, select the account (root or the username of the administrator account) whose password you
want to change.
5. You will be prompted for a new password.
The pwrec account is only active for one minute following a reboot. After that time you will have to reboot the system
again to reset the password.
Resetting FindMe Account Passwords

To change a password on behalf of a FindMe user without knowing their existing password (for example, when a user
forgets their password):
1. Go to the Edit FindMe account page (Users > FindMe accounts, then click View/Edit or the username) for the
account whose password you want to reset.
2. Enter the new password to be used when logging into this account into the New password and Confirm
password fields and click Save.
This procedure only applies if local FindMe account authentication is enabled. If remote authentication is enabled,
passwords are managed through your remote directory server instead.
268
Using the Root Account

The VCS provides a root account which can be used to log in to the VCS operating system. This account has a
username of root (all lower case) and a default password of TANDBERG (all upper case). For security reasons you
must change the password as soon as possible. An alarm is displayed on the web interface and the CLI if the root
account has the default password set.
Note: the root account may allow access to sensitive information and it should not be used in normal operation, and
in particular system configuration should not be conducted using this account. Use the admin account instead.
Changing the Root Account Password

To change the password for the root account:
1. Log in to the VCS as root using the existing password. By default you can only do this using a serial
connection or SSH.
2. Type the command passwd.
You will be asked for the new password.
3. Enter the new password and when prompted, retype the password.
4. Type exit to log out of the root account.
Accessing the Root Account Over SSH

The root account can be accessed over a serial connection or SSH only.
To enable and disable access to the root account using SSH:
1. Log in to the VCS as root.

2. Type one of the following commands:
rootaccess --ssh on to enable access using SSH
rootaccess --ssh off to disable access using SSH
If you have disabled SSH access while logged in using SSH, your current session will remain active until you log out,
but all future SSH access will be denied.
Managing SSOtokens
Go to Users >SSOtoken holders to view the list of users who currently hold SSOtokens. This page can help you
troubleshoot issues related to single sign-on for a particular user.
You can also use this page to Purge tokens from all holders. This option is probably disruptive for your users so make
sure you need it before you proceed. You may need it, for example, if you know your security is compromised, or if you
are upgrading internal or edge infrastructure.
To manage the tokens of a particular user:
1. [Optional] Filter by a substring of the username to return a smaller list.

You may need this if there are many usernames in the list, because a long list spans multiple pages of up to
200 usernames each.
2. Click a username to see the detail of the tokens held by that user.
The SSOtokens for user <Username> page appears, listing details of the tokens issued to that user. The
details include the token issuer and expiry.
269
3. [Optional] Click Delete these tokens if you want the user's identity to be confirmed before they continue to
access the UCservices.
The next time the user's client attempts to access UCservices via this VCS Control, the client will be
redirected to the IdP with a new, signed request. The user may need to reauthenticate at the IdP,so that it
can assert their identity to the VCS Control. The user can then be issued with new tokens where authorized.
270
271
Maintenance
This section describes the pages that appear under the Configuration > Maintenance menu of the VCS web
interface.
Enabling SSH access 272

Enabling Maintenance Mode 273
About Upgrading Software Components 273
Configuring Logging 276
Managing Option Keys 280
About Security Certificates 282
Advanced Security 292
Configuring Language Settings 295
Backing Up and Restoring VCS Data 296
Diagnostics Tools 298
Incident Reporting 300
Checking the Effect of a Pattern 303
Locating an Alias 303
Port Usage 304
Network Utilities 305
Restarting, Rebooting and Shutting Down 308
Developer Resources 309
Enabling SSH access

You may want to enable SSHaccess to the VCS so that you can access it securely without requiring password-based
login. One common reason for this is to improve the efficiency of monitoring and logging. You will need to repeat this
procedure on each VCS that you want to access in this way.
Caution:You will use root access to authorize your public key. Take care not to increase your security exposure or
cause any unsupported configuration. We strongly discourage using root.
1. Use SSH to log in as root

2. Enter mkdir /tandberg/.ssh to create .ssh directory if it is not already present
3. Copy your public key to /tandberg/.ssh
4. Append your public key to the authorized_keys file with cat /tandberg/.ssh/id_rsa.pub >>
/tandberg/.ssh/authorized_keys
where id_rsa.pub is substituted with the name of your public key. Do not place your key anywhere else
because the key could be lost on upgrade (authorized_keys file does persist)
272
5. Log off and test SSHaccess using your own key

If you cannot access the VCS with your key, you may need to connect as root and restart the SSHdaemon
with /etc/init.d/sshd restart
Enabling Maintenance Mode

Maintenance mode is typically used when you need to upgrade or take out of service a VCS peer that is part of a
cluster. It allows the other cluster peers to continue to operate normally while the peer that is in maintenance mode is
upgraded or serviced.
Putting a peer into maintenance mode provides a controlled method of stopping any further registrations or calls from
being managed by that peer:
Standard VCS sessions:

New calls and registrations will be handled by another peer in the cluster.
Existing registrations are allowed to expire and they then should re-register to another peer (see VCS
Cluster Creation and Maintenance Deployment Guide for more information about endpoint configuration
and setting up DNSSRV records).
Existing calls will continue until the call is terminated. If necessary, you can manually remove any calls on
this peer that do not clear automatically by going to Status > Calls, selecting the check box next to the calls
you want to terminate and clicking Disconnect (note that SIP calls may not disconnect immediately).
Unified CM mobile and remote access sessions:
Any existing calls passing through that VCS will be dropped.
Jabber clients will failover automatically and re-register through another peer in the cluster.
Clients running TC software will not failover automatically will have to be restarted.
To maintain capacity, we recommend that you only enable maintenance mode on one peer at a time.
To enable maintenance mode:
1. Log in the relevant peer.

2. Go to the Maintenance mode page (Maintenance > Maintenance mode).
3. Set Maintenance mode to On.
4. Click Save and click OK on the confirmation dialog.
Note that:
An alarm is raised while the peer is in maintenance mode.

You can monitor the Resource usage page (Status > System > Resource usage) to check how many
registrations and calls are currently being handled by that peer.
Maintenance mode is automatically disabled if the peer is restarted.
About Upgrading Software Components

You can install new releases of the VCS software components on your existing hardware. Component upgrades can
be performed in one of two ways:
Using the web interface - this is the recommended process.

Using secure copy (SCP/PSCP).
This guide describes how both of these methods are used to perform upgrades. You can also upgrade the System
platform component using Cisco TMS (see the Cisco TMS documentation for more information).
273
We recommended that you upgrade VCS components while the system is inactive.
If you are upgrading a cluster:
If you are currently running non-clustered VCS X5.1, X5.1.1 or X5.2, you must first upgrade to X6.1, then
upgrade from X6.1 to X8.n.
If you are currently running non-clustered VCS X5.0 or earlier, you must first upgrade to X5.2, then upgrade
from X5.2 to X6.1, and then upgrade from X6.1 to X8.n.
VCS software components
All existing installed components are listed on the Upgrade page (Maintenance > Upgrade), showing their current
version and associated release key where appropriate.
The main component is the System platform, and when upgraded this will typically include automatic upgrades of
some or all of the other components. However, you can independently upgrade the other components if required to
do so. The upgrade process ensures that compatibility is maintained across all components.
Upgrade prerequisites
The upgrade requires you to have:
a valid Release key, if you are upgrading to the next major release of the System platform, for example from
X7.2 to X8.1; it is not required for dot releases, for example X8.1 to X8.2
a software image file for the component you want to upgrade, and it is stored in a network location that is
locally accessible from your client computer; use the standard .tar.gz software image file when upgrading a
virtual machine (the .ova file is only required for the initial install of the VCS software on VMware)
release notes for the software version you are upgrading to additional manual steps may be required
Contact your Cisco representative for more information on how to obtain these.
Backing up before upgrading
You should backup your system configuration before upgrading. Click System backup to go to the Backup and
restore page.
Upgrading and option keys
All existing option keys are retained through the upgrade from one version of the System platform to the next,
including upgrades to the next major release. However, you are recommended to take note of your existing option
keys before performing the upgrade.
New features may also become available with each major release of the System platform component, and you may
need to install new option keys to take advantage of these new features. Contact your Cisco representative for more
information on all the options available for the latest release of VCS software.
Installing and rebooting
Upgrading the System platform component is a two-stage process. First, the new software image is uploaded onto
the VCS. At the same time, the current configuration of the system is recorded, so that this can be restored after the
upgrade. During this initial stage the system will continue running on its existing software version, and all normal
system processes will continue.
The second part of the upgrade involves rebooting the system. It is only during the reboot that the VCS installs the
new software version and restores the previous configuration. Rebooting causes all current calls to terminate, and all
current registrations to be ended.
This means that you can upload the new software at any time, and then wait until a convenient moment (for example,
when no calls are taking place) to switch to the new version by rebooting the system.
Note: Any configuration changes you make between the software upload and the reboot will be lost when the system
restarts using the new software version.
274
The upgrade of components other than the System platform does not involve a system reboot, however the services
provided by that component will be temporarily stopped while the upgrade process completes.
Upgrading VCS Software

The Upgrade page (Maintenance > Upgrade) is used to install new (or to downgrade) versions of VCS software
components.
To upgrade a component using the web interface:
1. Review the relevant release notes to see if any special steps are required either before or after installing the
software image file.
2. Go to the Upgrade page (Maintenance > Upgrade).
3. Click Browse and select the software image file for the component you want to upgrade.
The VCS automatically detects which component you are upgrading based upon the selected software image
file.
4. Enter the Release key if required.
5. Click Upgrade.
The VCS will start loading the file. This may take a few minutes.
6. For upgrades to the System platform component, the Upgrade confirmation page is displayed:
a. Check that:
the expected New software version number is displayed
the MD5 hash and SHA1 hash values match the values displayed on the cisco.com page, where you
have downloaded the software image file
b. Click Continue with upgrade.
The System upgrade page opens and displays a progress bar while the software installs.
When the software has installed, a summary of active calls and registrations is displayed. These will be
lost when you reboot the system.
c. Click Reboot system.
Note that if you make any configuration changes between uploading the software and rebooting, those
changes will be lost when the system restarts.
After the reboot is complete you are taken to the Login page.
7. For upgrades to other components, the software is automatically installed. No reboot is required.
The upgrade is now complete. The Overview and Upgrade pages now show the upgraded software component
version numbers.
Note that some components may require option keys to enable them; this is done through the Option keys page
(Maintenance > Option keys).
Downgrading
If you need to downgrade to an earlier release of the System platform, configuration changes, including changes
made to FindMe or Provisioning, will be lost. When the downgrade has completed you will have to restore a backup of
the system configuration that was made against the release you have just reinstalled. Other manual steps may be
required you must review the release notes for the version you are downgrading from.
To downgrade a component to an older release you should follow the same instructions as above for
upgrading, but select the appropriate software image file for the software version you want to downgrade to.
As with upgrading, you are recommended to backup your system configuration before downgrading.
Upgrading Using Secure Copy (SCP/PSCP)

To upgrade using a secure copy program such as SCP or PSCP (part of the PuTTY free package) you need to transfer
two files to the VCS:
275
A text file containing just the 16-character Release Key (required for the System platform component only).
Ensure there is no extraneous white space in this file.
The file containing the software image.
To transfer these files:
1. If you are upgrading the System platform component, upload the Release Key file using SCP/PSCP to the
/tmp/ folder on the system. The target name must be release-key, for example:
scp release-key [email protected]:/tmp/release-key
Enter the root password when prompted.
The Release Key file must be uploaded before the image file.
2. Upload the software image using SCP/PSCP.
For the System platform component:
Upload to the /tmp folder on the system. The target name must be /tmp/tandberg-image.tar.gz, for
example: scp s42700x8_1_0.tar.gz [email protected]:/tmp/tandberg-image.tar.gz
For other components:
Upload to the /tmp/pkgs/new/ folder on the system, preserving the file name and extension, for example:
scp [email protected]:/tmp/pkgs/new/vcs-lang-es-es_8.1_amd64.tlp
3. Enter the root password when prompted.
The software installation begins automatically. Wait until the software has installed completely. This should
not take more than five minutes.
4. If you have upgraded the System platform component, log in to the VCS, either using the web interface or
CLI, and reboot the VCS. After about five minutes the system will be ready to use.
Note: if you make any further configuration changes before rebooting, those changes will be lost when the system
restarts, so you are recommended to reboot your system immediately.
Configuring Logging
The VCS provides syslogging features for troubleshooting and auditing purposes.
The Event Log is a rotating local log that records information about such things as calls, registrations, and messages
sent and received.
The VCS's logging options are configured on the Logging page (Maintenance > Logging) where you can:
specify the Local event log verbosity to change the depth of event information recorded locally
toggle Media statistics logging
toggle Call Detail Records
define one or more remote syslog server addresses
filter the events sent to each remote syslog server by severity
toggle System Metrics Collection
Changing Event Log Verbosity

Control the local log verbosity by setting the Local event log verbosity between 1 and 4.
All events have an associated level in the range 1-4, with Level 1 Events considered the most important. The table
below gives an overview of the levels assigned to different events.
276
Level Assigned events
1 High-level events such as registration requests and call attempts. Easily human readable. For example:
call attempt/connected/disconnected
registration attempt/accepted/rejected
2 All Level 1 events, plus:
logs of protocol messages sent and received (SIP, H.323, LDAP and so on) excluding noisy
messages such as H.460.18 keepalives and H.245 video fast-updates
3 All Level 1 and Level 2 events, plus:
protocol keepalives
call-related SIP signaling messages
4 The most verbose level: all Level 1, Level 2 and Level 3 events, plus:
network level SIP messages
See the Events and levels section for a complete list of all events that are logged by the VCS, and the level at which
they are logged.
Notes:
Events are always logged locally (to the Event Log) regardless of whether or not remote logging is enabled.
Logging at level 3 or level 4 is not recommended for normal operation, because such detailed logging may
cause the 2GB log to rotate too quickly. You may need to record this level of detail while troubleshooting.
Changes to the log level affect both the Event Log that you can view via the web interface, and the
information that is copied to any remote log server.
Changes to the log level are not retrospective they only affect what is logged after you change the level.
The VCS uses the following facilities for local logging. The software components / logs that map to the (local)
facilities are emphasised:
0 (kern)
3 (daemon)
16 (local0) Administrator
17 (local1) Config
18 (local2) Mediastats
19 (local3) Apache error
20 (local4) etc/opt/apache2
21 (local5) Developer
22 (local6) Network
Logging Media Statistics

When you switch Media statistics to On, the VCS starts logging media statistics to the local hard disk, in
/mnt/harddisk/log. Up to 200 files of 10MB each are stored, with the oldest being deleted when the 200th is full.
Media statistics messages are also published as syslog messages. While the Media statistics logging option is on, the
VCS publishes statistics using facility 18 (local2) to all remote syslog servers you have configured.
277
Some examples of the media statistics are packets forwarded, packets lost, jitter, media type, codec, and actual
bitrate.
Note:The message severity is Informational but media statistics messages are always published, irrespective of the
severity filters.
Call Detail Records (CDRs)

The system can capture CDRs if you enable the service (which is off by default), and can publish them as syslog
messages if you are using remote logging.
If you select Service only the system keeps the CDRs for 7 days, and these CDRs can only be read via the
Representational State Transfer (REST)API to the VCS. If you select Service and logging, the local data is exposed in
the Event Log, and the CDRs are also sent as INFOmessages to your syslog host.
How to Configure CDRs

To configure CDRs on VCS:
1. Go to Maintenance > Logging.

2. In the Logging Options section, set the Call Detail Records field following the below guide.
CDR Mode Description
Off CDRs are not logged locally (default).
Service Only CDRs are stored locally for 7 days and then deleted. The records are not
accessible via the web GUI.
Services and Logging CDRs are stored locally for 7 days and then deleted. The records are accessible
from the local event log and the external syslog server if external logging has
been enabled.
For more information:

See the Cisco VCS Serviceability Guide on the VCS Maintain and Operate Guides page.
Publishing Logs to Remote Syslog Servers

Syslog is a convenient way to aggregate log messages from multiple systems to a single location. This is particularly
recommended for peers in a cluster.
You can configure the VCS to publish log messages to up to 4 remote syslog servers.
The syslog servers must support one of the following standard protocols:
BSD (as defined in RFC 3164)
IETF (as defined in RFC 5424)
Configuring Remote Syslog Servers
1. Go to Maintenance >Logging, and enter the IP addresses or Fully Qualified Domain Names (FQDNs) of the
Remote syslog servers to which this system will send log messages.
2. Click on the Options button for each server.
3. Specify the Transport protocol and Port you wish to use. The default is UDP over port 514. If you choose to
use TLS, you will see the option to enable Certificate Revocation List (CRL) checking for the syslog server.
4. In the Message Format field, select the writing format for remote syslog messages. The default is Legacy
BSD.
278
5. Use the Filter by Severity option to select how much detail to send. The VCS sends messages of the selected
severity and all of the more severe messages.
6. Use the Filter by Keywords option if you only want to send messages with certain keywords.
7. Click Save.
Notes:
The Filter by Keywords option is applied to messages already filtered by severity.

You can use up to five keywords, which includes groups of words (for example 'login successful'), separated
by commas.
You can use a maximum of 256 characters in the keyword search.
We recommend that you search for the most relevant keywords first to avoid any impact on system
performance. This ensures the system pushes the relevant log messages to the syslog server at the earliest
opportunity.
What are the Typical Values used for my Syslog Server?
The following table should help you select the format that best matches your logging server(s) and network
configuration and shows the typical values used.
Table 9 Syslog message formats
Message format Transport protocol Suggested port RFC
Legacy BSDformat UDP 514 BSDformat. See RFC 3164
IETF syslog format UDP 514 IETFformat. See RFC 5424
IETFsyslog using TLSconnection TLS 6514 IETFformat. See RFC 5424
279
Notes:
The UDPprotocol is stateless. If reliability of syslog messages is very important in your environment, you
should use a different transport protocol.
If there is a firewall between the VCS and the syslog server, you must open the appropriate port to allow the
messages through.
If you select TLStransport, the VCS must trust the syslog server's certificate. Upload the syslog server's
CAcertificate to the local trust store if necessary.
CRL checking when using TLS is disabled by default. To enable CRL, set CRLchecking to On and ensure that
relevant certificate revocation lists (CRLs) are loaded.
See About Security Certificates, page 282 for more information.
The remote server cannot be another VCS.
A VCS cannot act as a remote log server for other systems.
The VCS uses the following facilities for remote logging. The software components / logs that map to the
(local) facilities are emphasised:
0 (kern)
3 (daemon)
16 (local0) Administrator
17 (local1) Config
18 (local2) Mediastats
19 (local3) Apache error
20 (local4) etc/opt/apache2
21 (local5) Developer
22 (local6) Network
Configure System Metrics Collection on VCS

In the following procedure you'll use the web interface to configure the VCS to collect statistics and publish them to a
specified server.
1. Log on to the VCS and go to Maintenance >Logging.

2. Toggle System Metrics Collection to On.
3. Enter the Collection server address.
You can use IPaddress, hostname or FQDN to identify the remote server.
4. Change the Collection Interval and Collection server port if necessary.
You may need to change the port if the collection server is listening on a different port to the default (25826).
You may need to change the collection interval if your policy requires finer metrics than the default interval
(60s).
5. Click Save.
Managing Option Keys

Options are used to add additional features to the VCS. Option keys can either be valid for a fixed time period or have
an unlimited duration. Your VCS may have been shipped with one or more optional features pre-installed. To
purchase further options, contact your Cisco representative.
The Option keys page (Maintenance > Option keys) lists all the existing options currently installed on the VCS, and
allows you to add new options.
280
The System information section summarizes the existing features installed on the VCS and displays the Validity
period of each installed key. The options that you may see here include:
Traversal Server: enables the VCS to work as a firewall traversal server.

H.323 to SIP Interworking gateway: enables H.323 calls to be translated to SIP and vice versa.
FindMe: enables FindMe functionality.
Advanced Networking: enables the LAN 2 port on a VCS, and enables static NAT functionality on a VCS
Expressway.
Device Provisioning: enables the VCS's Provisioning Server. This allows VCS to provision endpoints with
configuration information on request and to supply endpoints with phone book information. (Endpoints
including Jabber Video, E20, and the EX and MX Series can request to be provisioned.) Note that the VCS
must use Cisco TMS to obtain configuration and phone book information for distribution.
Starter Pack: allows the VCS to offer basic device provisioning without the need for Cisco TMS (see
Provisioning (Starter Pack)).
Traversal calls: determines the number of traversal calls allowed on the VCS (or VCS cluster) at any one time.
Note that traversal calls that are passing through the VCS from one neighbor to another but where neither
endpoint in the call is locally registered will still be counted as one traversal call. See the Call Types and
Licensing, page 381 section for more information.
Non-traversal calls: determines the number of non-traversal calls allowed on the VCS (or VCS cluster) at any
one time. Note that non-traversal calls that are passing through the VCS from one neighbor to another but
where neither endpoint in the call is locally registered may or may not require a non-traversal call license,
depending on the Call signaling optimization setting. Note that a non-traversal call on a VCS Expressway will
consume a traversal license if there are no non-traversal call licenses available.
Registrations: the number of concurrent registrations allowed on the VCS. An endpoint can register with more
than one alias and this will be considered to be a single registration. However, an endpoint that supports both
SIP and H.323 and registers using both protocols will count as two registrations. H.323 systems such as
gateways, MCUs and Content Servers can also register with the VCS, and these will each count as one
registration.
TURN Relays: the number of concurrent TURN relays that can be allocated by this VCS (or VCS cluster). See
About ICE and TURN Services, page 47 for more information.
Encryption: indicates that AES (and DES) encryption is supported by this software build.
Advanced account security: enables advanced security features and restrictions for high-security
installations.
Microsoft Interoperability: enables encrypted calls to and from Microsoft Lync 2010 Server (for both native
SIP calls and calls interworked from H.323). It is also required by the Lync B2BUA when establishing ICE calls
to Lync 2010 clients. It is required for all types of communication with Lync 2013.
See License Usage Within a Cluster, page 162 for more information about how traversal call, non-traversal call and
TURNrelay option key licenses are shared across all peers in the cluster.
Adding option keys using the web interface
To add an option key:
1. In the Add option key field, enter the key that has been provided to you for the option you want to add.
2. Click Add option.
Some option keys require that the VCS is restarted before the option key will take effect. In such cases you will
receive an alarm on the web interface, which will remain in place as a reminder until the system has been restarted.
However, you can continue to use and configure the VCS in the meantime.
Adding option keys using the CLI
To return the indexes of all the option keys that are already installed on your system:
xStatus Options
To add a new option key to your system:
281
xConfiguration Option [1..64] Key
Note: when using the CLI to add an extra option key, you can use any unused option index. If you chose an existing
option index, that option will be overwritten and the extra functionality provided by that option key will no longer exist.
To see which indexes are currently in use, type xConfiguration option.
About Security Certificates

For extra security, you may want to have the VCS communicate with other systems (such as LDAP servers, neighbor
VCSs, or clients such as SIP endpoints and web browsers) using TLS encryption.
For this to work successfully in a connection between a client and server:
The server must have a certificate installed that verifies its identity. This certificate must be signed by a
Certificate Authority (CA).
The client must trust the CA that signed the certificate used by the server.
The VCS allows you to install appropriate files so that it can act as either a client or a server in connections using
TLS. The VCS can also authenticate client connections (typically from a web browser) over HTTPS. You can also
upload certificate revocation lists (CRLs) for the CAs used to verify LDAP server and HTTPS client certificates.
The VCS can generate server certificate signing requests (CSRs). This removes the need to use an external
mechanism to generate and obtain certificate requests.
For secure communications (HTTPS and SIP/TLS) we recommend that you replace the VCS default certificate with a
certificate generated by a trusted certificate authority.
Note that in connections:
to an endpoint, the VCS acts as the TLS server

to an LDAP server , the VCS is a client
between two VCS systems, either VCS may be the client with the other VCS being the TLS server
via HTTPS, the web browser is the client and the VCS is the server
TLS can be difficult to configure. For example, when using it with an LDAP server we recommend that you confirm
that your system is working correctly before you attempt to secure the connection with TLS. You are also
recommended to use a third party LDAP browser to verify that your LDAP server is correctly configured to use TLS.
Note: be careful not to allow your CA certificates or CRLs to expire as this may cause certificates signed by those
CAs to be rejected.
Certificate and CRL files can only be managed via the web interface. They cannot be installed using the CLI.
See Managing the Trusted CA Certificate List, page 282 and Managing the VCS's Server Certificate, page 283 for
instructions about how to install certificates. For further information, see Certificate Creation and Use with VCS
Deployment Guide.
Managing the Trusted CA Certificate List

The Trusted CA certificate page (Maintenance > Security certificates > Trusted CA certificate) allows you to
manage the list of certificates for the Certificate Authorities (CAs) trusted by this VCS. When a TLS connection to
VCS mandates certificate verification, the certificate presented to the VCS must be signed by a trusted CA in this list
and there must be a full chain of trust (intermediate CAs) to the root CA.
To upload a new file containing one or more CA certificates, Browse to the required PEM file and click
Append CA certificate. This will append any new certificates to the existing list of CA certificates. If you are
replacing existing certificates for a particular issuer and subject, you have to manually delete the previous
certificates.
To replace all of the currently uploaded CA certificates with the system's original list of trusted CA certificates,
click Reset to default CA certificate.
282
To view the entire list of currently uploaded trusted CA certificates, click Show all (decoded) to view it in a
human-readable form, or click Show all (PEM file) to view the file in its raw format.
To view an individual trusted CA certificate, click on View (decoded) in the row for the specific CA certificate.
To delete one or more CA certificates, tick the box(es) next to the relevant CA certificate(s) and click Delete.
Note: if you have enabled certificate revocation list (CRL) checking for TLS encrypted connections to an LDAP server
(for account authentication), you must add the PEM encoded CRL data to your trusted CA certificate file.
Managing the VCS's Server Certificate

The Server certificate page (Maintenance > Security certificates > Server certificate) is used to manage the VCS's
server certificate. This certificate is used to identify the VCS when it communicates with client systemsusing TLS
encryption, and with web browsers over HTTPS. You can:
view details about the currently loaded certificate

generate a certificate signing request
upload a new server certificate
Note:We highly recommend using certificates based on RSAkeys. Other types of certificate, such as those
based on DSA keys, are not tested and may not work with the VCS in all scenarios.
Viewing the currently uploaded certificate
The Server certificate data section shows information about the server certificate currently loaded on the VCS.
To view the currently uploaded server certificate file, click Show (decoded) to view it in a human-readable
form, or click Show (PEM file) to view the file in its raw format.
Note that if a certificate contains SRV-ID or XMPP-ID formatted entries, when that certificate is viewed those
entries will show as '<unsupported>'. That does not mean the certificate is invalid, but that the openssl code
does not know how to display those identifiers.
To replace the currently uploaded server certificate with the VCS's original certificate, click Reset to default
server certificate.
Note: Do not allow your server certificate to expire as this may cause other external systems to reject your certificate
and prevent the VCS from being able to connect to those systems.
Generating a certificate signing request (CSR)
The VCS can generate server certificate signing requests. This removes the need to use an external mechanism to
generate and obtain certificate requests.
To generate a CSR:
1. Go to Maintenance > Security certificates > Server certificate.

2. Click Generate CSR to go to the Generate CSR page.
3. Enter the required properties for the certificate.
See Server Certificates and Clustered Systems, page 284 if your VCS is part of a cluster.
See Server Certificate Requirements for Unified Communications, page 54 if this VCS is part of a Unified
Communications solution.
The certificate request includes automatically the public key that will be used in the certificate, and the
client and server authentication Enhanced Key Usage (EKU) extension.
4. Click Generate CSR. The system will produce a signing request and an associated private key.
The private key is stored securely on the VCS and cannot be viewed or downloaded. You must never disclose
your private key, not even to the certificate authority.
283
5. You are returned to the Server certificate page. From here you can:
Download the request to your local file system so that it can be sent to a certificate authority. You are
prompted to save the file (the exact wording depends on your browser).
View the current request (click Show (decoded) to view it in a human-readable form, or click Show (PEM
file) to view the file in its raw format).
Note:
Only one signing request can be in progress at any one time. This is because the VCS has to keep track of the
private key file associated with the current request. To discard the current request and start a new request,
click Discard CSR.
From version X8.5.1 the user interface provides an option to set the Digest algorithm. The default is set to
SHA-256, with options to change to SHA-1, SHA-384, or SHA-512.
The certificate signing request storage location changed in X8.
When you generate a CSR in X7, the application puts csr.pem and privkey_csr.pem into
/tandberg/persistent/certs.
When you generate a CSRin X8, the application puts csr.pem and privkey.pem into
/tandberg/persistent/certs/generated_csr.
If you want to upgrade from X7 and have an unsubmitted CSR, then we recommend discarding the CSRbefore
upgrade, and then regenerating the CSR after upgrade.
Uploading a new server certificate
When the signed server certificate is received back from the certificate authority it must be uploaded to the VCS.
The Upload new certificate section is used to replace the VCS's current server certificate with a new certificate.
To upload a server certificate:
1. Go to Maintenance > Security certificates > Server certificate.

2. Use the Browse button in the Upload new certificate section to select and upload the server certificate PEM
file.
3. If you used an external system to generate the Certificate Signing Request(CSR) you must also upload the
server private key PEM file that was used to encrypt the server certificate. (The private key file will have been
automatically generated and stored earlier if the VCS was used to produce the CSR for this server certificate.)
The server private key PEMfile must not be password protected.
You cannot upload a server private key if a certificate signing request is in progress.
4. Click Upload server certificate data.
Server Certificates and Clustered Systems

When a CSR is generated, a single request and private key combination is generated for that peer only.
If you have a cluster of VCSs, you must generate a separate signing request on each peer. Those requests must then
be sent to the certificate authority and the returned server certificates uploaded to each relevant peer.
You must ensure that the correct server certificate is uploaded to the appropriate peer, otherwise the stored private
key on each peer will not correspond to the uploaded certificate.
Server Certificates and Unified Communications

VCS Control server certificate requirements
The VCS Control server certificate needs to include the following elements in its list of subject alternate names:
284
Unified CM phone security profile names: the names of the Phone Security Profiles in Unified CM that are
configured for encrypted TLS and are used for devices requiring remote access. Use the FQDNformat and
separate multiple entries with commas.
Having the secure phone profiles as alternative names means that Unified CM can communicate via TLS with
the VCS Control when it is forwarding messages from devices that use those profiles.
IM and Presence chat node aliases (federated group chat): the Chat Node Aliases (e.g.
chatroom1.example.com) that are configured on the IM and Presence servers. These are required only for
Unified Communications XMPP federation deployments that intend to support group chat over TLS with
federated contacts.
The VCS Control automatically includes the chat node aliases in the CSR, providing it has discovered a set of
IM&P servers.
We recommend that you use DNSformat for the chat node aliases when generating the CSR. You must
include the same chat node aliases in the VCS Expressway server certificate's alternative names.
Figure 11 Entering subject alternative names for security profiles and chat node aliases on the VCS
Control's CSRgenerator
VCS Expressway server certificate requirements

The VCS Expressway server certificate needs to include the following elements in its list of subject alternate names:
Unified CM registrations domains: all of the domains which are configured on the VCS Control for Unified
CM registrations. They are required for secure communications between endpoint devices and VCS
Expressway.
multiple domains. You may select CollabEdgeDNS format instead, which simply adds the prefix collab-edge.
to the domain that you enter. This format is recommended if you do not want to include your top level domain
as a SAN (see example in following screenshot).
XMPP federation domains: the domains used for point-to-point XMPP federation. These are configured on
the IM&P servers and should also be configured on the VCS Control as domains for XMPP federation.
IM and Presence chat node aliases (federated group chat): the same set of Chat Node Aliases as entered
on the VCS Control's certificate. They are only required for voice and presence deployments which will
support group chat over TLS with federated contacts.
Note that you can copy the list of chat node aliases from the equivalent Generate CSR page on the VCS
Control.
285
Figure 12 Entering subject alternative names for Unified CMregistration domains, XMPPfederation
domains, and chat node aliases, on the VCS Expressway's CSRgenerator
Managing Certificate Revocation Lists (CRLs)

Certificate revocation list (CRL) files are used by the VCS to validate certificates presented by client browsers and
external systems that communicate with the VCS over TLS/HTTPS. A CRL identifies those certificates that have been
revoked and can no longer be used to communicate with the VCS.
We recommend that you upload CRL data for the CAs that sign TLS/HTTPS client and server certificates. When
enabled, CRL checking is applied for every CA in the chain of trust.
Certificate Revocation Sources

The VCS can obtain certificate revocation information from multiple sources:
automatic downloads of CRL data from CRL distribution points

through OCSP (Online Certificate Status Protocol) responder URIs in the certificate to be checked (SIP TLS
only)
manual upload of CRL data
CRL data embedded within the VCS's Trusted CA certificate file
The following limitations and usage guidelines apply:
when establishing SIP TLS connections, the CRL data sources are subject to the Certificate revocation
checking settings on the SIP configuration page
automatically downloaded CRL files override any manually loaded CRL files (except for when verifying
SIPTLS connections, when both manually uploaded or automatically downloaded CRL data may be used)
when validating certificates presented by external policy servers, the VCS uses manually loaded CRLs only
when validating TLS connections with an LDAP server for remote login account authentication, the VCS uses
CRL data within the Trusted CA certificate only
Automatic CRL Updates
We recommend that you configure the VCS to perform automatic CRL updates. This ensures that the latest CRLs are
available for certificate validation.
To configure the VCS to use automatic CRL updates:
1. Go to Maintenance > Security certificates > CRL management.

2. Set Automatic CRL updates to Enabled.
286
3. Enter the set of HTTP(S) distribution points from where the VCS can obtain CRL files.
Note:
you must specify each distribution point on a new line

only HTTP(S) distribution points are supported; if HTTPS is used, the distribution point server itself must
have a valid certificate
PEM and DER encoded CRL files are supported
the distribution point may point directly to a CRL file or to ZIP and GZIP archives containing multiple CRL
files
the file extensions in the URL or on any files unpacked from a downloaded archive do not matter as the VCS
will determine the underlying file type for itself; however, typical URLs could be in the format:
http://example.com/crl.pem
http://example.com/crl.der
http://example.com/ca.crl
https://example.com/allcrls.zip
https://example.com/allcrls.gz
4. Enter the Daily update time (in UTC). This is the approximate time of day when the VCS will attempt to update
its CRLs from the distribution points.
5. Click Save.
Manual CRL Updates
You can upload CRL files manually to the VCS. Certificates presented by external policy servers can only be validated
against manually loaded CRLs.
To upload a CRL file:
1. Go to Maintenance > Security certificates > CRL management.

2. Click Browse and select the required file from your file system. It must be in PEM encoded format.
3. Click Upload CRL file.
This uploads the selected file and replaces any previously uploaded CRL file.
Click Remove revocation list if you want to remove the manually uploaded file from the VCS.
If a certificate authority's CRL expires, all certificates issued by that CA will be treated as revoked.
Online Certificate Status Protocol (OCSP)
The VCS can establish a connection with an OCSP responder to query the status of a particular certificate.The VCS
determines the OCSP responder to use from the responder URI listed in the certificate being verified. The OCSP
responder sends a status of 'good', 'revoked' or 'unknown' for the certificate.
The benefit of OCSP is that there is no need to download an entire revocation list. OCSPis supported for SIPTLS
connections only. See below for information on how to enable OCSP.
Outbound communication from the VCS Expressway is required for the connection to the OCSPresponder. Check the
port number of the OCSPresponder you are using (typically this is port 80 or 443) and ensure that outbound
communication is allowed to that port from the VCS Expressway.
Configuring Revocation Checking for SIP TLS Connections

You must also configure how certificate revocation checking is managed for SIPTLS connections.
287
1. Go to Configuration > SIP.

2. Scroll down to the Certificate revocation checking section and configure the settings accordingly:
Certificate Controls whether revocation checking is performed for We recommend that revocation
revocation certificates exchanged during SIP TLS connection checking is enabled.
checking establishment.
mode
Use OCSP Controls whether the Online Certificate Status Protocol To use OCSP, the X.509
(OCSP) may be used to perform certificate revocation certificate to be checked must
checking. contain an OCSP responder URI.
Use CRLs Controls whether Certificate Revocation Lists (CRLs) CRLs can be used if the
are used to perform certificate revocation checking. certificate does not support
OCSP.
CRLs can be loaded manually

onto the VCS, downloaded
automatically from preconfigured
URIs (see Managing Certificate
Revocation Lists (CRLs), page
286), or downloaded
automatically from a CRL
distribution point (CDP) URI
contained in the X.509 certificate.
Allow CRL Controls whether the download of CRLs from the CDP
downloads URIs contained in X.509 certificates is allowed.
from CDPs
Fallback Controls the revocation checking behavior if the Treat as not revoked ensures that
behavior revocation status cannot be established, for example if your system continues to operate
the revocation source cannot be contacted. in a normal manner if the
revocation source cannot be
Treat as revoked: treat the certificate as revoked (and contacted, however it does
thus do not allow the TLS connection). potentially mean that revoked
certificates will be accepted.
Treat as not revoked: treat the certificate as not
revoked.
Configuring Certificate-Based Authentication

The Certificate-based authentication configuration page (Maintenance > Security certificates > Certificate-based
authentication configuration) is used to configure how the VCS retrieves authorization credentials (the username)
from a client browser's certificate.
This configuration is required if Client certificate-based security (as defined on the System page) has been set to
Certificate-based authentication. This setting means that the standard login mechanism is no longer available and
that administrators (and FindMe accounts, if accessed via the VCS) can log in only if they present a valid browser
certificate typically provided via a smart card (also referred to as a Common Access Card or CAC) and the
certificate contains appropriate credentials that have a suitable authorization level.
Enabling Certificate-Based Authentication

The recommended procedure for enabling certificate-based authentication is described below:
288
1. Add the VCS's trusted CA and server certificate files (on the Trusted CA certificate and Server certificate
pages, respectively).
2. Configure certificate revocation lists (on the CRL management page).
3. Use the Client certificate testing page to verify that the client certificate you intend to use is valid.
4. Set Client certificate-based security to Certificate validation (on the System administration page).
5. Restart the VCS.
6. Use the Client certificate testing page again to set up the required regex and format patterns to extract the
username credentials from the certificate.
7. Only when you are sure that the correct username is being extracted from the certificate, set Client
certificate-based security to Certificate-based authentication.
Authentication Versus Authorization

When the VCS is operating in certificate-based authentication mode, user authentication is managed by a process
external to the VCS.
When a user attempts to log in to the VCS, the VCS will request a certificate from the client browser. The browser
may then interact with a card reader to obtain the certificate from the smart card (or alternatively the certificate may
already be loaded into the browser). To release the certificate from the card/browser, the user will typically be
requested to authenticate themselves by entering a PIN. If the client certificate received by the VCS is valid (signed
by a trusted certificate authority, in date and not revoked by a CRL) then the user is deemed to be authenticated.
To determine the user's authorization level (read-write, read-only and so on) the VCS must extract the user's
authorization username from the certificate and present it to the relevant local or remote authorization mechanism.
The following diagram shows an example authorization and authentication process. It shows how a certificate is
obtained from a card reader and then validated by the VCS. It then shows how the VCS obtains the user's
authorization level from an Active Directory service.
Note that if the client certificate is not protected (by a PIN or some other mechanism) then unauthenticated access to
the VCS may be possible. This lack of protection may also apply if the certificates are stored in the browser, although
some browsers do allow you to password protect their certificate store.
289
Obtaining the Username from the Certificate

The username is extracted from the client browser's certificate according to the patterns defined in the Regex and
Username format fields on the Certificate-based authentication configuration page:
In the Regex field, use the (?<name>regex) syntax to supply names for capture groups so that matching sub-
patterns can be substituted in the associated Username format field, for example,
/(Subject:.*, CN=(?<Group1>.*))/m.
The regex defined here must conform to PHP regex guidelines.
The Username format field can contain a mixture of fixed text and the capture group names used in the
Regex. Delimit each capture group name with #, for example, prefix#Group1#suffix. Each capture group
name will be replaced with the text obtained from the regular expression processing.
You can use the Client certificate testing page to test the outcome of applying different Regex and Username
format combinations to a certificate.
Testing Client Certificates

The Client certificate testing page (Maintenance > Security certificates > Client certificate testing) is used to
check client certificates before enabling client certificate validation. You can:
Test whether a client certificate is valid when checked against the VCS's current trusted CA list and, if
loaded, the revocation list (see Managing Certificate Revocation Lists (CRLs), page 286).
Test the outcome of applying the regex and template patterns that retrieve a certificate's authorization
credentials (the username).
You can test against:
a certificate on your local file system

the browser's currently loaded certificate
To test if a certificate is valid:
1. Select the Certificate source. You can choose to:

upload a test file from your file system in either PEM or plain text format; if so click Browse to select the
certificate file you want to test
test against the certificate currently loaded into your browser (only available if the system is already
configured to use Certificate validation and a certificate is currently loaded)
2. Ignore the Certificate-based authentication pattern section - this is only relevant if you are extracting
authorization credentials from the certificate.
3. Click Check certificate.
4. The results of the test are shown in the Certificate test results section.
290
To retrieve authorization credentials (username) from the certificate:
1. Select the Certificate source as described above.

2. Configure the Regex and Username format fields as required. Their purpose is to extract a username from the
nominated certificate by supplying a regular expression that will look for an appropriate string pattern within
the certificate. The fields default to the currently configured settings on the Certificate-based authentication
configuration page but you can change them as required.
In the Regex field, use the (?<name>regex) syntax to supply names for capture groups so that matching sub-
patterns can be substituted in the associated Username format field, for example,
/(Subject:.*, CN=(?<Group1>.*))/m.
The regex defined here must conform to PHP regex guidelines.
The Username format field can contain a mixture of fixed text and the capture group names used in the
Regex. Delimit each capture group name with #, for example, prefix#Group1#suffix. Each capture group
name will be replaced with the text obtained from the regular expression processing.
3. Click Check certificate.
The results of the test are shown in the Certificate test results section. The Resulting string item is the
username credential that would be checked against the relevant authorization mechanism to determine that
user's authorization (account access) level.
4. If necessary, you can modify the Regex and Username format fields and repeat the test until the correct
results are produced.
Note that if the Certificate source is an uploaded PEM or plain text file, the selected file is temporarily
uploaded to the VCS when the test is first performed:
if you want to keep testing different Regex and Username format combinations against the same file, you
do not have to reselect the file for every test
if you change the contents of your test file on your file system, or you want to choose a different file, you
must click Browse again and select the new or modified file to upload
5. If you have changed the Regex and Username format fields from their default values and want to use these
values in the VCS's actual configuration (as specified on the Certificate-based authentication configuration
page) then click Make these settings permanent.
Note:
Any uploaded test file is automatically deleted from the VCS at the end of your login session.
The regex is applied to a plain text version of an encoded certificate. The system uses the command openssl
x509 -text -nameopt RFC2253 -noout to extract the plain text certificate from its encoded format.
Testing Secure Traversal

This utility tests whether a secure connection can be made from the VCS Control to the VCS Expressway. A secure
connection is required for a Unified Communications traversal zone, and is optional (recommended) for a normal
traversal zone.
If the secure traversal test fails, the utility raises a warning with appropriate resolution where possible.
1. On the VCS Control, go to Maintenance >Security certificates >Secure traversal test.

2. Enter the FQDNof the VCS Expressway that is paired with this VCS Control.
3. Enter the TLSverify name of this VCS Control, as it appears on the paired VCS Expressway.
This setting is in the SIPsection of the VCS Expressway's traversal zone configuration page.
4. Click Test connection.
The secure traversal test utility checks whether the hosts on either side of the traversal zone recognize each
other and trust each others' certificate chains.
291
Advanced Security
The Advanced security page (Maintenance > Advanced security) is used to configure the VCS for use in highly
secure environments. This page can only be accessed if the Advanced Account Security option key is installed.
You can configure the system for:
Advanced account security mode

FIPS140-2 cryptographic mode
Configuring Advanced Account Security Mode

Enabling advanced account security limits login access to remotely authenticated users using the web interface only,
and also restricts access to some system features. To indicate that the VCS is in advanced account security mode,
any text specified as the Classification banner message is displayed on every web page.
Note that a system reboot is required for changes to the advanced account security mode to take effect.
Prerequisites
Before advanced account security mode can be enabled:
the system must be configured to use remote account authentication for administrator accounts
the Advanced Account Security option key must be installed
Caution: ensure that the remote directory service is working properly, as after advanced account security is enabled
you will not be able to log in to the VCS via the local admin account or as root.
You are also recommended to configure your system so that:
SNMP is disabled
the session time out period is set to a non-zero value
HTTPS client certificate validation is enabled
user account LDAP server configuration uses TLS encryption and has certificate revocation list (CRL)
checking set to All
remote logging is disabled
incident reporting is disabled
any connection to an external manager uses HTTPS and has certificate checking enabled
Alarms are raised for any non-recommended configuration settings.
Enabling Advanced Account Security

To enable advanced account security:
1. Go to Maintenance > Advanced security.

2. Enter a Classification banner.
The text entered here is displayed on every web page.
3. Set Advanced account security mode to On.
4. Click Save.
5. Reboot the VCS (Maintenance >Reboot).
VCS Functionality: Changes and Limitations

When in secure mode, the following changes and limitations to standard VCS functionality apply:
292
access over SSH and through the serial port is disabled and cannot be turned on (the pwrec password
recovery function is also unavailable)
access over HTTPS is enabled and cannot be turned off
the command line interface (CLI) and API access are unavailable
the root account, the admin account and any other local administrator accounts are disabled
administrator account authentication source is set to Remote only and cannot be changed
if there are three consecutive failed attempts to log in (by the same or different users), login access to the VCS
is blocked for 60 seconds
immediately after logging in, the current user is shown statistics of when they previously logged in and details
of any failed attempts to log in using that account
administrator accounts with read-only or read-write access levels cannot view the Event Log, Configuration
Log and Network Log pages (these pages can be viewed only by accounts with Auditor access level)
the Upgrade page only displays the System platform component
downgrades to version X5.0 or below are not allowed
The Event Log, Configuration Log, Network Log, call history, search history and registration history are cleared
whenever the VCS is taken out of advanced account security mode. Note that if intrusion protection is enabled, this
will cause any existing blocked addresses to become unblocked.
Configuring FIPS140-2 Cryptographic Mode

FIPS140 is a U.S. and Canadian government standard that specifies security requirements for cryptographic modules.
FIPS140-1 became a mandatory standard for the protection of sensitive data in 1994 and was superseded by
FIPS140-2 in 2001.
VCS X8.1 or later implements FIPS140-2 compliant features. When in FIPS140-2 cryptographic mode, system
performance may be affected due to the increased cryptographic workload.
Prerequisites
Before FIPS140-2 mode can be enabled:
Ensure that the system is not using NTLM protocol challenges with a direct Active Directory Service
connection for device authentication; NTLM cannot be used while in FIPS140-2 mode.
If login authentication via a remote LDAP server is configured, ensure that it uses TLS encryption if it is using
SASL binding.
The Advanced Account Security option key must be installed.
FIPS140-2 compliance also requires the following configuration settings:
System-wide SIP transport mode settings must be TLS: On, TCP: Off and UDP: Off.
All SIP zones must use TLS.
The VCS cannot be a part of a cluster.
SNMP and NTP server configuration cannot use MD5 hashing or DES encryption.
If your system is running as a virtualized application and has never been through an upgrade process:
1. Ensure it has a valid release key (check this via Maintenance >Option keys).
2. Perform a system upgrade. You can upgrade the system to the same software release version that it is
currently running.
If you do not complete this step, the activation process described below will fail.
293
Enabling FIPS140-2 Cryptographic Mode
Caution: The transition to FIPS140-2 cryptographic mode requires a system reset to be performed. This will remove
all existing configuration data except IP addresses and option keys. To preserve your data you should take a backup
immediately prior to performing the reset, and then restore the backup file when the reset has completed.
The reset removes all administrator account information and reinstates the default security certificates. To log in after
the reset has completed you will have to use the default admin/TANDBERG credentials. We recommend that you limit
network access to the system during this process until you have secured your system by restoring previous data or by
changing the admin account password from its default value. The root account password will also be reset to
TANDBERG.
To turn your system into a compliant FIPS140-2 cryptographic system:
1. Enable FIPS140-2 cryptographic mode:

a. Go to Maintenance > Advanced security.
b. Set FIPS140-2 cryptographic mode to On.
c. Click Save.
2. Fix any alarms that have been raised that report non-compliant configuration.
3. Take a system backup if you want to preserve your current configuration data.
Note that backups taken while in FIPS140-2 mode require password protection.
4. Reset the system and complete the activation of FIPS140-2 mode:
a. Log in to VCS as root.

b. Type fips-activate
The reset takes approximately 30 minutes to complete.
5. When the system has restarted, log in using the default admin/TANDBERG credentials.
You will see several alarms related to non-FIPS140-2 compliance, insecure passwords and missing default
links. You can ignore these alarms if you intend to restore the backup taken prior to the reset.
6. Restore your previous data, if required.
Note that while in FIPS140-2 mode, you can only restore backup files that were taken when FIPS140-2
cryptographic mode was set On. Any previous administrator account information and passwords will be
restored, however the previous root account password will not be restored. If the data you are restoring
contains untrusted security certificates, the restart that occurs as part of the restore process may take up to 6
minutes to complete.
FIPS140-2 Compliant Features
The following VCS features are FIPS140-2 compliant / use FIPS140-2 compliant algorithms:
Administration over the web interface

XML and REST APIs
SSH access (restricted to only use AES or 3DES ciphers)
Login authentication via a remote LDAP server (must use TLS if using SASL binding)
Client certificate verification
SNMP (SNMPv3 authentication is restricted to SHA1, and SNMPv3 privacy is restricted to AES)
NTP (NTP server authentication using symmetric key is restricted to SHA1)
Device authentication against the local database
SIP connections to/from the VCS providing they use TLS
H.323 connections to/from the VCS
Delegated credential checking
294
SRTP media encryption

SIP/H.323 interworking
TURN server authentication
Encrypted backup/restore operations
Connections to an external manager
Connections to external policy services
Remote logging
Incident reporting
CSR generation
Other VCS features are not FIPS140-2 compliant, including:
SIP certificate revocation features

Any SIP media encryption policy other than Auto
SIP authentication over NTLM / Active Directory
SIP/H.323 device authentication against an H.350 directory service
Microsoft Lync B2BUA
Unified Communications mobile and remote access
Clustering
Use of Cisco TMSPE
Configuring Language Settings

The Language page (Maintenance > Language) controls which language is used for text displayed in the web user
interface.
You can also get to the Language page by clicking on the Language link at the
bottom of every page.
Changing the Language

You can configure both the default language and the language to use on an individual browser:
System The default language used on the web This applies to administrator and user (FindMe) sessions.
default interface. You can select from the set of installed language packs.
language
This The language used by the current browser This setting applies to the browser currently in use on
browser on the current client computer. It can be set the client computer. If you access the VCS user
to use either the system default language or interface using a different browser or a different
a specific alternative language. computer, a different language setting may be in place.
Installing Language Packs

You can install new language packs or install an updated version of an existing language pack.
Language packs are downloaded from the same area on cisco.com from where you obtain your VCS software files.
All available languages are contained in one language pack zip file. Download the appropriate language pack version
that matches your software release.
295
After downloading the language pack, unzip the file to extract a set of .tlp files, one per supported language.
To install a .tlp language pack file:
1. Go to Maintenance > Language.

2. Click Browse and select the .tlp language pack file you want to upload.
3. Click Install.
The selected language pack is then verified and uploaded. This may take several seconds.
4. Repeat steps 2 and 3 for any other languages you want to install.
For the list of available languages, see the relevant release notes for your software version.
Note that:
English (en_us) is installed by default and is always available.

You cannot create your own language packs. Language packs can be obtained only from Cisco.
If you upgrade to a later version of VCS software you will see a "Language pack mismatch" alarm. You may
need to install a later version of the associated language pack to ensure that all text is available in the chosen
language.
Removing Language Packs

To remove a language pack:
1. Go to the Language page (Maintenance > Language).

2. From the list of installed language packs, select the language packs you want to remove.
3. Click Remove.
4. Click Yes when asked to confirm their removal.
The selected language packs are then removed. This may take several seconds.
Backing Up and Restoring VCS Data

The Backup and restore page (Maintenance > Backup and restore) is used to create and restore backup files of
your VCS data.
When to Create a Backup

You are recommended to create a backup in the following situations:
before performing an upgrade

before performing a system restore
in demonstration and test environments if you want to be able to restore the VCS to a known configuration
Content of the Backup File

The data in the backup includes:
system configuration settings

clustering configuration
security certificates
administrator account details
call detail records (if the CDR service on VCS is enabled)
Log files are not included in the backup files.
296
Limitations
The following limitations apply:
Backups can only be restored to a system running the same version of software from which the backup was
made.
You can create a backup on one VCS and restore it to a different VCS, for example if the original system has
failed. However, before performing the restore you must install on the new system the same set of option keys
that were installed on the old system. If you attempt to restore a backup made on a different VCS, you will
receive a warning message, but you will be allowed to continue.
Do not use backups to copy data between VCSs, because system specific information, such as IP addresses,
will be duplicated.
Note: We recommend that you take the VCS unit out of service before performing a restore.
For extra information about backing up and restoring peers in a cluster, see the Cluster Upgrades, Backup and
Restore, page 168 section.
Creating a System Backup

To create a backup of VCS system data:
1. Go to Maintenance > Backup and restore.

2. Optionally, enter an Encryption password with which to encrypt the backup file.
If a password is specified, the same password will be required to restore the file.
3. Click Create system backup file.
4. After the backup file has been prepared, a pop-up window appears and prompts you to save the file (the exact
wording depends on your browser). The default name is in the format:
<software version>_<hardware serial number>_<date>_<time>_backup.tar.gz.
(The file extension is normally .tar.gz.enc if an encryption password is specified. However, if you use Internet
Explorer to create an encrypted backup file, the filename extension will be .tar.gz.gz by default. These
different filename extensions have no operational impact; you can create and restore encrypted backup files
using any supported browser.)
The preparation of the system backup file may take several minutes. Do not navigate away from this page
while the file is being prepared.
5. Save the file to a designated location.
Log files are not included in the system backup file.
Restoring a Previous Backup

To restore the VCS to a previous configuration of system data:
1. Go to Maintenance > Backup and restore.

2. In the Restore section, Browse to the backup file containing the configuration you want to restore.
3. In the Decryption password field, enter the password that was used to create the backup file, or leave it
blank if the backup file was created without a password.
4. Click Upload system backup file.
5. The VCS checks the file and takes you to the Restore confirmation page.
If the backup file is not valid or an incorrect decryption password is entered, you will receive an error
message at the top of the Backup and restore page.
You are shown the current software version and the number of calls and registrations.
6. Read all the warning messages that appear before proceeding with the restore.
297
7. Click Continue with system restore to continue with the restore process.
This will restart your system, so ensure that there are no active calls.
After the system restarts, you are taken to the Login page.
Diagnostics Tools
This section provides information about how to use the diagnostics tools:
diagnostic logging
system snapshot
Network Log and Support Log advanced logging configuration tools
incident reporting
Configuring Diagnostic Logging

The Diagnostic logging tool (Maintenance > Diagnostics > Diagnostic logging) can be used to assist in
troubleshooting system issues.
It allows you to generate a diagnostic log of system activity over a period of time, and then to download the log so
that it can be sent to your Cisco customer support representative. You can also take and subsequently download a
tcpdump while logging is in progress.
To use this tool:
1. Go to Maintenance > Diagnostics > Diagnostic logging.

2. Optionally, select Take tcpdump while logging.
3. Click Start new log.
4. (Optional) Enter some Marker text and click Add marker.
The marker facility can be used to add comment text to the log file before certain activities are performed.
This helps to subsequently identify the relevant sections in the downloaded diagnostic log file.
You can add as many markers as required, at any time while the diagnostic logging is in progress.
Marker text is added to the log with a "DEBUG_MARKER" tag.
5. Reproduce the system issue you want to trace in the diagnostic log.
6. Click Stop logging.
7. Click Download log to save the diagnostic log archive to your local file system. You are prompted to save the
archive (the exact wording depends on your browser).
The downloaded diagnostic log archive contains the following files:
loggingsnapshot_<system host name>_<timestamp>.txt - containing log messages in response to the

activities performed during the logging period
xconf_dump_<system host name>_<timestamp>.txt - containing information about the configuration of the
system at the time the logging was started
xconf_dump_<system host name>_<timestamp>.xml - more completeversion of xconfig, in XMLformat
xstat_dump_<system host name>_<timestamp>.txt - containing information about the status of the system at
the time the logging was started
xstat_dump_<system host name>_<timestamp>.xml - more completeversion of xstatus, in XMLformat
(if relevant) ethn_diagnostic_logging_tcpdumpx_<system host name>_<timestamp>.pcap - containing the
packets captured during the logging period
298
These files can be sent to your Cisco support representative, if you have been requested to do so.
Caution: tcpdump files may contain sensitive information. Only send tcpdump files to trusted recipients.
Consider encrypting the file before sending it, and also send the decrypt password out-of-band.
Note that:
Only one diagnostic log can be produced at a time; creating a new diagnostic log will replace any previously
produced log.
The VCS continually logs all system activity to a unified log file. The diagnostic logging facility works by
extracting a portion of this unified log. On busy systems the unified log file may become full over time and will
discard historic log data so that it can continue logging current activity. This means that all or part of your
diagnostic log could be overwritten. The system will warn you if you attempt to download a partial diagnostic
log file.
The diagnostic log will continue logging all system activity until it is stopped, including over multiple login
sessions and system restarts.
When starting a diagnostic log, the relevant system modules have their log levels automatically set to
"debug". You can ignore any "Verbose log levels configured" alarms; the log levels are reset to their original
values when you stop logging.
Diagnostic logging can only be controlled through the web interface; there is no CLI option.
The tcpdump has a maximum file size limit of 50 MB.
Clustered Systems
Diagnostic logging can also be used if your VCS is a part of a cluster, however some activities only apply to the
"current" peer (the peer to which you are currently logged in to as an administrator):
The start and stop logging operations are applied to every peer in the cluster, regardless of the current peer.
The taking a tcpdump operation is applied to every peer in the cluster, regardless of the current peer.
Each cluster peer maintains its own unified log, and logs activity that occurs only on that peer.
Marker text is only applied to log of the current peer.
You can only download the diagnostic log from the current peer.
To add markers to other peers' logs, or to download diagnostic logs from other peers, you must log in as an
administrator to that other peer.
To collect comprehensive information for debugging purposes, we recommend that you extract the diagnostic log for
each peer in a cluster.
Creating a System Snapshot

The System snapshot page (Maintenance > Diagnostics > System snapshot) lets you create files that can be used
for diagnostic purposes. The files should be sent to your support representative at their request to assist them in
troubleshooting issues you may be experiencing.
You can create several types of snapshot file:
Status snapshot: contains the system's current configuration and status settings.
Logs snapshot: contains log file information (including the Event Log, Configuration Log and Network Log).
Full snapshot: contains a complete download of all system information. The preparation of this snapshot file
may take several minutes to complete and may lead to a drop in system performance while the snapshot is in
progress.
To create a system snapshot file:
1. Click one of the snapshot buttons to start the download of the snapshot file. Typically your support
representative will tell you which type of snapshot file is required.
299
The snapshot creation process will start. This process runs in the background. If required, you can navigate
away from the snapshot page and return to it later to download the generated snapshot file.
When the snapshot file has been created, a Download snapshot button will appear.
2. Click Download snapshot. A pop-up window appears and prompts you to save the file (the exact wording
depends on your browser). Select a location from where you can easily send the file to your support
representative.
Configuring Network Log Levels

The Network Log configuration page (Maintenance > Diagnostics > Advanced > Network Log configuration) is
used to configure the log levels for the range of Network Log message modules.
Caution: changing the logging levels can affect the performance of your system. You should only change a log level
on the advice of Cisco customer support.
To change a logging level:
1. Click on the Name of the module whose log level you want to modify.
2. Choose the required Level from the drop-down list.
A log level of Fatal is the least verbose; Trace is the most verbose.
Each message category has a log level of Info by default.
3. Click Save.
Configuring Support Log Levels

The Support Log configuration page (Maintenance > Diagnostics > Advanced > Support Log configuration) is
used to configure the log levels for the range of Support Log message modules.
Caution: changing the logging levels can affect the performance of your system. You should only change a log level
on the advice of Cisco customer support.
To change a logging level:
1. Click on the Name of the module whose log level you want to modify.
2. Choose the required Level from the drop-down list.
A log level of Fatal is the least verbose; Trace is the most verbose.
Each message category has a log level of Info by default.
3. Click Save.
Incident Reporting
The incident reporting feature of the VCS automatically saves information about critical system issues such as
application failures. You can:
Configure the VCS to send the reports automatically to Cisco customer support
View the reports from the VCS web interface
Download and send the reports manually to Cisco (usually at the request of Cisco customer support)
The information contained in these reports can then be used by Cisco customer support to diagnose the cause of the
failures. All information gathered during this process will be held in confidence and used by Cisco personnel for the
sole purpose of issue diagnosis and problem resolution.
Incident Reporting Caution: Privacy-Protected Personal Data

IN NO EVENT SHOULD PRIVACY-PROTECTED PERSONAL DATA BE INCLUDED IN ANY REPORTS TO CISCO.
300
Privacy-Protected Personal Data means any information about persons or entities that the Customer receives or
derives in any manner from any source that contains any personal information about prospective, former, and existing
customers, employees or any other person or entity. Privacy-Protected Personal Data includes, without limitation,
names, addresses, telephone numbers, electronic addresses, social security numbers, credit card numbers,
customer proprietary network information (as defined under 47 U.S.C. 222 and its implementing regulations), IP
addresses or other handset identifiers, account information, credit information, demographic information, and any
other information that, either alone or in combination with other data, could provide information specific to a
particular person.
PLEASE BE SURE THAT PRIVACY-PROTECTED PERSONAL DATA IS NOT SENT TO CISCO WHEN THE VCS IS
CONFIGURED TO AUTOMATICALLY SEND REPORTS.
IF DISCLOSURE OF SUCH INFORMATION CANNOT BE PREVENTED, PLEASE DO NOT USE THE AUTOMATIC
CONFIGURATION FEATURE. Instead, copy the data from the Incident detail page and paste it into a text file. You can
then edit out any sensitive information before forwarding the file on to Cisco customer support.
Incident reports are always saved locally, and can be viewed via the Incident view page.
Enabling Automatic Incident Reporting

Read the privacy-protected personal data caution before you decide whether to enable automatic incident reporting.
To configure the VCS to send incident reports automatically to Cisco customer support:
1. Go to Maintenance > Diagnostics > Incident reporting > Configuration.

2. Set the Incident reports sending mode to On.
3. Specify the Incident reports URL of the web service to which any error reports are to be sent.
The default is https://cc-reports.cisco.com/submitapplicationerror/.
4. Optional. Specify a Contact email address that can be used by Cisco customer support to follow up any error
reports.
5. Optional. Specify a Proxy server to use for the connection to the incident reporting server.
Use the format (http|https)://address:port/ such as http://www.example.com:3128/
6. Ensure that Create core dumps is On; this is the recommended setting as it provides useful diagnostic
information.
Note: If the Incident reports sending mode is Off, incidents will not be sent to any URL but they will still be saved
locally and can be viewed and downloaded from the Incident detail page.
Sending Incident Reports Manually

Read the privacy-protected personal data caution before you decide whether to send an incident report manually to
Cisco.
To send an incident report manually to Cisco customer support:
1. Go to Maintenance > Diagnostics > Incident reporting > View.

2. Click on the incident you want to send. You will be taken to the Incident detail page.
3. Scroll down to the bottom of the page and click Download incident report. You will be given the option to
save the file.
4. Save the file in a location from where it can be forwarded to Cisco customer support.
Removing Sensitive Information from a Report

The details in the downloaded incident report are Base64-encoded, so you will not be able to meaningfully view or
edit the information within the file.
If you need to edit the report before sending it to Cisco (for example, if you need to remove any potentially sensitive
information) you must copy and paste the information from the Incident detail page into a text file, and edit the
information in that file before sending it to Cisco.
301
Viewing Incident Reports

The Incident view page (Maintenance > Diagnostics > Incident reporting > View) shows a list of all incident reports
that have occurred since the VCS was last upgraded. A report is generated for each incident, and the information
contained in these reports can then be used by Cisco customer support to diagnose the cause of the failures.
For each report the following information is shown:
Field Description
Time The date and time when the incident occurred.
Version The VCS software version running when the incident occurred.
Build The internal build number of the VCS software version running when the incident occurred.
State The current state of the incident:
Pending: indicates that the incident has been saved locally but not sent.
Sent: indicates that details of the incident have been sent to the URL specified in the Incident reporting
configuration page.
To view the information contained in a particular incident report, click on the report's Time. You will be taken to the
Incident detail page, from where you can view the report on screen, or download it as an XML file for forwarding
manually to Cisco customer support.
Incident Report Details

The Incident detail page (Maintenance > Diagnostics > Incident reporting > View, then click on a report's Time)
shows the information contained in a particular incident report.
This is the information that is sent to the external web service if you have enabled Incident reports sending mode
(via Maintenance > Diagnostics > Incident reporting > Configuration). It is also the same information that is
downloaded as a Base64-encoded XML file if you click Download incident report.
The information contained in the report is:
Field Description
Time The date and time when the incident occurred.
Version The VCS software version running when the incident occurred.
Build The internal build number of the VCS software version running when the incident occurred.
Name The name of the software.
System The system name (if configured), otherwise the IP address.
Serial number The hardware serial number.
Process ID The process ID the VCS application had when the incident occurred.
Release A true/false flag indicating if this is a release build (rather than a development build).
User name The name of the person that built this software. This is blank for release builds.
Stack The trace of the thread of execution that caused the incident.
Debug information A full trace of the application call stack for all threads and the values of the registers.
302
Caution: for each call stack, the Debug information includes the contents of variables which may contain some
sensitive information, for example alias values and IP addresses. If your deployment is such that this information could
contain information specific to a particular person, read the caution regarding privacy-protected personal data before
you decide whether to enable automatic incident reporting.
Checking the Effect of a Pattern

The Check pattern tool (Maintenance > Tools > Check pattern) lets you test whether a pattern or transform you
intend to configure on the VCS will have the expected result.
Patterns can be used when configuring:
Allow lists and Deny lists to specify aliases to be included in the lists
Transforms to specify aliases to be transformed before any searches take place
Search rules to filter searches based on the alias being searched for, and to transform an alias before the
search is sent to a zone
Subzone membership rules to determine, based on the address of the device, to which subzone an endpoint is
assigned when it registers with the VCS
To use this tool:
1. Enter an Alias against which you want to test the transform.

2. In the Pattern section, enter the combination of Pattern type and Pattern behavior for the Pattern string
being tested.
If you select a Pattern behavior of Replace, you also need to enter a Replace string.
If you select a Pattern behavior of Add prefix or Add suffix, you also need to enter an Additional text string
to append/prepend to the Pattern string.
The VCS has a set of predefined pattern matching variables that can be used to match against certain
configuration elements.
3. Click Check pattern to test whether the alias matches the pattern.
The Result section shows whether the alias matched the pattern, and displays the resulting alias (including
the effect of any transform if appropriate).
Locating an Alias
The Locate tool (Maintenance > Tools > Locate) lets you test whether the VCS can find an endpoint identified by the
given alias, within the specified number of "hops", without actually placing a call to that endpoint.
This tool is useful when diagnosing dial plan and network deployment issues.
To use this tool:
1. Enter the Alias you want to locate.

2. Enter the Hop count for the search.
3. Select the Protocol used to initiate the search, either H.323 or SIP. The search may be interworked during the
search process, but the VCS always uses the native protocol first to search those target zones and policy
services associated with search rules at the same priority, before searching those zones again using the
alternative protocol.
4. Select the Source from which to simulate the search request. Choose from the Default Zone (an unknown
remote system), the Default Subzone (a locally registered endpoint) or any other configured zone or subzone.
5. Select whether the request should be treated as Authenticated or not (search rules can be restricted so that
they only apply to authenticated messages).
6. Optionally, you can enter a Source alias. Typically, this is only relevant if the routing process uses CPL that
has rules dependent on the source alias. (If no value is specified a default alias of xcom-locate is used.)
303
7. Click Locate to start the search.

The status bar shows Searching... followed by Search completed. The results include the list of zones that
were searched, any transforms and Call Policy that were applied, and if found, the zone in which the alias
was located.
The locate process performs the search as though the VCS received a call request from the selected Source zone.
For more information, see the Call Routing Process, page 172 section.
Port Usage
The pages under the Maintenance > Tools > Port usage menu show, in table format, all the IP ports that have been
configured on the VCS.
The information shown on these pages is specific to that particular VCS and varies depending on the VCS's
configuration, the option keys that have been installed and the features that have been enabled.
The information can be sorted according to any of the columns on the page, so for example you can sort the list by IP
port, or by IP address.
Each page contains an Export to CSV option. This lets you save the information in a CSV (comma separated values)
format file suitable for opening in a spreadsheet application.
Note that IP ports cannot be configured separately for IPv4 and IPv6 addresses, nor for each of the two LAN
interfaces. In other words, after an IP port has been configured for a particular service, for example SIP UDP, this will
apply to all IP addresses of that service on the VCS. Because the tables on these pages list all IP ports and all IP
addresses, a single IP port may appear on the list up to 4 times, depending on your VCS configuration.
The port information is split into the following pages:
Local Inbound Ports, page 304

Local Outbound Ports, page 304
Remote Listening Ports, page 305
On a VCS Expressway you can also configure the specific listening ports used for firewall traversal via Configuration
> Traversal > Ports.
See Port Reference, page 367 for more information about the specific ports used by the VCS.
Local Inbound Ports

The Local inbound ports page (Maintenance > Tools > Port usage > Local inbound ports) shows the listening IP
ports on the VCS that are used to receive inbound communications from other systems.
For each port listed on this page, if there is a firewall between the VCS and the source of the inbound
communications, your firewall must allow:
inbound traffic to the IP port on the VCS from the source of the inbound communications, and
return traffic from that same VCS IP port back out to the source of the inbound communication.
Note: this firewall configuration is particularly important if this VCS is a traversal client or traversal server, in order for
Expressway firewall traversal to function correctly.
Local Outbound Ports

The Local outbound ports page (Maintenance > Tools > Port usage > Local outbound ports) shows the source IP
ports on the VCS that are used to send outbound communications to other systems.
For each port listed on this page, if there is a firewall between the VCS and the destination of the outbound
communications, your firewall must allow:
304
outbound traffic out from the IP port on the VCS to the destination of the outbound communications, and
return traffic from that destination back to the same VCS IP port.
Note: this firewall configuration is particularly important if this VCS is a traversal client or traversal server, in order for
Expressway firewall traversal to function correctly.
Remote Listening Ports

The Remote listening ports page (Maintenance > Tools > Port usage > Remote listening ports) shows the
destination IP addresses and IP ports of remote systems with which the VCS communicates.
Your firewall must be configured to allow traffic originating from the local VCS to the remote devices identified by the
IP addresses and IP ports listed on this page.
Note: there are other remote devices not listed here to which the VCS will be sending media and signaling, but the
ports on which these devices receive traffic from the VCS is determined by the configuration of the destination
device, so they cannot be listed here. If you have opened all the ports listed in the Local outbound ports page, the
VCS will be able to communicate with all remote devices. You only need to use the information on this page if you
want to limit the IP ports opened on your firewall to these remote systems and ports.
Network Utilities
This section provides information about how to use the network utility tools:
Ping: allows you to check that a particular host system is contactable from the VCS and that your network is
correctly configured to reach it.
Traceroute: allows you to discover the details of the route taken by a network packet sent from the VCS to a
particular destination host system.
Tracepath: allows you to discover the path taken by a network packet sent from the VCS to a particular
destination host system.
DNS lookup: allows you to check which domain name server (DNS server) is responding to a request for a
particular hostname.
Ping
The Ping tool (Maintenance > Tools > Network utilities > Ping) can be used to assist in troubleshooting system
issues.
It allows you to check that a particular host system is contactable and that your network is correctly configured to
reach it. It reports details of the time taken for a message to be sent from the VCS to the destination host system.
To use this tool:
1. In the Host field, enter the IP address or hostname of the host system you want to try to contact.
2. Click Ping.
A new section will appear showing the results of the contact attempt. If successful, it will display the following
information:
Host The hostname and IP address returned by the host system that was queried.
Response time The time taken (in ms) for the request to be sent from the VCS to the host system and back
(ms) again.
Traceroute
The Traceroute tool (Maintenance > Tools > Network utilities > Traceroute) can be used to assist in troubleshooting
system issues.
305
It allows you to discover the route taken by a network packet sent from the VCS to a particular destination host
system. It reports the details of each node along the path, and the time taken for each node to respond to the request.
To use this tool:
1. In the Host field, enter the IP address or hostname of the host system to which you want to trace the path.
2. Click Traceroute.
A new section will appear with a banner stating the results of the trace, and showing the following information for
each node in the path:
TTL (Time to Live). This is the hop count of the request, showing the sequential number of the node.
Response This shows the IP address of the node, and the time taken (in ms) to respond to each packet received
from the VCS.
*** indicates that the node did not respond to the request.
The route taken between the VCS and a particular host may vary for each traceroute request.
Tracepath
The Tracepath tool (Maintenance > Tools > Network utilities > Tracepath) can be used to assist in troubleshooting
system issues.
It allows you to discover the route taken by a network packet sent from the VCS to a particular destination host
system.
To use this tool:
1. In the Host field, enter the IP address or hostname of the host system to which you want to trace the route.
2. Click Tracepath.
A new section will appear with a banner stating the results of the trace, and showing the details of each node along
the path, the time taken for each node to respond to the request, and the maximum transmission units (MTU).
The route taken between the VCS and a particular host may vary for each tracepath request.
DNS Lookup
The DNS lookup tool (Maintenance > Tools > Network utilities > DNS lookup) can be used to assist in
troubleshooting system issues.
It allows you to query DNS for a supplied hostname and display the results of the query if the lookup was successful.
To use this tool:
1. In the Host field, enter either:

the name of the host you want to query, or
an IPv4 or IPv6 address if you want to perform a reverse DNS lookup
306
2. In the Query type field, select the type of record you want to search for:
(for reverse lookups the Query type is ignored - the search automatically looks for PTR records)
Option Searches for...
All any type of record
A (IPv4 address) a record that maps the hostname to the host's IPv4 address
AAAA (IPv6 address) a record that maps the hostname to the host's IPv6 address
SRV (services) SRV records (which includes those specific to H.323, SIP, Unified Communications
and TURN services, see below)
NAPTR (Name a record that rewrites a domain name (into a URI or other domain name for
authority pointer) example)
3. By default the system will submit the query to all of the system's default DNSservers (System >DNS). To
query specific servers only, set Check against the following DNS servers to Custom and then select the DNS
servers you want to use.
4. Click Lookup.
A separate DNS query is performed for each selected Query type. The domain that is included within the query sent
to DNS depends upon whether the supplied Host is fully qualified or not (a fully qualified host name contains at least
one "dot"):
If the supplied Host is fully qualified:

DNS is queried first for Host
If the lookup for Host fails, then an additional query for Host.<system_domain> is performed (where
<system_domain> is the Domain name as configured on the DNS page)
If the supplied Host is not fully qualified:
DNS is queried first for Host.<system_domain>
If the lookup for Host.<system_domain> fails, then an additional query for Host is performed
For SRV record type lookups, multiple DNS queries are performed. An SRV query is made for each of the following _
service._protocol combinations:
_h323ls._udp.<domain>
_h323rs._udp.<domain>
_h323cs._tcp.<domain>
_sips._tcp.<domain>
_sip._tcp.<domain>
_sip._udp.<domain>
_collab-edge._tls
_cisco-uds._tcp
_turn._udp.<domain>
_turn._tcp.<domain>
In each case, as for all other query types, either one or two queries may be performed for a <domain> of either Host
and/or Host.<system_domain>.
307
Results
A new section will appear showing the results of all of the queries. If successful, it will display the following
information:
Query The type of query that was sent by the VCS.

type
Name The hostname contained in the response to the query.
TTL The length of time (in seconds) that the results of this query will be cached by the VCS.
Class IN (internet) indicates that the response was a DNS record involving an internet hostname, server or IP
address.
Type The record type contained in the response to the query.
Response The content of the record received in response to the query for this Name and Type.
Restarting, Rebooting and Shutting Down

The Restart options page (Maintenance > Restart options) allows you to restart, reboot or shut down the VCS
without having physical access to the hardware.
Caution: do not restart, reboot or shut down the VCS while the red ALM LED on the front of the unit is on. This
indicates a hardware fault. Contact your Cisco customer support representative.
Restarting
The restart function shuts down and restarts the VCS application software, but not the operating system or hardware.
A restart takes approximately 3 minutes.
A restart is typically required in order for some configuration changes to take effect, or when the system is being
added to, or removed from, a cluster. In these cases a system alarm is raised and will remain in place until the system
is restarted.
If the VCS is part of a cluster and other peers in the cluster also require a restart, we recommend that you wait until
each peer has restarted before restarting the next peer.
Rebooting
The reboot function shuts down and restarts the VCS application software, operating system and hardware. A reboot
takes approximately 5 minutes.
Reboots are normally only required after software upgrades and are performed as part of the upgrade process. A
reboot may also be required when you are trying to resolve unexpected system errors.
Shutting down
A shutdown is typically required if you want to unplug your unit, prior to maintenance or relocation for example. The
system must be shut down before it is unplugged. Avoid uncontrolled shutdowns, in particular the removal of power
to the system during normal operation.
After the system has been shut down, the only way it can be restarted (unless it is a virtual appliance) is by pressing
the soft power button on the unit itself. You must therefore have physical access to the unit if you want to restart it
after it has been shut down.
Effect on active calls and registrations
Any of these restart options will cause all active calls and registrations to be terminated. (If the VCS is part of a
cluster, only those calls for which the VCS is taking the signaling will be terminated.)
For this reason, the System status section displays the number of current calls and registrations, so you can check
these before you restart the system. If you do not restart the system immediately, you should refresh this page before
restarting to check the current status of calls and registrations.
308
If Mobile and remote access is enabled, the number of currently provisioned sessions is displayed (VCS Control
only).
Restarting, rebooting or shutting down using the web interface
To restart the VCS using the web interface:
1. Go to Maintenance > Restart options.

2. Check the number of calls and registrations currently in place.
3. Click Restart, Reboot or Shutdown as appropriate and confirm the action.
Sometimes only one of these options, such as Restart for example, may be available. This typically occurs
when you access the Restart options page after following a link in an alarm or a banner message.
Restart/reboot: the Restarting/Rebooting page appears, with an orange bar indicating progress.
After the system has successfully restarted or rebooted, you are automatically taken to the Login page.
Shutdown: the Shutting down page appears.
This page remains in place after the system has successfully shut down but any attempts to refresh the
page or access the VCS will be unsuccessful.
Developer Resources
The VCS includes some features that are intended for the use of Cisco support and development teams only. Do not
access these pages unless it is under the advice and supervision of your Cisco support representative.
Caution: incorrect usage of the features on these pages could cause the system operation to become unstable,
cause performance problems and cause persistent corruption of system configuration.
These features are:
Debugging and System Administration Tools, page 309

Experimental Menu, page 309
Debugging and System Administration Tools

Caution: these features are not intended for customer use unless on the advice of a Cisco support representative.
Incorrect usage of these features could cause the system operation to become unstable, cause performance
problems and cause persistent corruption of system configuration.
The VCS includes a number of debugging and system admin tools that allow administrators to inspect what is
happening at a detailed level on a live system, including accessing and modifying configuration data and accessing
network traffic.
To access these tools:
1. Open an SSH session.

2. Log in as admin or root as required.
3. Follow the instructions provided by your Cisco support representative.
Experimental Menu
The VCS web interface contains a number of pages that are not intended for use by customers. These pages exist for
the use of Cisco support and development teams only. Do not access these pages unless it is under the advice and
supervision of your Cisco support representative.
Caution: incorrect usage of the features on these pages could cause the system operation to become unstable,
cause performance problems and cause persistent corruption of system configuration.
To access these pages:
309
1. Go to https://<VCS host name or IP address>/setaccess.

The Set access page appears.
2. In the Access password field, enter qwertsys.
3. Click Enable access.
A new top-level Experimental menu will appear to the right of the existing menu items.
310
311
Overview and Status Information
You can view information about the current status, registrations, current calls and call history, and configuration of
the VCS by using the Status menu options.
Status Overview 312

System Information 313
Ethernet Status 314
IP Status 315
Resource Usage 315
Registration Status 317
Call Status 318
B2BUA Calls 320
Search History 320
Search Details 321
Local Zone Status 322
Zone Status 322
Bandwidth 323
Policy Server Status and Resiliency 323
TURN Relay Usage 324
Unified Communications Status 325
Presence 325
Lync B2BUA 326
TMS Provisioning Extension Service Status 327
Starter Pack Provisioning Server Status 330
Managing Alarms 331
Logs 332
Hardware Status 335
Status Overview
The Overview page (Status >Overview) provides an overview of the current status of the VCS (or VCS cluster, if
applicable). This page is displayed by default after logging in to the VCSas an administrator.
312
Field Description
System information: many of the items in this section are configurable; click on the item name to go to its
configuration page.
System name The name that has been assigned to the VCS.
Up time The amount of time that has elapsed since the system last restarted.
Software version The version of software that is currently installed on the VCS.
IPv4 address The VCSs IPv4 addresses.
IPv6 address The VCSs IPv6 addresses.
Options The maximum number of calls and registrations, and the availability of additional VCS
features such as TURN Relays, FindMe, Device Provisioning and Advanced Networking,
are controlled through the use of option keys. This section shows all the options that are
currently installed on the VCS.
Resource usage
This section provides statistics about the current and cumulative license usage for calls and registrations.
It shows current and peak (highest concurrent) usage broken down by:
Unified CM remote session calls (if Unified Communications Mobile and remote access is enabled)
Traversal calls
Non-traversal calls
SIP traversal audio-only calls
Registrations
TURNrelays (VCS Expressway only)
It also displays resource and license usage information:
Monitored resource usage, expressed as a percentage of the system capacity.

Current and peak license usage, expressed as a percentage of the available licenses for each license type.
Each traversal call license allows either 1 video call or 2 audio-only SIP calls. Hence, a 100 traversal call
license would allow, for example, 90 video and 20 SIP audio-only simultaneous calls. Any other audio-only
call (non-traversal, H.323 or interworked) will consume a standard video call license (traversal or non-
traversal as appropriate).
You can view details of current calls or registrations by clicking on the relevant item in the section.
All statistics are based on data since the system was last restarted. The information on this page refreshes
automatically every 5 seconds.
Total usage statistics are also shown (unless Unified Communications Mobile and remote access is enabled, in
which case this data is shown on the Resource usage page only).
If the VCS is part of a cluster, then details for each peer are shown as well as totals for the entire cluster.
See About Clusters, page 160 for more information.
System Information
The System information page (Status > System > Information) provides details of the software, hardware, and time
settings of the VCS.
313
Many of the items in the System information and Time information sections are configurable; click on the item name
to be taken to its configuration page.
Field Description
System information section:
System name The name that has been assigned to the VCS.
Product This identifies the VCS.
Software version The version of software that is currently installed on the VCS.
Software build The build number of this software version.
Software release The date on which this version of the software was released.
date
Software name The internal reference number for this software release.
Software options The maximum number of calls, and the availability of additional VCS features such as
FindMe, Device Provisioning and Advanced Networking, are controlled through the use of
option keys. This section shows all the optional features currently installed on the VCS.
Hardware version The version number of the hardware on which the VCS software is installed.
Serial number The serial number of the hardware or virtual machine on which the VCS software is installed.
Time information section:
Up time The amount of time that has elapsed since the system last restarted.
System time (UTC) The time as determined by the NTP server.

If no NTP server is configured, this shows Time Not Set.
Time zone The time zone that has been configured on the Time page.
Local time If an NTP server is configured, the system time is shown in local time (UTC adjusted
according to the local time zone).
If no NTP server is configured, the time according to the VCSs operating system is shown.
Active sessions section:
Administrator The number of current active administrator sessions. Click on the link to see the list of active
sessions sessions.
FindMe sessions The number of current active FindMe sessions. Click on the link to see the list of active
sessions.
Ethernet Status
The Ethernet page (Status > System > Ethernet) shows the MAC address and Ethernet speed of the VCS.
The page displays the following information for the LAN 1 port and, if the Advanced Networking option key has been
installed, the LAN 2 port:
Field Description
MAC address The MAC address of the VCSs Ethernet device for that LAN port.
Speed The speed of the connection between the LAN port on the VCS and the Ethernet switch.
The Ethernet speed can be configured via the Ethernet page.
314
IP Status
The IP status page (Status > System > IP) shows the current IP settings of the VCS.
Field Description
IP section:
Protocol Indicates the IP protocol supported by the VCS:
IPv4: it only accepts registrations from endpoints using an IPv4 address, and only takes calls
between two endpoints communicating via IPv4. It communicates with other systems via IPv4
only.
IPv6: it only accepts registrations from endpoints using an IPv6 address, and only takes calls
between two endpoints communicating via IPv6. It communicates with other systems via IPv6
only.
Both: it accepts registrations from endpoints using either an IPv4 or IPv6 address, and takes
calls using either protocol. If a call is between an IPv4-only and an IPv6-only endpoint, the
VCS acts as an IPv4 to IPv6 gateway. It communicates with other systems via either protocol.
IPv4 The IPv4 gateway used by VCS.

gateway
IPv6 The IPv6 gateway used by VCS.

gateway
Advanced Indicates whether the second LAN port has been enabled. This is done by installing the Advanced
Networking Networking option key.
LAN 1 Shows the IPv4 address and subnet mask, and IPv6 address of the LAN 1 port.
LAN 2 If the Advanced Networking option key has been installed, this shows the IPv4 address and subnet
mask, and IPv6 address of the LAN 2 port.
DNS section:
Server 1..5 The IP addresses of each of the DNS servers that are queried when resolving domain names. Up to 5
address DNS servers may be configured.
Domain Specifies the name to be appended to the host name before a query to the DNS server is executed.
The IP settings can be configured via the IP page.
Resource Usage
The Resource usage page (Status > System > Resource usage) provides statistics about the current and cumulative
license usage for calls and registrations.
It shows current and peak (highest concurrent) usage broken down by:
Unified CM remote session calls (if Unified Communications Mobile and remote access is enabled)
Traversal calls
Non-traversal calls
SIP traversal audio-only calls
Registrations
TURNrelays (VCS Expressway only)
It also displays resource and license usage information:
315
Monitored resource usage, expressed as a percentage of the system capacity.

Current and peak license usage, expressed as a percentage of the available licenses for each license type.
Each traversal call license allows either 1 video call or 2 audio-only SIP calls. Hence, a 100 traversal call
license would allow, for example, 90 video and 20 SIP audio-only simultaneous calls. Any other audio-only
call (non-traversal, H.323 or interworked) will consume a standard video call license (traversal or non-
traversal as appropriate).
You can view details of current calls or registrations by clicking on the relevant item in the section.
All statistics are based on data since the system was last restarted. The information on this page refreshes
automatically every 5 seconds.
If the VCS is part of a cluster, details for each peer are shown as well as totals for the entire cluster.
The following types of licenses are pooled for use by any peer in a cluster, irrespective of which peer the licenses are
installed on:
Traversal or non-traversal call licenses

TURNrelay licenses
You can cluster up to 6 VCS systems to increase capacity by a maximum factor of 4 (see Performance Capabilities,
page 336 for per peer capacity limits).
If a cluster peer becomes unavailable, the shareable licenses installed on that peer remain available to the rest of the
cluster peers for two weeks from the time the cluster lost contact with the peer. This will maintain the overall license
capacity of the cluster however, note that each peer is limited by its physical capacity. After this two week period,
the licenses associated with the unavailable peer are removed from the cluster. To maintain the same capacity for
your cluster, you should ensure that either the problem with the peer is resolved or new option keys are installed on
another peer in the cluster.
The maximum number of licenses that each VCS system can use depends on the type of appliance or VM:
Table 10 Maximum licenses that a peer can use
Small / Medium / CE500 / CE1100 Large / CE1000 / CE1100

systems systems
Traversal calls 150 500
Non-traversal 750 750

calls
Registrations 2500 5000
TURN relays * 1800 6000
CE1100 appliance can run with medium or large capacity, depending on whether it has 1Gbps or 10Gbps NICs
installed.
This is the maximum number of licenses the system can use. This limit specifically applies to the case where a peer
becomes unavailable and other peers must use its licenses to honor the cluster's overall capacity. This is not
intended as a production capcacity limit, only as a temporary measure to allow the affected peer to be returned to
normal service. We strongly discourage installing more than 100 licenses on any platform that has small or
medium capacity.
* On a Large system, the total TURN capacity of 6000 relays is spread evenly across 6 ports; each port is limited to
handling 1000 relays. On a Small/Medium system, there is a single TURN port that handles up to 1800 relays.
Note that each VCS comes pre-installed with 2,500 registration licenses, and that registration licenses are not
shared across a cluster.
316
You can see a summary of all of the call, registration and TURN relay licenses installed on each cluster peer by going
to the Option keys page and scrolling down to the Current licenses section.
Licenses Used in Intercluster Calls
This section describes the licenses used when endpoints are registered to different peers in the same cluster.
If the call media does not traverse the cluster peers:
A SIP call between the endpoints consumes two non-traversal call licenses (one on each node).
An H.323 call between the endpoints consumes one non-traversal license (on the node where the endpoint
that initiated the call is registered).
If the call media traverses the cluster peers, or if either endpoint is registered with ASSENTor H.460 capability:
A SIP call between the endpoints consumes two traversal call licenses (one on each node).
An H.323 call between the endpoints consumes two traversal call licenses (one on each node).
See About Clusters, page 160 for more information.
Registration Status
Registration status information can be displayed for both current and historic registrations. If the VCS is part of a
cluster, all registrations that apply to any peer in the cluster are shown.
The Registrations by device page (Status > Registrations > By device) lists each device currently registered
with the VCS, and allows you to remove a device's registration. If the VCS is part of a cluster, all registrations
across the cluster are shown. Note that an H.323 device can register with more than one alias; in such cases
this page will show only one alias and (when present) one E.164 number for that device. Note also that a
single device can support both the SIP and H.323 protocols; in such a case the SIP registration and the H.323
registration will appear as separate entries on this page.
The Registrations by alias page (Status > Registrations > By alias) lists all the aliases, E.164 numbers and
prefixes used by all endpoints and systems currently registered with the VCS. Note that a single H.323 device
can register with more than one alias, and each will appear as a separate entry on this page.
The Registration history page (Status > Registrations > History) lists all the registrations that are no longer
current. It contains all historical registrations since the VCS was last restarted.
Field Description
Name For H.323 devices, this is one of its aliases. If the device has registered with more than one alias, this
will be (in order of preference) its H.323 ID, URI or email address. For MCUs and Gateways this will be its
alias or, if it has not registered an alias, one of its prefixes. For SIP devices, this is its SIP AOR.
Number For H.323 devices that have registered one or more E.164 numbers, the first will be shown here. For SIP
devices this will always be blank because they cannot register E.164 numbers. (This is shown in the
Alias column in the registration by alias view.)
Alias The H.323 alias, E.164 number, prefix or SIP AOR registered by a device. (Registration by alias view
only.)
Type Indicates the nature of the registration. This will most commonly be Endpoint, MCU, Gateway, or SIP UA.
The registration by alias view shows whether the alias is an H.323 ID, E.164 number, prefix or SIP AOR.
Protocol Indicates whether the registration is for a SIP or H.323 device.
Creation The date and time at which the registration was accepted.
time If an NTP server has not been configured, this will say Time not set.
317
Field Description
Address For H.323 devices this is its RAS address, and for SIP UAs it is the Contact address presented in the
REGISTER request.
End time The date and time at which the registration was terminated. (Registration history view only.)
Duration The length of time that the registration was in place. (Registration history view only.)
Reason The reason why the registration was terminated. (Registration history view only.)
Peer Identifies the cluster peer to which the device is registered.
Actions Click View to go to the Registration details page to see further detailed information about the
registration.
Registration details
The information shown on the Registration details page depends on the device's protocol, and whether the
registration is still current. For example, SIP registrations include the AOR, contact and, if applicable, public GRUU
details. H.323 registration details include all of the registered aliases. It also provides related tasks that let you View
active calls involving this registration and View previous calls involving this registration; these options take you to
the Calls by registration page, showing the relevant current or historic call status information filtered for that
particular registration.
Unregistering and blocking devices
The registration status pages provide options to manually unregister and block devices.
Click Unregister to unregister the device. Note that the device may automatically re-register after a period of
time, depending on its configuration. To prevent this, you must also use a registration restriction policy such
as an Allow List or Deny List.
Click Unregister and block to unregister the device and add the alias to the Deny List page, thus preventing
the device from automatically re-registering. (This option is only available if the Restriction policy is set to
Deny List.)
Note that if your VCS is part of a cluster you have to be logged into the peer to which the device is registered to be
able to unregister it.
Call Status
Call status information can be displayed for both current and completed calls:
Current calls: the Call status page (Status > Calls > Calls) lists all the calls currently taking place to or from
devices registered with the VCS, or that are passing through the VCS.
Completed calls: the Call history page (Status > Calls > History) lists all the calls that are no longer active.
The list is limited to the most recent 500 calls, and only includes calls that have taken place since the VCS
was last restarted.
The same set of call status information is also shown on the Calls by registration page (accessed via the
Registration details page).
If the VCS is part of a cluster, all calls that apply to any peer in the cluster are shown, although the list is limited to the
most recent 500 calls per peer.
Call summary information
The following summary information is displayed initially:
Field Description
Start time The date and time when the call was placed.
318
Field Description
End time The date and time when the call ended (completed calls only).
Duration The length of time of the call.
Source The alias of the device that placed the call. (If the call passes through more than one VCS and User
Policy is enabled, the caller's FindMe ID may be displayed instead.)
Destination The alias dialed from the device. This may be different from the alias to which the call was placed,
which may have been transformed (due to pre-search transforms, zone transforms or User Policy).
Type Indicates either a traversal or non-traversal call.
Protocol Shows whether the call used H.323, SIP, or both protocols. For calls passing through the B2BUA, this
may show "Multiple components"; you can view the call component summary section to see the
protocol of each individual call component.
Status The reason the call ended (completed calls only).
Peer Identifies the cluster peer through which the call is being made.
Actions Click View to see further information about the call, including a list of all of the call components that
comprise that call.
Call components summary information

After selecting a call from the primary list (as described above) you are shown further details of that call, including a
list of all of the call components that comprise that call.
Each call component may be one of the following types:
VCS: a standard VCS call

B2BUA: a call component that is routed through the B2BUA to apply a media encryption policy or ICE
messaging support
Microsoft Lync B2BUA: a call component that is routed through the Microsoft Lync B2BUA
You can view full details of each call component by clicking on the Local call serial number associated with each
component. This will open the Call details page which lists full information about that component, including all call
legs and sessions. It also provides further links to the Call media page which lists the individual media channels
(audio, video, data and so on) for the most relevant session for a traversal call.
If the VCS is part of a cluster and the call passes through two cluster peers, you can click View associated call on
other cluster peer to see the details of the other leg of the call.
Identifying mobile and remote access calls
The call status and call history pages show all call types: Unified CM remote sessions (if mobile and remote access is
enabled) as well as VCS traversal and non-traversal calls.
To distinguish between the call types you must drill down into the call components. Mobile and remote access calls
have different component characteristics depending on whether the call is being viewed on the VCS Control or VCS
Expressway:
On a VCS Control, a Unified CM remote session will have 3 components (as it uses the B2BUA to enforce
media encryption). One of the VCS components will route the call through one of the automatically generated
neighbor zones (with a name prefixed by either CEtcp or CEtls) between VCS and Unified CM.
On a VCS Expressway, there will be one component and that will route the call through the
CollaborationEdgeZone.
Note that if both endpoints are outside of the enterprise (i.e. off premises), you will see this treated as 2 separate
calls.
319
Disconnecting Calls
Click Disconnect to disconnect the selected calls. Note that if your VCS is part of a cluster you have to be logged into
the peer through which the call is associated to be able to disconnect the call.
Call disconnection works differently for H.323 and SIP calls due to differences in the way the protocols work:
H.323 calls, and interworked H.323 to SIP calls: the Disconnect command will actually disconnect the call.
SIP to SIP calls: the Disconnect command will cause the VCS to release all resources used for the call and
the call will appear on the system as disconnected. However, SIP calls are peer-to-peer and as a SIP proxy
the VCS has no authority over the endpoints. Although releasing the resources may have the side-effect of
disconnecting the SIP call, it is also possible that the call signaling, media or both may stay up (depending on
the type of call being made). The call will not actually disconnect until the SIP endpoints involved have also
cleared their resources.
SIP calls via the B2BUA: as the B2BUA can control the state of a call, if you disconnect the leg of the call that
is passing through the B2BUA (where the Type is B2BUA), the call will fully disconnect. Note that the call may
take a few seconds to disappear from the Call status page you may have to refresh the page on your
browser.
B2BUA Calls
The B2BUA calls page (Status > Calls > Calls or Status > Calls > History, then click View for a particular B2BUA call)
provides overview information about a call routed through the B2BUA.
Calls are routed through the B2BUA if:
a media encryption policy (any encryption setting other than Auto) has been applied to the call
ICE messaging support has been triggered
the Microsoft Lync B2BUA service is enabled and the call has been routed through the To Microsoft Lync
server via B2BUA neighbor zone
Note that for Microsoft Lync B2BUA calls, you can click the Corresponding VCS call link to see details of the leg
passing through the VCS.
Viewing B2BUA Call Media Details

The B2BUA call media page (accessed from the B2BUA calls page by clicking View media statistics for this call)
shows information about the media channels (audio and video) that made up the call passing through the B2BUA. For
calls using the Microsoft Lync B2BUA, this comprises legs between the VCS, the Lync server and, if applicable, the
transcoder.
Search History
The Search history page (Status > Search history) lists the most recent 255 searches that have taken place since
the VCS was last restarted.
About searches
Before a call can be placed, the endpoint being called must be located. The VCS sends and receives a series of
messages during its attempt to locate the endpoint being called; these messages are each known as searches. An
individual call can have one or more searches associated with it, and these searches can be of different types.
The type of search message that is sent depends on whether the call is for SIP or H.323, and whether the call request
was received locally or from an external zone, as follows:
H.323 calls that are placed locally: two messages are sent - the first is an ARQ which locates the device being
called, and the second is the call Setup which sends a request to the device asking it to accept the call. Each
message shows up as a separate search in the Search history page, but only the Setup message is
320
associated with a particular call.

H.323 searches originating from external zones: an LRQ will appear in the Search history page.
SIP: a single message is sent in order to place a call: this is either a SIP INVITE or a SIP OPTIONS.
Note that an individual call can have one or more searches associated with it, and these searches can be of different
types. Each search has an individual Search ID; each call has an individual Call Tag (see Identifying Calls, page 211).
The VCS supports up to 500 concurrent searches.
Search history list
The search history summary list shows the following information:
Field Description
Start time The date and time at which the search was initiated.
Search The type of message being sent.

type
Source The alias of the endpoint that initiated the call.
Destination The alias that was dialed from the endpoint. This may be different from the alias to which the call was
actually placed, as the original alias may have been transformed either locally or before the neighbor
was queried.
Status Indicates whether or not the search was successful.
Actions Allows you to click View to go to the Search details page, which lists full details of this search.
Filtering the list

To limit the list of searches, enter one or more characters in the Filter field and click Filter. Only those searches that
contain (in any of the displayed fields) the characters you entered are shown.
To return to the full list of searches, click Reset.
Search Details
The Search details page lists full information about either an individual search, or all searches associated with a
single call (depending on how you reached the page). The information shown includes:
the subzones and zones that were searched

the call path and hops
any transforms that were applied to the alias being searched for
use of policies such as Admin Policy or User Policy (FindMe)
any policy services that were used
Other information associated with the search and (if it was successful) the resulting call can be viewed via the links in
the Related tasks section at the bottom of the page:
View all events associated with this call tag takes you to the Event Log page, filtered to show only those
events associated with the Call Tag relating to this search.
View call information associated with this call tag takes you to the Call details page, where you can view
overview information about the call.
View all searches associated with this call tag is shown if you are viewing details of an individual search and
there are other searches associated with the same call. It takes you to a new Search details page which lists
full information about all the searches associated with the call's Call Tag.
321
Local Zone Status

The Local Zone status page (Status > Local Zone) lists all of the subzones on the VCS that together make up the
Local Zone. This always includes the Default Subzone and the Traversal Subzone, plus any other subzones that have
been configured.
Field Description
Subzone The names of each subzone currently configured on this VCS.

name Clicking on a Subzone name takes you to the configuration page for that subzone.
Registrations The number of devices currently registered within the subzone. Note that devices cannot be
registered to the Traversal Subzone.
Calls The number of calls currently passing through the subzone. Note that a single call may pass
through more than one subzone, depending on the route it takes. For example, traversal calls from
a locally registered endpoint will always pass through the Traversal Subzone, so they will show up
twice; once in the originating subzone and once in the Traversal Subzone.
Bandwidth The total amount of bandwidth used by all calls passing through the subzone.
used
Zone Status
The Zone status page (Status > Zones) lists all of the external zones on the VCS. It shows the number of calls and
amount of bandwidth being used by each zone.
The list of zones always includes the Default Zone, plus any other zones that have been created.
Field Description
Name The names of each zone currently configured on this VCS.
Clicking on a zone Name takes you to the configuration page for that zone.
Type The type of zone.
Calls The number of calls currently passing out to or received in from each zone.
Bandwidth The total amount of bandwidth used by all calls passing out to or received in from each zone.
used
H.323 / SIP Indicates the zone's H.323 or SIP connection status:

status
Off: the protocol is disabled at either the zone or system level
Active: the protocol is enabled for that zone and it has at least one active connection; if
multiple connections are configured and some of those connections have failed, the display
indicates how many of the connections are Active
On: applies to DNS and ENUM zones only and indicates that the protocol is enabled for that
zone
Failed: the protocol is enabled for that zone but its connection has failed
Checking: the protocol is enabled for that zone and the system is currently trying to establish a
connection
Search This area is used to indicate if that zone is not a target of any search rules.
rule status
322
Bandwidth
Link Status
The Link status page (Status > Bandwidth > Links) lists all of the links currently configured on the VCS, along with
the number of calls and the bandwidth being used by each link.
Field Description
Name The name of each link. Clicking on a link Name takes you to the configuration page for that link.
Calls The total number of calls currently traversing the link. Note that a single call may traverse more than
one link, depending on how your system is configured.
Bandwidth The total bandwidth of all the calls currently traversing the link.
used
Pipe Status
The Pipe status page (Status > Bandwidth > Pipes) lists all of the pipes currently configured on the VCS, along with
the number of calls and the bandwidth being used by each pipe.
Field Description
Name The name of each pipe. Clicking on a pipe Name takes you to the configuration page for that pipe.
Calls The total number of calls currently traversing the pipe. Note that a single call may traverse more than
one pipe, depending on how your system is configured.
Bandwidth The total bandwidth of all the calls currently traversing the pipe.
used
Policy Server Status and Resiliency

You must specify a Status path when configuring the VCS's connection to a policy server. It identifies the path from
where the status of the remote service can be obtained. By default this is status.
Up to 3 different policy server addresses may be specified. The VCS polls each address on the specified path every 60
seconds to test the reachability of that address. The VCS accepts standard HTTP(S) response status codes. (Note
that the developers of the policy service must ensure that this provides the appropriate status of the service.)
If a server does not respond to status requests, VCS will deem that server's status to be in a failed state and it will not
be queried for policy service requests until it returns to an active state. Its availability will not be checked again until
after the 60 second polling interval has elapsed.
When the VCS needs to make a policy service request, it attempts to contact the service via one of the configured
server addresses. It will try each address in turn, starting with Server 1 address, and then if necessary - and if
configured - via the Server 2 address and then the Server 3 address. The VCS only tries to use a server address if it
is in an active state, based on its most recent status query.
The VCS has a non-configurable 30 seconds timeout value for each attempt it makes to contact a policy server.
However, if the server is not reachable, the connection failure will occur almost instantaneously. (Note that the TCP
connection timeout is usually 75 seconds. Therefore, in practice, a TCP connection timeout is unlikely to occur as
either the connection will be instantly unreachable or the 30 second request timeout will occur first.)
The VCS uses the configured Default CPL if it fails to contact the policy service via any of the configured addresses.
323
Note that this method provides resiliency but not load balancing i.e. all requests will be sent to Server 1 address,
providing that server address is functioning correctly.
Viewing Policy Server Status via the VCS

A summarized view of the status of the connection to each policy service can be viewed by going to the Policy
service status page (Status > Policy services).
The set of policy services includes all of the services defined on the Policy services page (Configuration > Dial plan
> Policy services), plus if a remote service has been selected for either Call Policy or for registration restriction policy
it will also display a Call Policy or a Registration restriction service respectively.
Field Description
Name The name of the policy service.
Clicking on a Name takes you to the configuration page for that service where you can change any of the
settings or see the details of any connection problems.
URL The address of the service. Note that each service can be configured with multiple server addresses for
resiliency. This field displays the server address currently selected for use by the VCS.
Status The current status of the service based on the last attempt to poll that server.
Last Indicates when the service was last requested by the VCS.
used
TURN Relay Usage

The TURN relay usage page (Status > TURN relay usage) provides a summary list of all the clients that are
connected to the TURN server.
Note that TURN services are available on VCS Expressway systems only; they are configured via Configuration >
Traversal > TURN.
Field Description
Client The IP address of the client that requested the relay.
Media destinations The address of destination system the media is being relayed to.
Connection protocol Indicates if the client is connected over TCP or UDP.
Relays Number of current relays being used by the client.
Viewing TURN relay details for a client connection

You can click on a specific client to see all of the relays and ports that it is using.
For each relay, its associated relay peer address/port is displayed. It also displays each relay's associated peer
address/port (the TURNserver relay port from which the media is being sent to the destination system). To see
specific statistics about a relay, click View to go to the TURN relay summary page.
TURN Relay Summary

The TURN relay summary page provides overview information about a particular relay, including a summary count of
the permissions, channels and requests associated with that relay.
324
To access this page, go to Status > TURN relay usage, then click View for a TURN client, and then View again for the
required relay.
Further detailed information about the relay can be viewed by using the links in the Related tasks section at the
bottom of the page. These let you:
View permissions for this relay: information about the permissions that have been defined on this relay.
View channels for this relay: information about the channel bindings that have been defined on this relay.
View counters for this relay: information about the number of TURN requests received, and the number of
TURN success or error responses sent. It also shows counts of the number of packets forwarded to and from
the client that allocated this relay.
Unified Communications Status

The Unified Communications status page (Status > Unified Communications) shows the current status of the
Unified Communications services including:
the number of configured Unified CM and IM&P servers (VCS Control only)
the current number of active provisioning sessions (VCS Control only)
the number of current calls
all the domains and zones that have been configured for Unified Communications services
statistics about SSOaccess requests and responses
If any configuration or connectivity problems are detected, appropriate messages are displayed with either links or
guidelines as to how to resolve the issue.
You can also view some advanced status information, including:
a list of all current and recent (shown in red) provisioning sessions (VCS Control only)
a list of the automatically-generated SSH tunnels servicing requests through the traversal zone
Checking SSOStatistics
The SSOStatistics page (Status > Unified Communications >View detailed SSOstatistics) shows a summary of the
requests and responses issued, as well as more detailed statistics about successful and unsuccessful attempts to
sign on.
If there are no instances of a particular type of request or response, there is no counter shown for that type.
Presence
Presence Publishers
The Publishers page (Status > Applications > Presence > Publishers) lists each presentity whose presence
information is being managed by (that is, published to) the local Presence Server.
All presentities are listed here regardless of whether or not anyone is requesting their presence information. If there
are no publishers listed, this could mean that the presence server is not enabled on this VCS.
Note: FindMe users are not listed here as they do not have their status individually published. The status of a FindMe
user is based on the published status of the endpoints and/or presentities that make up the FindMe user, and is
determined by the presentity manager.
URI
The address of the presentity whose presence information is being published.
325
Publisher count
The number of sources of information that are being published for this particular presentity. All endpoints that are
registered to the VCS have information published on their behalf by the PUA (as long as they are registered with an
alias in the form of a URI). If an endpoint supports presence, it may also publish its own presence information. This
means that some presentities have more than one source of information about their presence. It is the job of the
presentity manager to aggregate this information and determine the actual status of the presentity.
Presence Presentities
The Presentities page (Status > Applications > Presence > Presentities) lists each presentity whose presence
information is being managed by (that is, published to) the local Presence Server and whose presence information
has been requested by a subscriber. Presentities are listed here whether or not there is any information currently
available about that presentity. If a presentity has been subscribed to but there is no information being published
about it, then it will be listed here if the local presence server is authoritative for the presentitys domain.
Presentities are listed here regardless of whether the subscriber that requested the information is registered locally or
to a remote system.
Note: FindMe users are listed here if their presence information has been requested by a subscriber.
URI
The address of the presentity whose presence information has been requested.
Subscriber count
The number of endpoints who have requested information about that particular presentity.
To view the list of all subscribers who are requesting information about a particular presentity, click on the
presentitys URI.
Presence Subscribers
The Subscribers page (Status > Applications > Presence > Subscribers) lists each endpoint that has requested
information about one or more presentities whose information is managed by (that is, published to) the local Presence
Server.
Endpoints requesting this information are listed here regardless of whether they are registered locally or to a remote
server.
Note that FindMe users are not listed here as a FindMe entity cannot subscribe to presence information. However,
one or more of the endpoints that make up a FindMe user may be requesting presence information, in which case that
endpoint will be listed here.
URI
The address of the endpoint that has requested presence information.
Subscription count
The number of local presentities about whom this endpoint is requesting information.
To view the list of all local presentities whose information is being requested by a particular endpoint, click on the
endpoints URI.
Lync B2BUA
Lync User Status

The Lync user status page (Status > Applications > Lync users) lists and shows the current status of all the FindMe
IDs being handled by the Microsoft Lync B2BUA.
326
It applies to deployments that use both Lync clients and FindMe, if they both use the same SIP domain. To enable this
feature, Register FindMe users as clients on Lync must be set to Yes on the Microsoft Lync B2BUA configuration
page.
Field Description
URI The FindMe ID being handled by the B2BUA Presence Relay application.
Presence Shows the presence information currently being published for the FindMe ID.
state
Registration Indicates whether the FindMe ID has registered successfully with Lync. Doing so allows Lync to
state forward calls to the FindMe ID.
Note that Lync only allows FindMe users to register if the FindMe ID being registered is a valid user
in the Lync Active Directory (in the same way that Lync users can only register if they have a valid
account enabled in the Lync AD).
Subscription Indicates whether the B2BUA Presence Relay application has subscribed successfully to the
state FindMe ID's presence information. Doing so allows Lync clients to view the presence information of
FindMe users.
Peer The cluster peer that is registering the URI.
You can view further status information for each FindMe ID by clicking Edit in the Action column. This can help
diagnose registration or subscription failures.
Lync B2BUA Status

The Lync B2BUA status page (Status > Applications > Lync B2BUA) displays the status of the Microsoft Lync B2BUA
service.
The Microsoft Lync back-to-back user agent (B2BUA) on the VCS is used to route SIP calls between the VCS and a
Microsoft Lync Server.
The information shown includes:
the number of current calls passing through the Lync B2BUA

resource usage as a percentage of the number of allowed Lync B2BUA calls
TMS Provisioning Extension Service Status

The TMS Provisioning Extension service status page (Status > Applications > TMS Provisioning Extension
services > TMS Provisioning Extension service status) shows the status of each of the Cisco TMSPE services to
which the VCS is connected (or to which it is attempting to connect).
Summary details of each service are shown including:
the current status of the connection

when the most recent update of new data occurred
when the service was last polled for updates
the scheduled time of the next poll
Click View to display further details about a service, including:
additional connection status and configuration information, including troubleshooting information about any
connection failures
327
which VCS in the cluster has the actual connection to the Cisco TMSPE services (only displayed if the VCS is
part of a cluster)
details of each of the data tables provided by the service, including the revision number of the most recent
update, and the ability to View the records in those tables
You are recommended to use Cisco TMS to make any changes to the services' configuration settings, however you
can modify the current configuration for this VCS from the TMS Provisioning Extension services page (System >
TMS Provisioning Extension services).
See the Provisioning Server section for more information.
Provisioning Server Device Requests Status (Cisco TMSPE)

The Device requests status page (Status > Applications > TMS Provisioning Extension services > Device
requests) shows the status of the VCS Provisioning Server when using Cisco TMSPE.
The VCS Provisioning Server provides provisioning-related services to provisioned devices, using data supplied by
Cisco TMS through the Cisco TMS provisioning mechanism. The server only operates if the Device Provisioning
option key is installed.
Provisioning server
This section displays the server's status and summarizes the subscription requests received by the server since the
VCS was last restarted. It shows counts of:
the total number of subscription requests received

how many requests were sent a successful provisioning response
failed requests because the account requesting provisioning could not be found
failed requests because the account requesting provisioning had no provisioned devices associated with it
Model licenses
This section shows the status of the provisioning licenses that are available within your system. Information displayed
includes:
the total license limit and the number of licenses still available (free) for use
the number of licenses currently being used by devices that are registered to this VCS (or VCS cluster); this
information is broken down by the device types that can be provisioned by this VCS
License information is exchanged between Cisco TMS and VCS by the Cisco TMSPE Devices service. If the Devices
service is not active, the VCS's Provisioning Server will not be able to provision any devices.
The license limit and the number of free licenses indicate the overall number of licenses that are available to all of the
VCSs or VCS clusters that are being managed by Cisco TMS, hence the difference between the license limit and free
counts may not equal the sum of the number of used licenses shown for this particular VCS or VCS cluster
Phone book server
The phone book server provides phone book directory and lookup facilities to provisioned users.
This section displays the server's status and summarizes the number of phone book search requests received by the
server from provisioned users since the VCS was last restarted.
User Records Provided by Cisco TMSPE Services

You can view the data records provided by the Cisco TMSPE Users service by going to Status > Applications > TMS
Provisioning Extension services > Users > ... and then the relevant table:
328
Accounts
Groups
Templates
All the records in the chosen table are listed. Note that some tables can contain several thousand records and you
may experience a delay before the data is displayed.
Filtering the view
The Filter section lets you filter the set of records that are shown. It is displayed only if there is more than one page of
information to display. Status pages show 200 records per page.
Enter a text string or select a value with which to filter each relevant field, and then click Filter.
Only those records that match all of the selected filter options are shown. Note that text string filtering is case
insensitive.
Viewing more details and related records
You can click View to display further details about the selected record. Many views also allow you to click on related
information to see the data records associated with that item. For example, when viewing user groups, you can also
access the related user templates. When viewing user accounts you can check the data that would be provisioned to
that user by clicking Check provisioned data.
FindMe Records Provided by Cisco TMSPE Services

You can view the data records provided by the Cisco TMSPE FindMe service by going to Status > Applications > TMS
Provisioning Extension services > FindMe > ... and then the relevant table:
Accounts
Locations
Devices
Filtering the view
insensitive.
information to see the data records associated with that item. For example, when viewing a FindMe user, you can
also access the related location and device records.
Phone Book Records Provided by Cisco TMSPE Services

You can view the data records provided by the Cisco TMSPE Phone books service by going to Status > Applications
> TMS Provisioning Extension services > Phone book > ... and then the relevant table:
Folders
Entries
Contact methods
User access
329
Filtering the view
insensitive.
information to see the data records associated with that item. For example, when viewing a phone book entry, you
can also access the related contact method or folder.
Provisioned Devices
The Provisioned device status page (Status > Applications > TMS Provisioning Extension services > Provisioned
device status) displays a list of all of the devices that have submitted provisioning requests to the VCS's Provisioning
Server.
Filtering the view
insensitive.
The list shows all current and historically provisioned devices. A device appears in the list after it has made its first
provisioning request. The Active column indicates if the device is currently being provisioned (and is thus consuming
a provisioning license).
Checking Provisioned Data

The Check provisioned data page is used to check the configuration data that the VCS's Provisioning Server will
provision to a specific user and device combination.
You can get to this page only through the User accounts status page (Status > Applications > TMS Provisioning
Extension services > Users > Accounts, locate the user you want to check and then click Check provisioned data).
To check provisioned data:
1. Verify that the User account name is displaying the name of the user account you want to check.
2. Select the Model and Version of the user's endpoint device.
If the actual Version used by the endpoint is not listed, select the nearest earlier version.
3. Click Check provisioned data.
The Results section will show the data that would be provisioned out to that user and device combination.
Starter Pack Provisioning Server Status

The Starter Pack status page (Status > Applications > Starter Pack > Starter Pack status) shows the status of the
VCS's Provisioning Server when running as a Starter Pack.
The Starter Pack Provisioning Server provides basic provisioning-related services to provisioned devices, without the
need for Cisco TMS.
330
Provisioning server
This section displays the server's status and summarizes the subscription requests received by the server since the
VCS was last restarted. It shows counts of:
the total number of subscription requests received

how many requests were sent a successful provisioning response
failed requests because the account requesting provisioning could not be found
failed requests because the account requesting provisioning had no provisioned devices associated with it
Model licenses
This section shows the number of licenses currently being used by devices that are registered to this VCS. This
information is broken down by the device types that can be provisioned by this VCS.
Phone book server
The phone book server provides phone book directory and lookup facilities to provisioned users.
This section displays the server's status and summarizes the number of phone book search requests received by the
server from provisioned users since the VCS was last restarted.
Managing Alarms
Alarms occur when an event or configuration change has taken place on the VCS that requires some manual
administrator intervention, such as a restart. Alarms may also be raised for hardware and environmental issues such
as faulty disks and fans or high temperatures.
The Alarms page (Status > Alarms) provides a list of all the alarms currently in place on your system (and, where
applicable, their proposed resolution). When there are unacknowledged alarms in place on the VCS, an alarm icon
appears at the top right of all pages. You can also access the Alarms page by clicking on the alarm icon.
Each alarm is identified by a 5-digit Alarm ID, shown in the rightmost column in the alarms list. The alarms are
grouped into categories as follows:
Alarm ID prefix Category
10nnn Hardware issues
15nnn Software issues
20nnn Cluster-related issues
25nnn Network and network services settings
30nnn Licensing / resources / option keys
35nnn External applications and services (such as policy services or LDAP/AD configuration)
40nnn Security issues (such as certificates, passwords or insecure configuration)
45nnn General VCS configuration issues
55nnn B2BUA issues
6nnnn Hybrid Services issues
All alarms raised on the VCS are also raised as Cisco TMS tickets. All the attributes of an alarm (its ID, severity and so
on) are included in the information sent to Cisco TMS.
Alarms are dealt with by clicking each Action hyperlink and making the necessary configuration changes to resolve
the problem.
331
Acknowledging an alarm (by selecting an alarm and clicking on the Acknowledge button) removes the alarm icon
from the web UI, but the alarm will still be listed on the Alarms page with a status of Acknowledged. If a new alarm
occurs, the alarm icon will reappear.
You cannot delete alarms from the Alarms page. Alarms are removed by the VCS only after the required action
or configuration change has been made.
After a restart of the VCS, any Acknowledged alarms that are still in place on the VCS will reappear with a
status of New, and must be re-acknowledged.
The display indicates when the alarm was first and last raised since the VCS was last restarted.
If your VCS is a part of a cluster, the Alarms page shows all of the alarms raised by any of the cluster peers.
However, you can acknowledge only those alarms that have been raised by the "current" peer (the peer to
which you are currently logged in to as an administrator).
You can click the Alarm ID to generate a filtered view of the Event Log, showing all occurrences of when that
alarm has been raised and lowered.
See the alarms list for further information about the specific alarms that can be raised.
Logs
Event Log
The Event Log page (Status > Logs > Event Log) lets you view and search the Event Log, which is a list of the events
that have occurred on your system since the last upgrade.
The Event Log holds a maximum of 2GB of data; when this size is reached, the oldest entries are overwritten.
However, only the first 50MB of Event Log data can be displayed through the web interface.
Filtering the Event Log
The Filter section lets you filter the Event Log. It is displayed only if there is more than one page of information to
display. Log pages show 1000 records per page.
Enter the words you want to search for and click Filter.Only those events that contain all the words you entered are
shown.
To do more advanced filtering, click more options. This gives you additional filtering methods:
Contains the string: only includes events containing the exact phrase entered here.
Contains any of the words: includes any events that contain at least one of the words entered here.
Not containing any of the words: filters out any events containing any of the words entered here.
Note: use spaces to separate each word you want to filter by.
Click Filter to reapply any modified filter conditions. To return to the complete log listing, click Reset.
Reconfiguring the log settings
Clicking Configure the log settings takes you to the Logging configuration page. From this page, you can set the
level of events that are recorded in the Event Log, and also set up a remote server to which the Event Log can be
copied.
Saving the results to a local disk
Click Download this page if you want to download the contents of the results section to a text file on your local PC or
server.
Results section
The Results section shows all the events matching the current filter conditions, with the most recent being shown
first.
332
Most tvcs events contain hyperlinks in one or more of the fields (such fields change color when you hover over them).
You can click on the hyperlink to show only those events that contain the same text string. For example, clicking on
the text that appears after Event= filters the list to show all the events of that particular type. Likewise, clicking on a
particular Call-Id shows just those events that contain a reference to that particular call.
Event Log color coding
Certain events in the Event Log are color-coded so that you can identify them more easily. These events are as
follows:
Green events:
System Start
Admin Session Start/Finish
Installation of <item> succeeded
Registration Accepted
Call Connected
Request Successful
Beginning System Restore
Completed System Restore
Orange events:
System Shutdown
Intrusion Protection Unblocking
Purple events:
Diagnostic Logging
Red events:
Registration Rejected
Registration Refresh Rejected
Call Rejected
Security Alert
License Limit Reached
Decode Error
TLS Negotiation Error
External Server Communications Failure
Application Failed
Request Failed
System Backup Error
System Restore Error
Authorization Failure
Intrusion Protection Blocking
For more information about the format and content of the Event Log see Event Log Format, page 338 and Events and
Levels, page 341.
333
Configuration Log
The Configuration Log page (Status > Logs > Configuration Log) provides a list of all changes to the VCS
configuration.
The Configuration Log holds a maximum of 30MB of data; when this size is reached, the oldest entries are
overwritten. The entire Configuration Log can be displayed through the web interface.
Filtering the Configuration Log
The Filter section lets you filter the Configuration Log. It is displayed only if there is more than one page of information
to display. Log pages show 1000 records per page.
shown.
Results section
The Results section shows all the web-based events, with the most recent being shown first.
Most events contain hyperlinks in one or more of the fields (such fields change color when you hover over them). You
can click on the hyperlink to show only those events that contain the same text string. For example, clicking on the
text that appears after Event= filters the list to show all the events of that particular type. Likewise, clicking on a
particular user shows just those events relating to that particular administrator account.
All events that appear in the Configuration Log are recorded as Level 1 Events, so any changes to the logging levels
will not affect their presence in the Configuration Log.
Configuration Log events
Changes to the VCS configuration made by administrators using the web interface have an Event field of System
Configuration Changed.
The Detail field of each of these events shows:
the configuration item that was affected

what it was changed from and to
the name of the administrator user who made the change, and their IP address
the date and time that the change was made
Network Log
The Network Log page (Status > Logs > Network Log) provides a list of the call signaling messages that have been
logged on this VCS.
The Network Log holds a maximum of 2GB of data; when this size is reached, the oldest entries are overwritten.
However, only the first 50MB of Network Log data can be displayed through the web interface.
Filtering the Network Log
The Filter section lets you filter the Network Log. It is displayed only if there is more than one page of information to
display. Log pages show 1000 records per page.
334
shown.
Reconfiguring the log settings
Clicking Configure the log settings takes you to the Network Log configuration page. From this page, you can set the
level of events that are recorded in the Network Log.
Saving the results to a local disk
Click Download this page if you want to download the contents of the results section to a text file on your local PC or
server.
Results Section
The Results section shows the events logged by each of the Network Log modules.
Most events contain hyperlinks in one or more of the fields (such fields change color when you hover over them). You
can click on the hyperlink to show only those events that contain the same text string. For example, clicking on the
text that appears after Module= filters the list to show all the events of that particular type.
The events that appear in the Network Log are dependent on the log levels configured on the Network Log
configuration page.
Hardware Status
The Hardware page (Status > Hardware) provides information about the physical status of your VCS appliance.
Information displayed includes:
fan speeds
component temperatures
component voltages
Any appropriate minimum or maximum levels are shown to help identify any components operating outside of their
standard limits.
Warning: do not attempt to service the apparatus yourself as opening or removing covers may expose you to
dangerous voltages or other hazards, and will void the warranty. Refer all servicing to qualified service personnel.
Note that hardware status information is not displayed if the VCS is running on VMware.
335
Reference Material
This section provides supplementary information about the features and administration of the VCS.
Performance Capabilities 336

About Event Log Levels 338
CPL Reference 347
LDAP Server Configuration for Device Authentication 357
DNS Configuration Examples 362
Changing the Default SSH Key 363
Restoring Default Configuration (Factory Reset) 363
Password Encryption 365
Pattern Matching Variables 366
Port Reference 367
Mobile and Remote Access Port Reference 372
Microsoft Lync B2BUA Port Reference 374
Device Authentication Port Reference 376
Regular expressions 378
Supported Characters 380
Call Types and Licensing 381
Alarms 383
Command Reference xConfiguration 400
Command Reference xCommand 459
Command Reference xStatus 483
External Policy Overview 484
Flash Status Word Reference Table 488
Supported RFCs 488
Software Version History 491
Related Documentation 514
Legal Notices 517
Performance Capabilities
The performance capabilities of VCSX8.7 software are summarized below. In all cases, note that:
You can cluster up to 6 VCSs to increase capacity. This offers N+1 redundancy, because the maximum
capacity of a cluster is 4 times the physical limit of a single VCS.
Logging is at default levels.
336
Performance capacity will be reduced by features such as presence, provisioning, TURN relay services,
RDPtranscoding, and by configuring large numbers of zones and search rules.
VM hardware requires a minimum of 6GBRAM.
The VCS supports up to 500 concurrent searches.
CE1000 appliances, or Large VM servers (minimum 8 cores with 2 x 10Gb NIC), or CE1100 appliances with 10
Gbps NICs
Supports the following set of concurrent calls and registrations:
500 encrypted traversal calls @ 768kbps or 1000 encrypted SIP audio traversal calls @ 64kbps; and
500 non-traversal calls; and
5000 registrations
This assumes a maximum sustained call rate of 10 calls per second.
CE500 or legacy appliances, or Small/Medium VM servers (2 cores and 1GbNIC), or CE1100 appliances with 1
Gbps NICs
Supports the following set of concurrent calls and registrations:
100 encrypted traversal calls @ 768kbps or 200 encrypted SIPaudio-only traversal calls @ 64 kbps; and
500 non-traversal calls; and
2500 registrations
This assumes a maximum sustained call rate of 5 calls per second.
337
About Event Log Levels

All events have an associated level in the range 1-4, with Level 1 Events considered the most important. The table
below gives an overview of the levels assigned to different events.
Level Assigned events
1 High-level events such as registration requests and call attempts. Easily human readable. For example:
call attempt/connected/disconnected
registration attempt/accepted/rejected
2 All Level 1 events, plus:
logs of protocol messages sent and received (SIP, H.323, LDAP and so on) excluding noisy
messages such as H.460.18 keepalives and H.245 video fast-updates
3 All Level 1 and Level 2 events, plus:
protocol keepalives
call-related SIP signaling messages
4 The most verbose level: all Level 1, Level 2 and Level 3 events, plus:
network level SIP messages
See the Events and levels section for a complete list of all events that are logged by the VCS, and the level at which
they are logged.
Event Log Format

The Event Log is displayed in an extension of the UNIX syslog format:
date time process_name: message_details
where:
Field Description
date The local date on which the message was logged.
time The local time at which the message was logged.
process_name The name of the program generating the log message. This could include:
tvcs for all messages originating from VCS processes

web for all web login and configuration events
licensemanager for messages originating from the call license manager
provisioning for provisioning server events
b2bua for B2BUA events
presencerelay for B2BUA Presence Relay application events
portforwarding for internal communications between the VCS Control and the VCS
Expressway
ssh for ssh tunnels between the VCS Control and the VCS Expressway
but will differ for messages from other applications running on the VCS.
message_details The body of the message (see the Message details field section for further information).
338
Administrator and FindMe User Events

Administrator session related events are:
Admin Session Start

Admin Session Finish
Admin Session Login Failure
FindMe user session related events are:
User Session Start

User Session Finish
User Session Login Failure
For both administrator and FindMe user related events, the Detail field includes:
the name of the administrator or FindMe user to whom the session relates, and their IP address
the date and time that the login was attempted, started, or ended
Message Details Field

For all messages logged from the tvcs process, the message_details field, which contains the body of the message,
consists of a number of human-readable name=value pairs, separated by a space.
The first name element within the message_details field is always Event and the last name element is always Level.
The table below shows all the possible name elements within the message_details field, in the order that they would
normally appear, along with a description of each.
Note: in addition to the events described below, a syslog.info event containing the string MARK is logged after each
hour of inactivity to provide confirmation that logging is still active.
Name Description
Event The event which caused the log message to be generated. See Events and levels for a list of all events
that are logged by the VCS, and the level at which they are logged.
User The username that was entered when a login attempt was made.
ipaddr The source IP address of the user who has logged in.
Protocol Specifies which protocol was used for the communication. Valid values are:
TCP
UDP
TLS
Reason Textual string containing any reason information associated with the event.
339
Name Description
Service Specifies which protocol was used for the communication. Will be one of:
H323
SIP
H.225
H.245
LDAP
Q.931
NeighbourGatekeeper
Clustering
ConferenceFactory
Message Specifies the type of the message.

Type
Response- SIP response code or, for H.323 and interworked calls, a SIP equivalent response code.
code
Src-ip Source IP address (the IP address of the device attempting to establish communications). This can be
an IPv4 address or an IPv6 address.
Dst-ip Destination IP address (the IP address of the destination for a communication attempt). The
destination IP is recorded in the same format as Src-ip.
Src-port Source port: the IP port of the device attempting to establish communications.
Dst-port Destination port: the IP port of the destination for a communication attempt.
Src-alias If present, the first H.323 alias associated with the originator of the message.
If present, the first E.164 alias associated with the originator of the message.
Dst-alias If present, the first H.323 alias associated with the recipient of the message.
If present, the first E.164 alias associated with the recipient of the message.
Detail Descriptive detail of the Event.
Auth Whether the call attempt has been authenticated successfully.
Method SIP method (INVITE, BYE, UPDATE, REGISTER, SUBSCRIBE, etc).
Contact Contact: header from REGISTER.
AOR Address of record.
Call-id The Call-ID header field uniquely identifies a particular invitation or all registrations of a particular
client.
Call- The local Call Serial Number that is common to all protocol messages for a particular call.
serial-
number
Tag The Tag is common to all searches and protocol messages across a VCS network for all forks of a call.
Call- Indicates if the VCS took the signaling for the call.
routed
340
Name Description
To for REGISTER requests: the AOR for the REGISTER request

for INVITEs: the original alias that was dialed
for all other SIP messages: the AOR of the destination.
Request- The SIP or SIPS URI indicating the user or service to which this request is being addressed.
URI
Num- The number of bytes sent/received in the message.

bytes
Protocol- Shows the data contained in the buffer when a message could not be decoded.
buffer
Duration Request/granted registration expiry duration.
Time A full UTC timestamp in YYYY/MM/DD-HH:MM:SS format. Using this format permits simple ASCII text
sorting/ordering to naturally sort by time. This is included due to the limitations of standard syslog
timestamps.
Level The level of the event as defined in the About Event Log levels section.
UTCTime Time the event occurred, shown in UTC format.
Events and Levels

The following table lists the events that can appear in the Event Log.
Event Description Level
Alarm An administrator has acknowledged an alarm. The Detail event parameter provides 1
acknowledged information about the nature of the issue.
Alarm lowered The issue that caused an alarm to be raised has been resolved. The Detail event 1
parameter provides information about the nature of the issue.
Alarm raised The VCS has detected an issue and raised an alarm. The Detail event parameter provides 1
information about the nature of the issue.
Admin Session An unsuccessful attempt has been made to log in when the VCS is configured to use 1
CBA certificate-based authentication.
Authorization
Failure
Admin Session An administrator has logged off the system. 1

Finish
Admin Session An unsuccessful attempt has been made to log in as an administrator. This could be 1
Login Failure because an incorrect username or password (or both) was entered.
Admin Session An administrator has logged onto the system. 1

Start
Application Exit The VCS application has been exited. Further information may be provided in the Detail 1
event parameter.
Application The VCS application is out of service due to an unexpected failure. 1

Failed
341
Application The VCS has started. Further detail may be provided in the Detail event parameter. 1
Start
Application The VCS application is still running but has experienced a recoverable problem. Further 1
Warning detail may be provided in the Detail event parameter.
Authorization The user has either entered invalid credentials, does not belong to an access group, or 1
Failure belongs to a group that has an access level of "None". Applies when remote
authentication is enabled.
Beginning A system backup has started. 1

System Backup
Beginning A system restore has started. 1

System Restore
Call Answer An attempt to answer a call has been made. 1

Attempted
Call Attempted A call has been attempted. 1
Call Bandwidth The endpoints in a call have renegotiated call bandwidth. 1

Changed
Call Connected A call has been connected. 1
Call Diverted A call has been diverted. 1
Call A call has been disconnected. 1

Disconnected
Call Inactivity A call has been disconnected due to inactivity. 1

Timer
Call Rejected A call has been rejected. The Reason event parameter contains a textual representation 1
of the H.225 additional cause code.
Call Rerouted The VCS has Call signaling optimization set to On and has removed itself from the call 1
signaling path.
CBA An attempt to log in using certificate-based authentication has been rejected due to 1
Authorization authorization failure.
Failure
Certificate Indicates that security certificates have been uploaded. See the Detail event parameter 1
Management for more information.
Completed A system backup has completed. 1

System Backup
Completed A system restore has completed. 1

System restore
Configlog An operator cleared the Configuration Log. 1

Cleared
Decode Error A syntax error was encountered when decoding a SIP or H.323 message. 1
Diagnostic Indicates that diagnostic logging is in progress. The Detail event parameter provides 1
Logging additional details.
342
Error Response The TURN server has sent an error message to a client (using STUN protocol). 3
Sent
Eventlog An operator cleared the Event Log. 1

Cleared
External Server Communication with an external server failed unexpectedly. The Detail event parameter 1
Communication should differentiate between "no response" and "request rejected". Servers concerned
Failure are:
DNS
LDAP servers
Neighbor Gatekeeper
NTP servers
Peers
FindMe Search A search of the FindMe database has failed, for example due to no alias being provided. 1
Failed
Hardware There is an issue with the VCS hardware. If the problem persists, contact your Cisco 1
Failure support representative.
License Limit Licensing limits for a given feature have been reached. The Detail event parameter 1
Reached specifies the facility/limits concerned. Possible values for the detail field are:
Non Traversal Call Limit Reached

Traversal Call Limit Reached
If this occurs frequently, you may want to contact your Cisco representative to purchase
more licenses.
Message An incoming RAS message has been received. 2

Received
Message An incoming RAS NSM Keepalive, H.225, H.245 or a RAS message between peers has 3
Received been received.
Message (SIP) An incoming message has been received. 4

Received
Message This could be for one of two reasons: 1

Rejected
If authentication is enabled and an endpoint has unsuccessfully attempted to send
a message (such as a registration request) to the VCS. This could be either
because the endpoint has not supplied any authentication credentials, or because
its credentials do not match those expected by the VCS.
Clustering is enabled but bandwidth across the cluster has not been configured
identically, and the VCS has received a message relating to an unknown peer, link,
pipe, subzone or zone.
Message Sent An outgoing RAS message has been sent. 2
Message Sent An outgoing RAS NSM Keepalive, H.225, H.245 or a RAS message between peers has 3
been sent.
Message Sent (SIP) An outgoing message has been sent. 4
343
Operator Call An administrator has disconnected a call. 1

Disconnect
Outbound TLS The VCS is unable to communicate with another system over TLS. The event parameters 1
Negotiation provide more information.
Error
Package Install A package, for example a language pack, has been installed or removed. 2
Policy Change A policy file has been updated. 1
POST request A HTTP POST request was submitted from an unauthorized session. 1
failed
Provisioning Diagnostic messages from the provisioning server. The Detail event parameter provides 1
additional information.
Reboot A system reboot has been requested. The Reason event parameter provides specific 1
Requested information.
Registration A registration request has been accepted. 1

Accepted
Registration A request to refresh or keep a registration alive has been accepted. 3

Refresh
Accepted
Registration A request to refresh a registration has been rejected. 1

Refresh
Rejected
Registration A request to refresh or keep a registration alive has been received. 3

Refresh
Requested
Registration A registration request has been rejected. The Reason and Detail event parameters 1
Rejected provide more information about the nature of the rejection.
Registration A registration has been removed by the VCS. The Reason event parameter specifies the 1
Removed reason why the registration was removed. This is one of:
Authentication change
Conflicting zones
Operator forced removal
Operator forced removal (all registrations removed)
Registration superseded.
Registration A registration has been requested. 1

Requested
Relay Allocated A TURN server relay has been allocated. 2
Relay Deleted A TURN server relay has been deleted. 2
Relay Expired A TURN server relay has expired. 2
Request Failed A request sent to the Conference Factory has failed. 1
Request A call-related SIP request has been received. 2

Received
344
Request A non-call-related SIP request has been received. 3

Received
Request Sent A call-related SIP request has been sent. 2
Request Sent A non-call-related SIP request has been sent. 3
Request A successful request was sent to the Conference Factory. 1

Successful
Response A call-related SIP response has been received. 2

Received
Response A non-call-related SIP response has been received. 3

Received
Response Sent A call-related SIP response has been sent. 2
Response Sent A non-call-related SIP response has been sent. 3
Restart A system restart has been requested. The Reason event parameter provides specific 1
Requested information.
Search A search has been attempted. 1

Attempted
Search A search has been cancelled. 1

Cancelled
Search A search has been completed. 1

Completed
Search Loop The VCS is in Call loop detection mode and has identified and terminated a looped 2
detected branch of a search.
Secure mode The VCS has successfully exited Advanced account security mode. 1
disabled
Secure mode The VCS has successfully entered Advanced account security mode. 1
enabled
Security Alert A potential security-related attack on the VCS has been detected. 1
Source Aliases A source alias has been changed to indicate the caller's FindMe ID. 1
Rewritten
Success The TURN server has sent a success message to a client (using STUN protocol). 3
Response Sent
System backup The system backup process has completed. 1

completed
System Backup An error occurred while attempting a system backup. 1

error
System backup The system backup process has started. 1

started
System An item of configuration on the system has changed. The Detail event parameter contains 1
Configuration the name of the changed configuration item and its new value.
Changed
345
System restore The system restore process has completed. 1

completed
System restore System restore process has started backing up the current configuration 1
backing up
current config
System restore System restore process has completed backing up the current configuration 1
backup of
current config
completed
System restore An error occurred while attempting a system restore. 1

error
System restore The system restore process has started. 1

started
System The operating system was shutdown. 1

Shutdown
System A system snapshot has been initiated. 1

snapshot
started
System A system snapshot has completed. 1

snapshot
completed
System Start The operating system has started. The Detail event parameter may contain additional 1
information if there are startup problems.
TLS Transport Layer Security (TLS) connection failed to negotiate. 1

Negotiation
Error
Unregistration An unregistration request has been accepted. 1

Accepted
Unregistration An unregistration request has been rejected. 1

Rejected
Unregistration An unregistration request has been received. 1

Requested
Upgrade Messages related to the software upgrade process. The Detail event parameter provides 1
specific information.
User session A FindMe user has logged out of the system. 1

finish
User session An unsuccessful attempt has been made to log in as a FindMe user. This could be 1
Login failure because either an incorrect username or password (or both) was entered.
User session A FindMe user has logged on to the system. 1

start
346
CPL Reference
Call Processing Language (CPL) is an XML-based language for defining call handling. This section gives details of
the VCSs implementation of the CPL language and should be read in conjunction with the CPL standard RFC 3880.
The VCS has many powerful inbuilt transform features so CPL should be required only if advanced call handling rules
are required.
The VCS supports most of the CPL standard along with some TANDBERG-defined extensions. It does not support the
top level actions <incoming> and <outgoing> as described in RFC 3880. Instead it supports a single section of CPL
within a <taa:routed> section.
When Call Policy is implemented by uploading a CPL script to the VCS, the script is checked against an XML schema
to verify the syntax. There are two schemas - one for the basic CPL specification and one for the TANDBERG
extensions. Both of these schemas can be downloaded from the web interface and used to validate your script before
uploading to the VCS.
The following example shows the correct use of namespaces to make the syntax acceptable:
<?xml version="1.0" encoding="UTF-8" ?>
<cpl xmlns="urn:ietf:params:xml:ns:cpl"
xmlns:taa="http://www.tandberg.net/cpl-extensions"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:cpl cpl.xsd">
<taa:routed>
<address-switch field="destination">
<address is="[email protected]">
<proxy/>
</address>
</address-switch>
</taa:routed>
</cpl>
Source and destination address formats

When the descriptions in this section refer to the source or destination aliases of a call, this means all supported
address formats (URIs, IP addresses, E.164 aliases and so on).
CPL Address-Switch Node

The address-switch node allows the script to run different actions based on the source or destination aliases of the
call. It specifies which fields to match, and then a list of address nodes contains the possible matches and their
associated actions.
The address-switch has two node parameters: field and subfield.
Address
The address construct is used within an address-switch to specify addresses to match. It supports the use of regular
expressions.
Valid values are:
is=string Selected field and subfield exactly match the given string.
contains=string Selected field and subfield contain the given string. Note that the CPL standard only allows for
this matching on the display subfield; however the VCS allows it on any type of field.
subdomain- If the selected field is numeric (for example, the tel subfield) then this matches as a prefix; so
of=string address subdomain-of="555" matches 5556734 and so on. If the field is not numeric then normal
domain name matching is applied; so
address subdomain-of="company.com" matches nodeA.company.com and so on.
347
regex="regular Selected field and subfield match the given regular expression.
expression"
All address comparisons ignore upper/lower case differences so address is="Fred" will also match fred, freD and so
on.
Field
Within the address-switch node, the mandatory field parameter specifies which address is to be considered. The
supported attributes and their interpretation are shown below:
Field parameter SIP H.323

attributes
unauthenticated- The "From" and "ReplyTo" fields The source aliases from the original LRQ or ARQ that
origin of the incoming message. started the call. If a SETUP is received without a preceding
RAS message then the origin is taken from the SETUP.
authenticated- The "From" and "ReplyTo" fields The source aliases from the original LRQ or ARQ that
origin of the message if it authenticated started the call if it authenticated correctly (or where the
correctly (or where the relevant relevant AuthenticationPolicy is Treat as authenticated)
and AuthenticationPolicy is Treat as otherwise not-present. Because SETUP messages are not
authenticated), otherwise not- authenticated, if the VCS receives a SETUP without a
origin
present. preceding RAS message the origin will always be not-
present.
originating-zone The name of the zone or subzone for the originating leg of the call. If the call originates from a
neighbor, traversal server or traversal client zone then this will equate to the zone name. If it
comes from an endpoint within one of the local subzones this will be the name of the subzone.
If the call originates from any other locally registered endpoint this will be "DefaultSubZone". In
all other cases this will be "DefaultZone".
originating-user If the relevant AuthenticationPolicy is Check credentials or Treat as authenticated this is the
username used for authentication, otherwise not-present.
registered- If the call originates from a registered endpoint this is the list of all aliases it has registered,
origin otherwise not-present.
destination The destination aliases.
original- The destination aliases.
destination
Note that any Authentication Policy settings that apply are those configured for the relevant zone or subzone
according to the source of the incoming message.
If the selected field contains multiple aliases then the VCS will attempt to match each address node with all of the
aliases before proceeding to the next address node, that is, an address node matches if it matches any alias.
Subfield
Within the address-switch node, the optional subfield parameter specifies which part of the address is to be
considered. The following table gives the definition of subfields for each alias type.
If a subfield is not specified for the alias type being matched then the not-present action is taken.
address- Either h323 or sip, based on the type of endpoint that originated the call.
type
user For URI aliases this selects the username part. For H.323 IDs it is the entire ID and for E.164 numbers it is
the entire number.
348
host For URI aliases this selects the domain name part. If the alias is an IP address then this subfield is the
complete address in dotted decimal form.
tel For E.164 numbers this selects the entire string of digits.
alias- Gives a string representation of the type of alias. The type is inferred from the format of the alias.
type Possible types are:
Address Type
Result
URI
url-ID
H.323 ID
h323-ID
Dialed Digits
dialedDigits
Otherwise
The otherwise node is executed if the address specified in the address-switch was found but none of the preceding
address nodes matched.
Not-Present
The not-present node is executed when the address specified in the address-switch was not present in the call setup
message. This form is most useful when authentication is being used. With authentication enabled the VCS will only
use authenticated aliases when running policy so the not-present action can be used to take appropriate action
when a call is received from an unauthenticated user (see the example Call screening of authenticated users).
Location
As the CPL script is evaluated it maintains a list of addresses (H.323 IDs, URLs and E.164 numbers) which are used as
the destination of the call if a proxy node is executed. The taa:location node allows the location set to be modified so
that calls can be redirected to different destinations.
At the start of script execution the location set is initialized to the original destination.
The following attributes are supported on taa:location nodes. It supports the use of regular expressions.
Clear = "yes" | Specifies whether to clear the current location set before adding the new location. The
"no" default is to append this location to the end of the set.
url=string The new location to be added to the location set. The given string can specify a URL (for
example, [email protected]), H.323 ID or an E.164 number.
priority=<0.0..1.0> Specified either as a floating point number in the range 0.0 to 1.0, or random, which assigns a
| "random" random number within the same range. 1.0 is the highest priority. Locations with the same
priority are searched in parallel.
regex="<regular Specifies the way in which a location matching the regular expression is to be changed.
expression>"
replace="<string>"
source-url-for- Replaces the From header (source alias) with the specified string. Note that this will override
message="<string>" any User Policy that may have been applied.
349
source-url-for- Replaces any From header (source alias) that matches the regular expression with the
message- specified replacement string. If there are multiple From headers (applies to H.323 only) then
regex="<regular any From headers that do not match are left unchanged. Note that this will override any User
expression>" Policy that may have been applied.
together with
source-url-for-
message-
replace="<string>"
If the source URL of a From header is modified, any corresponding display name is also modified to match the
username part of the modified source URL.
Rule-Switch
This extension to CPL is provided to simplify Call Policy scripts that need to make decisions based on both the source
and destination of the call. A taa:rule-switch can contain any number of rules that are tested in sequence; as soon
as a match is found the CPL within that rule element is executed.
Each rule must take one of the following forms:
<taa:rule-switch>
<taa:rule origin="<regular expression>" destination="<regular expression>" message-regex="<regular
expression>">
<taa:rule authenticated-origin="<regular expression>" destination="<regular expression>" message-
regex="<regular expression>">
<taa:rule unauthenticated-origin="<regular expression>" destination="<regular expression>" message-
<taa:rule registered-origin="<regular expression>" destination="<regular expression>" message-
<taa:rule originating-user="<regular expression>" destination="<regular expression>" message-
<taa:rule originating-zone="<regular expression>" destination="<regular expression>" message-
</taa:rule-switch>
The meaning of the various origin selectors is as described in the field section.
The message-regex parameter allows a regular expression to be matched against the entire incoming SIP message.
Note that any rule containing a message-regex parameter will never match an H.323 call.
Proxy
On executing a proxy node the VCS attempts to forward the call to the locations specified in the current location set.
If multiple entries are in the location set then this results in a forked call. If the current location set is empty the call is
forwarded to its original destination.
The proxy node supports the following optional parameters:
timeout=<1..86400> Timeout duration, specified in seconds

stop-on-busy = "yes" | "no" Whether to stop searching if a busy response is received
The proxy action can lead to the results shown in the table below.
failure The proxy failed to route the call

busy Destination is found but is busy
noanswer Destination is found but does not answer
350
redirection VCS is asked to redirect the call

default CPL to run if the other results do not apply
The CPL can perform further actions based on these results. Any results nodes must be contained within the proxy
node. For example:
<proxy timeout="10">
<busy>

<location clear="yes" url="recorder">
<proxy/>
</location>
</busy>
</proxy>
Reject
If a reject node is executed the VCS stops any further script processing and rejects the current call.
The custom reject strings status=string and reason=string options are supported here and should be used together
to ensure consistency of the strings.
Unsupported CPL Elements

The VCS does not currently support some elements that are described in the CPL RFC. If an attempt is made to
upload a script containing any of the following elements an error message will be generated and the VCS will
continue to use its existing policy.
The following elements are not currently supported:
time-switch
string-switch
language-switch
priority-switch
redirect
mail
log
subaction
lookup
remove-location
CPL Examples
This section provides a selection of CPL examples:
Call screening of authenticated users

Call screening based on alias
Call screening based on domain
Allow calls from locally registered endpoints only
Block calls from Default Zone and Default Subzone
Restricting access to a local gateway
Redirecting failed calls based on status code
Reject attempts to subscribe to a presentity
351
CPL Example: Call Screening of Authenticated Users
Note:You can configure this behavior using Call Policy Rules, so you don't need to do it using a CPLscript. However,
you cannot use a combination of UIconfigured rules and uploaded CPLscript, so if you have any CPLrequirements
that you cannot implement using the UI rules, you must use a script for all of your rules. See About Call Policy, page
192.
In this example, only calls from users with authenticated source addresses are allowed. See About Device
Authentication, page 108 for details on how to enable authentication.
If calls are coming in through VCS Expressway, then we recommend screening on the VCS Expressway to prevent
unwelcome calls from progressing into the network.
<taa:routed>
<address-switch field="authenticated-origin">
<not-present>

<reject status="403" reason="Denied by policy"/>
</not-present>
</address-switch>
</taa:routed>
</cpl>
CPL Example: Call Screening Based on Alias
192.
In this example, user ceo will only accept calls from users vpsales, vpmarketing or vpengineering.
<taa:routed>
<address is="ceo">
<address-switch field="authenticated-origin">
<address regex="vpsales|vpmarketing|vpengineering">

<proxy/>
</address>
<not-present>

</not-present>
<otherwise>
</otherwise>
</address-switch>
</address>
352
</address-switch>
</taa:routed>
</cpl>
CPL Example: Call Screening Based on Domain
192.
In this example, user fred will not accept calls from anyone at annoying.com, or from any unauthenticated users. All
other users will allow any calls.
<taa:routed>
<address is="fred">
<address-switch field="authenticated-origin" subfield="host">
<address subdomain-of="annoying.com">

</address>
<not-present>

</not-present>
<otherwise>

<proxy/>
</otherwise>
</address-switch>
</address>
</address-switch>
</taa:routed>
</cpl>
CPL Example: Allow Calls From Locally Registered Endpoints Only

In this example, the administrator only wants to allow calls that originate from locally registered endpoints.
<taa:routed>
<address-switch field="registered-origin">
<not-present>
<reject status="403" reason="Only local endpoints can use this VCS"/>
</not-present>
</address-switch>
</taa:routed>
</cpl>
353
CPL Example: Block Calls From Default Zone and Default Subzone
192.
The script to allow calls from locally registered endpoints only can be extended to also allow calls from configured
zones but not from the Default Zone or Default Subzone.
<taa:routed>
<address-switch field="registered-origin">
<not-present>
<address-switch field="originating-zone">
<address is="DefaultZone">
</address>
<address is="DefaultSubZone">
</address>
<otherwise>
<proxy/>
</otherwise>
</address-switch>
</not-present>
</address-switch>
</taa:routed>
</cpl>
CPL Example: Restricting Access to a Local Gateway
192.
In these examples, a gateway is registered to the VCS with a prefix of 9 and the administrator wants to stop calls from
outside the organization being routed through it.
This can be done in two ways: using the address-switch node or the taa:rule-switch node. Examples of each are
shown below.
Using the Address-Switch Node

<taa:routed>
<address regex="9(.*)">
<address-switch field="originating-zone">

<address is="TraversalZone">
354

</address>
</address-switch>
</address>
</address-switch>
</taa:routed>
</cpl>
Using the Taa:Rule-Switch Node

<taa:routed>
<taa:rule-switch>
<taa:rule originating-zone="TraversalZone" destination="9(.*)">

</taa:rule>
<taa:rule origin="(.*)" destination="(.*)">

<proxy/>
</taa:rule>
</taa:rule-switch>
</taa:routed>
</cpl>
CPL Example: Redirecting Failed Calls Based on Status Code

The output from a proxy node allow actions to be taken based on the result of the proxy operation. In base CPL a
single failure output is allowed which is invoked if the call attempt fails for any reason (see section 6.1 of RFC 3880
for details).
The VCS supports an extension to the base CPL specification that allows a status code to be specified so that the
failure action is only invoked if the call attempt fails for the specified reason. In addition the VCS allows multiple
failure outputs to be specified within a single proxy node. This allows a script to redirect the call to different locations
(such as different recorded messages) based on the exact reason for call failure.
For example:
<taa:routed>


<proxy>
<failure status="403">

<taa:location url="[email protected]" clear="yes">
<proxy/>
</taa:location>
</failure>
<failure status="404">

<proxy/>
</taa:location>
</failure>
355
<failure>

<proxy/>
</taa:location>
</failure>
</proxy>
</taa:routed>
</cpl>
CPL Example: Reject Attempts to Subscribe to a Presentity

In this example, attempts to subscribe to the presence of [email protected] are rejected.
<taa:routed>
<taa:rule-switch>
<taa:rule origin=".*" destination="[email protected]" message-regex="^SUBSCRIBE.*">

</taa:rule>
</taa:rule-switch>
</taa:routed>
</cpl>
356
LDAP Server Configuration for Device Authentication

The VCS can be configured to authenticate devices against an H.350 directory service on an LDAP server.
This section describes how to:
download the schemas that must be installed on the LDAP server

install and configure two common types of LDAP servers for use with the VCS:
Microsoft Active Directory
OpenLDAP
Downloading the H.350 Schemas

The following ITU specifications describe the schemas which are required to be installed on the LDAP server:
H.350 Directory services architecture for multimedia conferencing - an LDAP schema to represent endpoints on
the network.
H.350.1 Directory services architecture for H.323 - an LDAP schema to represent H.323 endpoints.
H.350.2 Directory services architecture for H.235 - an LDAP schema to represent H.235 elements.
H.350.4 Directory services architecture for SIP - an LDAP schema to represent SIP endpoints.
The schemas can be downloaded from the web interface on the VCS. To do this:
1. Go to Configuration > Authentication > Devices > H.350 directory schemas. You are presented with a list of
downloadable schemas.
2. Click on the Download button next to each file to open it.
3. Use your browser's Save As command to store it on your file system.
Configuring a Microsoft Active Directory LDAP Server
Prerequisites
These instructions assume that Active Directory has already been installed. For details on installing Active Directory
please consult your Windows documentation.
The following instructions are for Windows Server 2003 Enterprise Edition. If you are not using this version of
Windows, your instructions may vary.
Installing the H.350 Schemas

After you have downloaded the H.350 schemas, install them as follows:
Open an elevated command prompt by right-clicking Command Prompt and selecting 'Run as administrator'. For each
file execute the following command:
ldifde -i -c DC=X <ldap_base> -f filename.ldf
where:
<ldap_base> is the base DN for your Active Directory server.
Adding H.350 Objects

Create the organizational hierarchy:
357
1. Open up the Active Directory Users and Computers MMC snap-in.

2. Under your BaseDN right-click and select New Organizational Unit.
3. Create an Organizational unit called h350.
It is good practice to keep the H.350 directory in its own organizational unit to separate out H.350 objects from other
types of objects. This allows access controls to be setup which only allow the VCS read access to the BaseDN and
therefore limit access to other sections of the directory.
Add the H.350 objects:
1. Create an ldif file with the following contents:

# MeetingRoom1 endpoint
dn: commUniqueId=comm1,ou=h350,DC=X
objectClass: commObject
objectClass: h323Identity
objectClass: SIPIdentity
commUniqueId: comm1
h323Identityh323-ID: MeetingRoom1
h323IdentitydialedDigits: 626262
h235IdentityEndpointID: meetingroom1
h235IdentityPassword: mypassword
SIPIdentityUserName: meetingroom1
SIPIdentityPassword: mypassword
SIPIdentitySIPURI: sip:MeetingRoom@X
2. Add the ldif file to the server using the command:

ldifde -i -c DC=X <ldap_base> -f filename.ldf
where:
<ldap_base> is the base DN of your Active Directory Server.
The example above will add a single endpoint with an H.323 ID alias of MeetingRoom1, an E.164 alias of 626262 and a
SIP URI of MeetingRoom@X. The entry also has H.235 and SIP credentials of ID meetingroom1 and password mypassword
which are used during authentication.
H.323 registrations will look for the H.323 and H.235 attributes; SIP will look for the SIP attributes. Therefore if your
endpoint is registering with just one protocol you do not need to include elements relating to the other.
Note: the SIP URI in the ldif file must be prefixed by sip:.
For information about what happens when an alias is not in the LDAP database see Source of aliases for
registration in the Using an H.350 Directory Service Lookup via LDAP, page 126 section.
Securing with TLS

To enable Active Directory to use TLS, you must request and install a certificate on the Active Directory server. The
certificate must meet the following requirements:
Be located in the Local Computers Personal certificate store. This can be seen using the Certificates MMC
snap-in.
Have the private details on how to obtain a key associated for use with it stored locally. When viewing the
certificate you should see a message saying You have a private key that corresponds to this certificate.
Have a private key that does not have strong private key protection enabled. This is an attribute that can be
added to a key request.
The Enhanced Key Usage extension includes the Server Authentication object identifier, again this forms part
of the key request.
Issued by a CA that both the domain controller and the client trust.
358
Include the Active Directory fully qualified domain name of the domain controller in the common name in the
subject field and/or the DNS entry in the subject alternative name extension.
To configure the VCS to use TLS on the connection to the LDAP server you must upload the CAs certificate as a
trusted CA certificate. This can be done on the VCS by going to: Maintenance > Security certificates > Trusted CA
certificate.
Configuring an OpenLDAP Server
Prerequisites
These instructions assume that an OpenLDAP server has already been installed. For details on installing OpenLDAP
see the documentation at http://www.openldap.org.
The following examples use a standard OpenLDAP installation on the Linux platform. For installations on other
platforms the location of the OpenLDAP configuration files may be different. See the OpenLDAP installation
documentation for details.
Installing the H.350 Schemas
1. Download all the schema files from the VCS (Configuration > Authentication > Devices > LDAP schemas).
Ensure that all characters in the filename are in lowercase and name each file with a .schema extension.
Hence:
commobject.schema
h323identity.schema
h235identity.schema
sipidentity.schema
2. Determine the index of each schema file via slapcat. For example,for commobject.schema:
sudo slapcat -f schema_convert.conf -F ldif_output -n 0 | grep commobject,cn=schema
will return something similar to: dn: cn={14}commobject,cn=schema,cn=config
The index value inside the curly brackets {} will vary.
3. Convert each schema file into ldif format via slapcat. Use the index value returned by the previous command.
For example, for commobject.schema:
slapcat -f schema_convert.conf -F ldif_output -n0 -H ldap:///cn={14}commobject,cn=schema,cn=config -l
cn=commobject.ldif
4. Use a text editor to edit the newly created file (cn=commobject.ldif in the case of the commobject file) and
remove the following lines:
structuralObjectClass:
entryUUID:
creatorsName:
createTimestamp:
entryCSN:
modifiersName:
modifyTimestamp:
5. Add each schema to the ldap database via ldapadd. For example, for cn=commobject.ldif:
sudo ldapadd -Q -Y EXTERNAL -H ldapi:/// -f cn\=commobject.ldif
(the backslash after cn is an escape character)
6. Repeat these steps for every schema file.
More information is available at https://help.ubuntu.com/13.04/serverguide/openldap-server.html.
Adding H.350 Objects

Create the organizational hierarchy:
359

# This example creates a single organizational unit to contain the H.350 objects
dn: ou=h350,dc=my-domain,dc=com
objectClass: organizationalUnit
ou: h350
2. Add the ldif file to the server via slapadd using the format:
slapadd -l <ldif_file>
This organizational unit will form the BaseDN to which the VCS will issue searches. In this example the BaseDN will
be: ou=h350,dc=my-domain,dc=com.
It is good practice to keep the H.350 directory in its own organizational unit to separate out H.350 objects from other
types of objects. This allows access controls to be setup which only allow the VCS read access to the BaseDN and
therefore limit access to other sections of the directory.
Note: the SIP URI in the ldif file must be prefixed by sip:
Add the H.350 objects:

# MeetingRoom1 endpoint
dn: commUniqueId=comm1,ou=h350,dc=mydomain,dc=com
objectClass: commObject
objectClass: SIPIdentity
commUniqueId: comm1
h323Identityh323-ID: MeetingRoom1
h323IdentitydialedDigits: 626262
h235IdentityEndpointID: meetingroom1
h235IdentityPassword: mypassword
SIPIdentityUserName: meetingroom1
SIPIdentityPassword: mypassword
SIPIdentitySIPURI: sip:[email protected]
2. Add the ldif file to the server via slapadd using the format:
slapadd -l <ldif_file>
The example above will add a single endpoint with an H.323 ID alias of MeetingRoom1, an E.164 alias of 626262 and a
SIP URI of [email protected]. The entry also has H.235 and SIP credentials of ID meetingroom1 and password
mypassword which are used during authentication.
H.323 registrations will look for the H.323 and H.235 attributes; SIP will look for the SIP attributes. Therefore if your
endpoint is registering with just one protocol you do not need to include elements relating to the other.
For information about what happens when an alias is not in the LDAP database see Source of aliases for
registration in the Using an H.350 Directory Service Lookup via LDAP, page 126 section.
Securing with TLS

The connection to the LDAP server can be encrypted by enabling Transport Level Security (TLS) on the connection.
To do this you must create an X.509 certificate for the LDAP server to allow the VCS to verify the servers identity.
After the certificate has been created you will need to install the following three files associated with the certificate
onto the LDAP server:
the certificate for the LDAP server

the private key for the LDAP server
the certificate of the Certificate Authority (CA) that was used to sign the LDAP servers certificate
All three files should be in PEM file format.
360
The LDAP server must be configured to use the certificate. To do this:
Edit /etc/openldap/slapd.conf and add the following three lines:

TLSCACertificateFile <path to CA certificate>
TLSCertificateFile <path to LDAP server certificate>
TLSCertificateKeyFile <path to LDAP private key>
The OpenLDAP daemon (slapd) must be restarted for the TLS settings to take effect.
To configure the VCS to use TLS on the connection to the LDAP server you must upload the CAs certificate as a
trusted CA certificate. This can be done on the VCS by going to: Maintenance > Security certificates > Trusted CA
certificate.
361
DNS Configuration Examples

This section gives examples of DNS configuration using Microsoft DNS Server and BIND 8 & 9.
These examples show how to set up an SRV record to handle H.323 URIs of the form [email protected]. These are
handled by the system with the fully qualified domain name of vcs.example.com which is listening on port 1719, the
default registration port.
It is assumed that both A and AAAA records already exist for vcs.example.com. If not, you will need to add them.
Verifying the SRV Record

There are a range of tools available to investigate DNS records. One commonly found on Microsoft Windows and
UNIX platforms is nslookup. Use this to verify that everything is working as expected. For example:
nslookup -querytype=srv_h323ls._udp.example.com
and check the output.
Microsoft DNS Server

Using Microsoft DNS Server you can add the SRV record using either the command line or the MMC snap-in.
To use the command line, on the DNS server open a command window and enter:
dnscmd . /RecordAdd domain service_name SRV Priority Weight Port Target
where:
domain is the domain into which you want to insert the record
service_name is the name of the service you are adding
Priority is the priority as defined by RFC 2782
Weight is the weight as defined by RFC 2782
Port is the port on which the system hosting the domain is listening
Target is the FQDN of the system hosting the domain
For example:
dnscmd . /RecordAdd example.com_h323ls._udp SRV 1 0 1719 vcs.example.com
BIND 8 & 9
BIND is a commonly used DNS server on UNIX and Linux systems. Configuration is based around two sets of text files:
named.conf which describes which zones are represented by the server, and a selection of zone files which describe
the detail of each zone.
BIND is sometimes run chrooted for increased security. This gives the program a new root directory, which means
that the configuration files may not appear where you expect them to be. To see if this is the case on your system, run
ps aux | grep named
This will give the command line that named (the BIND server) was invoked with. If there is a -t option, then the path
following that is the new root directory and your files will be located relative to that root.
In /etc/named.conf look for a directory entry within the options section. This will give the directory in which the zone
files are stored, possibly relative to a new root directory. In the appropriate zone section, a file entry will give the
name of the file containing the zone details.
For more details of how to configure BIND servers and the DNS system in general see the publication DNS and BIND.
362
Changing the Default SSH Key

Using the default key means that SSH sessions established to the VCS may be vulnerable to "man-in-the-middle"
attacks, so you are recommended to generate new SSH keys which are unique to your VCS.
An alarm message "Security alert: the SSH service is using the default key is displayed if your VCS is still configured
with its factory default SSH key.
To generate a new SSH key for the VCS:
1. Log into the CLI as root.

2. Type regeneratesshkey.
4. Log in to the web interface.
5. Go to Maintenance > Restart. You are taken to the Restart page.
6. Check the number of calls and registrations currently in place.
7. Click Restart system and then confirm the restart when asked.
If you have a clustered VCS system you must generate new SSH keys for every cluster peer. Log into each peer in turn
and follow the instructions above. You do not have to decluster or disable replication.
When you next log in to the VCS over SSH you may receive a warning that the key identity of the VCS has
changed. Please follow the appropriate process for your SSH client to suppress this warning.
If your VCS is subsequently downgraded to an earlier version of VCS firmware, the default SSH keys will be
restored.
Restoring Default Configuration (Factory Reset)

Very rarely, it may become necessary to run the factory-reset script on your system. This reinstalls the software
image and resets the configuration to the functional minimum.
Note: Restoring default configuration causes the system to use its current default values, which may be different from
the previously configured values, particularly if the system has been upgraded from an older version. In particular this
may affect port settings, such as multiplexed media ports. After restoring default configuration you may want to reset
those port settings to match the expected behavior of your firewall.
Prerequisite Files
The factory-reset procedure described below rebuilds the system based on the most recent successfully-installed
software image. The files that are used for this reinstallation are stored in the /mnt/harddisk/factory-reset/ folder on
the system. These files are:
A text file containing just the 16-character Release Key, named rk

A file containing the software image in tar.gz format, named tandberg-image.tar.gz
In some cases (most commonly a fresh VM installation that has not been upgraded), these files will not be present on
the system. If so, these files must first be put in place using SCP as root.
Performing a Reset to Default Configuration

The following procedure must be performed from the serial console (or via a direct connection to the appliance with a
keyboard and monitor). This is because the network settings will be rewritten, so any SSH session used to initiate the
reset would be dropped and the output of the procedure would not be seen.
The process takes approximately 20 minutes.
363
1. Log in to the system as root.

2. Type factory-reset
3. Answer the questions as required:
The recommended responses will reset the system completely to a factory default state.
Prompt Recommended response
Keep option keys [YES/NO]? YES
Keep IP configuration [YES/NO]? YES
Keep ssh keys [YES/NO]? YES
Keep ssl certificates and keys [YES/NO]? YES
Keep root and admin passwords [YES/NO]? YES
Save log files [YES/NO]? YES
Replace hard disk [YES/NO]? NO

(only applies to systems running on legacy appliance hardware)
4. Finally, confirm that you want to proceed.
Resetting via USB Stick

Cisco TAC may also suggest an alternative reset method. This involves downloading the software image onto a USB
stick and then rebooting the system with the USB stick plugged in.
If you use this method you must clear down and rebuild the USB stick after use. Do not reset one system and then
take the USB stick and re-use it on another system.
364
Password Encryption
All passwords configured on the VCS are stored securely in either an encrypted or hashed form. This applies to the
following items, which all have usernames and passwords associated with them:
the default admin administrator account

any additional administrator accounts
local authentication database credentials (a list of valid usernames and passwords that are used when other
devices are required to authenticate with the VCS)
outbound connection credentials (used by the VCS when required to authenticate with another system)
LDAP server (used by the VCS when binding to an LDAP server)
Web interface
When entering or viewing passwords using the web interface, you will see placeholder characters (e.g. dots or stars,
depending on your browser) instead of the characters you are typing.
Command line interface (CLI)
When entering passwords using the command line interface (CLI), you type the password in plain text. However, after
the command has been executed, the password is displayed in its encrypted form with a {cipher} prefix, for example:
xConfiguration Authentication Password: "{cipher}xcy6k+4NgB025vYEgoEXXw=="
Note that FindMe is a standalone application that can be hosted by the VCS or by another remote server. This means
that FindMe account information is not configured or accessible using the CLI of the VCS. However, FindMe account
passwords are still stored securely.
Maximum length of passwords
For each type of password, the maximum number of plain text characters that can be entered is shown in the table
below.
Password type Maximum length
Admin account 1024
Other local administrator accounts 1024
Local database authentication credentials 128
Outbound connection credentials 128
LDAP server 60
FindMe accounts 1024
Note that:
local administrator account passwords are hashed using SHA512; other passwords are stored in an encrypted
format
when a password is encrypted and stored, it uses more characters than the original plain text version of the
password
365
Pattern Matching Variables

The VCS makes use of pattern matching in a number of its features, namely Allow Lists and Deny Lists, pre-search
transforms and when configuring search rules and zone transforms.
For each of these pattern matches, the VCS allows you to use a variable that it will replace with the current
configuration values before the pattern is checked.
These variables can be used as either or both of:
all or part of the pattern that is being searched for

all or part of the string that is replacing the pattern that was found
The variables can be used in all types of patterns (Prefix, Suffix, Regex and Exact).
The table below shows the strings that are valid as variables, and the values they represent.
String Represents value returned by... When used in a Pattern field When used in a
Replace field
%ip% xConfiguration Ethernet 1 IP V4 Matches all IPv4 and IPv6 not applicable
Address addresses.
xConfiguration Ethernet 1 IP V6
Address Applies to all peer addresses if
xConfiguration Ethernet 2 IP V4 the VCS is part of a cluster.
Address
xConfiguration Ethernet 2 IP V6
Address
%ipv4% xConfiguration Ethernet 1 IP V4 Matches the IPv4 addresses not applicable

Address currently configured for LAN 1
xConfiguration Ethernet 2 IP V4 and LAN 2.
Address
Applies to all peer addresses if
the VCS is part of a cluster.
%ipv4_1% xConfiguration Ethernet 1 IP V4 Matches the IPv4 address Replaces the string
Address currently configured for LAN with the LAN 1 IPv4
1. address.
Applies to all peer addresses if If the VCS is part of

the VCS is part of a cluster. a cluster, the
address of the local
peer is always used.
2. address.

%ipv6% xConfiguration Ethernet 1 IP V6 Matches the IPv6 addresses not applicable

Address currently configured for LAN 1
xConfiguration Ethernet 2 IP V6 and LAN 2.
Address
Applies to all peer addresses if
the VCS is part of a cluster.
366
String Represents value returned by... When used in a Pattern field When used in a
Replace field
1. address.

2. address.

%localdomains% xConfiguration SIP Domains Domain 1 Matches all the SIP domains not applicable
Name currently configured on the
... VCS.
xConfiguration SIP Domains Domain
200 Name
%localdomain1% xConfiguration SIP Domains Domain 1 Matches the specified SIP Replaces the string
... Name domain. Up to 200 SIP with the specified
%localdomain200% ... domains can be configured on SIP domain.
xConfiguration SIP Domains Domain the VCS, and they are
200 Name identified by an index number
between 1 and 200.
%systemname% xConfiguration SystemUnit Name Matches the VCSs System Replaces the string
Name. with the VCSs
System Name.
You can test whether a pattern matches a particular alias and is transformed in the expected way by using the Check
pattern tool (Maintenance > Tools > Check pattern).
Port Reference
The following tables list the IP ports and protocols used by VCS for general services and functions. Also see:
Microsoft Lync B2BUA Port Reference, page 374

Device Authentication Port Reference, page 376
Mobile and Remote Access Port Reference, page 372
The tables show the generic defaults for each service, many of which are configurable. The actual services and ports
used on your system will vary depending on its configuration, the option keys installed and features that have been
enabled. A specific list of all the IP ports in use on a particular VCS can be viewed via the port usage pages
(Maintenance >Tools >Port usage).
Local VCS Inbound/Outbound Ports

These are the IP ports on the VCS used to receive (inbound) or send (outbound) communications with other systems.
367
Table 11 Local inbound/outbound ports
Service/ Purpose VCS port (default) Direction Configurable via

function
SSH Encrypted command line administration. 22 TCP inbound not configurable
HTTP Unencrypted web administration. 80 TCP inbound not configurable
NTP System time updates (and important for 123 UDP outbound not configurable
H.235 security).
SNMP Network management. 161 UDP inbound not configurable
HTTPS Encrypted web administration. 443 TCP inbound not configurable
Clustering IPsec secure communication between 500 UDP inbound not configurable
cluster peers. outbound
Clustering IPsec secure communication between IP protocol 51 (IPSec inbound not configurable
cluster peers. AH) outbound
Reserved 636 inbound not configurable
DNS Sending requests to DNS servers. 1024 - 65535 UDP outbound System >DNS
Gatekeeper Multicast gatekeeper discovery. The 1718 UDP inbound not configurable
discovery VCS does not listen on this port when
H.323 Gatekeeper Auto discover mode
is set to Off (this disables IGMP
messages).
H.323 Listens for inbound H.323 UDP 1719 UDP inbound Configuration >
registration registrations. If the VCS is part of a outbound Protocols > H.323
Clustering cluster, this port is used for inbound and
outbound communication with peers,
even if H.323 is disabled.
H.323 call Listens for H.323 call signaling. 1720 TCP inbound Configuration >
signaling Protocols > H.323
Assent call Assent signaling on the VCS 2776 TCP inbound Configuration >
signaling Expressway. Traversal > Ports
H.460.18 call H.460.18 signaling on the VCS 2777 TCP inbound Configuration >
signaling Expressway. Traversal > Ports
Traversal Optionally used on the VCS Expressway 2776/2777 UDP inbound Configuration >
server media for demultiplexing RTP/RTCP media on outbound Traversal > Ports
demultiplexing Small/Medium systems only.
RTP/RTCP
TURN services Listening port for TURN relay requests 3478 UDP/TCP * inbound Configuration >
on VCS Expressway. Traversal > TURN
System Encrypted administration connector to 4444 TCP inbound not configurable

database the VCS system database.
SIP UDP Listens for incoming SIP UDP calls. 5060 UDP inbound Configuration >
outbound Protocols > SIP
SIP TCP Listens for incoming SIP TCP calls. 5060 TCP inbound Configuration >
Protocols > SIP
368
Table 11 Local inbound/outbound ports (continued)

function
SIP TLS Listens for incoming SIP TLS calls. 5061 TCP inbound Configuration >
Protocols > SIP
SIPMTLS Listens for incoming SIPMutual TLS 5062 TCP inbound Configuration >
calls. Protocols > SIP
B2BUA Internal ports used by the B2BUA. Other 5071, 5073 TCP inbound not configurable
traffic sent to these ports is blocked
automatically by the VCS's non-
configurable firewall rules.
Traversal Port on the VCS Expressway used for 6001 UDP, inbound Configuration >
server zone H.323 firewall traversal from a particular increments by 1 for Zones
H.323 Port traversal client. each new zone
Traversal Port on the VCS Expressway used for 7001 TCP, inbound Configuration >
server zone SIP firewall traversal from a particular increments by 1 for Zones
SIP Port traversal client. each new zone
H.225 and Range of ports used for call signaling 15000 - 19999 TCP inbound Configuration >
H.245 call after a call is established. outbound Protocols > H.323
signaling port
range
SIP TCP Range of ports used by outbound 25000 - 29999 TCP outbound Configuration >
outbound port TCP/TLS SIP connections to a remote Protocols > SIP
range SIP device.
Ephemeral Various purposes. 30000 35999 outbound System >

ports Administration
(The default range of 30000 35999
applies to new installations of X8.1 or
later; the previous default range of
40000 49999 still applies to earlier
releases that have upgraded to X8.1.)
369

function
Multiplexed Ports used for multiplexed media in 36000 36001 UDP inbound Configuration >
traversal traversal calls. RTP and RTCP media (Small / Medium outbound Local Zone >
media demultiplexing ports are allocated from systems) Traversal Subzone
(Assent, the start of the traversal media ports
H.460.19 range. or
multiplexed
media) On new installations of X8.1 or later, the 36000 36011 UDP
default media traversal port range is (Large systems)
36000 to 59999, and is set on the VCS
Control (Configuration >Local Zones
>Traversal Subzone). In Large VCS
Expressway systems the first 12 ports in
the range 36000 to 36011 by default
are always reserved for multiplexed
traffic. The VCS Expressway listens on
these ports. You cannot configure a
distinct range of demultiplex listening
ports on Large systems: they always use
the first 6 pairs in the media port range.
On Small/Medium systems you can
explicitly specify which 2 ports listen for
multiplexed RTP/RTCP traffic, on the
VCS Expressway (Configuration >
Traversal >Ports).
On upgrades to X8.2 or later, the VCS

Control retains the media traversal port
range from the previous version (could
be 50000 - 54999 or 36000 - 59999,
depending on source version). The VCS
Expressway retains the previously
configured demultiplexing pair (either
2776 & 2777 or 50000 & 50001 by
default, depending on upgrade path)
and the switch Use configured
demultiplexing ports is set to Yes. If
you do not want to use a particular pair
of ports, switch Use configured
demultiplexing ports to No, then the
VCS Expressway will listen on the first
pair of ports in the media traversal port
range (36000 and 36001 by default). In
this case, we recommend that you close
the previously configured ports after you
configure the firewall for the new ports.
370

function
Non- Range of ports used for non-multiplexed 36002 59999 UDP inbound Configuration >
multiplexed media. Ports are allocated from this (Small / Medium outbound Local Zone >
media port range in pairs, with the first port number systems) Traversal Subzone
range of each pair being an even number.
or
On new installations of X8.1 or later, the
default media traversal port range is 36012 59999 UDP
36000 to 59999, and is set on the VCS (Large systems)
Control (Configuration >Local Zones
>Traversal Subzone). In Large VCS
Expressway systems the first 12 ports in
the range 36000 to 36011 by default
are always reserved for multiplexed
traffic. The VCS Expressway listens on
these ports. You cannot configure a
distinct range of demultiplex listening
ports on Large systems: they always use
the first 6 pairs in the media port range.
On Small/Medium systems you can
explicitly specify which 2 ports listen for
multiplexed RTP/RTCP traffic, on the
VCS Expressway (Configuration >
Traversal >Ports).
On upgrades to X8.2 or later, the VCS

Control retains the media traversal port
range from the previous version (could
be 50000 - 54999 or 36000 - 59999,
depending on source version). The VCS
Expressway retains the previously
configured demultiplexing pair (either
2776 & 2777 or 50000 & 50001 by
default, depending on upgrade path)
and the switch Use configured
demultiplexing ports is set to Yes. If
you do not want to use a particular pair
of ports, switch Use configured
demultiplexing ports to No, then the
VCS Expressway will listen on the first
pair of ports in the media traversal port
range (36000 and 36001 by default). In
this case, we recommend that you close
the previously configured ports after you
configure the firewall for the new ports.
TURN relay Range of ports available for TURN media 24000 29999 UDP inbound Configuration >
media port relay. ** outbound Traversal > TURN
range
Note that two services or functions cannot share the same port and protocol; an alarm will be raised if you attempt to
change an existing port or range and it conflicts with another service.
* On Large systems you can configure a range of TURN request listening ports. The default range is 3478 3483.
** The default TURN relay media port range of 24000 29999 applies to new installations of X8.1 or later. The
previous default range of 60000 61799 still applies to earlier releases that have upgraded to X8.1.
371
Remote Listening Ports

These tables show the default listening (destination) ports on the remote systems with which the VCS communicates.
The source port on the VCS for all of these communications is assigned from the VCS's ephemeral range.
Table 12 Remote listening ports
Service/ Purpose Destination port Configurable via

function (default)
DNS Requests to a DNS server. 53 UDP System >DNS
External manager Outbound connection to an external 80 TCP System >External

manager, for example Cisco TMS. manager
NTP System time updates. 123 UDP System >Time
LDAP account LDAP queries for login account 389 / 636 TCP Users >LDAP
authentication authentication. configuration
TMSProvisioning Connection to Cisco TMSPE services. 443 TCP System > TMS
Extension Provisioning Extension
services
Incident reporting Sending application failure details. 443 TCP Maintenance >
Diagnostics > Incident
reporting > Configuration
Third-party FindMe / Outbound connection to a third-party 443 TCP Applications >FindMe

User Policy server FindMe / User Policy server.
Remote logging Sending messages to the remote 514 UDP Maintenance >Logging
syslog server. 6514 TCP
Neighbors (H.323) H.323 connection to a neighbor zone. 1710 UDP Configuration >Zones
Neighbors (SIP) SIP connection to a neighbor zone. 5060 / 5061 TCP Configuration >Zones
Traversal zone (H.323) H.323 connection to a traversal server. 6001 UDP Configuration >Zones
Traversal zone (SIP) SIP connection to a traversal server. 7001 TCP Configuration >Zones
Endpoint (H.323) Endpoint listening port 1720 TCP Defined by endpoints

registration
Endpoint (SIP) Endpoint listening port 5060 / 5061 Defined by endpoints

TCP / UDP registration
System Metrics Publishing metrics to a remote 25826 UDP Maintenance >Logging

Collection analytics server
TURN media relay Range of ports available for TURN 24000 29999 Configuration > Traversal
media relay. UDP ** > TURN (on VCS
Expressway)
Mobile and Remote Access Port Reference

This section summarizes the ports that could potentially be used between your internal network (where the VCS
Control is located) and the DMZ (where the VCS Expressway is located) and between the DMZ and the public
372
internet.
XMPP (IM and Presence) TCP Ephemeral port 7400
SSH (HTTP/S tunnels) TCP Ephemeral port 2222
Traversal zone SIP signaling TLS 25000 to 29999 7001
Traversal zone SIP media UDP 36000 to 59999* 36000 (RTP), 36001
(RTCP) (defaults)
(for small/medium systems on X8.1 or
later) 2776 (RTP), 2777 (RTCP)
(old defaults*)
Traversal zone SIPmedia UDP 36000 to 59999* 36000 to 36011 (6 pairs of

RTPand RTCPports for
(for large systems) multiplexed media
traversal)
Purpose Protocol VCS Expressway (source) Internet endpoint

(listening)
SIP media UDP 36002 to 59999 or >= 1024
36012 to 59999
SIP signaling TLS 25000 to 29999 >= 1024
Purpose Protocol Internet endpoint (source) VCS Expressway (listening)
XMPP (IM and Presence) TCP >= 1024 5222
HTTP proxy (UDS) TCP >= 1024 8443
Media UDP >= 1024 36002 to 59999 or
36012 to 59999*

SIP signaling TLS >= 1024 5061
HTTPS (only required for external TCP >= 1024 443

administrative access, which is
strongly discouraged)
From VCS Control to Internal Infrastructure and Endpoints
XMPP (IM and Presence) TCP Ephemeral port 7400 (IM and Presence)
HTTP proxy (UDS) TCP Ephemeral port 8443 (Unified CM)
373
HTTP proxy (SOAP) TCP Ephemeral port 8443 (IMand Presence

Service)
HTTP (configuration file retrieval) TCP Ephemeral port 6970 (Unified CM)
CUC (voicemail) TCP Ephemeral port 443 (Unity Connection)
Message Waiting Indicator (MWI) from TCP Ephemeral port 7080 (Unity Connection)
Unity Connection
Media UDP 36000 to 59999* >= 1024 (Media recipient

eg. endpoint)
SIPsignaling TCP 25000 to 29999 5060 (Unified CM)
Secure SIP signaling TLS 25000 to 29999 5061 (Unified CM)
Note that:
Ports 8191/8192 TCP and 8883/8884 TCP are used internally within the VCS Control and the VCS
Expressway applications. Therefore these ports must not be allocated for any other purpose. The VCS
Expressway listens externally on port 8883; therefore we recommend that you create custom firewall rules on
the external LAN interface to drop TCP traffic on that port.
The VCS Expressway listens on port 2222 for SSH tunnel traffic. The only legitimate sender of such traffic is
the VCS Control (cluster). Therefore we recommend that you create the following firewall rules for the SSH
tunnels service:
one or more rules to allow all of the VCS Control peer addresses (via the internal LAN interface, if
appropriate)
followed by a lower priority (higher number) rule that drops all traffic for the SSH tunnels service (on the
internal LAN interface if appropriate, and if so, another rule to drop all traffic on the external interface)
Microsoft Lync B2BUA Port Reference

The port numbers listed below are the default port values. The values used in a real deployment may vary if they have
been modified, for example, by changes of registry settings or through group policy, on Lync and Lync client, or
configuration on VCS (Applications >B2BUA).

374
Table 13 Between B2BUA and Lync
Purpose Protocol IP port Lync IP port
Signaling to Lync Server TLS 65072 5061 (Lync signaling destination

port)
Signaling from Lync Server TLS 65072 Lync ephemeral port
Presence to Lync Server TLS 10011 5061 (Lync signaling destination

port)
Presence from Lync Server TLS 10011 Lync ephemeral port
Media UDP 56000 to 57000 Lync client media ports
(The Lync B2BUA application should run Each call can use
on a separate "Gateway" VCS and so up to 18 ports if
this range should not conflict with the you Enable RDP
standard traversal media port range) Transcoding for
this B2BUA.
Note:The VCS does not forward
DSCPinformation that it receives in Increase this range
media streams. if you see "Media
port pool
exhausted"
warnings.
Desktop shares from Lync clients to TCP 56000 to 57000 Lync client RDPports
B2BUA
Table 14 Between B2BUA and Internal Video Network
Purpose Protocol B2BUAport VCS IP port
Internal communications with VCS TLS 65070 SIP TCP outbound port on VCS
application
Transcoded desktop shares from B2BUA UDP 56000 to 57000 Recipient of media is dependent
to internal recipients on deployment and called alias;
eg. endpoint, TelePresence
Server, VCS Control
Table 15 Between B2BUA and VCS Expressway Hosting the TURN Server
Purpose Protocol B2BUA IP port VCS Expressway IP port
All communications UDP 56000 to 57000 3478 (media/signaling) *
Ensure that the firewall is opened to allow the data traffic through from B2BUA to VCS Expressway.
* On Large systems you can configure a range of TURN request listening ports. The default range is 3478 3483.

375
Table 16 External Lync Client and Edge Server
Purpose Protocol Edge server Lync client
SIP/MTLS used between Lync Client and TCP 5061 5061

Edge server for signaling (including any
ICE messaging to the Edge Server)
SIP/TLS TCP 443 443
STUN UDP 3478 3478
UDP Media UDP 50000-59999 1024-65535
TCP Media TCP 50000-59999 1024-65535
Table 17 External Lync Client / Edge Server and VCS Expressway
Purpose Protocol Lync client / Edge VCS Expressway

server
ICE messaging (STUN/TURN) UDP & TCP 3478 3478
(VCS Expressway must listen on

TCP3478 for desktop sharing relay
requests from Lync clients, and on
UDP3478 for A/Vmedia relay requests)
UDP media UDP 1024-65535 24000-29999 **

Table 18 Between B2BUA and External Transcoder
Purpose Protocol B2BUA IP port Transcoder
B2BUA communications with transcoder TLS 65080 5061

(Cisco AM GW)
Device Authentication Port Reference
H.350 Directory Service

The following table lists the ports used for device authentication between VCS and the H.350 server. They are
configurable via Configuration > Authentication > Devices > H.350 directory service.
Purpose VCS port Destination port
H.350 LDAP server TCP ephemeral port TCP/389 or TCP/636
Active Directory (Direct)

The following table lists the ports used for device authentication between VCS and the AD system. They are
configurable via Configuration > Authentication > Devices > Active Directory Service.
376
Purpose VCS port Destination port
Kerberos Key Distribution Center UDP ephemeral port 88 UDP
Kerberos TCP ephemeral port 88 TCP
VCS with Domain Controller (CLDAP) UDP ephemeral port 389 UDP
VCS with Domain Controller (LDAP) TCP ephemeral port 389 / 636 TCP
Client credential authentication with the Domain TCP ephemeral port 445 / 139 TCP
Controller (Microsoft-DS). VCS initially tries port 445,
but if that cannot be reached it tries port 139.
377
Regular expressions
Regular expressions can be used in conjunction with a number of VCS features such as alias transformations, zone
transformations, CPL policy and ENUM. The VCS uses POSIX format regular expression syntax. The table below
provides a list of commonly used special characters in regular expression syntax. This is only a subset of the full range
of expressions available. For a detailed description of regular expression syntax see the publication Regular
Expression Pocket Reference.
Character Description Example
. Matches any single character.
\d Matches any decimal digit, i.e. 0-9.
* Matches 0 or more repetitions of the .* matches against any sequence of characters

previous character or expression.
+ Matches 1 or more repetitions of the

previous character or expression.
? Matches 0 or 1 repetitions of the previous 9?123 matches against 9123 and 123
character or expression.
{n} Matches n repetitions of the previous \d{3} matches 3 digits

character or expression
{n,m} Matches n to m repetitions of the previous \d{3,5} matches 3, 4 or 5 digits

character or expression
[...] Matches a set of specified characters. Each [a-z] matches any alphabetical character
character in the set can be specified
individually, or a range can be specified by [0-9#*] matches against any single E.164 character -
giving the first character in the range the E.164 character set is made up of the digits 0-9 plus
followed by the - character and then the last the hash key (#) and the asterisk key (*)
character in the range.
You cannot use special characters within

the [] - they will be taken literally.
[^...] Matches anything except the set of [^a-z] matches any non-alphabetical character
specified characters. Each character in the
set can be specified individually, or a range [^0-9#*] matches anything other than the digits 0-9, the
can be specified by giving the first character hash key (#) and the asterisk key (*)
in the range followed by the - character and
then the last character in the range.
You cannot use special characters within

the [] - they will be taken literally.
(...) Groups a set of matching characters A regular expression can be constructed to transform a
together. Groups can then be referenced in URI containing a users full name to a URI based on their
order using the characters \1, \2, etc. as initials. The regular expression (.).*_(.).*
part of a replace string. (@example.com) would match against the user john_
[email protected] and with a replace string of \1\2\3
would transform it to [email protected]
| Matches against one expression or an .*@example.(net|com) matches against any URI for the
alternate expression. domain example.com or the domain example.net
\ Escapes a regular expression special

character.
378
^ Signifies the start of a line. [^abc] matches any single character that is NOT one of
a, b or c
When used immediately after an opening
brace, negates the character set inside the
brace.
$ Signifies the end of a line. ^\d\d\d$ matches any string that is exactly 3 digits long
(?!...) Negative lookahead. Defines a (?!.*@example.com$).* matches any string that does not
subexpression that must not be present. end with @example.com
(?!alice).* matches any string that does not start with

alice
(?<!...) Negative lookbehind. Defines a .*(?<!net) matches any string that does not end with
subexpression that must not be present. net
Note that regex comparisons are not case sensitive.

For an example of regular expression usage, see the CPL examples section.
379
Supported Characters
The VCS supports the following characters when entering text in the CLI and web interface:
the letters A-Z and a-z

decimal digits ( 0-9 )
underscore ( _ )
minus sign / hyphen ( - )
equals sign ( = )
plus sign ( + )
at sign ( @ )
comma ( , )
period/full stop ( . )
exclamation mark ( ! )
spaces
FindMe account names additionally allow the use of all uppercase and lowercase Unicode characters
The following characters are specifically not allowed:
tabs
angle brackets ( < and > )
ampersand ( & )
caret ( ^ )
Note that some specific text fields (including Administrator and user groups) have different restrictions and these are
noted in the relevant sections of this guide.
Case sensitivity
Text items entered through the CLI and web interface are case insensitive. The only exceptions are passwords and
local administrator account names which are case sensitive.
380
Call Types and Licensing

This section describes the different call types recognized by the VCS and how they are licensed.
Call Types
The VCS distinguishes between the following types of call:
Unified CM remote sessions: these are "mobile and remote access" calls i.e.video or audio calls from
devices located outside the enterprise that are routed via the Expressway firewall traversal solution to
endpoints registered to Unified CM. These calls do not require any type of call license, although they do
contribute to traversal load.
VCS traversal calls: these are standard VCS video or audio calls, including business-to-business calls,
B2BUA calls (for media encryption or ICE), and interworked or gatewayed calls to third-party solutions where
the VCS takes both the call signaling and the call media. Each call consumes a traversal call license.
Audio-only SIP traversal calls are treated distinctly from video SIP traversal calls. Each traversal call license
allows either 1 video call or 2 audio-only SIP calls. Hence, a 100 traversal call license would allow, for
example, 90 video and 20 SIP audio-only simultaneous calls. Any other audio-only call (non-traversal, H.323
or interworked) will consume a standard video call license (traversal or non-traversal as appropriate).
VCS non-traversal calls: these are standard VCS video or audio calls where the signaling passes through the
VCS but the media goes directly between the endpoints, or between an endpoint and another system in the
call route. Each call consumes a non-traversal call license. Note that Lync B2BUA calls are classified as non-
traversal calls (even though the media does traverse the VCS).
Each VCS also allows up to 750 concurrent non-traversal calls.
Note that:
VCS defines an "audio-only" SIP call as one that was negotiated with a single m= line in the SDP. Thus, for
example, if a person makes a telephone call but the SIP UA includes an additional m= line in the SDP, the
call will consume a video call license.
While an "audio-only" SIP call is being established, it is treated (licensed) as a video call. It only becomes
licensed as "audio-only" when the call setup has completed. This means that if your system approaches its
maximum licensed limit, you may be unable to connect some "audio-only" calls if they are made
simultaneously.
The VCS does not support midcall license optimization.

License Bypass for Calls to Collaboration Meeting Rooms (CMRs)

The VCS no longer requires traversal call licenses for calls to and from cloud-based CMRs. This includes SIP calls
between Collaboration Cloud and the CMR Hybrid solution.
Note: This only applies when the dialed string does not need transformation on the VCS (for example,
[email protected]).
Although untransformed SIP calls to cloud-based CMRs do not consume licenses, they do consume resources and
may not progress if the VCS is at full capacity.
There is no license bypass for CMR Premises calls. H.323 calls to cloud-based CMRs still consume licenses.
What are Traversal Calls?

A traversal call is any call passing through the VCS that includes both the signaling (information about the call) and
media (voice and video). The only other type of call is a non-traversal call, where the signaling passes through the
VCS but the media goes directly between the endpoints (or between one endpoint and another VCS in the call route,
or between two VCSs in the call route).
381
A call is traversal or non-traversal from the point of view of the VCS through which it is being routed at the time. A
call between two endpoints may pass through two or more VCSs. Some of these VCSs may just take the signaling, in
which case the call will be a non-traversal call for that VCS. Other VCSs in the route may need to take the media as
well, and so the call will count as a traversal call on that particular VCS.
The following types of calls require the VCS to take the media. They are classified as traversal calls, require a
traversal call license, and always pass through the Traversal Subzone:
Unified CM remote sessions (these do not require a traversal call license)

all other firewall traversal calls that are not Unified CM remote sessions, where the local VCS is either the
traversal client or traversal server
calls that are gatewayed (interworked) between H.323 and SIP on the local VCS
calls that are gatewayed (interworked) between IPv4 and IPv6 on the local VCS
for a VCS Expressway with Advanced Networking enabled, calls that are inbound from one LAN port and
outbound on the other
a SIP to SIP call when one of the participants is behind a NAT (unless both endpoints are using ICE for NAT
traversal)
calls that invoke the B2BUA to apply a media encryption policy or for ICE messaging support
Note that for calls via the Microsoft Lync B2BUA, the B2BUA application always takes the media but the call is not
classified as a VCS traversal call and does not consume a traversal call license (it may still consume a non-traversal
license if the VCS takes the call signaling).
Traversal calls use more resource than non-traversal calls, and the numbers of each type of call are licensed
separately. The VCS has one license for the maximum number of concurrent traversal calls it can take, and another
for the maximum number of concurrent non-traversal calls. You can increase the number of each type of call
available on your VCS (or VCS cluster, see License Usage Within a Cluster, page 162 for more information) by
purchasing and installing the appropriate option key. While every deployment is different, as a guideline we
recommend that your system has a 10:1 ratio of registrations to concurrent call licenses.
Note that a non-traversal call on a VCS Expressway will consume a traversal license if there are no non-traversal call
licenses available (in this situation, the call will remain a non-traversal call the VCS Expressway will not take the
media, even though it is using a traversal license).
382
Alarms
Alarms occur when an event or configuration change has taken place on the VCS that requires some manual
administrator intervention, such as a restart. Alarms may also be raised for hardware and environmental issues such
as faulty disks and fans or high temperatures.
The Alarms page (Status > Alarms) provides a list of all the alarms currently in place on your system (and, where
applicable, their proposed resolution). When there are unacknowledged alarms in place on the VCS, an alarm icon
appears at the top right of all pages. You can also access the Alarms page by clicking on the alarm icon.
Each alarm is identified by a 5-digit Alarm ID, shown in the rightmost column in the alarms list. The alarms are
grouped into categories as follows:
Alarm ID prefix Category
10nnn Hardware issues
15nnn Software issues
20nnn Cluster-related issues
25nnn Network and network services settings
30nnn Licensing / resources / option keys
35nnn External applications and services (such as policy services or LDAP/AD configuration)
40nnn Security issues (such as certificates, passwords or insecure configuration)
45nnn General VCS configuration issues
55nnn B2BUA issues
6nnnn Hybrid Services issues
All alarms raised on the VCS are also raised as Cisco TMS tickets. All the attributes of an alarm (its ID, severity and so
on) are included in the information sent to Cisco TMS.
List of alarms
The following table lists the alarms that can be raised on the VCS.
ID Title Description Solution Severity
10001 Hardware failure <problem description> Critical
10002 RAID degraded <problem description> Follow your Cisco RMA process Critical
to obtain replacement parts, and
then see 'Cisco UCS C220
Server Installation and Service
Guide' for information about how
to replace server components.
10003 PSU redundancy <problem description> Follow your Cisco RMA process Critical
lost to obtain replacement parts, and
then see 'Cisco UCS C220
Server Installation and Service
Guide' for information about how
to replace server components.
383
10004 RAID rebuilding <problem description> Wait for the rebuild to complete. Critical
On successful completion, all
RAID-related alarms will be
automatically lowered.
15004 Application An unexpected software error was View the incident reporting page Error
failed detected in <module>
15005 Database failure Please remove database and restore from Reboot the system Warning
backup, then reboot the system
15007 The system is The system is shutting down, or starting Alert

busy
15008 Failed to load The database failed to load; some Restore system data from Warning
database configuration data has been lost backup
15009 Factory reset Factory reset started Alert

started
15012 Language pack Some text labels may not be translated Contact your Cisco Warning
mismatch representative to see if an up-to-
date language pack is available
15013 Factory reset Factory reset failed Alert

failed
15014 Restart required Core dump mode has been changed, Restart the system Warning
however a restart is required for this to
take effect
15015 Maintenance The VCS is in Maintenance mode and will Warning

mode no longer accept calls and registrations
15016 Directory service The directory service database is not Restart the system Warning
database failure running
15017 Application The OpenDS service has stopped If the problem persists, contact Warning
failed unexpectedly and has been restarted your Cisco representative
15018 Boot selection Booted system does not match expected Reboot the system Critical
mismatch configuration; this may be caused by user
input or spurious characters on the serial
console during the boot
15019 Application An unexpected software error was Restart the system; if the Critical
failed detected in <details> problem persists, contact your
Cisco support representative
20003 Invalid cluster The cluster configuration is invalid Check the Clustering page and Warning
configuration ensure that this system's IP
address is included and there are
no duplicate IP addresses
384
20004 Cluster The system is unable to communicate Check the clustering Warning
communication with one or more of the cluster peers configuration
failure
20005 Invalid peer One or more peer addresses are invalid Check the Clustering page and Warning
address ensure that all Peer fields use a
valid IP address
20006 Cluster The database is unable to replicate with Check the clustering Warning
database one or more of the cluster peers configuration and restart
communication
failure
20007 Restart required Cluster configuration has been changed, Restart the system Warning
take effect
20008 Cluster Automatic replication of configuration has Please wait until the upgrade Warning
replication error been temporarily disabled because an has completed
upgrade is in progress
20009 Cluster There was an error during automatic View cluster replication Warning
replication error replication of configuration instructions
20010 Cluster The NTP server is not configured Configure an NTP server Warning
replication error
20011 Cluster This peer's configuration conflicts with View cluster replication Warning
replication error the master's configuration, manual instructions
synchronization of configuration is
required
20012 Cluster This peer's cluster configuration settings Configure this peer's cluster Warning
replication error do not match the configuration master settings
peer's settings
20014 Cluster Cannot find master or this peer's View cluster replication Warning
replication error configuration file, manual synchronization instructions
of configuration is required
20015 Cluster The local VCS does not appear in the list Check the list of peers for this Warning
replication error of peers cluster
20016 Cluster The master peer is unreachable Check the list of peers for this Warning
replication error cluster
20017 Cluster Configuration master ID is inconsistent, View cluster replication Warning

replication error manual synchronization of configuration instructions
is required
20018 Invalid clustering H.323 mode must be turned On - Configure H.323 mode Warning
configuration clustering uses H.323 communications
between peers
20019 Cluster name If FindMe or clustering are in use a cluster Configure the cluster name Warning
not configured name must be defined.
25001 Restart required Network configuration has been changed, Restart the system Warning
take effect
385
25002 Date and time The system is unable to obtain the correct Check the time configuration Warning
not validated time and date from an NTP server
25003 IP configuration IP protocol is set to both IPv4 and IPv6, Configure IP settings Warning
mismatch but the system does not have any IPv4
addresses defined
mismatch but the system does not have an IPv4
gateway defined
25006 Restart required Advanced Networking option key has Configure your required LAN and Warning
been changed, however a restart is static NAT settings on the IP
required for this to take effect page and then restart the
system.
25007 Restart required QoS settings have been changed, Restart the system Warning
take effect
25008 Restart required Port configuration has been changed, Restart the system Warning
take effect
25009 Restart required Ethernet configuration has been changed, Restart the system Warning
take effect
25010 Restart required IP configuration has been changed, Restart the system Warning
take effect
25011 Restart required HTTPS service has been changed, Restart the system Warning
take effect
mismatch but the system does not have an IPv6
gateway defined
25014 Configuration IP protocol is set to both IPv4 and IPv6, Configure IP settings Warning
warning but the VCS does not have any IPv6
addresses defined
25015 Restart required SSH service has been changed, however Restart the system Warning
a restart is required for this to take effect
25016 Ethernet speed An Ethernet interface speed setting has Configure Ethernet parameters Warning
not been negotiated to a value other than
recommended 1000Mb/s full duplex or 100Mb/s full
duplex; this may result in packet loss over
your network
25017 Restart required HTTP service has been changed, however Restart the system Warning
a restart is required for this to take effect
25018 Port conflict There is a port conflict between Review the port configuration on Warning
<function><port> and <function><port> the Local inbound ports and
Local outbound ports pages
386
25019 Verbose log One or more modules of the Network Log Network Log and Support Log Warning
levels or Support Log are set to a level of Debug modules should be set to a level
configured or Trace of Info, unless advised otherwise
by your Cisco support
representative. If diagnostic
logging is in progress they will be
reset automatically when
diagnostic logging is stopped
25020 NTP client The system is unable to run the NTP client Check NTP status information, Warning
failure including any key configuration
and expiry dates
25021 NTP server not The system is unable to contact an NTP Check Time configuration and Warning
available server status; check DNS configuration
25022 Time not The system time of this server is different Ensure that your systems have Warning
synchronized from that on a server on the other side of a consistent Time configuration;
over traversal SIP traversal zone note that any changes may take
zone some time to become effective
30001 Capacity The number of concurrent traversal calls Contact your Cisco Warning
warning has approached the licensed limit representative
30002 Capacity The number of concurrent traversal calls Contact your Cisco Warning
warning has approached the unit's physical limit representative
30003 Capacity The number of concurrent non-traversal Contact your Cisco Warning
warning calls has approached the unit's physical representative
limit
30004 Capacity The number of concurrent non-traversal Contact your Cisco Warning
warning calls has approached the licensed limit representative
30005 Capacity TURN relays usage has approached the Contact your Cisco Warning
warning unit's physical limit representative
30006 Restart required The release key has been changed, Restart the system Warning
take effect
30007 Capacity TURN relays usage has approached the Contact your Cisco Warning
warning licensed limit representative
30008 Invalid release The release key is not valid; if you do not Add/Remove option keys Warning
key have a valid key, contact your Cisco
support representative
30009 TURN relays TURN services are only available on VCS Add/Remove option keys Warning
installed Expressway; TURN option key ignored
30010 Capacity The number of concurrent registrations Contact your Cisco Warning
warning has approached the licensed limit representative
30011 TURN relay TURN services are enabled but no TURN Add option key or disable TURN Warning
licenses relay license option keys are installed services
required
387
30012 License usage Cluster peer <n> has been unavailable for Resolve the issue with this peer, Warning
of lost cluster more than <n> hours. Its licenses will be or remove it from the cluster
peer removed from the total available for use configuration
across the cluster on <date>.
30013 License usage Several cluster peers have been Resolve the issue with this peer, Warning
of lost cluster unavailable for more than <n> hours. Their or remove it from the cluster
peer licenses will be removed from the total configuration
available for use across the cluster as
follows: <details>.
30014 License usage Cluster peer <n> has been unavailable for Resolve the issue with this peer, Warning
of lost cluster more than <n> days. Its licenses will be or remove it from the cluster
peer removed from the total available for use configuration
across the cluster on <date>.
30015 License usage Several cluster peers have been Resolve the issue with this peer, Warning
of lost cluster unavailable for more than <n> days. Their or remove it from the cluster
peer licenses will be removed from the total configuration
available for use across the cluster as
follows: <details>.
30016 Licenses of lost Cluster peer <n> has been unavailable for Resolve the issue with this peer, Warning
cluster peer more than <n> days. Its licenses have or remove it from the cluster
have been taken been removed from the total available for configuration
off the license use across the cluster on <date>.
pool
30017 Licenses of lost Several cluster peers have been Resolve the issue with this peer, Warning
cluster peer unavailable for more than <n> days. Their or remove it from the cluster
have been taken licenses have been removed from the configuration
off the license total available for use across the cluster
pool as follows: <details>.
30018 Provisioning The number of concurrently provisioned Provisioning limits are set by Warning
licenses limit devices has reached the licensed limit Cisco TMS; contact your Cisco
reached representative if you require
more licenses
30019 Call license limit You have reached your license limit of If the problem persists, contact Warning
reached <n> concurrent non-traversal call your Cisco representative to buy
licenses more call licenses
30020 Call license limit You have reached your license limit of If the problem persists, contact Warning
reached <n> concurrent traversal call licenses your Cisco representative to buy
more call licenses
30021 TURN relay You have reached your license limit of If the problem persists, contact Warning
license limit <n> concurrent TURN relay licenses your Cisco representative to buy
reached more TURN relay licenses
30022 Call capacity The number of concurrent non-traversal Ensure that your registrations are Warning
limit reached calls has reached the unit's physical limit distributed evenly across all
peers
30023 Call capacity The number of concurrent traversal calls Ensure that your registrations are Warning
limit reached has reached the unit's physical limit distributed evenly across all
peers
388
30024 TURN relay The number of concurrent TURN relay Ensure that your registrations are Warning
capacity limit calls has reached the unit's physical limit distributed evenly across all
reached peers
30025 Restart required An option key has been changed, Restart the system Warning
take effect
35001 Configuration Active Directory mode has been enabled Configure DNS hostname Warning
warning but the DNS hostname has not been
configured
35002 Configuration Active Directory mode has been enabled Configure NTP server Warning
warning but the NTP server has not been
configured
35003 Configuration Active Directory mode has been enabled Configure a DNS server Warning
warning but no DNS servers have been configured
35004 LDAP Remote login authentication is in use for Configure LDAP parameters Warning
configuration administrator or FindMe accounts but a
required valid LDAP Server address, Port, Bind_DN
and Base_DN have not been configured
35005 Configuration Active Directory mode has been enabled Configure domain on Active Warning
warning but a domain has not been configured Directory Service page
35007 Configuration Active Directory SPNEGO disabled; you Enable SPNEGO Warning
warning are recommended to enable the SPNEGO
setting
35008 Configuration Active Directory mode has been enabled Configure workgroup on Active Warning
warning but a workgroup has not been configured Directory Service page
35009 TMS The VCS is unable to communicate with Go to the TMSProvisioning Warning
Provisioning the TMS Provisioning Extension services. Extension service status page
Extension Phone book service failures can also and select the failed service to
services occur if TMS does not have any users view details about the problem
communication provisioned against this cluster.
failure
35010 TMS An import from the TMS Provisioning See the VCS Event Log for Warning
Provisioning Extension services has been canceled as details, then check the
Extension it would cause the VCS to exceed internal corresponding data within TMS;
services data table limits you must perform a full
import failure synchronization after the data
has been corrected in TMS
35011 TMS One or more records imported from the See the VCS Event Log for Warning
Provisioning TMS Provisioning Extension services have details, then check the
Extension been dropped due to unrecognized data corresponding data within TMS;
services data format you must perform a full
import failure synchronization after the data
has been corrected in TMS
35012 Failed to Failed to connect to the LDAP server for Ensure that your H.350 directory Warning
connect to LDAP H.350 device authentication service is correctly configured
server
389
35013 Unified This system cannot communicate with Review the Event Log and check Warning
Communications one or more remote hosts: <Host 1, Host that the traversal zone between
SSH tunnel 2, ...> the VCS Control and the VCS
failure Expressway is active
Note that the list of hosts is truncated to
200 characters.
35014 Unified This system cannot communicate with Ensure that your firewall allows Warning
Communications one or more remote hosts traffic from the VCS Control
SSHtunnel ephemeral ports to 2222 TCP on
notification the VCS Expressway
failure
35015 Unified CM port There is a port conflict on Unified CM The same port on Unified CM Warning
conflict <name> between neighbor zone <name> cannot be used for line side
and Unified Communications (both are (Unified Communications) and
using port <number>) SIP trunk traffic. Review the port
configuration on Unified CM and
reconfigure the <zone> if
necessary
35016 SAML metadata Configuration changes have modified the Export the SAML metadata so Warning
has been local SAML metadata, which is now you can import it on the Identity
modified different to any copies on Identity Provider Provider
(s). This metadata may have been
modified by changing the server
certificate or the SSO-enabled domains,
or by changing the number of traversal
server peers or their addresses
40001 Security alert No CRL distribution points have been Check CRL configuration Warning
defined for automatic updates
40002 Security alert Automatic updating of CRL files has failed If the problem persists, contact Warning
your Cisco representative
40003 Insecure The root user has the default password View instructions on changing Warning
password in use set the root password
40004 Certificate- Your system is recommended to have Configure client certificate- Warning
based client certificate-based security set to based security
authentication Certificate-based authentication when in
required advanced account security mode
40005 Insecure The admin user has the default password Change the admin password Error
password in use set
40006 Security alert Unable to download CRL update Check CRL distribution points Warning
and the Event Log
40007 Security alert Failed to find configuration file for CRL If the problem persists, contact Warning
automatic updates your Cisco representative
40008 Security alert The SSH service is using the default key View instructions on replacing Warning
the default SSH key
40009 Restart required HTTPS client certificates validation mode Restart the system Warning
has changed, however a restart is
required for this to take effect
390
40011 Per-account A non-zero per-account session limit is Configure per-account session Warning
session limit required when in advanced account limit
required security mode
40012 External You are recommended to use HTTPS Configure external manager Warning
manager connections to the external manger when
connection is in advanced account security mode
using HTTP
40013 HTTPS client You are recommended to enable client Configure HTTPS client Warning
certificate side certificate validation for HTTPS certificate validation
validation connections when in advanced account
disabled security mode
40014 Time out period A non-zero system session time out Configure session time out Warning
required period is required when in advanced period
account security mode
40015 System session A non-zero system session limit is Configure system session limit Warning
limit required required when in advanced account
security mode
40016 Encryption Your login account LDAP server Configure login account LDAP Warning
required configuration is recommended to have server
encryption set to TLS when in advanced
40017 Incident You are recommended to disable incident Configure incident reporting Warning
reporting reporting when in advanced account
enabled security mode
40018 Insecure One or more users has a non-strict Warning

password in use password
40019 External You are recommended to enable external Configure external manager Warning
manager has manager certificate checking when in
certificate advanced account security mode
checking
disabled
40020 Security alert The connection to the Active Directory Configure Active Directory Warning
Service is not using TLS encryption Service connection settings
40021 Remote logging You are recommended to disable the Configure remote logging Warning
enabled remote syslog server when in advanced
40022 Security alert Active Directory secure channel disabled; Enable secure channel Warning
you are recommended to enable the
secure channel setting
40024 CRL checking Your login account LDAP server Configure login account LDAP Warning
required configuration is recommended to have server
certificate revocation list (CRL) checking
set to All when in advanced account
security mode
40025 SNMP enabled You are recommended to disable SNMP Configure SNMP mode Warning
when in advanced account security mode
391
40026 Reboot required The advanced account security mode has Reboot the VCS Warning
changed, however a reboot is required for
this to take effect
40027 Security alert The connection to the TMS Provisioning Configure TMS Provisioning Warning
Extension services is not using TLS Extension services connection
encryption settings
40028 Insecure The root user's password is hashed using View instructions on changing Warning
password in use MD5, which is not secure enough the root password
40029 LDAP server CA A valid CA certificate for the LDAP Upload a valid CA certificate Warning
certificate is database has not been uploaded; this is
missing required for connections via TLS
40030 Security alert Firewall rules activation failed; the Check your firewall rules Warning
firewall configuration contains at least configuration, fix any rejected
one rejected rule rules and re-try the activation
40031 Security alert Unable to restore previous firewall Check your firewall rules Warning
configuration configuration, fix any rejected
rules, activate and accept the
rules; if the problem persists,
contact your Cisco
representative
40032 Security alert Unable to initialize firewall Restart the system; if the Warning
problem persists, contact your
Cisco representative
40033 Configuration The Default Zone access rules are Either disable UDP and TCP on Warning
warning enabled, but leaving SIP over UDP or SIP the SIP page to enforce
over TCP enabled offers a way to certificate identity checking
circumvent this security feature using TLS, or disable the access
rules for the Default Zone.
40034 Security alert Firewall rules activation failed; the Check your firewall rules Warning
firewall configuration contains rules with configuration, ensure all rules
duplicated priorities have a unique priority and re-try
the activation
40036 Delegated The traversal server zone associated with Check that the domain and its Warning
credential SIP domain <domain> cannot connect to associated traversal server zone
checking error the traversal client system are configured correctly. You
may also need to check the
remote traversal client system
40037 Delegated There is a communication problem with Check that the traversal client Warning
credential the traversal client zone <zone> used to zone is configured correctly. You
checking error receive delegated credential checking may also need to check the
requests remote traversal server system
40038 Delegated TLS verify mode is not enabled on the Check the domain and ensure Warning
credential traversal server zone associated with SIP that TLS verify mode is enabled
checking domain <domain> on the associated traversal
configuration server zone
error
392
40039 Delegated TLS verify mode is not enabled on the Ensure that TLS verify mode is Warning
credential traversal client zone (<zone>) that has enabled on the traversal client
checking been configured to accept delegated zone
configuration authentication requests
error
40040 Unified TLS verify mode is not enabled on a Ensure that TLS verify mode is Warning
Communications traversal zone configured for Unified enabled on the traversal zone;
configuration Communications services you may also need to check the
error remote traversal system
40041 Security alert Automated intrusion protection rules are Disable and then re-enable the Warning
not available failed services
40042 FIPS140-2 Some SIP configuration is not using TLS Ensure that TLS is the only Warning
compliance transport; FIPS140-2 compliance requires enabled system-wide SIP
restriction TLS transport mode on the SIP page,
and that all zones are using TLS.
Alternatively, if you are
transitioning into FIPS140-2 you
may want to restore a FIPS-
compliant backup of your data.
40043 Unified Media encryption is not enforced on a Ensure that media encryption is Warning
Communications traversal zone configured for Unified set to 'Force encrypted' on the
configuration Communications services traversal zone
error
40044 System reset FIPS140-2 mode has been enabled; a Ensure that all alarms are Warning
required system reset is required to complete this cleared, then take a system
process backup before performing a
system reset
40045 Restart required FIPS140-2 mode has been disabled; a Restart the system Warning
system restart is required to complete this
process
40046 FIPS140-2 Clustered systems are not FIPS140-2 Disband the cluster Warning
compliance compliant
restriction
40048 Unified Unified Communications services are Ensure that SIP TLS mode is set Warning
Communications enabled but SIP TLS is disabled to 'On' on SIP configuration page
configuration
error
40100 Security alert Firewall rules are not synchronized with Restart the system; if the Warning
network interfaces problem persists, contact your
Cisco representative
45001 Failed to load <failure details> Configure Call Policy Warning

Call Policy file
45002 Configuration Expected default link between the Default Configure default links Warning
warning Subzone and the Default Zone is missing
45003 Configuration H.323 and SIP modes are set to Off; one Configure H.323 and/or SIP Warning
warning or both of them should be enabled modes
393
45004 Configuration The FindMe mode is set to On or Remote Reconfigure FindMe mode or Warning
conflict service but the FindMe option key has reinstall the option key
been deleted
45005 Configuration H323-SIP Protocol Interworking mode is Reconfigure Interworking mode Warning
conflict set to "On" but the H323-SIP or reinstall the option key
Interworking Gateway option key has
been deleted
warning Subzone and the Cluster Subzone is
missing
warning Subzone and the Traversal Subzone is
missing
45008 Configuration Expected default link between the Configure default links Warning
warning Traversal Subzone and the Default Zone
is missing
45009 Configuration For provisioning to work correctly, Set authentication policy to Warning
warning authentication policy must be enabled on either 'Check credentials' or
the Default Zone and any other relevant 'Treat as authenticated' for each
zone that receives provisioning requests relevant zone
45012 Configuration For Presence services to work correctly, Set authentication policy to Warning
warning authentication policy must be enabled on either Check credentials or
the Default Subzone and any other Treat as authenticated for the
relevant subzone; authentication must Default Subzone and each
also be enabled on the Default Zone if the relevant subzone and zone
endpoints are not registered
45013 Configuration For phone book requests to work Set authentication policy to Warning
warning correctly, authentication policy must be either Check credentials or
enabled on the Default Subzone and any Treat as authenticated for the
other relevant subzone; authentication Default Subzone and each
must also be enabled on the Default Zone relevant subzone and zone
if the endpoints are not registered
45014 Configuration H.323 is enabled in a zone with a SIP On the relevant zone, either Warning
warning media encryption mode of "Force disable H.323 or select a
encrypted" or "Force unencrypted" different SIP media encryption
mode
45016 Configuration A zone has a SIP media encryption mode On the relevant zone, either set Warning
warning of "Best effort" or "Force encrypted" but the SIP transport to TLS or select
the transport is not TLS. TLS is required a different SIP media encryption
for encryption. mode
45017 Configuration A subzone has a SIP media encryption Either enable TLS on the SIP Warning
warning mode of "Best effort" or "Force configuration page or select a
encrypted" but TLS is not enabled. TLS is different SIP media encryption
required for encryption. mode for the relevant subzone or
Default Subzone
45018 Configuration DNS zones (including <zone_name>) Check that the SIP default Warning
warning have their SIP default transport protocol transport protocol for the DNS
set to <protocol>, but that protocol is zone and the system-wide SIP
disabled system-wide. transport settings are consistent
394
45019 Insufficient There is an insufficient number of media Increase the media port range Warning
media ports ports to support the number of licensed
calls
55001 B2BUA service Some B2BUA service specific Restart the B2BUA service Warning
restart required configuration has changed, however a
restart is required for this to take effect
55002 B2BUA The port on B2BUA for VCS Check B2BUA configuration Warning
misconfiguration communications is misconfigured (advanced settings)
55003 B2BUA Invalid trusted host IP address of Lync Check configured addresses of Warning
misconfiguration device trusted hosts
55004 B2BUA The port on B2BUA for Lync Check B2BUA configuration Warning
misconfiguration communications is misconfigured (advanced settings)
55005 B2BUA The Lync signaling destination address is Check B2BUA configuration Warning
misconfiguration misconfigured
55005 B2BUA The Lync signaling destination address is Check B2BUA configuration Warning
55006 B2BUA The Lync signaling destination port is Check B2BUA configuration Warning
55007 B2BUA The Lync transport type is misconfigured Check B2BUA configuration Warning
misconfiguration
55008 B2BUA Missing or invalid FQDN of service Check the VCS's system host Warning
misconfiguration name and domain name
55009 B2BUA Invalid IP address of service Check the VCS's LAN 1 IPv4 Warning
misconfiguration address
55010 B2BUA The B2BUA media port range end value is Check B2BUA configuration Warning
misconfiguration misconfigured (advanced settings)
55011 B2BUA The B2BUA media port range start value is Check B2BUA configuration Warning
misconfiguration misconfigured (advanced settings)
55012 B2BUA Invalid Microsoft Lync B2BUA mode Check B2BUA configuration Warning
misconfiguration
55013 B2BUA Invalid option key Check option keys Warning

misconfiguration
55014 B2BUA Invalid hop count Check B2BUA configuration Warning

misconfiguration (advanced settings)
55015 B2BUA Invalid trusted host IP address of Check configured addresses of Warning
misconfiguration transcoder trusted hosts
55016 B2BUA The setting to enable transcoders for this Check B2BUA configuration Warning
misconfiguration B2BUA is misconfigured (transcoder settings)
55017 B2BUA The port on B2BUA for transcoder Check B2BUA configuration Warning
misconfiguration communications is misconfigured (transcoder settings)
395
55018 B2BUA Transcoder address and/or port details Check B2BUA configuration Warning
misconfiguration are misconfigured (transcoder settings) and the
configured addresses of trusted
hosts
55019 B2BUA Invalid TURN server address Check B2BUA configuration Warning
misconfiguration (TURN settings)
55021 B2BUA The setting to offer TURN services for this Check B2BUA configuration Warning
misconfiguration B2BUA is misconfigured (TURN settings)
55023 B2BUA The transcoder policy rules are Check transcoder policy rules Warning
misconfiguration misconfigured configuration
55024 B2BUA The setting to use transcoder policy rules Check B2BUA configuration Warning
misconfiguration is misconfigured (transcoder settings)
55025 B2BUA The B2BUA has been enabled to use Configure one or more Warning
misconfiguration transcoders, but there are no transcoders transcoders
configured
55026 B2BUA TURN services are enabled, but there are Configure the TURN server Warning
misconfiguration no valid TURN servers configured address
55028 B2BUA The start and end media port ranges are Check the B2BUA media port Warning
misconfiguration misconfigured range settings
55029 B2BUA The media port ranges used by the B2BUA Check the port configuration for Warning
misconfiguration overlap with the media port ranges used both services
by <module>
55030 B2BUA The port used by the B2BUA for VCS Check the port configuration for Warning
misconfiguration communications is also used by <module> both services
55031 B2BUA The port used by the B2BUA for Lync Check the port configuration for Warning
misconfiguration communications is also used by <module> both services
55032 B2BUA The port used by the B2BUA for Check the port configuration for Warning
misconfiguration transcoder communications is also used both services
by <module>
55033 B2BUA No valid Lync trusted host devices have Configure at least one Lync Warning
misconfiguration been configured trusted host device
55034 B2BUA No valid transcoder trusted hosts have Configure at least one Warning
misconfiguration been configured transcoder trusted host
55035 B2BUA The B2BUA cannot connect to the Restart the B2BUA service Warning
connectivity transcoders
problem
55036 B2BUA The B2BUA cannot connect to the VCS Restart the B2BUA service Warning
connectivity
problem
55037 B2BUA The B2BUA cannot connect to Lync Check the Lync B2BUA status Warning
connectivity page for more information about
problem the problem; you will then need
to restart the B2BUA service
after making any configuration
changes
396
55101 B2BUA Invalid VCS authorized host IP address Restart the service; contact your Warning
misconfiguration Cisco representative if the
problem persists
55102 B2BUA Invalid URI format of VCS contact address Restart the service; contact your Warning
problem persists
55103 B2BUA Invalid VCS encryption mode Restart the service; contact your Warning
problem persists
55104 B2BUA Invalid VCS ICE mode Restart the service; contact your Warning
problem persists
55105 B2BUA Invalid VCS next hop host configuration Restart the service; contact your Warning
problem persists
55106 B2BUA Invalid VCS next hop liveness mode Restart the service; contact your Warning
problem persists
55107 B2BUA Invalid VCS next hop mode Restart the service; contact your Warning
problem persists
55108 B2BUA Invalid VCS next hop port Restart the service; contact your Warning
problem persists
55109 B2BUA Invalid VCS transport type Restart the service; contact your Warning
problem persists
55110 B2BUA Invalid URI format of B side contact Restart the service; contact your Warning
misconfiguration address Cisco representative if the
problem persists
55111 B2BUA Invalid B side encryption mode Restart the service; contact your Warning
problem persists
55112 B2BUA Invalid B side ICE mode Restart the service; contact your Warning
problem persists
55113 B2BUA Invalid B side next hop liveness mode Restart the service; contact your Warning
problem persists
55114 B2BUA Invalid B side next hop mode Restart the service; contact your Warning
problem persists
55115 B2BUA Invalid command listening port Restart the service; contact your Warning
problem persists
397
55116 B2BUA Invalid debug status path Restart the service; contact your Warning
problem persists
55117 B2BUA Invalid service Restart the service; contact your Warning
problem persists
55118 B2BUA Invalid software string Restart the service; contact your Warning
problem persists
55119 B2BUA Invalid URI format of transcoding service Restart the service; contact your Warning
misconfiguration contact address Cisco representative if the
problem persists
55120 B2BUA Invalid transcoding service encryption Restart the service; contact your Warning
misconfiguration mode Cisco representative if the
problem persists
55121 B2BUA Invalid transcoding service ICE mode Restart the service; contact your Warning
problem persists
55122 B2BUA Invalid transcoding service next hop Restart the service; contact your Warning
misconfiguration liveness mode Cisco representative if the
problem persists
55123 B2BUA The transcoding service transport type is Restart the service; contact your Warning
misconfiguration misconfigured Cisco representative if the
problem persists
55124 B2BUA The mandatory TURN server setting is Restart the service; contact your Warning
misconfiguration misconfigured Cisco representative if the
problem persists
55125 B2BUA Invalid VCS next hop host configuration Restart the service; contact your Warning
problem persists
55126 B2BUA Invalid VCS authorized host IP address Restart the service; contact your Warning
problem persists
55127 B2BUA Cannot start B2BUA application because Configure the System host Warning
misconfiguration FQDN configuration is missing name and Domain name on the
DNS page, and then restart the
B2BUA service
55128 B2BUA Cannot start B2BUA application because Configure the LAN 1 IPv4 Warning
misconfiguration IPv4 interface address configuration is address on the IP page, and then
missing restart the B2BUA service
55129 B2BUA Cannot start B2BUA application because Configure the cluster name on Warning
misconfiguration cluster name configuration is missing the Clustering page
55130 B2BUA Invalid cluster name Check the cluster name and then Warning
misconfiguration restart the B2BUA service
398
55131 B2BUA Invalid session refresh interval Check B2BUA configuration Warning
misconfiguration (advanced settings), then restart
the B2BUA service
55132 B2BUA Invalid call resource limit Restart the service; contact your Warning
problem persists
55133 B2BUA The B2BUA session refresh interval is Check both settings on the Warning
misconfiguration smaller than the minimum session refresh B2BUA configuration (advanced
interval settings) and then restart the
B2BUA service
55134 B2BUA Invalid minimum session refresh interval Check B2BUA configuration Warning
misconfiguration (advanced settings), then restart
the B2BUA service
55135 B2BUA A large number of Lync trusted host Review your network topology Warning
configuration devices have been configured; this may and try lowering the number of
warning impact performance, or in extreme cases trusted host devices on the
it may prevent calls from accessing B2BUA trusted hosts page.
enough network resources to connect
6nnnn [Hybrid services] This range is reserved for alarms raised by

VCS-based hybrid services.
399
Command Reference xConfiguration

The xConfiguration group of commands are used to set and change individual items of configuration. Each command
is made up of a main element followed by one or more sub-elements.
To obtain information about existing configuration, type:
xConfiguration to return all current configuration settings

xConfiguration <element> to return configuration for that element and all its sub-elements
xConfiguration <element> <subelement> to return configuration for that sub-element
To obtain information about using each of the xConfiguration commands, type:
xConfiguration ? to return a list of all elements available under the xConfiguration command
xConfiguration ?? to return a list of all elements available under the xConfiguration command, along with the
valuespace, description and default values for each element
xConfiguration <element> ? to return all available sub-elements and their valuespace, description and default
values
xConfiguration <element> <sub-element> ? to return all available sub-elements and their valuespace,
description and default values
To set a configuration item, type the command as shown. The valid values for each command are indicated in the
angle brackets following each command, using the following notation:
Table 19 Data conventions used in the CLIreference
Format Meaning
<0..63> Indicates an integer value is required. The numbers indicate the minimum and maximum
value. In this example the value must be in the range 0 to 63.
<S: 7,15> An S indicates a string value, to be enclosed in quotation marks, is required. The numbers
indicate the minimum and maximum number of characters for the string. In this example the
string must be between 7 and 15 characters long.
<Off/Direct/Indirect> Lists the set of valid values. Do not enclose the value in quotation marks.
[1..50] Square brackets indicate that you can configure more than one of this particular item. Each
item is assigned an index within the range shown.
For example IP Route [1..50] Address <S: 0,39> means that up to 50 IP routes can be
specified with each route requiring an address of up to 39 characters in length.
xConfiguration commands
All of the available xConfiguration commands are listed in the table below:
Table 20 xConfiguration CLIreference

Administration HTTP Mode: <On/Off>
Determines whether HTTP calls will be redirected to the HTTPS port. You must restart the system for any changes to take effect.
Default: On.
On: calls will be redirected to HTTPS.
Off: no HTTP access will be available.
Example: xConfiguration Administration HTTP Mode: On
400
Table 20 xConfiguration CLIreference (continued)

Administration HTTPS Mode: <On/Off>
Determines whether the VCS can be accessed via the web interface. This must be On to enable both web interface and TMS
access. You must restart the system for any changes to take effect. Default: On.
Example: xConfiguration Administration HTTPS Mode: On
Administration LCDPanel Mode: <On/Off>
Controls whether the LCD panel on the front of the VCS identifies the system. Default: On.
On: the system name and first active IP address are shown.
Off: the LCD panel reveals no identifying information about the system.
Example: xConfiguration Administration LCDPanel Mode: On
Administration SSH Mode: <On/Off>
Determines whether the VCS can be accessed via SSH and SCP. You must restart the system for any changes to take effect.
Default: On.
Example: xConfiguration Administration SSH Mode: On
Alternates Cluster Name: <S: 0,128>
The fully qualified domain name used in SRV records that address this VCS cluster, for example "cluster1.example.com". The
name can only contain letters, digits, hyphens and underscores.
Warning: if you change the cluster name after any user accounts have been configured on this VCS, you may need to reconfigure
your user accounts to use the new cluster name.
Example: xConfiguration Alternates Cluster Name: "Regional"
Alternates ConfigurationMaster: <1..6>
Specifies which peer in this cluster is the master, from which configuration will be replicated to all other peers. A cluster consists
of up to 6 peers, including the local VCS.
Example: xConfiguration Alternates ConfigurationMaster: 1
Alternates Peer [1..6] Address: <S: 0, 128>
Specifies the IP address of one of the peers in the cluster to which this VCS belongs. A cluster consists of up to 6 peers, including
the local VCS. This must be a valid IPv4 or IPv6 address.
Example: xConfiguration Alternates 1 Peer Address: "10.13.0.2"
ApacheModReqTimeOut
You can set all available properties for the request timeout using a single shorthand command.
Example: xConfiguration ApacheModReqTimeout Apachehead:20 Apachebody:20 Status:On
ApacheModReqTimeOut Apachebody: <0..120>
Modifes the number of seconds that the Apache web server waits for the request body. If the full request body is not received before
the timeout expires, Apache returns a timeout error. Default:20.
Example: xConfiguration ApacheModReqTimeout Apachebody:20
401

ApacheModReqTimeOut Apacheheader: <0..120>
Modifes the number of seconds that the Apache web server waits for the request header. If the full request header is not received
before the timeout expires, Apache returns a timeout error. Default:20.
Example: xConfiguration ApacheModReqTimeout Apacheheader:20
ApacheModReqTimeOut Status: <On/Off>
Toggles the custom Apache request timeout. Displays the status of the timeout if you omit the switch.
On: The default Apache request timeout is superseded with your settings (or the defaults) for Apachebody and Apacheheader.
Off: Apachebody and Apacheheader have no effect. The Apache request timeout defaults to 300 seconds.
Example: xConfiguration ApacheModReqTimeout Status:On
Applications ConferenceFactory Alias: <S:0,60>
The alias that will be dialed by the endpoints when the Multiway feature is activated. This must be pre-configured on all endpoints
that may be used to initiate the Multiway feature.
Example: xConfiguration Applications ConferenceFactory Alias: "[email protected]"
Applications ConferenceFactory Mode: <On/Off>
The Mode option allows you to enable or disable the Conference Factory application. Default: Off.
Example: xConfiguration Applications ConferenceFactory Mode: Off
Applications ConferenceFactory Range End: <1..65535>
The last number of the range that replaces %% in the template used to generate a conference alias. Default: 65535.
Example: xConfiguration Applications ConferenceFactory Range End: 30000
Applications ConferenceFactory Range Start: <1..65535>
The first number of the range that replaces %% in the template used to generate a conference alias. Default: 65535.
Example: xConfiguration Applications ConferenceFactory Range Start: 10000
Applications ConferenceFactory Template: <S:0,60>
The alias that the VCS will tell the endpoint to dial in order to create a Multiway conference on the MCU. This alias must route to
the MCU as a fully-qualified SIP alias
Example: Applications ConferenceFactory Template: "563%%@example.com"
Applications External Status [1..10] Filename: <S:0,255>
XML file containing status that is to be attached for an external application.
Example: xConfiguration Applications External Status 1 Filename: "foo.xml"
Applications External Status [1..10] Name: <S:0,64>
Descriptive name for the external application whose status is being referenced.
Example: xConfiguration Applications External Status 1 Name: "foo"
402

Applications Presence Server Mode: <On/Off>
Enables and disables the SIMPLE Presence Server. SIP must also be enabled for the Presence Server to function. Default: Off.
Example: xConfiguration Applications Presence Server Mode: On
Applications Presence Server Publication ExpireDelta: <30..7200>
Specifies the maximum time (in seconds) within which a publisher must refresh its publication.
Default: 1800
Example: xConfiguration Applications Presence Server Publication ExpireDelta: 1800
Applications Presence Server Subscription ExpireDelta: <30..7200>
Specifies the maximum time (in seconds) within which a subscriber must refresh its subscription. Default: 3600.
Example: xConfiguration Applications Presence Server Subscription ExpireDelta: 3600
Applications Presence User Agent ExpireDelta: <1..65534>
Specifies the lifetime value (in seconds) the Presence User Agent will advertise in the PUBLISH messages it sends to the Presence
Server. The Presence User Agent will refresh its PUBLISH messages at 75% of this value (to keep them active). The Presence
Server may reduce this value in its responses.
Default: 3600
Example: xConfiguration Applications Presence User Agent ExpireDelta: 3600
Applications Presence User Agent Mode: <On/Off>
Enables and disables the SIMPLE Presence User Agent (PUA). The PUA provides presence information on behalf of registered
endpoints. SIP mode must also be enabled for the PUA to function. Default: Off.
Example: xConfiguration Applications Presence User Agent Mode: Off
Applications Presence User Agent Presentity Idle Status: <Offline/Online>
Default presentity status published by the Presence User Agent. Default: Online.
Online: publish registered endpoints as online.
Offline: publish registered endpoints as offline.
Example: xConfiguration Applications Presence User Agent Presentity Idle Status: Online
Applications Presence User Agent RetryDelta: <1..65534>
Specifies the time (in seconds) after which the Presence User Agent will attempt to resend a PUBLISH to the Presence Server.
This will occur if the original attempt failed due to resource issues or other transitory errors. Default: 1800.
Example: xConfiguration Applications Presence User Agent RetryDelta: 1800
Authentication ADS ADDomain: <S: 0,255>
The Kerberos realm used when the VCS joins the AD domain. Note: this field is case sensitive.
Example: xConfiguration Authentication ADS ADDomain: CORPORATION.INT
Authentication ADS Clockskew: <1..65535>
Maximum allowed clockskew between the VCS and the KDC before the Kerberos message is assumed to be invalid (in seconds).
Default: 300.
Example: xConfiguration Authentication ADS Clockskew: 300
403

Authentication ADS CipherSuite: <S:1,2048>
Specifies the cipher suite to use when the VCS makes a TLS-encrypted LDAPconnection to join the ADdomain. The command
accepts a string in the 'OpenSSLciphers' format (See https://www.openssl.org/docs/apps/ciphers.html#CIPHER-LIST-FORMAT).
Example:xConfiguration Authentication ADS CipherSuite: "HIGH:MEDIUM:!ADH:!aNULL:!eNULL:-AES128-

SHA256:@STRENGTH"
Authentication ADS DC [1..5] Address: <S: 0,39>
The address of a domain controller that can be used when the VCS joins the AD domain. Not specifying a specific AD will result
the use of DNS SRV queries to find an AD.
Example: xConfiguration Authentication ADS DC 1 Address: "192.168.0.0"
Authentication ADS Encryption: <Off/TLS>
Sets the encryption to use for the LDAP connection to the ADS server. Default: TLS.
Example: xConfiguration Authentication ADS Encryption: TLS
Authentication ADS KDC [1..5] Address: <S: 0,39>
The address of a Kerberos Distribution Center (KDC) to be used when connected to the AD domain. Not specifying a specific KDC
will result in the use of DNS SRV queries to find a KDC.
Example: xConfiguration Authentication ADS KDC 1 Address: "192.168.0.0"
Authentication ADS KDC [1..5] Port: <1..65534>
Specifies the port of a KDC that can be used when the VCS joins the AD domain. Default: 88.
Example: xConfiguration Authentication ADS KDC 1 Port: 88
Authentication ADS MachineName: <S: 0..15>
This overides the default NETBIOS machine name used when the VCS joins the AD domain.
Example: xConfiguration Authentication ADS MachineName: "short_name"
Authentication ADS MachinePassword Refresh: <On/Off>
Determines if this samba client should refresh its machine password every 7 days, when joined to the AD domain. Default: On.
Example: xConfiguration Authentication ADS MachinePassword Refresh: On
Authentication ADS Mode: <On/Off>
Indicates if the VCS should attempt to form a relationship with the AD. Default: Off.
Example: xConfiguration Authentication ADS Mode: On
Authentication ADS SPNEGO: <Enabled/Disabled>
Indicates if SPNEGO (Simple and Protected GSSAPI Negotiation Mechanism) is used when the client (the VCS) authenticates with
the server (the AD domain controller). Default: Enabled.
Example: xConfiguration Authentication ADS SPNEGO: Enabled
404

Authentication ADS SecureChannel: <Auto/Enabled/Disabled>
Indicates if data transmitted from the VCS to an AD domain controller is sent over a secure channel. Default: Auto.
Example: xConfiguration Authentication ADS SecureChannel: Auto
Authentication ADS Workgroup: <S: 0,15>
The workgroup used when the VCS joins the AD domain.
Example: xConfiguration Authentication ADS Workgroup: "corporation"
Authentication Account Admin Account [1..n] AccessAPI: <On/Off>
Determines whether this account is allowed to access the system's status and configuration via the Application Programming
Interface (API). Default: On.
Example: xConfiguration Authentication Account Admin Account 1 AccessAPI: On
Authentication Account Admin Account [1..n] AccessWeb: <On/Off>
Determines whether this account is allowed to log in to the system using the web interface. Default: On.
Example: xConfiguration Authentication Account Admin Account 1 AccessWeb: On
Authentication Account Admin Account [1..n] Enabled: <On/Off>
Indicates if the account is enabled or disabled. Access will be denied to disabled accounts. Default: On.
Example: xConfiguration Authentication Account Admin Account 1 Enabled: On
Authentication Account Admin Account [1..n] Name: <S: 0, 128>
The username for the administrator account.
Example: xConfiguration Authentication Account Admin Account 1 Name: "bob_smith"
Authentication Account Admin Account [1..n] Password: <Password>
The password that this administrator will use to log in to the VCS.
Example: xConfiguration Authentication Account Admin Account 1 Password: "abcXYZ_123"
Authentication Account Admin Group [1..n] AccessAPI: <On/Off>
Determines whether members of this group are allowed to access the system's status and configuration using the Application
Programming Interface (API). Default: On.
Example: xConfiguration Authentication Account Admin Group 1 AccessAPI: On
Authentication Account Admin Group [1..n] AccessWeb: <On/Off>
Determines whether members of this group are allowed to log in to the system using the web interface. Default: On.
Example: xConfiguration Authentication Account Admin Group 1 AccessWeb: On
Authentication Account Admin Group [1..n] Enabled: <On/Off>
Indicates if the group is enabled or disabled. Access will be denied to members of disabled groups. Default: On.
Example: xConfiguration Authentication Account Admin Group 1 Enabled: On
405

Authentication Account Admin Group [1..n] Name: <S: 0, 128>
The name of the administrator group.
Example: xConfiguration Authentication Account Admin Group 1 Name: "administrators"
Authentication Certificate Crlcheck: <None/Peer/All>
Specifies whether HTTPS client certificates are checked against certificate revocation lists (CRLs). CRL data is uploaded to the
VCS via the CRL management page. Default: All.
Peer: only the CRL associated with the CA that issued the client's certificate is checked.
All: all CRLs in the trusted certificate chain of the CA that issued the client's certificate are checked.
Example: xConfiguration Authentication Certificate Crlcheck: All
Authentication Certificate Crlinaccessible: <Ignore/Fail>
Controls the revocation list checking behavior if the revocation status cannot be established, for example if the revocation source
cannot be contacted or no appropriate revocation list is present. Default: Ignore.
Ignore: treat the certificate as not revoked.
Fail: treat the certificate as revoked (and thus do not allow the TLS connection).
Example: xConfiguration Authentication Certificate Crlinaccessible: Ignore
Authentication Certificate Mode: <NotRequired/Validation/Authentication>
Controls the level of security required to allow client systems (typically web browsers) to communicate with the VCS over HTTPS.
Default: NotRequired.
NotRequired : the client system does not have to present any form of certificate.
Validation : the client system must present a valid certificate that has been signed by a trusted certificate authority (CA). Note that a
restart is required if you are changing from Not required to Certificate validation.
Authentication : the client system must present a valid certificate that has been signed by a trusted CA and contains the client's
authentication credentials. When this mode is enabled, the standard login mechanism is no longer available.
Example: xConfiguration Authentication Certificate Mode: NotRequired
Authentication Certificate UsernameRegex: <String>
The regular expression to apply to the client certificate presented to the VCS. Use the (? regex) syntax to supply names for capture
groups so that matching sub-patterns can be substituted in the associated template. Default: /Subject:.*CN= (? ([^,\]|(\,))*)/m
Example: xConfiguration Authentication Certificate UsernameRegex: "/Subject:.*CN= (? ([^,\]|(\,))*)/m"
Authentication Certificate UsernameTemplate: <String>
A template containing a mixture of fixed text and the capture group names used in the Regex. Delimit each capture group name
with # , for example, prefix#Group1#suffix. Each capture group name will be replaced with the text obtained from the regular
expression processing. The resulting string is used as the user's authentication credentials (username). Default:
#captureCommonName#
Example: xConfiguration Authentication Certificate UsernameTemplate: "#captureCommonName#"
406

Authentication H350 BindPassword: <S: 0, 60>
Sets the password to use when binding to the LDAP server.
Example: xConfiguration Authentication H350 BindPassword: "abcXYZ_123"
Authentication H350 BindSaslMode: <None/DIGEST-MD5>
The SASL (Simple Authentication and Security Layer) mechanism to use when binding to the LDAP server. Default: DIGEST-MD5.
DIGEST-MD5: the DIGEST-MD5 mechanism is used.
Example: xConfiguration Authentication H350 BindSaslMode: DIGEST-MD5
Authentication H350 BindUserDn: <S: 0, 500>
Sets the user distinguished name to use when binding to the LDAP server.
Example: xConfiguration Authentication H350 BindUserDn: "manager"
Authentication H350 BindUserName: <S: 0, 500>
Sets the username to use when binding to the LDAP server. Only applies if using SASL.
Example: xConfiguration Authentication H350 BindUserName: "manager"
Authentication H350 DirectoryBaseDn: <S: 0, 500>
Sets the Distinguished Name to use when connecting to an LDAP server.
Example: xConfiguration Authentication H350 DirectoryBaseDn: "dc=example,dc=company,dc=com"
Authentication H350 LdapEncryption: <Off/TLS>
Sets the encryption to use for the connection to the LDAP server. Default : TLS.
Off : no encryption is used.
TLS : TLS encryption is used.
Example: xConfiguration Authentication H350 LdapEncryption: TLS
Authentication H350 LdapServerAddress: <S: 0, 256>
The IP address or Fully Qualified Domain Name of the LDAP server to use when making LDAP queries for device authentication.
Example: xConfiguration Authentication H350 LdapServerAddress: "ldap_server.example.com"
Authentication H350 LdapServerAddressResolution: <AddressRecord/ServiceRecord>
Sets how the LDAP server address is resolved if specified as an FQDN. Default: AddressRecord.
Address record: DNS A or AAAA record lookup.
SRV record: DNS SRV record lookup.
Example: xConfiguration Authentication H350 LdapServerAddressResolution: AddressRecord
Authentication H350 LdapServerPort: <1..65535>
Sets the IP port of the LDAP server to use when making LDAP queries for device authentication. Typically, non-secure connections
use 389 and secure connections use 636. Default : 389
Example: xConfiguration Authentication H350 LdapServerPort: 389
407

Authentication H350 Mode: <On/Off>
Enables or disables the use of an H.350 directory for device authentication. Default: Off.
Example: xConfiguration Authentication H350 Mode: Off
Authentication LDAP AliasOrigin: <LDAP/Endpoint/Combined>
Determines how aliases are checked and registered. Default: LDAP.
LDAP: the aliases presented by the endpoint are checked against those listed in the LDAP database.
Endpoint: the aliases presented by the endpoint are used; any in the LDAP database are ignored.
Combined: the aliases presented by the endpoint are used in addition to any listed in the LDAP database.
Example: xConfiguration Authentication LDAP AliasOrigin: LDAP
Authentication Password: <S: 0, 215>
The password used by the VCS when authenticating with another system. The maximum plaintext length is 128 characters, which
is then encrypted. Note: this does not apply to traversal client zones.
Example: xConfiguration Authentication Password: "password123"
Authentication Remote Digest Cache ExpireCheckInterval: <0..65535>
The interval between digest authentication cache expiration checks in seconds. Default: 600
Example: xConfiguration Authentication Remote Digest Cache ExpireCheckInterval: 600
Authentication Remote Digest Cache Lifetime: <0..43200>
The lifetime of digest authentication interim hashes in seconds. Default: 600
Example: xConfiguration Authentication Remote Digest Cache Lifetime: 600
Authentication Remote Digest Cache Limit: <0..65535>
The interval between digest authentication cache expiration checks in seconds. Default: 10000
Example: xConfiguration Authentication Remote Digest Cache Limit: 10000
Authentication Remote Digest Cache Mode: <On/Off>
Controls whether the digest authentication cache is enabled. Default: On
Example: xConfiguration Authentication Remote Digest Cache Mode: On
Authentication StrictPassword Enabled: <On/Off>
Determines whether local administrator account passwords must meet a minimum level of complexity before they are accepted. In
addition, passwords must not: be based on a dictionary word contain too many consecutive characters such as "abc" or "123",
contain too few different characters or be palindromes. Default: Off.
On : local administrator account passwords must meet the complexity requirements.
Off : passwords are not checked for complexity.
Example: xConfiguration Authentication StrictPassword Enabled: Off
Authentication StrictPassword MaximumConsecutiveRepeated: <0..255>
The maximum number of times the same character can be repeated consecutively. A value of 0 disables this check. Default: 0
Example: xConfiguration Authentication StrictPassword MaximumConsecutiveRepeated: 0
408

Authentication StrictPassword MinimumClasses: <0..4>
The minimum number of character classes that must be present. There are four character classes: digit, upper case, lower case
and special. Use this setting if you want to mandate the use of 2-3 different character classes without requiring all of them to be
present. A value of 0 disables this check. Default: 0.
Example: xConfiguration Authentication StrictPassword MinimumClasses: 0
Authentication StrictPassword MinimumDigits: <0..255>
The minimum number of digits that must be present. A value of 0 disables this check. Default: 2.
Example: xConfiguration Authentication StrictPassword MinimumDigits: 2
Authentication StrictPassword MinimumLength: <6..255>
The minimum length of the password. Default: 15.
Example: xConfiguration Authentication StrictPassword MinimumLength: 15
Authentication StrictPassword MinimumLowerCase: <0..255>
The minimum number of lower case characters that must be present. A value of 0 disables this check. Default: 2.
Example: xConfiguration Authentication StrictPassword MinimumLowerCase: 2
Authentication StrictPassword MinimumOther: <0..255>
The minimum number of special characters that must be present. A special character is anything that is not a letter or a digit. A
value of 0 disables this check. Default: 2
Example: xConfiguration Authentication StrictPassword MinimumOther: 2
Authentication StrictPassword MinimumUpperCase: <0..255>
The minimum number of upper case characters that must be present. A value of 0 disables this check. Default : 2
Example: xConfiguration Authentication StrictPassword MinimumUpperCase: 2
Authentication UserName: <S: 0, 128>
The username used by the VCS when authenticating with another system. Note: this does not apply to traversal client zones.
Example: xConfiguration Authentication UserName: "user123"
Bandwidth Default: <64..65535>
The bandwidth (in kbps) to use on calls managed by the VCS where no bandwidth has been specified by the endpoint. Default: 384.
Example: xConfiguration Bandwidth Default: 384
Bandwidth Downspeed PerCall Mode: <On/Off>
Determines whether the VCS attempts to downspeed a call if there is insufficient per-call bandwidth available to fulfill the request.
Default: On.
On: the VCS will attempt to place the call at a lower bandwidth.
Off: the call will be rejected.
Example: xConfiguration Bandwidth Downspeed PerCall Mode: On
409

Bandwidth Downspeed Total Mode: <On/Off>
Determines whether the VCS attempts to downspeed a call if there is insufficient total bandwidth available to fulfill the request.
Default: On.
On: the VCS will attempt to place the call at a lower bandwidth.
Off: the call will be rejected.
Example: xConfiguration Bandwidth Downspeed Total Mode: On
Bandwidth Link [1..3000] Name: <S: 1, 50>
Assigns a name to this link.
Example: xConfiguration Bandwidth Link 1 Name: "HQ to BranchOffice"
Bandwidth Link [1..3000] Node1 Name: <S: 0, 50>
Specifies the first zone or subzone to which this link will be applied.
Example: xConfiguration Bandwidth Link 1 Node1 Name: "HQ"
Bandwidth Link [1..3000] Node2 Name: <S: 0, 50>
Specifies the second zone or subzone to which this link will be applied.
Example: xConfiguration Bandwidth Link 1 Node2 Name: "BranchOffice"
Bandwidth Link [1..3000] Pipe1 Name: <S: 0, 50>
Specifies the first pipe to be associated with this link.
Example: xConfiguration Bandwidth Link 1 Pipe1 Name: "512Kb ASDL"
Bandwidth Link [1..3000] Pipe2 Name: <S: 0, 50>
Specifies the second pipe to be associated with this link.
Example: xConfiguration Bandwidth Link 1 Pipe2 Name: "2Gb Broadband"
Bandwidth Pipe [1..1000] Bandwidth PerCall Limit: <1..100000000>
If this pipe has limited per-call bandwidth, sets the maximum amount of bandwidth (in kbps) available for any one call. Default:
1920.
Example: xConfiguration Bandwidth Pipe 1 Bandwidth PerCall Limit: 256
Bandwidth Pipe [1..1000] Bandwidth PerCall Mode: <Limited/Unlimited/NoBandwidth>
Determines whether or not this pipe is limiting the bandwidth of individual calls. Default: Unlimited.
NoBandwidth: no bandwidth available. No calls can be made on this pipe.
Example: xConfiguration Bandwidth Pipe 1 Bandwidth PerCall Mode: Limited
Bandwidth Pipe [1..1000] Bandwidth Total Limit: <1..100000000>
If this pipe has limited bandwidth, sets the maximum bandwidth (in kbps) available at any one time on the pipe. Default: 500000.
Example: xConfiguration Bandwidth Pipe 1 Bandwidth Total Limit: 1024
410

Bandwidth Pipe [1..1000] Bandwidth Total Mode: <Limited/Unlimited/NoBandwidth>
Determines whether or not this pipe is enforcing total bandwidth restrictions. Default: Unlimited.
NoBandwidth: no bandwidth available. No calls can be made on this pipe.
Example: xConfiguration Bandwidth Pipe 1 Bandwidth Total Mode: Limited
Bandwidth Pipe [1..1000] Name: <S: 1, 50>
Assigns a name to this pipe.
Example: xConfiguration Bandwidth Pipe 1 Name: "512Kb ASDL"
Call Loop Detection Mode: <On/Off>
Specifies whether the VCS will check for call loops. Default: On.
Example: xConfiguration Call Loop Detection Mode: On
Call Routed Mode: <Always/Optimal>
Specifies whether the VCS routes the signaling for calls. Default: Always.
Always: the VCS will always route the call signaling.
Optimal: if possible, the VCS will remove itself from the call signaling path, which may mean the call does not consume a call
license.
Example: xConfiguration Call Routed Mode: Always
Call Services CallsToUnknownIPAddresses: <Off/Direct/Indirect>
The way in which the VCS attempts to call systems that are not registered with it or one of its neighbors. Default: Indirect.
Direct: allows an endpoint to make a call to an unknown IP address without the VCS querying any neighbors. The call setup would
occur just as it would if the far end were registered directly to the local system.
Indirect: upon receiving a call to an unknown IP address, the VCS will query its neighbors for the remote address and if permitted
will route the call through the neighbor.
Off: endpoints registered directly to the VCS may only call an IP address of a system also registered directly to that VCS.
Example: xConfiguration Call Services CallsToUnknownIPAddresses: Indirect
Call Services Fallback Alias: <S: 0, 60>
Specifies the alias to which incoming calls are placed for calls where the IP address or domain name of the VCS has been given
but no callee alias has been specified.
Example: xConfiguration Call Services Fallback Alias: "[email protected]"
CollaborationEdge Enabled:<On/Off>
Enables or disables Mobile and Remote Access on this VCS.
Example: xConfiguration CollaborationEdge Enabled: On
CollaborationEdge JabbercEnabled:<On/Off>
Enables or disables Jabber Guest services on this VCS.
Example: xConfiguration JabbercEnabled: Off
411

CollaborationEdge JabbercProxyProtocol:<http/https>
Selects the protocol used to proxy Jabber Guest services requests through the VCS.
Example: xConfiguration JabbercProxyProtocol: https
CollaborationEdge SSOIdP <index> Digest:<sha1/sha256>
Changes the hash algorithm that the VCS uses when signing SAML authentication requests given to the client.
<index> is an integer distinguishing a particular IdP from the list that is configured on the VCS.
Example: xConfiguration CollaborationEdge SSO IdP 1 Digest: sha256
CollaborationEdge SsoAlwaysAvailable:<On/Off>
Determines whether the VCS Control will check if the user's home node has SSO available.
On: The VCS Expressway always tells the client that SSO is available, without actually checking the home node.
Off: Allow the VCS Control to check if SSO is available on the user's home node before the VCS Expressway responds to the client.
Example:xConfiguration CollaborationEdge SsoAlwaysAvailable: Off
Note:The default value Off corresponds to the following default on the web UI: Check for internal SSOavailability:Yes
CollaborationEdge SsoEnabled:<On/Off>
Toggles Single Sign-On for mobile and remote access to UC services.
Example:xConfiguration CollaborationEdge SsoEnabled: Off
CollaborationEdge SsoSipTokenExtraTtl:<0..172800>
Extends the lifetime of the SIP authorization token by the supplied number of seconds.
Example:xConfiguration CollaborationEdge SsoSipTokenExtraTtl: 0
CollaborationEdgeDeployments <index> DeploymentId:<1..65535>
Changes the deployment IDof a particular deployment.
Example:xConfiguration CollaborationEdgeDeployments 1 DeploymentId: 5
CollaborationEdgeDeployments <index> UserReadableName:<String>
Enter a name for this deployment. You can use multiple deployments to partition the Unified Communications services provided via
this VCS. See Using deployments to partition Unified Communications services.
Example:xConfiguration CollaborationEdgeDeployments 1 UserReadableName: StagingDeployment
DNS PerDomainServer [1..5] Address: <S: 0, 39>
The IP address of the DNS server to use only when resolving hostnames for the associated domain names.
Example: xConfiguration DNS PerDomainServer 1 Address: "192.168.12.1"
DNS PerDomainServer [1..5] Domain1: <S: 0, 39>
The first domain name to be resolved by this particular DNS server.
Example: xConfiguration DNS PerDomainServer 1 Domain1: "dept.example.com"
412

DNS PerDomainServer [1..5] Domain2: <S: 0, 39>
The second domain name to be resolved by this particular DNS server.
Example: xConfiguration DNS PerDomainServer 1 Domain2: "other.example.com"
DNS Server [1..5] Address: <S: 0, 39>
The IP address of a default DNS server to use when resolving domain names. You can specify up to 5 servers. These default DNS
servers are used if there is no per-domain DNS server defined for the domain being looked up.
Example: xConfiguration DNS Server 1 Address: "192.168.12.0"
EdgeConfigServer CredentialTtl: <0..604800>
Does not apply to SSO authentications.
Specifies the lifetime of the authentication token issued by the VCS to a successfully authenticated client. A client that successfully
authenticates should request a refresh before this token expires, or it will need to re-authenticate.
Example:EdgeConfigServer CredentialTtl: 28800
EdgeConfigServer PurgeInterval: <0..604800>
Does not apply to SSO authentications.
Specifies how long the VCS waits between cache clearing operations. Only expired tokens are removed when the cache is
cleared, so this setting is the longest possible time that an expired token can remain in the cache.
Example:EdgeConfigServer PurgeInterval: 43200
EdgeConfigServer RateLimitLogins: <0..100>
Limits the number of times that any user's credentials can authorize via VCS per rate control period. Any device using the same
user credentials contributes to the number.
After the limit is reached, any further attempts to use these credentials are rejected until the current rate control period expires.
Enter 0 to disable the rate control feature.
Example: xConfiguration EdgeConfigServer RateLimitLogins: 3
EdgeConfigServer RateLimitPeriod: <0..86400>
Defines the period (in seconds) over which authorizations are counted. If rate control is enabled, then a user's first authorization
starts the counter and the timer. When the rate control period expires, the counter is reset and a new period will start with the
user's next authorization.
Enter 0 to disable the rate control feature.
Example: xConfiguration EdgeConfigServer RateLimitPeriod: 300
ErrorReport Contact: <S: 0, 128>
An optional contact email address for follow up on incident reports if required.
Example: xConfiguration ErrorReport Contact: "bob smith"
ErrorReport CoreDump: <On/Off>
Determines whether diagnostic core dump files are created. Default: On.
Example: xConfiguration ErrorReport CoreDump: On
413

ErrorReport Mode: <On/Off>
Determines whether details of application failures are automatically sent to a web service. Default: Off.
Example: xConfiguration ErrorReport Mode: Off
ErrorReport Proxy: <S: 0, 128>
An optional proxy server to use for the HTTP/HTTPS connections to the incident reporting server.
Example: xConfiguration ErrorReport Proxy: https://proxy_address/submiterror/
ErrorReport Url: <S: 0, 128>
The URL of the web service to which details of application failures are sent. Default: https://cc-
reports.cisco.com/submitapplicationerror/
Example: xConfiguration ErrorReport Url: https://cc-reports.cisco.com/submitapplicationerror/
Ethernet [1..2] IP V4 Address: <S: 7,15>
Specifies the IPv4 address of the specified LAN port. Note: you must restart the system for any changes to take effect.
Example: xConfiguration Ethernet 1 IP V4 Address: "192.168.10.10"
Ethernet [1..2] IP V4 StaticNAT Address: <S:7,15>
If the VCS is operating in static NAT mode, this specifies the external public IPv4 address of that static NAT. You must restart the
system for any changes to take effect.
Example: xConfiguration Ethernet 1 IP V4 StaticNAT Address: "64.22.64.85"
Ethernet [1..2] IP V4 StaticNAT Mode: <On/Off>
Specifies whether the VCS is located behind a static NAT. You must restart the system for any changes to take effect. Default: Off.
Example: xConfiguration Ethernet 1 IP V4 StaticNAT Mode: On
Ethernet [1..2] IP V4 SubnetMask: <S: 7,15>
Specifies the IPv4 subnet mask of the specified LAN port. You must restart the system for any changes to take effect.
Example: xConfiguration Ethernet 1 IP V4 SubnetMask: "255.255.255.0"
Ethernet [1..2] IP V6 Address: <S: 0, 39>
Specifies the IPv6 address of the specified LAN port. You must restart the system for any changes to take effect.
Example: xConfiguration Ethernet 1 IP V6 Address: "2001:db8::1428:57ab"
Ethernet [1..2] Speed: <Auto/10half/10full/100half/100full/1000full
Sets the speed of the Ethernet link from the specified LAN port. Use Auto to automatically configure the speed. You must restart the
system for any changes to take effect. Default: Auto.
Example: xConfiguration Ethernet 1 Speed: Auto
ExternalManager Address: <S: 0, 128>
Sets the IP address or Fully Qualified Domain Name (FQDN) of the external manager.
Example: xConfiguration ExternalManager Address: "192.168.0.0"
414

ExternalManager Path: <S: 0, 255>
Sets the URL of the external manager. Default: tms/public/external/management/SystemManagementService.asmx
Example: xConfiguration ExternalManager Path: "tms/public/external/management/SystemManagementService.asmx"
ExternalManager Protocol: <HTTP/HTTPS>
The protocol used to connect to the external manager. Default: HTTPS.
Example: xConfiguration ExternalManager Protocol: HTTPS
ExternalManager Server Certificate Verification Mode: <On/Off>
Controls whether the certificate presented by the external manager is verified. Default: On.
Example: xConfiguration ExternalManager Server Certificate Verification Mode: On
H323 Gatekeeper AutoDiscovery Mode: <On/Off>
Determines whether or not the VCS responds to gatekeeper discovery requests from endpoints. Default: On.
Example: xConfiguration H323 Gatekeeper AutoDiscovery Mode: On
H323 Gatekeeper CallSignaling PortRange End: <1024..65534>
Specifies the upper port in the range to be used by calls once they are established. Default: 19999.
Example: xConfiguration H323 Gatekeeper CallSignaling PortRange End: 19999
H323 Gatekeeper CallSignaling PortRange Start: <1024..65534>
Specifies the lower port in the range to be used by calls once they are established. Default: 15000.
Example: xConfiguration H323 Gatekeeper CallSignaling PortRange Start: 15000
H323 Gatekeeper CallSignaling TCP Port: <1024..65534>
Specifies the port that listens for H.323 call signaling. Default: 1720.
Example: xConfiguration H323 Gatekeeper CallSignaling TCP Port: 1720
H323 Gatekeeper CallTimeToLive: <60..65534>
Specifies the interval (in seconds) at which the VCS polls the endpoints in a call to verify that they are still in the call. Default: 120.
Example: xConfiguration H323 Gatekeeper CallTimeToLive: 120
H323 Gatekeeper Registration ConflictMode: <Reject/Overwrite>
How the system behaves if an endpoint attempts to register an alias currently registered from another IP address. Default: Reject.
Reject: denies the registration.
Overwrite: deletes the original registration and replaces it with the new registration.
Example: xConfiguration H323 Gatekeeper Registration ConflictMode: Reject
H323 Gatekeeper Registration UDP Port: <1024..65534>
Specifies the port to be used for H.323 UDP registrations. Default: 1719.
Example: xConfiguration H323 Gatekeeper Registration UDP Port: 1719
415

H323 Gatekeeper TimeToLive: <60..65534>
The interval (in seconds) at which an H.323 endpoint must re-register with the VCS to confirm that it is still functioning. Default:
1800.
Example: xConfiguration H323 Gatekeeper TimeToLive: 1800
H323 Gateway CallerId: <IncludePrefix/ExcludePrefix>
Specifies whether the prefix of the ISDN gateway is inserted into the caller's E.164 number presented on the destination endpoint.
Including the prefix allows the recipient to directly return the call. Default: ExcludePrefix.
IncludePrefix: inserts the ISDN gateway's prefix into the source E.164 number.
ExcludePrefix: only displays the source E.164 number.
Example: xConfiguration H323 Gateway CallerId: ExcludePrefix
H323 Mode: <On/Off>
Determines whether or not the VCS will provide H.323 gatekeeper functionality. Default: On.
Example: xConfiguration H323 Mode: On
Interworking BFCP Compatibility Mode: <Auto/TAA/Draft>
Controls the compatibility settings of the SIP to H.323 interworking BFCP component. Default: Auto.
Example: xConfiguration Interworking BFCP Compatibility Mode: Auto
Interworking Encryption Mode: <Auto/Off>
Determines whether or not the VCS will allow encrypted calls between SIP and H.323 endpoints. Default: Auto.
Off: interworked calls will never be encrypted.
Auto: interworked calls will be encrypted if the endpoints request it.
Example: xConfiguration Interworking Encryption Mode: Auto
Interworking Encryption Replay Protection Mode: <On/Off>
Controls whether the VCS will perform replay protection for incoming SRTP packets when interworking a call. Default: Off.
On: replayed SRTP packets will be dropped by the VCS.
Off: the VCS will not check for replayed SRTP packets.
Example: xConfiguration Interworking Encryption Replay Protection Mode: Off
Interworking Mode: <On/Off/RegisteredOnly>
Determines whether or not the VCS will act as a gateway between SIP and H.323 calls. Default: RegisteredOnly.
Off: the VCS will not act as a SIP-H.323 gateway.
On: the VCS will act as SIP-H.323 gateway regardless of whether the endpoints are locally registered.
RegisteredOnly: the VCS will act as a SIP-H.323 gateway but only if at least one of the endpoints is locally registered.
Example: xConfiguration Interworking Mode: On
416

Interworking Require Invite Header Mode: <On/Off>
Controls whether the SIP to H.323 interworking function sends com.tandberg.sdp.duo.enable and com.tandberg.sdp.bfcp.udp in the
require header for dialog forming INVITEs. Default: Off.
Example: xConfiguration Interworking Require Invite Header Mode: Off"
IP DNS Domain Name: <S: 0, 128>
The name to be appended to an unqualified host name before querying the DNS server. Used when attempting to resolve
unqualified domain names for NTP, LDAP, external manager and remote syslog servers. May also be used along with the System
host name to identify references to this VCS in SIP messaging.
Example: xConfiguration IP DNS Domain Name: "example.com"
IP DNS Hostname : <S: 0, 63>
The DNS host name that this system is known by. This is not the fully-qualified domain name, just the host label portion. The name
can only contain letters, digits, hyphens and underscores. The first character must be a letter and the last character must be a letter
or a digit.
Example: xConfiguration IP DNS Hostname: "localsystem"
IP DNS MaxPort: <1024..65535>
The upper source port in the range used for sending DNS queries. Requests choose a random port from this range. Warning: setting
a small source port range increases your vulnerability to DNS spoofing attacks. Default: 65535.
Example: xConfiguration IP DNS MaxPort: 65535
IP DNS MinPort: <1024..65535>
The lower source port in the range used for sending DNS queries. Requests choose a random port from this range. Warning: setting
a small source port range increases your vulnerability to DNS spoofing attacks. Default: 1024.
Example: xConfiguration IP DNS MinPort: 1024
IP DNS UseEphemeralPortRange: <On/Off>
Determines whether outgoing DNS queries use the system's normal ephemeral port range, or a custom port range that you can
configure. Default: On.
Example: xConfiguration IP DNS UseEphemeralPortRange: On
IP Ephemeral PortRange End: <1024..65534>
The highest port in the range used for ephemeral outbound connections not otherwise constrained by VCS call processing. Default:
35999.
Example: xConfiguration IP Ephemeral PortRange End: 35999
IP Ephemeral PortRange Start: <1024..65534>
The lowest port in the range used for ephemeral outbound connections not otherwise constrained by VCS call processing. Default:
30000.
Example: xConfiguration IP Ephemeral PortRange Start: 30000
IP External Interface: <LAN1/LAN2>
Defines which LAN interface is externally facing. Default: LAN1.
Example: xConfiguration IP External Interface: LAN1
417

IP Gateway: <S: 7,15>
Specifies the IPv4 gateway of the VCS. Note: you must restart the system for any changes to take effect. Default: 127.0.0.1
Example: xConfiguration IP Gateway: "192.168.127.0"
IP QoS Mode: <None/DiffServ>
The type of QoS (Quality of Service) tags to apply to all signaling and media packets. You must restart the system for any changes to
take effect. Default: None.
None: no specific QoS tagging is applied.
DiffServ: puts the specified Tag value in the TOS (Type Of Service) field of the IPv4 header or TC (Traffic Class) field of the IPv6
header.
Example: xConfiguration IP QoS Mode: DiffServ
IP QoS Value: <0..63>
The value to stamp onto all signaling and media traffic routed through the system. You must restart the system for any changes to
take effect. Default: 0.
Example: xConfiguration IP QoS Value: 16
IP RFC4821 Mode: <Auto/Enabled/Disabled>
Determines when RFC4821 Packetization Layer Path MTU Discovery is used by the VCS network interface. Default: Disabled.
Enabled: Packetization layer MTU probing is always performed.
Auto: Disabled by default, enabled when an ICMP black hole is detected.
Disabled: Packetization layer MTU probing is not performed.
Example: xConfiguration IP RFC4821 Mode: Disabled
IP Route [1..50] Address: <S: 0, 39>
Specifies an IP address used in conjunction with the Prefix Length to determine the network to which this route applies.
Example: xConfiguration IP Route 1 Address: "128.168.0.0"
IP Route [1..50] Gateway: <S: 0, 39>
Specifies the IP address of the Gateway for this route.
Example: xConfiguration IP Route 1 Gateway: "192.168.0.0"
IP Route [1..50] Interface: <Auto/LAN1/LAN2>
Specifies the LAN interface to use for this route. Auto: The VCS will select the most appropriate interface to use. Default: Auto.
Example: xConfiguration IP Route 1 Interface: Auto
IP Route [1..50] PrefixLength: <0..128>
The number of bits of the IP address which must match when determining the network to which this route applies. Default: 32.
Example: xConfiguration IP Route 1 PrefixLength: 16
IP V6 Gateway: <S: 0, 39>
Specifies the IPv6 gateway of the VCS. You must restart the system for any changes to take effect.
Example: xConfiguration IP V6 Gateway: "3dda:80bb:6::9:144"
418

IPProtocol: <Both/IPv4/IPv6>
Selects whether the VCS is operating in IPv4, IPv6 or dual stack mode. You must restart the system for any changes to take effect.
Default: IPv4.
Example: xConfiguration IPProtocol: IPv4
Language Default: <S: 0, 128>
The default language used on the web interface. Default: "en_US".
Example: xConfiguration Language Default: "en_US"
Log CDR Service: <off/serviceonly/serviceandlogging>
Select how to log Call Detail Records produced by this VCS.
Off: Call Detail Records are not logged.
serviceonly: Call Detail Records are stored locally for 7 days and then deleted. The logged records are not accessible via the user
interface.
serviceandlogging: As for serviceonly, except the CDRs are accessible via the local Event log. If you have added syslog server
addresses, the records are sent to those as Info messages.
Default : off
Example: xconfig Log CDR Service: serviceonly
Log Level: <1..4>
Controls the granularity of Event Logging. 1 is the least verbose, 4 the most. Note: this setting is not retrospective; it determines
which events are written to the Event Log from now onwards. Default: 1
Example: xConfiguration Log Level: 1
Log MediaStats Logging: <On/Off>
Toggles media statistics logging. Default: Off
Example: xConfiguration Log MediaStats Logging: On
Log SystemMetrics Interval: <30..600>
Sets the number of seconds to wait between metrics collection events.
Important: A shorter interval has more impact on system performance, while a longer interval yields coarser metrics. We
recommend using the longest interval unless you need very fine metrics.
Default: 60
Example: xconfig Log SystemMetrics Interval: 60
Log SystemMetrics Mode: <On/Off>
Toggles the System Metrics Collection service. Enter On to start collecting metrics for this system.
Default: Off
Example: xconfig Log SystemMetrics Mode: On
419

Log SystemMetrics Network Address: <S: 0,1024>
Enter the address of the listening server. You may use IP address, hostname, or FQDN.
Default: Empty
Example: xconfig log SystemMetrics Network Address: "192.168.0.5"
Log SystemMetrics Network Port: <1..65535>
Enter the port on which the listening server is expecting System Metrics traffic.
Default: 25826
Example: xconfig log SystemMetrics Network Port: 25826
Logger Network [1..n] Level: <FATAL/ERROR/WARN/INFO/DEBUG/TRACE>
The logging level for the nominated module. Default : INFO.
Example: xConfiguration Logger Developer 1 Level: INFO
Login Remote LDAP BaseDN Accounts: <S: 0,255>
Sets the Distinguished Name to use as the base when searching for administrator and user accounts.
Example: xConfiguration Login Remote LDAP BaseDN Accounts: "ou=useraccounts,dc=corporation,dc=int"
Login Remote LDAP BaseDN Groups: <S: 0,255>
Sets the Distinguished Name to use as the base when searching for administrator and user groups.
Example: xConfiguration Login Remote LDAP BaseDN Groups: "ou=groups,dc=corporation,dc=int"
Login Remote LDAP CRLCheck: <None/Peer/All>
Specifies whether certificate revocation lists (CRLs) are checked when forming a TLS connection with the LDAP server. CRL data
is uploaded to the VCS via the trusted CA certificate PEM file. Default: None.
Peer: only the CRL associated with the CA that issued the LDAP server's certificate is checked.
All: all CRLs in the trusted certificate chain of the CA that issued the LDAP server's certificate are checked.
Example: xConfiguration Login Remote LDAP CRLCheck: Peer
Login Remote LDAP DirectoryType: <ActiveDirectory>
Defines the type of LDAP directory that is being accessed. Default: ActiveDirectory.
ActiveDirectory: directory is Windows Active Directory.
Example: xConfiguration Login Remote LDAP DirectoryType: ActiveDirectory
Login Remote LDAP Encryption: <Off/TLS>
Sets the encryption to use for the connection to the LDAP server. Default: TLS.
Example: xConfiguration Login Remote LDAP Encryption: Off
420

Login Remote LDAP SASL: <None/DIGEST-MD5>
The SASL (Simple Authentication and Security Layer) mechanism to use when binding to the LDAP server. Default: DIGEST-MD5.
DIGEST-MD5: The DIGEST-MD5 mechanism is used.
Example: xConfiguration Login Remote LDAP SASL: DIGEST-MD5
Login Remote LDAP Server Address: <S: 0,128>
Sets the IP address or Fully Qualified Domain Name (FQDN) of the LDAP server to use when making LDAP queries.
Example: xConfiguration Login Remote LDAP Server Address: "server.example.com"
Login Remote LDAP Server FQDNResolution: <AddressRecord/SRVRecord>
Sets how the LDAP server address is resolved if specified as an FQDN. Default: AddressRecord.
AddressRecord: DNS A or AAAA record lookup.
SRVRecord: DNS SRV record lookup.
Example: xConfiguration Login Remote LDAP Server FQDNResolution: AddressRecord
Login Remote LDAP Server Port: <1..65534>
Sets the IP port of the LDAP server to use when making LDAP queries. Non-secure connections use 389 and secure connections
use 636. Other ports are not supported. Default: 389.
Example: xConfiguration Login Remote LDAP Server Port: 389
Login Remote LDAP VCS BindDN: <S: 0,255>
Sets the user distinguished name to use when binding to the LDAP server.
Example: xConfiguration Login Remote LDAP VCS BindDN: "systemmanager"
Login Remote LDAP VCS BindPassword: <S: 0,122>
Sets the password to use when binding to the LDAP server. The maximum plaintext length is 60 characters, which is then
encrypted.
Example: xConfiguration Login Remote LDAP VCS BindPassword: "password123"
Login Remote LDAP VCS BindUsername: <S: 0,255>
Sets the username to use when binding to the LDAP server. Only applies if using SASL.
Example: xConfiguration Login Remote LDAP VCS BindUsername: "systemmanager"
Login Remote Protocol: <LDAP>
The protocol used to connect to the external directory. Default: LDAP.
Example: xConfiguration Login Remote Protocol: LDAP
421

Login Source Admin: <LocalOnly/RemoteOnly/Both>
Defines where administrator login credentials are authenticated before access is allowed. Default: LocalOnly.
LocalOnly: credentials are verified against a local database stored on the VCS.
RemoteOnly: credentials are verified against an external credentials directory, for example Windows Active Directory. Note that
this disables login access via the default admin account.
Both: credentials are verified first against a local database stored on the VCS, and then if no matching account is found the external
credentials directory is used instead.
Example: xConfiguration Login Source Admin: LocalOnly
Login Source User: <Local/Remote>
Defines where FindMe login credentials are authenticated before access is allowed. Default : Local.
Remote: credentials are verified against an external credentials directory, for example Windows Active Directory.
Local: credentials are verified against a local database stored on the VCS.
Example: xConfiguration Login Source User: Local
Login User [1..n] Name: <S: 0,60>
Defines the name for this entry in the local authentication database.
Example: xConfiguration Login User 1 Name: "alice"
Login User [1..n] Password: <S: 0,128>
Defines the password for this entry in the local authentication database.
Example: xConfiguration Login User 1 Password: "abcXYZ_123"
Management Interface HstsMode: <On/Off>
Determines whether web browsers are instructed to only ever use a secure connection to access this server. Enabling this feature
gives added protection against man-in-the-middle (MITM) attacks. Default: On.
On: the Strict-Transport-Security header is sent with all responses from the web server, with a 1 year expiry time.
Off : the Strict-Transport-Security header is not sent, and browsers work as normal. Note: you must restart the system for any
changes to take effect.
Example: xConfiguration Management Interface HstsMode: On
Management Session InactivityTimeout: <0..65535>
Sets the number of minutes that an administration session (serial port, HTTPS or SSH) or a user (FindMe) session may be inactive
before the session is timed out. A value of 0 turns session time outs off. Default: 30.
Example: xConfiguration Management Session InactivityTimeout: 30
Management Session MaxConcurrentSessionsTotal: <0..65535>
The maximum number of concurrent administrator sessions allowed on the system. This includes web, SSH and serial sessions. A
value of 0 turns session limits off. Default: 0.
Example: xConfiguration Management Session MaxConcurrentSessionsTotal: 0
422

Management Session MaxConcurrentSessionsUser: <0..65535>
The number of concurrent sessions that each individual administrator account is allowed on the system. This includes web, SSH
and serial sessions. A value of 0 turns session limits off. Default: 0.
Example: xConfiguration Management Session MaxConcurrentSessionsUser: 0
NTP Server [1..5] Address: <S: 0, 128>
Sets the IP address or Fully Qualified Domain Name (FQDN) of up to 5 NTP servers to be used when synchronizing system time.
Example: xConfiguration NTP Server 1 Address: "ntp.server.example.com"
Option [1..64] Key: <S: 0, 90>
Specifies the option key of your software option. These are added to the system in order to add extra functionality, such as
increasing the systems capacity. Contact your Cisco support representative for further information.
Example: xConfiguration Option 1 Key: "1X4757T5-1-60BAD5CD"
Policy AdministratorPolicy Mode: <Off/LocalCPL/LocalService/PolicyService>
Enables and disables use of Call Policy. Default: Off.
Off: Disables call policy.
LocalCPL: uses policy from an uploaded CPL file.
LocalService: uses group policy information and a local file.
PolicyService: uses an external policy server.
Example: xConfiguration Policy AdministratorPolicy Mode: Off
Policy AdministratorPolicy Service DefaultCPL: <S: 0,255>
The CPL used by the VCS when the remote service is unavailable. Default: <reject status='403' reason='Service Unavailable'/>
Example: xConfiguration Policy AdministratorPolicy Service DefaultCPL: "<reject status='403'

reason='Service Unavailable'/>"
Policy AdministratorPolicy Service Password: <S: 0,82>
Specifies the password used by the VCS to log in and query the remote service. The maximum plaintext length is 30 characters,
which will then be encrypted.
Example: xConfiguration Policy AdministratorPolicy Service Password: "password123"
Policy AdministratorPolicy Service Path: <S: 0,255>
Specifies the URL of the remote service.
Example: xConfiguration Policy AdministratorPolicy Service Path: "service"
Policy AdministratorPolicy Service Protocol: <HTTP/HTTPS>
Specifies the protocol used to connect to the remote service. Default: HTTPS.
Example: xConfiguration Policy AdministratorPolicy Service Protocol: HTTPS
Policy AdministratorPolicy Service Server [1..3] Address: <S: 0,128>
Specifies the IP address or Fully Qualified Domain Name (FQDN) of the remote service.
Example: xConfiguration Policy AdministratorPolicy Service Server 1 Address: "service.server.example.com"
423

Policy AdministratorPolicy Service Status Path: <S: 0..255>
Specifies the path for obtaining the remote service status. Default: status
Example: xConfiguration Policy AdministratorPolicy Service Status Path: status
Policy AdministratorPolicy Service TLS CRLCheck Mode: <On/Off>
Controls certificate revocation list checking of the certificate supplied by the policy service. When enabled, the server's X.509
certificate will be checked against the revocation list of the certificate authority of the certificate. Default: Off.
Example: xConfiguration Policy AdministratorPolicy Service TLS CRLCheck Mode: Off
Policy AdministratorPolicy Service TLS Verify Mode: <On/Off>
Controls X.509 certificate checking and mutual authentication between this VCS and the policy service. When enabled, the server's
FQDN or IP address, as specified in the address field, must be contained within the server's X.509 certificate (in either the Subject
Common Name or the Subject Alternative Name attributes). Default: On.
Example: xConfiguration Policy AdministratorPolicy Service TLS Verify Mode: On
Policy AdministratorPolicy Service UserName: <S: 0,30>
Specifies the user name used by the VCS to log in and query the remote policy service.
Example: xConfiguration Policy AdministratorPolicy Service UserName: "user123"
Policy FindMe CallerID: <FindMeID/IncomingID>
Determines how the source of an incoming call is presented to the callee. Default: IncomingID.
IncomingID: displays the address of the endpoint from which the call was placed.
FindMeID: displays the FindMe ID associated with the originating endpoint's address.
Example: xConfiguration Policy FindMe CallerId: FindMeID
Policy FindMe Mode: <Off/On/ThirdPartyManager>
Configures how the FindMe application operates. Default: Off.
Off: disables FindMe.
On: enables FindMe.
ThirdPartyManager: uses an off-box, third-party FindMe manager.
Example: xConfiguration Policy FindMe Mode: On
Policy FindMe Server Address: <S: 0, 128>
Specifies the IP address or Fully Qualified Domain Name (FQDN) of the remote FindMe Manager.
Example: xConfiguration Policy FindMe Server Address: "userpolicy.server.example.com"
Policy FindMe Server Password: <S: 0, 82>
Specifies the password used by the VCS to log in and query the remote FindMe Manager. The maximum plaintext length is 30
characters, which will then be encrypted.
Example: xConfiguration Policy FindMe Server Password: "password123"
424

Policy FindMe Server Path: <S: 0, 255>
Specifies the URL of the remote FindMe Manager.
Example: xConfiguration Policy FindMe Server Path: "service"
Policy FindMe Server Protocol: <HTTP/HTTPS>
Specifies the protocol used to connect to the remote FindMe Manager. Default: HTTPS.
Example: xConfiguration Policy FindMe Server Protocol: HTTPS
Policy FindMe Server UserName: <S: 0, 30>
Specifies the user name used by the VCS to log in and query the remote FindMe Manager.
Example: xConfiguration Policy FindMe Server UserName: "user123"
Policy FindMe UserDeviceRestriction: <Off/On>
Controls if users are restricted from adding, deleting or modifying their own devices. Default: Off.
Example: xConfiguration Policy FindMe UserDeviceRestriction: Off
Policy Services Service [1..20] DefaultCPL: <S: 0,255>
The CPL used by the VCS when the remote service is unavailable. Default: <reject status='504' reason='Policy Service
Unavailable'/>
Example: xConfiguration Policy Services Service 1 DefaultCPL: "<reject status='403' reason='Service

Unavailable'/>"
Policy Services Service [1..20] Description: <S: 0,64>
A free-form description of the Policy Service.
Example: xConfiguration Policy Services Service 1 Description: "Conference management service"
Policy Services Service [1..20] HTTPMethod: <POST/GET>
Specifies the HTTP method type to use for the remote service. Default: POST.
Example: xConfiguration Policy Services Service 1 HTTPMethod: POST
Policy Services Service [1..20] Name: <S: 0,50>
Assigns a name to this Policy Service.
Example: xConfiguration Policy Services Service 1 Name: "Conference handler"
Policy Services Service [1..20] Password: <S: 0,82>
Example: xConfiguration Policy Services Service 1 Password: "password123"
Policy Services Service [1..20] Path: <S: 0,255>
Example: xConfiguration Policy Services Service 1 Path: "service"
425

Policy Services Service [1..20] Protocol: <HTTP/HTTPS>
Example: xConfiguration Policy Services Service 1 Protocol: HTTPS
Policy Services Service [1..20] Server [1..3] Address: <S: 0,128>
Example: xConfiguration Policy Services Service 1 Server 1 Address: "192.168.0.0"
Policy Services Service [1..20] Status Path: <S: 0..255>
Example: xConfiguration Policy Services Service 1 Status Path: status
Policy Services Service [1..20] TLS CRLCheck Mode: <On/Off>
Example: xConfiguration Policy Services Service 1 TLS CRLCheck Mode: Off
Policy Services Service [1..20] TLS Verify Mode: <On/Off>
Example: xConfiguration Policy Services Service 1 TLS Verify Mode: On
Policy Services Service [1..20] UserName: <S: 0,30>
Specifies the user name used by the VCS to log in and query the remote service.
Example: xConfiguration Policy Services Service 1 UserName: "user123"
Registration AllowList [1..2500] Description: <S: 0,64>
A free-form description of the Allow List rule.
Example: xConfiguration Registration AllowList 1 Description: "Everybody at @example.com"
Registration AllowList [1..2500] Pattern String: <S: 0, 60>
Specifies an entry to be added to the Allow List. If one of an endpoints aliases matches one of the patterns in the Allow List, the
registration will be permitted.
Example: xConfiguration Registration AllowList 1 Pattern String: "[email protected]"
Registration AllowList [1..2500] Pattern Type: <Exact/Prefix/Suffix/Regex>
Specifies whether the entry in the Allow List is a prefix, suffix, regular expression, or must be matched exactly. Default: Exact.
Exact: the string must match the alias character for character.
Prefix: the string must appear at the beginning of the alias.
Suffix: the string must appear at the end of the alias.
Regex: the string will be treated as a regular expression.
Example: xConfiguration Registration AllowList 1 Pattern Type: Exact
426

Registration DenyList [1..2500] Description: <S: 0,64>
A free-form description of the Deny List rule.
Example: xConfiguration Registration DenyList 1 Description: "Anybody at @nuisance.com"
Registration DenyList [1..2500] Pattern String: <S: 0, 60>
Specifies an entry to be added to the Deny List. If one of an endpoints aliases matches one of the patterns in the Deny List, the
registration will not be permitted.
Example: xConfiguration Registration DenyList 1 Pattern String: "[email protected]"
Registration DenyList [1..2500] Pattern Type: <Exact/Prefix/Suffix/Regex>
Specifies whether the entry in the Deny List is a prefix, suffix, regular expression, or must be matched exactly. Default: Exact.
Exact: the string must match the alias character for character.
Regex: the string will be treated as a regular expression.
Example: xConfiguration Registration DenyList 1 Pattern Type: Exact
Registration RestrictionPolicy Mode: <None/AllowList/DenyList/Directory/PolicyService>
Specifies the policy to be used when determining which endpoints may register with the system. Default: None.
None: no restriction.
AllowList: only endpoints attempting to register with an alias listed on the Allow List may register.
DenyList: all endpoints, except those attempting to register with an alias listed on the Deny List, may register.
Directory: only endpoints who register an alias listed in the local Directory, may register.
PolicyService: only endpoints who register with details allowed by the Policy Service, may register.
Example: xConfiguration Registration RestrictionPolicy Mode: None
Registration RestrictionPolicy Service DefaultCPL: <S: 0,255>
The CPL used by the VCS when the remote service is unavailable. Default: <reject status='504' reason='Policy Service
Unavailable'/>
Example: xConfiguration Registration RestrictionPolicy Service DefaultCPL: "<reject status='403'

reason='Service Unavailable'/>"
Registration RestrictionPolicy Service Password: <S: 0,82>
Example: xConfiguration Registration RestrictionPolicy Service Password: "password123"
Registration RestrictionPolicy Service Path: <S: 0,255>
Example: xConfiguration Registration RestrictionPolicy Service Path: "service"
427

Registration RestrictionPolicy Service Protocol: <HTTP/HTTPS>
Example: xConfiguration Registration RestrictionPolicy Service Protocol: HTTPS
Registration RestrictionPolicy Service Server [1..3] Address: <S: 0,128>
Example: xConfiguration Registration RestrictionPolicy Service Server 1 Address: "192.168.0.0"
Registration RestrictionPolicy Service Status Path: <S: 0..255>
Example: xConfiguration Registration RestrictionPolicy Service Status Path: status
Registration RestrictionPolicy Service TLS CRLCheck Mode: <On/Off>
Example: xConfiguration Registration RestrictionPolicy Service TLS CRLCheck Mode: Off
Registration RestrictionPolicy Service TLS Verify Mode: <On/Off>
Example: xConfiguration Registration RestrictionPolicy Service TLS Verify Mode: On
Registration RestrictionPolicy Service UserName: <S: 0,30>
Example: xConfiguration Registration RestrictionPolicy Service UserName: "user123"
Remote Syslog [1..4] Address: <S: 0..128>
The IP address or Fully Qualified Domain Name (FQDN) of up to 4 remote syslog servers to which the log is written. These servers
must support the BSD or IETF syslog protocols.
Example: xConfiguration Remote Syslog 1 Address: "remote_server.example.com"
Remote Syslog [1..4] Crlcheck: <On/Off>
Controls whether the certificate supplied by the syslog server is checked against the certificate revocation list (CRL). Default: Off.
Example: xConfiguration Remote Syslog 1 Crlcheck: Off
Remote Syslog [1..4] Format: <bsd/ietf>
The format in which remote syslog messages are written. Default: bsd.
Example: xConfiguration Remote Syslog 1 Format: bsd
Remote Syslog [1..4] Loglevel: <emergency/alert/critical/error/warning/notice/informational/debug>
Select the minimum severity of log messages to send to this syslog server. Default: informational.
Example: xConfiguration Remote Syslog 1 Loglevel: informational
428

Remote Syslog [1..4] Mode: <bsd/ietf/ietf_secure/user_defined>
Select the syslog protocol to use when sending messages to the syslog server, or choose user_defined to configure individually the
transport type, port and format. Default: bsd.
Example: xConfiguration Remote Syslog 1 Mode: bsd
Remote Syslog [1..4] Port: <1..65535>
The UDP/TCP destination port to use. Suggested ports: UDP=514 TCP/TLS=6514. Default : 514.
Example: xConfiguration Remote Syslog 1 Port: 514
Remote Syslog [1..4] Transport: <udp/tcp/tls>
The transport protocol to use when communicating with the syslog server. If you use TLS encryption, you must upload a suitable CA
certificate file. Default: UDP.
Example: xConfiguration Remote Syslog 1 Transport: udp
ResourceUsage Warning Activation Level: <0..100>
Controls if and when the VCS will warn that it is approaching its maximum licensed capacity for calls or registrations. The number
represents the percentage of the maximum that, when reached, will trigger a warning. 0: Warnings will never appear. Default: 90.
Example: xConfiguration ResourceUsage Warning Activation Level: 90
SIP Advanced SipTcpConnectTimeout: <1..150>
Enter the maximum number of seconds to wait for an outgoing SIP TCP connection to be established. Default: 10.[OF:withheld ref
jason tomo end march 15, pending full implementation]
Example: xConfiguration SIP Advanced SipTcpConnectTimeout: 10
SIP Authentication Digest Nonce ExpireDelta: <30..3600>
Specifies the maximum time (in seconds) that a nonce may be re-used for. Default: 300.
Example: xConfiguration SIP Authentication Digest Nonce ExpireDelta: 300
SIP Authentication Digest Nonce Length: <32..512>
Length of nonce or cnonce to generate for use in SIP Digest authentication. Default: 60.
Example: xConfiguration SIP Authentication Digest Nonce Length: 60
SIP Authentication Digest Nonce Limit: <1..65535>
Maximum limit on the number of nonces to store. Default: 10000.
Example: xConfiguration SIP Authentication Digest Nonce Limit: 10000
SIP Authentication Digest Nonce Maximum Use Count: <1..1024>
Maximum number of times that a nonce generated by the VCS may be used by a client. Default: 128.
Example: xConfiguration SIP Authentication Digest Nonce Maximum Use Count: 128
429

SIP Authentication NTLM Mode: <On/Off/Auto>
Controls when the VCS will challenge endpoints using the NTLM protocol. Default: Auto.
Off: the VCS will never send a challenge containing the NTLM protocol.
On: the VCS will always include NTLM in its challenges.
Auto: the VCS will decide based on endpoint type whether to challenge with NTLM.
Example: xConfiguration SIP Authentication NTLM Mode: Auto
SIP Authentication NTLM SA Lifetime: <30..43200>
Specifies the lifetime of NTLM security associations in seconds. Default: 28800.
Example: xConfiguration SIP Authentication NTLM SA Lifetime: 28800
SIP Authentication NTLM SA Limit: <1..65535>
Maximum number of NTLM security associations to store. Default: 10000.
Example: xConfiguration SIP Authentication NTLM SA Limit: 10000
SIP Authentication Retry Limit: <1..16>
The number of times a SIP UA will be challenged due to authentication failure before receiving a 403 Forbidden response. Note
that this applies only to SIP Digest challenges (not NTLM challenges). Default: 3.
Example: xConfiguration SIP Authentication Retry Limit: 3
SIP Domain [1..200] Authzone: <S: 0,128>
The traversal zone to use when delegating credential checks for SIP messages for this domain.
Example: xConfiguration SIP Domain 1 Authzone: "traversalzone"
SIP Domain [1..200] Edge: <On/Off>
Whether remote and mobile collaboration features are enabled. Default Off.
Example: xConfiguration SIP Domain 1 Edge: On
SIP Domain [1..200] Name: <S: 0,128>
Specifies a domain for which this VCS is authoritative. The domain name can comprise multiple levels. Each level's name can only
contain letters, digits and hyphens, with each level separated by a period (dot). A level name cannot start or end with a hyphen, and
the final level name must start with a letter. An example valid domain name is "100.example-name.com".
Example: xConfiguration SIP Domain 1 Name: "100.example-name.com"
SIP Domain [1..200] Sip: <On/Off>
Specifies whether the VCS will act as a SIP registrar and Presence Server for this domain, and will accept registration requests for
any SIP endpoints attempting to register with an alias that includes this domain. Default On.
Example: xConfiguration SIP Domain 1 Sip: On
SIP GRUU Mode: <On/Off>
Controls whether GRUU (RFC5627) support is active. Default: On.
Example: xConfiguration SIP GRUU Mode: On
430

SIP MediaRouting ICE Mode: <On/Off>
Controls whether the VCS takes the media for an ICE to non-ICE call where the ICE participant is thought to be behind a NAT
device. Default: Off.
Example: xConfiguration SIP MediaRouting ICE Mode: Off
SIP Mode: <On/Off>
Determines whether or not the VCS will provide SIP registrar and SIP proxy functionality. This mode must be enabled in order to
use either the Presence Server or the Presence User Agent. Default: On.
Example: xConfiguration SIP Mode: On
SIP Registration Call Remove: <Yes/No>
Specifies whether associated calls are dropped when a SIP registration expires or is removed. Default: No.
Example: xConfiguration SIP Registration Call Remove: No
SIP Registration Outbound Flow Timer: <0..600>
Specifies the value for the Flow-Timer header in Outbound registration responses. It defines the number of seconds after which the
server will consider the registration flow to be dead if no keep-alive is sent by the user agent. Default: 0 (no header is added).
Example: xConfiguration SIP Registration Outbound Flow Timer: 0
SIP Registration Outbound Refresh Maximum: <30..7200>
The maximum allowed value for a SIP registration refresh period for Outbound registrations. Requests for a value greater than this
will result in a lower value (calculated according to the Outbound registration refresh strategy) being returned. Default: 3600
seconds.
Example: xConfiguration SIP Registration Outbound Refresh Maximum: 3600
SIP Registration Outbound Refresh Minimum: <30..7200>
The minimum allowed value for a SIP registration refresh period for Outbound registrations. Requests for a value lower than this
value will result in the registration being rejected with a 423 Interval Too Brief response. Default: 600 seconds.
Example: xConfiguration SIP Registration Outbound Refresh Minimum: 600
SIP Registration Outbound Refresh Strategy: <Maximum/Variable>
The method used to generate the SIP registration expiry period for Outbound registrations. Default: Variable.
Maximum: uses the lesser of the configured maximum refresh value and the value requested in the registration.
Variable: generates a random value between the configured minimum refresh value and the lesser of the configured maximum
refresh value and the value requested in the registration.
Example: xConfiguration SIP Registration Outbound Refresh Strategy: Variable
SIP Registration Proxy Mode: <Off/ProxyToKnownOnly/ProxyToAny>
Specifies how proxied registrations should be handled. Default: Off.
Off: registration requests will not be proxied.
ProxyToKnownOnly: registration requests will be proxied to neighbors only.
ProxyToAny: registration requests will be proxied in accordance with the VCSs existing call processing rules.
Example: xConfiguration SIP Registration Proxy Mode: Off
431

SIP Registration Standard Refresh Maximum: <30..7200>
The maximum allowed value for a SIP registration refresh period for standard registrations. Requests for a value greater than this
will result in a lower value being returned. That value is calculated according to the standard registration refresh strategy. Default:
60 seconds.
Example: xConfiguration SIP Registration Standard Refresh Maximum: 60
SIP Registration Standard Refresh Minimum: <30..3600>
The minimum allowed value for a SIP registration refresh period for standard registrations. Requests for a value lower than this
value will result in the registration being rejected with a 423 Interval Too Brief response. Default: 45 seconds.
Example: xConfiguration SIP Registration Standard Refresh Minimum: 45
SIP Registration Standard Refresh Strategy: <Maximum/Variable>
The method used to generate the SIP registration expiry period for standard registrations. Default: Maximum.
Maximum: uses the lesser of the configured maximum refresh value and the value requested in the registration.
Variable: generates a random value between the configured minimum refresh value and the lesser of the configured maximum
refresh value and the value requested in the registration.
Example: xConfiguration SIP Registration Standard Refresh Strategy: Maximum
SIP Require Duo Video Mode: <On/Off>
Controls whether the VCS requires the use of the com.tandberg.sdp.duo.enable extension for endpoints that support it. Default: On.
Example: xConfiguration SIP Require Duo Video Mode: On
SIP Require UDP BFCP Mode: <On/Off>
Controls whether the VCS will require the use of the com.tandberg.udp.bfcp extension for endpoints that support it. Default: On.
Example: xConfiguration SIP Require UDP BFCP Mode: On
SIP Routes Route [1..20] Address: <S:0,39>
Specifies the IP address of the next hop for this route, where matching SIP requests will be forwarded. Note: this command is
intended for developer use only.
Example: xConfiguration SIP Routes Route 1 Address: "127.0.0.1"
SIP Routes Route [1..20] Authenticated: <On/Off>
Whether to forward authenticated requests. Default: Off. Note: this command is intended for developer use only.
On: only forward requests along route if incoming message has been authenticated.
Off: always forward messages that match this route.
Example: xConfiguration SIP Routes Route 1 Authenticated: On
SIP Routes Route [1..20] Header Name: <S:0,64>
Name of SIP header field to match (e.g. Event). Note: this command is intended for developer use only.
Example: xConfiguration SIP Routes Route 1 Header Name: "Event"
432

SIP Routes Route [1..20] Header Pattern: <S:0,128>
Regular expression to match against the specified SIP header field. Note: this command is intended for developer use only.
Example: xConfiguration SIP Routes Route 1 Header Pattern: "(my-event-package)(.*)"
SIP Routes Route [1..20] Method: <S:0,64>
SIP method to match to select this route (e.g. INVITE, SUBSCRIBE). Note: this command is intended for developer use only.
Example: xConfiguration SIP Routes Route 1 Method: "SUBSCRIBE"
SIP Routes Route [1..20] Port: <1..65534>
Specifies the port on the next hop for this route to which matching SIP requests will be routed. Default: 5060. Note: this command
is intended for developer use only.
Example: xConfiguration SIP Routes Route 1 Port: 22400
SIP Routes Route [1..20] Request Line Pattern: <S:0,128>
Regular expression to match against the SIP request line. Note: this command is intended for developer use only.
Example: xConfiguration SIP Routes Route 1 Request Line Pattern: ".*@(%localdomains%|%ip%)"
SIP Routes Route [1..20] Tag: <S:0,64>
Tag value specified by external applications to identify routes that they create. Note: this command is intended for developer use
only.
Example: xConfiguration SIP Routes Route 1 Tag: "Tag1"
SIP Routes Route [1..20] Transport: <UDP/TCP/TLS>
Determines which transport type will be used for SIP messages forwarded along this route. Default: TCP. Note: this command is
intended for developer use only.
Example: xConfiguration SIP Routes Route 1 Transport: TCP
SIP Session Refresh Minimum: <90..7200>
The minimum value the VCS will negotiate for the session refresh interval for SIP calls. For more information see the definition of
Min-SE header in RFC 4028. Default: 500.
Example: xConfiguration SIP Session Refresh Minimum: 500
SIP Session Refresh Value: <90..86400>
The maximum time allowed between session refresh requests for SIP calls. For more information see the definition of Session-
Expires in RFC 4028. Default: 1800.
Example: xConfiguration SIP Session Refresh Value: 1800
SIP TCP Mode: <On/Off>
Determines whether incoming and outgoing SIP calls using the TCP protocol will be allowed. Default: On.
Example: xConfiguration SIP TCP Mode: On
SIP TCP Outbound Port End: <1024..65534>
Specifies the upper port in the range to be used by outbound TCP/TLS SIP connections. Default: 29999.
Example: xConfiguration SIP TCP Outbound Port End: 29999
433

SIP TCP Outbound Port Start: <1024..65534>
Specifies the lower port in the range to be used by outbound TCP/TLS SIP connections. Default: 25000.
Example: xConfiguration SIP TCP Outbound Port Start: 25000
SIP TCP Port: <1024..65534>
Specifies the listening port for incoming SIP TCP calls. Default: 5060.
Example: xConfiguration SIP TCP Port: 5060
SIP TLS Certificate Revocation Checking CRL Mode: <On/Off>
Controls whether Certificate Revocation Lists (CRLs) are used to perform certificate revocation checking. CRLs can be loaded
manually onto the VCS, downloaded automatically from pre-configured URIs, or downloaded automatically from a CRL distribution
point (CDP) URI contained in the X.509 certificate. Default: On.
Example: xConfiguration SIP TLS Certificate Revocation Checking CRL Mode: On
SIP TLS Certificate Revocation Checking CRL Network Fetch Mode: <On/Off>
Controls whether the download of CRLs from the CDP URIs contained in X.509 certificates is allowed. Default: On.
Example: xConfiguration SIP TLS Certificate Revocation Checking CRL Network Fetch Mode: On
SIP TLS Certificate Revocation Checking Mode: <On/Off>
Controls whether revocation checking is performed for certificates exchanged during SIP TLS connection establishment. Default:
Off.
Example: xConfiguration SIP TLS Certificate Revocation Checking Mode: Off
SIP TLS Certificate Revocation Checking OCSP Mode: <On/Off>
Controls whether the Online Certificate Status Protocol (OCSP) may be used to perform certificate revocation checking. To use
OCSP, the X.509 certificate to be checked must contain an OCSP responder URI. Default: On.
Example: xConfiguration SIP TLS Certificate Revocation Checking OCSP Mode: On
SIP TLS Certificate Revocation Checking Source Inaccessibility Behavior: <Ignore/Fail>
Controls the revocation checking behavior if the revocation source cannot be contacted. Default: Fail.
Fail: treat the certificate as revoked (and thus do not allow the TLS connection).
Ignore: treat the certificate as not revoked.
Example: xConfiguration SIP TLS Certificate Revocation Checking Source Inaccessibility Behavior: Fail
SIPTLSCipherSuite:<S:0,1000>
Specifies the SIP TLS cipher suite to use in 'OpenSSL ciphers' format (See
https://www.openssl.org/docs/apps/ciphers.html#CIPHER-LIST-FORMAT). Note that existing connections (e.g. zones and device
registrations) will be dropped when this configuration changes because a new TLS exchange must occur. Also note that aNULL
ciphers are not supported for inbound connections. Default: ALL:!EXP:!LOW:!MD5:@STRENGTH:+ADH
Example: SIP TLS CipherSuite: ALL:!EXP:!LOW:!MD5:@STRENGTH:+ADH
SIP TLS Mode: <On/Off>
Determines whether incoming and outgoing SIP calls using the TLS protocol will be allowed. Default: On.
Example: xConfiguration SIP TLS Mode: On
434

SIP TLS Port: <1024..65534>
Specifies the listening port for incoming SIP TLS calls. Default: 5061.
Example: xConfiguration SIP TLS Port: 5061
SIP UDP Mode: <On/Off>
Determines whether incoming and outgoing SIP calls using the UDP protocol will be allowed. Default: Off.
Example: xConfiguration SIP UDP Mode: On
SIP UDP Port: <1024..65534>
Specifies the listening port for incoming SIP UDP calls. Default: 5060.
Example: xConfiguration SIP UDP Port: 5060
SNMP CommunityName: <S: 0, 16>
The VCS's SNMP community name. Default: public
Example: xConfiguration SNMP CommunityName: "public"
SNMP SystemContact: <S: 0, 70>
The name of the person who can be contacted regarding issues with the VCS. Default: Administrator.
Example: xConfiguration SNMP SystemContact: Administrator
SNMP SystemLocation: <S: 0, 70>
The physical location of the system.
Example: xConfiguration SNMP SystemLocation: "Server Room 128"
SNMP V1Mode: <On/Off>
Enables or disables SNMP Version 1 support. Default: Off.
Example: Configuration SNMP V1Mode: Off
SNMP V2cMode: <On/Off>
Enables or disables SNMP Version 2c support. Default: On.
Example: xConfiguration SNMP V2cMode: On
SNMP V3AuthenticationMode: <On/Off>
Enables or disables SNMP Version 3 authentication. Default: On.
Example: xConfiguration SNMP V3AuthenticationMode: On
SNMP V3AuthenticationPassword: <S: 0,215>
Sets SNMP Version 3 authentication password. It must be at least 8 characters.
Example: xConfiguration SNMP V3AuthenticationPassword: "password123"
SNMP V3AuthenticationType: <MD5/SHA>
Sets SNMP Version 3 authentication type. Default: SHA.
Example: xConfiguration SNMP V3AuthenticationType: SHA
435

SNMP V3Mode: <On/Off>
Enables or disables SNMP Version 3 support. Default: On.
Example: xConfiguration SNMPV3 Mode: On
SNMP V3PrivacyMode: <On/Off>
Enables or disables SNMP Version 3 privacy. Default: On.
Example: xConfiguration SNMP V3PrivacyMode: On
SNMP V3PrivacyPassword: <S: 0,215>
Sets SNMP Version 3 privacy password. It must be at least 8 characters.
Example: xConfiguration SNMP V3PrivacyPassword: "password123"
SNMP V3PrivacyType: <DES/AES>
Sets SNMP Version 3 privacy type. Default: AES.
Example: xConfiguration SNMP V3PrivacyType: AES
SNMP V3UserName: <S: 0,70>
Sets the username to use when using SNMP V3.
Example: xConfiguration SNMP V3UserName: "user123"
SystemUnit Maintenance Mode: <On/Off>
Sets the VCS into maintenance mode.New calls and registrations are disallowed and existing registrations are allowed to expire.
Default: Off.
Example: xConfiguration SystemUnit Maintenance Mode: Off
SystemUnit Name: <S:, 0, 50>
Defines the name of the VCS. The system name appears in various places in the web interface and on the front panel of the unit.
Choose a name that uniquely identifies the system.
Example: xConfiguration SystemUnit Name: "MainHQ"
TimeZone Name: <S: 0, 64>
Sets the local time zone of the VCS. Time zone names follow the POSIX naming convention e.g. Europe/London or America/New_
York. Default: GMT.
Example: xConfiguration TimeZone Name: "GMT"
Transform [1..100] Description: <S: 0,64>
A free-form description of the transform.
Example: xConfiguration Transform [1..100] Description: "Change example.net to example.com"
436

Transform [1..100] Pattern Behavior: <Strip/Replace>
How the alias is modified. Default: Strip.
Strip: removes the matching prefix or suffix from the alias.
Replace: substitutes the matching part of the alias with the text in replace string.
AddPrefix: prepends the replace string to the alias.
AddSuffix: appends the replace string to the alias.
Example: xConfiguration Transform 1 Pattern Behavior: Replace
Transform [1..100] Pattern Replace: <S: 0, 60>
The text string to use in conjunction with the selected Pattern behavior.
Example: xConfiguration Transform 1 Pattern Replace: "example.com"
Transform [1..100] Pattern String: <S: 0, 60>
The pattern against which the alias is compared.
Example: xConfiguration Transform 1 Pattern String: "example.net"
Transform [1..100] Pattern Type: <Exact/Prefix/Suffix/Regex>
How the pattern string must match the alias for the transform to be applied. Default: Prefix.
Exact: the entire string must exactly match the alias character for character.
Regex: the string is treated as a regular expression.
Example: xConfiguration Transform 1 Pattern Type: Suffix
Transform [1..100] Priority: <1..65534>
Assigns a priority to the specified transform. Transforms are compared with incoming aliases in order of priority, and the priority
must be unique for each transform. Default: 1 .
Example: xConfiguration Transform 1 Priority: 10
Transform [1..100] State: <Enabled/Disabled>
Indicates if the transform is enabled or disabled. Disabled transforms are ignored.
Example: xConfiguration Transform 1 State: Enabled
Traversal Media Port End: <1025..65533>
For traversal calls (where the VCS takes the media as well as the signaling), specifies the upper port in the range to use for the
media. Ports are allocated from this range in pairs, the first of each being even. Thus the range must end with an odd number.
Default: 59999 .
Example: xConfiguration Traversal Media Port End: 59999
437

Traversal Media Port Start: <1024..65532>
For traversal calls (where the VCS takes the media as well as the signaling), specifies the lower port in the range to use for the
media. Ports are allocated from this range in pairs, the first of each being even. Thus the range must start with an even number.
Default: 36000 .
Example: xConfiguration Traversal Media Port Start: 36000
Traversal Server H323 Assent CallSignaling Port: <1024..65534>
The port on the VCS to use for Assent signaling. Default: 2776 .
Example: xConfiguration Traversal Server H323 Assent CallSignaling Port: 2777
Traversal Server H323 H46018 CallSignaling Port: <1024..65534>
The port on the VCS to use for H460.18 signaling. Default: 2777 .
Example: xConfiguration Traversal Server H323 H46018 CallSignaling Port: 2777
Traversal Server TURN Authentication Realm: <S: 1,128>
The realm sent by the server in its authentication challenges. Default: TANDBERG .
Example: xConfiguration Traversal Server TURN Authentication Realm: "TANDBERG"
Traversal Server TURN Authentication Remote Mode: <On/Off>
Determines whether the server requires requests to be authenticated. When enabled the server will also authenticate its responses.
Default: On.
Example: xConfiguration Traversal Server TURN Authentication Remote Mode: On
Traversal Server TURN Media Port End: <1024..65534>
The upper port in the range used for TURN relays. Default: 61799.
Example: xConfiguration Traversal Server TURN Media Port End: 61799
Traversal Server TURN Media Port Start: <1024..65534>
The lower port in the range used for TURN relays. Default: 60000.
Example: xConfiguration Traversal Server TURN Media Port Start: 60000
Traversal Server TURN Mode: <On/Off>
Determines whether the VCS offers TURN services to traversal clients. Default: Off .
Example: xConfiguration Traversal Server TURN Mode: Off
Traversal Server TURN Port: <1024..65534>
The listening port for TURN requests. Default: 3478.
Example: xConfiguration Traversal Server TURN Port: 3478
Traversal Server TURN PortRangeEnd: <1024..65534>
The upper port in the range used for TURN requests. Default: 3483
Example: xConfiguration Traversal Server TURN PortRangeEnd: 3483
438

Traversal Server TURN PortRangeStart: <1024..65534>
The lower port in the range used for TURN requests. Default: 3478.
Example: xConfiguration Traversal Server TURN PortRangeStart: 3478
Traversal Server TURN ProtocolMode: <TCP/UDP/Both>
The permitted protocols for TURN requests. Default: Both.
Example: xConfiguration Traversal Server TURN ProtocolMode: Both
Zones DefaultZone Authentication Mode: <DoNotCheckCredentials/TreatAsAuthenticated/CheckCredentials>
Controls how the VCS authenticates incoming messages from this zone and whether they are subsequently treated as
authenticated, unauthenticated, or are rejected. The behavior varies for H.323 messages, SIP messages that originate from a local
domain and SIP messages that originate from non-local domains. Default: DoNotCheckCredentials.
Example: xConfiguration Zones DefaultZone Authentication Mode: DoNotCheckCredentials
Zones DefaultZone SIP Media Encryption Mode: <Off/On/BestEffort/Auto>
The media encryption policy applied by the VCS for SIP calls (including interworked calls) to and from this zone. Default: Auto.
On: All media must be encrypted.
Off: All media must be unencrypted.
BestEffort: Use encryption if available otherwise fallback to unencrypted media.
Auto: No media encryption policy is applied.
Example: xConfiguration Zones DefaultZone SIP Media Encryption Mode: Auto
Zones DefaultZone SIP Record Route Address Type: <IP/Hostname>
Controls whether the VCS uses its IP address or host name in the record-route or path headers of outgoing SIP requests to this
zone. Note: setting this value to hostname also requires a valid DNS system host name to be configured on the VCS. Default: IP.
Example: xConfiguration Zones DefaultZone SIP Record Route Address Type: IP
Zones DefaultZone SIP TLS Verify Mode: <On/Off>
Controls whether the hostname contained within the certificate presented by the external system is verified by the VCS. If enabled,
the certificate hostname (also known as the Common Name) is checked against the patterns specified in the Default Zone access
rules. Default: Off.
Example: xConfiguration Zones DefaultZone SIP TLS Verify Mode: Off
Zones LocalZone DefaultSubZone Authentication Mode: <DoNotCheckCredentials/TreatAsAuthenticated/CheckCredentials>
Controls how the VCS authenticates incoming messages from this subzone and whether they are subsequently treated as
authenticated, unauthenticated or are rejected. The behavior varies for H.323 messages, SIP messages that originate from a local
Example: xConfiguration Zones LocalZone DefaultSubZone Authentication Mode: DoNotCheckCredentials
Zones LocalZone DefaultSubZone Bandwidth PerCall Inter Limit: <1..100000000>
The bandwidth limit (in kbps) for any one call to or from an endpoint in the Default Subzone (applies only if the mode is set to
Limited). Default: 1920.
Example: xConfiguration Zones LocalZone DefaultSubZone Bandwidth PerCall Inter Limit: 1920
439

Zones LocalZone DefaultSubZone Bandwidth PerCall Inter Mode: <Limited/Unlimited/NoBandwidth>
Controls if there is a limit on the bandwidth for any one call to or from an endpoint in the Default Subzone. Default: Unlimited.
NoBandwidth: no bandwidth available. No calls can be made to or from the Default Subzone.
Example: xConfiguration Zones LocalZone DefaultSubZone Bandwidth PerCall Inter Mode: Limited
Zones LocalZone DefaultSubZone Bandwidth PerCall Intra Limit: <1..100000000>
The bandwidth limit (in kbps) for any one call between two endpoints within the Default Subzone (applies only if the mode is set to
Example: xConfiguration Zones LocalZone DefaultSubZone Bandwidth PerCall Intra Limit: 1920
Zones LocalZone DefaultSubZone Bandwidth PerCall Intra Mode: <Limited/Unlimited/NoBandwidth>
Controls if there is a limit on the bandwidth for any one call between two endpoints within the Default Subzone. Default: Unlimited.
NoBandwidth: no bandwidth available. No calls can be made within the Default Subzone.
Example: xConfiguration Zones LocalZone DefaultSubZone Bandwidth PerCall Intra Mode: Limited
Zones LocalZone DefaultSubZone Bandwidth Total Limit: <1..100000000>
Sets the total bandwidth limit (in kbps) of the Default Subzone (applies only if Mode is set to Limited). Default: 500000 .
Example: xConfiguration Zones LocalZone DefaultSubZone Bandwidth Total Limit: 500000
Zones LocalZone DefaultSubZone Bandwidth Total Mode: <Limited/Unlimited/NoBandwidth>
Controls if the Default Subzone has a limit on the total bandwidth being used by its endpoints at any one time. Default: Unlimited.
NoBandwidth: no bandwidth available. No calls can be made to, from, or within the Default Subzone.
Example: xConfiguration Zones LocalZone DefaultSubZone Bandwidth Total Mode: Limited
Zones LocalZone DefaultSubZone Registrations: <Allow/Deny>
Controls whether registrations assigned to the Default Subzone are accepted. Default: Allow.
Example: xConfiguration Zones LocalZone DefaultSubZone Registrations: Allow
Zones LocalZone DefaultSubZone SIP Media Encryption Mode: <Off/On/BestEffort/Auto>
The media encryption policy applied by the VCS for SIP calls (including interworked calls) to and from this subzone. Default: Auto
Example: xConfiguration Zones LocalZone DefaultSubZone SIP Media Encryption Mode: Auto
Zones LocalZone SIP Record Route Address Type: <IP/Hostname>
zone. Note: setting this value to hostname also requires a valid DNS system host name to be configured on the VCS. Default: IP.
Example: xConfiguration Zones LocalZone SIP Record Route Address Type: IP
440

Zones LocalZone SubZones MembershipRules Rule [1..3000] Description: <S: 0,64>
A free-form description of the membership rule.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 Description: "Office-based staff"
Zones LocalZone SubZones MembershipRules Rule [1..3000] Name: <S: 0,50>
Assigns a name to this membership rule.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 Name: "Office Workers"
Zones LocalZone SubZones MembershipRules Rule [1..3000] Pattern String: <S: 0,60>
Specifies the pattern against which the alias is compared.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 Pattern String: "@example.com"
Zones LocalZone SubZones MembershipRules Rule [1..3000] Pattern Type: <Exact/Prefix/Suffix/Regex>
The way in which the pattern must match the alias.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 Pattern Type: Suffix
Zones LocalZone SubZones MembershipRules Rule [1..3000] Priority: <1..65534>
Determines the order in which the rules are applied (and thus to which subzone the endpoint is assigned) if an endpoint's address
satisfies multiple rules. The rules with the highest priority (1, then 2, then 3 and so on) are applied first. If multiple Subnet rules have
the same priority the rule with the largest prefix length is applied first. Alias Pattern Match rules at the same priority are searched in
configuration order. Default: 100.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 Priority: 100
Zones LocalZone SubZones MembershipRules Rule [1..3000] State: <Enabled/Disabled>
Indicates if the membership rule is enabled or disabled. Disabled membership rules are ignored. Default: Enabled.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 State: Enabled
Zones LocalZone SubZones MembershipRules Rule [1..3000] SubZoneName: <S: 0,50>
The subzone to which an endpoint is assigned if its address satisfies this rule.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 SubZoneName: "Branch Office"
Zones LocalZone SubZones MembershipRules Rule [1..3000] Subnet Address: <S: 0,39>
Specifies an IP address used (in conjunction with the prefix length) to identify this subnet.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 Subnet Address: "192.168.0.0"
Zones LocalZone SubZones MembershipRules Rule [1..3000] Subnet PrefixLength: <1..128>
The number of bits of the subnet address which must match for an IP address to belong in this subnet. Default: 32.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 Subnet PrefixLength: 32
Zones LocalZone SubZones MembershipRules Rule [1..3000] Type: <Subnet/AliasPatternMatch>
The type of address that applies to this rule.
Subnet: assigns the device if its IP address falls within the configured IP address subnet.
AliasPatternMatch: assigns the device if its alias matches the configured pattern.
Example: xConfiguration Zones LocalZone SubZones MembershipRules Rule 1 Type: Subnet
441

Zones LocalZone SubZones SubZone [1..1000] Authentication Mode:
<DoNotCheckCredentials/TreatAsAuthenticated/CheckCredentials>
Controls how the VCS authenticates incoming messages from this subzone and whether they are subsequently treated as
authenticated, unauthenticated or are rejected. The behavior varies for H.323 messages, SIP messages that originate from a local
domain and SIP messages that originate from non-local domains. See the Administrator Guide for further information. Default:
DoNotCheckCredentials.
Example: xConfiguration Zones LocalZone SubZones SubZone 1 Authentication Mode: DoNotCheckCredentials
Zones LocalZone SubZones SubZone [1..1000] Bandwidth PerCall Inter Limit: <1..100000000>
The bandwidth limit (in kbps) on any one call to or from an endpoint in this subzone (applies only if Mode is set to Limited). Default:
1920.
Example: xConfiguration Zones LocalZone SubZones SubZone 1 Bandwidth PerCall Inter Limit: 1920
Zones LocalZone SubZones SubZone [1..1000] Bandwidth PerCall Inter Mode: <Limited/Unlimited/NoBandwidth>
Determines whether there is a limit on the bandwidth for any one call to or from an endpoint in this subzone. Default: Unlimited.
NoBandwidth: no bandwidth available. No calls can be made to or from this subzone.
Example: xConfiguration Zones LocalZone SubZones SubZone 1 Bandwidth PerCall Inter Mode: Limited
Zones LocalZone SubZones SubZone [1..1000] Bandwidth PerCall Intra Limit: <1..100000000>
The bandwidth limit (in kbps) for any one call between two endpoints within this subzone (applies only if the mode is set to
Example: Zones LocalZone SubZones SubZone 1 Bandwidth PerCall Intra Limit: 1920
Zones LocalZone SubZones SubZone [1..1000] Bandwidth PerCall Intra Mode: <Limited/Unlimited/NoBandwidth>
Determines whether there is a limit on the bandwidth for any one call between two endpoints within this subzone. Default:
Unlimited.
NoBandwidth: no bandwidth available. No calls can be made within this subzone.
Example: xConfiguration Zones LocalZone SubZones SubZone 1 Bandwidth PerCall Intra Mode: Limited
Zones LocalZone SubZones SubZone [1..1000] Bandwidth Total Limit: <1..100000000>
Sets the total bandwidth limit (in kbps) of this subzone (applies only if the mode is set to Limited). Default: 500000.
Example: xConfiguration Zones LocalZone SubZones SubZone 1 Bandwidth Total Limit: 500000
Zones LocalZone SubZones SubZone [1..1000] Bandwidth Total Mode: <Limited/Unlimited/NoBandwidth>
Controls if this subzone has a limit on the total bandwidth of calls being used by its endpoints at any one time. Default: Unlimited.
NoBandwidth: no bandwidth available. No calls can be made to, from, or within this subzone.
Example: xConfiguration Zones LocalZone SubZones SubZone 1 Bandwidth Total Mode: Limited
Zones LocalZone SubZones SubZone [1..1000] Name: <S: 0, 50>
Assigns a name to this subzone.
Example: xConfiguration Zones LocalZone SubZones SubZone 1 Name: "BranchOffice"
442

Zones LocalZone SubZones SubZone [1..1000] Registrations: <Allow/Deny>
Controls whether registrations assigned to this subzone are accepted. Default: Allow.
Example: xConfiguration Zones LocalZone SubZones SubZone 1 Registrations: Allow
Zones LocalZone SubZones SubZone [1..1000] SIP Media Encryption Mode: <Off/On/BestEffort/Auto>
The media encryption policy applied by the VCS for SIP calls (including interworked calls) to and from this subzone. Default: Auto
Example: xConfiguration Zones LocalZone SubZones SubZone 1 SIP Media Encryption Mode: Auto
Zones LocalZone Traversal H323 Assent Mode: <On/Off>
Determines whether or not H.323 calls using Assent mode for firewall traversal will be allowed. Applies to traversal-enabled
endpoints registered directly with the VCS. Default: On .
Example: xConfiguration Zones LocalZone Traversal H323 Assent Mode: On
Zones LocalZone Traversal H323 H46018 Mode: <On/Off>
Controls whether H.323 calls using H460.18 mode for firewall traversal are allowed. Applies to traversal-enabled endpoints
registered directly with the VCS. Default: On .
Example: xConfiguration Zones LocalZone Traversal H323 H46018 Mode: On
Zones LocalZone Traversal H323 H46019 Demultiplexing Mode: <On/Off>
Controls whether the VCS operates in Demultiplexing mode for calls from traversal-enabled endpoints registered directly with it.
Default: Off .
On: allows use of the same two ports for all calls.
Off: each call will use a separate pair of ports for media.
Example: xConfiguration Zones LocalZone Traversal H323 H46019 Demultiplexing Mode: Off
Zones LocalZone Traversal H323 Preference: <Assent/H46018>
If an endpoint that is registered directly with the VCS supports both Assent and H460.18 protocols, this setting determines which
the VCS uses. Default: Assent.
Example: xConfiguration Zones LocalZone Traversal H323 Preference: Assent
Zones LocalZone Traversal H323 TCPProbe KeepAliveInterval: <1..65534>
Sets the interval (in seconds) with which a traversal-enabled endpoint registered directly with the VCS will send a TCP probe to
the VCS once a call is established, in order to keep the firewalls NAT bindings open. Default: 20 .
Example: xConfiguration Zones LocalZone Traversal H323 TCPProbe KeepAliveInterval: 20
Zones LocalZone Traversal H323 TCPProbe RetryCount: <1..65534>
Sets the number of times traversal-enabled endpoints registered directly with the VCS will attempt to send a TCP probe. Default: 5
.
Example: xConfiguration Zones LocalZone Traversal H323 TCPProbe RetryCount: 5
443

Zones LocalZone Traversal H323 TCPProbe RetryInterval: <1..65534>
Sets the frequency (in seconds) with which traversal-enabled endpoints registered directly with the VCS will send a TCP probe.
Default: 2 .
Example: xConfiguration Zones LocalZone Traversal H323 TCPProbe RetryInterval: 2
Zones LocalZone Traversal H323 UDPProbe KeepAliveInterval: <1..65534>
Sets the interval (in seconds) with which a traversal-enabled endpoint registered directly with the VCS will send a UDP probe to
the VCS once a call is established, in order to keep the firewalls NAT bindings open. Default: 20 .
Example: xConfiguration Zones LocalZone Traversal H323 UDPProbe KeepAliveInterval: 20
Zones LocalZone Traversal H323 UDPProbe RetryCount: <1..65534>
Sets the number of times traversal-enabled endpoints registered directly with the VCS will attempt to send a UDP probe. Default: 5
.
Example: xConfiguration Zones LocalZone Traversal H323 UDPProbe RetryCount: 5
Zones LocalZone Traversal H323 UDPProbe RetryInterval: <1..65534>
Sets the frequency (in seconds) with which traversal-enabled endpoints registered directly with the VCS will send a UDP probe.
Default: 2 .
Example: xConfiguration Zones LocalZone Traversal H323 UDPProbe RetryInterval: 2
Zones LocalZone TraversalSubZone Bandwidth PerCall Limit: <1..100000000>
The bandwidth limit (in kbps) applied to any one traversal call being handled by the VCS (applies only if the mode is set to Limited).
Default: 1920 .
Example: xConfiguration Zones LocalZone TraversalSubZone Bandwidth PerCall Limit: 1920
Zones LocalZone TraversalSubZone Bandwidth PerCall Mode: <Limited/Unlimited/NoBandwidth>
Determines whether there is a limit on the bandwidth of any one traversal call being handled by the VCS. Default: Unlimited.
NoBandwidth: no bandwidth available. No traversal calls can be made.
Example: xConfiguration Zones LocalZone TraversalSubZone Bandwidth PerCall Mode: Limited
Zones LocalZone TraversalSubZone Bandwidth Total Limit: <1..100000000>
The total bandwidth (in kbps) allowed for all traversal calls being handled by the VCS (applies only if the mode is set to Limited).
Default: 500000 .
Example: xConfiguration Zones LocalZone TraversalSubZone Bandwidth Total Limit: 500000
Zones LocalZone TraversalSubZone Bandwidth Total Mode: <Limited/Unlimited/NoBandwidth>
Determines whether or not there is a limit to the total bandwidth of all traversal calls being handled by the VCS. Default: Unlimited.
NoBandwidth: no bandwidth available. No traversal calls can be made.
Example: xConfiguration Zones LocalZone TraversalSubZone Bandwidth Total Mode: Limited
444

Zones Policy Mode: <SearchRules/Directory>
The mode used when attempting to locate a destination. Default: SearchRules.
SearchRules: use the configured search rules to determine which zones are queried and in what order.
Directory: use the facilities of a directory service to direct the request to the correct zones.
Example: xConfiguration Zones Policy Mode: SearchRules
Zones Policy SearchRules Rule [1..2000] Authentication: <Yes/No>
Specifies whether this search rule applies only to authenticated search requests. Default: No.
Example: xConfiguration Zones Policy SearchRules Rule 1 Authentication: No
Zones Policy SearchRules Rule [1..2000] Description: <S: 0,64>
A free-form description of the search rule.
Example: xConfiguration Zones Policy SearchRules Rule 1 Description: "Send query to the DNS zone"
Zones Policy SearchRules Rule [1..2000] Mode: <AliasPatternMatch/AnyAlias/AnyIPAddress>
Determines whether a query is sent to the target zone. Default: AnyAlias.
AliasPatternMatch: queries the zone only if the alias matches the corresponding pattern type and string.
AnyAlias: queries the zone for any alias (but not IP address).
AnyIPAddress: queries the zone for any given IP address (but not alias).
Example: xConfiguration Zones Policy SearchRules Rule 1 Mode: AnyAlias
Zones Policy SearchRules Rule [1..2000] Name: <S: 0,50>
Descriptive name for the search rule.
Example: xConfiguration Zones Policy SearchRules Rule 1 Name: "DNS lookup"
Zones Policy SearchRules Rule [1..2000] Pattern Behavior: <Strip/Leave/Replace>
Determines whether the matched part of the alias is modified before being sent to the target zone. (Applies to Alias Pattern Match
mode only.) Default: Strip.
Leave: the alias is not modified.
Strip: the matching prefix or suffix is removed from the alias.
Replace: the matching part of the alias is substituted with the text in the replace string.
Example: xConfiguration Zones Policy SearchRules Rule 1 Pattern Behavior: Strip
Zones Policy SearchRules Rule [1..2000] Pattern Replace: <S: 0,60>
The string to substitute for the part of the alias that matches the pattern. (Applies to Replace pattern behavior only.)
Example: xConfiguration Zones Policy SearchRules Rule 1 Pattern Replace: "@example.net"
Zones Policy SearchRules Rule [1..2000] Pattern String: <S: 0,60>
The pattern against which the alias is compared. (Applies to Alias Pattern Match mode only.)
Example: xConfiguration Zones Policy SearchRules Rule 1 Pattern String: "@example.com"
445

Zones Policy SearchRules Rule [1..2000] Pattern Type: <Exact/Prefix/Suffix/Regex>
How the pattern string must match the alias for the rule to be applied. (Applies to Alias Pattern Match mode only.) Default: Prefix.
Exact: the entire string must exactly match the alias character for character.
Regex: the string is treated as a regular expression.
Example: xConfiguration Zones Policy SearchRules Rule 1 Pattern Type: Suffix
Zones Policy SearchRules Rule [1..2000] Priority: <1..65534>
The order in the search process that this rule is applied, when compared to the priority of the other search rules. All Priority 1
search rules are applied first, followed by all Priority 2 search rules, and so on. Default: 100 .
Example: xConfiguration Zones Policy SearchRules Rule 1 Priority: 100
Zones Policy SearchRules Rule [1..2000] Progress: <Continue/Stop>
Specifies the ongoing search behavior if the alias matches this search rule. If 'stop' is selected, any rules with the same priority
level as this rule are still applied. Default: Continue.
Continue: continue applying the remaining search rules (in priority order) until the endpoint identified by the alias is found.
Stop: do not apply any more search rules, even if the endpoint identified by the alias is not found in the target zone.
Example: xConfiguration Zones Policy SearchRules Rule 1 Progress: Continue
Zones Policy SearchRules Rule [1..2000] Protocol: <Any/H323/SIP>
The source protocol required for the rule to match.
Example: xConfiguration Zones Policy SearchRules Rule 1 Protocol: Any
Zones Policy SearchRules Rule [1..2000] Source Mode: <Any/AllZones/LocalZone/Named>
The sources of the requests for which this rule applies. Default: Any.
Any: locally registered devices, neighbor or traversal zones, and any non-registered devices.
All zones: locally registered devices plus neighbor or traversal zones.
Local Zone: locally registered devices only.
Named: A specific Zone or SubZone.
Example: xConfiguration Zones Policy SearchRules Rule 1 Source Mode: Any
Zones Policy SearchRules Rule [1..2000] Source Name: <S: 0..50>
The name of the source (Sub)Zone for which this rule applies.
Example: xConfiguration Zones Policy SearchRules Rule 1 Source Name: "Local Office"
Zones Policy SearchRules Rule [1..2000] State: <Enabled/Disabled>
Indicates if the search rule is enabled or disabled. Disabled search rules are ignored. Default: Enabled .
Example: xConfiguration Zones Policy SearchRules Rule 1 State: Enabled
446

Zones Policy SearchRules Rule [1..2000] Target Name: <S: 0,50>
The zone or policy service to query if the alias matches the search rule.
Example: xConfiguration Zones Policy SearchRules Rule 1 Target Name: "Sales Office"
Zones Policy SearchRules Rule [1..2000] Target Type: <Zone/PolicyService>
The type of target this search rule applies to.
Example: xConfiguration Zones Policy SearchRules Rule 1 Target Type: Zone
Zones Zone [1..1000] DNS IncludeAddressRecord: <On/Off>
Determines whether, if no NAPTR (SIP) or SRV (SIP and H.323) records have been found for the dialed alias via this zone, the VCS
will then query for A and AAAA DNS Records. Default: Off .
Example: xConfiguration Zones Zone 1 DNS IncludeAddressRecord: Off
Zones Zone [1..1000] DNS Interworking SIP Audio DefaultCodec: <G711u/G711a/G722_48/G722_56/

G722_64/G722_1_16/G722_1_24/G722_1_32/G722_1_48/G723_1/G728/G729/AACLD_48/AACLD_56/
AACLD_64/AMR>
Specifies which audio codec to use when empty INVITEs are not allowed. Default: G711u .
Example: xConfiguration Zones Zone 1 DNS Interworking SIP Audio DefaultCodec: G711u
Zones Zone [1..1000] DNS Interworking SIP EmptyInviteAllowed: <On/Off>
Controls if the VCS will generate a SIP INVITE message with no SDP to send to this zone. INVITEs with no SDP mean that the
destination device is asked to initiate the codec selection, and are used when the call has been interworked locally from H.323.
Default: On.
On: SIP INVITEs with no SDP will be generated and sent to this neighbor.
Off: SIP INVITEs will be generated and a pre-configured SDP will be inserted before the INVITEs are sent to this neighbor.
Example: xConfiguration Zones Zone 1 DNS Interworking SIP EmptyInviteAllowed: On
Zones Zone [1..1000] DNS Interworking SIP Video DefaultBitrate: <64..65535>
Specifies which video bit rate to use when empty INVITEs are not allowed. Default: 384 .
Example: xConfiguration Zones Zone 1 DNS Interworking SIP Video DefaultBitrate: 384
Zones Zone [1..1000] DNS Interworking SIP Video DefaultCodec: <None/H261/H263/H263p/H263pp/H264>
Specifies which video codec to use when empty INVITEs are not allowed. Default: H263 .
Example: xConfiguration Zones Zone 1 DNS Interworking SIP Video DefaultCodec: H263
Zones Zone [1..1000] DNS Interworking SIP Video DefaultResolution: <None/QCIF/CIF/4CIF/SIF/4SIF/VGA/SVGA/XGA>
Specifies which video resolution to use when empty INVITEs are not allowed. Default: CIF .
Example: xConfiguration Zones Zone 1 DNS Interworking SIP Video DefaultResolution: CIF
Zones Zone [1..1000] DNS SIP Default Transport: <UDP/TCP/TLS>
Determines which transport type is used for SIP calls from the DNS zone, when DNS NAPTR records and SIP URI parameters do
not provide the preferred transport information. RFC 3263 suggests that UDP should be used. Default: UDP.
Example: xConfiguration Zones Zone [1..1000] DNS SIP Default Transport: UDP
447

Zones Zone [1..1000] DNS SIP Media Encryption Mode: <Off/On/BestEffort/Auto>
Example: xConfiguration Zones Zone 1 DNS SIP Media Encryption Mode: Auto
Zones Zone [1..1000] DNS SIP Poison Mode: <On/Off>
Determines whether SIP requests sent out to this zone will be "poisoned" such that if they are received by the local VCS again they
will be rejected. Default: Off .
On: SIP requests sent out via this zone that are received again by this VCS will be rejected.
Off: SIP requests sent out via this zone that are received by this VCS again will be processed as normal.
Example: xConfiguration Zones Zone 1 DNS SIP Poison Mode: Off
Zones Zone [1..1000] DNS SIP Record Route Address Type: <IP/Hostname>
zone. Note: setting this value to Hostname also requires a valid DNS system host name to be configured on the VCS. Default: IP.
Example: xConfiguration Zones Zone 1 DNS SIP Record Route Address Type: IP
Zones Zone [1..1000] DNS SIP SearchAutoResponse: <On/Off>
Controls what happens when the VCS receives a SIP search that originated as an H.323 search, destined for this zone. Default: Off
.
Off: a SIP OPTION message will be sent to the zone.
On: searches will be responded to automatically, without being forwarded to the zone.
Example: xConfiguration Zones Zone 1 DNS SIP SearchAutoResponse: Off
Zones Zone [1..1000] DNS SIP TLS Verify Mode: <On/Off>
Controls X.509 certificate checking between this VCS and the destination system server returned by the DNS lookup. When
enabled, the domain name submitted to the DNS lookup must be contained within the server's X.509 certificate (in either the
Subject Common Name or the Subject Alternative Name attributes). Default: Off .
Example: xConfiguration Zones Zone 1 DNS SIP TLS Verify Mode: On
Zones Zone [1..1000] DNS SIP TLS Verify Subject Name: <S: 0..128>
The certificate holder's name to look for in the traversal client's X.509 certificate (must be in either the Subject Common Name or
the Subject Alternative Name attributes). If empty then the domain portion of the resolved URI is used.
Example: xConfiguration Zones Zone 1 DNS SIP TLS Verify Subject Name: "example.com"
448

Zones Zone [1..1000] DNS SIP UDP BFCP Filter Mode: <On/Off>
Determines whether INVITE requests sent to this zone filter out UDP/BFCP. This option may be required to enable interoperability
with SIP devices that do not support the UDP/BFCP protocol. Default: Off .
On: any media line referring to the UDP/BFCP protocol is replaced with TCP/BFCP and disabled.
Example: xConfiguration Zones Zone 1 DNS SIP UDP BFCP Filter Mode: Off
Zones Zone [1..1000] DNS ZoneProfile: <Default/Custom/CiscoUnifiedCommunicationsManager/

CiscoUnifiedCommunicationsManagerBFCP/NortelCS1000/NonRegisteringDevice/LocalB2BUAService>
Determines how the zone's advanced settings are configured.
Default: uses the factory defaults.
Custom: allows you to configure each setting individually.
Preconfigured profiles: alternatively, choose one of the preconfigured profiles to automatically use the appropriate settings required
for connections to that type of system.
Example: xConfiguration Zones Zone 1 DNS ZoneProfile: Default
Zones Zone [1..1000] ENUM DNSSuffix: <S: 0, 128>
The DNS zone to append to the transformed E.164 number to create an ENUM host name which this zone is then queried for.
Example: xConfiguration Zones Zone 2 ENUM DNSSuffix: "e164.arpa"
Zones Zone [1..1000] H323 Mode: <On/Off>
Determines whether H.323 calls will be allowed to and from this zone. Default: On .
Example: xConfiguration Zones Zone 2 H323 Mode: On
Zones Zone [1..1000] HopCount: <1..255>
Specifies the hop count to be used when sending an alias search request to this zone. Note: if the search request was received
from another zone and already has a hop count assigned, the lower of the two values will be used. Default: 15 .
Example: xConfiguration Zones Zone 2 HopCount: 15
Zones Zone [1..1000] Name: <S: 1, 50>
Assigns a name to this zone.
Example: xConfiguration Zones Zone 3 Name: "UK Sales Office"
Zones Zone [1..1000] Neighbor Authentication Mode: <DoNotCheckCredentials/TreatAsAuthenticated/

CheckCredentials>
Example: xConfiguration Zones Zone 3 Neighbor Authentication Mode: DoNotCheckCredentials
Zones Zone [1..1000] Neighbor H323 CallSignaling Port: <1024..65534>
The port on the neighbor to use for H.323 calls to and from this VCS. Default: 1720 .
Example: xConfiguration Zones Zone 3 Neighbor H323 CallSignaling Port: 1720
449

Zones Zone [1..1000] Neighbor H323 Port: <1024..65534>
The port on the neighbor to use for H.323 searches to and from this VCS. Default: 1719 .
Example: xConfiguration Zones Zone 3 Neighbor H323 Port: 1719
Zones Zone [1..1000] Neighbor H323 SearchAutoResponse: <On/Off>
Determines what happens when the VCS receives a H323 search, destined for this zone. Default: Off.
Off: an LRQ message will be sent to the zone.
Example: xConfiguration Zones Zone 3 Neighbor H323 SearchAutoResponse: Off
Zones Zone [1..1000] Neighbor Interworking SIP Audio DefaultCodec: <G711u/G711a/G722_48/G722_56/

G722_64/G722_1_16/G722_1_24/G722_1_32/G722_1_48/G723_1/G728/G729/AACLD_48/AACLD_56/AACLD_64/AMR>
Specifies which audio codec to use when empty INVITEs are not allowed. Default: G711u .
Example: xConfiguration Zones Zone 3 Neighbor Interworking SIP Audio DefaultCodec: G711u
Zones Zone [1..1000] Neighbor Interworking SIP EmptyInviteAllowed: <On/Off>
Determines whether the VCS will generate a SIP INVITE message with no SDP to send to this zone. INVITEs with no SDP mean
that the destination device is asked to initiate the codec selection, and are used when the call has been interworked locally from
H.323. Default: On .
On: SIP INVITEs with no SDP will be generated and sent to this neighbor.
Off: SIP INVITEs will be generated and a pre-configured SDP will be inserted before the INVITEs are sent to this neighbor.
Example: xConfiguration Zones Zone 3 Neighbor Interworking SIP EmptyInviteAllowed: On
Zones Zone [1..1000] Neighbor Interworking SIP Encryption EncryptSRTCP: <Yes/No>
Controls if the VCS offers encrypted SRTCP in calls to this zone. The VCS will send an INFO request. Default: No.
Example: xConfiguration Zones Zone 3 Neighbor Interworking SIP Encryption EncryptSRTCP: No
Zones Zone [1..1000] Neighbor Interworking SIP Search Strategy: <Options/Info>
Determines how the VCS will search for SIP endpoints when interworking an H.323 call. Default: Options .
Options: the VCS will send an OPTIONS request.
Info: the VCS will send an INFO request.
Example: xConfiguration Zones Zone 3 Neighbor Interworking SIP Search Strategy: Options
Zones Zone [1..1000] Neighbor Interworking SIP Video DefaultBitrate: <64..65535>
Specifies which video bit rate to use when empty INVITEs are not allowed. Default: 384 .
Example: xConfiguration Zones Zone 3 Neighbor Interworking SIP Video DefaultBitrate: 384
Zones Zone [1..1000] Neighbor Interworking SIP Video DefaultCodec: <None/H261/H263/H263p/H263pp/H264>
Specifies which video codec to use when empty INVITEs are not allowed. Default: H263 .
Example: xConfiguration Zones Zone 3 Neighbor Interworking SIP Video DefaultCodec: H263
450

Zones Zone [1..1000] Neighbor Interworking SIP Video DefaultResolution: <None/QCIF/CIF/4CIF/SIF/4SIF/VGA/SVGA/XGA>
Specifies which video resolution to use when empty INVITEs are not allowed. Default: CIF .
Example: xConfiguration Zones Zone 3 Neighbor Interworking SIP Video DefaultResolution: CIF
Zones Zone [1..1000] Neighbor Monitor: <Yes/No>
Specifies whether the zone monitors the aliveness of its neighbor peers. H323 LRQs and/or SIP OPTIONS will be periodically sent
to the peers. If any peer fails to respond, that peer will be marked as inactive. If no peer manages to respond the zone will be
marked as inactive. Default: Yes.
Example: xConfiguration Zones Zone 3 Neighbor Monitor: Yes
Zones Zone [1..1000] Neighbor Peer [1..6] Address: <S:0,128>
Specifies the IP address or Fully Qualified Domain Name (FQDN) of the neighbor. If the neighbor zone is a VCS cluster, this will be
one of the peers in that cluster.
Example: xConfiguration Zones Zone 3 Neighbor Peer 1 Address: "192.44.0.18"
Zones Zone [1..1000] Neighbor Registrations: <Allow/Deny>
Controls whether proxied SIP registrations routed through this zone are accepted. Default: Allow .
Example: xConfiguration Zones Zone 3 Neighbor Registrations: Allow
Zones Zone [1..1000] Neighbor SIP Authentication Trust Mode: <On/Off>
Controls if authenticated SIP messages (ones containing a P-Asserted-Identity header) from this zone are trusted. Default: Off .
On: messages are trusted without further challenge.
Off: messages are challenged for authentication.
Example: xConfiguration Zones Zone 3 Neighbor SIP Authentication Trust Mode: On
Zones Zone [1..1000] Neighbor SIP B2BUA Service Identifier: <0..64>
The identifier that represents an instance of a local SIP Back-to-Back User Agent service.
Example: xConfiguration Zones Zone 3 Neighbor SIP B2BUA Service Identifier: 1
Zones Zone [1..1000] Neighbor SIP ClassFiveResponseLiveness: <Yes/No>
Specifies whether Class 5 SIP responses from neighbor peers result in the zone being considered alive for use. Default: Yes.
Example: xConfiguration Zones Zone 3 Neighbor SIP ClassFiveResponseLiveness: Yes
Zones Zone [1..1000] Neighbor SIP Encryption Mode: <Auto/Microsoft/Off>
Determines how the VCS handles encrypted SIP calls on this zone. Default: Auto.
Auto: SIP calls are encrypted if a secure SIP transport (TLS) is used.
Microsoft: SIP calls are encrypted using MS-SRTP.
Off: SIP calls are never encrypted.
Example: xConfiguration Zones Zone 3 Neighbor SIP Encryption Mode: Auto
451

Zones Zone [1..1000] Neighbor SIP MIME Strip Mode: <On/Off>
Controls whether multipart MIME stripping is performed on requests from this zone. This must be set to On for connections to a
Microsoft Office Communications Server 2007. Default: Off .
Example: xConfiguration Zones Zone 3 Neighbor SIP MIME Strip Mode: Off
Zones Zone [1..1000] Neighbor SIP Media Encryption Mode: <Off/On/BestEffort/Auto>
The media encryption policy applied by the VCS for SIP calls (including interworked calls) to and from this zone. Default: Auto
Example: xConfiguration Zones Zone 3 Neighbor SIP Media Encryption Mode: Auto
Zones Zone [1..1000] Neighbor SIP MediaRouting Mode: <Auto/Signaled/Latching>
How the VCS handles media for calls to and from this neighbor, and where it will forward the media destined for this neighbor.
Default: Auto. .
Signaled: media is always taken for calls to and from this neighbor. It will be forwarded as signaled in the SDP received from this
neighbor.
Latching: media is always taken for calls to and from this neighbor. It will be forwarded to the IP address and port from which
media from this neighbor is received.
Auto: media is only taken if the call is a traversal call. If this neighbor is behind a NAT the VCS will forward the media to the IP
address and port from which media from this zone is received (latching). Otherwise it will forward the media to the IP address and
port signaled in the SDP (signaled).
Example: xConfiguration Zones Zone 3 Neighbor SIP MediaRouting Mode: Auto
Zones Zone [1..1000] Neighbor SIP Poison Mode: <On/Off>
Controls whether SIP requests sent out to this zone will be "poisoned" such that if they are received by the local VCS again they
will be rejected. Default: Off .
Example: xConfiguration Zones Zone 3 Neighbor SIP Poison Mode: Off
Zones Zone [1..1000] Neighbor SIP Port: <1024..65534>
Specifies the port on the neighbor to be used for SIP calls to and from this VCS. Default: 5061 .
Example: xConfiguration Zones Zone 3 Neighbor SIP Port: 5061
Zones Zone [1..1000] Neighbor SIP ProxyRequire Strip List: <S: 0,255>
A comma separated list of option tags to search for and remove from Proxy-Require headers in SIP requests received from this
zone. By default, no option tags are specified.
Example: xConfiguration Zones Zone 3 Neighbor SIP ProxyRequire Strip List:

"com.example.something,com.example.somethingelse"
452

Zones Zone [1..1000] Neighbor SIP RFC3327 Enabled: <Yes/No>
Controls whether the VCS will insert RFC3327 Path headers when proxying REGISTER messages toward this zone. If disabled the
VCS will instead rewrite the contact header to allow interworking with SIP registrars that do not support RFC3327. Default: Yes.
Example: xConfiguration Zones Zone [1..1000] Neighbor SIP RFC3327 Enabled: Yes
Zones Zone [1..1000] Neighbor SIP Record Route Address Type: <IP/Hostname>
zone. Note: setting this value to Hostname also requires a valid DNS system host name to be configured on the VCS. Default: IP.
Example: xConfiguration Zones Zone 3 Neighbor SIP Record Route Address Type: IP
Zones Zone [1..1000] Neighbor SIP SearchAutoResponse: <On/Off>
Controls what happens when the VCS receives a SIP search that originated as an H.323 search, destined for this zone. Default: Off
.
Off: a SIP OPTION message will be sent to the zone.
Example: xConfiguration Zones Zone 3 Neighbor SIP SearchAutoResponse: Off
Zones Zone [1..1000] Neighbor SIP TLS Verify Mode: <On/Off>
Controls X.509 certificate checking and mutual authentication for inbound and outbound connections between this VCS and the
neighbor system. When enabled, the neighbor system's FQDN or IP address, as specified in the Peer address field, must be
contained within the neighbor's X.509 certificate (in either the Subject Common Name or the Subject Alternative Name attributes).
Default: Off .
Example: xConfiguration Zones Zone 3 Neighbor SIP TLS Verify Mode: On
Zones Zone [1..1000] Neighbor SIP Transport: <UDP/TCP/TLS>
Determines which transport type will be used for SIP calls to and from this neighbor. Default: TLS .
Example: xConfiguration Zones Zone 3 Neighbor SIP Transport: TLS
Zones Zone [1..1000] Neighbor SIP UDP BFCP Filter Mode: <On/Off>
Determines whether INVITE requests sent to this zone filter out UDP/BFCP. This option may be required to enable interoperability
with SIP devices that do not support the UDP/BFCP protocol. Default: Off .
On: any media line referring to the UDP/BFCP protocol is replaced with TCP/BFCP and disabled.
Example: xConfiguration Zones Zone 3 Neighbor SIP UDP BFCP Filter Mode: Off
Zones Zone [1..1000] Neighbor SIP UPDATE Strip Mode: <On/Off>
Determines whether the VCS strips the UPDATE method from the Allow header of all requests and responses going to and from this
zone. Default: Off .
Example: xConfiguration Zones Zone 3 Neighbor SIP UPDATE Strip Mode: Off
453

Zones Zone [1..1000] Neighbor SignalingRouting Mode: <Auto/Always>
Specifies how the VCS handles the signaling for calls to and from this neighbor. Default: Auto.
Auto: Signaling will be taken as determined by the Call Routed Mode configuration.
Always: Signaling will always be taken for calls to or from this neighbor, regardless of the Call Routed Mode configuration.
Example: xConfiguration Zones Zone 3 Neighbor SignalingRouting Mode: Auto
Zones Zone [1..1000] Neighbor ZoneProfile: <Default/Custom/CiscoUnifiedCommunicationsManager/

CiscoUnifiedCommunicationsManagerBFCP/NortelCS1000/NonRegisteringDevice/LocalB2BUAService>
Determines how the zone's advanced settings are configured.
Default: uses the factory defaults.
Custom: allows you to configure each setting individually.
Preconfigured profiles: alternatively, choose one of the preconfigured profiles to automatically use the appropriate settings required
for connections to that type of system.
Example: xConfiguration Zones Zone 3 Neighbor ZoneProfile: Default
Zones Zone [1..1000] SIP Mode: <On/Off>
Determines whether SIP calls will be allowed to and from this zone. Default: On.
Example: xConfiguration Zones Zone 3 SIP Mode: On
Zones Zone [1..1000] TraversalClient Accept Delegated Credential Checks: <On/Off>
Controls whether this traversal client accepts delegated credential checking requests from the VCS Expressway. Default: Off.
Off: reject the requests.
On: accept the requests and perform the credential checking using the authentication methods configured on this VCS.
Example: xConfiguration Zones Zone [1..1000] TraversalClient Accept Delegated Credential Checks: Off
Zones Zone [1..1000] TraversalClient Authentication Mode:

Example: xConfiguration Zones Zone 4 TraversalClient Authentication Mode: DoNotCheckCredentials
Zones Zone [1..1000] TraversalClient Authentication Password: <S: 0,215>
The password used by the VCS when connecting to the traversal server. The maximum plaintext length is 128 characters, which is
then encrypted.
Example: xConfiguration Zones Zone 4 TraversalClient Authentication Password: "password123"
Zones Zone [1..1000] TraversalClient Authentication UserName: <S: 0,128>
The user name used by the VCS when connecting to the traversal server.
Example: xConfiguration Zones Zone 4 TraversalClient Authentication UserName: "clientname"
454

Zones Zone [1..1000] TraversalClient H323 Port: <1024..65534>
The port on the traversal server to use for H.323 firewall traversal calls from this VCS. If the traversal server is a VCS Expressway,
this must be the port number that is configured on the VCS Expressway's traversal server zone associated with this VCS.
Example: xConfiguration Zones Zone 4 TraversalClient H323 Port: 2777
Zones Zone [1..1000] TraversalClient H323 Protocol: <Assent/H46018>
Determines which of the two firewall traversal protocols will be used for calls to and from the traversal server. Note: the same
protocol must be set on the server for calls to and from this traversal client. Default: Assent.
Example: xConfiguration Zones Zone 4 TraversalClient H323 Protocol: Assent
Zones Zone [1..1000] TraversalClient Peer [1..6] Address: <S:0,128>
Specifies the IP address or Fully Qualified Domain Name (FQDN) of the traversal server. If the traversal server is a VCS
Expressway cluster, this will be one of the peers in that cluster.
Example: xConfiguration Zones Zone 4 TraversalClient Peer 1 Address: "10.192.168.1"
Zones Zone [1..1000] TraversalClient Registrations: <Allow/Deny>
Controls whether proxied SIP registrations routed through this zone are accepted. Default: Allow.
Example: xConfiguration Zones Zone 4 TraversalClient Registrations: Allow
Zones Zone [1..1000] TraversalClient RetryInterval: <1..65534>
The interval (in seconds) with which a failed attempt to establish a connection to the traversal server should be retried. Default:
120.
Example: xConfiguration Zones Zone 4 TraversalClient RetryInterval: 120
Zones Zone [1..1000] TraversalClient SIP Media Encryption Mode: <Off/On/BestEffort/Auto>
Example: xConfiguration Zones Zone 4 TraversalClient SIP Media Encryption Mode: Auto
Zones Zone [1..1000] TraversalClient SIP Poison Mode: <On/Off>
Controls whether SIP requests sent out to this zone are "poisoned" such that if they are received by the local VCS again they will
be rejected. Default: Off .
Example: xConfiguration Zones Zone 4 TraversalClient SIP Poison Mode: Off
Zones Zone [1..1000] TraversalClient SIP Port: <1024..65534>
Specifies the port on the traversal server to be used for SIP calls from this VCS. If your traversal server is a VCS Expressway, this
must be the port number that has been configured in the traversal server zone for this VCS.
Example: xConfiguration Zones Zone 4 TraversalClient SIP Port: 5061
455

Zones Zone [1..1000] TraversalClient SIP Protocol: <Assent/TURN/ICE>
Determines which firewall traversal protocol will be used for SIP calls to and from the traversal server. Note: the same protocol
must be set on the server for calls to and from this traversal client. Default: Assent.
Example: xConfiguration Zones Zone 4 TraversalClient SIP Protocol: Assent
Zones Zone [1..1000] TraversalClient SIP TLS Verify Mode: <On/Off>
Controls X.509 certificate checking and mutual authentication between this VCS and the traversal server. When enabled, the
server's FQDN or IP address, as specified in the Peer address field, must be contained within the server's X.509 certificate (in
either the Subject Common Name or the Subject Alternative Name attributes). Default: Off .
Example: xConfiguration Zones Zone 4 TraversalClient SIP TLS Verify Mode: On
Zones Zone [1..1000] TraversalClient SIP Transport: <TCP/TLS>
Determines which transport type will be used for SIP calls to and from the traversal server. Default: TLS .
Example: xConfiguration Zones Zone 4 TraversalClient SIP Transport: TLS
Zones Zone [1..1000] TraversalServer Authentication Mode:

Example: xConfiguration Zones Zone 5 TraversalServer Authentication Mode: DoNotCheckCredentials
Zones Zone [1..1000] TraversalServer Authentication UserName: <S: 0,128>
The name used by the traversal client when authenticating with the traversal server. If the traversal client is a VCS, this must be the
VCSs authentication user name. If the traversal client is a gatekeeper, this must be the gatekeepers System Name.
Example: xConfiguration Zones Zone 5 TraversalServer Authentication UserName: "User123"
Zones Zone [1..1000] TraversalServer H323 H46019 Demultiplexing Mode: <On/Off>
Determines whether the VCS will operate in demultiplexing mode for calls from the traversal client. Default: Off .
On: allows use of the same two ports for all calls.
Off: each call will use a separate pair of ports for media.
Example: xConfiguration Zones Zone 5 TraversalServer H323 H46019 Demultiplexing Mode: Off
Zones Zone [1..1000] TraversalServer H323 Port: <1024..65534>
Specifies the port on the VCS being used for H.323 firewall traversal from this traversal client. Default: 6001, incrementing by 1 for
each new zone.
Example: xConfiguration Zones Zone 5 TraversalServer H323 Port: 2777
Zones Zone [1..1000] TraversalServer H323 Protocol: <Assent/H46018>
Determines which of the two firewall traversal protocols will be used for calls to and from the traversal client. Note: the same
protocol must be set on the client for calls to and from this traversal server. Default: Assent .
Example: xConfiguration Zones Zone 5 TraversalServer H323 Protocol: Assent
456

Zones Zone [1..1000] TraversalServer Registrations: <Allow/Deny>
Controls whether proxied SIP registrations routed through this zone are accepted. Default: Allow .
Example: xConfiguration Zones Zone 5 TraversalServer Registrations: Allow
Zones Zone [1..1000] TraversalServer SIP Media Encryption Mode: <Off/On/BestEffort/Auto>
The media encryption policy applied by the VCS for SIP calls (including interworked calls) to and from this zone. Default: Auto
Example: xConfiguration Zones Zone 5 TraversalServer SIP Media Encryption Mode: Auto
Zones Zone [1..1000] TraversalServer SIP Poison Mode: <On/Off>
Controls whether SIP requests sent out to this zone are "poisoned" such that if they are received by the local VCS again they will
be rejected. Default: Off .
Example: xConfiguration Zones Zone 5 TraversalServer SIP Poison Mode: Off
Zones Zone [1..1000] TraversalServer SIP Port: <1024..65534>
The port on the VCS being used for SIP firewall traversal from this traversal client. Default: 7001, incrementing by 1 for each new
zone.
Example: xConfiguration Zones Zone 5 TraversalServer SIP Port: 5061
Zones Zone [1..1000] TraversalServer SIP Protocol: <Assent/TURN/ICE>
Determines which firewall traversal protocol will be used for SIP calls to and from the traversal client. Note: the same protocol
must be set on the client for calls to and from this traversal server. Default: Assent.
Example: xConfiguration Zones Zone 5 TraversalServer SIP Protocol: Assent
Zones Zone [1..1000] TraversalServer SIP TLS Verify Mode: <On/Off>
Controls X.509 certificate checking and mutual authentication between this VCS and the traversal client. If enabled, a TLS verify
subject name must be specified. Default: Off.
Example: xConfiguration Zones Zone 5 TraversalServer SIP TLS Verify Mode: On
Zones Zone [1..1000] TraversalServer SIP TLS Verify Subject Name: <S: 0,128>
The certificate holder's name to look for in the traversal client's X.509 certificate (must be in either the Subject Common Name or
the Subject Alternative Name attributes).
Example: xConfiguration Zones Zone 5 TraversalServer SIP TLS Verify Subject Name: "myclientname"
Zones Zone [1..1000] TraversalServer SIP Transport: <TCP/TLS>
Determines which of the two transport types will be used for SIP calls between the traversal client and VCS. Default: TLS .
Example: xConfiguration Zones Zone 5 TraversalServer SIP Transport: TLS
457

Zones Zone [1..1000] TraversalServer TCPProbe KeepAliveInterval: <1..65534>
Sets the interval (in seconds) with which the traversal client will send a TCP probe to the VCS once a call is established, in order
to keep the firewalls NAT bindings open. Default: 20.
Example: xConfiguration Zones Zone 5 TraversalServer TCPProbe KeepAliveInterval: 20
Zones Zone [1..1000] TraversalServer TCPProbe RetryCount: <1..65534>
Sets the number of times the traversal client will attempt to send a TCP probe to the VCS. Default: 5 .
Example: xConfiguration Zones Zone 5 TraversalServer TCPProbe RetryCount: 5
Zones Zone [1..1000] TraversalServer TCPProbe RetryInterval: <1..65534>
Sets the frequency (in seconds ) with which the traversal client will send a TCP probe to the VCS. Default: 2 .
Example: xConfiguration Zones Zone 5 TraversalServer TCPProbe RetryInterval: 2
Zones Zone [1..1000] TraversalServer UDPProbe KeepAliveInterval: <1..65534>
Sets the interval (in seconds) with which the traversal client will send a UDP probe to the VCS once a call is established, in order
to keep the firewalls NAT bindings open. Default: 20.
Example: xConfiguration Zones Zone 5 TraversalServer UDPProbe KeepAliveInterval: 20
Zones Zone [1..1000] TraversalServer UDPProbe RetryCount: <1..65534>
Sets the number of times the traversal client will attempt to send a UDP probe to the VCS. Default: 5.
Example: xConfiguration Zones Zone 5 TraversalServer UDPProbe RetryCount: 5
Zones Zone [1..1000] TraversalServer UDPProbe RetryInterval: <1..65534>
Sets the frequency (in seconds) with which the traversal client will send a UDP probe to the VCS. Default: 2.
Example: xConfiguration Zones Zone 5 TraversalServer UDPProbe RetryInterval: 2
Zones Zone [1..1000] Type: <Neighbor/TraversalClient/TraversalServer/ENUM/DNS>
Determines the nature of the specified zone, in relation to the local VCS.
Neighbor: the new zone will be a neighbor of the local VCS.
TraversalClient: there is a firewall between the zones, and the local VCS is a traversal client of the new zone.
TraversalServer: there is a firewall between the zones and the local VCS is a traversal server for the new zone.
ENUM: the new zone contains endpoints discoverable by ENUM lookup.
DNS: the new zone contains endpoints discoverable by DNS lookup.
Example: xConfiguration Zones Zone 3 Type: Neighbor
458
Command Reference xCommand

The xCommand group of commands are used to add and delete items and issue system commands.
The following section lists all the currently available xCommand commands.
To issue a command, type the command as shown, followed by one or more of the given parameters and values. The
valid values for each parameter are indicated in the angle brackets following each parameter, using the following
notation:
Format Meaning
<0..63> Indicates an integer value is required. The numbers indicate the minimum and maximum
value.
In this example the value must be in the range 0 to 63.
<S: 7,15> An S indicates a string value, to be enclosed in quotation marks, is required. The numbers
indicate the minimum and maximum number of characters for the string.
In this example the string must be between 7 and 15 characters long.
<Off/Direct/Indirect> Lists the set of valid values for the command. Do not enclose the value in quotation marks
(r) (r) indicates that this is a required parameter. Note that the (r) is not part of the command
itself.
To obtain information about using each of the xCommand commands from within the CLI, type:
xCommand or xCommand ? to return a list of all available xCommand commands.

xCommand ?? to return all current xCommand commands, along with a description of each command, a list of its
parameters, and for each parameter its valuespaces and description.
xCommand <command> ? to return a description of the command, a list of its parameters, and for each parameter
its valuespaces and description.
xCommand commands
All of the available xCommand commands are listed in the table below:
459
AdminAccountAdd
Adds a local administrator account.
Name(r): <S: 0, 128>
The username for this account.
Password(r): <Password>
The password for this account.
AccessAPI: <On/Off>
Whether this account is allowed to access the system's status and configuration via the API. Default: On.
AccessWeb: <On/Off>
Whether this account is allowed to log in to the system using the web interface. Default: On.
Enabled: <On/Off>
Indicates if the account is enabled or disabled. Access is denied to disabled accounts. Default: On.
Example: xCommand AdminAccountAdd Name: "bob_smith" Password: "abcXYZ_123" AccessAPI: On AccessWeb: On

Enabled: On
AdminAccountDelete
Deletes a local administrator account.
Name(r): <S: 0, 128>
The username of the account to delete.
Example: xCommand AdminAccountDelete: "bob_smith"
AdminGroupAdd
Name(r): <S: 0, 128>
The name of the administrator group.
AccessAPI: <On/Off>
Whether members of this group are allowed to access the system's status and configuration using the API. Default: On.
AccessWeb: <On/Off>
Whether members of this group are allowed to log in to the system using the web interface. Default: On.
Enabled: <On/Off>
Indicates if the group is enabled or disabled. Access is denied to members of disabled groups. Default: On.
Example: xCommand AdminGroupAdd Name: "administrators" AccessAPI: On AccessWeb: On Enabled: On
AdminGroupDelete
Deletes an administrator group.
Name(r): <S: 0, 128>
The name of the group to delete.
Example: xCommand AdminGroupDelete: "administrators"
460
AdsDcAdd
Adds a new Active Directory server.
ActiveDirectoryAddress(r): <S: 0,39>
The address of a domain controller that can be used when the VCS joins the AD domain. Not specifying a specific AD will result
the use of DNS SRV queries to find an AD.
Example: xCommand AdsDcAdd ActiveDirectoryAddress: "192.168.0.0"
AdsDcDelete
Deletes an Active Directory server.
ActiveDirectoryId(r): <1..5>
The index of the Active Directory server to be deleted.
Example: xCommand AdsDcDelete ActiveDirectoryId: 1
AdsKdcAdd
Adds a new Kerberos KDC.
KerberosKDCAddress(r): <S: 0,39>
The address of a Kerberos Distribution Center (KDC) to be used when connected to the AD domain. Not specifying a specific
KDC will result in the use of DNS SRV queries to find a KDC.
KerberosKDCPort: <1..65534>
Specifies the port of a KDC that can be used when the VCS joins the AD domain. Default: 88
Example: xCommand AdsKdcAdd KerberosKDCAddress: "192.168.0.0" KerberosKDCPort: 88
AdsKdcDelete
Deletes a configured Kerberos KDC.
KerberosKDCId(r): <1..5>
The index of the Kerberos KDC to be deleted.
Example: xCommand AdsKdcDelete KerberosKDCId: 1
AllowListAdd
Adds an entry to the Allow List.
PatternString(r): <S: 1, 60>
Specifies an entry to be added to the Allow List. If one of an endpoint's aliases matches one of the patterns in the Allow List, the
registration will be permitted.
PatternType: <Exact/Prefix/Suffix/Regex>
Specifies whether the entry in the Allow List is a prefix, suffix, regular expression, or must be matched exactly. Exact: the string
must match the alias character for character. Prefix: the string must appear at the beginning of the alias. Suffix: the string must
appear at the end of the alias. Regex: the string will be treated as a regular expression.
Default: Exact.
Description: <S: 0,64>
A free-form description of the Allow List rule.
Example: xCommand AllowListAdd PatternString: "[email protected]" PatternType: Exact Description:

"Allow John Smith"
461
AllowListDelete
Deletes an entry from the Allow List.
AllowListId(r): <1..2500>
The index of the entry to be deleted.
Example: xCommand AllowListDelete AllowListId: 2
Boot
Reboots the VCS.
This command has no parameters.
Example: xCommand boot
CheckBandwidth
A diagnostic tool that returns the status and route (as a list of nodes and links) that a call of the specified type and bandwidth would
take between two nodes. Note that this command does not change any existing system configuration.
Node1(r): <S: 1, 50>
The subzone or zone from which the call originates.
Node2(r): <S: 1, 50>
The subzone or zone at which the call terminates.
Bandwidth(r): <1..100000000>
The requested bandwidth of the call (in kbps).
CallType(r): <Traversal/NonTraversal>
Whether the call type is Traversal or Non-traversal.
Example: xCommand CheckBandwidth Node1: "DefaultSubzone" Node2: "UK Sales Office" Bandwidth: 512 CallType:
nontraversal
CheckPattern
A diagnostic tool that allows you to check the result of an alias transform (local or zone) before you configure it on the system.
Target(r): <S: 1, 60>
The alias you want to use to test the pattern match or transform.
Pattern(r): <S: 1, 60>
The pattern against which the alias is compared.
Type(r): <Exact/Prefix/Suffix/Regex>
How the pattern string must match the alias for the pattern behavior to be applied.
Behavior(r): <Strip/Leave/Replace/AddPrefix/AddSuffix>
How the alias is modified.
Replace: <S: 0, 60>
Example: xCommand CheckPattern Target: "[email protected]" Pattern: "@a.net" Type: "suffix" Behavior: replace
Replace: "@a.com"
462
ClearAllStatus
Clears all status and history on the system.
Example: xCommand ClearAllStatus
CredentialAdd
Adds an entry to the local authentication database.
Name(r): <String>
Defines the name for this entry in the local authentication database.
Password(r): <Password>
Defines the password for this entry in the local authentication database.
The maximum plaintext length is 128 characters, which will then be encrypted.
Example: xCommand CredentialAdd Name: "alice" Password: "abcXYZ_123"
CredentialDelete
Deletes an entry from the local authentication database.
Name(r): <String>
The name of the entry to delete.
Example: xCommand CredentialDelete Name: "alice"
Cucmconfigadd
Performs a lookup on a Unified CM publisher.
Address(r): <Value>
The FQDN or IP address of the Unified CM publisher.
Axlpassword(r): <Value>
The password used by the VCS to access the Unified CM publisher.
Axlusername(r): <Value>
The user name used by the VCS to access the Unified CM publisher.
CertValidationDisabled: <On/Off>
Controls X.509 certificate checking against the certificate presented by the Unified CM publisher. Default: On
Example: xCommand Cucmconfigadd Address: "cucm.example.com" Axlpassword: "xyz" Axlusername: "abc"
Cucmconfigdelete
Deletes the details of a Unified CM publisher.
Address(r): <Value>
The FQDN or IP address of the Unified CM publisher.
Example: xCommand Cucmconfigdelete Address: "cucm.example.com"
463
DefaultLinksAdd
Restores links between the Default Subzone, Traversal Subzone and the Default Zone.
Example: xCommand DefaultLinksAdd
DefaultValuesSet
Resets system parameters to default values. Level 1 resets most configuration items to their default value, with the exception of the
Level 2 and Level 3 items. Level 2 resets configuration items related to remote authentication, plus Level 1 items to their default
value. Level 3 resets all critical configuration items, plus Level 1 and Level 2 items to their default value.
Level(r): <1..3>
The level of system parameters to be reset.
Example:xCommand DefaultValuesSet Level: 1
DenyListAdd
Adds an entry to the Deny List.
PatternString(r): <S: 1, 60>
Specifies an entry to be added to the Deny List. If one of an endpoint's aliases matches one of the patterns in the Deny List, the
registration will not be permitted.
PatternType: <Exact/Prefix/Suffix/Regex>
Specifies whether the entry in the Deny List is a prefix, suffix, regular expression, or must be matched exactly. Exact: the string
must match the alias character for character. Prefix: the string must appear at the beginning of the alias. Suffix: the string must
appear at the end of the alias. Regex: the string will be treated as a regular expression.
Default: Exact.
Description: <S: 0, 64>
A free-form description of the Deny List rule.
Example: xCommand DenyListAdd PatternString: "[email protected]" PatternType: exact Description:

"Deny Sally Jones"
DenyListDelete
Deletes an entry from the Deny List.
DenyListId(r): <1..2500>
The index of the entry to be deleted.
Example: xCommand DenyListDelete DenyListId: 2
DisconnectCall
Disconnects a call.
Call: <1..1000>
The index of the call to be disconnected.
CallSerialNumber: <S: 1, 255>
The serial number of the call to be disconnected. You must specify either a call index or a call serial number.
Example: xCommand DisconnectCall CallSerialNumber: "6d843434-211c-11b2-b35d-0010f30f521c"
464
Dnslookup
Queries DNS for a supplied hostname.
Hostname: <Value>
The name of the host you want to query.
RecordType: <all/a/aaaa/srv/naptr>
The type of record you want to search for. If not specified, all record types are returned.
Example: xCommand Dnslookup Hostname: "example.com" RecordType: all
DNSPerDomainServerAdd
Adds a DNS server to use only for resolving hostnames for specific domains.
Address(r): <Value>
The IP address of the DNS server to use when resolving hostnames for the associated domain names.
Domain1(r): <Value>
The domain to associate with the specific DNS server.
Domain2(r): <Value>
An optional second domain to associate with the specific DNS server.
Index: <0..5>
The index of the server to add.
Example: xCommand DNSServerAdd Address: "192.168.12.0" Index: 1
DNSPerDomainServerDelete
Deletes a DNS server used for resolving hostnames for a specific domain.
Address: <Value>
The IP address of the DNS server to delete.
Example: xCommand DNSPerDomainServerDelete Address: "192.168.12.0"
DNSServerAdd
Adds a default DNS server. Default servers are used if there is no per-domain DNS server defined for the domain being looked up.
Address(r): <Value>
The IP address of a default DNS server to use when resolving domain names.
Index: <0..5>
The index of the server to add.
Example: xCommand DNSServerAdd Address: "192.168.12.0" Index: 1
DNSServerDelete
Deletes a DNS server
Address: <Value>
The IP address of the DNS server to delete.
Example: xCommand DNSServerDelete Address: "192.168.12.0"
465
DomainAdd
Adds a domain for which this VCS is authoritative.
Name(r): <S: 1, 128>
The domain name. It can comprise multiple levels. Each level's name can only contain letters, digits and hyphens, with each
level separated by a period (dot). A level name cannot start or end with a hyphen, and the final level name must start with a
letter.
Authzone: <S: 1, 128>
The name of the traversal zone to use when delegating credential checks for SIP messages for this domain. Leave this parameter
unspecified if you want this VCS Expressway to perform the credential checking.
Edgesip: <On/Off>
Endpoint registration, call control and provisioning services are provided by Unified CM. Default: Off.
Edgexmpp: <On/Off>
Instant messaging and presence services for this SIP domain are provided by the Unified CM IM&P service. Default: Off.
Sip: <On/Off>
Controls whether the VCS is authoritative for this domain. The VCS acts as a SIP registrar and Presence Server for the domain,
and will accept registration requests for any SIP endpoints attempting to register with an alias that includes this domain. Default:
On.
Xmppfederation: <On/Off>
Controls whether the domain is available for XMPP federation. Default: Off.
Example: xCommand DomainAdd Name: "100.example-name.com" Authzone: "Traversal zone" Edge: Off Sip: On
DomainDelete
Deletes a domain.
DomainId(r): <1..200>
The index of the domain to be deleted.
Example: xCommand DomainDelete DomainId: 2
Edgessodeletetokens
Deletes all tokens issued to a particular user.
Username(r): <String>
Specifes which user's tokens will be deleted.
Example: xCommand Edgessodeletetokens Username: "APerson"
Edgessopurgetokens
Deletes all tokens issued to all users.
Example: xCommand Edgessopurgetokens
Edgessostatusclear
Resets the SSOrequest/response counters to 0.
Example: xCommand Edgessostatusclear
466
ExtAppStatusAdd
Allows another application running on the VCS to attach xstatus to the VCS XML xstatus tree.
Note: this command is intended for developer use only.
Name(r): <S:1, 64>
Filename(r): <S:0, 255>
XML file containing status that is to be attached for an external application.
Example: xCommand ExtAppStatusAdd Name: "foo" Filename: "foo.xml"
ExtAppStatusDelete
Deletes an external application status entry.
Name(r): <S:1, 64>
Example: xCommand ExtAppStatusDelete Name: foo
Fail2ban
Configures automated intrusion protection categories.
Argument: <S:1, 64>
The value applied by the command.
Command: <unbanip/banip/reload/bantime/findtime/maxretry/addignoreip/delignoreip/status>
The action to take.
Jail: <S:1, 64>
The category to which the command is applied.
Example: xCommand Fail2ban Argument "192.0.12.0" Command: addignoreip Jail: sip-auth
Fail2banExemptionAdd
Adds an automated intrusion protection exemption.
Address: <String>
The IPaddress / range that is exempted from Fail2ban intrusion protection.
Jail: <http-ce-auth/web-intrusion/ssh-intrusion/apache-auth/sshpfwd-intrusion/xmpp-intrusion/sip-auth/sip-reg/sip-
violations/http-ce-intrusion/web-auth/ssh-auth/http-ce-resource_access>
The exempted categories for the corresponding address range
Example:xCommand Fail2banExemptionAdd Address: "192.0.0.18/32" Jail: "ssh-auth"
Fail2banExemptionDelete
Removes an automated intrusion protection exemption.
467
FeedbackDeregister
Deactivates a particular feedback request.
ID: <1..3>
The index of the feedback request to be deactivated.
Example: xCommand FeedbackDeregister ID: 1
FeedbackRegister
Activates notifications on the event or status changes described by the expressions. Notifications are sent in XML format to the
specified URL. Up to 15 expressions may be registered for each of 3 feedback IDs.
ID: <1..3>
The ID of this particular feedback request.
URL(r): <S: 1, 256>
The URL to which notifications are to be sent.
Expression.1..15: <S: 1, 256>
The events or status change to be notified. Valid Expressions are:
Status/Ethernet Status/Calls Event/CallDisconnected

Event/ Status/NTP Status/Registrations
Event/CallFailure Event/Bandwidth Status/LDAP
Status/Zones Event/RegistrationAdded Event/Locate
Status/Feedback Event/CallAttempt Event/RegistrationRemoved
Event/ResourceUsage Status/ExternalManager Event/CallConnected
Event/RegistrationFailure Event/AuthenticationFailure
Example: xCommand FeedbackRegister ID: 1 URL: "http://192.168.0.1/feedback/" Expression.1: "Status/Calls"
Expression.2: "Event/CallAttempt"
FindRegistration
Returns information about the registration associated with the specified alias. The alias must be registered on the VCS on which the
command is issued.
Alias(r): <S: 1, 60>
The alias that you wish to find out about.
Example: xCommand FindRegistration Alias: "[email protected]"
Fips
Sets FIPS140-2 cryptographic mode.
Command: <leave/enter/status>
Either enters, leaves or provides the current status of the system's FIPS140-2 cryptographic mode.
Example: xCommand Fips Command: enter
ForceConfigUpdate
Forces the relevant configuration on this peer to be updated to match that of the cluster master.
Example: xCommand ForceConfigUpdate
468
HTTPProxyExtraTargetsAdd
Adds a server to the HTTPserver allow list.
Server(r):<S:1,1024>
The hostname or IP address of an HTTP server that a Jabber client located outside of the enterprise is allowed to access. Access
is granted if the server portion of the client-supplied URI matches the name entered here, or if it resolves via DNS lookup to an
IP address specified here.
Description:<S:0,1024>
A free-form description of the service.
Example: xCommand HTTPProxyExtraTargetsAdd Server: "allowme.example.com" Description: "A whitelisted

server"
HTTPProxyExtraTargetsDelete
Deletes a server from the HTTPserver allow list.
Server(r):<S:1,1024>
The hostname or IP address of the HTTP server that you want to remove from the allow list.
Example: xCommand HTTPProxyExtraTargetsDelete Server: "allowme.example.com"
HTTPProxyJabberCTargetsAdd
Configures a Jabber Guest Server and associates it with a Jabber Guest domain.
DomainIndex(r): <0..200>
Index of the domain with which this Jabber Guest Server is associated
Host(r): <S:1,1024>
The FQDN of a Jabber Guest Server to use for the selected domain. This must be an FQDN, not an unqualified hostname or an IP
address.
Note that you can specify alternative addresses for the same domain, each with different priorities.
Priority: <0..9>
The order in which connections to this hostname are attempted for this domain. All priority 1 hostnames for the domain are
attempted first, followed by all priority 2 hostnames, and so on.
Example: xCommand HTTPProxyJabberCTargetsAdd DomainIndex: 2 Host: jabberguest.example.com
HTTPProxyJabberCTargetsDelete
Deletes the configured Jabber Guest Server from the VCS.
Host(r): <S:1,1024> The FQDN of the Jabber Guest Server to delete.
Example:
469
LinkAdd
Adds and configures a new link.
LinkName(r): <S: 1, 50>
Assigns a name to this link.
Node1: <S: 1, 50>
Specifies the first zone or subzone to which this link will be applied.
Node2: <S: 1, 50>
Specifies the second zone or subzone to which this link will be applied.
Pipe1: <S: 1, 50>
Specifies the first pipe to be associated with this link.
Pipe2: <S: 1, 50>
Specifies the second pipe to be associated with this link.
Example: xCommand LinkAdd LinkName: "Subzone1 to UK" Node1: "Subzone1" Node2: "UK Sales Office" Pipe1:
"512Kb ASDL"
LinkDelete
Deletes a link.
LinkId(r): <1..3000>
The index of the link to be deleted.
Example: xCommand LinkDelete LinkId: 2
ListPresentities
Returns a list of all the presentities being watched by a particular subscriber.
Subscriber(r): <S:1, 255>
The URI of the subscriber who is watching.
Example: xCommand ListPresentities Subscriber: "[email protected]"
ListSubscribers
Returns a list of all subscribers who are watching for the presence information of a particular presentity.
Presentity(r): <S:1, 255>
The URI of the presentity being watched.
Example: xCommand ListSubscribers Presentity: "[email protected]"
470
Locate
Runs the VCS's location algorithm to locate the endpoint identified by the given alias, searching locally, on neighbors, and on
systems discovered through the DNS system, within the specified number of 'hops'. Results are reported back through the
xFeedback mechanism, which must therefore be activated before issuing this command (e.g. xFeedback register event/locate).
Alias(r): <S: 1, 60>
The alias associated with the endpoint you wish to locate.
HopCount(r): <0..255>
The hop count to be used in the search.
Protocol(r): <H323/SIP>
The protocol used to initiate the search.
SourceZone: <S: 1, 50>
The zone from which to simulate the search request. Choose from the Default Zone (an unknown remote system), the Local
Zone (a locally registered endpoint) or any other configured neighbor, traversal client or traversal server zone.
Authenticated: <Yes/No>
Whether the search request should be treated as authenticated or not.
SourceAlias: <S: 0, 60>
The source alias to be used for the search request. Default: xcom-locate
Example: xCommand Locate Alias: "[email protected]" HopCount: 15 Protocol: SIP SourceZone: LocalZone
Authenticated: Yes SourceAlias: [email protected]
Networkinterface
Controls whether the LAN 2 port is enabled for management and call signaling.
DualInterfaces(r): <enable/disable/status>
Sets or reports on the current status of the the LAN 2 port.
Example: xCommand Networkinterface DualInterfaces: enable
NTPServerAdd
Adds an NTP server to be used when synchronizing system time.
Address(r): <Value>
The IP address or Fully Qualified Domain Name (FQDN) of the NTP server to add.
Example: xCommand NTPServerAdd Address: "ntp.server.example.com"
NTPServerDelete
Address(r): <Value>
The IP address or Fully Qualified Domain Name (FQDN) of the NTP server to delete.
Example: xCommand NTPServerDelete Address: "ntp.server.example.com"
471
OptionKeyAdd
Adds a new option key to the VCS. These are added to the VCS in order to add extra functionality, such as increasing the VCS's
capacity. Contact your Cisco representative for further information.
Key(r): <S: 0, 90>
Specifies the option key of your software option.
Example: xCommand OptionKeyAdd Key: "1X4757T5-1-60BAD5CD"
OptionKeyDelete
Deletes a software option key from the VCS.
OptionKeyId(r): <1..64>
Specifies the ID of the software option to be deleted.
Example: xCommand OptionKeyDelete OptionKeyId: 2
Ping
Checks that a particular host system is contactable.
Hostname: <Value>
The IP address or hostname of the host system you want to try to contact.
Example: xCommand Ping Hostname: "example.com"
PipeAdd
Adds and configures a new pipe.
PipeName(r): <S: 1, 50>
Assigns a name to this pipe.
TotalMode: <Unlimited/Limited/NoBandwidth>
Controls total bandwidth restrictions for the pipe. NoBandwidth: no calls can be made using this pipe. Default: Unlimited.
Total: <1..100000000>
If this pipe has limited bandwidth, sets the maximum bandwidth (in kbps) available at any one time on the pipe. Default: 500000.
PerCallMode: <Unlimited/Limited/NoBandwidth>
Controls bandwidth restrictions of individual calls. NoBandwidth: no calls can be made using this pipe. Default: Unlimited.
PerCall: <1..100000000> For limited per-call mode, sets the maximum bandwidth (in kbps) available per call. Default: 1920.
Example: xCommand PipeAdd PipeName: "512k ADSL" TotalMode: Limited Total: 512 PerCallMode: Limited PerCall:
128
PipeDelete
Deletes a pipe.
PipeId(r): <1..1000>
The index of the pipe to be deleted.
Example: xCommand PipeDelete PipeId: 2
472
PolicyServiceAdd
Adds a policy service.
Name(r): <S: 0, 50>
Assigns a name to this Policy Service.
A free-form description of the Policy Service.
Protocol: <HTTP/HTTPS>
Specifies the protocol used to connect to the remote service. Default: HTTPS
Verify: <On/Off>
Controls X.509 certificate checking and mutual authentication between this VCS and the policy service. When enabled, the
server's FQDN or IP address, as specified in the address field, must be contained within the server's X.509 certificate (in either
the Subject Common Name or the Subject Alternative Name attributes). Default: On
CRLCheck: <On/Off>
certificate will be checked against the revocation list of the certificate authority of the certificate. Default: Off
Address: <S: 0, 128>
Path: <S: 0, 255>
StatusPath: <S: 0..255>
UserName: <S: 0, 30>
Password: <S: 0, 82>
The password used by the VCS to log in and query the remote service. The maximum plaintext length is 30 characters.
DefaultCPL: <S: 0, 255>
The CPL used when the remote service is unavailable. Default: <reject status='403' reason='Service Unavailable'/>
Example: xCommand PolicyServiceAdd Name: "Conference" Description: "Conference service" Protocol: HTTPS
Verify: On CRLCheck: On Address: "service.example.com" Path: "service" StatusPath: "status" UserName:
"user123" Password: "password123" DefaultCPL: "<reject status='403' reason='Service Unavailable'/>"
PolicyServiceDelete
Deletes a policy service.
PolicyServiceId(r): <1..20>
The index of the policy service to be deleted.
Example: xCommand PolicyServiceDelete PolicyServiceId: 1
473
RemoteSyslogAdd
Adds the address of a remote syslog server.
Address(r): <Value>
The IP address or FQDN of the remote syslog server.
Crlcheck: <On/Off>
Controls whether the certificate supplied by the syslog server is checked against the certificate revocation list (CRL). Default :
Off
Format: <bsd/ietf>
The format in which remote syslog messages are written. Default : bsd
Loglevel: <emergency/alert/critical/error/warning/notice/informational/debug>
The minimum severity of log messages to send to this syslog server. Default: informational.
Mode: <bsd/ietf/ietf_secure/user_defined>
The syslog protocol to use when sending messages to the syslog server. Default: bsd.
Port: <1..65535>
The UDP/TCP destination port to use. Suggested ports: UDP=514 TCP/TLS=6514 Default : 514
Transport: <udp/tcp/tls>
The transport protocol to use when communicating with the syslog server. Default: udp
Example: xCommand RemoteSyslogAdd Address: "remote_server.example.com" Crlcheck: Off Format: bsd Loglevel:
warning Mode: bsd Port: 514 Transport: udp
RemoteSyslogDelete
Address(r): <Value>
The IP address or Fully Qualified Domain Name (FQDN) of the remote syslog server to delete.
Port(r): <1..65535>
The port used by the remote syslog server to be deleted.
Transport(r): <udp/tcp/tls>
The transport protocol used by the remote syslog server to be deleted.
Example: xCommand RemoteSyslogDelete Address: "remote_server.example.com" Port: 514 Transport: udp
RemoveRegistration
Removes a registration from the VCS.
Registration: <1..3750>
The index of the registration to be removed.
RegistrationSerialNumber: <S: 1, 255>
The serial number of the registration to be removed.
Example: xCommand RemoveRegistration RegistrationSerialNumber: "a761c4bc-25c9-11b2-a37f-0010f30f521c"
474
Restart
Restarts the VCS without a full system reboot.
Example: xCommand Restart
RouteAdd
Adds and configures a new IP route (also known as a static route).
Address(r): <S: 1, 39>
Specifies an IP address used in conjunction with the prefix length to determine the network to which this route applies. Default:
32
PrefixLength(r): <1..128>
Specifies the number of bits of the IP address which must match when determining the network to which this route applies.
Gateway(r): <S: 1, 39>
Specifies the IP address of the gateway for this route.
Interface: <Auto/LAN1/LAN2>
The LAN interface to use for this route. Auto: the VCS will select the most appropriate interface to use. Default: Auto
Example: xCommand RouteAdd Address: "10.13.8.0" PrefixLength: 32 Gateway: "192.44.0.1"
RouteDelete
Deletes a route.
RouteId(r): <1..50>
The index of the route to be deleted.
Example: xCommand RouteDelete RouteId: 1
Securemode
Controls Advanced Account Security options.
Command(r): <on/off/status>
The index of the route to be deleted.
Example: xCommand Securemode Command: off
SearchRuleAdd
Adds a new search rule to route searches and calls toward a zone or policy service.
Name(r): <S: 0, 50>
Descriptive name for the search rule.
ZoneName: <S: 0, 50>
The zone or policy service to query if the alias matches the search rule.
A free-form description of the search rule.
Example: xCommand SearchRuleAdd Name: "DNS lookup" ZoneName: "Sales Office" Description: "Send query to the
DNS zone"
475
SearchRuleDelete
Deletes a search rule.
SearchRuleId(r): <1..2000>
The index of the search rule to be deleted.
Example: xCommand SearchRuleDelete SearchRuleId: 1
SIPRouteAdd
Adds a route that will cause SIP messages matching the given criteria to be forwarded to the specified IP address and port.
Method(r): <S:0, 64>
SIP method to match to select this route (e.g. INVITE, SUBSCRIBE).
RequestLinePattern(r): <S:0, 128>
Regular expression to match against the SIP request line.
HeaderName(r): <S:0, 64>
Name of SIP header field to match (e.g. Event).
HeaderPattern(r): <S:0, 128>
Regular expression to match against the specified SIP header field.
Authenticated(r): <On/Off>
Whether to forward authenticated requests. On: only forward requests along route if incoming message has been authenticated.
Off: always forward messages that match this route. Default: Off
Address(r): <S:0, 39>
Specifies the IP address of the next hop for this route, where matching SIP requests will be forwarded.
Port(r): <1..65534>
Specifies the port on the next hop for this route to which matching SIP requests will be routed. Default: 5060
Transport(r): <UDP/TCP/TLS>
Determines which transport type will be used for SIP messages forwarded along this route.
Tag(r): <S:0, 64>
Tag value specified by external applications to identify routes that they create.
Example: xCommand SIPRouteAdd Method: "SUBSCRIBE" RequestLinePattern: ".*@(%localdomains%|%ip%)"

HeaderName: "Event" HeaderPattern: "(my-event-package)(.*)" Authenticated: On Address: "127.0.0.1" Port:
22400 Transport: TCP Tag: "Tag1"
476
SIPRouteDelete
Deletes an existing SIP route, identified either by the specified index or tag.
SipRouteId: <1..20>
The index of the SIP route to be deleted.
Tag: <S:0, 64>
Tag value specified by external applications to uniquely identify routes that they create.
Example: xCommand SIPRouteDelete SipRouteId: Tag: "Tag1"
SubZoneAdd
Adds and configures a new subzone.
SubZoneName(r): <S: 1, 50>
Assigns a name to this subzone.
TotalMode: <Unlimited/Limited/NoBandwidth>
Determines whether this subzone has a limit on the total bandwidth of calls being used by its endpoints at any one time.
NoBandwidth: no bandwidth available. No calls can be made to, from, or within this subzone. Default: Unlimited.
Total: <1..100000000>
Sets the total bandwidth limit (in kbps) of this subzone (applies only if the mode is set to Limited). Default: 500000.
PerCallInterMode: <Unlimited/Limited/NoBandwidth>
Sets bandwidth limits for any one call to or from an endpoint in this subzone. NoBandwidth: no bandwidth available. No calls can
be made to or from this subzone. Default: Unlimited.
PerCallInter: <1..100000000>
Specifies the bandwidth limit (in kbps) on any one call to or from an endpoint in this subzone (applies only if the mode is set to
PerCallIntraMode: <Unlimited/Limited/NoBandwidth>
Sets bandwidth limits for any one call between two endpoints within this subzone. NoBandwidth: no bandwidth available. No
calls can be made within this subzone. Default: Unlimited.
PerCallIntra: <1..100000000>
Specifies the bandwidth limit (in kbps) for any one call between two endpoints within this subzone (applies only if the mode is
set to Limited). Default: 1920.
Example: xCommand SubZoneAdd SubZoneName: "BranchOffice" TotalMode: Limited Total: 1024 PerCallInterMode:
Limited PerCallInter: 512 PerCallIntraMode: Limited PerCallIntra: 512
SubZoneDelete
Deletes a subzone.
SubZoneId(r): <1..1000>
The index of the subzone to be deleted.
Example: xCommand SubZoneDelete SubZoneId: 2
477
SubZoneMembershipRuleAdd
Adds and configures a new membership rule.
Name(r): <S: 1, 50>
Assigns a name to this membership rule.
Type(r): <Subnet/AliasPatternMatch>
The type of address that applies to this rule. Subnet: assigns the device if its IP address falls within the configured IP address
subnet. Alias Pattern Match: assigns the device if its alias matches the configured pattern.
SubZoneName(r): <S: 1, 50>
The subzone to which an endpoint is assigned if its address satisfies this rule.
A free-form description of the membership rule.
Example: xCommand SubZoneMembershipRuleAdd Name: "Home Workers" Type: Subnet SubZoneName: "Home Workers"
Description: "Staff working at home"
SubZoneMembershipRuleDelete
Deletes a membership rule.
SubZoneMembershipRuleId(r): <1..3000>
The index of the membership rule to be deleted.
Example: xCommand SubZoneMembershipRuleDelete SubZoneMembershipRuleId: 1
Tracepath
Discover the path taken by a network packet sent to a particular destination host system.
Hostname: <Value>
The IP address or hostname of the host system to which you want to trace the path.
Example: xCommand Tracepath Hostname: "example.com"
Traceroute
Discover the route taken by a network packet sent to a particular destination host system. It reports the details of each router along
the path, and the time taken for each router to respond to the request.
Hostname: <Value>
The IP address or hostname of the host system to which you want to trace the route.
Example: xCommand Traceroute Hostname: "example.com"
478
TransformAdd
Adds and configures a new transform.
Pattern(r): <S: 1, 60>
Specifies the pattern against which the alias is compared.
Type: <Exact/Prefix/Suffix/Regex>
How the pattern string must match the alias for the transform to be applied. Exact: the entire string must exactly match the alias
character for character. Prefix: the string must appear at the beginning of the alias. Suffix: the string must appear at the end of
the alias. Regex: the string is treated as a regular expression. Default: Prefix
Behavior: <Strip/Replace/AddPrefix/AddSuffix>
How the alias is modified. Strip: removes the matching prefix or suffix from the alias. Replace: substitutes the matching part of
the alias with the text in the replace string. AddPrefix: prepends the replace string to the alias. AddSuffix: appends the replace
string to the alias. Default: Strip
Replace: <S: 0, 60>
Priority: <1..65534>
Assigns a priority to the specified transform. Transforms are compared with incoming aliases in order of priority, and the priority
must be unique for each transform. Default: 1
A free-form description of the transform.
State: <Enabled/Disabled>
Indicates if the transform is enabled or disabled. Disabled transforms are ignored. Default: Enabled
Example: xCommand TransformAdd Pattern: "example.net" Type: suffix Behavior: replace Replace: "example.com"
Priority: 3 Description: "Change example.net to example.com" State: Enabled
TransformDelete
Deletes a transform.
TransformId(r): <1..100>
The index of the transform to be deleted.
Example: xCommand TransformDelete TransformId: 2
479
UcxnConfigAdd
Configures a link to a Cisco Unity Connection server, for use with Mobile and Remote Access.
Address(r): <S:0,1024>
The FQDN or IP address of a Unity Connection publisher.
If CertValidationDisabled is Off, the Cisco Unity Connection system's FQDN or IP address must be contained within the X.509
certificate presented by that system (in either the Subject Common Name or the Subject Alternative Name attributes of the
certificate). The certificate itself must also be valid and signed by a trusted certificate authority.
DeploymentId: <1..65535>
This Unity Connection publisher is associated with the selected deployment and can only communicate with other members of
the selected deployment. It cannot communicate with members of other deployments.
Password(r): <S:1,1024>
The password used by the VCS Control to access the Cisco Unity Connection publisher.
Username(r): <S:1,1024>
The username used by the VCS to access the Unity Connection publisher.
UcxnConfigDelete
Removes a link to a Cisco Unity Connection server from the VCS.
Address(r): <S:0,1024>
The FQDN or IP address of a Unity Connection publisher.
WarningAcknowledge
Acknowledges an existing warning.
WarningID(r): <S:36, 36>
The warning ID
Example: xCommand WarningAcknowledge WarningID: "ab3d63f6-c0bb-4a9c-a121-e683abfedff0"
WarningLower
Lowers a warning.
The warning ID.
Example: xCommand WarningLower WarningID: "ab3d63f6-c0bb-4a9c-a121-e683abfedff0"
480
WarningRaise
Raises a warning.
The warning ID.
WarningText(r): <S:0, 255>
The description of the warning.
Example: xCommand WarningRaise WarningID: "ab3d63f6-c0bb-4a9c-a121-e683abfedff0" WarningText: "Module foo

is malfunctioning
Xmppdelete
Deletes the details of IM and Presence servers.
Address(r): <Value>
The IP address or Fully Qualified Domain Name (FQDN) of the IM and Presence server to delete.
Example: xCommand Xmppdelete Address: "imp_server.example.com"
Xmppdiscovery
Discovers the details of IM and Presence servers.
Address(r): <Value>
The IP address or Fully Qualified Domain Name (FQDN) of the IM and Presence server to discover.
Axlpassword(r): <Password>
The password used to access the IM and Presence publisher.
Axlusername(r): <String>
The username used to access the IM and Presence publisher.
Controls X.509 certificate checking against the certificate presented by the IM and Presence publisher. Default: On
Example: xCommand Xmppdiscovery Address: "imp.example.com" Axlpassword: "xyz" Axlusername: "abc"
ZoneAdd
Adds and configures a new zone.
ZoneName(r): <S: 1, 50>
Assigns a name to this zone.
Type(r): <Neighbor/TraversalClient/TraversalServer/ENUM/DNS>
Determines the nature of the specified zone, in relation to the local VCS. Neighbor: the new zone will be a neighbor of the local
VCS. TraversalClient: there is a firewall between the zones, and the local VCS is a traversal client of the new zone.
TraversalServer: there is a firewall between the zones and the local VCS is a traversal server for the new zone. ENUM: the new
zone contains endpoints discoverable by ENUM lookup. DNS: the new zone contains endpoints discoverable by DNS lookup.
Example: xCommand ZoneAdd ZoneName: "UK Sales Office" Type: Neighbor
481
ZoneDelete
Deletes a zone.
ZoneId(r): <1..1000>
The index of the zone to be deleted.
Example: xCommand ZoneDelete ZoneId: 2
ZoneList
A diagnostic tool that returns the list of zones (grouped by priority) that would be queried, and any transforms that would be applied,
in a search for a given alias.
Note that this command does not change any existing system configuration.
Alias(r): <S: 1, 60>
The alias to be searched for.
Example: xCommand ZoneList Alias: "[email protected]"
482
Command Reference xStatus

The xStatus group of commands are used to return information about the current status of the system. Each xStatus
element returns information about one or more sub-elements.
The following section lists all the currently available xStatus commands, and the information that is returned by each
command.
To obtain information about the existing status, type:
xStatus to return the current status of all status elements

xStatus <element> to return the current status for that particular element and all its sub-elements
xStatus <element> <sub-element> to return the current status of that group of sub-elements
To obtain information about the xStatus commands, type:
xStatus ? to return a list of all elements available under the xStatus command
xStatus elements
The current xStatus elements are:
Alarm
Alternates
Applications
Authentication
B2BUACalls
B2buapresencerelayservice
B2buapresencerelayuser
CDR
Cafe
Calls
Cloud
Cluster
CollaborationEdge
EdgeConfigProvisioning
Edgeconfigprovisioning
Edgedomain
Edgeexternalfqdn
Edgesso
ExternalManager
Fail2banjailbannedaddress
Feedback
FindMeManager
Fips
Firewall
Gwtunnels
H323
HTTPProxy
483
Hardware
Iptablesacceptedrule
Iptablesrule
License
Links
Mediastatistics
NetworkInterface
Ntpcertificates
Options
PhonebookServer
Pipes
Policy
PortUsage
ProvisioningServer
Provisioningdevice
Provisioningdevicestatussynch
Provisioningservice
Registrations
ResourceUsage
SIP
SipServiceDomains
SipServiceZones
SystemMetrics
SystemUnit
TURN
Teststatus
Time
Traversalserverresourceusage
Tunnels
Warnings
XMPP
Xcps2s
Zones
External Policy Overview

The Cisco TelePresence Video Communication Server (VCS) has built in support for Registration Policy, Call Policy
and User Policy (FindMe) configuration. It also supports CPL (Call Processing Language) for implementing more
complex policy decisions. CPL is designed as a machine-generated language and is not immediately intuitive; while
the VCS can be loaded with CPL to implement advanced call policy decisions, complex CPL is difficult to write and
maintain.
The VCSs external policy feature allows policy decisions to be taken by an external system which can then instruct
the VCS on the course of action to take (such as whether to accept a registration, fork a call and so on). Call policy
can now be managed independently of the VCS, and can implement features that are unavailable on the VCS. The
484
external policy server can make routing decisions based on data available from any source that the policy server has
access to, allowing companies to make routing decisions based on their specific requirements.
When the VCS is configured to use an external policy server the VCS sends the external policy server a service
request (over HTTP or HTTPS), the service will send a response back containing a CPL snippet which the VCS will
then execute.
Using an External Policy Server

The main areas where the VCS can be configured to use an external policy server are:
Registration Policy to allow or reject registrations.

Call Policy (also known as Admin Policy) to control the allowing, rejecting, routing (with fallback if calls fail)
and forking of calls.
Search rules (policy can be applied for specific dial plan search rules).
Each of these areas can be configured independently of each other as to whether or not to use a policy service. If a
policy service is used, the decisions made by the policy service replace (rather than supplement) those made by the
VCS.
When configuring policy services:
Up to 3 external policy servers may be specified to provide resiliency (and not load balancing).
Default CPL can be configured, to be processed by the VCS as a fallback, if the service is not available.
The status and reachability of the service can be queried via a status path.
If you require FindMe functionality beyond that provided by VCS / Cisco TMS, we recommend that you implement it
through Call Policy.
More information about policy services, including example CPL, can be found in the External Policy on VCS
Deployment Guide.
External Policy Request Parameters

When the VCS uses a policy service it sends information about the call or registration request to the service in a POST
message using a set of name-value pair parameters. The service can then make decisions based upon these
parameters combined with its own policy decision logic and supporting data (for example lists of aliases that are
allowed to register or make and receive calls, via external data lookups such as an LDAP database or other
information sources).
The service response must be a 200 OK message with CPL contained in the body.
The following table lists the possible parameters contained within a request and indicates with a in which request
types that parameter is included. It also indicates, where relevant, the range of accepted values.
485
Parameter name Values Registration Search Call User

Policy rules Policy Policy
ALIAS
ALLOW_INTERWORKING TRUE / FALSE
AUTHENTICATED TRUE / FALSE
AUTHENTICATED_SOURCE_ALIAS
AUTHENTICATION_USER_NAME
CLUSTER_NAME
DESTINATION_ALIAS
DESTINATION_ALIAS_PARAMS
GLOBAL_CALL-SERIAL_NUMBER GUID
LOCAL_CALL_SERIAL_NUMBER GUID
METHOD INVITE / ARQ / LRQ /

OPTIONS / SETUP /
REGISTER / SUBSCRIBE /
PUBLISH
NETWORK_TYPE IPV4 / IPV6
POLICY_TYPE REGISTRATION /
SEARCH / ADMIN / USER
PROTOCOL SIP / H323
REGISTERED_ALIAS
SOURCE_ADDRESS
SOURCE_IP
SOURCE_PORT
TRAVERSAL_TYPE TYPE_[UNDEF /
ASSENTSERVER /
ASSENTCLIENT /
H460SERVER /
H460CLIENT /
TURNSERVER /
TURNCLIENT / ICE]
UNAUTHENTICATED_SOURCE_ALIAS
UTCTIME
ZONE_NAME
Cryptography support
External policy servers should support TLS and AES-256/AES-128/3DES-168.
SHA-1 is required for MAC and Diffie-Hellman / Elliptic Curve Diffie-Hellman key exchange; the VCS does not support
MD5.
486
Default CPL for Policy Services

When configuring a policy service, you can specify the Default CPL that is used by the VCS if the service is not
available.
The Default CPL for registrations and Call Policy defaults to:
<reject status='403' reason='Service Unavailable'/>
and this will reject the request.

The Default CPL for policy services used by search rules defaults to:
<reject status='504' reason='Policy Service Unavailable'/>
and this will stop the search via that particular search rule.
This default CPL mean that in the event of a loss of connectivity to the policy server, all call and registration requests
will be rejected. If this is not your required behavior then you are recommended to specify alternative default CPL.
We recommend that you use unique reason values for each type of service, so that if calls or registrations are
rejected it is clear why and which service is rejecting the request.
487
Flash Status Word Reference Table

The flash status word is used in diagnosing NTP server synchronization issues.
It is displayed by the ntpq program rv command. It comprises a number of bits, coded in hexadecimal as follows:
Code Tag Message Description
0001 TEST1 pkt_dup duplicate packet
0002 TEST2 pkt_bogus bogus packet
0004 TEST3 pkt_unsync server not synchronized
0008 TEST4 pkt_denied access denied
0010 TEST5 pkt_auth authentication failure
0020 TEST6 pkt_stratum invalid leap or stratum
0040 TEST7 pkt_header header distance exceeded
0080 TEST8 pkt_autokey Autokey sequence error
0100 TEST9 pkt_crypto Autokey protocol error
0200 TEST10 peer_stratum invalid header or stratum
0400 TEST11 peer_dist distance threshold exceeded
0800 TEST12 peer_loop synchronization loop
1000 TEST13 peer_unreach unreachable or nonselect
Supported RFCs
VCS supports the following RFCs:
Table 21 Supported RFCs
RFC Description
791 Internet Protocol
1213 Management Information Base for Network Management of TCP/IP-based internets
1305 Network Time Protocol (Version 3) Specification, Implementation and Analysis
2327 SDP: Session Description Protocol
2460 Internet Protocol, Version 6 (IPv6) Specification (partial, static global addresses only)
2464 Transmission of IPv6 Packets over Ethernet Networks
2560 X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP
2782 A DNS RR for specifying the location of services (DNS SRV)
2833 RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
2915 The Naming Authority Pointer (NAPTR) DNS Resource Record
2976 SIP INFO method
488
Table 21 Supported RFCs (continued)
RFC Description
3164 The BSD syslog Protocol
3261 Session Initiation Protocol
3263 Locating SIP Servers
3264 An Offer/Answer Model with the Session Description Protocol (SDP)
3325 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
3326 The Reason Header Field for the Session initiation Protocol (SIP)
3265 Session Initiation Protocol (SIP) Specific Event Notification
3327 Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts
3489 STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
3515 The Session Initiation Protocol (SIP) Refer Method
3550 RTP: A Transport Protocol for Real-Time Applications
3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
3596 DNS Extensions to Support IP Version 6
3761 The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application
(ENUM)
3856 A Presence Event Package for the Session Initiation Protocol (SIP)
3863 Presence Information Data Format (PIDF)
3880 Call Processing Language (CPL): A Language for User Control of Internet Telephony Services
3891 Replaces header
3892 Referred-by header
3903 Session Initiation Protocol (SIP) Extension for Event State Publication
3944 H.350 Directory Services
3986 Uniform Resource Identifier (URI): Generic Syntax
4028 Session Timers in the Session Initiation Protocol
4213 Basic Transition Mechanisms for IPv6 Hosts and Routers
4291 IP Version 6 Addressing Architecture
4443 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
4479 A Data Model for Presence
4480 RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF)
4787 Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
4861 Neighbor Discovery for IP version 6 (IPv6)
5095 Deprecation of Type 0 Routing Headers in IPv6
489
Table 21 Supported RFCs (continued)
RFC Description
5104 Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF): Temporary Maximum
Media Stream Bit Rate Request (TMMBR)
5245 Interactive Connectivity Establishment (ICE)
5389 Session Traversal Utilities for NAT (STUN)
5424 The Syslog Protocol
5626 Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
5627 Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP).
Note that this RFC is only partially supported: Public GRUU is supported; Temporary GRUU is not supported.
5766 Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
5806 Diversion Indication in SIP
6156 Traversal Using Relays around NAT (TURN) Extension for IPv6
490
Software Version History

This section summarizes feature updates that have occurred in earlier software releases.
For information about earlier releases not listed here, see the online help or previous versions of this document.
X8.6.1
X8.6
X8.5.3
X8.5.2
X8.5.1
X8.5
X8.2
X8.1.1
X8.1
X7.2.1
X7.2
X7.1
X7
X8.6.1
X8.6.1 is a maintenance release. No new features are introduced.
X8.6
Table 22 Feature history by release number
Feature / change X8.6.1 X8.6
Lync Desktop Sharing Supported Supported
Hybrid Services Supported Withdrawn
License bypass for calls to cloud-based Supported Supported

Collaboration Meeting Rooms (CMRs)
New codec support: OPUSand H.265 Supported Supported
System Metrics Collection Supported Supported
Cisco DXSeries endpoints over MRA Supported with endpoint Supported with endpoint
version 10.2.4(99) or later version 10.2.4(99) or later
Cisco IPPhone 7800/8800 Series over MRA Preview with endpoint version Preview with endpoint version
10.3.1 or later 10.3.1 or later
Multiple Presence Domains via MRA Preview Preview
Japanese, Korean, Russian localizations X8.5.1 UI X8.5.1 UI
Changes and minor enhancements Supported Supported
Support for desktop sharing from Lync

The VCS now supports desktop or application sharing from Lync clients with conference participants using Cisco
Collaboration endpoints.
491
The VCS does the transcoding of the Microsoft Remote Desktop Protocol (RDP), originating from the Lync client, into
the Binary Floor Control Protocol (BFCP) used by many standards-based endpoints. The VCS does not perform the
reverse transcoding from BFCPto RDP, and presentation towards Lync will go in the video channel as in previous
releases.
The following deployments support screen sharing from Lync:
Figure 13 Lync environment to conference registered to VCS
Figure 14 Lync environment to conference managed by TelePresence Conductor neighbored to VCS
Figure 15 Lync environment to SIPor H.323 endpoint registered to VCS
Notes:
1. If you are using the Optimize Resources feature with Lync screen sharing, you need TelePresence Conductor
version XC4.0 or later.
2. If you are using the Optimize Resources feature with Lync screen sharing, you need TelePresence Server
version 4.2 or later.
3. Requires Interworking option key.
To configure your Cisco Collaboration environment to interoperate with Microsoft Lync, see the Microsoft Lync and
Cisco VCS Deployment Guide on the VCS Configuration Guides page.
Hybrid Services
What are Hybrid Services and what do they do?
Cisco Hybrid Services empower cloud-based and premises-based solutions to deliver a more capable, better
integrated collaboration user experience.
Which services am Ientitled to use?
When you purchase Hybrid Services you get access to Cloud Collaboration Management an administrative
interface to the Cisco Collaboration Cloud. In Cloud Collaboration Management you can check your organization's
service entitlements and enable features for your users.
What software do Ineed?
The on-premises components of Hybrid Services are called "connectors", and the VCS software contains a
management connector to manage registration and other connectors.
The management connector is dormant until you register. When you register, the management connector is
automatically upgraded if a newer version is available.
The VCS then downloads any other connectors that you selected using Cloud Collaboration Management. They are
not started by default and you need to do some configuration before they'll work.
492
How do Iinstall, upgrade, or downgrade?
The connectors are not active by default, and will not do anything until you configure and start them. You can do this
on new UI pages that the connectors install on the VCS.
Connector upgrades are made available through Cloud Collaboration Management, and the management connector
will download the new versions to VCS when you have authorized the upgrade.
You can also deregister, which disconnects your VCS from Collaboration Cloud and removes all connectors and
related configuration.
Note:We do not normally advise downgrading VCS, although we try to ensure that the interface remains accessible if
you are forced to restore a previous version. However, we explicitly do not support a downgrade of the VCS software
from X8.6 versions while the VCS is registered for Hybrid Services. If you have to downgrade, you must deregister
from Hybrid Services before you downgrade.
Where can Iread more about Hybrid Services?
Hybrid Services are continuously developed and may be published more frequently than VCS. This means that
information about Hybrid Services is maintained on the Hybrid Services help site, and several VCS interface pages link
out to that site.
License bypass for calls to Collaboration Meeting Rooms (CMRs)

The VCS no longer requires traversal call licenses for calls to and from cloud-based CMRs. This includes SIP calls
between Collaboration Cloud and the CMR Hybrid solution.
Note: This only applies when the dialed string does not need transformation on the VCS (for example,
[email protected]).
Although untransformed SIP calls to cloud-based CMRs do not consume licenses, they do consume resources and
may not progress if the VCS is at full capacity.
There is no license bypass for CMR Premises calls. H.323 calls to cloud-based CMRs still consume licenses.
New codec support
The VCS now supports the H.265 video and OPUSaudio codecs. The codecs are supported in SIPtraversal calls (that
is, calls where the VCS is handling the media streams).
These codecs are not supported on SIP- H.323 interworked or H.323 - H.323 calls.
System Metrics Collection
What is System Metrics Collection, and how does it work on VCS?
System Metrics Collection is a feature on VCS that publishes system performance statistics, enabling remote
monitoring of performance.
The VCS collects statistics about the performance of the hardware, OS, and the application, and publishes these
statistics to a remote host (typically a data analytics server) that aggregates the data.
Where do Iconfigure System Metrics Collection?
You can configure this feature on VCS via the web interface or the command line. The configuration from one peer
applies throughout the cluster, so we recommend that you configure it on the master peer if you are monitoring a
cluster.
There is also some configuration required on the remote server; the collectd daemon should be running on the server,
and should have the collectd network plugin configured to listen on an address that can be seen by the clients.
Further details depend on your monitoring environment and are beyond the scope of this information.
493
How can Iuse this data?
You can use the data to generate graphs, aggregate statistics, and analyze performance, using tools such as
Circonus and Graphite.
Where can I read more about System Metrics Collection?
For more details see the Cisco VCS Serviceability Guide on the Cisco VCS Maintain and Operate Guides page.
MRAsupport for new endpoints

Mobile and Remote Access is being expanded to include the following new endpoints.
The DXSeries endpoints are officially supported via MRAif they are running version 10.2.4(99) or later. The Cisco
IPPhone 78/8800 Series endpoints are not yet officially supported via MRA, but they must be running version 10.3.1
or later if you want to preview them with Mobile and Remote Access.
Cisco DX650
Cisco DX80
Cisco DX70
(Preview) Multiple Presence Domains / Multiple IM Address Domains via MRA
Jabber 10.6 can be deployed into an infrastructure where users are organized into more than one domain, or into
domains with subdomains. This requires IMand Presence Service 10.0.x (or later).
Limited testing has shown that this feature works via MRA. Hence this feature is in preview with VCS X8.5.1 and
later, pending further testing and full support in a future version of VCS.
Note: This feature is distinct from the multiple deployments feature released in X8.5. That feature is limited to one
domain per deployment, where all IMand Presence Service clusters within a deployment serve a single domain. This
feature is different because it concerns MRAsupport for all IMand Presence Service clusters within a deployment
serving a common set of one or more Presence domains.
Each new domain impacts the VCSs performance. We currently recommend that you do not exceed 50 domains.
Updated language packs
Language packs are now available for the following languages. The packs include localized web interface and
embedded webhelp.
Japanese
Russian
Korean
494
Note:These localizations apply to the X8.5.1 versions of the UIand embedded help. They complete the set
announced in the X8.5.3 release notes (Chinese, French, German, and Spanish).
Changes and minor enhancements
There is a new option to modify the SIPTCPconnect timeout (Configuration >Protocols >SIP>Advanced).
The default is 10 seconds.
Mutual TLSauthentication can now be configured for SIPcalls (Configuration >Protocols >SIP). Two new
parameters were added Mutual TLSmode (default Off) and Mutual TLS port (default 5062).
Anew zone parameter called SIP parameter preservation controls whether the SIPURIand Contact
parameters are preserved between the zone and the B2BUA.
Anew zone parameter called Preloaded SIP routes support controls whether the zone processes SIP INVITE
requests that contain the Route header.
There is a new command line option to change the cipher suites used for SIPTLS connections. The command
takes a colon-delimited string of cipher suites (see
https://www.openssl.org/docs/apps/ciphers.html#CIPHER-LIST-FORMAT). For example, to set the current
VCS default suite, use:
xConfiguration SIP TLS CipherSuite: ALL:!EXP:!LOW:!MD5:@STRENGTH:+ADH
The diagnostic log now includes two new .xml files, to record the xconfig and xstatus of the VCS at the time
the log was taken.
The Call Detail Records (CDR) switch has moved from the System >Administration page to the Maintenance
>Logging page.
The CLIcommands xCommand LoginUserAdd and xCommand LoginUserDelete have been replaced by xCommand
CredentialAdd and xCommand CredentialDelete.
The hop count logic has changed so that internal hops between the VCS application and its B2BUA do not
decrement the hop count.
Several advanced zone parameters have been removed because they are no longer required. These are SIP
SDP attribute line limit mode, SIP SDP attribute line limit length, and SIP Duo Video filter mode.
The Maximum authorizations per period default has increased to 8.
X8.5.3
X8.5.3 is a maintenance release. No new features are introduced. X8.5.3 supersedes X8.5.2.
Table 23 Feature history by release number
Feature / change X8.5.3 X8.5.2 (withdrawn) X8.5.1 X8.5
KPML Supported Supported Not supported Not supported
Multiple Presence Preview Preview Preview Not supported

Domains via MRA
SSOover MRA Supported Supported Supported; Preview

SAMLsigning
algorithm changed
CSRUIdigest algorithm Supported Supported Supported Not supported

options
Cisco DXSeries Supported with Supported with Preview (no KPML) Preview (no KPML)
endpoints over MRA 10.2.4(99) and later 10.2.4(99) and later
Cisco IPPhone Preview (with Preview (with Preview (no KPML) Preview (no KPML)
7800/8800 Series over KPML) KPML)
MRA
495
Table 23 Feature history by release number (continued)
Feature / change X8.5.3 X8.5.2 (withdrawn) X8.5.1 X8.5
Early media Supported Supported Supported Supported
Unsolicited Supported Supported Supported Supported

NOTIFYpass-through
Multiple deployments Supported Supported Supported Supported
Secure connection Supported Supported Supported Supported

checker
Syslog publish filter Supported Supported Supported Supported
Call Detail Records Supported Supported Supported Supported

(CDRs)
Media statistics Supported Supported Supported Supported
Password change Supported Supported Supported Supported

requires authorization
Static routes Supported Supported Supported Supported
X8.5.2
Note:This release has been withdrawn and is no longer available for download.
MRAsupport for new endpoints
Mobile and Remote Access is being expanded to include the following new endpoints.
The DXSeries endpoints are officially supported via MRAif they are running version 10.2.4(99) or later. The Cisco
IPPhone 78/8800 Series endpoints are not yet officially supported via MRA, but they must be running version 10.3.1
or later if you want to preview them with Mobile and Remote Access.
Cisco DX650
Cisco DX80
Cisco DX70
KPMLpass-through
With Key Press Markup Language support, phone users outside the network can use endpoint-signaled Unified CM
features like off-hook dial, group call pickup, abbreviated dial and others.
496
Updated language packs

The web interface and embedded webhelp are localized into the following languages.
Chinese
French
German
Spanish
Japanese
Korean
Russian
Note:These localizations apply to the X8.5.1 versions of UI and help.

Important behavior changes
MRAauthorizations are now rate controlled by default, to reduce the load of unnecessary authorizations on the VCS.
Take care when you upgrade because your current endpoint software may be reauthorizing more often than
necessary, which could result in the VCS issuing HTTP429 "Too Many Requests". If you routinely see this error after
upgrade, you can edit the rate control settings at Configuration >Unified Communications >Configuration
>Advanced.
Software enhancements
This release introduces rate control for successful authorisations, via MRA,of users accessing collaboration
services; this feature applies to SSO-authenticated users as well as non-SSO-authenticated users.
The Single Sign-On feature introduced in X8.5.1 has been further improved in this release. The status
information concerning user tokens has been improved. You can also purge tokens issued to a user, or to all
users, if necessary. The UIfor the SAMLexport feature has been improved.
The cluster database (CDB) resiliency has been improved.
X8.5.1
SSOover MRA
The VCS Control now defaults to SHA-256 for signing SSOrequests it gives to clients, and you can change it to use
SHA-1 if required. In version X8.5, when the SSOfeature was previewed, the VCS Control defaulted to SHA-1 and
there was no way to select a different algorithm.
Note:If you were using the SSOfeature with X8.5, this change may cause it to stop working after upgrade to X8.5.1.
You have two options to resolve this: leave the new default on the VCS Control, and you may need to reconfigure the
IdPto expect requests to be signed with SHA-256 (recommended for better security); the other option is to revert the
VCS Control's signing algorithm to SHA-1 for your IdP (go to Configuration >Unified Communications >Identity
Providers (IdP), locate your IdProw, then in Actions column click Configure Digest).
Jabber 10.6 File Transfer support
The Cisco Jabber file transfer over MRAlimitation, which was previously documented in VCS documents, has now
changed as follows:
Peer-to-peer file transfer when using IMand Presence Service and Jabber is unsupported via MRA.
Managed File Transfer (MFT) with IMand Presence Service 10.5.2 (and later) and Jabber 10.6 (and later)
clients is supported via MRA.
File transfer with WebEx Messenger Service and Cisco Jabber is supported via MRA.
Jabber 10.6 can be deployed into an infrastructure where users are organized into more than one domain, or into
domains with subdomains. This requires IMand Presence Service 10.0.x (or later).
497
Limited testing has shown that this feature works via MRA. Hence this feature is in preview with VCS X8.5.1 and
later, pending further testing and full support in a future version of VCS.
Note: This feature is distinct from the multiple deployments feature released in X8.5. That feature is limited to one
domain per deployment, where all IMand Presence Service clusters within a deployment serve a single domain. This
feature is different because it concerns MRAsupport for all IMand Presence Service clusters within a deployment
serving a common set of one or more Presence domains.
Each new domain impacts the VCSs performance. We currently recommend that you do not exceed 50 domains.
X8.5
Feature previews
The following features are implemented in this version for the purpose of previewing with dependent systems. They
are not currently supported and should not be relied upon in your production environment. Full support for these
features is planned for a future release of the VCS software.
(Preview) Single sign-on over MRA
Enables single sign-on (common identity) for SSO-capable clients that are accessing on-premises Unified
Communications services from outside the network.
(Preview) MRAsupport for new endpoints
Mobile and Remote Access is extended in this release to include support for the Cisco DXSeries endpoints, and the
8800 Series and 7800 Series IPphones, registering to Cisco Unified Communications Manager. Some features on the
IPphones, particularly where they rely on DTMF/KPML pass-through, were not available in X8.5. This limitation was
resolved in X8.5.2.
Single sign-on over MRA

Use this feature to enable single sign-on for endpoints accessing Unified Communications services from outside the
network. Single sign-on over the edge relies on the secure traversal capabilities of the VCS pair at the edge, and trust
relationships between the internal service providers and the externally resolvable identity provider (IdP).
The endpoints do not need to connect via VPN; they use one identity and one authentication mechanism to access
multiple Unified Communications services. Authentication is owned by the IdP, and there is no authentication at the
VCS, nor at the internal Unified CM services.
Supported endpoints

Supported Unified Communications services

Cisco Unity Connection 10.5(2) or later
Cisco Unified Communications Manager IMand Presence Service 10.5(2) or later
Other internal web servers, for example intranet
How it works
Cisco Jabber determines whether it is inside the organization's network before it requests a Unified Communications
service. If it is outside the network, then it requests the service from the VCS Expressway on the edge of the network.
If single sign-on is enabled at the edge, the VCS Expressway redirects Jabber to the IdP with a signed request to
authenticate the user.
The IdP challenges the client to identify itself. When this identity is authenticated, the IdPredirects Jabber's service
request back to the VCS Expressway with a signed assertion that the identity is authentic.
498
The VCS Expressway trusts the IdP, so it passes the request to the appropriate service inside the network. The Unified
Communications service trusts the IdPand the VCS Expressway, so it provides the service to the Jabber client.
Figure 16 Single sign-on for on-premises UCservices
Improved line-side capabilities

The line-side SIPcapabilities of the VCS have been extended to improve the support that MRAoffers for endpoints
registering to Unified CM. The improvements are:
Early Media support over MRA
Support for this feature means that endpoint users can hear media from the far end before the call is fully established,
to indicate call progress (eg. busy tone) or play interactive voice responder messages.
The MRAdeployment now supports passing through the 183 provisional response to enable early media, but the
feature is dependent on endpoint support. Early media is supported in recent software for TCseries endpoints but is
not supported in Jabber 10.6.
Unsolicited NOTIFY pass-through
The unsolicited NOTIFY between Unified CM and the endpoints provides support for features like Message Waiting
Indicator (MWI).
Multiple deployments for partitioning mobile and remote access to Unified Communications
services
This release introduces the concept of "deployments" to the VCS.
Adeployment is an abstract boundary used to enclose a domain and one or more Unified Communications service
providers, such as Unified CM, Cisco Unity Connection, and IMand Presence Service nodes.
The purpose of multiple deployments is to partition the Unified Communications services available to mobile and
remote access (MRA) users. This enables different subsets of MRAusers to access different sets of services over the
same VCS pair. We recommend that you do not exceed 10 deployments.
499
For example, consider an implementation of two sets of Unified Communications infrastructure to provide a live
MRAenvironment and a staging environment, respectively. This implementation might also require an isolated
environment for sensitive communications.
Figure 17 Multiple deployments to partition Unified Communications services accessed from outside the
network
Serviceability improvements
Secure connection checker
This new utility enables you to test whether or not a secure connection can be made from the VCS. It checks the
validity of certificates presented by the transacting parties, looking for errors that would prevent the secure
connection.
You simply enter an FQDN, hostname, or IPaddress to test the secure connection without otherwise affecting your
configuration.
The feature can be used in the following circumstances:
you are discovering Unified Communications servers / nodes while configuring Mobile and Remote Access,
and wish to test whether TLSor HTTPSwill be possible with the configured nodes
you are configuring a Unified Communications traversal zone, or Secure Traversal zone, between the VCS
Control and the VCS Expressway
You can now filter the logs that VCS sends to each remote syslog host by severity level.
For example, your syslog host is typically receiving syslog messages from multiple systems, so you may want to limit
VCS to sending only "Error" messages (and anything more severe) to this host. If you want to leave the host
untouched while troubleshooting a VCS problem, you could configure a second, temporary, host to receive "Debug"
level (most verbose = messages of all severities). Then you could safely remove the configuration after resolving the
issue, without risking your primary syslog host.
Call detail records (CDRs)
The VCS now has the ability to record call connections and disconnections. There is a new service that allows short-
lived CDRs to be read from the VCS by an external system.
500
There is also an option to log the CDRs more permanently, in which case the CDRs are published as Informational
messages to your syslog host. This option also keeps CDRs for a few days on the event log, but the local data could
rotate quickly.
Note:CDR reporting is best effort and should not be relied upon for accurate billing purposes.
Media statistics
Amedia statistics logging service has been added to this release. When the service is active, up to 2GB of data is
kept locally in a rotating log. The stats are also published as syslog messages for offline storage and analysis. For
each call, the VCS tracks statistics like packet counts, bitrates, and jitter.
Other changes
Enhancements and usability improvements
You can add static IProutes via the web UI, where previously these could only be added by CLI. There is a
new page System >Network interfaces >Static routes to provide this functionality.
The Certificate Signing Request (CSR) generator now enables you to select the digest algorithm requested for
your certificate. The options are SHA-1, SHA-256 (new default), SHA-384, and SHA-512. In VCS versions
prior to X8.5.1, the CSRpage had no way to select the algorithm, and the CSR used SHA-1 by default.
Changed functionality
When changing an administrator account password, the logged in administrator is now required to authorize
the change by entering their own password.
The IPand Ethernet configuration pages have a new menu location. Previously these were System >IPand
System >Ethernet. These pages are now System >Network interfaces >IP and System >Network
interfaces >Ethernet.
The VCS Control now defaults to SHA-256 for signing SSOrequests it gives to clients, and you can change it
to use SHA-1 if required. In version X8.5, when the SSOfeature was previewed, the VCS Control defaulted to
SHA-1 and there was no way to select a different algorithm.
Note:If you were using the SSOfeature with X8.5, this change may cause it to stop working after upgrade to
X8.5.1. You have two options to resolve this: leave the new default on the VCS Control, and you may need to
reconfigure the IdPto expect requests to be signed with SHA-256 (recommended for better security); the
other option is to revert the VCS Control's signing algorithm to SHA-1 for your IdP (go to Configuration
>Unified Communications >Identity Providers (IdP), locate your IdProw, then in Actions column click
Configure Digest).
X8.2
Unified Communications: Jabber Guest
Cisco Jabber Guest is a consumer to business (C2B) solution that extends the reach of Cisco's enterprise telephony
to people outside of a corporate firewall who do not have phones registered with Cisco Unified Communications
Manager.
External XMPP federation
External XMPP federation enables users registered to Unified CM IM & Presence to communicate via the VCS
Expressway with users from a different XMPP deployment.
TURN media over TCP
The VCS Expressway TURN server supports TURNmedia over TCP.
This allows clients to use TURN services in environments where UDP connections are not supported or blocked.
Configuration of the supported protocols is available only through the CLI command xConfiguration Traversal Server
TURN ProtocolMode.
501
New 'Unified Communications traversal' zone type

To simplify the configuration of secure traversal client and traversal server zones for Unified Communications, you
must now use the new zone type of Unified Communications traversal when configuring zones via the web interface.
This automatically configures an appropriate traversal zone (a traversal client zone when selected on a VCS Control,
or a traversal server zone when selected on a VCS Expressway) that uses SIP TLS with TLS verify mode set to On,
and Media encryption mode set to Force encrypted.
This replaces the previous Unified Communications services setting that was available when configuring traversal
client and traversal server zones. Existing zones configured in previous software versions for Unified
Communications services are automatically converted to use the new Unified Communications traversal zone type.
Note that this zone type applies to the web interface only, the underlying CLI configuration settings have not
changed.
Support for X-cisco-srtp-fallback
Support has been added for the X-cisco-srtp-fallback package, allowing the VCS's B2BUA to use Cisco Unified
Communications Manager-style best effort media encryption for the automatically generated TLSneighbor zones.
RTP and RTCP media demultiplexing ports
In Small/Medium systems, 1 pair of RTP and RTCP media demultiplexing ports are used. These can now either be
explicitly specified (Configuration > Traversal > Ports) or they can be allocated from the start of the general range of
traversal media ports. In previous X8 releases they were always allocated from the start of the traversal media ports
range.
In Large systems, 6 pairs of RTP and RTCP media demultiplexing ports are used. These are still always allocated from
the start of the traversal media ports range.
After upgrading to X8.2, all existing traversal media port configurations / firewall requirements are maintained.
Diagnostic logging
The diagnostic logging feature has been extended to include:
an xconfig file
an xstatus file
enabling the tcpdump (if requested) cluster-wide
consolidating all of the files into a single downloadable diagnostic log archive (per peer)
an indication on the web administration page of which user / IP address initiated the logging
The xconfig and xstatus files are taken at the start of the logging process.
SIPREFERsupport
The VCS B2BUA has SIP REFER message support. A SIP REFER mode advanced zone configuration parameter has
been introduced.
By default it will forward REFER messages, but it can be configured to terminate REFER messages and use the B2BUA
to perform the transfer (typically to a bridge) on behalf of the far endpoint.
Other enhancements and usability improvements
The HTTP server allow list page (used for mobile and remote access clients to access additional web
services inside the enterprise) now displays any automatically configured entries.
You can configure the timeout period for TLS socket handshake (Configuration >Protocols > SIP).
The TURN relay status page (Status > TURN relay usage) now provides a summary list of all the clients that
are connected to the TURN server. From there you can select a specific client to see all of the relays and ports
that it is using.
Ability to copy search rules. You can use the Clone action on the search rules listing page (Configuration
>Dial plan >Search rules) to copy and then edit an existing search rule.
502
The DNS lookup tool allows you to select which DNS servers (from the configured set of default DNS servers)
to use for the lookup.
The automated protection service now supports IPv6 addresses.
Access to the systemunit.xml file is now protected. Only authenticated VCS administrator accounts can access the
file. This may affect the discovery of VCS by Cisco TMS.
Call status and call history now indicates components routed through the B2BUA for encryption or ICE support with a
component type of 'B2BUA' (formerly 'Encryption B2BUA').
Note:The combination of having static NATmode on and having the B2BUA engaged to do media
encryption/decryption can cause the firewall outside the VCS Expressway to mistrust packets originating from the
VCS Expressway. You can work around this by configuring the firewall to allow NATreflection. If your firewall cannot
allow this, you must configure the traversal path such that the B2BUAon the VCS Expressway is not engaged.
X8.1.1
Unified Communications: mobile and remote access
Cisco Unified Communications mobile and remote access is a core part of the Cisco CollaborationEdge Architecture.
It allows endpoints such as Cisco Jabber to have their registration, call control, provisioning, messaging and
presence services provided by Cisco Unified Communications Manager (Unified CM) when the endpoint is not within
the enterprise network. The VCS provides secure firewall traversal and line-side support for Unified CM registrations.
For more information including configuration recommendations and troubleshooting details, see Unified
Communications: Mobile and Remote Access via VCS Deployment Guide.
Support to modify Maximum transmission unit (MTU) size
You can configure the maximum transmission unit (MTU) for each network interface on the System >IP page.
Diagnostic logging
The tcpdump facility has been removed from the Diagnostic logging tool.
Jabber Guest
Jabber Guest support has been removed (it was previously provided as a feature preview in X8.1). It will be
reintroduced in a future release of VCS software.
X8.1
Microsoft Lync 2013 / H.264 SVC support
The Microsoft Lync B2BUA now supports calls to and from Microsoft Lync 2013 clients. It provides interworking
between standard H.264 AVC and Lync 2013's H.264UC SVC codec. To use Lync 2013 you must install the Microsoft
Interoperability option key (formerly known as the Enhanced OCS Collaboration option key). Note that for Lync 2010,
the Microsoft Interoperability option key requirements remain as per previous releases (i.e. it is required for
encrypted calls to and from Microsoft Lync Server and for establishing ICE calls to Lync clients).
Presentation sharing via Lync 2013 is supported but only from VCS to Lync.
Support for standards-based H.264 SVC codecs
The B2BUA now supports calls to standards-based H.264 SVC codecs.
Improved performance and scalability
VCS X8.1 software can take advantage of the improved performance and scalability capabilities that are
available when running on Large VM server deployments. It can support up to 500 traversal calls, 750 non-
traversal calls and 5000 registrations. Note that standard VCS appliances or equivalent VM hardware still
503
provides support for up to 150 traversal calls, 750 non-traversal calls and 2500 registrations.
The number of concurrent searches has increased from 100 to 500.
New traversal media port framework
For new installations of X8.1 or later, the default range for traversal media ports is 36000 59999. The
previous default range of 50000 - 54999 still applies to earlier releases that have upgraded to X8.1. The larger
range is required to support the improved scalability features.
The media demultiplexing ports on the VCS Expressway now use the first set of ports from the general range of
traversal media ports instead of 2776 and 2777.
On existing systems that have been upgraded to X8.1, this will be 50000 and 50001 by default.
On new installations of X8.1, this will be 36000 and 36001 by default.
On large VM deployments, the first 12 ports in the traversal media port range are used (50000 - 50011 or
36000 - 36011 as appropriate).
This applies to all RTP/RTCP media, regardless of whether it is H.323 or SIP. Thus, the previously used Media
demultiplexing RTP port and RTCP port settings (Configuration > Traversal > Ports) and associated
xConfiguration Traversal Server CLI commands have been removed.
Administrators will need to adjust their firewall settings accordingly.
New TURN server port framework
On Large systems you can configure a range of TURN request listening ports. The default range is 3478 3483.
For new installations of X8.1 or later, the default range for TURN relay media ports is 24000 29999. The previous
default range of 60000 61799 still applies to earlier releases that have upgraded to X8.1.
Delegated credential checking for device authentication (SIP only)
By default, the VCS uses the relevant credential checking mechanisms (local database, Active Directory Service or
H.350 directory via LDAP) on the VCS performing the authentication challenge.
Alternatively you can now configure the VCS so that the credential checking of SIP messages is delegated, via a
traversal zone, to another VCS. Delegated credential checking is useful in deployments where you want to allow
devices to register on a VCS Expressway, but for security you want all communications with authentication systems
(such as an Active Directory server) to be performed inside the enterprise.
Credential checking for both Digest and NTLM messages may be delegated.
Automated protection
An automated intrusion protection feature has been added. It can be used to detect and block malicious traffic and to
help protect the VCS from dictionary-based attempts to breach login security.
It works by parsing the system's log files to look for repeated failures to access specific service categories, such as
SIP, SSH and web/HTTPS access. When the number of failures within a specified time window reaches the
configured threshold, the source host address (the intruder) is blocked for a period of time. You can configure sets of
addresses that are exempted always from one or more categories.
Automated protection should be used in combination with the existing firewall rules feature - use automated
protection to temporarily block specific threats and use firewall rules to block permanently a range of known host
addresses.
Licensing of audio-only SIP traversal calls
Audio-only SIP traversal calls are now treated distinctly from video SIP traversal calls. Each traversal call license
allows either 1 video call or 2 audio-only SIP calls. Hence, a 100 traversal call license would allow, for example, 90
video and 20 SIP audio-only simultaneous calls. Any other audio-only call (non-traversal, H.323 or interworked) will
consume a standard video call license (traversal or non-traversal as appropriate).
The Overview and Resource usage pages show separate counts for video and audio-only SIP traversal calls.
Note that:
504
VCS defines an "audio-only" SIP call as one that was negotiated with a single m= line in the SDP. Thus, for
example, if a person makes a telephone call but the SIP UA includes an additional m= line in the SDP, the
call will consume a video call license.
While an "audio-only" SIP call is being established, it is treated (licensed) as a video call. It only becomes
licensed as "audio-only" when the call setup has completed. This means that if your system approaches its
maximum licensed limit, you may be unable to connect some "audio-only" calls if they are made
simultaneously.
The VCS does not support midcall license optimization.
TMS Agent functionality removed
TMS Agent (legacy mode) functionality has been removed. Instead, if you use TMS provisioning, you must use TMS
Provisioning Extension services.
Java application removed
The Java application has been removed. This removes the threat of Java security vulnerabilities.
OCS Relay functionality and Microsoft OCS 2007 zone profile removed
OCS Relay functionality and the Microsoft Office Communications Server 2007 zone profile have been removed. The
Cisco AM GW configuration options previously under the VCS configuration menu, and the Cisco Advanced Media
Gateway zone profile have also been removed.
Instead, we recommend that you use the Microsoft Lync B2BUA to route SIP calls between the VCS and a Microsoft
Lync Server, and to configure your Cisco AM GWs as B2BUA transcoders. Note that B2BUA connections to Microsoft
OCS are no longer supported from X8.1.
Support for Active Control
VCS supports Active Control (iX Channel passthrough) as supported by Cisco TelePresence Server 3.1 or later and
endpoints running TC6.2 or later. It can be configured on a per-zone basis.
FIPS140-2 cryptographic mode
VCS has implemented FIPS140-2 compliant features.
New VMware installations
New VMware installations have a choice of 3 .ova files: Small (for Cisco Business Edition 6000 deployments),
Medium (for typical deployments) or Large (for large-scale deployments). Note that the VM .ova files are used for
new installations only. Do not use them to upgrade your existing VM installation.
See VCS on Virtual Machine Installation Guide for information about deploying on UCS tested reference
configurations and their associated memory and CPU resource reservation requirements.
ICE messaging support
ICE messaging support is now configurable at the zone and subzone level.
Certificate management
The certificate management pages are now located under Maintenance > Security certificates:
The management of CA certificates has been improved, allowing you to view, upload and delete individual CA
certificates.
The VCS's server and trusted CA certificates can be viewed in either a human-readable, decoded format, or in
their raw, PEM format.
The online help has a new skin and an improved search capability.
There is a new Cisco Unified Communications Manager (8.6.1 or later) zone profile. This profile supports BFCP
and should be used in SIP trunk neighbor zones to Unified CM running version 8.6.1 or later.
The ephemeral port range can be configured via the web interface (System > Administration).
505
Maintenance mode can be configured via the web interface (Maintenance > Maintenance mode).
The Microsoft Lync B2BUA supports multiple TURN servers.
The Lync B2BUA status page now shows the number of active calls, and resource usage as a percentage of
the number of allowed Lync B2BUA calls.
A B2BUA service restart is no longer required to enable changes to the list of trusted hosts to take effect.
A contact email address and a proxy server can be specified when configuring the incident reporting server.
The DNS cache is flushed automatically whenever any DNS configuration is changed (System >DNS). The
DNS page also contains a manual option to flush the DNS cache.
When logging in, you now have to choose the administrator login option only if you are using "standalone
FindMe" i.e. FindMe without Cisco TMSPE.
CPL location node supports regex-based source alias rewriting.
Active Directory Service configuration: you can specify an override value for the NetBIOS machine name if the
System host name, which is used as the default name, exceeds 15 characters.
Previously-installed language packs can be deleted.
The VCS Starter Pack Express supports device provisioning for SX20 endpoints. Note: this is a preview
feature.
You have the option to take a tcpdump while diagnostic logging is in progress.
SIP network logging at the DEBUG level now includes the local address and port (as well as the
destination/source information).
You can specify the transport type to use for SIP calls from a DNS zone, when DNS NAPTR records and SIP
URI parameters do not provide the preferred transport information.
The VCS supports time-limited option keys. The options keys page displays the validity period of each key. All
pre-existing option keys have an Unlimited validity period.
Filtering options are only displayed on status and list pages if there is more than one page of information to
display. Status and list pages show 200 records per page, except for Log pages which show 1000 records per
page.
When configuring firewall rules:
You can choose whether to drop or reject denied traffic. On upgrade to X8.1 or later, any existing "deny"
rules will now drop the traffic; prior to X8.1 the traffic would have been rejected.
If you have made several changes there is now an option to revert all changes. This discards all pending
changes and resets the working copy of the rules to match the current active rules.
You can more easily change the order of the rules by using up/down arrow buttons to swap the priorities of
adjacent rules.
Rules can be configured for XMPP traffic.
The Search rules page now indicates if the target zone of a rule is unavailable.
Port conflict alarms now indicate the exact features and ports that are in conflict.
When performing a system backup, the backup filename is now prefixed by the software version number.
The application now uses CiscoSSL (instead of OpenSSL).
The xConfiguration and xCommand CLI command sets removed in version X7.2 have been reinstated.
When using CPL to modify the source URL of a From header, any corresponding display name is also modified
to match the username part of the modified source URL.
Improved web interface usability when switching between SRV and address record resolution modes when
configuring the address of an LDAP server for remote user account authentication.
For new installations of X8.1 or later, the default range for ephemeral ports is 30000 35999. Prior to X8.1,
the default range was 40000 49999. Existing systems upgraded to X8.1 or later will preserve their previous
506
port ranges.
The Dual Network Interfaces option key is now called Advanced Networking. When the key is installed you
can now configure the use of dual network interfaces separately from the use of static NAT.
Most system configuration items are now peer-specific (they are not replicated across peers when the VCS is
part of a cluster). See Peer-Specific Items in Clustered Systems, page 166 for more information.
New installations of VCS software now ship with a temporary trusted CA, and a server certificate issued by
that temporary CA. We strongly recommend that you replace the server certificate with one generated by a
trusted certificate authority, and that you install CA certificates for the authorities that you trust. When you
upgrade to this release from an earlier installation of VCS software, your existing server and trusted CA
certificates are retained, and will not be affected by this feature.
When configuring the sources for administrator account authentication, the Remote option is now labeled as
Remote only.
This also means you can no longer access the VCS via the default admin account if a Remote only
authentication source is in use. The Local option has also been renamed to Local only. Note: do not use
Remote only if VCS is managed by Cisco TMS.
The Reboot, Restart and Shutdown maintenance options have been combined into one Restart options page.
When starting a diagnostic log, the relevant system modules now have their log levels automatically set to
"debug" and are automatically reset to their original values when logging is stopped.
You can no longer access the system over Telnet.
The Expressway option key is now called Traversal Server.
The DNS Local host name is now referred to as the System host name.
Auditor access level now includes the Alarms page.
The login account configuration pages are now accessed under a new top-level Users menu (previously
under Maintenance > Login accounts).
The Clustering page is now accessed under the System menu.
The System administration page is now accessed under System > Administration.
The Firewall rules configuration pages are now accessed under System > Protection.
The VCS configuration menu is now called just Configuration.
The SIP page is now accessed directly via Configuration > Protocols > SIP and the Domains page is now
accessed via Configuration > Domains.
The Calls page and menu is now calledCall routing. Call routed mode is now called Call signaling
optimization and the options are On and Off.
On the VCS Expressway, the VCS configuration > Expressway menu is now Configuration > Traversal.
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.
References to 'Movi' have been changed to 'Jabber Video'.
The FindMe configuration page is now accessed directly under Applications > FindMe.
On the Upgrade page, the VCS platform component is now referred to as System platform.
The Advanced account security page is now called Advanced security and is accessed via Maintenance >
Advanced security.
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.
The advanced zone configuration Empty INVITE allowed setting is now referred to as Send empty INVITE for
interworked calls.
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.
507
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.
The xConfiguration Interworking Require Invite Header Mode is now Off by default.
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.
The DNS lookup tool includes Unified Communications SRV services.
X7.2.1
The VCS Starter Pack Express supports Cisco Jabber for iPad.
X7.2
Controlled SIP TLS connections to the Default Zone
Default Zone access rules that control which external systems are allowed to connect over SIPTLS to the VCS via
the Default Zone can now be configured.
Each rule specifies a pattern type and string that is compared to the identities (Subject Common Name and any
Subject Alternative Names) contained within the certificate presented by the external system. You can then allow or
deny access to systems whose certificates match the specified pattern.
Device authentication
The VCS can now be configured to authenticate devices against multiple remote H.350 directory servers. This
provides a redundancy mechanism in the event of reachability problems to an H.350 directory server.
As from version X7.2, the VCS attempts to verify device credentials presented to it (for Digest authentication)
by first checking against its on-box local database of usernames and passwords, before checking against any
configured H.350 directory server. As a result of this:
The Device authentication configuration page no longer exists; there is no longer an option to switch
between an authentication database type of Local database or LDAP database.
The NTLM protocol challenges setting is now configured on the Active Directory Service page.
The Device LDAPconfiguration and Device LDAP schemas pages are now called Device authentication
H.350 configuration and Device authentication H.350 schemas respectively.
The Alias origin field on the Device authentication H.350 configuration page is now called Source of aliases
for registration.
Enhanced account security
Administrator accounts can now be configured to authenticate first against the local database and then if no
matching account is found to fall back to a check against the external credentials directory.
When defining administrator accounts and groups, you can now also specify if the account/group can access
the web interface and/or the XML/REST APIs.
When strict passwords are enforced for administrator accounts, you can now customize the rules for what
constitutes a strict password.
Local administrator passwords are now stored using a SHA512 hash.
In a cluster, the default admin account password is now replicated across all peers.
Note that the Login Administrator set of xConfiguration CLI commands are no longer supported.
508
System security enhancements
You can now configure firewall rules to control access to the VCS at the IP level. You can:
specify the source IP address subnet from which to allow or deny traffic
configure well known services such as SSH, HTTP/HTTPS or specify customized rules based on transport
protocols and port ranges
The VCS can be configured to use a combination of OCSP and CRL checking for certificates exchanged
during SIP TLS connection establishment. CRLs can be loaded manually onto the VCS, downloaded
automatically from preconfigured URIs, or downloaded automatically from a CRL distribution point (CDP).
The VCS can now generate server certificate signing requests. This removes the need to use an external
mechanism to generate and obtain certificate requests. The upload of the VCS's trusted CA certificate and the
management of its server certificate are now configured on separate pages under the Maintenance
>Certificate management menu.
When enabling client certificate-based security you can now configure CRL checking behavior.
VCS can now be configured to use HTTP Strict Transport Security (HSTS). This can be used to force a web
browser to communicate with the VCS using secure connections only.
Access to the VCS via the serial port can be disabled.
You can configure the authentication method used by the VCS when connecting to an NTP server. It utilizes
the security features available in NTPv4 and retains compatibility with NTPv3 implementations. Options
include symmetric key message hashing and private key encryption.
System backup files can now be encrypted / password protected.
OpenSSL has been updated to version 1.0.1b (includes support for TLS v1.2).
Zone and subzone media encryption policy
Media encryption policy settings allow you to selectively add or remove media encryption capabilities for SIP calls
flowing through the VCS. This allows you to configure your system so that, for example, all traffic arriving or leaving
the VCS Expressway from the public internet is encrypted, but is unencrypted when in your private network. The
policy is configured on a per zone/subzone basis; this level of granularity means that different encryption policies
could be applied to each leg of a call in/out of a zone/subzone.
Call processing
When configuring search rules you can now specify:
The source protocol for which the rule applies.

A specific source zone or subzone for which the rule applies.
Improved interworking flow control
The VCS now supports the ability to interwork the H.323 flowControlCommand into RFC 5104 Temporary Maximum
Media Stream Bit Rate Request (TMMBR). This provides the ability to stem the flow of data from a remote participant.
Enhanced diagnostics
There is an improved filter mechanism for call and registration status management.
Search history shows additional information including search start timestamps and durations, and improved
reporting of search failure reasons.
A Tracepath network utility has been added (to complement the existing traceroute tool).
The Locate tool now allows you to specify a specific subzone (or zone) as the source of the search request.
The VCS now supports IETF format messages when sending events to remote syslog servers. Note that the
Logging page is now located under the Maintenance menu.
When a diagnostic log file is downloaded, the filename now includes the local host name; this helps
distinguish it from diagnostic files downloaded from other cluster peers.
509
Core dump mode is now enabled by default. It can be configured on the Incident reporting configuration
page; it can no longer be configured via the CLI.
System snapshot files now include a list of active alarms.
The default Traversal Subzone media port range is now 50000 - 54999 (previously 50000 - 52399), in order to
support the new media encryption policy feature. To reflect this change, system administrators may need to
modify the rules configured in their firewall devices.
Up to 20 policy services can now be configured (the limit was 5 previously).
When configuring a DNS zone you can now specify a TLS verify subject name to use when verifying the
destination system server's certificate.
The %ip% pattern matching variables now apply to all peer addresses if the VCS is part of a cluster; when
used in a replace string the variable is always substituted with the address of the local peer only.
The Microsoft B2BUA now supports up to 100 simultaneous calls (the limit was 50 previously); however, calls
that use transcoder resources count as 2 calls.
TURN server now has full IPv6 support (as per RFC 6156). The TURN relays status page displays the
addresses on which the TURN server is listening, and the addresses from which it is allocating relays.
The VCS now supports early dialog SIP UPDATE messages. Note that the relevant zone must be configured
with SIPUPDATEstrip mode set to Off (set via the Custom zone profile).
Automatic CRL updates can now use HTTPS distribution points.
DNS queries can now be configured to use the ephemeral port range or to use a customized range.
The Clustering page displays the name (in addition to the address) of all of the peers.
The SIPDomains page includes an Index column that corresponds to the numeric elements of the
%localdomain1%,%localdomain2%, . . . %localdomain200% pattern matching variables.
When upgrading software components, the MD5 and SHA1 hash values of the software image file being
uploaded are displayed for user verification (when upgrading from X7.2 or later).
There is no longer a need to restart the VCS after uploading a language pack.
Support for some xConfiguration commands removed
The following xConfiguration CLI command sets are no longer supported:
xConfiguration Administration HTTPS RequireClientCertificate

xConfiguration Administration MaxConcurrentSessions
xConfiguration Administration TimeOut
xConfiguration Authentication Database
xConfiguration Authentication LDAP BaseDN
xConfiguration Certification AdvancedAccountSecurity
xConfiguration Core Dump Mode
xConfiguration Error Reports
xConfiguration IP DNS Server
xConfiguration LDAP
xConfiguration Log
xConfiguration Login Administrator
xConfiguration Login User
xConfiguration NTP Address
xConfiguration SNMP
xConfiguration SystemUnit AdminAccount
510
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.
You are recommended to switch from using the TMS Agent legacy mode to the new Provisioning Extension mode as
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.
Virtual appliance support
The VCS can run on VMware on Cisco UCS C200 M2 and UCS C210 M2 servers.
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.
Automatically uploaded CRL files are now included when checking the validity of client certificates on the
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.
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.
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.
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 Using Active Directory Database (Direct), page 129 for more information.
511
Previously this feature was only configurable via the CLI, from X7.0 it can be configured via the web 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 License Usage Within a Cluster, page 162 for
more information. Note that any other option keys (FindMe, for example) must still be installed identically on each
cluster peer, as before.
Microsoft Edge Server support via B2BUA for Microsoft OCS/Lync
Support for Microsoft Edge Server communications has been added via the introduction of a back-to-back user agent
(B2BUA) application. The B2BUA provides interworking between Microsoft ICE (used when MOC / Lync clients
communicate through the Edge Server) and media for communications with standard video endpoints. The B2BUA
also provides call hold, call transfer and Multiway support for calls with OCS/Lync clients, and can share FindMe
presence information with OCS/Lync. See Microsoft Lync B2BUA, page 236 for more information.
Presence User Agent
You can now configure the Default published status for registered endpoints to be either Online or Offline. This is
the presentity status published by the Presence User Agent for registered endpoints when they are not "In-Call". See
Configuring Presence, page 233 for more information.
Enhanced SIP registration expiry controls
New SIP registration settings on the SIP page (Configuration >Protocols >SIP > Configuration) allow you to
configure how the VCS calculates the expiry period for SIP registration requests. These settings enable the system to
balance the load of registration and re-registration requests. They can be configured separately for standard and
Outbound registration connections.
These settings supersede the previous Registration expire delta setting.
Improved diagnostics
A range of tools have been introduced to improve troubleshooting.
Diagnostic logging
Additional diagnostic tools have been introduced under a new Maintenance > Diagnostics menu structure:
There is a Diagnostic logging tool (Maintenance > Diagnostics > Diagnostic logging) that can be used to
assist in troubleshooting system issues. It allows you to generate a diagnostic log of system activity over a
period of time, and then to download the log so that it can be sent to your Cisco customer support
representative.
You can configure log levels for specific Network Log and Support Log modules. Note that these are
advanced logging configuration options and should only be changed on the advice of Cisco customer support.
The existing System snapshot and Incident reporting options have been moved under the new Maintenance
> Diagnostics menu structure.
The System snapshot tool can now generate three types of snapshot: system status, system logs or a full
snapshot.
Network utilities
The following network utility tools have been introduced under Maintenance > Tools >Network utilities:
Ping: allows you to check that a particular host system is contactable from the VCS and that your network is
correctly configured to reach it.
Traceroute: allows you to discover the route taken by a network packet sent from the VCS to a particular
destination host system.
DNS lookup: allows you to check which domain name server (DNS server) is responding to a request for a
particular hostname.
512
Alarms (warnings)
Warnings are now referred to as alarms.

The alarm icon in the menu bar indicates the current number of unacknowledged alarms.
The Alarms page indicates when an alarm was last raised and the number of times it has occurred since the
last restart.
In a clustered VCS system the Alarms page shows all of the alarms raised by any of the cluster peers. Only
those alarms that have been raised by the "current" peer can be acknowledged.
GRUU (Globally Routable User Agent URI) support
The VCS has implemented the Public GRUU element of RFC 5627: Obtaining and Using Globally Routable User Agent
URIs (GRUUs) in the Session Initiation Protocol (SIP).
A GRUU is a SIP URI that can be used anywhere on the internet to route a request to a specific AOR instance. Note
that the registering domain must be globally routable in order for the VCS to support GRUU.
Improved DNS subsystem
The DNS subsystem within the VCS has been re-structured and improved to be standards compliant. It provides the
ability to specify explicit upstream DNS servers for specified domains.
Improved NTP synchronization
The VCS can now be configured to connect to up to 5 standards-based NTP server addresses.
TMS Agent database credentials included within local authentication database lookups
In addition to any manually created entries, the Cisco VCS now checks credentials stored within the TMS Agent
database when the device authentication database type is set to Local database.
This makes it easier to enable authentication on the Cisco VCS when provisioning is using passwords originating from
TMS.
You can now configure up to 200 SIP domains.

You can now configure up to 10,000 local authentication database credentials.
Full support of RFC 5806: any SIP diversion headers received in a 302 response are now maintained in the
outgoing INVITE message.
Improved zone status reporting: the zones summary page now shows separate SIP and H.323 connection
status information.
Table sorting indicators: tabular displays now indicate by which column each table is sorted.
A filter facility has been added to the Subzones list page.
Chrome web browser is now supported; Internet Explorer 6 is no longer officially supported.
The administrator no longer has to log out and log back in again after reconfiguring DNS server addresses.
There is a new Call signaling routed mode advanced zone profile setting for neighbor zones. It controls
whether the zone always takes the signaling or uses the system-wide Call routed mode setting.
There is a new H.323 call signaling port advanced zone profile setting for neighbor zones. It identifies the call
signaling port on the neighbor system to use if Automatically respond to H.323 searches is set to On.
SSH and SCP clients are no longer available in the VCS operating system.
Reverse Path Filtering (RFC1812) is enabled by default. This ensures that the VCS will only accept packets on
interfaces from source addresses to which there are valid routes in the routing table for that interface. This
change may necessitate the adding of additional static routes on dual-interface VCSs to ensure the VCS
routing table matches the network topology.
513
Related Documentation
The following table lists documents and web sites referenced in this document, and other supporting documentation.
All documentation for the latest version of VCS can be found at www.cisco.com.
Title Link
VCS Administrator Guide (this document) www.cisco.com
Cisco TMS Provisioning Extension Deployment Guide www.cisco.com
Authenticating VCS Accounts Using LDAP Deployment Guide www.cisco.com
Basic Configuration - Single VCS Control Deployment Guide www.cisco.com
Basic Configuration - VCS Expressway with VCS Control Deployment Guide www.cisco.com
VCS Certificate Creation and Use Deployment Guide www.cisco.com
Cisco Unified Communications Manager with VCS Deployment Guide www.cisco.com
VCS and Cisco Unity Connection Voicemail Integration Deployment Guide www.cisco.com
VCS Cluster Creation and Maintenance Deployment Guide www.cisco.com
Device Authentication on VCS Deployment Guide www.cisco.com
ENUM Dialing on VCS Deployment Guide www.cisco.com
External Policy on VCS Deployment Guide www.cisco.com
FindMe Deployment Guide www.cisco.com
VCS Getting Started Guide www.cisco.com
VCS CE500 Appliance Installation Guide www.cisco.com
VCS CE1000 Appliance Installation Guide www.cisco.com
VCS CE1100 Appliance Installation Guide VCS Installation Guides page
VCS IP Port Usage for Firewall Traversal www.cisco.com
Microsoft Lync 2010, Cisco AM GW and VCS Deployment Guide www.cisco.com
Microsoft Lync and VCS Deployment Guide www.cisco.com
Multiway Deployment Guide www.cisco.com
VCS Starter Pack Express Deployment Guide www.cisco.com
Unified Communications: Mobile and Remote Access via VCS Deployment www.cisco.com
Guide
VCS on Virtual Machine Installation Guide www.cisco.com
DNS and BIND Fourth Edition, Albitz and Liu, OReilly and Associates, ISBN: 0-
596-00158-4
ITU Specification: H.235 Security and encryption for H-Series multimedia http://www.itu.int/rec/ T-REC-
terminals H.235/en
ITU Specification: H.323: Packet-based multimedia communications systems http://www.itu.int/rec/ T-REC-

H.323/en
514
Title Link
ITU Specification: H.350 Directory services architecture for multimedia http://www.itu.int/rec/ T-REC-
conferencing H.350/en
Management Information Base for Network Management of TCP/IP-based http://tools.ietf.org/html/rfc1213

internets: MIB-II
Network Time Protocol website http://www.ntp.org/
PHP regex guidelines http://php.net/manual/en/

book.pcre.php
Regular Expression Pocket Reference ISBN-10: 0596514271 ISBN-13: 978-

0596514273
RFC 791: Internet Protocol http://tools.ietf.org/html/rfc791
RFC 1305: Network Time Protocol http://tools.ietf.org/html/rfc1305
RFC 2460: Internet Protocol, Version 6 (IPv6) Specification http://tools.ietf.org/html/rfc2460
RFC 2782: A DNS RR for specifying the location of services (DNS SRV) http://tools.ietf.org/html/rfc2782
RFC 2915: The Naming Authority Pointer (NAPTR) DNS Resource Record http://tools.ietf.org/html/rfc2915
RFC 3164: The BSD syslog Protocol http://tools.ietf.org/html/rfc3164
RFC 3261: SIP: Session Initiation Protocol http://tools.ietf.org/html/rfc3261
RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers http://tools.ietf.org/html/rfc3263
RFC 3326: The Reason Header Field for the Session Initiation Protocol (SIP) http://tools.ietf.org/html/rfc3326
RFC 3327: Session Initiation Protocol (SIP) Extension Header Field for http://tools.ietf.org/html/rfc3327
Registering Non-Adjacent Contacts
RFC 3489: STUN - Simple Traversal of User Datagram Protocol (UDP) Through http://tools.ietf.org/html/rfc3489
NATs
RFC 3550: RTP: A Transport Protocol for Real-Time Applications http://tools.ietf.org/html/rfc3550
RFC 3761: The E.164 to URI Dynamic Delegation Discovery System (DDDS) http://tools.ietf.org/html/rfc3761
Application (ENUM)
RFC 3880: Call Processing Language (CPL): A Language for User Control of http://tools.ietf.org/html/rfc3880
Internet Telephony Services
RFC 4028: Session Timers in the Session Initiation Protocol (SIP) http://tools.ietf.org/html/rfc4028
RFC 4787: Network Address Translation (NAT) Behavioral Requirements for http://tools.ietf.org/html/rfc4787
Unicast UDP
RFC 5245: Interactive Connectivity Establishment (ICE) http://tools.ietf.org/html/rfc5245
RFC5424:The Syslog Protocol http://tools.ietf.org/html/rfc5424
RFC 5626: Managing Client-Initiated Connections in the Session Initiation http://tools.ietf.org/html/rfc5626

Protocol (SIP)
RFC 5627: Obtaining and Using Globally Routable User Agent URIs (GRUUs) in http://tools.ietf.org/html/rfc5627
SIP
RFC 5806: Diversion Indication in SIP http://tools.ietf.org/html/rfc5806
Session Traversal Utilities for NAT (STUN) http://tools.ietf.org/html/rfc5389
515
Title Link
Traversal Using Relays around NAT (TURN): Relay Extensions to Session http://tools.ietf.org/html/rfc5766
Traversal Utilities for NAT (STUN)
516
Legal Notices
Intellectual Property Rights

This Administrator Guide and the product to which it relates contain information that is proprietary to TANDBERG and
its licensors. Information regarding the product is found below in the Copyright notice and Patent information
sections.
TANDBERG is a registered trademark belonging to Tandberg ASA. Other trademarks used in this document are the
property of their respective holders. This Guide may be reproduced in its entirety, including all copyright and
intellectual property notices, in limited quantities in connection with the use of this product. Except for the limited
exception set forth in the previous sentence, no part of this Guide may be reproduced, stored in a retrieval system, or
transmitted, in any form, or by any means, electronically, mechanically, by photocopying, or otherwise, without the
prior written permission of TANDBERG.
COPYRIGHT TANDBERG
Copyright Notice
The product that is covered by this Administrator Guide is protected under copyright, patent, and other intellectual
property rights of various jurisdictions.
This product is Copyright 2014, Tandberg Telecom UK Limited. All rights reserved.
TANDBERG is now part of Cisco. Tandberg Telecom UK Limited is a wholly owned subsidiary of Cisco Systems, Inc.
The terms and conditions of use can be found at:
http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/license_info/Cisco_VCS_EULA.pdf.
This product includes copyrighted software licensed from others. A list of the licenses and notices for open source
software used in this product can be found at: http://www.cisco.com/en/US/products/ps11337/products_licensing_
information_listing.html.
This product includes software developed by Computing Services at Carnegie Mellon University
(http://www.cmu.edu/computing/).
This product includes software developed by the University of California, Berkeley and its contributors.
IMPORTANT: USE OF THIS PRODUCT IS SUBJECT IN ALL CASES TO THE COPYRIGHT RIGHTS AND THE TERMS AND
CONDITIONS OF USE REFERRED TO ABOVE. USE OF THIS PRODUCT CONSTITUTES AGREEMENT TO SUCH TERMS
AND CONDITIONS.
AVC Video License
With respect to each AVC/H.264 product, we are obligated to provide the following notice:
This product is licensed under the AVC patent portfolio license for the personal use of a consumer or other uses in
which it does not receive remuneration to (i) encode video in compliance with the AVC standard (AVC video) and/or
(ii) decode AVC video that was encoded by a consumer engaged in a personal activity and/or was obtained from a
video provider licensed to provide AVC video. No license is granted or shall be implied for any other use. Additional
information may be obtained from MPEGLA, L.L.C.
See http://www.mpegla.com.
Accordingly, please be advised that service providers, content providers, and broadcasters are required to obtain a
separate use license from MPEG LA prior to any use of AVC/H.264 encoders and/or decoders.
Patent Information
This product is covered by one or more of the following patents:
US7,512,708
EP1305927
517
EP1338127
518
Cisco Legal Information
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE
WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED
TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST
TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE
INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS
REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR
CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of
California, Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. All rights reserved.
Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE
SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL
WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING,
USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR
INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA
ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual
addresses and phone numbers. Any examples, command display output, network topology diagrams, and other
figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone
numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version
should be referred to for latest version.
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco
website at www.cisco.com/go/offices.
2015 Cisco Systems, Inc. All rights reserved.
Cisco Trademark
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other
countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks
mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
519

Cisco VCS Administrator Guide X8 7

Uploaded by

Copyright:

Available Formats

Cisco VCS Administrator Guide X8 7

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cisco VCS Administrator Guide X8 7

Uploaded by

Copyright:

Available Formats

Cisco TelePresence Video Communication

Software version: X8.7

Cisco Systems, Inc. www.cisco.com

About the Cisco TelePresence Video Communication Server (VCS) 2

About the Cisco TelePresence Video Communication Server (VCS)

Cisco Systems, Inc. www.cisco.com

VCS Base Applications

1000 subzones and supporting up to 3000 membership rules

SIP to Microsoft Lync 2010 / 2013 Interoperability

Appliance and Virtual Machine Options

Virtual Machine Options

Small (for BE 6000 platform)

Software Versions Supported by Hardware Platforms

Platform name Serial Numbers Scope of software version support

VCS appliance (1st generation) 52A##### All features in versions up to and

Critical fixes only in X8.7.n*

Small VM (OVA) (Auto-generated) X8.1 onwards

Medium VM (OVA) (Auto-generated) X8.1 onwards

Large VM (OVA) (Auto-generated) X8.1 onwards

CE500 (VCS pre-installed on UCS C220 52C##### X8.1.1 onwards

CE1000 (VCS pre-installed on UCS 52B##### X8.1.1 onwards

CE1100 (VCS pre-installed on UCS 52D##### X8.6.1 onwards

About This Guide

Using the Web Interface

1. Open a browser window and in the address bar type either:

Using the Command Line Interface (CLI)

1. Start an SSH session.

Web Page Features and Layout

Figure 1 Example list page

Figure 2 Example configuration page

Mandatory Indicates an input field that must be completed.

Whats New in This Version?

Table 2 Feature History by Release Number

Feature / change X8.7

Dial via Office-Reverse (DVO-R) Supported

Lync Screen Sharing Through a Gateway Cluster Supported

Hybrid Services and Expressway/VCS Rebranding Supported

Hosting on VMWare vSphere 6.0 Supported

Keyword Filter for Syslog Output Supported

Changes and Minor Enhancements Supported

Dial via Office-Reverse Through MRA

The users Mobile Identity (mobile number).

Cisco Unified Communications Manager 11.0(1) or later

Cisco IP Phone 8800 Series

Hosting on VMWare vSphere 6.0

Configuring Ethernet Settings

Cisco Systems, Inc. www.cisco.com

IPv4 to IPv6 Interworking

About Advanced Networking

Configuring Dual Network Interfaces

Configuring Static NAT

1. Ensure that the Advanced Networking option key is installed.

Configuring DNS Settings

Configuring the System Host Name and Domain Name

It must be unique for each peer in a cluster.

Configuring DNS Server Addresses

Configuring Quality of Service Settings

Configuring Firewall Rules

Setting Up and Activating Firewall Rules

To set up and activate new rules: