









Legal Notices
Intellectual Property Rights
The specifications for the product and the information in this Administrator Guide are subject to change at any time, without notice, by TANDBERG.
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 adjacent in the Copyright Notice and Patent Information sections.
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 covered by one or more of the following patents:
Every effort has been made to supply complete and accurate information in this Administrator Guide, however, TANDBERG assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.
Copyright © 2008, Tandberg Telecom AS. All rights reserved.
This Administrator Guide may be reproduced in its entirety, including all copyright and intellectual property notices, in limited quantities in connection with the use of the product. Except for the limited exception set forth in the previous sentence, no part of this Administrator 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. Requests for such permission should be addressed to ipr@tandberg.com.
This product includes copyrighted software licensed from others. A list of the copyright notices and the terms and conditions of use can be found at:
http://www.tandberg.com/collateral/ documentation/User_Manuals/TANDBERG VCS EULA.pdf
http://www.tandberg.com/collateral/ documentation/User_Manuals/TANDBERG VCS Copyrights.pdf.
TANDBERG® is a registered trademark belonging to Tandberg ASA. Other trademarks used in this document are the property of their respective holders.
All rights reserved.
Philip Pedersens vei 22 1366 Lysaker Norway
This product is · and

For your protection please read these safety instructions completely before you connect the equipment to the power source. Carefully observe all warnings, precautions and instructions both on the apparatus and in these operating instructions. Retain this manual for future reference.
Electromagnetic Compatibility (EMC)
Never use this apparatus, or connect or disconnect communication cables or power cables during lightning storms.
This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.
Never install cables, or any peripherals, • without first unplugging the device from it's power source.
EC Declaration of Conformity
Water and Moisture
Do not operate the apparatus in areas with high concentration of dust.
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.
Manufacturer: TANDBERG Telecom AS Product Name: TANDBERG Video Communication Server Type Number: TTC2-04 Description: Network unit
Do not operate the apparatus under or near • water – for example near a bathtub, kitchen sink, or laundry tub, in a wet basement, near a swimming pool or in other areas with high humidity.
Do not operate the apparatus in areas with vibration or place it on an unstable surface.
Never install jacks for communication cables • in wet locations unless the jack is specifically designed for wet locations.
Unplug the apparatus from its power source • and refer servicing to qualified personnel under the following conditions:
This product complies with Commission Directives:
The product may have hazardous voltage • inside. Never attempt to open this product, or any peripherals connected to the product, where this action requires a tool.
If the power cord or plug is damaged or • frayed.
If liquid has been spilled into the • apparatus.
Unplug the apparatus from communication • lines, mains power-outlet or any power source before cleaning or polishing.
This product should always be powered from • an earthed power outlet.
Never connect attached power supply cord to • other products.
Do not use liquid cleaners or aerosol • cleaners. Use a lint-free cloth lightly moistened with water for cleaning the exterior of the apparatus.
If the apparatus has been subjected to • excessive shock by being dropped.
In case any parts of the product has visual • damage never attempt to connect mains power, or any other power source, before consulting service personnel
The plug connecting the power cord to the • product/power supply serves as the main disconnect device for this equipment. The power cord must always be easily accessible.
Year which the CE mark was affixed: 2007
Do not block any of the ventilation openings • of the apparatus. Never cover the slots and openings with a cloth or other material. Never install the apparatus near heat sources such as radiators, heat registers, stoves, or other apparatus (including amplifiers) that produce heat.
For an official, signed version of this document, or details regarding documentation from the technical construction file, please contact TANDBERG.
If the apparatus fails to operate in • accordance with the operating instructions.
Route the power cord so as to avoid it being • walked on or pinched by items placed upon or against it. Pay particular attention to the plugs, receptacles and the point where the cord exits from the apparatus.
JATE Approval (Japan only)
Use only accessories specified by the manufacturer, or sold with the apparatus.
This unit must be connected to the public internet via a router/switch that has JATE approval.
Do not place the product in direct sunlight or • close to a surface directly heated by the sun.

Thank you for buying a product which contributes to a reduction in pollution, and thereby helps save the environment. Our products reduce the need for travel and transport and thereby reduce pollution. Our products have either none or few consumable parts (chemicals, toner, gas, paper). Our products are low energy consuming products.
As a manufacturer of electrical and electronic equipment TANDBERG is responsible for compliance with the requirements in the European Directives 2002/96/EC (WEEE) and 2002/95/ EC (RoHS).
As part of compliance with the European WEEE Directive, TANDBERG provides recycling information on request for all types of new equipment put on the market in Europe after August 13th 2005.
The primary aim of the WEEE Directive and RoHS Directive is to reduce the impact of disposal of electrical and electronic equipment at end-of-life. The WEEE Directive aims to reduce the amount of WEEE sent for disposal to landfill or incineration by requiring producers to arrange for collection and recycling. The RoHS Directive bans the use of certain heavy metals and brominated flame retardants to reduce the environmental impact of WEEE which is landfilled or incinerated.
Please contact TANDBERG and provide the following details for the product for which you would like to receive recycling information:
Environmental stewardship is important to TANDBERG’s culture. As a global company with strong corporate values, TANDBERG is committed to following international environmental legislation and designing technologies that help companies, individuals and communities creatively address environmental challenges.
TANDBERG has implemented necessary process changes to comply with the European RoHS Directive (2002/95/EC) and the European WEEE Directive (2002/96/EC).
TANDBERG’s environmental objectives are to:
Develop products that reduce energy consumption, CO • 2 emissions, and traffic congestion
Provide products and services that improve quality of life for • our customers
Produce products that can be recycled or disposed of safely • at the end of product life
In order to avoid the dissemination of hazardous substances in our environment and to diminish the pressure on natural resources, we encourage you to use the appropriate take-back systems in your area. Those systems will reuse or recycle most of the materials of your end of life equipment in a sound way.
TANDBERG is pleased to announce that we have replaced the printed versions of our User Guides with a digital CD version. Instead of a range of different user manuals, there is now one CD – which can be used with all TANDBERG products – in a variety of languages. The environmental benefits of this are significant. The CDs are recyclable and the savings on paper are huge. A simple web-based search feature helps you directly access the information you need. In addition, the TANDBERG video systems now have an intuitive on-page help function, which provides a range of useful features and tips. The contents of the CD can still be printed locally, whenever needed.
TANDBERG products put on the market after August 2005 are marked with a crossed-out wheelie bin symbol that invites you to use those take-back systems.
Please contact your local supplier, the regional waste administration, or http://www.tandberg.com/recycling if you need more information on the collection and recycling system in your area.



VCS Base Applications
The TANDBERG Video Communication Server (VCS) is an industry unique multi-application device that enhances the video experience with new functionality and provides transparent communication between SIP and H.323 endpoints. It allows you to manage endpoint registrations and calls, and control the bandwidth being used within your network. The VCS also offers advanced call policy that allows you to accept, reject and re- route calls.
VCS Expressway
The VCS Control provides internal video control and administration for all SIP and H.323 devices. It is normally deployed within your wide area network with endpoints that are behind the same firewalls or NAT devices.
The VCS Expressway provides standards-based firewall traversal for SIP and H.323 devices allowing secure firewall traversal of any firewall or NAT device.
As well as all the functionality of a VCS Control, it also provides registration of traversal-enabled devices and STUN Discovery and STUN Relay services.
The VCS Control replaces the need to have separate H.323 gatekeeper, SIP registrar and H.323 - SIP gateway servers.
The VCS forms part of TANDBERG’s Expressway™ firewall traversal solution, allowing you to securely connect to other video networks and equipment from your secured private network.
The VCS Expressway is normally deployed outside of your firewall or within the DMZ.
The VCS is supplied as either of two base applications: VCS Control and VCS Expressway.
Introduction

What’s New in this Version?
The following features have been introduced in version X2.0 of the VCS software:
Allows the VCS Expressway to connect to two separate networks in a DMZ deployment.
Easier to manage, quicker to deploy
Increased usability of the administration web interface.
Improved feature parity between H323 & SIP
Encryption supported for H323 – SIP gateway calls.
Dual video support for H323 – SIP gateway calls.
Enables the LAN 2 ethernet port on the VCS Expressway, allowing you to have a secondary IP address for your VCS.
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.
This configuration is intended for high-security deployments where the VCS Expressway is located in a DMZ between two separate firewalls on separate network segments.

This Administrator Guide is provided to help you make the best use of your TANDBERG VCS.
Your approach to this documentation depends on what you want to do and how much you already know.
Most configuration tasks on the VCS can be performed via either the web interface or a command line interface. This Guide will describe how to use both methods.
The Administrator Guide has been divided into several sections, each providing different information. In some places information is duplicated between sections to let you have all the relevant information in one place.
In this Guide, instructions for performing a task via the web interface are shown in the format:
This document does not have an index. This is intentional; if the Table of Contents does not direct you to the information you need, you can use the Find function in Adobe Reader to search the text for keywords.
Menu > Submenu • followed by the Name of the page that you will be taken to.
In most cases a screenshot of the page will be shown adjacent, with callouts describing each of the configurable options.
Our main objective with this Guide is to address your goals and needs. Please let us know how well we succeeded!
In this Guide, instructions for performing a task using the command line interface (CLI) are shown in the format:
These are meant as a reference only. Each command is hyperlinked to the Command Reference table at the back of this Guide; clicking on the hyperlink will take you to the appropriate section of the table showing all the available sub-elements, parameters and valuespaces for the given command.
Typing the given • xConfiguration path into the CLI will return a list of values currently configured for that element (and sub-elements where applicable).
Typing the given • xConfiguration path into the CLI followed by a ? will return information about the usage for that element and sub-elements.
Typing the given • xCommand command into the CLI with or without a ? will return information about the usage of that command.
Web Interface · Command Line Interface


This section describes how to install the VCS and carry out its initial configuration. It also gives an overview of the VCS’s Administrator settings and describes how to access it via either the Command Line Interface (CLI) or the web interface.

Make sure that the VCS is accessible and that all cables can • be easily connected.
The socket outlet shall be installed near to the equipment • and shall be easily accessible.
To avoid damage to the unit during transportation, the TANDBERG VCS is delivered in a special shipping box, which should contain the following components:
For ventilation: leave a space of at least 10cm (4 inches) • behind the VCS’s rear panel and 10cm (4 inches) in front of the front panel.
The room in which you install the VCS should have an ambient • temperature between 0ºC and 35ºC (32ºF and 95ºF) and between 10% and 90% non-condensing relative humidity.
A brief yet concise description of the procedure to get you up and going can be found in the Installation Sheet accompanying your TANDBERG product.
To use the VCS over IP, connect the ethernet cable from the LAN1 port on the VCS to your network.
To control the VCS using a
The LAN2 port can also be used if you have the Dual Network Interfaces option installed.
Connect the system power cable to an electrical distribution socket.
direct connection to a PC, connect the serial cable between the VCS’s DATA port and the COM port on a PC.
The LAN3 and LAN4 ports are not used.

To start the VCS:
To set the initial configuration using a PC connected to the VCS DATA port via a serial cable:
The LAN 1 IP address of the system. c.
Once it has rebooted, the VCS is ready to use. You can continue to use the serial connection, or you can connect to the system remotely over IP using either or both:
Ensure the power cable is connected. 1.
The LAN1 IPv4 subnet mask of the system d.
(if you have selected IPv4).
Ensure the LAN cable is connected to the 2. LAN1 port.
Connect the supplied serial cable from the 1. DATA port on the VCS to the COM port on a PC.
The IP default gateway of the system. e.
Turn on the power switch on the back right 3. of the unit (adjacent to the power cable).
The f. ethernet speed.
a • command line interface via SSH or Telnet.
Whether you want to use SSH to g.
Start a terminal emulator program on the 2. PC and configure it to use the DATA port as follows:
Press the soft power button on the back left 4. of the unit.
administer the system.
We recommend that you now configure the following:
Whether you want to use Telnet to h.
The system name of the VCS. This is used by • the TANDBERG Management Suite (TMS) to identify the system. See About the System Name for more information.
The system will power up. Wait until:
administer the system.
the green PWR LED on the front of the unit • is a steady green color (it may flash briefly during power up).
Once the wizard is finished you will be 7. prompted to log in again. Login with the username admin and your new password.
Automatic discovery. If you have multiple • VCSs in the same network you may want to disable automatic discovery on some of them. See Auto Discover for more information.
the red ALM LED on the front of the unit has • gone out.
You will again get the install wizard prompt; 8. this time select n and press Enter in order to skip the wizard.
the IP address is showing in the display • panel on the front of the unit.
A welcome message similar to the following will appear:
The terminal emulator program will display start up information.
You now must set the system's IP address, subnet mask and default gateway before the system can be used. Consult your network administrator for information on which addresses to use. Note that the VCS must use a static IP address.
The DNS server address (if URI dialing • or FQDNs are to be used). See DNS configuration for more information.
After approximately 2 minutes you will get the login prompt (if the unit is already on, press Enter to get the login prompt):
TANDBERG Video Communication Server Release X2.0
tandberg login:
Enter the username 4. admin and press Enter. You will get the password prompt: Password:
The initial configuration can be done:
by connecting from a PC to the VCS • via a serial cable
You must now reboot the system in order 9. for the new settings take effect. To do this, type the command:
Enter the default password of 5. TANDBERG and press Enter.
xCommand boot •
if your network is set up to allow it, by • connecting via a web browser to the default IP address of 192.168.0.100.
You will get the install wizard prompt:
Run install wizard [n]:
Type y and press Enter.
Follow the prompts given by the install 6. wizard to specify the following:
The IP configuration made via the serial cable applies to the LAN 1 ethernet port only. If you have enabled the LAN 2 port (by installing the Dual Network Interfaces option key) you must use the web interface or CLI to configure the LAN 2 settings.
Do not leave a terminal emulator session open once it is no longer in use. An open session may cause issues during a system restart.
If the red ALM LED flashes rapidly it indicates a hardware fault. Contact your local TANDBERG representative.
The password you want to use for your a.
system. See Administrator Account Password for details.
The yellow HDD LED indicates disk activity and may flicker during normal operation, more so on a busy system.
Whether you wish to use IPv4 or IPv6. b.
See IP Protocol for details.
Welcome to

The LCD panel makes it possible to configure and check the IP settings as well as to reboot the system.
Press ENTER to produce the Main Menu. Use UP/DOWN to navigate to the IP Settings submenu.
Press ENTER to access the IP Settings submenu. Use the UP/DOWN keys to navigate to IP Address and press ENTER to select this option.
By default, during normal operation the front panel will show the system name (if configured) and the LAN 1 IPv4 Address.
To access the front panel menu options, press ENTER.
Press ENTER again to produce the cursor. Use the up/down keys to move left and right between the digits of the number. When you reach a digit you wish to change, press ENTER.
The front panel LCD menu items are as follows:
IP Address IP Default GW IP Netmask
Use UP/DOWN to increase or decrease the digit value. Press ENTER to select the amended digit.
To amend the remaining digits, either press ENTER to move to the right, or ESC followed by UP/DOWN to move to the left.
When you have finished editing press ESC twice to go to the Confirm change menu.
Use the UP/DOWN key to select yes or no followed by ENTER to confirm. Use ESC key to navigate back to the main menu. Repeat the process, selecting IP Default GW to configure the default gateway and IP Netmask for the subnet mask.
The steps opposite give an example of how to use the front panel, in this case to configure the LAN 1 IPv4 address. Use the same procedure to configure the system's LAN 1 IPv4 subnet mask and IPv4 default gateway.
The IPv4 address and IPv4 subnet mask configuration made via the front panel applies to the LAN 1 ethernet port only. To configure the system's IPv6 settings and (if you have the Dual Network Interfaces option key installed) the LAN 2 settings, you must use the web interface or CLI.
DOWN key ESC key

About Administrator Access
Administrator Account Password
Administrator Session Timeout
While it is possible to administer the TANDBERG VCS via a PC connected directly to the unit via a serial cable, you may wish to access the system remotely over IP.
All administration requires you to log in to the administration account with the username admin (all lower case) and a password. Both the username and password are case-sensitive.
By default, Administrator sessions do not time out – they remain active until you logout.
However, you can set the system to timeout an Administrator session after a set number of minutes of inactivity. The timeout period will apply to Administrator sessions using both the Web Interface and the Command Line Interface.
You can do this using either or both:
The default password is TANDBERG (all upper case). You should change this as soon as possible. Choose a strong password, particularly if administration over IP is enabled.
a • command line interface via SSH or Telnet.
To set the timeout period:
By default, access via HTTPS and SSH is enabled; access via Telnet is disabled.
System Configuration > System • . You will be taken to the System Administration page. In the Admin Access section, in the Session time out (minutes) box, enter the number of minutes of inactivity after which an administrator session should time out.
You can also enable access via HTTP. However, this mode works by redirecting HTTP calls to the HTTPS port, so HTTPS must be enabled for access via HTTP.
Changing the Administrator Password
To change the administrator password:
Maintenance > Passwords. • You will be taken to the Passwords page. In the Administrator Password section, enter and then retype the new password. To set an empty password via the web UI, tick the Delete password box.
Tandberg Management Suite (TMS) accesses the VCS via the web server. If HTTPS mode is turned off, TMS will not be able to access it.
Values must be between 0 and 10,000. A value of 0 means that Administrator sessions will never time out.
xConfiguration SystemUnit Passwor • d To set an empty password via the CLI, type: xConfiguration SystemUnit Password: ""
It is possible to have more than one Administrator session running at the same time. These sessions could be via the web interface, command line interface, or a mixture of both. This may cause issues if each Administrator session is attempting to make the same configuration changes.
To securely manage the VCS you should disable Telnet, using the encrypted HTTPS and SSH protocols instead.
For further security, disable HTTPS and SSH as well and use the serial port to manage the system.
Resetting the Administrator Password
If you forget your password, it is possible to set a new password using the following procedure:
Connect a PC to the VCS using the serial cable as per the 1. instructions in steps 1 and 2 of Initial Configuration via Serial Cable.
Because access to the serial port allows the password to be reset, it is recommended that you install the VCS in a physically secure environment.
To configure the ways in which your system is accessed:
System Configuration > System • . You will be taken to the System Administration page. In the Admin Access section, select Off or On from the drop- down boxes for each service.
Reboot the VCS. 2.
Login from the PC with the username 3. pwrec. No password is required.
xConfiguration Administratio • n
The VCS provides a root account with the same password as the admin account. This 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.
You will be prompted for a new password. 4.
You must restart the system for any changes to the Administrator settings to take effect.
The pwrec account is only active for one minute following a restart. Beyond that time you will have to restart the system again to change the password.
Default Administrator Password

Using the Web Interface
To use the web interface:
Open a browser window and in the address line type either: 1.
Enter the Username 3. admin and your system password and select Login.
You will be presented with the Overview page.
The VCS web interface is designed for use with Internet Explorer (6 and up) or Firefox (1.5 and up). It may work with Opera and Safari, but you may encounter unexpected behavior.
Javascript and cookies must be enabled to use the VCS web interface.
In this Administrator Guide, instructions for performing a task via the web interface are shown in the format:
Menu option1 > Menu option2 • followed by the Name of the page that you will be taken to in order to perform the task. In most cases the page will be shown adjacent with callouts describing each of the configurable options.

General page features
Page name and Location
These are the features that can be found on some or all of the web UI pages.
Every page shows the page name and the menu path that you took to get there. Each part of the menu path is a link; clicking on any of the higher level menu items will take you to that page.
This icon appears on the top right corner of every page when there is a system warning in place. Clicking on this icon will take you to the Warning page which will provide you with information about the warning and its suggested resolution.
The VCS provides you with feedback in certain situations, for example when settings have been saved or when you need to take further action. This feedback is given in a yellow information bar along the top of the page.
This icon appears on the top right corner of every page. Clicking on this icon will end your Administrator session. You will be taken to the Administrator Login page.
Click on column headings to sort the information in ascending and descending order.
This icon appears on the top right corner of every page. Clicking on this icon will take you directly to the latest version of the VCS Administrator Guide on the TANDBERG website.
Select All and Unselect All
Use these buttons to select and unselect all items in the list.
A yellow information box will appear on the configuration pages whenever you either click on the 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.
On configuration pages, this section shows you the current status of the items you are configuring.
To close the information box, click on the X at its top right corner.
Each page will always show the system name (or LAN 1 IPv4 address if no system name is configured) at the bottom left corner, and the hardware serial number and VCS software version at the bottom right corner.
This icon appears to the right of most input fields in the web interface.
Clicking on this icon will activate the Information Box.

Using the Command Line Interface (CLI)
How Command are Shown in this Guide
The command line interface is available over SSH, Telnet and through the serial port.
In this Guide, instructions for performing a task using the command line interface (CLI) are shown in the format:
To use the command line interface:
Start a SSH or Telnet session. 1.
Enter the IP address or FQDN of the VCS. 2.
These are meant as a reference only. Each command is hyperlinked to the Command Reference table at the back of this Guide; clicking on the hyperlink will take you to the appropriate section of the table showing all the available sub-elements, parameters and valuespaces for the given command.
Login with a username of 3. admin and your system password.
You will see a screen similar to that shown on the right. You are now ready to start using the CLI by typing the appropriate commands.
Typing the given • xConfiguration path into the CLI will return a list of values currently configured for that element (and sub- elements where applicable).
Commands are divided into different groups according to their function:
Typing the given • xConfiguration path into the CLI followed by a ? will return information about the usage for that element and sub-elements.
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.
Typing the given • xCommand command into the CLI with or without a ? will return information about the usage of that command.
xConfiguration These commands allow you to add and edit single items of data such as IP address and zones.
xCommand These commands allow you to add and configure items and obtain information.
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.
See the Command Reference Appendix for a full description of commands available on the VCS.
Types of Commands


This section describes the information that appears on the Overview page and all the pages under the Status menu of the web interface.
These pages provide information on the current status and configuration of the VCS.

The Overview page summarizes the current configuration and status of your VCS.
The maximum number of calls and registrations, and the availability of additional VCS features such as User Policy and Dual Network Interfaces, are controlled through the use of Option Keys. This section shows all the Options that are currently installed on the VCS.
The Overview page opens automatically when you first log on to the web interface.
You can also access it at any time by clicking on the Overview menu at the top left of any page.
Current: The number of traversal calls going through the VCS at this moment.
The name that has been assigned to the VCS.
Max (peak): The highest number of concurrent traversal calls handled by the VCS since it was last restarted.
The amount of time that has elapsed since the system last restarted.
Total: The total number of traversal calls handled by the VCS since it was last restarted.
See the section Traversal Calls for details on what constitutes a traversal call.
The version of software that is currently installed on the VCS.
Current: The number of non-traversal calls going through the VCS at this moment.
The VCS’s IPv4 address(es).
Max (peak): The highest number of concurrent non-traversal calls handled by the VCS since it was last restarted.
Total: The total number of non-traversal calls handled by the VCS since it was last restarted.
The VCS’s IPv6 address(es).
Many of the items on this page are configurable, and contain links to the page where they can be configured. For example, clicking on System name will take you to the System Administration page, from where you can configure the system name.
Current: The number of endpoints registered to the VCS at this moment.
Max (peak): The highest number of endpoints concurrently registered to the VCS since it was last restarted.
Total: The total number of registrations on the VCS since it was last restarted.

Understanding the System Information Page
The System Information page provides details of the software, hardware, and time settings of the VCS.
The name that has been assigned to the VCS.
To view the System Information page:
This will be TANDBERG VCS.
The amount of time that has elapsed since the system last restarted.
The version of software that is currently installed on the VCS.
The time as determined by the NTP server.
The build number of this software version.
If no NTP server has been configured, this will show Time Not Set.
The date on which this version of the software was released.
The time zone that has been configured on the NTP page.
The internal TANDBERG reference number for this software release.
If an NTP server has been configured, this will be a combination of the NTP server time (which is UTC) and the local time zone.
All the extra features installed on the VCS via option keys.
If no NTP server has been configured, this will show the time according to the VCS’s operating system.
The version number of the hardware on which the VCS software is installed.
Some of the items on this page are configurable, and contain links to the page where they can be configured. For example, clicking on Software Options will take you to the Option Keys page, from where you can install new optional features.
The serial number of the hardware on which the VCS software is installed.


The Ethernet page provides details of the MAC address and ethernet speed settings of the VCS.
If the Dual Network Interfaces option key has been installed, this will show the MAC addresses of the ethernet cards for both the LAN1 port and the LAN2 port.
The speed of the connection between the VCS and the ethernet switch.
If the Dual Network Interfaces option key has been installed, this will show the ethernet speed for both the LAN1 port and the LAN2 port.

Understanding the IP Status Page
The IP Status page provides details of the IP and DNS settings of the VCS.
The IPv4 gateway used by VCS.
To view the IP Status page:
Indicates the IP protocol supported by the VCS.
The IPv6 gateway used by VCS.
IPv4: The VCS will only accept registrations from endpoints using an IPv4 address, and will only take calls between two endpoints or devices communicating via IPv4. It will communicate with other systems via IPv4 only.
The IPv4 address configured on the VCS.
IPv6: The VCS will only accept registrations from endpoints using an IPv6 address, and will only take calls between two endpoints communicating via IPv6. It will communicate with other systems via IPv6 only.
If the Dual Network Interfaces option key has been installed, this will show the IPv4 addresses for both the LAN1 port and the LAN2 port.
Both: The VCS will accept registrations from endpoints using either an IPv4 or IPv6 address, and will take calls using either protocol. If a call is between an IPv4-only and an IPv6-only endpoint, the VCS will act as an IPv4 to IPv6 gateway (note that this will require a traversal call licence). The VCS can communicate with other systems via either protocol.
The IPv4 subnet mask configured on the VCS.
If the Dual Network Interfaces option key has been installed, this will show the IPv4 subnet masks for both the LAN1 port and the LAN2 port.
Server 1..5 address
The IP address(es) of each of the DNS servers that will be queried when resolving domain names. Up to 5 DNS servers may be configured.
The IPv6 address configured on the VCS.
If the Dual Network Interfaces option key has been installed, this will show the IPv6 addresses for both the LAN1 port and the LAN2 port.
Specifies the name to be appended to the host name before a query to the DNS server is executed.

Understanding the Resource Usage Page
The Resource Usage page provides statistics about the numbers of current and cumulative calls and registrations on the VCS. This page automatically refreshes every 5 seconds.
Current: The number of traversal calls going through the VCS at this moment.
Max (peak): The highest number of concurrent traversal calls handled by the VCS since it was last restarted.
To view the Resource Usage page:
Total: The total number of traversal calls handled by the VCS since it was last restarted.
Current: The number of non-traversal calls going through the VCS at this moment.
Max (peak): The highest number of concurrent non-traversal calls handled by the VCS since it was last restarted.
Total: The total number of non-traversal calls handled by the VCS since it was last restarted.
Current: The number of devices registered to the VCS at this moment.
Max (peak): The highest number of devices concurrently registered to the VCS since it was last restarted.
Total: The total number of registrations on the VCS since it was last restarted.
Traversal calls · Non-traversal calls · Registrations

Understanding the Registrations Page
The Registrations page lists all the devices that are currently registered with the VCS.
The H.323 alias or SIP AOR that the device registered.
Devices that are configured for both SIP and H.323 will register twice; once as an H.323 endpoint and once as a SIP UA.
Clicking on an individual name will take you to the Registrations Details page for that registration.
To view the Registrations page:
Indicates the nature of the registration. This will most commonly be Endpoint, Gateway, or SIP UA.
Click here to remove the selected registrations.
For H.323 devices, this is the RAS address.
For SIP UAs it is the Contact address presented in the REGISTER request.
The date and time at which the registration was accepted.
To limit the list of registrations, enter one or more characters in the Filter field and select Filter. Only those registrations that contain (in any of the displayed fields) the string you entered will be shown.
If an NTP server has not been configured, this will say Time not set.
To return to the full list of registrations, click Reset.
Whether the registration is for a SIP or H.323 device.

Understanding the Registration History Page
The Registration History page lists all the registrations that are no longer current. It lists the most recent historical registrations since the last reboot, up to a maximum of 255.
The H.323 alias or SIP AOR that the device registered.
Clicking on an individual name will take you to the Registrations Details page for that registration.
To view the Registration History page:
Indicates the nature of the registration. This will most commonly be Endpoint, Gateway, or SIP UA.
Whether the registration was for a SIP or H.323 device.
The reason why the registration was terminated.
The length of time that the registration was in place.
The date and time at which the registration was terminated.
To limit the list of registrations, enter one or more characters in the Filter field and select Filter. Only those registrations that contain (in any of the displayed fields) the string you entered will be shown.
To return to the full list of registrations, click Reset.
The date and time at which the registration was accepted.
If an NTP server has not been configured, this will say Time not set.

Understanding the Calls Page
The Calls page lists all the calls currently taking place to or from devices registered with the VCS, or that are passing through the VCS.
The date and time at which the call was placed.
To view the Calls page:
The alias of the device that placed the call.
Click here to disconnect the selected calls.
The alias to which the call was placed.
Call disconnection works differently for H.323 and SIP calls due to differences in the way the protocols work.
This may be different from the alias that was actually dialed from the device, as it may have been transformed either locally or before the neighbor was queried.
For H.323 calls, and interworked H.323 to SIP calls, the Disconnect command will actually disconnect the call.
For 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.
Click View to go to the Call Details page which lists full details of this call.
Shows whether the call used H.323, SIP, or both protocols.
The subzone or zone from which the call was received and the subzone or zone to which the call was placed.
Intermediary subzones are not shown here. To see the complete route within the VCS that the call took, click on View to go to the Call Details page.
To limit the list of calls, enter one or more characters in the Filter field and select Filter. Only those calls that contain (in any of the displayed fields) the characters you entered will be shown.
The amount of bandwidth allocated to this call.
To return to the full list of calls, click Reset.

Understanding the Call History Page
The Call History page lists all the calls that are no longer active that have taken place since the VCS was last restarted.
The date and time at which the call was placed.
To view the Call History page:
The alias of the device that placed the call.
The alias to which the call was placed.
This may be different to the alias that was actually dialled from the endpoint, as it may have been transformed either locally or before the neighbor was queried.
Click View to go to the Call Details page which lists full details of this call.
The reason the call was terminated.
The length of time of the call.
To limit the list of calls, enter one or more characters in the Filter field and select Filter. Only those calls that contain (in any of the displayed fields) the characters you entered will be shown.
To return to the full list of calls, click Reset.
Shows whether the call used H.323, SIP, or both protocols.

Understanding the Search History Page
The Search History page lists all the searches that have taken place since the VCS was last restarted.
The date and time at which the search was initiated.
To view the Search History page:
The type of message being sent.
Click View to go to the Search Details page which lists full details of this call.
For H.323, two messages are sent for every call that is placed locally: 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 will be associated with a particular call.
Indicates whether or not the search was successful.
True: the search was successful.
False: the search was unsuccessful.
For SIP, a single message is sent in order to place a call: this is the SIP INVITE.
The alias that was dialled 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.
To limit the list of calls, enter one or more characters in the Filter field and select Filter. Only those calls that contain (in any of the displayed fields) the characters you entered will be shown.
The alias of the endpoint that initiated the call.
To return to the full list of calls, click Reset.

Understanding the Local Zone Page
The Local Zone page lists all the subzones that together make up the Local Zone. This will always include the Default Subzone and the Traversal Subzone, plus any other subzones that you have created.
The names of each subzone currently configured on this VCS.
To view the Local Zone page:
The number of devices currently registered within each subzone.
The total amount of bandwidth used by all calls passing through each subzone.
The number of calls currently passing through each subzone.
Each subzone name is also a link to the configuration page for that subzone. To configure the subzone, click on the subzone name.

Understanding the Zones Page
The Zones status page lists all the zones that are currently configured on your VCS, the number of calls and amount of bandwidth being used by each, and their current status.
The names of each zone currently configured on this VCS.
The list of zones will always include the Default Zone, plus any other zones that you have created.
To view the Zones page:
The type of zone.
See About Zones for a full description of each zone type.
The number of calls currently passing out to or received in from each zone.
The current status of each zone.
The total amount of bandwidth used by all calls passing out to or received in from each zone.
Each zone name is also a link to the configuration page for that zone. To configure the zone, click on the zone name. Note that this does not apply to the Default Zone, as this is not configurable.


The Links status page gives you an overview of all the links currently configured on your VCS, along with the number of calls and the bandwidth being used by each link.
The total number of calls currently traversing each link. Note that a single call may traverse more than one link, depending on how your system is configured.
The total bandwidth of all the calls currently traversing each link.
Each link name is also a hyperlink to the configuration page for that link. To configure the link, click on the link name.


The Pipes page provides a list of all the pipes currently configured on your VCS, along with the number of calls and the bandwidth being used by each pipe.
Clicking on the name will take you to the Edit Pipe page, where you can configure the pipe.
The total bandwidth of all the calls currently traversing each pipe.
Each pipe name is also a link to the configuration page for that pipe. To configure the pipe, click on the pipe name.


The STUN Relays page provides a list of all the currently active STUN Relays on the VCS. For each Relay, it shows the requesting client address and port and the corresponding VCS address and port.
The IP address and port on the NAT (or the client if there is no NAT) from which the STUN Relay request has come.
The IP address and port on the VCS that has been allocated for this particular relay request.
The date and time at which the STUN Relay will become inactive.
The date and time on which the STUN Relay became active.


The Warnings page provides a list of all the warnings currently in place on your system.
Each warning, and where relevant its proposed resolution, is listed here.
When there are warnings in place on the VCS, a warning icon
will appear at the top right of the page.

The Event Log page allows you to view and search the event log, which is a list of all the events that have occurred on your system since the last upgrade. The event log holds a maximum 100 MB of data.
This field allows you to filter the event log. Enter the text you wish to search for and click Filter. Only those events that contain the text you entered will then be shown.
To view the Event Log page:
Status > Event Log • You can also view the Event Log via the CLI:
To return to the complete Event Log listing, click Reset.
Reconfigure Event Log settings
Clicking this link will take you to the Logging configuration page. From this page, you can determine 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.
Certain events in the Event Log are color-coded so that you can identify them more easily, These events are as follows:
This section shows all the events, with the most recent being shown first.
Most tvcs events contain hyperlinks in one or more of the fields. 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= will filter the list to show all the events of that particular type. Likewise, clicking on a particular Call-Id will show just those events that contain a reference to that particular call.
Search for · Results


The event log is displayed in an extension of the UNIX syslog format:
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 will be tvcs for all messages originating from TANDBERG VCS processes, but will differ for messages from third party processes which are used in the VCS product
message _ details the body of the message (see Message details field for further information)

The first field within the message _ details field is always Event and the last field is always Level.
In addition to the events described below, a syslog.info event containing the string MARK will be logged after each hour of inactivity to provide confirmation that logging is still active.
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 table below shows all the possible fields within the message _ details field, in the order that they would normally appear, along with a description of each.
Event The event which caused the log message to be generated. See Events Logged at Level 1, Events Logged at Level 2 and Events Logged at Level 3 for lists of all events that are logged by the VCS.
Dst-port Specifies the destination port: the IP port of the destination for a communication attempt.
Src-port Specifies the source port: the IP port of the device attempting to establish communications.
User The username that was entered when a login attempt was made.
Protocol Specifies which protocol was used for the communication.
Src-Alias If present, the first H.323 Alias associated with the originator of the message.
Valid values are:
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.
Auth Whether call attempt has been authenticated successfully.
Method SIP method (INVITE, BYE, UPDATE, REGISTER, SUBSCRIBE, etc).
Service Specifies which protocol was used for the communication.
Contact Contact: header from REGISTER.
A service entry is one of:
AOR Address of record.
Call-Id The Call-ID header field uniquely identifies a particular invitation or all registrations of a particular client.
To (for REGISTER requests): the AOR for the REGISTER request.
RequestURI The SIP or SIPS URI indicating the user or service to which this request is being addressed.
NumBytes The number of bytes sent/received in the message.
ResponseCode SIP response code.
Duration Request/granted registration expiry duration.
Src-ip Specifies the source IP address (the IP address of the device attempting to establish communications). This can be an IPv4 address or an IPv6 address.
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.
Dst-ip Specifies the destination IP address (the IP address of the destination for a communication attempt).
Level The level of the event as defined in Event Log Levels.
The destination IP is recorded in the same format as Src-ip.
Field Description · Field Description

Admin Session Finish An administrator has logged off the system.
Admin Session Login Failure An unsuccessful attempt has been made to log in as an administrator. This could be because either the username “admin” was not used, or an incorrect password was entered (or both).
Admin Session Start An administrator has logged onto the system.
Application Failed The VCS application is out of service due to an unexpected failure.
Application Start The VCS has started.
Further detail may be provided in the event data Detail field.
Call Answer Attempted An attempt to answer a call has been made.
Call Attempted A call has been attempted.
Call Bandwidth Changed The bandwidth of a call has changed.
Call Connected A call has been connected.
Call Disconnected A call has been disconnected.
Call Rejected A call has been rejected.
The Reason event parameter contains a textual representation of the H.225 additional cause code.
Decode Error A syntax error was encountered when decoding a SIP or H.323 message.
Eventlog Cleared An operator cleared the event log.
External Server Communication Failure
Communication with an external server failed unexpectedly. The event detail data should differentiate between ‘no response’ and ‘request rejected’.
Servers concerned are:
License Limit Reached Licensing limits for a given feature have been reached.
The event detail field specifies the facility/limits concerned. Possible values for the detail field are:
Event Description

Policy Change A policy file has been updated.
System Configuration Changed An item of configuration on the system has changed.
The Detail event parameter contains the name of the changed configuration item and its new value.
Registration Accepted A registration request has been accepted.
Registration Refresh Rejected A request to refresh a registration has been rejected.
Registration Rejected A registration request has been rejected.
The Reason event parameter contains the H.225 cause code. Optionally, the Detail event parameter may contain a textual representation of the H.225 additional cause code.
Registration Removed A registration has been removed by the VCS.
The Reason event parameter specifies the reason why the registration was removed. This is one of:
System Shutdown The operating system was shutdown.
System Start The operating system has started.
TLS Negotiation Error Transport Layer Security (TLS) connection failed to negotiate.
Unregistration Accepted An unregistration request has been accepted.
Unregistration Rejected An unregistration request has been rejected.
Unregistration Requested An unregistration request has been received.
User session finish A FindMe user has logged out of the system.
User session Login failure An unsuccessful attempt has been made to log in as a FindMe user. This could be because either an incorrect username or password (or both) was entered.
User session start A FindMe user has logged on to the system.
Event Description


Message Received (H.323) An incoming message has been received.
Message Sent (H.323) An outgoing message has been sent.
Registration Refresh Accepted A request to refresh a SIP registration has been accepted.
Registration Refresh Request A request to refresh a SIP registration has been received.
Keepalive Registration Accepted A keepalive RRQ (requesting that an existing H.323 registration is refreshed) has been accepted.
Keepalive Registration Requested A keepalive RRQ (requesting that an existing H.323 registration is refreshed) has been received.
Message Received (SIP) An incoming message has been received.
Message Sent (SIP) An outgoing message has been sent.


This section describes all the options that appear under the System Configuration 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 and the external services used by the VCS (e.g. DNS, NTP and SNMP).

Configuration
To configure the VCS’s system administration settings:
Defines the name of the VCS. Choose a name that uniquely identifies the system.
System Configuration > System • . You will be taken to the System Administration page.
Session time out (minutes)
Sets the number of minutes that an administration session (HTTPS, Telnet or SSH) may be inactive before the session is timed out. A value of 0 turns session time outs off.
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 TANDBERG’s TMS.
Determines whether the VCS can be accessed via Telnet.
If no system name is specified, the LAN1 IPv4 address will be shown instead.
Determines whether the VCS can be accessed via SSH and SCP.
We recommend that you give the VCS a name that allows you to easily and uniquely identify it.
On: HTTP calls will be redirected to the HTTPS port.
Off: no HTTP access will be available.
While it is possible to administer the TANDBERG VCS via a PC connected directly to the unit via a serial cable, you may wish to access the system remotely over IP.
Determines whether the VCS can be accessed via the web server. This must be On to enable both web interface and TMS access.
You can do this using either or both:
a • command line interface via SSH or Telnet.
By default, access via HTTPS and SSH is enabled; access via Telnet is disabled. To securely manage the VCS you should disable Telnet, using the encrypted HTTPS and SSH protocols instead. For further security, disable HTTPS and SSH as well and use the serial port to manage the system.
By default, access via HTTPS and SSH is enabled; access via Telnet is disabled.
Click here to save your changes.
Click here to restart the system.
You can also enable access via HTTP. However, this mode works by redirecting HTTP calls to the HTTPS port, so HTTPS must also be enabled for access via HTTP to function.
You must save your changes and restart the system for any changes made via this page to take effect.
TMS accesses the VCS via the web server. If HTTPS mode is turned off, TMS will not be able to access it.

To configure the VCS’s Ethernet settings:
System Configuration >Ethernet • . You will be taken to the Ethernet page.
Sets the speed of the connection between the VCS and the ethernet switch.
If you have the Dual Network Interfaces option key installed, you will be able to configure this for both LAN1 and LAN2.
The Ethernet speed setting determines the speed of the connection between the VCS and the ethernet switch. It must be set to the same value on both systems.
The default is Auto, which means that the two systems will auto-negotiate the appropriate speed.
We recommend that you do not change from the default value of Auto unless the switch to which you are connecting is unable to auto-negotiate. A mismatch in Ethernet speed settings between the VCS and ethernet switch will at best result in packet loss; at worst it will make the system inaccessible for endpoints and system administrators.
You must save your changes and restart the system for changes made via this page to take effect.
Click here to restart the system.
Click here to save your changes.
Ethernet speed · Restart · Save

To configure the VCS’s IP settings:
System Configuration > IP • . You will be taken to the IP page.
You can configure the VCS to use IPv4, IPv6 or Both protocols. The default is Both.
IPv4: The VCS will only accept registrations from endpoints using an IPv4 address, and will only take calls between two endpoints communicating via IPv4. It will communicate with other systems via IPv4 only.
IPv6: The VCS will only accept registrations from endpoints using an IPv6 address, and will only take calls between two endpoints communicating via IPv6. It will communicate with other systems via IPv6 only.
The VCS can act as a gateway between IPv4 and IPv6 calls. To enable this feature, select an IP Protocol of Both.
Some endpoints support both IPv4 and IPv6, however an endpoint can use only one protocol when registering with the VCS. Which protocol it uses will be determined by the format used to specify the IP address of the VCS on the endpoint. Once the endpoint has registered using one protocol, calls to it from an endpoint using the other protocol will be gatewayed by the VCS.
Both: The VCS will accept registrations from endpoints using either an IPv4 or IPv6 address, and will take calls using either protocol. If a call is between an IPv4-only and an IPv6-only endpoint, the VCS will act as an IPv4 to IPv6 gateway. It can communicate with other systems via either protocol.
Specifies the default IPv4 gateway of the VCS.
The options on this page allow you to set the default IPv4 and IPv6 gateways used by the VCS. This is the gateway to which IP requests are sent for IP addresses that do not fall within the VCS’s local subnet. However, you can also configure additional IP routing information on the VCS. This is sometimes required when using the Dual Network Interfaces option and occasionally required in other complex network deployments. You can configure routes for up to 10 networks and host combinations.
Specifies the default IPv6 gateway of the VCS.
You must save your changes and restart the system for changes to take effect.
Click here to restart the system.
The VCS cannot act as an IPv4 to IPv6 gateway at the same time as it is acting as a SIP to H.323 gateway.
Calls for which the VCS is acting as an IPv4 to IPv6 gateway are traversal calls. They will therefore require a traversal call licence.
IP routes are configured via the CLI only using:
Click here to save your changes.

To configure the VCS’s LAN 1 and LAN 2 ethernet port settings:
Specifies the IPv4 IP address of the VCS’s LAN1 port..
System Configuration > IP • . You will be taken to the IP page.
The VCS is shipped with a default IP address for LAN 1 of 192.168.0.100. This allows you to connect the VCS to your network and access it via the default address so that you can configure it remotely.
Specifies the IPv4 subnet mask of the VCS’s LAN1 port.
Specifies the IPv6 gateway of the VCS’s LAN1 port.
LAN 1 is the primary network port on the VCS. You can configure the IPv4 address and subnet mask, and IPv6 address for this port.
In addition, if you have the Dual Network Interface option key installed, you will also be able to configure the LAN 2 port.
If you have the Dual Network Interfaces option key installed, you will also be able to configure the IPv4 address, IPv4 subnet mask and IPv6 address for the LAN2 port via this page.
The Dual Network Interface option enables the LAN 2 port on the VCS for both management and call signaling. This allows you to have a secondary IP address for your VCS.
This configuration is intended for high-security deployments where the VCS 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.
Click here to restart the system.
Click here to save your changes.
You must save your changes and restart the system for changes to take effect.

About DNS Servers
To configure the VCS’s DNS settings:
System Configuration > DNS • . You will be taken to the DNS page.
You must specify at least one DNS server to be queried for address resolution if you wish to either:
use FQDNs (Fully Qualified Domain Names) instead of IP • addresses when specifying external addresses (for example for LDAP and NTP servers, neighbor zones and alternates), or
Address 1 to Address 5
Sets the IP address of a DNS server to be queried when resolving domain names.
You can specify up to 5 DNS servers. The VCS sends requests to all configured servers in parallel taking the first result received and discounting the rest.
This can lead to confusing behavior should local network administrators, for example, deploy ‘split horizon’ DNS where records held on an internal, corporate, DNS server use the same domain names but with different values to those on the public internet - an often used tactic in corporate intranets.
The DNS Domain Name is used when attempting to resolve server addresses configured on the VCS that are without any form of qualification (e.g. ldap or ldap_server but not ldap.server). It applies only to the following:
Specifies the name to be appended to an unqualified server address before a query to the DNS server is executed.
If the server address is an IP address or is in the format of a domain name, DNS will only be queried for the server address as configured, without the DNS Domain Name appended. For this reason we recommend that all server addresses use an IP address or FQDN (Fully Qualified Domain Name).
Click here to save your changes.
The DNS Domain name plays no part in URI dialing.
Domain name · Save

To configure the VCS’s NTP settings:
System Configuration > NTP • You will be taken to the NTP page.
Sets the IP address or FQDN of the NTP server to be used when synchronizing system time.
xConfiguration TimeZone Nam • e
The NTP server is a remote server with which the VCS synchronizes in order to ensure its time setting is accurate. The NTP server provides the VCS with UTC time.
Accurate timestamps play an important part in authentication, helping to guard against replay attacks. For this reason, if you are using authentication, both the VCS and the endpoints must use an NTP server to synchronize their system time.
Traversal clients must always authenticate with traversal servers, even if the server’s authentication mode is off (this setting applies to endpoint authentication only). Therefore in order for a traversal client and traversal server to connect to each other, both must be configured with details of an NTP server.
Sets the local time zone of the VCS.
The NTP server provides the VCS with UTC time. You can also determine the local time to be used on your system by configuring the Time Zone. This takes the UTC time and offsets it by the number of hours specified by the selected time zone to make the local time.
The local time is used throughout the web UI and to set the timestamp that appears at the start of each line in the Event Log.
Click here to save your changes.
NTP server · Time zone · Save

To configure the VCS’s SNMP settings:
System Configuration > SNMP • You will be taken to the SNMP page.
Select On to enable SNMP support.
You must save your changes and restart the system for any changes to take effect.
Tools such as TANDBERG Management Suite (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.
Sets the VCS’s SNMP community name.
The VCS offers basic support for SNMP, and supports Version 1 and Version 2c of the SNMP protocol. The information provided by the VCS is defined by SNMP MIB-2 and is:
Specifies the name of the person who can be contacted regarding issues with the VCS.
Specifies the physical location of the VCS.
By default, SNMP is Enabled with a SNMP community name of public.
Click here to restart the system.
Click here to save your changes.

To configure the VCS’s External Manager settings:
Sets the IP address or FQDN of the External Manager.
System Configuration > External Manager • . You will be taken to the External Manager page.
An External Manager is a remote system, such as the TANDBERG Management Suite (TMS), used to monitor events occurring on the VCS, for example call attempts, connections and disconnections.
Sets the path of the External Manager.
The use of an External Manager is optional.
In order to use an External Manager, you must configure the VCS with the IP address or host name and path of the External Manager to be used.
If you are using TMS as your external manager, use the default path of tms/public/external/management/ SystemManagementService.asmx.
Click here to save your changes.
Address · Path · Save


You are recommended to maintain a backup of your VCS configuration. To do this:
Use the command line interface to log on to the VCS. 1.
Save the resulting output to a file, using cut-and-paste or some other means provided by your 3. terminal emulator.
Remove the 1. *c from in front of each command.
Paste this information back in to the command line interface. 2.

Remote Logging
About Logging
About Remote Logging
Enabling Remote Logging
The VCS provides an event logging facility for troubleshooting and auditing purposes. The event log records information about such things as calls, registrations, and messages sent and received.
The event log is always stored locally on the VCS. However, it is often convenient to collect copies of all event logs from various systems in a single location. A computer running a BSD-style syslog server, as defined in RFC 3164 [4], may be used as the central log server.
To enable remote logging, you must configure the VCS with the address of the central log server to which the event log will be copied. To do this:
The VCS logging facility allows you to:
A VCS will not act as a central logging server for other systems.
Events will be always logged locally (i.e. to the Event Log) regardless of whether or not remote logging has been enabled.
Enter the IP address or FQDN of the server to which the log will be written.
This server must support the BSD syslog protocol. It cannot be another VCS.
Click here to save your changes.
View the Event Log
Clicking on this link will take you to the Event Log page, which displays the Event Log.
Remote syslog server · Save

About Event Log Levels
Setting the Event Log Level
All events have an associated level in the range 1-3, with level 1 events considered the most important. The table below gives an overview of the levels assigned to different events.
You can control which events are logged by the VCS by setting the log level. All events with a level numerically equal to and lower than the specified logging level are recorded in the event log. So, at Level 1, only Level 1 events are logged; at Level 2, Level 1 and Level 2 events are logged, etc.
See Events Logged at Level 1, Events Logged at Level 2 and Events Logged at Level 3 for complete tables of the events logged at each level.
To set the log level:
System Configuration > Logging • . You will be taken to the Logging page.
High-level events such as registration requests and call attempts. Easily human readable. For example:
Select the level of logging you require.
The default is 1.
All Level 1 Events, plus:
Logs of protocol messages sent and received (H.323, LDAP, etc.) excluding noisy messages such as H.460.18 keepalives and H.245 video fast-updates.
Level 3 (Protocol Verbose)
Protocol keepalives are suppressed at Level 2. At logging Level 3, keepalives are also logged, along with all Level 1 and Level 2 events.
We do not usually recommend logging at Level 3, as the Event Log holds a maximum of 100 MB of data and logging at this level on a busy system could cause the Event Log to be recycled too quickly.
Click here to save your changes.
Changes to the event log level are not retrospective. If you change the event log level, it will only effect what is logged from that point onwards.
View the Event Log
Clicking on this link will take you to the Event Log page, where you can view and search the Event Log.
Changes to the event log level affect both the event log that you can view via the web interface, and the information that is copied to the remote log server (if any) that you have configured.


This section provides information on the pages that appear under the Protocols, Registrations and Authentication sub-menus of the VCS Configuration menu. These pages allow you to configure the functionality of the VCS in each of these areas.
an overview of H.323 and SIP and the configuration options available on the VCS • for each of these protocols

H.323 Endpoint Registration
About H.323 on the VCS
Overview
Auto Discover
The VCS supports the H.323 protocol: it is an H.323 gatekeeper, and will provide interworking between H.323 and SIP calls. In order to support H.323, the H.323 mode must be enabled.
H.323 endpoints in your network must register with the VCS in order to use it as their gatekeeper.
The VCS has an Auto Discover setting which determines whether it will respond to the Gatekeeper Discovery Requests sent out by endpoints.
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).
To prevent H.323 endpoints being able to register automatically with the VCS, set Auto Discover to Off. This will mean that endpoints will be able to register with the VCS only if they have been configured with the VCS’s IP address.
Time to Live
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.
H.323 endpoints must periodically re-register with the VCS in order to confirm that they are still functioning. The VCS allows you to configure the interval between these re-registrations, known as the Time to Live.
Some older endpoints do not support the ability to periodically re-register with the system. In this case, and in any other situation where the system has not had a confirmation from the endpoint within the specified period, it will send an IRQ to the endpoint to verify that it is still functioning.
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. The reasons for this could include:
Call Time to Live
The VCS allows you to configure the listening port for H.323 registrations and call signaling, and the range of ports to be used by H.323 calls once they are established.
Once the endpoint is in a call, the VCS will periodically poll it to confirm whether it is still in the call. If the endpoint does not respond, the call will be disconnected.
The default VCS configuration uses standard port numbers so you can use H.323 services out of the box without having to first set these up.
The VCS allows you to configure the interval at which the endpoints are polled, known as the Call Time to Live.
The system will poll endpoints in a call regardless of whether the call type is traversal or non-traversal.

To configure the VCS’s H.323 settings:
Determines how the system will behave if an endpoint attempts to register an alias currently registered from another IP address.
Reject: denies the registration.
Overwrite: deletes the original registration and replaces it with the new registration.
H.323 Mode
Determines whether or not the VCS will provide H.323 gatekeeper functionality.
The default is Reject.
Specifies the port to be used for H.323 UDP registrations.
The default is 1719.
Specifies the interval (in seconds) at which an H.323 endpoint must re-register with the VCS in order to confirm that it is still functioning.
Call signaling TCP port
Specifies the port that listens for H.323 call signaling.
The default is 1800.
The default is 1720.
Call time to live
Specifies the interval (in seconds) at which the VCS polls the endpoints in a call to verify that they are still in the call
Call signaling port range start
Specifies the lower port in the range to be used by H.323 calls once they are established.
The default is 120.
The default is 15000.
Call signaling port range end
Determines whether or not the VCS responds to gatekeeper discovery requests from endpoints.
Specifies the upper port in the range to be used by H.323 calls once they are established.
The default is 19999.
The default is On.
The call signalling port range must be great enough to support all the required concurrent calls.
Click here to save your changes.

About SIP on the VCS
Using the VCS as a SIP Registrar
SIP Registration Expiry
The VCS supports the SIP protocol: it is both a SIP Proxy and SIP Registrar, and will provide interworking between SIP and H.323 calls. In order to support SIP, SIP mode must be enabled and at least one of the SIP transport protocols (i.e. UDP, TCP or TLS) must be active.
In order for a SIP endpoint to be contactable via its registered alias, it must register its location with a SIP Registrar. The VCS can act as a SIP Registrar for up to 20 domains.
SIP endpoints must periodically re-register with the SIP Registrar in order to prevent their registration expiring. You can configure the interval with which SIP endpoints must register with the VCS.
SIP aliases always take the form username@domain. To enable the VCS to act as a SIP Registrar, you must configure it with the SIP Domain(s) for which it will be authoritative. It will then accept registration requests for any endpoints attempting to register with an alias that includes that domain.
If no Domains are configured, then the VCS will not act as a SIP Registrar.
If the VCS has no domains configured, or it receives a registration request for a domain for which it is not acting as a Registrar, then the VCS may proxy the registration request. This depends on the SIP Registration Proxy Mode setting, as follows;
The SIP Registration Proxy Mode setting also impacts the VCS’s behavior when acting as a SIP Proxy Server.
The SIP Registration Expiry setting applies only when the VCS is acting as a SIP Registrar, and to endpoints registered with the VCS. It does not apply to endpoints whose registrations are being proxied through the VCS.
Proxying Registration Requests

Using the VCS as a SIP Proxy Server
SIP protocols and ports
When SIP mode has been enabled the VCS may act as a SIP Proxy Server. The role of a Proxy Server is to forward requests (such as REGISTER and INVITE) from endpoints or other Proxy Servers. These requests are forwarded on to other Proxy Servers or to the destination endpoint.
The VCS supports SIP over UDP, TCP and TLS transport protocols. You can configure whether or not incoming calls using each protocol are supported, and if so, the ports on which the VCS will listen for such calls. You can also specify the range of ports the VCS will use once calls are established. This range must be sufficient to support all required concurrent calls.
Whether or not the VCS acts as a SIP Proxy Server, and its exact behavior when proxying requests, is determined by the SIP Registration Proxy Mode setting. In addition, this also depends on the presence of Route Set information in the request header and whether or not the Proxy Server from which the request was received is a Neighbor of the VCS.
A Route Set can specify the path that must be taken when requests are being proxied between an endpoint and its Registrar. For example, when a REGISTER request is proxied by a VCS, the VCS adds a Path header component to the request which signals that the VCS must be included on any call to that endpoint. The information is usually required in situations where firewalls exist and the media must follow a specified path in order to successfully traverse the firewall. For more information about the path header field, see RFC 3327 [10].
When the VCS proxies a request that contains existing Route Set information, it will forward it directly to the URI specified in the path. Any call policy configured on the VCS will therefore be bypassed. This may present a security risk if the information in the Route Set cannot be trusted. For this reason, you can configure the VCS with three different behaviors when proxying requests, as follows:
At least one of the UDP, TCP or TLS transport protocols must be set to a Mode of On in order for SIP functionality to be supported.

SIP settings are configured via:
Determines whether or not incoming SIP calls using the UDP protocol will be allowed.
The default is On.
Specifies the listening port for incoming SIP calls over UDP.
Determines whether or not the VCS will provide SIP functionality (i.e. SIP Registrar and SIP proxy services).
The default is 5060.
Specifies the period within which a SIP endpoint must re-register to prevent its registration expiring.
Determines whether or not incoming SIP calls using the TCP protocol will be allowed.
The default is On.
The default is 60.
SIP registration proxy mode
Specifies the listening port for incoming SIP calls over TCP.
Specifies how proxied registrations and invites will be handled.
Off: Registration requests will not be proxied (but will still be permitted locally if the VCS is authoritative for that domain). Invite requests with existing Route Sets will be rejected.
The default is 5060.
Determines whether or not incoming SIP calls using the TLS protocol will be allowed.
Proxy to known only: Registration requests will be proxied, and invite requests will be proxied only if the Route Set contains the URI(s) of neighbors (including traversal clients and traversal servers).
The default is On.
Proxy to any: Registration requests and invite requests will always be proxied.
Specifies the listening port for incoming SIP calls over TLS.
The default is 5061.
TCP Outbound Port Start
TCP Outbound Port End
Specifies the lower port in the range to be used by outbound TCP/TLS SIP connections.
Specifies the upper port in the range to be used by outbound TCP/TLS SIP connections.
Click here to save your changes.
The default is 25000.
The default is 29999.

SIP domains are configured via:
VCS Configuration > Protocols >SIP > • Domains. You will be taken to the Domains page.
Click here to change the domain name or delete the domain.
To add a new domain, click • New. You will be taken to the Create Domain page. Enter the domain in the Name field and click Create Domain. The new domain will be added and you will be returned to the Domains page.
To edit the name of an existing domain, click • View/Edit. You will be taken to the Edit Domain page. Edit the Name of the domain and click Save. The name of the domain will be changed.
Specifies a domain for which the VCS is authoritative.
The VCS will act as a SIP Registrar for this domain, and will accept registration requests for any SIP endpoints attempting to register with an alias that includes this domain.
To delete an existing domain, click • View/ Edit. You will be taken to the Edit Domain page. Click Delete. The domain will be deleted and you will be returned to the Domains page.
To delete one or more existing domains, • select the boxes next to the domains you wish to delete and click Delete.
Click here to return to the Domains page without saving your changes.
xCommand DomainDelet • e
xConfiguration SIP Domain • s
Click here to delete the domain and return to the Domains page.
Click here to save your changes.

About Interworking
Interworking options are configured via:
The VCS is able to act as a gateway between SIP and H.323, translating calls from one protocol to the other. This is known as “interworking”.
By default, the VCS will act as a SIP-H.323 gateway but only if at least one of the endpoints is locally registered.
You can change this setting so that he VCS will act as SIP-H.323 gateway regardless of whether the endpoints involved are locally registered.
You also have the option to disable interworking completely.
We recommend that you leave this setting as RegisteredOnly (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.
The VCS cannot act as an IPv4 to IPv6 gateway at the same time as it is acting as a SIP to H.323 gateway.
H.323 SIP interworking mode
Click here to save your changes.
Determines whether or not the VCS will act as a gateway between SIP and H.323 calls.
Off: the VCS will not act as a SIP-H.323 gateway.
Calls for which the VCS is acting as an SIP to H.323 gateway are traversal calls. They will therefore require a traversal call licence.
RegisteredOnly: the VCS will act as a SIP-H.323 gateway but only if at least one of the endpoints is locally registered.
On: the VCS will act as SIP-H.323 gateway regardless of whether the endpoints are locally registered.
Save

Endpoint Registration
Registrations on a VCS Expressway
MCU, Gateway and Content Server Registration
In order for an endpoint to use the TANDBERG 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. Two separate mechanisms are provided:
If a traversal-enabled endpoint registers directly with a VCS Expressway, the VCS Expressway will provide VCS services to that endpoint in addition to firewall traversal. Traversal-enabled endpoints include all TANDBERG Expressway™ endpoints and third party endpoints which support the ITU H.460.18 and H.460.19 standards.
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.
an • authentication process based on the username and password supplied by the endpoint
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:
a simple Registration Restriction Policy that uses • Allow Lists or Deny Lists to specify which aliases can and cannot register with the VCS.
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 a pattern match equal to the prefix to be used.
It is possible to use both mechanisms together. For example, you can use authentication to verify an endpoint’s identity from a corporate directory, and registration restriction to control which of those authenticated endpoints may register with a particular VCS.
This section gives an overview of how endpoints and other devices register with the VCS, and then describes the two mechanisms by which registrations can be restricted.
To ensure firewall traversal will work successfully for H.323 endpoints behind a NAT, the endpoint must be traversal-enabled.
The TANDBERG MPS and TANDBERG Content Server (TCS) both support Expressway. They can therefore register directly with a VCS Expressway for firewall traversal.

Finding a VCS with which to Register
H.323
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.
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).
SIP endpoints must find a SIP Registrar with which to register. The SIP Registrar maintains a record of the endpoint’s details against the endpoint’s Address of Record (AOR). When a call is received for that AOR, the SIP Registrar refers to the record in order to find the endpoint to which it corresponds. (Note that the same AOR can be used by more than one SIP endpoint at the same time.)
You can prevent H.323 endpoints being able to register automatically with the VCS by disabling Auto Discovery on the VCS. The Auto Discovery setting determines whether the VCS responds to the Gatekeeper Discovery requests sent out by endpoints.
The SIP Registrar will only accept registrations for domains for which it is authoritative.
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).
To configure the Auto Discovery setting:
If the • Server Discovery mode is set to automatic, the endpoint will send a REGISTER message to its SIP Server. This will be forwarded (via DNS if necessary) to the Registrar 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 john.smith@example.com, the request will be sent to the Registrar authoritative for the domain example.com.
VCS Configuration > Protocols > H.323 • . You will be taken to the H.323 page.
If the • Server Discovery mode is set to manual, the user must specify the IP address or FQDN of the Registrar with which they wish to register, and the endpoint will attempt to register with that Registrar only.
On: The VCS will respond to Gatekeeper discovery requests.
The VCS is a SIP Server for endpoints in its local zone, and can also act as a SIP Registrar.
If the VCS is acting as the endpoint’s SIP Server and SIP Registrar, when the registration request • is received from the endpoint it will be accepted by the VCS and the endpoint will be registered and able to receive inbound calls. See Using the VCS as a SIP Registrar for more information.
Off: The VCS will reject Gatekeeper discovery requests. H.323 endpoints will be able to register with the VCS only if their Gatekeeper Discovery setting is Manual and they have entered the IP address of the VCS.
If the VCS is acting as the endpoint’s SIP server but is not a SIP Registrar, it will proxy the • registration request. See Proxying registration requests for more information.
Preventing automatic registrations · Auto discover

About Authentication for Local Registrations
Configuring Authentication for Local Registrations
To configure endpoint Authentication options:
The VCS can be configured to use a username and password-based challenge-response scheme to permit endpoint registrations. This process is known as authentication.
In order to authenticate with the VCS, the endpoint must supply it with a username. For TANDBERG endpoints using H.323, the username is the endpoint’s Authentication ID; for TANDBERG endpoints using SIP it is the endpoint’s Authentication Username.
On: all endpoints must authenticate with the VCS before registering.
Off: no authentication is required for endpoints.
For details of how to configure endpoints with a username and password, please consult the endpoint manual.
The default is Off.
In order to verify the identity of the device, the VCS needs access to a database on which all authentication credential information (usernames, passwords, and other relevant information) is stored. This database may be located either locally on the VCS, or on an LDAP Directory Server. The VCS looks up the endpoint’s username in the database and retrieves the authentication credentials for that entry. If the credentials match those supplied by the endpoint, the registration is allowed to proceed.
Determines which database the VCS will use during authentication.
LocalDatabase: the local database is used. You must configure the Local database to use this option.
LDAP: A remote LDAP database is used. You must configure the LDAP server to use this option.
The VCS supports the ITU H.235 specification [1] for authenticating the identity of H.323 network devices with which it communicates.
The default is LocalDatabase.
Mode · Database type

About External Registration Credentials
Configuring External Registration Credentials
To configure Authentication options:
The VCS may be required to authenticate itself with another system. 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.
The Authentication Username is the name that the VCS uses when authenticating with other systems.
Additionally, traversal clients must always successfully authenticate with traversal servers before they can connect.
The username and password that your VCS provides when authenticating with other systems is configured under the External Registration Credentials section of the Authentication Configuration page.
Specifies the password to be used by the VCS (in conjunction with the Authentication username) when the VCS is authenticating with other systems.
Authentication username · Authentication password

Alias Origin Setting
Authentication using an LDAP Server
This setting determines the alias(es) with which the endpoint will attempt to register. The options are as follows:
If the VCS is using an LDAP server for authentication, the process is as follows:
The endpoint presents its username and authentication credentials (these are generated using 1. its password) to the VCS, and the alias(es) with which it wishes to register
The VCS looks up the username in the LDAP database and obtains the authentication and alias 2. information for that entry.
The alias(es) presented by the endpoint will be used as long as they are listed in the LDAP database for the endpoint’s username.
If the authentication credentials match those supplied by the endpoint, the registration will 3. continue.
The VCS will then determine which alias(es) the endpoint will be allowed to attempt to register with, based on the alias origin 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 endpoint’s aliases. For SIP endpoints, you can use this setting to reject a registration if the endpoint’s AOR does not match that in the LDAP database.
Configuring the LDAP Server Directory
Securing the LDAP Connection with TLS
The traffic between the VCS and the LDAP server can be encrypted using Transport Layer Security (TLS).
The directory on the LDAP server should be configured to implement the ITU H.350 specification [2] to store credentials for devices with which the VCS communicates. The directory should also be configured with the aliases of endpoints that will register with the VCS.
To use TLS:
The alias(es) presented by the endpoint will be used in addition to any that are listed in the LDAP database for the endpoint’s username. In other words, this is the same as for LDAP, with one exception:
If an endpoint presents an alias that is not in the LDAP database, it will be allowed to register • with that alias.
TLS can be difficult to configure, so we recommend that you confirm that your LDAP database is working correctly before you attempt to secure the connection with TLS. We also recommend that you use a third party LDAP browser to verify that your LDAP server is correctly configured to use TLS.
The alias(es) presented by the endpoint will be used; any in the LDAP database will be ignored.
If no aliases are presented by the endpoint, it will not be allowed to register. •
For instructions on how to configure common LDAP servers, see the Appendix LDAP Configuration.
For information on how to configure the VCS to trust the certificate installed on the LDAP server, see Security.
Combined · Endpoint

Configuring LDAP Server settings
To configure the settings for accessing the LDAP server:
The IP address or FQDN of the LDAP server.
The IP port of the LDAP server.
The default is 389.
Determines whether the connection to the LDAP server will be encrypted. (For more information on configuring encryption, see Securing the LDAP connection with TLS.)
Determines the source of the alias(es) with which the endpoint will be registered.
TLS: TLS Encryption will be used for the connection with the LDAP server.
Off: No encryption will be used.
LDAP: The aliases listed in the LDAP database for the endpoint’s username will be used; those presented by the endpoint will be ignored.
The default is Off.
Endpoint: The aliases presented by the endpoint will be used; any in the LDAP database will be ignored.
The user distinguished name to be used by the VCS when binding to the LDAP server.
Combined: The endpoint will be registered both with the aliases which it has presented and with those configured in the LDAP database.
The default is LDAP.
The password to be used by the VCS when binding to the LDAP server.
Upload a CA Certificate file for TLS
Clicking here will take you to the Security page, where you can upload a file that contains the trusted CA certificate for the LDAP server. This is required if the connection between the VCS and the LDAP server is encrypted.
The area of the directory on the LDAP server to be searched for the credential information.
This should be specified as the Distinguished Name (DN) in the LDAP directory under which the H.350 objects reside.
For more information on how to configure the VCS to trust the certificate installed on the LDAP server, see Security.

Authentication using a Local Database
The local database is included as part of your VCS system. It consists of a list of usernames and passwords, which you add via the web interface and/or the CLI. The database can hold up to 2500 entries.
The Credentials page shows all the existing entries in the Local Database.
You can sort these entries by clicking on the Name column heading.
Configuring the Local Database
To manage entries in the Local Database:
Select View/Edit to add a make changes to an existing entry. You will be taken to the Edit Credential page.
Returns you to the Credentials page without saving your changes.
Select New to add a new entry to the Local Database. You will be taken to the Create Credential page.
Removes the entry from the Local Database and returns you to the Credentials page. Name
The username used by the endpoint when authenticating with the VCS.
Saves the changes you have made.
The password used by the endpoint when authenticating with the VCS.
The same credentials can be used by more than one endpoint - you do not need to have a separate entry in the database for each endpoint.
Select Create Credential to add the new entry to the Local Database and return to the Credentials page.

About Alias Registration
Attempts to Register using an Existing Alias
SIP
Once the authentication process (if required) has been completed, the endpoint will then attempt to register its alias(es) with the VCS.
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.
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”.
H.323 Alias Registration
When registering, the H.323 endpoint presents the VCS with one or more of the following:
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. The reasons for this could include:
To configuring the Registration Conflict Mode:
We recommended that you 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.
Determines what will happen when an H.323 endpoint attempts to register using an alias that has already been registered from another IP address.
We recommended that you do not use aliases that reveal sensitive information. Due to the nature of H.323, call setup information is exchanged in an unencrypted form.
Reject: The registration from the new IP address will be rejected. This is useful if your priority is to prevent two users registering with the same alias.
Overwrite: The existing registration will be overwritten using the new IP address. This is useful if your network is such that endpoints are often allocated new IP addresses, because it will prevent unwanted registration rejections.
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.
The default is Reject.
Registration conflict mode · SIP Alias Registration

About Allow and Deny Lists
Activating use of Allow or Deny Lists
When an endpoint attempts to register with the VCS it presents a list of aliases. You can control which endpoints are allowed to register by setting the Restriction Policy to AllowList or DenyList and then including any one of the endpoint’s 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.
To activate the use of Allow or Deny lists to determine which aliases are allowed to register with the VCS:
For example, If the Registration Restriction policy is set to DenyList and an endpoint attempts to register using three aliases, one of which matches a pattern on the Deny list, that endpoint’s registration will be denied. Likewise, if the Registration Restriction policy is set to AllowList, only one of the endpoint’s aliases needs to match a pattern on the Allow list for it to be allowed to register using all its aliases.
Patterns and Pattern Types
Entries on the Allow List and Deny List are a combination of Pattern and Type. The Pattern specifies the string to be matched; the Type determines whether that string;
Specifies the policy to be used when determining which endpoints may register with the VCS.
Click here to save your changes.
None: Any endpoint may register.
AllowList: Only those endpoints with an alias that matches an entry in the Allow List may register.
Allow Lists and Deny Lists are mutually exclusive: only one may be in use at any given time.
DenyList: All endpoints may register, unless they match an entry on the Deny List.
The default is None.
Restriction policy · Save

Managing Entries in the Allow List
To view and manage the entries in the Allow List:
This page shows all the existing entries in the Allow List.
You can sort these entries by clicking on the relevant column heading.
This warning is a reminder that you must set the restriction policy to Allow List (VCS Configuration > Registration > Configuration) in order for it to be activated.
Click here to add a new entry to the Allow List. You will be taken to the Create Allow Pattern page.
Select View/Edit to make changes to an existing entry. You will be taken to the Edit Allow Pattern page.
Enter the pattern you wish to add to the Allow List.
Edit the pattern.
Select the way in which the Pattern must match the alias for the registration to be allowed. Options are:
Edit the type.
Exact: the alias must match the Pattern exactly.
Prefix: the alias must begin with the Pattern.
Select Cancel to return to the Registration Allow List page without saving your changes.
Suffix: the alias must end with the Pattern.
Regex: the Pattern is a regular expression. See Regular Expression Reference for further information.
Select Delete to remove the registration from the list.
Add Allow List Pattern
Click here to save the entry and return to the Registration Allow List page.
Select Save to save your changes.

Managing Entries in the Deny List
To view and manage the entries in the Deny List:
This page shows all the existing entries in the Deny List.
You can sort these entries by clicking on the relevant column heading.
This warning is a reminder that you must set the restriction policy to Deny List (VCS Configuration > Registration > Configuration) in order for it to be activated.
Click here to add a new entry to the Deny List. You will be taken to the Create Deny Pattern page.
Select View/Edit to make changes to an existing entry. You will be taken to the Edit Deny Pattern page.
Enter the pattern you wish to add to the Deny List.
Edit the pattern.
Select the way in which the Pattern must match the alias for the registration to be denied. Options are:
Edit the type.
Exact: the alias must match the Pattern exactly.
Select Cancel to return to the Registration Deny List page without saving your changes.
Prefix: the alias must begin with the Pattern.
Suffix: the alias must end with the Pattern.
Regex: the Pattern is a regular expression. See Regular Expression Reference for further information.
Select Delete to remove the registration from the list.
Add Deny List Pattern
Click here to save the entry and return to the Registration Deny List page.
Select Save to save your changes.

This section provides information on the pages that appear under the Local Zone, Zones and Alternates sub-menus of the VCS Configuration menu.
These pages allow you to configure the VCS’s Local Zone (which is made up of subzones, including the Traversal Subzone and Default Subzone) and also create and configure relationships with other systems (including other VCSs, Gatekeepers, Border Controllers or SIP devices) via the use of zones. You can also configure up to 5 Alternates for resiliency.
This section includes an overview on all the different types of subzones and zones and how these fit into the overall structure of your video communication network.

The most basic implementation of a TANDBERG 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 wish to apply restrictions to the amount of bandwidth used by and between different parts of your network.
VCS CONTROL
LOCAL ZONE
VCS EXPRESSWAY
This section will give you 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.
The diagram opposite shows the different components of a VCS (subzones, zones and Alternates) 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. The VCS also has 4 Alternates to provide resilience.
ENUM
All these components are described in more detail in the sections that follow.

Configuring the Local Zone and its Subzones
The collection of all endpoints, gateways, MCUs and Content Servers registered with the VCS make up its Local Zone.
The Local Zone and its subzones exist for the purposes of bandwidth management. Once you have set up your subzones you can apply bandwidth limits to:
The Local Zone is made up of subzones. These include an automatically created Default Subzone and up to 100 manually configurable subzones. Each manually configured subzone specifies a range of IP addresses. When an endpoint registers with the VCS it is allocated to the appropriate subzone based on its IP address. If the endpoint’s IP address does not match any of the subzones, it is assigned to the Default Subzone. The Local Zone may be independent of network topology, and may be comprised of multiple network segments.
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 section on Bandwidth Control.
Traversal Subzone
The VCS also has a special type of subzone known as the Traversal Subzone. This is a conceptual subzone; no endpoints can be registered to it, but all traversal calls (i.e. calls for which the VCS is taking the media in addition to the signaling) must pass through it. The Traversal Subzone exists in order to allow you to control the amount of bandwidth used by traversal calls, as these can be particularly resource-intensive.
The VCS allows you to configure the range of ports to be used for the media in traversal calls. A single traversal call can consist of up to 5 types of media (audio, video, far end camera control, duo video and BFCP) and each type of media may require a pair of ports – for example, audio and video each require one port for RTP, and one for RTCP. Separate pairs of ports are required for the inbound and outbound portions of a call. A single traversal call can therefore take up to 20 ports.
The default range for the ports to be used for media is 50000 - 51119 UDP, but these can be changed to anywhere between 1024 and 65533. Ports are allocated from this range in pairs, the first of each being even. Therefore the range must start with an even number and end with an odd number.
The following types of calls require the VCS to take the media. They are classified as traversal calls and must always pass through the Traversal Subzone:
To configure the ports used for media in traversal calls:
a SIP to SIP call when one of the participants is behind a NAT. • All such calls will require a traversal call licence each time they pass through the Traversal Subzone.
You must ensure that the port range is large enough to support the maximum number of traversal calls available on your VCS. A single traversal call can take up to 20 ports (5 pairs in each direction). So for example, if your VCS is licensed for 5 traversal calls you must ensure that the range of ports configured for traversal media is at least 100. If you add extra traversal calls to your system, you must also ensure that the range of ports available is sufficient.
STUN Relays also consume traversal call licences (three relays take one licence) but they do not actually pass through the traversal subzone.

Traversal Client Zone Traversal Server Zone
A zone is a collection of endpoints, either all registered to a single system (e.g. VCS, gatekeeper or Border Controller), or of a certain type such as ENUM or DNS. The use of zones enables you to:
In order to be able to traverse a firewall, the VCS must be neighbored with a traversal server (for example a TANDBERG VCS Expressway or a TANDBERG Border Controller).
A VCS Expressway is able to act as a traversal server, providing firewall traversal on behalf of traversal clients (for example, VCS Controls or gatekeepers).
In this situation your local VCS is a traversal client, so you neighbor 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.)
In order to act as a traversal server, the VCS Expressway must have a special type of two-way neighbor relationship with each traversal client. To do this, you create a traversal server zone on your local VCS Expressway and configure it with the details of the corresponding zone on the traversal client. (The client must also be configured with details of the VCS Expressway.)
use links to determine 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
Once you have neighbored with the traversal server you can:
Once you have neighbored with the traversal client you can:
control the bandwidth used for calls between your local VCS • and the traversal server.
control the bandwidth used for calls between your local VCS • and the traversal client.
A Neighbor zone could be a collection of endpoints registered to another system (e.g. VCS, gatekeeper, or Border Controller), or it could be a SIP device. 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 stand- alone systems.
You create a neighbor relationship with the other system by adding it as a neighbor zone on your local VCS. Once you have added it, you can:
Neighbor zone relationships are one-way; adding another system to your VCS as a neighbor does not mean that your VCS will also be a neighbor of that other system. In such a situation, your VCS will know about and be able to query the other system, but the other system will not know about or be able to query your VCS. However, inbound calls will be identified as coming from that neighbor if the source IP address matches.
Traversal client-server zone relationships are two-way; in order for firewall traversal to work, the traversal server and the traversal client must each be configured with the other’s details. (See Quick Guide to VCS Traversal Client - Server Configuration for more information.) The client and server will then be able to query each other.

DNS Zone Default Zone
ENUM zones allow you to locate endpoints via an ENUM lookup. You can create one or more ENUM zones based on the ENUM DNS suffix used and/or by pattern matching of the endpoints’ aliases.
DNS zones allow you to locate endpoints via a DNS lookup. You can create one or more DNS zones based on pattern matching of the endpoints’ aliases.
Any incoming calls from endpoints that are not recognized as belonging to any of the existing configured zones are deemed to be coming from the Default Zone.
Once you have configured one or more DNS zones, you can:
The VCS comes pre-configured with the Default Zone and default links between it and both the Default Subzone and the Traversal Subzone.
Once you have configured one or more ENUM zones, you can:
The purpose of the Default Zone is to allow you to manage incoming calls from unrecognized endpoints to the VCS. You can do this by:
deleting the default links. This will prevent any incoming calls • from unrecognized endpoints
applying pipes to the default links. This will allow you to • control the bandwidth consumed by incoming calls from unrecognized endpoints.
See ENUM Dialing for more information on the use of ENUM zones.
The default links can be reinstated at any time via the command:
xCommand DefaultLinksAdd

Configuring Zones
In order to neighbor with another system (e.g. VCS, gatekeeper or Border Controller) or create an ENUM or DNS zone, you must add a new zone on the local VCS. When adding a new zone you will be asked to specify its Type; this will determine which configuration options will then be available.
Once you have created a new zone on the local VCS you must configure it appropriately. For traversal server zones, traversal client zones and neighbor zones this will include providing information about the neighbor system such as IP address and ports.
Zones are configured via the Edit Zone page. You will be taken to this page automatically upon creation of a new zone. To access this page for an existing zone:
To create a new zone:
Enter the name you wish to give to this zone. The name acts as a unique identifier, allowing you to distinguish between zones of the same type.
From the Type drop-down menu, select the type of zone you wish to add.
Once the zone has been created, the Type cannot be changed.
Click here to create the zone. You will be taken directly to the Edit Zone page.
Click here to return to the Zones page without creating the zone.

Assigns a name to the zone. The name acts as a unique identifier, allowing you to distinguish between zones of the same type.
Determines the nature of the zone:
Neighbor: the new zone will be a connection to a neighbor of the local VCS.
TraversalClient: the local VCS is a traversal client of the new zone, and there is a firewall between the two.
TraversalServer: the local VCS is a traversal server for new zone, and there is a firewall between the two.
ENUM: the new zone contains endpoints discoverable by ENUM lookup.
DNS: the new zone contains endpoints discoverable by DNS lookup.
Once the zone has been created, the Type cannot be changed.
The hop count is the number of times a request will be forwarded to a neighbor gatekeeper or proxy (see Hop Counts for more information). This field specifies the hop count to be used when sending an alias search request to this particular zone.
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.
The Match sections allow you to configure when and how search requests will be sent to this zone, and also whether any transforms will be applied to aliases being searched for in this zone. These features are described in full in the section Zone searching and alias transforming.

Determines whether SIP calls will be allowed to and from the neighbor zone.
Determines which transport type will be used for SIP calls to and from the neighbor zone.
Specifies the port on the neighbor system to be used for SIP calls from the local VCS.
This must be the same port number as that configured on the neighbor system as its SIP TCP or SIP TLS port (depending on which SIP transport mode is in use).
Determines which transport type will be used for SIP calls to and from the neighbor zone.
H.323 mode
Determines whether H.323 calls will be allowed to and from the neighbor zone.
H.323 port
Specifies the port on the neighbor system to be used for H.323 calls from the local VCS.
This must be the same port number as that configured on the neighbor system as its H.323 UDP port. If the neighbor is another VCS, this will be the port found under VCS Configuration > Protocols > H.323 in the Registration UDP Port field.
Alternate 1 to Alternate 5 address
Enter the IP address or FQDN of the neighbor system.
Enter the IP addresses or FQDNs of all Alternates configured on the neighbor system.

Traversal clients must always authenticate with traversal servers by providing their authentication username and password.
Determines whether SIP calls will be allowed to and from this zone.
The client’s authentication username is shown here for reference, to make it easier to configure the corresponding zone on the traversal server.
Specifies the port on the traversal server to be used for SIP calls to and from the VCS.
The authentication username is a system-wide setting that is set via VCS Configuration > Authentication > Configuration.
Determines which transport type will be used for SIP calls to and from the traversal server.
H.323 mode
Determines whether H.323 calls will be allowed to and from the traversal server.
For firewall traversal to work via SIP, the traversal server must have a traversal server zone configured on it to represent this VCS, using this same transport type and port number.
H.323 protocol
Determines which of the two firewall traversal protocols (Assent or H.460.18) to use for calls to the traversal server. (See Firewall Traversal Protocols for more information.)
H.323 port
Specifies the interval in seconds with which a failed attempt to establish a connection to the traversal server should be retried.
Specifies the port on the traversal server to be used for H.323 calls to and from the local VCS.
For firewall traversal to work via H.323, the traversal server must have a traversal server zone configured on it to represent this VCS, using this same port number.
Specifies the IP address or FQDN of the traversal server.
For full details on how traversal client zones and traversal server zones work together to achieve firewall traversal, see Firewall Traversal.
Alternate 1 to Alternate 5 address
Specifies the IP addresses or FQDNs of any alternates configured on the traversal server.

There must be an entry in the traversal server’s Authentication database for this username. See Authentication for more information.
Determines whether SIP calls will be allowed to and from this zone.
If the traversal client is a VCS, this is its Authentication Username. If the traversal client is a TANDBERG Gatekeeper, this is its System Name.
Specifies the port on the local VCS Expressway to be used for SIP calls to and from the traversal client.
H.323 mode
Determines which transport type will be used for SIP calls to and from the traversal client.
Determines whether H.323 calls will be allowed to and from the traversal client.
H.323 protocol
Sets the frequency (in seconds) with which the client will send a UDP probe to the traversal server if a keep alive confirmation has not been received.
Determines the protocol (Assent or H.460.18) to be used to traverse the firewall/NAT. (See Firewall Traversal Protocols for more information.)
H.323 port
Sets the number of times the client will attempt to send a UDP probe to the VCS Expressway during call setup.
Specifies the port on the local VCS to be used for H.323 calls to and from the traversal client.
H.460.19 demultiplexing Mode
UDP keep alive interval
Determines whether or not the same two ports will be used for media by two or more calls.
Sets the interval (in seconds) with which the client will send a UDP probe to the VCS Expressway once a call is established, in order to keep the firewall’s NAT bindings open. TCP retry interval
On: all calls will use the same two ports.
TCP keep alive interval
Off: each call will use a separate pair of ports.
Sets the interval (in seconds) with which the traversal client will send a TCP probe to the VCS once a call is in place, in order to maintain the firewall’s NAT bindings.
Sets the number of times the client will attempt to send a TCP probe to the VCS Expressway during call setup.
Sets the frequency (in seconds ) with which the traversal client will send a TCP probe to the VCS during call setup.
The default UDP and TCP probe retry intervals are suitable for most situations. However, if you experience problems with NAT bindings timing out, they may need to be changed.
For full details on how traversal client zones and traversal server zones work together to achieve firewall traversal, see Firewall Traversal.


Specifies the domain to be appended to the transformed E.164 number to create an ENUM domain for which this zone is queried.
Determines whether SIP records will be looked up for this zone.
Determines whether H.323 records will be looked up for this zone.
Full details of how to use and configure ENUM zones is given in ENUM Dialing.
Determines whether SIP calls will be allowed to this zone.
Determines whether H.323 calls will be allowed to this zone.
Full details of how to use and configure DNS zones is given in URI Dialing.

Configuring Alternates
The purpose of an Alternate is to provide extra reliability in the rare case that a VCS fails.
Alternates are not used to increase the capacity of your network; they are to provide redundancy. To increase capacity, add one or more additional VCSs to your network and neighbor them together.
Each VCS can be configured with the IP addresses of up to five other VCSs that will act as Alternates should the current VCS become unavailable.
Each VCS can be part of a pool of up to 6 Alternate VCSs that act as backups to each other in case one becomes unavailable (for example, due to a network or power outage).
To configure Alternate VCSs:
All the Alternates in a pool are configured similarly and share responsibility for their H.323 endpoint community. When an H.323 endpoint registers with the VCS, it is given the IP addresses of all the VCS’s Alternates. If the endpoint loses contact with the initial VCS, it will seek to register with one of the Alternates. This may result in your H.323 endpoint community’s registrations being spread over all the Alternates.
Alternates are periodically interrogated to ensure that they are still functioning. In order to prevent delays during call setup, any non-functioning Alternates will not receive Location Requests.
If you have Alternates configured, you should change the registration Time to live on the primary VCS and on each of its alternates from the default 30 minutes to just a few minutes. This setting determines how often endpoints are required to re-register with their VCS, and changing this to just a few minutes will ensure that if the primary VCS has failed, the endpoint will quickly failover to one of its Alternates.
When the VCS receives a Location Request, it checks its own registration database along with that of each of its Alternates before responding. This allows the pool of endpoints to be treated as if they were registered with a single VCS.
You must configure all Alternates in a pool identically for all registration and call features such as authentication, bandwidth control and policy. If you do not do this, endpoint behavior will vary unpredictably depending on which Alternate it is currently registered with. Alternates should also be deployed on the same LAN as each other so that they may be configured with the same routing information such as local domain names and local domain subnet masks.
When configuring your VCS with the details of the system it will be using as a traversal server, you are given the opportunity to include details of any Alternates of that traversal server. Adding this information to your VCS will ensure that, if the original traversal server becomes unavailable, your VCS can use one of its Alternates instead.
Alternate 1 to Alternate 5 IP address
Click Save to save your changes.
To configure another VCS as an Alternate, enter its IP address. Up to 5 Alternates may be configured.
Systems that are configured as Alternates must not be configured as neighbors to each other.
Failover re-registration to an Alternate applies to H.323 re-registrations only. SIP currently has no equivalent.
Save

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 chose will depend on the complexity of your system. Some possible options are described in the following sections.
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.
An alternative deployment would use a structured dial plan whereby endpoints are assigned an alias based on the system they are registering with.
In this type of structure one VCS is nominated as the Directory for the deployment, and all other VCSs are neighbored with it alone. Each VCS is configured with the Directory VCS as a neighbor zone with a Match Mode of Always, and the Directory VCS is configured with each VCS as a neighbor zone with a Match Mode of Pattern and its prefix as the Pattern String.
If you are using E.164 aliases, each VCS would be assigned an area code. When the VCSs are neighbored together, each neighbor zone is configured with its corresponding area code as a prefix (i.e. a Match Mode of Pattern and a Type of Prefix). That neighbor will now only be queried for calls to numbers which begin with its prefix.
Whilst 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 and its Alternates.
There is no need to neighbor the VCSs with each other. Adding a new VCS now only requires changing configuration on that system and the Directory VCS.
In a URI based dial plan, similar behavior may be obtained by configuring neighbors with a suffix to match the desired domain name.
However, failure of the Directory VCS in this situation could cause significant disruption to communications. Consideration should be given to the use of Alternates for increased resilience.
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 VCS could be configured to strip prefixes before sending the query to that zone.
A structured dial plan will minimize 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.

This section provides information on the pages that appear under the Calls, Transforms and Policy sub-menus of the VCS Configuration menu. These pages allow you to configure the way in which the VCS receives and process calls.
This section includes the following:

One of the functions of the VCS is to route calls to their appropriate destination, based on the address or alias received from a locally registered endpoint or neighbor zone.
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.
YES
Does the alias match a Local Zone Transform pattern?
(from locally registered endpoint or
Search Process
NO
The process followed by the VCS when attempting to locate a destination endpoint is shown in the diagram opposite.
Has the alias been
The user enters into their endpoint the alias or address of the 1. destination endpoint. This can be in a number of different formats.
The destination address is sent from the caller’s endpoint to 2. its local VCS (i.e. the VCS to which it is registered).
NO
NO
The VCS applies any Local Zone transforms to the alias. 3.
Route call to new alias(es) listed in the FindMe configuration
The VCS applies any Administrator Policy to the (transformed) 4. alias. If this results in a new alias, the process starts again, with the new alias checked against the Local Zone transforms.
Is User Policy enabled?
Is the alias a FindMe
The VCS applies any User Policy to the alias. If the alias is a 5. FindMe name, the process will start again; all the resulting aliases will be checked against Local Zone transforms and Administrator Policy.
The VCS then checks all its local registrations and those 6. of its Alternates for the alias, placing the call if the alias is found.
If the alias is not found locally, the VCS will then query its 7. zones, in priority order, to see if any of them can find the alias. If the alias matches an ENUM zone, this may return a URI. If so, the process starts again; the URI is checked against any Local Zone transforms, Administrator Policy and User Policy.
Does the alias match an ENUM zone
Search Zones (in order of priority)
Has the alias been found?
YES
If the alias is found by one of the neighbor zones, the call will 8. be placed to that zone.

Dialing by H.323 ID or E.164 alias
The destination address that is entered via the caller’s endpoint can take a number of different formats, and this will affect the specific process that the VCS follows when attempting to locate the destination endpoint. The address types supported by the VCS are:
No special configuration is required in order to place a call using an H.323 ID or E.164 alias. The VCS follows the usual process and searches for the ID or alias among its local registrations and those of its Alternates. If no match is found, it may forward the query on to its neighbors, depending on the match and priority settings of each.
SIP endpoints must register using a URI. We recommend 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
Dialing by IP address is necessary when the destination endpoint is not registered with any system (e.g. VCS, gatekeeper or Border Controller). If the destination endpoint is registered with one of these systems, then it may still be possible to call it using its IP address but we recommend that one of the other addressing schemes should be used instead as they are more flexible.
When a user places a call using URI dialing, they will typically dial name@example.com.
For endpoints that are not locally registered, URI dialing may make use of DNS to locate the destination endpoint. In order to support full URI dialing on the VCS you must configure it with at least one DNS server and at least one DNS zone,
In order to make a call by dialing the destination endpoint’s IP address, the call must be able to be routed via a VCS that is configured with a Calls to Unknown IP Addresses setting of Direct. This could be the local VCS, or it could be one of its neighbors (in which case the local VCS would route the call to the neighbor, which would then place the call directly to the IP address).
Full instructions on how to configure the VCS to support URI dialing (both outbound and inbound) are given in URI Dialing.
However, if the destination IP address is found in a local subzone (i.e. it is an endpoint registered to the same VCS as the endpoint making the call), then the call will be placed regardless of the Calls to Unknown IP Addresses setting.
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.
Endpoints registered to a VCS Expressway
Calls made by dialing the IP address of an H.323 endpoint registered directly with a VCS Expressway will be forced to route through the VCS Expressway. The call will therefore be subject to any restrictions configured on that system.
The ENUM dialing facility allows you to retain the flexibility of URI dialing whilst having the simplicity of being called using just a number - particularly important if any of your callers are restricted to dialing via a numeric keypad.
In order to support ENUM dialing on the VCS you must configure it with at least one DNS server and the appropriate ENUM zone(s).
If you are calling from an unregistered endpoint, we do not recommend dialing the destination endpoint using its IP address. The presence of a firewall may disrupt the call. Instead place the call to the VCS to which the destination endpoint is registered as described in Calls from an Unregistered Endpoint.
Full instructions on how to configure the VCS to support ENUM dialing (both outbound and inbound) are given in ENUM Dialing.

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.
To configure the hop count for a zone:
For full details on other zone options, see Configuring Zones.
For search requests initiated by the local VCS, the hop count assigned to the request is configurable on a zone-by-zone basis. The zone’s hop count will apply 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 (i.e. the original hop count or the hop count configured for that zone) will be used.
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.
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.
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.

Administrator Policy and Authentication
The VCS allows you to set up a set of 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 Administrator Policy.
Administrator Policy uses the source and destination of a call to determine the action to be taken. Policy interacts with Authentication when considering the source alias of the call. If your VCS is part of a secure environment, any policy decisions based on the source of the call should only be made when that source can be authenticated. Whether or not the VCS considers an endpoint to be authenticated depends on the Authentication Mode setting of the VCS.
If Administrator 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
When Authentication Mode is set to On on the VCS, all endpoints and neighbors are required to authenticate with it before calls will be accepted. If a call is received from an unauthenticated source (e.g. neighbor or endpoint) the call’s source aliases will be removed from the call request and replaced with an empty field before the Administrator Policy is executed. This is because there is a possibility that the source aliases could be forged and therefore they should not be used for policy decisions in a secure environment. This means that, when Authentication Mode is On and you configure policy based on the source alias, it will only apply to authenticated sources.
reject the call. • You can set up an Administrator Policy in either of two ways:
The VCS determines whether or not an endpoint is authenticated as follows:
by • configuring basic administrator policy using the web interface. (Note that this will only allow you to Allow or Reject specified calls)
An H.323 endpoint is considered to be authenticated if either of the following conditions apply:
by • uploading a script written in the Call Processing Language (CPL).
it is a locally registered endpoint. (Because Authentication Mode is On, the registration will have been accepted only after the • endpoint authenticated successfully with the VCS.)
it is a remote endpoint that is registered to and authenticated with a Neighbor VCS, and that Neighbor in turn has authenticated • with the local VCS.
An H.323 endpoint is considered to be unauthenticated when:
it is a remote endpoint registered to a neighbor and that neighbor has not authenticated with the VCS. This is regardless of • whether or not the endpoint authenticated with the neighbor.
Only one of these two methods can be used at any one time to specify Administrator Policy. If a CPL script has been uploaded, this will disable use of the web interface to configure administrator policy. In order to use the web interface, you must delete the CPL script that has been uploaded.
A SIP endpoint is considered to be authenticated when:
it falls within one of the domains for which the VCS is authoritative and has successfully responded to an authentication challenge. • A SIP endpoint is considered to be unauthenticated if any of the following conditions apply:
When enabled, Administrator Policy is executed for all calls going through the VCS.
Use Administrator Policy to determine which callers can make or receive calls via the VCS. Use Allow and Deny lists to determine which aliases can or cannot register with the VCS.
When Authentication Mode is set to Off on the VCS, calls will be accepted from any endpoint or neighbor. The assumption is that the source alias is trusted, so authentication is not required.

To enable Administrator Policy:
On: Administrator Policy is enabled. If a CPL script has been uploaded, this policy will be used. Otherwise, the policy configured via the Administrator Policy section will be used.
Off: Administrator Policy is not in use.
You must click here for any changes to the Administrator Policy Mode to take effect.
Once you have enabled the use of Administrator Policy, you must define the policy to be used. This is done either via the web interface or by uploading a CPL script.
If Administrator Policy is on but a policy has not been configured, then a default policy will be applied that allows all calls, regardless of source or destination.
Administrator Policy Mode · Save

To configure Administrator Policy using the web interface:
Each combination of Source and Destination is compared, in the order shown, with the details of the call being made until a match is found. To move a particular item to higher or lower in the list, click on the
VCS Configuration > Policy > Administrator • . You will be taken to the Administrator Policy page.
icons respectively.
You will not be able to use the web interface to configure Administrator Policy if a CPL file is already in place. If this is the case, you will have the option to Delete Existing file. Doing so will delete the existing Administrator Policy and enable use of the web interface for Administrator Policy configuration.
The alias that the endpoint dialed to make the call. This field supports Regular Expressions.
Whether or not the call will be permitted.
Allow: if both the Source and Destination aliases match those listed, call processing will continue.
This section shows the web-configured Administrator policy currently in place.
Reject: if both the Source and Destination aliases match those listed, the call will be rejected.
To edit the existing policy, click Add New.
The alias that the calling endpoint used to identify itself when placing the call. This field supports Regular Expressions.
Returns to the Administrator Policy page without adding the new item.
Adds the new item to the Administrator Policy.
Check this box if you wish the new policy to apply to all incoming calls where the endpoint making the call is not either:
Updates the existing Administrator Policy with the changes you have made.
To remove one or more line items from the list, check the box to the left of the item and then click Delete.
Click to add the new item to the Policy. A new row with empty fields for you to complete will appear.

Downloading policy files
To configure Administrator Policy using a CPL script:
Click here to download the Administrator Policy that is currently in place, as an XML-based CPL script.
VCS Configuration > Policy > Administrator • . You will be taken to the Administrator Policy page.
You can use CPL scripts to configure advanced Administrator 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.
The CPL script cannot be uploaded via the command line interface.
You may wish to download the file in order to take a backup copy of the Administrator Policy, or you may want to use the web-configured Administrator Policy as a starting point for a more advanced CPL script.
The CPL script must be in a format supported by the VCS. The Administrator Policy page allows you to download the XML schemas which are used to check the script before it is uploaded to the VCS, so you can check in advance that your CPL script is valid.
If you download a web-configured Administrator policy as a CPL script and then upload it back to the VCS without editing it, the VCS will recognise the file and automatically add each rule back into the Administrator Policy section of the web interface.
Select the new policy file
Enter the file name or Browse to the CPL script you wish to upload.
Show CPL XSD file
Downloads the XML schema used for the CPL script.
Once you have selected the file containing the CPL script, click here to upload it to the VCS.
Show CPL Extensions XSD file
For information on the CPL syntax and commands that are supported by the VCS, see CPL Reference.
Downloads the XML schema used for additional CPL elements supported by the VCS.
Show Policy file · Upload File

What is User Policy?
Process Overview
Recommendations When Deploying FindMe
User Policy is the set of rules that determines what happens to a call for a particular user or group when it is received by the TANDBERG VCS.
When the VCS receives a call for a particular alias, it checks to see whether User Policy has been enabled. If so, the VCS queries the User Policy Manager to see whether that alias is listed as a FindMe name. If so, the call is forwarded to the aliases according to configuration for that FindMe alias.
The FindMe name should be in the form of a URI, and should • be the individual’s primary URI.
Endpoints should not register with an alias that is the • same as an existing FindMe name. You can prevent this by including all FindMe names on the Deny List.
The VCS’s User Policy is also known as TANDBERG FindMe™. This feature lets you assign a single “FindMe” name to individuals or groups in your enterprise. Users can determine which devices will be called when their FindMe name is dialled, and can also specify what happens if those devices are busy or go unanswered.
If User Policy has not been enabled, or the alias is not present in the User Policy Manager, the VCS will continue to search for the alias in the usual manner, i.e. first locally and then sending the request out to neighbors.
Users at Example Corp. have a FindMe name in the format john.smith@example.com. Each of the user’s 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 john.smith.office@example.com and their home endpoint as john.smith.home@example.com. Both of these endpoints are included in the list of devices to ring when the FindMe name is dialed. The alias john.smith@example. com is added to the Deny List, to prevent an individual endpoint registering with that alias.
The FindMe feature means that potential callers can be given a single FindMe Alias on which they can contact an individual or group in your enterprise - callers won’t have to know details of all the devices on which that person or group might be available.
User Policy is invoked after any Administrator Policy configured on the VCS has been applied. See the Call Processing Diagram for more information.
Who Must do What Before FindMe™ Can Be Used?
User Policy Manager
When configuring their FindMe account, users are asked to specify the devices to which calls to their FindMe name will be routed.
FindMe™ is an optional feature on the VCS, and you must install the appropriate option key before it can be used. Contact your TANDBERG representative for more information.
The User Policy Manager is the application that manages the FindMe user accounts.
The VCS has its own User Policy Manager. However, you also have the option to use a User Policy Manager on a remote system.
It is possible to specify aliases and even other FindMe names as one or more of the devices. However, care must be taken in these situations to avoid circular configurations.
The following steps are required for the use of FindMe once the option has been installed:
The VCS administrator 1. enables and configures User Policy.
For this reason, we recommend that users specify the physical devices they wish to ring when their FindMe name is called, by entering the alias with which that device has registered.
The VCS administrator 2. creates a user account for each user or group who require a FindMe name.
The owner of the FindMe name 3. configures their account settings.
Example

Configuring User Policy Manager
To configure the User Policy Manager:
Determines whether or not User Policy will be enabled, and if so, the location of the User Policy Manager.
Off: User Policy is not enabled.
Local: User Policy is enabled and the VCS’s own User Policy Manager is used.
Remote: User Policy is enabled and a User Policy Manager located on another system is used. If you select this option, further configuration options will appear (see below).
The protocol used to connect to the remote User Policy Manager.
The IP address or domain name of the remote User Policy Manager.
The URL of the remote User Policy Manager.
The username used by the VCS to log in and query the remote User Policy Manager.
The password used by the VCS to log in and query the remote User Policy Manager.
Administrator Policy will always be applied regardless of the User Policy mode.
Click here to save your changes.

About User Accounts
Creating a New User Account
FindMe user accounts must be created by the VCS Administrator before they can be accessed and configured by users.
VCS Configuration > Policy > User Accounts • . You will be taken to the User Accounts page. Select New. You will be taken to the Create User Account page.
Each user account is accessed via a username and password associated with a specific FindMe name.
The name of the user for whom you are creating an account. This is the name they will use to log in when configuring their FindMe options.
The FindMe name on which the user can be contacted.
The FindMe name can be any string of up to 60 characters. However, not all endpoints are able to dial aliases with spaces or other non- alphanumeric characters so we recommend that these are not used in your FindMe names.
The password to be used along with the Username when logging into this account.
Users will be able to change the password for their account once they have logged in.
Once a new account has been created, calls to the FindMe name for that account will be rejected until one or more devices have been configured for that account.
Retype the password. Save
Click here to create the new account and return to the User Accounts page.
Click here to return to the User Accounts page without creating the new account.

Changing a User Password
You can change a password on behalf of a user without knowing their existing password. This is useful when the user has forgotten their password.
Type the new password to be used along with the Username when logging into this account.
To change the password:
VCS Configuration > Policy > User Accounts • . You will be taken to the User Accounts page. Click on the user account whose password you wish to change. You will be taken to the Edit User Account page.
Retype the new password.
To view the configuration of an existing user account:
VCS Configuration > Policy > User Accounts • . You will be taken to the User Accounts page. Click on the user account whose password you wish to change. You will be taken to the Edit User Account page.
Click here to return to the User Accounts page without changing the password.
Click here to delete any existing configuration for this FindMe name. This will have the effect that any calls to that FindMe name will be rejected until one or more devices are reconfigured for that account.
FindMe Configuration for...
This section shows you the current configuration for the user.
Click here to update the password and return to the User Accounts page.


Tick the box next to the account you wish to delete.
To select all the accounts, click on Select All.
VCS Configuration > Policy > User Accounts • . You will be taken to the User Accounts page.
A confirmation window will appear to ensure that you wish to proceed. Click OK to continue.

Accessing the FindMe Configuration Page
About FindMe™
To configure your FindMe user account, log in via a web browser as described below:
The FindMe feature allows you as an individual or part of a group to have a single name on which you can always be called, and you chose where calls to that name will be routed. You can also determine what happens if your first choices are either busy or unanswered after a certain period of time.
Go to the FindMe link provided to you by your system administrator.
For example, you could set up your individual FindMe name so that it will call you on your desktop endpoint first. If there’s no answer after 10 seconds it will divert the call to your mobile phone, and if your desktop phone is busy it will divert the call to your colleague’s desktop videophone.
This will take you to the Login page.
Select User Login.
Alternatively, you could have a single FindMe name for your team, and set it up so that all the team member’s desktop videophones will ring when anyone calls the FindMe name.
Each FindMe name has an associated user account. Your FindMe user account is set up by your system administrator. Once this has been done, you can log in to your account via a web interface and configure it with details of the device(s) on which you want to be contacted:
Enter the Username and Password provided to you by your System Administrator.
Select Login.
Individual versus Group FindMe
There are two types of FindMe names: individual and group.
The only difference between the two is what happens if one of the devices in the initial list is busy.
You will be taken to the FindMe page. From here you can configure your FindMe options as either an individual or a group.
For individuals, it is assumed that you will only be able to take calls on one device at a time, therefore if any devices in your Primary list are busy, the call will immediately divert to the device(s) in your Busy list.
For groups, it is assumed that more than one person is available to take calls, so the call will only divert to the device(s) in the Busy list if all devices in the Primary list are engaged.
FindMe User Accounts

!
If no devices are configured for a FindMe name, all calls to that name will be rejected.
List the all the device(s) that will ring when your FindMe name is first dialled.
If more than one device is listed here, they will all ring at the same time.
The username for this FindMe account.
Ring the primary devices
Select the amount of time in seconds you wish the devices in the Primary list to ring before the call is diverted. Alternatively, you can specify that the devices will ring until the caller hangs up.
The FindMe name being configured.
Select whether this FindMe name is to apply to an individual or a group of people. This will affect how calls are diverted to the Busy devices.
List all the device(s) that will ring if none of the devices in the Primary list are answered within the specified time.
If no devices are listed here, the caller will receive a “no answer” response if none of the Primary devices are answered.
Click here to change the password used to access your FindMe account. You will be taken to a new page where you can enter the new password.
If you have selected a Timeout period of ring until caller hangs up, you will not be able to list any devices here.
Ensure that none of the Primary devices are set to Autoanswer. If they are, the system will consider the call to have been answered when Autoanswer is initiated, and so it will not divert the call to any other devices.
Click here to exit the FindMe page.
Click here to update your FindMe account with any changes.
For an individual, list all the device(s) that will ring immediately if any of the devices in the Primary list are busy.
Adding a device to a list
For a group of people, list all the device(s) that will ring immediately if all of the devices in the Primary list are busy. (If some of the devices in the Primary list are busy, the rest will continue to ring for the specified time before the call will divert to the devices listed here.)
You can have up to five devices in each list. To add a device to any of the lists, enter one of the following in any of the available fields:
To remove a device from a list, delete it from the relevant field and click Save Changes.
If no devices are listed in this section, the caller will get a busy response if any/all of the Primary devices are busy.

About Searches
About Local Alias Transforms
Local zone alias transforms will be applied prior to any possible CPL modification and Zone transforms. These alias transforms will not have any effect on aliases presented in GRQ or RRQ messages.
One of the VCS’s functions is to process incoming requests to search for a particular alias. These search requests are received from
The local alias transform function allows you to modify the alias in an incoming search request. The transformation is applied before conducting the search locally. It applies to all incoming search requests other than those received from Alternates. It applies to requests received from locally registered endpoints and from neighboring VCSs.
Each local alias transform defines a string against which an alias is compared, and the changes to make to the alias if it matches that string.
The VCS searches its local zone and that of its Alternates to see if the alias belongs to any 1. endpoints registered directly to it or its Alternates.
Once the alias has been transformed in this way, it remains changed. and all further processing is applied to the new alias.
If it is not found locally, the VCS forwards the search request to its neighboring zones. Which 2. zones are searched, and in what order, depends on the zone search settings for that zone.
If you add a new transform that has the same priority as an existing transform, all transforms with a lower priority will be moved down the list, 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, then you will get an error message.
Up to 100 local alias 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 checks or transformations of the new alias will take place. The new alias is then searched for locally.
The VCS allows you to transform the alias in a search request if it matches certain criteria. This transformation can be applied to the alias at two points in the search process:
as soon as it is received and before it is searched for locall • y
before sending a search request out to neighboring zone • s.
You can transform the alias by removing or replacing its prefix, suffix, or the entire string, and by the use of regular expressions.
If the new alias is not found locally, the search is expanded to neighbors. It is always the transformed alias, not the alias that was received originally, that is queried for.
When an • Alternate is queried, it will identify that the request has come from one of its own Alternates and will search for the transformed alias locally without applying any further transforms.
All Alternates should be configured identically, including any local zone transforms. However, this means that an alias that was not found locally would be transformed twice - once before the local zone was searched and again after being sent to the Alternate, before the Alternate searched its own local zone. To prevent this, a VCS is able to determine whether a search request has come from one of its Alternates and if so will not transform the alias before searching for it locally.
When • neighbors are queried, you can specify further transforms to be applied prior to sending out the search request. The neighbor’s configuration may also be such that it will transform the alias before searching for it locally.

Configuring Local Alias Transforms
To configure local alias transforms:
Specifies the pattern against which the alias is compared.
Assigns a priority to this transform. Transforms are applied in order of priority, and the priority must be unique for each transform.
Determines the way in which the string must match the alias. Options are:
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.
Determines how the matched part of the alias will be modified. Options are:
Replace string (applies only if Pattern Behavior is set to Replace)
Strip: the matching prefix or suffix will be removed from the alias.
Local transforms support the use of Regular Expressions in both the Pattern String and Replace String fields. See the Appendix Regular Expression Reference for more information.
Click here to save the transform and return to the Transforms page.
Click here to return to the Transforms page without adding the new transform.
Replace: the matching part of the alias will be substituted with the text in the Replace String.
Specifies the string to be used as a substitution for the part of the alias that matched the pattern.

About Zone Searching
About Zone Transforms
Zone Search and Transform Process
The VCS allows you to filter the search requests sent to each zone, and prioritize the order in which zones are searched. This allows you to reduce the potential number of search requests sent out, and speed up the search process.
The VCS allows you to change the alias being searched for before a search request is sent out to a particular zone. This feature uses the PatternMatch mode of the zone search function.
Zones are queried when an alias has not been found locally. The search and transform process is as follows:
The VCS looks at all matches for all zones to find all those 1. with either:
The VCS uses the concept of zone “matches” when filtering search requests to zones. Each zone has up to five configurable “matches” available to it. Each match is assigned a Mode and Priority (described below). The combination of the two determines if and when that zone will be queried.
To set up a zone transform, you must:
a • Mode of PatternMatch and a Pattern String that matches the alias being searched for.
These matches are listed in order of the 2. Priority that has been assigned to them.
If there are any duplicates in the list, the entry with the lower 3. Priority is removed. (This applies to a zone with the same pattern string and the same transform but different priorities.)
If there is a zone which has an 4. AlwaysMatch as well as a PatternMatch with no transforms, the PatternMatch is removed from the list.
The match Mode allows you to specify whether and how you will filter requests to the zone. Alternatively, you can use this mode to prevent search requests from ever being sent to the zone.
Each zone has up to five configurable matches. This means that you can specify up to five different transforms for each zone. This could be:
The Mode options are:
All zones with a Priority 1 match on the list are queried. For 5. AlwaysMatch matches, the query will use the original alias; for PatternMatch matches the query will use the alias specified by the transform rules.
If the alias is found, the call will be forwarded to that zone. 6. If the alias is found by more than one zone, the call will be forwarded to the zone that responded first.
Disabled • : never query the zone (this mode does not need a corresponding Priority option).
If the alias is not found, all zones with a Priority 2 match are 7. queried as per steps 5 and 6.
The process is repeated until either: 8.
The zone searching feature and the zone transforms feature both make use of the PatternMatch mode. You can use these two features together or separately.
The match Priority allows you to specify when in the search process that zone will be queried. Search requests are sent to all zones with a Priority 1 match first, followed by all zones with Priority 2 matches, and so on.
The remainder of this section:
explains how to • configure zone searches and transforms
gives some • examples of how zone searches and transforms could be used together. It is possible for the same priority to be given to more than one match, either in the same zone or in different zones. In this case, all zones with that match priority will be queried at the same time.
Mode · Priority
![Page 109 of the TANDBERG Security Camera user manual — xConfiguration Zones Zone [1..200] • Match [1..5]](/cdn/reader/9a/9a94646fb4a881d35b1a0f9d56871769188836c2936deddce87dcd3ebd834bb3/images/page-109.webp?w=400)
Configuring Zone Searches and Transforms
Determines if and when a query will be sent to this zone. Options are:
To configure when a zone will be searched and any transforms that will be applied before the search request is sent:
AlwaysMatch: the zone will always be queried.
PatternMatch: the zone will only be queried if the alias queried for matches the specified Pattern String.
VCS Configuration > Zones • . You will be taken to the Zones page. Click on the zone you wish to configure. You will be taken to the Edit Zone page. Scroll down until you get to the Match1 section.
Disabled: this match is not used. If all 5 matches for a zone are disabled, the zone will never be queried.
Determines the order in which the zone will be sent a search request. Zones with priority 1 matches are searched first, followed by priority 2, and so on. More than one match can be assigned the same priority; in this case the matches will be queried simultaneously.
You can configure up to five different Matches (i.e. search/transform combinations) for each zone.
Pattern string (Applies only if the Mode is PatternMatch.)
Specifies the pattern against which the alias is compared.
When a new zone is created, by default Match1 will be set to AlwaysMatch with a Priority of 100. All remaining matches will be set to Disabled. This means that the zone will be queried for the original alias, with no transforms applied.
Pattern type (Applies only if the Mode is PatternMatch.)
Determines the way in which the string must match the alias. Options are:
Replace string (Applies only if the Mode is PatternMatch and Pattern Behavior is Replace.)
Pattern behavior (Applies only if the Mode is PatternMatch.)
Exact: the string must match the alias character for character.
Determines if and how the matched part of the alias will be modified. Options are:
Specifies the string to be used as a substitution for the part of the alias that matched the pattern.
Prefix: the string must appear at the beginning of the alias.
Zone transforms support the use of Regular Expressions in both the Pattern String and Replace String fields. See the Appendix Regular Expression Reference for more information.
Leave: the alias will not be modified.
Strip: the matching prefix or suffix will be removed from the alias.
Suffix: the string must appear at the end of the alias.
Regex: the string will be treated as a regular expression.
Replace: the matching part of the alias will be substituted with the text in the Replace String.
Mode · Priority · Default Settings

Combining Match Types and Priorities
Never Query a Zone
Always Query a Zone, Never Apply Transforms
To configure the zone so that it is never sent an alias search request (for example if you only want to receive incoming calls from this zone), set all 5 matches to a Mode of Disabled:
To configure the zone so that it is always sent search requests using the original alias, set Match 1 to AlwaysMatch with a Priority of 1:
By using both AlwaysMatch and PatternMatch matches in the same zone, and applying the same or different priorities to each match, you will have a great deal of flexibility in determining if and when the zone will be queried and whether any transforms will be applied. Some example configurations are given here.
The AlwaysMatch mode does not support alias transforms. Should you wish to always query a zone using a different alias to that received, you will need to use a mode of PatternMatch in combination with a regular expression.

Filter Queries to a Zone Without Transforming
It is possible to 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 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.
To achieve this, on your local VCS create and configure the zone representing the sales office VCS as shown:


You may wish 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 match with a mode of AlwaysMatch, and a second match with a mode of PatternMatch along with details of the transform to be applied. Both matches must be given the same Priority level.
For example, you may wish to query a neighbor zone for both a full URI and just the name (i.e. the URI with the domain removed).
To achieve this, on your local VCS configure the zone representing the neighbor VCS as shown:

Query a Zone for Two or More Transformed Aliases
Zones are queried in order of priority of the matches configured within them.
It is possible to configure a single zone with up to five PatternMatch matches, each with the same Priority and with an identical Pattern String to be matched, but each with a different replacement pattern. In this situation, the VCS will query that zone for each of the new aliases simultaneously. (Any duplicate aliases produced by the transforms will be removed prior to the search requests being sent out.)
If any of the new aliases are found by that zone, the call will be forwarded to the zone. It is then up to the controlling system to determine the alias to which the call will be forwarded.

Enabling URI Dialing URI Resolution Process via DNS
A URI address typically takes the form name@example.com, where name is the alias and example.com is the domain.
When a system is attempting to locate a destination URI address using the DNS system, the general process is as follows:
URI dialing is enabled separately for outgoing and incoming calls.
URI dialing can make use of DNS to enable endpoints registered with different systems to locate and call each other. With URI dialing, it is possible to find an endpoint by using DNS to locate the domain in the URI address and then query that domain for the alias.
The system will send a query (via its DNS server) for a SRV record for the 1. domain in the URI. If available, this SRV record will return information about the authoritative H.323 gatekeeper for that domain (e.g. its FQDN and listening port). The system will then send out another query for an A/AAAA record for the FQDN returned in the SRV record. If available, this will return the actual IP address of the gatekeeper. Once its IP address has been discovered, the system will query that gatekeeper for the URI.
To enable endpoints registered to your VCS to place calls to non- locally registered endpoints directly using URI dialing, you must:
configure at least one DNS Serve • r.
Without URI dialing, you would need to neighbor all the systems to each other in order for one system to be able to locate an endpoint registered to another system. This does not scale well as the number of systems grows. It is also inconvenient for making one-off calls to endpoints registered with previously unknown systems.
This is described in the section Configuring URI dialing for outgoing calls.
If a relevant SRV record cannot be located, the system will fall back to looking 2. 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.
To enable endpoints registered to your VCS to receive calls directly from non-locally registered endpoints using URI dialing, you must:
H.323 endpoints should register with the VCS using a URI address in order to be reachable using URI dialing. SIP endpoints always register with an AOR in the form of a URI.
The system will send a NAPTR query for the domain in the URI. If available, 1. the result set of this query will describe 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._tls., _sip._tcp. and _sip._udp. for that domain as if they had been returned from DNS.
This is described in the section Configuring URI dialing for Incoming calls.
The system will send SRV queries for each result returned from the NAPTR 2. record lookup. A prioritized list of A/AAAA records returned is built. If no SRV records are found then the domain name from the URI is added as the only entry in list of A/AAAA records to lookup.
To configure your system so that you can place and receive calls using URI dialing through a firewall, see the section URI Dialing and firewall traversal.
The system will send an A/AAAA record query for each name record returned by 3. 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.
There is an exception to the requirement for H.323 endpoints to register with the VCS using a URI address in order to be reachable using URI dialing. This is the case where endpoints register with an alias, and incoming calls are made to alias@domain.com. A local transform is then configured to strip the @domain, and the search is made locally for alias.
If a DNS zone and/or a DNS server have not been configured on the local VCS, calls to non-locally registered endpoints could still be placed if the local VCS is neighbored with another VCS that has been configured for DNS. In this case, any URI dialed calls will go via the neighbor. This configuration is useful if you want all URI dialing to be made via one particular system, e.g. a VCS Expressway.
Without DNS, calls made using URI dialing will still be placed if the destination endpoint is locally registered, or registered to a neighbor system as locating these this does not require the use of DNS.
Outgoing Calls · Incoming Calls · Firewall Traversal Calls

Process
Configuring Matches for DNS Zones
When a user places a call using URI dialing, they will typically dial an address in the form name@ example.com from their endpoint. Below is the process that is followed when a URI address is dialed from an endpoint registered with your VCS:
If you wish locally registered endpoints to be able to place URI calls via the VCS, then at a minimum you should configure a DNS zone with a match that has a Mode of AlwaysMatch. This will result in DNS always being queried, but will mean it is queried for all aliases, not just URI addresses.
The VCS will check its own list of registrations, and those of its Alternates, to see if the address 1. is registered locally.
To filter the queries sent to the DNS server:
If the address is not registered locally, the VCS will check all its zones to see if any of them are 2. configured with either:
To set up further filters, configure the remaining matches in the same DNS zone. You don’t need to create new DNS zones unless you want to configure more than the maximum of 5 matches.
If one or more of the zones that contain a match are neighbor zones, the neighbor will be queried 3. for the URI. If the neighbor supports URI dialing, it may route the call itself.
You should create separate DNS zones if you want to filter based on the protocol (SIP or H.323) or hop count to be used.
If one or more of the zones that contain a match are DNS zones, this will trigger the VCS to 4. attempt 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 DNS resolution process.
If the domain part of the URI address was resolved successfully using an H.323 Location SRV 5. record (i.e. for _ h323ls) then the address returned is queried via an LRQ for the full URI address.
If the domain part of the URI address was resolved using an H.323 Call SRV record (i.e. for 6. _ h323cs) or an A/AAAA record lookup then the call is routed directly to the IP address returned in that record. An exception to this is where the original dial string has a port specified (e.g. user@example.com:1720) in which case the address returned is queried via an LRQ for the full URI address.
If the domain part of the URI address was resolved successfully the request is forwarded to 7. those address(es).

Adding and Configuring DNS Zones
In order for locally registered endpoints to use URI dialing through the VCS, you must configure at least one DNS zone. To do this:
Assigns a name to this zone.
For DNS zones, this will be DNS.
Specifies the hop count to be used when sending an alias search request to this zone. 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.
Determines whether or not SIP calls will be allowed to this zone. Normal zone pattern matching and prioritization rules will apply to DNS zones.
H.323 mode
Determines whether or not H.323 calls will be allowed to this zone.
When dialing by URI, the hop count used is that configured for the DNS zone that matches the URI address.
If there is no DNS zone configured that matches the URI address, then the query may be forwarded to a neighbor. In this case, the hop count used will be that configured for the neighbor zone.
These sections allow you to specify any filtering criteria you wish to apply to this zone.
See Configuring Matches for DNS zones for full information on how the Match options can be used.

Configuring DNS Servers
Address 1 to Address 5
To configure the DNS servers to be used by the VCS when querying DNS:
Enter the IP address(es) 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.
In order for endpoints registered to the local VCS to make outgoing calls using URI dialing to endpoints that are not registered to the local VCS or one of its neighbors, you must configure at least one DNS server for the VCS to query. For resilience, you can specify up to five DNS servers.
The DNS server(s) configured here are used as part of both the ENUM dialing and URI dialing processes.
Without DNS, calls made using URI dialing will still be placed if the destination endpoint is locally registered or registered to a neighbor system as locating these URIs does not require the use of DNS.

Types of DNS Records Required
SRV Record Format
The ability of the VCS to receive incoming calls made via URI dialing relies on the presence of DNS records for each domain the VCS is hosting.
The format of SRV records is defined by RFC 2782 [3] as:
_ Service. _ Proto.Name TTL Class SRV Priority Weight Port Target
For the VCS, these will be as follows:
These records can be of various types including:
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.
Configuring SIP SRV Records
Annex O of H.323 [15] 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.
RFC 3263 [16] describes the DNS procedures used to resolve a SIP URI into the IP address, port, and transport protocol of the next hop to contact.
You should provide an SRV or NAPTR record for each combination of domain hosted and protocol and transport type enabled on the VCS.
The VCS supports two types of SRV record as defined by this Annex. These are Location and Call, with _ Service set to _ h323ls and _ h323cs respectively.
If you wish the VCS to be contactable via SIP URI dialing, you should configure an SRV record for each SIP transport protocol enabled on the VCS (i.e. UDP, TCP or TLS) as follows:
If you wish the VCS to be contactable via H.323 URI dialing, you should provide at least a Location SRV record, as it provides the most flexibility and the simplest configuration.
For each domain hosted by the VCS, you should configure a Location SRV record as follows:
When an incoming call has been placed using URI dialing, the VCS will have been located by the calling system via one of the DNS record lookups described above. The VCS will receive the request containing the dialled URI in the form user@example. com. The VCS will then check its local registrations and FindMe names and if any are an exact match, the call will be routed to the appropriate device(s).
Call SRV records (and A/AAAA records) are intended primarily for use by endpoints which cannot participate in a location transaction, exchanging LRQ and LCF. The configuration of a Call SRV record should be as follows:
Location SRV Records · Call SRV Records

URI Dialing and Firewall Traversal
Example DNS Record Configuration
Recommended Configuration
A company with the domain name example.com wants to enable incoming H.323 and SIP calls using URI addresses in the format user@example.com. The VCS hosting the domain has the FQDN vcs.example.com.
If URI dialing is being used in conjunction with firewall traversal, DNS zones and DNS Servers 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 or servers configured. This will ensure that any outgoing URI calls made by endpoints registered with the VCS will be routed through the VCS Expressway.
Their DNS records would typically be as follows:
In addition, the DNS records should be configured with the address of the VCS Expressway as the authoritative gatekeeper/proxy for the enterprise (see the Appendix DNS Configuration). This ensures that incoming calls placed using URI dialing enter the enterprise through the VCS Expressway, allowing successful traversal of the firewall.
SRV record for • _ sip. _ udp.example.com returns vcs.example.com
SRV record for • _ sip. _ tcp.example.com returns vcs.example.com
SRV record for • _ sips. _ tcp.example.com returns vcs.example.com
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 Appendix DNS Configuration.
In order for locally registered endpoints to be reached using URI dialing, they must register using a full URI. This applies to both SIP and H.323 endpoints. If endpoints do not register using a full URI, they will be discoverable only by the VCS to which they are registered, and any neighbor VCSs.
Several mechanisms could have been used to locate the VCS. You may wish to enable calls placed to user@ to be routed to an existing registration for user@example.com. In this case you would configure a Local Zone Transform that would strip the IP address of the VCS from the incoming URI and replace it with the domain name of example.com.

Process Enabling 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.
When a VCS is attempting to dial a destination endpoint using ENUM, the general process is as follows:
ENUM dialing is enabled separately for incoming and outgoing calls.
The user dials the E.164 number from their endpoint. 1.
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 VCS converts the E.164 number into an ENUM domain as 2. follows:
To allow locally registered endpoints to dial out to other endpoints using ENUM, you must
the digits are reversed and separated by a dot a.
the name of the domain that is hosting the NAPTR records b.
The ENUM dialing facility allows you to retain the flexibility of URI dialing whilst having the simplicity of being called using just a number - particularly important if any of your callers are restricted to dialing via a numeric keypad.
for that E.164 number is added as a suffix.
DNS is then queried for the resulting ENUM domain. 3.
If a NAPTR record exists for that ENUM domain, this will 4. advise how the number should be converted into one (or possibly more) H.323/SIP URIs.
The VCS begins the search again, this time for the converted 5. URI as per the URI dialing process. Note that this is considered to be a completely new search, and so local transforms and administrator policy will therefore apply.
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 section Configuring ENUM dialing for incoming calls for instructions on how to do this.
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 via DNS.
If an ENUM zone and/or 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.
Outgoing Calls · Incoming Calls

Prerequisites
Process
Example
In order for a local endpoint to be able to dial another endpoint using ENUM via your VCS, the following three conditions must be met:
Below is the process that is followed when an ENUM (E.164) number is dialed from an endpoint registered with your VCS:
In this example, we wish to call Fred at Example Corp. Fred’s endpoint is actually registered with the URI fred@example.com, 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.
The user dials the E.164 number from their endpoint. 1.
There must be a NAPTR record available in DNS that maps 1. the called endpoint’s 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 wish the endpoints in their enterprise to be contactable via ENUM dialing.
The VCS initiates a search for the E.164 number as dialed. 2. It follows the usual alias search process, first applying any local zone transforms, then searching local and Alternate registrations and FindMe names for the E.164 number.
We know that the NAPTR record for example.com uses the DNS domain of e164.arpa.
If the E.164 number is not found locally, the VCS will check all 3. its zones to see if any of them are configured with either:
We create an ENUM zone on our local VCS with a 1. DNS suffix of e164.arpa.
You must 2. 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.
We configure this zone with a pattern match mode of 2. AlwaysMatch, so that ENUM will always be queried regardless of the format of the alias being searched for.
a • PatternMatch with pattern that matches the E.164 number.
We dial 3. 44123456789 from our endpoint.
These zones will then be queried in priority order.
You must 3. 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).
If one or more of the zones that contain a match is a neighbor 4. zone, the neighbor will be queried for the E.164 number. If the neighbor supports ENUM dialing, it may route the call itself.
The VCS initiates a search for a registration of 4. 44 118 123 456. Because the ENUM zone we have configured has a match mode of AlwaysMatch, it is queried at the same time as any other zones with a matching priority.
Once 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 via a DNS lookup.
Because the zone being queried is an ENUM zone, the VCS is 5. automatically triggered to transform the number into an ENUM domain as follows:
If one or more of the zones that contain a match is an 5. ENUM zone, this will trigger the VCS to attempt 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:
the digits are reversed and separated by a dot: a.
9.8.7.6.5.4.3.2.1.4.4
the b. DNS Suffix configured for this ENUM zone, e164.arpa, is appended.
the digits are reversed and separated by a dot a.
the b. DNS Suffix configured for that ENUM zone is appended.
This results in a transformed domain of 9.8.7.6.5.4.3.2.1.4.4.e164.arpa.
DNS is then queried for the resulting ENUM domain. 6.
If the DNS server finds at that ENUM domain a NAPTR record 7. that matches the transformed E.164 number (i.e., after it has been reversed and separated by a dot), it returns the associated URI to the VCS.
DNS is then queried for that ENUM domain. 6.
The DNS server finds the domain and returns the information 7. in the associated NAPTR record. This tells the VCS that the E.164 number we have dialed is mapped to the SIP URI of fred@example.com.
The VCS then initiates a new search for that URI (maintaining 8. the existing hop count). The VCS starts at the beginning of the search process (i.e. applying any local zone transforms, then searching locally, then searching zones). From this point, as it is now searching for a SIP/H.323 URI, the process for URI Dialing is followed.
The VCS then starts another search, this time for 8. fred@ example.com. From this point the process for URI Dialing is followed, and results in the call being forwarded to Fred’s endpoint.

Configuring Matches for ENUM Zones
Configuring Transforms for ENUM Zones
If you wish locally registered endpoints to be able to make ENUM calls via the VCS, then at a minimum you should configure an ENUM zone with:
You can configure transforms for ENUM zones in the same way as any other zones (see Zone Searching and Transforming for full information).
If there are any transforms configured for an ENUM zone, these will be applied prior to the number being converted to an ENUM domain.
a • DNS suffix of e164.arpa (the domain specified by the ENUM standard).
This will result in DNS always being queried for all aliases, not just ENUMs. It will also mean that ENUM dialing will only be successful if the enterprise being dialed uses the e164.arpa 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 that has a Match configured as follows:
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 wish to dial.
Once these ENUM zones have been created, you can filter the queries that are sent to each as follows:
Pattern string • of 8(\d{4})
configure a match that has a • Mode of PatternMatch
use the • Pattern string and Pattern type fields to define the aliases that will trigger an ENUM lookup.
Pattern behavior • of Replace
Replace string • of 44123123(\1)
With this configuration, it will be the resulting string (i.e. 44123123xxxx) that will then be converted into an ENUM domain and queried for via DNS.
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 that has a Match configured as follows:
Pattern string • of 44
Pattern type • of Prefix.
This will result in an ENUM query being sent to that zone only when someone dials a number starting with 44.
To verify that you have configured your outward ENUM dialing correctly, use the xCommand Locate command to try and resolve an E.164 alias.
Example · Example

Configuring ENUM Zones
In order for locally registered endpoints to use ENUM dialing, you must configure an ENUM zone for each ENUM service used by remote endpoints. To do this:
Assigns a name to this zone.
For ENUM zones, this will be ENUM.
VCS Configuration > Zones • . You will be taken to the Zones page.
Click • New. You will be taken to the Create Zone page.
Specifies the hop count to be used when sending an alias search request to this zone. 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.
Enter the zone • Name and select a Type of ENUM.
Click • Create Zone. You will be taken to the Edit Zone page.
xConfiguration Zones Zone [1..200 • ]
The DNS zone that is to be queried for a NAPTR record. This suffix is appended to the transformed E.164 number in an attempt to find a matching NAPTR record.
Determines whether or not SIP records will be looked up for this zone.
H.323 mode
Determines whether or not H.323 records will be looked up for this zone.
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.
These sections allow you to specify any filtering criteria and/or transforms you wish to apply to this zone. See Configuring Matches for ENUM zones and Configuring Transforms for ENUM zones for full information on how the Match options can be applied.
Normal zone pattern matching and prioritization rules will apply to ENUM zones.

Configuring DNS Servers
Address 1 to Address 5
To configure the DNS servers to be used by the VCS when querying DNS:
Enter the IP address(es) of up to 5 DNS servers that the VCS will query when attempting to locate a domain.
System Configuration > DNS • . You will be taken to the DNS page.
In order for endpoints registered to the VCS to make outgoing calls using ENUM dialing, you must configure at least one DNS server for the VCS to query. For resilience, you can specify up to five DNS servers.
The DNS server(s) configured via this page are used as part of both the ENUM dialing and URI dialing processes.

Prerequisites
Configuring DNS NAPTR Records
Example
In order 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 via ENUM dialing.
ENUM relies on the presence of NAPTR records, as defined by RFC 2915 [7]. These are used to obtain an H.323 or SIP URI from an E.164 number.
For example, the record:
IN NAPTR 10 100 "u" "E2U+h323" "!^(.*)$!h323:\1@ • example.com!" . would be interpreted as follows:
The record format that the VCS supports is:
10 • is the order
100 • is the preference
where:
order • and preference determine the order in which NAPTR records will be 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.
!^(.*)$!h323:\[email protected]! • describes the conversion:
! • is a field separator
ENUM relies on the presence of NAPTR records to provide the mapping between E.164 numbers and their SIP/H.323 URIs.
the first field represents the string to be converted. In this • example, ^(.*)$ represents the entire E.164 number
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.
RFC 3761 [8], 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 wish 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
the second field represents the H.323 URI that will be • generated. In this example, h323:\1@example.com states that the E.164 number will be concatenated with @example.com. For example, 1234 will be mapped to 1234@example.com.
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 URI.
. • shows that the replacement field has not been used.
replacement • is not currently used by the VCS and should be set to . (i.e. 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 [8],

An unregistered endpoint is any device that is not registered with an H.323 gatekeeper or SIP Registrar (e.g. VCS, gatekeeper or Border Controller). Although most calls are made between endpoints each registered with such a system, it is sometimes necessary to place a call to, or receive a call from, an unregistered endpoint.
An unregistered endpoint (one that is not registered to any system) can call an endpoint registered with the local VCS.
If there are no firewalls between the unregistered endpoint and the locally registered endpoint, it is possible for the caller to place the call by dialing the locally registered endpoint’s IP address. However, we do not recommend that callers are given IP addresses to use as the call may not always be successful (for example if the IP address is private).
Instead, we recommend that callers from unregistered endpoints dial the IP address or the domain name (if configured) of the local VCS, prefixed by the alias they wish to call (for example, [email protected]). The VCS will then place the call as normal.
Overview
To configure how the VCS will behave when receiving a call for an IP address that is not registered locally:
Calls can be placed from an endpoint registered to the local VCS to an endpoint that is not registered with any system in two ways:
VCS Configuration > Calls • You will be taken to the Calls page.
Calls to Unknown IP Addresses
Determines the way in which the VCS will manage calls to IP addresses which are not registered with it or one of its neighbors.
Direct: A locally registered endpoint will be allowed to make the call to the 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 the call the VCS will check to see if the IP address belongs to one of its locally registered H.323 endpoints. If so, it will allow the call. If not, it will query its neighbors for the remote address. If the neighbor’s configuration allows it to connect a call to that alias, the VCS will pass the call to that neighbor for completion.
When the VCS Expressway is neighbored with an 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:
The call will go from the endpoint to the VCS Control with which it is registered. 1.
Since the IP address being called is not registered to that VCS, and its 2. 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 Control’s behalf.
Off: This will not allow any endpoint registered locally to the VCS to call an IP address of any system not also registered locally to that VCS.
The VCS Expressway receives the call and since its 3. Calls to unknown IP addresses setting is Direct, it will make the call directly to the called IP address.

Configuration Example Usage
It is possible for the VCS to receive a call that is destined for it but which does not specify an alias. This could be for one of the following reasons:
To configure the Fallback Alias:
You may wish to configure your Fallback Alias to be that of your receptionist, so that all calls that do not specify an alias will still be answered personally and can then be redirected appropriately.
VCS Configuration > Calls • . You will be taken to the Calls page.
the caller has dialled the IP address of the • VCS directly
For example, Example Inc. has the domain of example.com. The endpoint at reception has the alias reception@example.com.
the caller has dialled the domain name • without giving an alias as a prefix
They configure their VCS with a fallback alias of reception@example.com. This means that any calls made directly to example.com (i.e. without being prefixed by an alias), are forwarded to reception@example.com, where the receptionist answers the call and directs it appropriately.
the caller has dialled the IP address or • domain name of the VCS prefixed by the VCS’s system name as an alias.
Normally such calls would be disconnected. However, the VCS allows you to specify an alias to which all such calls should be routed. This alias is known as the Fallback Alias.
Some endpoints do not allow users to enter an alias and an IP address to which the call should be placed.
If no fallback alias is configured, calls that do not specify an alias will be disconnected.
Click here to save your changes.
Enter the alias to which you want to forward all calls that do not already specify an alias.
Save · Fallback alias

The VCS provides a third party call control API. Currently this API supports the following feature:
Each call that passes through the VCS is assigned a call ID number and a call serial number, both of which can be referenced when disconnecting a call via the CLI.
To control calls using the CLI, you must reference the call using either its call ID or serial number. These can be obtained using the command:
disconnecting a call. •
The VCS assigns each call currently in progress a different call ID number. The 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 an ID of 1, the next call will be assigned an ID of 2. If call 1 is then disconnected, the third call to be made will be assigned an ID of 1.
This will return details of each call currently in progress in order of their call ID number. The second line of each entry will list the call serial number.
The call ID number is not therefore a unique identifier: while no two calls in progress at the same time will have the same call ID number, the same number will be assigned to more than one call over time.
The VCS assigns a unique serial number to every call passing through it. No two calls on a VCS will ever have the same serial number. However, a single call passing through a number of VCSs will be identified by a different serial number on each system.

The VCS web UI does not use the call ID number. Calls are identified using their call serial number only.
Call ID number · Call serial number

Disconnecting a Call via the CLI
To disconnect one or more existing call via the web interface:
To disconnect an existing call using the CLI, you must first obtain either the call ID number or the call serial number. Then use either one of the following commands as appropriate:
Status > Calls • . You will be taken to the Calls page.
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.
The call disconnection API 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 will actually disconnect the call.
For 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.
Endpoints that support RFC 4028 [14] have a call refresh timer which should cause them to clear the resources of any hung SIP calls after a certain period of time. This includes all TANDBERG endpoints.
Check the box next to the call(s) you wish to terminate and select Disconnect.
Disconnect


This section describes the pages that appear under the Local Zone and Bandwidth sub-menus of the VCS Configuration menu in the web interface.
These pages allow you to control the bandwidth that is used for calls within your local zone, as well as calls out to other zones.

The TANDBERG 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 applying limits to the bandwidth that can be used:
The diagram below shows a typical network deployment:
This section describes the different types of subzones and how to add and configure them, and explains how to use Links and Pipes to apply bandwidth controls between subzones and zones.
HOME OFFICE
INTERNET
Pipe A Pipe B
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.

About the Traversal Subzone
All endpoints registered with the VCS are part of its Local Zone.
The Traversal Subzone is a conceptual subzone. No endpoints can be registered to the Traversal Subzone; its sole purpose is to allow for the control of bandwidth used by traversal calls.
The Local Zone is made up of two or more subzones. The first two subzones are automatically created for you. These are the Default Subzone and the Traversal Subzone. You can create and configure further subzones manually on the basis of endpoints’ IP addresses: when an endpoint registers with the VCS its IP address is checked and it is assigned to the appropriate subzone.
All traversal calls are deemed to 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/ or on a per-call basis.
The main purpose of all three types of subzones is to enable you to control the bandwidth used by various parts of your network.
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.
When an endpoint registers with the VCS, its IP address is checked and it is assigned to the appropriate subzone. If no subzones have been created, or the endpoint’s IP address does not match any of the configured subzones, it will be assigned to the Default Subzone.
Traversal calls are always one of the following:
The use of a Default Subzone on its own (i.e. without any other manually configured subzones) is suitable only if you have uniform bandwidth available between all your endpoints. However, it is possible for a Local Zone to contain two or more different networks with different bandwidth limitations. In this situation, you should configure separate subzones for each different part of the network.
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 a series of VCSs. Some of these systems may just take the signaling, in which case the call will be a non-traversal call for that VCS. Other systems 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.
A subzone is defined by specifying a range of IP addresses. The VCS allocates endpoints to a subzone based on their IP address. You specify which IP addresses are associated with the subzone by configuring up to 5 subnets for that subzone.
The VCS is shipped with the Default Subzone and Traversal Subzone (and Default Zone) already created, and with links between the three. You may delete or amend these default links if you need to model restrictions of your network.
If any of these links have been deleted, they may be automatically restored via:
Traversal calls between two endpoints within a single subzone on the VCS must, like all traversal calls, pass through the VCS’s Traversal Subzone. This means that such calls will consume an amount of bandwidth from the originating subzone’s 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.
If an endpoint’s IP address matches more than one subnet, it will be allocated to the subnet with the narrowest range.
To restore these links via the web interface, you must recreate them manually. See Creating Links for instructions on how to do this.
In addition, since this call passes through the Traversal Subzone, it will consume an amount of bandwidth from the Traversal Subzone equal to that of the call.

To add a new subzone:
Enter the name you wish to assign to the subzone. You will refer to this name when creating Links.

Enter the IP address of the subnet. In conjunction with the Prefix, this will define the range of IP addresses that will belong to this subzone.
Up to 4 further subnets can be configured once the subzone has been created via the Edit Subzone page.
Enter the number of bits of the Subnet IP Address which must match for an IP address to belong in this subzone.
This shows the range of IP addresses that will be allocated to this subzone, based on the combination of the subnet address and prefix length that have been configured.
See Applying Bandwidth Limitations to Subzones for a description of these fields.
Click here to create the subzone and return to the subzones page.

To configure a subzone:
Enter the name you wish to assign to the subzone. You will refer to this name when creating Links and Pipes.
Enter the subnet IP Address and Prefix, This will define the range of IP addresses that will belong to the first subnet in this subzone.
This shows the range of IP addresses that will be allocated to this subzone, based on the combination of the subnet address and prefix length that have been configured.
Subnet 2 - 5
Use these fields to define up to 4 further subnets for this Subzone.
See Applying Bandwidth Limitations to Subzones for a description of these fields.
Click here to save your changes.

Types of Limitations
How Different Bandwidth Limitations are Managed
You can apply bandwidth limits to the Default Subzone, Traversal Subzone and all manually configured subzones. The types of limitations you can apply vary depending on the type of subzone, as follows:
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.
Limitation Description Can be applied to
Total Limits the total concurrent bandwidth being used by all endpoints in the subzone at any one time. In the case of the Traversal Subzone, this is the maximum bandwidth available for all concurrent traversal calls.
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 128, any calls between the two subzones will still be limited to 128kbps.
Calls entirely within...
Limits the bandwidth of any individual call between two endpoints within the subzone.
Calls into our out of...
Limits the bandwidth of any individual call between an endpoint in the subzone, and an endpoint in another subzone or zone.
Calls handled by...
The maximum bandwidth available to any individual traversal call.
For all these settings, a bandwidth mode of:
NoBandwidth • will mean that no bandwidth is allocated and therefore no calls can be made.
Limited • will mean that limits are applied. You must also enter a value in the corresponding bandwidth (kbps) field.
Unlimited • will mean that no restrictions will be 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.
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 call, pass through the Traversal Subzone. This means that such calls will consume an amount of bandwidth from the originating subzone’s 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.
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 both subzone bandwidth limits and pipe limits), the lowest limit will always apply to that call.
In addition, since this call passes through the Traversal Subzone, it will consume an amount of bandwidth from the Traversal Subzone equal to that of the call.

Creating Links
Subzones are connected to other subzones and zones via links. 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.
Enter the name you wish to assign to this link.
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.
Node 1, Node 2
Select the names of the two subzones, or the subzone and zone between which you wish to create a link.
To create a new link:
Pipe 1, Pipe 2
If you wish to apply bandwidth limitations to this link, select the pipe(s) to be applied.
For more information, see Applying Pipes to Links.
If a subzone has no links configured, then endpoints within the subzone will only be able to call other endpoints within the same subzone. For this reason, when a subzone is created, it is automatically given certain links. See Default Links for more information.
Click here to create the link and return to the Links page.
Name · Create Link


Enter the name you wish to assign to this link.
Select the names of the two subzones, or the subzone and zone between which you wish to create a link.
If you wish to apply bandwidth limitations to this link, select the pipe(s) to be applied.
For more information, see Applying Pipes to Links.
Click here to return to the Links page without saving your changes.

About Default Links
Pre-Configured Links
Automatically Created Links
If a subzone has no links configured, then endpoints within the subzone will only be 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.
The VCS is shipped with the Default Subzone, Traversal Subzone and Default Zone already created, and with links pre-configured between the three. You may delete or amend these default links if you need to model restrictions of your network.
Whenever a new subzone or zone is created, links are automatically created as follows:
New zone/subzone type Default links are created to...
If any of these links have been deleted, they may all be automatically restored via:
Subzone Default Subzone and Traversal Subzone
xCommand DefaultLinksAdd • To restore these links via the web interface, you must do so manually. See Creating Links for instructions on how to do this.
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
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.
You can edit any of these default links in the same way you would edit manually configured links. See Editing Links for more information.

Creating Pipes
It is possible 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.
Enter the name you wish to give to this pipe. You will refer to this name when creating links.
To apply these limits, you 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 pipe’s bandwidth limitations applied to them.
Determines whether there is a limit on the total concurrent bandwidth of this pipe.
Unlimited: no limitations are in place.
Limited: there is a limit in place; you must enter the limit in the field below.
See Applying Pipes to Links for more information.
NoBandwidth: there is no bandwidth available.
To create a pipe:
Total bandwidth limit (kbps)
Sets the limit on the total concurrent bandwidth of this pipe.
Determines whether there is a limit on the bandwidth of individual calls via this pipe.
Unlimited: no limitations are in place.
Limited: there is a limit in place; you must enter the limit in the field below.
NoBandwidth: there is no bandwidth available.
Per call bandwidth limit (kbps)
Sets the limit on the bandwidth of individual calls via this pipe.
Click here to create the pipe and return to the Pipes page.

Editing an Existing Pipe
To configure details of a pipe:
Enter the name you wish to give to this pipe. You will refer to this name when creating links.
Determines whether there is a limit on the total concurrent bandwidth of this pipe.
Unlimited: no limitations are in place.
Limited: there is a limit in place; you must enter the limit in the field below.
NoBandwidth: there is no bandwidth available.
Total bandwidth limit (kbps)
Sets the limit on the total concurrent bandwidth of this pipe.
Determines whether there is a limit on the bandwidth of individual calls via this pipe.
Unlimited: no limitations are in place.
Limited: there is a limit in place; you must enter the limit in the field below.
NoBandwidth: there is no bandwidth available.
Per call bandwidth (kbps)
Sets the limit on the bandwidth of individual calls via this pipe.
Click here to delete the pipe.
Click here to save the changes.

Pipes are used to restrict the bandwidth of a link. When a pipe is applied to a link, it will restrict the bandwidth of calls made between the two nodes of the link - the restrictions will 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 wish to model your network.
HOME OFFICE
INTERNET
One Pipe, One Link
Pipe A Pipe B
Applying a single pipe to a single link is useful when you wish to apply specific limits to calls between a subzone and another specific subzone or zone.
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 will allow you to configure the bandwidth options for calls in and out of that site.
In the diagram opposite, 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 Head Office subzone. In this case, Pipe A represents the Head Office’s broadband connection to the internet, and would have total and per-call restrictions placed on it.
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 opposite, the link between the Default Subzone and the Home Office Subzone has two pipes associated with it: Pipe A, which represents the Head Office’s broadband connection to the internet, and Pipe B, which represents the Home Office’s 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.

Configuring Default Call Bandwidth and Downspeeding
Usually, when a call is initiated the endpoint will include in the request the amount of bandwidth it wishes to use. For those cases where the endpoint has not specified the bandwidth, you can set the VCS to apply a default bandwidth value.
The default call bandwidth and downspeeding behavior are configured via:
Default call bandwidth (kbps)
Enter the bandwidth value to be used for calls for which no bandwidth value has been specified by the system that initiated the call.
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.
This value cannot be blank. The default value is 384 kbps.
Downspeeding can be configured so that it is applied in either or both of the following scenarios:
Downspeed per call mode
when the requested bandwidth for the call exceeds the lowest • per-call limit for the subzone or pipe(s)
Determines what will happen if the per-call bandwidth restrictions on a subzone or pipe mean that there is insufficient bandwidth available to place a call at the requested rate.
when placing the call at the requested bandwidth would mean • that the total bandwidth limits for that subzone or pipe(s) 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 was connected at a lower than requested speed. In this situation users will get one of the following messages, depending on the message that initiated the search:
On: the call will be downspeeded.
Off: the call will not be placed.
Click here to save your changes
Determines what will happen if the total bandwidth 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.
Save · Downspeed total mode

An example deployment is shown opposite. In this example, there are three geographically separate offices: Enterprise, Branch and Home. All endpoints in the Enterprise 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 enterprise’s leased line connection to the Internet, and the DSL connections to the remote offices are modeled as separate pipes.
HOME OFFICE
There are no firewalls involved in this scenario, so we can configure direct links 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.
Home Office
Default Subzone
Subzone
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. The Enterprise’s bandwidth budget will be unaffected by the call.
BRANCH OFFICE
Branch Office
Subzone

If we modify the previous example deployment to include firewalls between the offices, we can use TANDBERG’s 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, the endpoints in the Head Office register with the VCS Control, whilst 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.
HEAD OFFICE
INTERNET
Pipe B Home Office
The VCS Expressway has subzones configured for the Home Office and Branch Office. These are linked to the VCS Expressway’s 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.
In this example we have assumed that there is no bottleneck on the link between the VCS Expressway and the Head Office network, so have not placed a pipe 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.


This section describes how to configure your VCS Control and VCS Expressway in order to traverse firewalls. It also describes how to configure the additional firewall traversal server functions of a VCS Expressway, including STUN services.

VCS as a Firewall Traversal Client
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 TANDBERG’s Expressway™ solution to enable secure traversal of any firewall.
Your VCS can act as a firewall traversal client on behalf of SIP and H.323 endpoints registered to it, and any gatekeepers that are neighbored with it.
In order to act as a firewall traversal client, the VCS must be configured with information about the system(s) that will be acting as its firewall traversal server. See the section on Configuring the VCS as a Traversal Client for full details on how to do this.
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 can be a TANDBERG VCS Expressway, or (for H.323 only) a TANDBERG Border Controller.
The Expressway™ solution consists of:
a TANDBERG VCS Expressway or TANDBERG Border Controller 1. located outside the firewall on the public network or in the DMZ, which acts as the firewall traversal server
a TANDBERG VCS Control, TANDBERG Gatekeeper, MXP 2. endpoint or other traversal-enabled endpoint located in a private network, which acts as the firewall traversal client.
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 TANDBERG systems and any traversal-enabled endpoints that are registered directly to it. It can also provide STUN Discovery and STUN relay services to endpoints with STUN clients. These features are enabled as follows:
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.
In order for the VCS Expressway to act as a firewall traversal server for TANDBERG systems, you must create and configure a new • traversal server zone on the VCS Expressway for every system that is its traversal client. See Configuring the VCS as a Traversal Server for full instructions.
In order for the VCS Expressway to act as a firewall traversal server for traversal-enabled endpoints (i.e. TANDBERG 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 Traversal for Endpoints for more information on the options available.
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.
To enable STUN Discovery and STUN Relay services, see • STUN Services.
To reconfigure the default ports used by the VCS Expressway, see • Configuring Traversal Server Ports.
This process ensures that from the firewall’s point of view, all connections are initiated from the traversal client inside the firewall out to the traversal server.
In order 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. The ports and protocols configured for each pair of client-server zones must be the same. (See Quick Guide to VCS Traversal Client - Server Configuration for a summary of the configuration on each system.) Because the VCS Expressway listens for connections from the client on a specific port, we recommend that you create the traversal server zone on the VCS Expressway before you create the traversal client zone on the VCS Control.

VCS Expressway (Server) VCS Control (Client)
Full details of how to configure a VCS Control and VCS Expressway as traversal client and server respectively are given in the following pages. However, the basic steps are:


Ensure the VCS Control has been configured with an Authentication username and Authentication password to use as its External Registration Credentials. These can be added or edited via VCS Configuration > Authentication > Configuration (or by clicking on the Edit Authentication Username/Password link in the Edit Zone page for an existing Traversal Client Zone).


On the VCS Expressway, create a Traversal Server Zone (this represents the incoming connection from the VCS Control). In the Client authentication username field, enter the VCS Control’s Authentication username.
On the VCS Expressway, add the VCS Control’s authentication username and password as credentials in the authentication database. These can be added or edited via VCS Configuration > Authentication > Local Database, or by clicking on the Add/Edit Local Authentication Database link in the Edit Zone page.
On the VCS Control, create a Traversal Client Zone (this represents the connection to the VCS Expressway). Enter the VCS Expressway’s IP address or FQDN in the Primary address field.
On the VCS Control, configure all the modes and ports in the Protocol section to match identically those of the Traversal Server Zone on the VCS Expressway.

Expressway Process H.323 Firewall Traversal Protocols
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.
The Expressway™ solution works as follows:
The VCS supports two different firewall traversal protocols for H.323: Assent and H.460.18/H.460.19.
Each traversal client connects via the firewall to a unique port 1. on the VCS Expressway.
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 then must then configure their systems to connect to these specific ports on the server. The only port configuration that is done on the 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.
The server identifies each client by the port on which it 2. receives the connection, and the Authentication credentials provided by the client.
Once established, the client constantly sends a probe to 3. the VCS Expressway via this connection in order to keep the connection alive.
In order for a traversal server and traversal client to communicate, they must be using the same protocol.
When the VCS Expressway receives an incoming call for the 4. client, it uses this initial connection to send an incoming call request to the client.
The two protocols each use a slightly different range of ports.
The client then initiates one or more outbound connections. 5. The destination ports used for these connections will differ for signaling and/or media, and will depend on the protocol being used (see the following sections for more details).
The VCS supports the Assent protocol for SIP firewall traversal of media.
The signaling is traversed through TCP/TLS connection established from the client to the server.

Assent Ports H.460.18/19 Ports
Ports for Connections out to the
Traversal Clients
Public Internet
For connections to the VCS Expressway using the Assent protocol, the default ports are:
For connections to the VCS Expressway using the H.460.18/19 protocols, the default ports are:
Each traversal server zone specifies an H.323 port and a SIP port to be used for the initial connection from the client.
In situations where the VCS Expressway is attempting to connect to an endpoint on the public internet, you will not know the exact port(s) 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 once the server has located the endpoint on the public internet. This may cause problems if your VCS Expressway is located within a DMZ (i.e. there is a firewall between the VCS Expressway and the public internet) as you will not be able to specify in advance rules that will allow you to connect out to the endpoint’s ports.
Call signaling
Each time you configure a new traversal server zone on the VCS Expressway, you will be allocated default port numbers for these connections:
H.323 ports will start at UDP/6001 and • increment by 1 for every new traversal server zone
Media
SIP ports will 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.
You can however specify the ports on the VCS Expressway that will be 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:
If your VCS Expressway does not have any endpoints registering directly with it, and it has no Alternates configured, 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.
Once the H.323 and SIP ports have been set on the VCS Expressway, matching ports must be configured on the corresponding traversal client.
STUN Ports
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 Expressway’s traversal server zones.
The VCS Expressway can be enabled to provide STUN services (STUN Relay and STUN Binding Discovery) which can be used by SIP endpoints which support the ICE firewall traversal protocol.
SIP call signaling uses the same port as used by the initial connection between the client and server.
The ports used by these services are configurable via:
The default port used for the initial connections from MXP endpoints is the same as that used for standard RAS messages, i.e. UDP/1719. While it is possible to change this port on the VCS Expressway, most endpoints will not support connections to ports other than UDP/1719. We therefore recommend that this be left as the default.
Where the traversal client is a VCS, SIP media uses Assent to traverse the firewall . The default ports are the same as for H.323, i.e.:
The ICE clients on each of the SIP endpoints must be able to discover these ports, either via SRV records in DNS or by direct configuration.

In order to control which systems can use the VCS Expressway as a traversal server, each VCS Control or Gatekeeper that wishes to be its client must first authenticate with it.
VCS Control or VCS Expressway
The VCS client provides its • Authentication Username and Authentication Password. These are set on the VCS client via VCS Configuration > Authentication > Configuration, in the External Registration Credentials section.
Upon receiving the initial connection request from the traversal client, the VCS Expressway asks the client to authenticate itself by providing a username and password. The VCS Expressway then looks up the client’s username and password in its own authentication database. If a match is found, the VCS Expressway will accept the request from the client.
The endpoint client provides its • Authentication ID and Authentication Password.
There must be an entry in the VCS Expressway’s authentication • database with the corresponding client username and password.
The settings used for authentication depend on the combination of client and server being used. These are detailed in the table opposite.
TANDBERG Gatekeeper (version 5.2 and earlier)
The Gatekeeper looks up its • System Name in its own authentication database and retrieves the password for that name. It then provides this name and password.
All VCS and Gatekeeper traversal clients must authenticate with the VCS Expressway, regardless of the VCS Expressway’s Authentication Mode setting. However, endpoint clients are only required to authenticate if the VCS Expressway’s Authentication Mode is On.
TANDBERG Gatekeeper (version 6.0 and later)
The Gatekeeper provides its • Authentication Username and Authentication Password. These are set on the Gatekeeper via Gatekeeper Configuration > Authentication, in the External Registration Credentials section.
All VCS and Gatekeeper traversal clients must authenticate with the VCS Expressway. The authentication process makes use of timestamps and requires that each system is using an accurate system time. The system time on a VCS is provided by a remote NTP server. Therefore, in order for firewall traversal to work, all systems involved must be configured with details of an NTP server.
VCS Control or VCS Expressway
If Authentication is On on the Border Controller, there must be an entry • in the Border Controller’s authentication database that matches the VCS client’s Authentication Username and Authentication Password.
If the Border Controller is in Assent mode, the traversal zone • configured on the Border Controller to represent the VCS client must use the VCS’s Authentication Username in the Assent Account name field. This is set on the Border Controller via TraversalZone > Assent > Account name.

Firewall Configuration
The Dual Network Interfaces option enables the LAN 2 interface on your VCS Expressway (the option is not available on a VCS Control). The LAN 2 interface is used in situations where your VCS Expressway is located in a DMZ that consists of two separate networks - an inner DMZ and an outer DMZ - and your firewall rules prevent communication between the two.
In order for Expressway™ firewall traversal to function correctly, the firewall must be configured to:
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.
All ports configured on the VCS, including those relating to firewall traversal, will apply to both IP addresses; it is not possible to configure these ports separately for each IP address.
We recommend that you turn off any H.323 and SIP protocol support on the firewall: these are not needed in conjunction with the TANDBERG Expressway™ solution and may interfere with its operation.

Adding a New Traversal Client Zone
To enable your VCS to act as a traversal client on behalf of its endpoints and neighbor gatekeepers, you must create a connection between it and a traversal server (e.g. a TANDBERG VCS Expressway or Border Controller).
You do this by adding a new traversal client zone on the VCS client and configuring it with the details of the traversal server.
Enter the name you wish to give to this zone. The name acts as a unique identifier, allowing you to distinguish between zones of the same type.
From the Type drop-down menu, select TraversalClient.
Click here to create the zone. You will be taken directly to the Edit Zone page, where you can configure the traversal client zone as required.
You can create more than one traversal client zone if you wish to connect to multiple traversal servers.
Name · Type · Create Zone
![Page 153 of the TANDBERG Security Camera user manual — xConfiguration Zones Zon • e [1..200]](/cdn/reader/9a/9a94646fb4a881d35b1a0f9d56871769188836c2936deddce87dcd3ebd834bb3/images/page-153.webp?w=400)
VCS Configuration > Zones • . You will be taken to the Zones page. Click on the name of the zone you wish to configure. You will be taken to the Edit Zone page.
Determines whether SIP calls will be allowed to and from this zone.
xConfiguration Zones Zon • e [1..200] Traversal Client
Specifies the port on the traversal server to be used for SIP calls from this VCS.
Specifies the hop count to be used when querying this zone.
Determines which transport type will be used for SIP calls to and from the traversal server.
This field displays the Authentication username that has been configured on this VCS. The Authentication username and password are system-wide settings that are used for all Traversal Client Zones. The Authentication username cannot be edited directly from this page but it is shown here for reference as it is needed when configuring the corresponding Traversal Server Zone.
H.323 mode
Determines whether H.323 calls will be allowed to and from this zone.
H.323 protocol
Determines which of the two firewall traversal protocols to use for calls to the traversal server.
To edit the Authentication username, click on the Edit Authentication Username/Password link. This will take you to the Authentication page, where you can edit the settings under the External Registration Credentials section.
H.323 port
Specifies the port on the traversal server to be used for H.323 firewall traversal calls.
Specifies the IP address or FQDN of the traversal server.
Specifies the interval in seconds with which a failed attempt to establish a connection to the traversal server should be retried.
Alternate 1..5 Address
Specifies the IP addresses or FQDNs of any alternates configured on the traversal server.
Remember to Save your changes.

Adding a New Traversal Server Zone
The VCS Expressway can act as a firewall traversal server. This feature means you can:
Enter the name you wish to give to this zone. The name acts as a unique identifier, allowing you to distinguish between zones.
From the Type drop-down menu, select TraversalServer.
Click here to create the zone. You will be taken directly to the Edit Zone page, where you can configure the traversal server zone as required.
Name · Type · Create Zone
![Page 155 of the TANDBERG Security Camera user manual — xConfiguration Zones Zone [1..200] • TraversalServer](/cdn/reader/9a/9a94646fb4a881d35b1a0f9d56871769188836c2936deddce87dcd3ebd834bb3/images/page-155.webp?w=400)
VCS Configuration > Zones • . You will be taken to the Zones page. Click on the name of the zone you wish to configure. You will be taken to the Edit Zones page.
Determines whether SIP calls will be allowed to and from the traversal client.
Specifies the port on the VCS Expressway to be used for SIP calls from the traversal client.
Determines which transport type will be used for SIP calls to and from the traversal client.
If the traversal client is a VCS, this must be the VCS’s Authentication Username.
You must also add the client’s Authentication username and password to the VCS’s authentication database. To go directly to the page where you can do this, click on the Add/ Edit Local Authentication Database link.
H.460.19 demux mode
On: allows use of the same two ports for media for all calls from the traversal client.
Off: each call from the traversal client will use a separate pair of ports for media.
H.323 mode
Determines whether H.323 calls will be allowed to and from the traversal client.
Sets the interval (in seconds) with which the traversal client will send a UDP probe to the VCS Expressway.
H.323 protocol
Determines which of the two firewall traversal protocols will be used for calls through the firewall, to and from the client. The same protocol must be used by the client.
Sets the number of times the traversal client will attempt to send a UDP probe to the VCS Expressway.
H.323 port
Specifies the port on the VCS Expressway to be used for H.323 connections from the client.
UDP keep alive interval
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 firewall’s NAT bindings open.
TCP keep alive interval
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 firewall’s NAT bindings open.
Sets the number of times the traversal client will attempt to send a TCP probe to the VCS Expressway.
Sets the frequency (in seconds ) with which the traversal client will send a TCP probe to the VCS Expressway.

Overview
UDP probe retry interval
Traversal-enabled H.323 endpoints can register directly with the VCS Expressway and use it for firewall traversal.
Sets the frequency (in seconds) with which locally registered endpoints will send a UDP probe to the VCS Expressway.
To configure the options for these endpoints:
UDP probe retry count
Sets the number of times locally registered endpoints will attempt to send a UDP probe to the VCS Expressway.
UDP probe keep alive interval
Sets the interval (in seconds) with which locally registered endpoints will send a UDP probe to the VCS Expressway once a call is established, in order to keep the firewall’s NAT bindings open.
H.323 Assent mode
Determines whether or not H.323 calls using Assent mode for firewall traversal will be allowed.
TCP probe retry interval
H.460.18 mode
Sets the frequency (in seconds) with which locally registered endpoints will send a TCP probe to the VCS Expressway.
Determines whether or not H.323 calls using H.460.18/19 mode for firewall traversal will be allowed.
TCP probe retry count
H.460.19 demux mode
Sets the number of times locally registered endpoints will attempt to send a TCP probe to the VCS Expressway.
Determines whether the VCS Expressway will operate in Demultiplexing mode for calls from locally registered endpoints.
On: allows use of the same two ports for all calls.
TCP probe keep alive interval
Off: Each call will use a separate pair of ports for media.
Sets the interval (in seconds) with which locally registered endpoints will send a TCP probe to the VCS Expressway once a call is established, in order to keep the firewall’s NAT bindings open.
H.323 preference
If an endpoint supports both Assent and H.460.18 protocols, this setting determines which the VCS Expressway uses.
Click here to save your settings.
Save

Overview
Media demultiplexing RTP port
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.
Specifies the port on the VCS to be used for demultiplexing RTP media.
Media demultiplexing RTCP port
Specifies the port on the VCS to be used for demultiplexing RTCP media.
To configure the VCS Expressway ports:
VCS Configuration > Expressway > Ports • You will be taken to the Ports page.
H.323 Assent call signaling port
Specifies the port on the VCS to be used for Assent signaling.
xConfiguration Traversal Server • H.323
H.323 H.460.18 call signaling port
Specifies the port on the VCS to be used for H.460.18 signaling.
Click here to save your settings.
Save

About STUN
STUN Binding Discovery
STUN Relay
STUN is a network protocol that enables a SIP or H.323 client to communicate via UDP or TCP from behind a NAT firewall.
The STUN Binding Discovery service provides information back to the client about the binding allocated by the NAT firewall being traversed.
The STUN Relay service (formerly known as TURN) allows a client to ask for data to be relayed to it from specific remote peers via the relay server and through a single connection between the client and the relay server.
The VCS Expressway can be configured to provide two types of STUN services to traversal clients. These services are STUN Binding Discovery and STUN Relay. Currently the VCS supports STUN over UDP only.
A client behind a NAT firewall sends a STUN discovery request via the firewall to the VCS Expressway, which has been configured as a STUN discovery server. Upon receipt of the message, the VCS Expressway responds to the client with information about the allocated NAT binding, i.e. the public IP address and the ports being used.
A client behind a NAT firewall sends a STUN Allocate request to the VCS Expressway which is acting as the STUN relay server. The sending of this request opens a binding on the firewall. Upon receipt of the request, the VCS Expressway opens a public IP port on behalf of the client, and reports back to the client this IP address and port, as well as details of the firewall binding. The client can then provide this IP address and port to other systems which may want to reach it.
For detailed information on the base STUN protocol and the Binding Discovery service, refer to Session Traversal Utilities for (NAT) (STUN) [11].
The client can then provide this information to other systems which may want to reach it, allowing it to be found even though it is not directly available on the public internet.
For detailed information on the STUN Relay service, refer to Obtaining Relay Addresses from Simple Traversal Underneath NAT (STUN) [12].
The client can restrict the remote address and ports from which the relay should forward on media. Any incoming calls to this IP address and port on the VCS server are relayed via the allocated binding on the NAT to the client.
Currently, the most likely users of STUN services are ICE endpoints.
ICE (Interactive Connectivity Establishment) is a collaborative algorithm that works together with STUN services (and other NAT traversal techniques) to allow clients to achieve firewall traversal. The individual techniques on their own may allow traversal in certain network topologies but not others. Also some techniques maybe less efficient than others, involving extra hops (e.g. STUN Relay).
ICE involves the collecting of potential (candidate) points of contact (IP address and port combination) via each of the traversal techniques, the verification of peer-to-peer connectivity via each of these points of contact and then the selection of the “best” successful candidate point of contact to use.
The endpoint will only be reachable if the firewall has the Endpoint-Independent Mapping behavior as described in RFC 4787 [13].
STUN Relays consume traversal call licences (three relays take one licence) but they do not actually pass through the traversal subzone.
How it works · How it works

Configuring STUN Services
To configure the STUN Binding Discovery and STUN Relay services:
Determines whether the VCS will offer STUN Discovery services to traversal clients.
VCS Configuration > Expressway > STUN. • You will be taken to the STUN page.
Specifies the port on the VCS on which it will be listening for STUN Discovery requests.
Determines whether the VCS will offer STUN Relay services to traversal clients.
Specifies the port on the VCS on which it will be listening for STUN relay requests.
STUN relay media port start
Specifies the lower port in the range to be used for STUN media relay.
STUN relay media port end
Specifies the upper port in the range to be used for STUN media relay.
Click here to save your changes.


This section describes the pages that appear under the Maintenance menu of the VCS web interface.
These pages allow you to perform the following tasks:
restore the system to its default setting • s.

Upgrading Using SCP/PSCP
It is possible to install new releases of the VCS software on your existing hardware. Software upgrade can be done in one of two ways:
To upgrade using SCP or PSCP (part of the PuTTY free Telnet/ SSH package) you will need to transfer two files to the VCS:
The existing configuration will be restored after performing an upgrade. However, we recommend that you make a backup of the existing configuration before performing the upgrade.
a text file containing just the 16-character Release Key • (not required for dot release upgrades). Ensure there is no extraneous white space in this file.
using the web interface (HTTP/HTTP • S).
To do this:
the file containing the software image. • To upgrade using SCP or PSCP:
This section describes how both of these methods are used to perform upgrades.
Use the command line interface to log on to the VCS. 1.
Issue the command 2. xConfiguration.
Ensure the VCS is turned on and available over IP. 1.
Save the resulting output to a file, using cut-and-paste or 3. some other means provided by your terminal emulator.
Upload the release key file using SCP/PSCP to the 2. /tmp folder on the system. The target name must be release-key, e.g.
The upgrade requires you to have:
To restore your configuration:
Remove the 1. *c from in front of each command.
a valid Release key. This is required for upgrades to a major • release, e.g. X1.2 to X2.0; it is not required for dot releases, e.g. X2.0 to X2.1)
scp release-key [email protected]:/tmp/release-key or pscp release-key [email protected]:/tmp/release-key
Paste this information back in to the command line interface. 2.
Enter password when prompted. 3.
a software image file. • Contact your TANDBERG representative for more information on how to obtain these.
Upload the software image using SCP/PSCP to the 4. /tmp folder on the system. The target name must be /tmp/tandberg-image.tar.gz, e.g.
scp s42100x11.tar.gz [email protected]:/tmp/ tandberg-image.tar.gz or pscp s42100x11.tar.gz [email protected]:/tmp/ tandberg-image.tar.gz
Upgrading and Option Keys
Upgrading software is a two-stage process. Firstly, 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 installation stage the system will continue running on its existing software version, and all normal system processes will continue.
All existing option keys will be retained from one upgrade to the next, including upgrades to the next major release. However, we recommend that you take note of your existing option keys before performing an upgrade.
Enter password when prompted. 5.
Wait until the software has installed completely. This should 6. not take more than four minutes.
New features may also become available with each major release of VCS software, and you may need to install new option keys if you wish to take advantage of these new features. Contact your TANDBERG representative for more information on all the options available for the latest release of VCS software.
Reboot the system. 7.
After about four minutes the system will be ready to use.
The second part of the upgrade involves restarting the system. It is only during the restart that the VCS swaps over to the new software version and restores all previous configuration.
This means that you can install the new software to your system at any time, and then wait until a convenient moment (for example, when no calls are taking place) to swap over to the new version by rebooting the system. However, this also means that any configuration changes made between the installation and the reboot will be lost once the system restarts using the new software version.
You must name the files exactly as described above.
You must transfer the Release Key file before transferring the software image.

To upgrade your software via the web interface:
Maintenance > Upgrade • . You will be taken to the Upgrade page.
This section tells you about the software and hardware that currently make up your system.
Enter the 16-character Release Key that has been provided to you. This is not required if you are upgrading to a dot release, e.g. X2.0 to X2.1.
If you have cut and pasted the release key, ensure there are no trailing white spaces.
Select the software file
Enter the path of the software image file, or click Browse to locate it on the network.
You must restart the system after you have uploaded the new software version in order for the installation to complete. Any configuration changes you make between upload and restart will be lost, so we recommend restarting your system immediately.
Click Install Software. You will be taken to the System Upgrade page.
When the upgrade is complete, this page will refresh and you will see a message saying software successfully upgraded.
You must now restart the system for the upgrade to take effect.
Before you start the upgrade, ensure that the software image file for the new version has been saved in a network location that can be accessed via the web interface. Also ensure that you have the 16-character Release Key readily available.
You must restart your system before the new software can be used.

Adding Options via the CLI
The following VCS features can be added to your existing system by installing the appropriate options:
To return the indexes of all the Option Keys that are already installed on your system:
To add a new Option Key to your system:
H.323 to SIP Interworking gateway • : enables H.323 calls to be translated to SIP and vice versa
User Policy • : enables TANDBERG FindMe functionality
Dual Network Interfaces • : enables the LAN 2 port
Traversal calls: • determines the number of traversal calls allowed on the VCS at any one time. A traversal call is any call where the VCS is required to take the media as well as the signalling, i.e. firewall traversal calls, IPv4 to IPv6 calls, and SIP to H.323 calls. 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 non-traversal call.
Non-traversal calls • : determines the number of non-traversal calls allowed on the VCS at any one time. A non-traversal call is any call where the VCS is taking the signalling but not the media. 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 will still be counted as one non-traversal call.
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 a VCS, and these will each count as one registration.
Your system may have come with one or more of these options pre-configured. Further options can be installed by obtaining a valid Option Key and installing it on your system. Contact your TANDBERG representative for more information on how to obtain Option Keys.
Options can be installed in either of two ways:
via the CL • I.
via the web interfac • e.
This section describes both methods.
Some option keys require that the VCS is restarted before the option key will take effect. In such cases you will receive a warning, 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.
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.


This section lists the keys that are already installed on your system along with a description of the options they provide.
Maintenance > Option Keys • . You will be taken to the Option Keys page.
This section tells you about the hardware and options that currently make up your system.
Enter the 20-character Option Key that has been provided to you for the option you wish to add.
Some option keys require that the VCS is restarted before the option key will take effect. You will receive a warning if this is the case.

Enabling Security
For extra security, you may wish to have the VCS communicate with other systems (e.g. servers such as LDAP servers or clients such as SIP endpoints) using TLS encryption.
Select the file containing...
Allows you to upload a PEM file that identifies the list of Certificate Authorities trusted by the VCS. The VCS will only accept certificates signed by a CA on this list. If you are connecting to an LDAP database using TLS encryption, the certificate used by the LDAP database must be signed by a CA on this list.
For this to work successfully in a connection between a client and server:
Shows you the currently uploaded PEM file that identifies the list of Certificate Authorities trusted by the VCS.
Click here once you have selected the file to upload it.
To enable security using the web interface:
Select the server private key file
Maintenance > Security • . You will be taken to the Security page.
Allows you to upload a PEM file that identifies the private key used to encrypt the server certificate used by the VCS. This private key must not be password protected.
Select the server certificate file
Allows you to upload a PEM file that contains the server certificate used for HTTPS connections to the VCS from user or administrator web browsers, and by SIP endpoints or servers connecting to the VCS over TLS.
The files that enable secure connections over TLS are installed via the web interface. They cannot be installed using the CLI.
Upload server certificate data
Click here once you have selected the files to upload them.
Shows you the currently uploaded PEM file containing the certificate used by the VCS to identify itself to SIP and HTTPS clients when communicating over SSL/TLS.
Show CA certificate · Upload CA certificate · Show server certificate

Configuring Administrator Password
In order to access the VCS administrator interface, you must log in using a valid username and password.
To change the password used to log in to the VCS:
The same username and password are used whether you are accessing the VCS via the web interface or the command line interface.
The username is always admin (all lower case); this can not be changed.
The default password is TANDBERG (all upper case). You should change this as soon as possible. We recommend that you choose a strong password, particularly if administration over IP is enabled. The maximum password length is 16 characters.
Enter your new password here.
Both the username and password are case- sensitive.
Retype your new password here.
If you forget the Administrator password, it is possible to reset it if you have physical access to the VCS. See the section Resetting the Administrator Password for details.
Click here to reset the Administrator Password to a blank field.
This page describes how to reset the Administrator password. For instructions on how to reset passwords for FindMe users, see the section Changing a User Password.
You must restart the system for changes to take effect.

Creating a System Snapshot
The system snapshot is used for diagnostic purposes. It is a file that can be sent to your TANDBERG support representative at their request to assist them in troubleshooting issues you may be experiencing.
To create a system snapshot file:
Maintenance > System Snapshot • . You will be taken to the System Snapshot page.
Clicking on this button will initiate the download of the system snapshot file. You will then be asked whether and where you would like to save the file.
Select a location from which you can easily send the file to your TANDBERG support representative. You can configure the VCS to automatically send reports to a specified web service each time it experiences application failures such as system crashes. The information contained in these reports can then be used by TANDBERG technical support to diagnose the cause of the failures. This feature is only intended for use at the request of TANDBERG technical support in exceptional situations, and is OFF by default. This feature cannot be configured via the web interface; it is configured via xConfiguration Error Reports.
Create System Snapshot

Restarting the VCS
Some configuration changes will require a restart of the system to take effect. There will be a Restart button at the bottom of any web pages that include such options, and clicking on this button will take you to the Restart page. If you do not restart the system after making these changes, you will receive a warning telling you the system needs to be restarted.
Restarting will cause any active calls and registrations to be terminated. For this reason, the Restart page displays the number of current calls and registrations, so you can check these before you restart.
Do not restart the system while the red ALM LED on the front of the box is on. This indicates a hardware fault. Contact your TANDBERG representative.
To restart the VCS:
Click here to restart the system.
The Restarting page will appear, with an orange bar indicating progress.
Once the system has successfully restarted, you will automatically be taken to the Login page.
Restart System

Shutting Down
The system must be shut down before it is unplugged.
Once the system has been shut down, the only way it can be restarted is by pressing the soft power button on the unit itself. You must therefore have physical access to the unit if you wish to be able to restart it after it has been shut down.
Shutting down will cause any active calls and registrations to be terminated. For this reason, the Shutdown page displays the number of current calls and registrations, so you can check these before you restart.
Do not shutdown the system while the red ALM LED on the front of the box is on. This indicates a hardware fault. Contact your TANDBERG representative.
To shut down the VCS:
Maintenance > Shutdown • . You will be taken to the Shutdown page.
Click here to shutdown the system.
The Shutting Down page will appear. This page will remain in place once the system has successfully shut down but any attempts to refresh the page or access the VCS will then be unsuccessful.
Shutdown System

DefaultValuesSet Level 3
It is possible to restore the VCS to its default configuration. This is done via the CLI using xCommand DefaultValuesSet. This command is not available via the web UI.
Configuration item Default value after xCommand DefaultValuesSet Level: 3
SystemUnit Name
The DefaultValuesSet command allows you to specify the level of configuration to restore, from 1 to 3 as follows:
Option [1..64] Key
Level 1 • resets most configuration items to their default value, with the exception of the items shown in the table opposite. The xConfiguration reference table shows a full list of all configuration items and where applicable their default values.
IP Gateway 127.0.0.1
IP V6 Gateway
Level 2 • is not currently used, so setting this level has the same effect as setting Level 1.
IP DNS Server [1..5] Address
Level 3 • resets all configuration items to their default value, including those shown in the table opposite.
IP DNS Domain Name
Ethernet [1..2] Speed Auto
Ethernet [1..2] IP V4 Address 192.168.0.100
Ethernet [1..2] IP V4 SubnetMask 255.255.255.0
Ethernet [1..2] IP V6 Address
ExternalManager Path tms/public/external/management/SystemManagementService.asmx
Policy AdministratorPolicy Mode Off
Policy UserPolicy Mode Local
xCommand DefaultValuesSet Level: 3 must be used with caution, as it resets the system’s IPv4 and IPv6 addresses, meaning you will no longer be able to access the system over IP. It also deletes all option keys including pre-installed options such as Expressway and the number of registrations and calls.
Policy UserPolicy Server Protocol HTTP
Policy UserPolicy Server Address
Policy UserPolicy Server Path
Policy UserPolicy Server UserName
Policy UserPolicy Server Password


This section includes the following appendices which provide supplementary information regarding the administration of the VCS:

This Appendix gives details of the VCS’s implementation of the CPL language and should be read in conjunction with the CPL standard RFC 3880 [5] and the TANDBERG guide to writing CPL [22].
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 VCS supports most of the CPL standard along with some TANDBERG-defined extensions. It does not support the top level actions and as described in RFC 3880. Instead it supports a single section of CPL within a section.
The address-switch has two node parameters: Field and Subfield.
When Administrator 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 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:
The address construct is used within an address-switch to specify addresses to match. It supports the use of Regular Expressions (see the Regular Expression Reference for further information).
xmlns:taa="http://www.tandberg.net/cpl-extensions"
Valid values are:
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
is=string Selected field and subfield exactly match the given string.
xsi:schemaLocation="urn:ietf:params:xml:ns:cpl cpl.xsd">
contains=string Selected field and subfield contain the given string.
subdomain-of=string If the selected field is numeric (e.g. the tel subfield) then this matches as a prefix; so address subdomain-of="555" matches 5556734 etc.
If the field is not numeric then normal domain name matching is applied; so address subdomain-of="company.com" matches nodeA.company.com etc.
regex="regular expression" Selected field and subfield match the given regular expression.
All address comparisons ignore upper/lower case differences so address is="Fred" will also match fred, freD etc.

field
Within the address-switch node, the mandatory field parameter specifies which address is to be considered. The supported attributes and their interpretation are as follows:
Field SIP H.323 SIP H.323
origin The "From" and "ReplyTo" fields of the message if it authenticated correctly, otherwise not-present.
The source aliases from the original LRQ or ARQ that started the call if it authenticated correctly otherwise not-present. Since SETUP messages are not authenticated if we receive a setup without a preceding RAS message the origin will always be not-present.
The "From" and "ReplyTo" fields of the incoming message.
The source aliases from the original LRQ or ARQ that started the call. If a SETUP is received without a preceding RAS message then the origin is taken from the SETUP.
unauthenticated-origin The "From" and "ReplyTo" fields of the incoming message.
The source aliases from the original LRQ or ARQ that started the call. If a SETUP is received without a preceding RAS message then the origin is taken from the SETUP.
The "From" and "ReplyTo" fields of the incoming message.
The source aliases from the original LRQ or ARQ that started the call. If a SETUP is received without a preceding RAS message then the origin is taken from the SETUP.
authenticated-origin The "From" and "ReplyTo" fields of the message if it authenticated correctly, otherwise not-present.
The source aliases from the original LRQ or ARQ that started the call if it authenticated correctly otherwise empty. Since SETUP messages are not authenticated if we receive a setup without a 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 The username used for authentication. not-present
registered-origin If the call originates from a registered endpoint this is the list of all aliases it has registered, otherwise not-present.
destination The destination aliases.
original-destination The destination aliases.
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 i.e. an address node matches if it matches any alias.
not-present

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 will be taken.
address-type Either h323 or sip, based on the type of endpoint that originated the call.
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.
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-type Gives a string representation of the type of alias. The type is inferred from the format of the alias. Possible types are:
The otherwise node will be executed if the address specified in the address-switch was found but none of the preceding address nodes matched.
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 Unauthenticated Users).

proxy
As the CPL script is evaluated it maintains a list of addresses (H.323 IDs, URLs and E.164 numbers) which will be used as the destination of the call if a proxy node is executed. The location node allows the location set to be modified so that calls can be redirected to different destinations.
On executing a proxy node the VCS will attempt 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 will be forwarded to its original destination.
At the start of script execution the location set is initialized to empty for incoming calls and to the original destination for outgoing calls.
The following attributes are supported on location nodes. It supports the use of Regular Expressions (see the Regular Expression Reference for further information).
Clear = "yes" | "no" Specifies whether to clear the current location set before adding the new location. The default is to append this location to the end of the set.
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.
url=string The new location to be added to the location set. The given string can specify a URL (e.g. user@domain.com), H.323 ID or an E.164 number.
priority= | "random" Specified either as a floating point number in the range 0.0 to 1.0, or random, which assigns a random number within the same range. 1.0 is the highest priority. Locations with the same priority are searched in parallel.
regex="" replace="" Specifies the way in which a location matching the regular expression is to be changed.
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:
This extension to CPL is provided to simplify administrator policy scripts that need to make decisions based on both the source and destination of the call. A rule-switch may 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:
The meaning of the various origin selectors is as described in the Field section.


In this example, only calls from users with authenticated source addresses are allowed.
In this example, user ceo will only accept calls from users vpsales, vpmarketing or vpengineering.
See the section on Authentication for details on how to enable authentication.

Call Screening Based on Domain
Change of Domain Name
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.
In this example, Example Inc has changed its domain from example.net to example.com. For a period of time some users are still registered at example.net. The following script would attempt to connect calls to user@example.com first and if that fails then fallback to example.net.
xmlns:taa="http://www.tandberg.net/cpl-extensions"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:taa="http://www.tandberg.net/cpl-extensions"
xsi:schemaLocation="urn:ietf:params:xml:ns:cpl cpl.xsd">
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:cpl cpl.xsd">
replace="\1@example.net">


In this example, the administrator only wants to allow calls that originate from locally registered endpoints.
The same script can be extended to also allow calls from configured zones but not from the Default Zone or Default Subzone.

Restricting Access to a Local Gateway
Using the rule-switch node
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.
We can do this in two ways: using the address-switch node or the rule-switch node. Examples of each are shown below.
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">
Using the address-switch node
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">

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.
. Matches any single character.
* Matches 0 or more repetitions of the previous match. .* will match against any sequence of characters.
+ Matches 1 or more repetitions of the previous match.
The table opposite 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 Mastering Regular Expressions [9].
\ Escapes a regular expression special character.
\d Matches any decimal digit, i.e. 0-9.
[...] Matches a set of characters. Each character in the set can be specified individually, or a range can be specified by giving the first character in the range followed by the - character and then the last character in the range.
[a-z] will match against any lower case alphabetical character.
[a-zA-Z] will match against any alphabetical character.
[0-9#*] will match against any single E.164 character - the E.164 character set is made up of the digits 0-9 plus the hash key (#) and the asterisk key (*).
You can not use special characters within the [] - they will be taken literally.
(...) Groups a set of matching characters together. Groups can then be referenced in order using the characters \1, \2, etc. as part of a replace string.
A regular expression can be constructed to transform a URI containing a user’s full name to a URI based on their initials.
The regular expression (.).* _ (.).*(@example.com) would match against the user john _ smith@example.com and with a replace string of \1\2\3 would transform it to js@example.com.
| Matches against one expression or an alternate expression.
.*@example.(net|com) will match against any URI for the domain example.com or the domain example.net.
^ Signifies the start of a line.
When used immediately after an opening brace, negates the character set inside the brace.
[^abc] matches any single character that is NOT one of a, b or c.
$ Signifies the end of a line. ^\d\d\d$ will match any string that is exactly 3 digits long.
(?!...) Negative lookahead. Defines a subexpression that must not be present in order for there to be a match.
(?!.*@tandberg.net$).* will match any string that does not end with @ tandberg.net.
For an example of regular expression usage, see the section CPL Examples.
Character Description Example

The VCS makes use of pattern matching in a number of its features, namely Allow Lists and Deny Lists, pre-search Transforms and Zone Transforms.
String Equals current value(s) returned by... When used in a Match field When used in a Replace field
%ip% xConfiguration Ethernet 1 IP V4 Address
Matches all IPv4 and IPv6 addresses currently configured on the VCS.
xConfiguration Ethernet 1 IP V6 Address
For each of these pattern matches, the VCS allows you to use a variable that it will replace with the current configuration value(s) before the pattern is checked.
xConfiguration Ethernet 2 IP V4 Address
xConfiguration Ethernet 2 IP V6 Address
%ipv4% xConfiguration Ethernet 1 IP V4 Address
Matches the IPv4 addresses currently configured on the VCS for LAN 1 and LAN 2.
These variables can be used as either or both of:
xConfiguration Ethernet 2 IP V4 Address
%ipv4 _ 1% xConfiguration Ethernet 1 IP V4 Address Matches all IPv4 address currently configured on the VCS for LAN 1.
Replaces the string with the LAN 1 IPv4 address.
%ipv4 _ 2% xConfiguration Ethernet 2 IP V4 Address Matches all IPv4 address currently configured on the VCS for LAN 2.
all or part of the string that is replacing the • pattern that was found.
Replaces the string with the LAN 2 IPv4 address.
%ipv6% xConfiguration Ethernet 1 IP V6 Address
Matches the IPv6 addresses currently configured on the VCS for LAN 1 and LAN 2.
The variables can be used in all types of patterns, i.e. prefix, suffix, regex and exact.
xConfiguration Ethernet 2 IP V6 Address
The table opposite shows the strings that are valid as variables, and the values they represent.
%ipv6 _ 1% xConfiguration Ethernet 1 IP V6 Address Matches the IPv6 address currently configured on the VCS for LAN 1.
Replaces the string with the LAN 1 IPv6 address.
%ipv6 _ 2% xConfiguration Ethernet 2 IP V6 Address Matches the IPv6 address currently configured on the VCS for LAN 2.
Replaces the string with the LAN 2 IPv6 address.
%localdomains% xConfiguration SIP Domains Domain 1 Name
Matches all the SIP domains currently configured on the VCS.
xConfiguration SIP Domains Domain 20 Name
xConfiguration SIP Domains Domain 1 Name
Matches the specified SIP domain. Up to 20 SIP domains can be configured on the VCS, and they are identified by an index number between 1 and 20.
Replaces the string with the specified SIP domain.
xConfiguration SIP Domains Domain 20 Name
%systemname% xConfiguration SystemUnit Name Matches the VCS’s System Name. Replaces the string with the VCS’s System Name.

The VCS uses different ports and protocols for different services and functions, and many of these are configurable.
Two services or functions cannot share the same port and protocol; if you attempt to change an existing port or range and it conflicts with another service, you will get a warning message.
The table below shows all the ports on the VCS that are used for each of these services and functions. It shows the default port(s) and protocol used, and if the ports are configurable it shows the available range and how to configure them via the web UI or CLI.
Service/Function Description Default Available Range Configurable via
SSH for encrypted command line administration 22 TCP not configurable
Telnet used for unencrypted command line administration
23 TCP not configurable
HTTP used for unencrypted Web administration 80 TCP not configurable
SNMP used for network management 161 UDP not configurable
NTP used for updating the system time (and important for H.235 security)
123 UDP not configurable
HTTPS used for encrypted Web administration 443 TCP not configurable
Remote Logging used to send message to the remote syslog server
514 UDP not configurable
Gatekeeper discovery Multicast Gatekeeper discovery 1718 UDP not configurable
H323 Registration and Alternate communication
used to listen for inbound H.323 UDP registrations. Also used for inbound and outbound communication with Alternates, even if H.323 is disabled
1719 UDP 1024 - 65534 VCS Configuration > Protocols > H.323
xConfiguration H323 Gatekeeper Registration UDP Port
H.323 call signaling listens for H.323 call signaling 1720 TCP 1024 - 65534 VCS Configuration > Protocols > H.323
xConfiguration H323 Gatekeeper CallSignaling TCP Port
Traversal Server Media Demultiplexing RTP
used on the VCS Expressway for demultiplexing RTP media
2776 UDP 1024 - 65534 VCS Configuration > Expressway > Ports
xConfiguration Traversal Server Media Demultiplexing RTP Port
Assent call signaling used on the VCS Expressway for Assent signaling 2776 TCP 1024 - 65534 VCS Configuration > Expressway > Ports
xConfiguration Traversal Server H323 Assent CallSignaling Port
H.460.18 call signaling used on the VCS Expressway for H.460.18 signaling
2777 TCP 1024 - 65534 VCS Configuration > Expressway > Ports
xConfiguration Traversal Server H323 H46018 CallSignaling Port

Service/Function Description Default Available Range Configurable via
Traversal Server Media Demultiplexing RTCP
used on the VCS Expressway for demultiplexing RTCP media
2777 UDP 1024 - 65534 VCS Configuration > Expressway > Ports
xConfiguration Traversal Server Media Demultiplexing RTCP Port
STUN Discovery used on the VCS Expressway for STUN discovery services
3478 UDP 1024 - 65534 VCS Configuration > Expressway > STUN
xConfiguration Traversal Server STUN Discovery Port
STUN Relay used on the VCS Expressway listening port for STUN relay requests.
4678 UDP 1024 - 65534 VCS Configuration > Expressway > STUN
xConfiguration Traversal Server STUN Relay Port
SIP UDP listens for incoming SIP UDP calls 5060 UDP 1024 - 65534 VCS Configuration > Protocols > SIP > Configuration
xConfiguration SIP UDP Port
SIP TCP listens for incoming SIP TCP calls. 5060 TCP 1024 - 65534 VCS Configuration > Protocols > SIP > Configuration
xConfiguration SIP TCP Port
SIP TLS listens for incoming SIP TLS calls 5061 TLS 1024 - 65534 VCS Configuration > Protocols > SIP > Configuration
xConfiguration SIP TLS Port
Traversal Server Zone H323 Port
the port on the VCS Expressway being used for H.323 firewall traversal from a particular traversal client.
6001 UDP, incrementing by 1 for each new zone.
1024 - 65534 VCS Configuration > Zones > Edit Zone
xConfiguration Zones Zone [1..200] TraversalServer H323 Port
Traversal Server Zone SIP Port
the port on the VCS Expressway being used for SIP firewall traversal from a particular traversal client.
7001 TCP/TLS, incrementing by 1 for each new zone.
1024 - 65534 VCS Configuration > Zones > Edit Zone
xConfiguration Zones Zone [1..200] TraversalServer SIP Port
DNS used for sending requests to DNS servers 10000 - 10210 UDP
H.225 and H.245 call signaling port range
the range of ports to be used for call signalling once a call is established
1024 - 65534 VCS Configuration > Protocols > H.323
xConfiguration H323 Gatekeeper CallSignaling PortRange Start
xConfiguration H323 Gatekeeper CallSignaling PortRange End
SIP TCP outbound port range
The range of ports to be used by outbound TCP/ TLS SIP connections to a remote SIP device
25000 - 29999 VCS Configuration > Protocols > SIP > Configuration
xConfiguration SIP TCP Outbound Port Start
xConfiguration SIP TCP Outbound Port End
not configurable

Service/Function Description Default Available Range Configurable via
Traversal media port range For traversal calls (i.e. where the VCS is taking the media as well as the signaling), the range of ports to be used for the media. Ports are allocated from this range in pairs, the first of each being even. Therefore the range must start with an even number. See Configuring the Traversal Subzone Ports for more information.
1024 - 65533 VCS Configuration > Local Zone > Traversal Subzone
xConfiguration Traversal Media Port Start
xConfiguration Traversal Media Port End
STUN Relay media port range
The range of ports to be used for STUN media relay.
1024 - 65534 VCS Configuration > Expressway > STUN
xConfiguration Traversal Server STUN Relay Media Port Start
xConfiguration Traversal Server STUN Relay Media Port End
LDAP used for outbound connection to an LDAP server a random TCP source port is used
TMS used for outbound connection to TMS a random source port in the range 32768 - 65535 is used
User Policy Server used for outbound connection to a User Policy Server
a random source port in the range 32768 - 65535 is used

This section gives examples of DNS configuration using Microsoft DNS Server and BIND 8 & 9.
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:
In these examples we show how to set up an SRV record to handle H.323 URIs of the form user@example.com. 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.
dnscmd . /RecordAdd domain service _ name SRV Priority Weight Port Target • where:
domain is the domain into which you wish to insert the record
service _ name is the name of the service you’re adding
Priority is the priority as defined by RFC 2782 [3]
Weight is the weight as defined by RFC 2782 [3]
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:
It is assumed that both A and AAAA records already exist for vcs.example.com. If not, you will need to add one.
dnscmd . /RecordAdd example.com _ h323ls. _ udp SRV 1 0 1719 vcs.example.com •
BIND 8 & 9
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.
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
For example:
nslookup -querytype=srv _ h323ls. _ udp. • example.com and check the output.
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 [6].

Microsoft Active Directory
The VCS can be configured to use a database on an LDAP Directory Server to store authentication credential information (usernames, passwords, and other relevant information)
These step-by-step instructions assume that Active Directory has already been installed. For details on installing Active Directory please consult your Windows documentation.
This section describes how to download the schemas that must be installed on the LDAP server, and how to install and configure two common types of LDAP servers, Microsoft Active Directory and OpenLDAP, for use with the VCS.
The following instructions are for Windows Server 2003 Enterprise Edition. If you are not using this version of Windows, your instructions may vary.
Once you have downloaded the H.350 schemas, install them as follows:
Open a command prompt and for each file execute the following command:
ldifde -i -c DC=X -f filename.ldf
where:
The following ITU specification describes the schemas which are required to be installed on the LDAP server:
is the base DN for your Active Directory 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.
The schemas can be downloaded in ldif format from the web interface on the VCS. To do this:
Navigate to 1. VCS Configuration > Authentication > LDAP > Schemas. You will see a list of downloadable schemas.
Click on the 2. Download button next to each file to open it.

Adding H.350 Objects
Add the ldif file to the server using the command: 2. ldifde -i -c DC=X -f filename.ldf
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:
Create the Organizational Hierarchy
where:
is the base DN of your Active Directory Server.
Open up the Active Directory 1. Users and Computers MMC snap-in.
Be located in the Local Computer’s Personal certificate store. • This can be seen using the Certificates MMC snap-in.
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.
Under your BaseDN right-click and select 2. New Organizational Unit.
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’’.
Create an Organizational unit called 3. 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.
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.
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.
Add the H.350 Objects
Create an 1. ldif file with the following contents:
Issued by a CA that both the domain controller and the client • trust.
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 CA’s certificate as a trusted CA certificate. This can be done on the VCS by navigating to:
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 the section Alias Origin Setting.
# MeetingRoom1 endpoint

Prerequisites
Installing the H.350 Schemas
These instructions assume that an OpenLDAP server has already been installed. For details on installing OpenLDAP see the documentation at http://www.openldap.org
Copy the OpenLDAP files to the OpenLDAP schema directory: 1.
/etc/openldap/schemas/commobject.ldif
/etc/openldap/schemas/h323identity.ldif
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.
/etc/openldap/schemas/h235identity.ldif
/etc/openldap/schemas/sipidentity.ldif
Edit 2. /etc/openldap/slapd.conf to add the new schemas. You will need to add the following lines:
include /etc/openldap/schemas/commobject.ldif
include /etc/openldap/schemas/h323identity.ldif
include /etc/openldap/schemas/h235identity.ldif
include /etc/openldap/schemas/sipidentity.ldif
The OpenLDAP daemon (slapd) must be restarted for the new schemas to take effect.

Adding H.350 Objects
Add the H.350 Objects
Create an 1. ldif file with the following contents:
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 server’s identity. Once the certificate has been created you will need to install the following three files associated with the certificate onto the LDAP server:
Create the Organizational Hierarchy
Create an 1. ldif file with the following contents:
# This example creates a single # organizational unit to contain the H.350 # objects
Add the ldif file to the server using the command: 2.
All three files should be in PEM file format.
slapadd -l
The LDAP server must be configured to use the certificate. To do this:
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.
Edit 1. /etc/openldap/slapd.conf and add the following three lines:
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.
TLSCACertificateFile
TLSCertificateFile
Add the 2. ldif file to the server using the command:
TLSCertificateKeyFile
slapadd -l
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@domain.com. The entry also has H.235 and SIP credentials of ID meetingroom1 and password mypassword which are used during authentication.
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 CA’s certificate as a trusted CA certificate. This can be done on the VCS by navigating to:
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 the section Alias Origin Setting.
The SIP URI in the ldif file must be prefixed by sip:.
# MeetingRoom1 endpoint

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.
The valid values for this command are one of the options shown within the angle brackets.
The following pages list all the xConfiguration commands currently available on the VCS.
To set a particular item of configuration, type the command as shown. The valid values for each command are indicated in the angle brackets following each command; these are explained opposite.
The valid value for this command is an integer. The minimum and maximum values are shown within the angle brackets.
To obtain information about the existing configuration on the VCS:
type • xConfiguration to return all current configuration settings for the VCS.
type • xConfiguration to return all current configuration for that particular element and all its sub-elements.
type • xConfiguration to return all current configuration for that group of sub-elements.
The valid value for this command is a string. The minimum and maximum number of characters is shown after the S.
To obtain information about using each of the xConfiguration commands:
When issuing this command, the string must be typed in double quotes.
type • xConfiguration ? to return a list of all elements available under the xConfiguration command.
type • xConfiguration ? to return all available sub-elements, along with the valuespace and description, and default values for each.
Square brackets indicate that you can configure more than one of this particular item. Each item is assigned an index within the range shown.
type • xConfiguration ? to return all available sub-elements, along with the valuespace and description, and default values for each.

Determines whether HTTP calls will be redirected to the HTTPS port. On: calls will be redirected to HTTPS. Off: no HTTP access will be available. Note: You must restart the system for any changes to take effect. Default: On
Determines whether the VCS can be accessed via the web server. This must be On to enable both web interface and TMS access. Note: You must restart the system for any changes to take effect. Default: On
Determines whether the VCS can be accessed via SSH and SCP. Note: You must restart the system for any changes to take effect. Default: On
Determines whether the VCS can be accessed via telnet. Note: You must restart the system for any changes to take effect. Default: Off
Sets the number of minutes that an administration session (HTTPS, Telnet or SSH) may be inactive before the session is timed out. A value of 0 turns session time outs off. Default: 0
Specifies the IP Address of an Alternate VCS. Up to 5 Alternates may be configured. When the VCS receives a Location Request, all Alternates will also be queried. Note: must be a Valid IPv4 or IPv6 address
Defines the name for this entry in the local authentication database.

Authentication Credential [1..2500] Password:
Defines the password for this entry in the local authentication database.
Selects between a local database and a remote LDAP repository for the storage of password information for authentication. Default: LocalDatabase
Determines which aliases (i.e. from the LDAP repository or the endpoint) should be used to register the endpoint. Combined: the endpoint will be registered both with the aliases which it has presented and with those configured in the LDAP repository. Default: LDAP
Specifies the Distinguished Name to use when connecting to an LDAP server.
Determines whether or not to enforce authentication for H.323 and SIP registrations. Default: Off
Specifies the password to be used by the VCS when authenticating with another system, including when your VCS is a traversal client connecting to a traversal server.
Specifies the user name to be used by the VCS when authenticating with another system, including when your VCS is a traversal client connecting to a traversal server.
Sets the bandwidth (in kbps) to be used on calls managed by the VCS in cases where no bandwidth has been specified by the endpoint. Default: 384

Determines whether or not the VCS will attempt to downspeed a call if there is insufficient per-call bandwidth available to fulfill the request. On: the VCS will attempt to place the call at a lower bandwidth. Off: the call will be rejected. Default: On
Determines whether or not the VCS will attempt to downspeed a call if there is insufficient total bandwidth available to fulfill the request. On: the VCS will attempt to place the call at a lower bandwidth. Off: the call will be rejected. Default: On
Assigns a name to this link.
Specifies the first zone or subzone to which this link will be applied.
Specifies the second zone or subzone to which this link will be applied.
Specifies the first pipe to be associated with this link.
Specifies the second pipe to be associated with this link.
Bandwidth Pipe [1..100] Bandwidth PerCall Limit:
If this pipe has limited per-call bandwidth, sets the maximum amount of bandwidth (in kbps) available for any one call. Default: 1920

Bandwidth Pipe [1..100] Bandwidth PerCall Mode:
Determines whether or not this pipe is limiting the bandwidth of individual calls. NoBandwidth: no bandwidth available. No calls can be made on this pipe. Default: Unlimited
Bandwidth Pipe [1..100] Bandwidth Total Limit:
If this pipe has limited bandwidth, sets the maximum bandwidth (in kbps) available at any one time on the pipe. Default: 500000
Bandwidth Pipe [1..100] Bandwidth Total Mode:
Determines whether or not this pipe is enforcing total bandwidth restrictions. NoBandwidth: no bandwidth available. No calls can be made on this pipe. Default: Unlimited
Assigns a name to this pipe.
Determines the way in which the VCS will attempt to call systems which are not registered with it or one of its neighbors. 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. Default: Indirect
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.
Determines whether the VCS will automatically send details of application failures to a specified web service. Note: You must restart the system for any changes to take effect.

The URL of the web service to which error reports are sent. Default: Off
Specifies the IPv4 address of the specified LAN port. Note: You must restart the system for any changes to take effect. Default: 192.168.0.100
Specifies the IPv4 subnet mask of the specified LAN port. Note: You must restart the system for any changes to take effect.
Specifies the IPv6 address of the specified LAN port. Note: You must restart the system for any changes to take effect
Sets the speed of the Ethernet link from the specified LAN port. Use Auto to automatically configure the speed. Note: You must restart the system for any changes to take effect.
Sets the IP Address or Fully Qualified Domain Name (FQDN) of the External Manager.
Sets the URL of the External Manager. Default: tms/public/external/management/SystemManagementService.asmx
Determines whether or not the VCS responds to gatekeeper discovery requests from endpoints. Default: On

H323 Gatekeeper CallSignaling PortRange End:
Specifies the upper port in the range to be used by calls once they are established. Default: 19999
H323 Gatekeeper CallSignaling PortRange Start:
Specifies the lower port in the range to be used by calls once they are established. Default: 15000
Specifies the port that listens for H.323 call signaling. Default: 1720
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
H323 Gatekeeper Registration ConflictMode:
Determines how the system will behave if an endpoint attempts to register an alias currently registered from another IP Address. Reject: denies the registration. Overwrite: deletes the original registration and replaces it with the new registration. Default: Reject
Specifies the port to be used for H.323 UDP registrations. Default: 1719
Specifies the interval (in seconds) at which an H.323 endpoint must re-register with the VCS in order to confirm that it is still functioning. Default: 1800

Determines whether or not the VCS will provide H.323 gatekeeper functionality. Default: On
Determines whether or not the VCS will allow encrypted calls between SIP and H.323 endpoints. Off: interworked calls will never be encrypted. Auto: interworked calls will be encrypted if the endpoints request it. Default: Auto
Determines whether or not the VCS will act as a gateway between SIP and H.323 calls. Off: the VCS will not act as a SIP-H.323 gateway. RegisteredOnly: the VCS will act as a SIP-H.323 gateway but only if at least one of the endpoints is locally registered. On: the VCS will act as SIP-H.323 gateway regardless of whether the endpoints are locally registered. Default: RegisteredOnly
Specifies the name to be appended to the host name before a query to the DNS server is executed. Used only when attempting to resolve a domain name which is not fully qualified for NTP, LDAP, External Manager and Log servers.
Sets the IP Address of up to 5 DNS servers to be used when resolving domain names.
Specifies the IPv4 gateway of the VCS. Note: You must restart the system for any changes to take effect. Default: 127.0.0.1
Specifies an IP Address used in conjunction with the Prefix Length to determine the network to which this route applies.

Specifies the IP Address of the Gateway for this route.
Specifies the LAN interface to use for this route. Auto: The VCS will select the most appropriate interface to use. Default: Auto
Specifies the number of bits of the IP Address which must match when determining the network to which this route applies.
Specifies the IPv6 gateway of the VCS. Note: You must restart the system for any changes to take effect.
Selects whether the VCS is operating in IPv4, IPv6 or dual stack mode. Note: You must restart the system for any changes to take effect. Default: IPv4
Sets the encryption to be used for the connection to the LDAP server. Off: no encryption is used. TLS: TLS encryption is used. Default: Off
Sets the password to be used when binding to the LDAP server.
Sets the IP Address or Fully Qualified Domain Name (FQDN) of the LDAP server to be used when making LDAP queries.
Sets the IP port of the LDAP server to be used when making LDAP queries. Default: 389

Sets the user distinguished name to be used when binding to the LDAP server.
Controls the granularity of event logging. 1 is the least verbose, 3 the most. Note: this setting is not retrospective; it will determine which events are written to the event log from now onwards. Default: 1
Specifies the IP Address or Fully Qualified Domain Name (FQDN) of the remote syslog server to which the log will be written. This server must support the BSD syslog protocol. It cannot be another VCS.
Sets the IP Address or Fully Qualified Domain Name (FQDN) of the NTP server to be used when synchronizing system time.
Specifies the option key of your software option. These are added to the VCS in order to add extra functionality, such as increasing the VCS’s capacity. Contact your TANDBERG representative for further information.
Enables and disables use of Administrator Policy. Default: Off
Determines the User Policy Manager usage and location. Off: User Policy Manager is not used. Local: the on-box User Policy Manager is used. Remote: the off-box User Policy Manager is used. Default: Local
Specifies the IP Address or Fully Qualified Domain Name (FQDN) of the remote User Policy Manager.

Specifies the password used by the VCS to log in and query the remote User Policy Manager.
Specifies the URL of the remote User Policy Manager. Default: otimgr/query.php
Specifies the protocol used to connect to the remote User Policy Manager. Default: HTTP
Specifies the user name used by the VCS to log in and query the remote User Policy Manager.
Registration AllowList [1..2500] Pattern String:
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.
Registration AllowList [1..2500] Pattern Type:
Specifies whether the entry in the Allow List is a prefix, suffix, regular expression, or must be matched exactly. Default: Exact
Registration DenyList [1..2500] Pattern String:
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.
Registration DenyList [1..2500] Pattern Type:
Specifies whether the entry in the Deny List is a prefix, suffix, regular expression, or must be matched exactly. Default: Exact
Specifies the policy to be used when determining which endpoints may register with the system. Default: None

Specifies a domain for which this VCS is authoritative.
Determines whether or not the VCS will provide SIP registrar and SIP proxy functionality. Default: On
Specifies the period (in seconds) within which a SIP endpoint must re-register with the VCS to prevent its registration expiring. Default: 60
Specifies how proxied registrations should be handled. 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 VCS’s existing call processing rules. Default: Off
Determines whether incoming SIP calls using the TCP protocol will be allowed. Default: On
Specifies the upper port in the range to be used by outbound TCP/TLS SIP connections. Default: 29999
Specifies the lower port in the range to be used by outbound TCP/TLS SIP connections. Default: 25000

Specifies the listening port for incoming SIP TCP calls. Default: 5060
Determines whether incoming SIP calls using the TLS protocol will be allowed. Default: On
Specifies the listening port for incoming SIP TLS calls. Default: 5061
Determines whether incoming SIP calls using the UDP protocol will be allowed. Default: On
Specifies the listening port for incoming SIP UDP calls. Default: 5060
Sets the VCS’s SNMP community name. Default: public
Enables or disables SNMP support. Note: You must restart the system for any changes to take effect. Default: On
Specifies the name of the person who can be contacted regarding issues with the VCS.

Specifies the physical location of the VCS.
Defines the name of the VCS. Choose a name that uniquely identifies the system.
Defines the password of the VCS. The password is used to login with Telnet, HTTP(S), SSH, SCP, and on the serial port.
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
Determines how the matched part of the alias will be modified. Strip: the matching prefix or suffix will removed from the alias. Replace: the matching part of the alias will be substituted with the text in the Pattern Replace string.
(Applies only if pattern behavior is set to Replace.) Specifies the string to be used as a substitution for the part of the alias that matched the pattern.
Specifies the pattern against which the alias is compared.
Determines the way in which the string must match the alias. 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.

Assigns a priority to the specified transform. Transforms are applied in order of priority, and the priority must be unique for each transform.
For traversal calls (i.e. where the VCS is taking the media as well as the signaling), specifies the upper port in the range to be used for the media. Ports are allocated from this range in pairs, the first of each being even. Therefore the range must end with an odd number. Default: 51199
For traversal calls (i.e. where the VCS is taking the media as well as the signaling), specifies the lower port in the range to be used for the media. Ports are allocated from this range in pairs, the first of each being even. Therefore the range must start with an even number. Default: 50000
Traversal Server H323 Assent CallSignaling Port:
Specifies the port on the VCS to be used for Assent signaling. Default: 2776
Traversal Server H323 H46018 CallSignaling Port:
Specifies the port on the VCS to be used for H460.18 signaling. Default: 2777
Traversal Server Media Demultiplexing RTCP Port:
Specifies the port on the VCS to be used for demultiplexing RTCP media. Note: You must restart the system for any changes to take effect. Default: 2777
Traversal Server Media Demultiplexing RTP Port:
Specifies the port on the VCS to be used for demultiplexing RTP media. Note: You must restart the system for any changes to take effect. Default: 2776
Determines whether the VCS will offer STUN discovery services to traversal clients. Default: On

Specifies the port to be used for STUN discovery services. Default: 3478
Traversal Server STUN Relay Media Port End:
Specifies the upper port in the range to be used for STUN media relay. Default: 61200
Traversal Server STUN Relay Media Port Start:
Specifies the lower port in the range to be used for STUN media relay. Default: 60000
Determines whether the VCS will offer STUN relay services to traversal clients. Default: On
Specifies the listening port for STUN relay requests. Default: 4678
Zones LocalZone DefaultSubZone Bandwidth PerCall Inter Limit:
Specifies the bandwidth limit (in kbps) for any one call to or from an endpoint in the Default Subzone (applies only if Mode is set to Limited). Default: 1920
Zones LocalZone DefaultSubZone Bandwidth PerCall Inter Mode:
Determines whether there is a limit on the bandwidth for any one call to or from an endpoint in the Default Subzone. NoBandwidth: no bandwidth available. No calls can be made to or from the Default Subzone. Default: Unlimited
Zones LocalZone DefaultSubZone Bandwidth PerCall Intra Limit:
Specifies the bandwidth limit (in kbps) for any one call between two endpoints within the Default Subzone (applies only if Mode is set to Limited). Default: 1920

Zones LocalZone DefaultSubZone Bandwidth PerCall Intra Mode:
Determines whether there is a limit on the bandwidth for any one call between two endpoints within the Default Subzone. NoBandwidth: no bandwidth available. No calls can be made within the Default Subzone. Default: Unlimited
Zones LocalZone DefaultSubZone Bandwidth Total Limit:
Sets the total bandwidth limit (in kbps) of the Default Subzone (applies only if Mode is set to Limited). Default: 500000
Zones LocalZone DefaultSubZone Bandwidth Total Mode:
Determines whether the Default Subzone has a limit on the total bandwidth being used by its endpoints at any one time. NoBandwidth: no bandwidth available. No calls can be made to, from, or within the Default Subzone. Default: Unlimited
Zones LocalZone SubZone [1..100] Bandwidth PerCall Inter Limit:
Specifies 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
Zones LocalZone SubZone [1..100] Bandwidth PerCall Inter Mode:
Determines whether there is a limit on the bandwidth 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
Zones LocalZone SubZone [1..100] Bandwidth PerCall Intra Limit:
Specifies the bandwidth limit (in kbps) for any one call between two endpoints within this subzone (applies only if Mode is set to Limited). Default: 1920
Zones LocalZone SubZone [1..100] Bandwidth PerCall Intra Mode:
Determines whether there is a limit on the bandwidth for any one call between two endpoints within this subzone. NoBandwidth: no bandwidth available. No calls can be made within this subzone. Default: Unlimited

Zones LocalZone SubZone [1..100] Bandwidth Total Limit:
Sets the total bandwidth limit (in kbps) of this subzone (applies only if Mode is set to Limited). Default: 500000
Zones LocalZone SubZone [1..100] Bandwidth Total Mode:
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
Assigns a name to this subzone.
Zones LocalZone SubZone [1..100] Subnet [1..5] IP Address:
Specifies an IP Address used (in conjunction with the IP Prefix Length) to identify a subnet to be assigned to this subzone. Default: 0.0.0.0
Zones LocalZone SubZone [1..100] Subnet [1..5] IP PrefixLength:
Specifies the number of bits of the Subnet IP Address which must match for an IP Address to belong in this subzone. Default: 32
Zones LocalZone Traversal H323 Assent Mode:
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
Zones LocalZone Traversal H323 H46018 Mode:
Determines whether or not H.323 calls using H460.18 mode for firewall traversal will be allowed. Applies to traversal-enabled endpoints registered directly with the VCS. Default: On

Zones LocalZone Traversal H323 H46019 Demultiplexing Mode:
Determines whether the VCS will operate in Demultiplexing mode for calls from traversal-enabled endpoints registered directly with it. On: allows use of the same two ports for all calls. Off: Each call will use a separate pair of ports for media. Default: Off
Zones LocalZone Traversal H323 Preference:
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
Zones LocalZone Traversal H323 TCPProbe KeepAliveInterval:
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 firewall’s NAT bindings open. Default: 20
Zones LocalZone Traversal H323 TCPProbe RetryCount:
Sets the number of times traversal-enabled endpoints registered directly with the VCS will attempt to send a TCP probe to the VCS. Default: 5
Zones LocalZone Traversal H323 TCPProbe RetryInterval:
Sets the frequency (in seconds) with which traversal-enabled endpoints registered directly with the VCS will send a TCP probe to the VCS. Default: 2
Zones LocalZone Traversal H323 UDPProbe KeepAliveInterval:
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 firewall’s NAT bindings open. Default: 20
Zones LocalZone Traversal H323 UDPProbe RetryCount:
Sets the number of times traversal-enabled endpoints registered directly with the VCS will attempt to send a UDP probe to the VCS. Default: 5

Zones LocalZone Traversal H323 UDPProbe RetryInterval:
Sets the frequency (in seconds) with which traversal-enabled endpoints registered directly with the VCS will send a UDP probe to the VCS. Default: 2
Zones LocalZone TraversalSubZone Bandwidth PerCall Limit:
Specifies the bandwidth limit (in kbps) applied to any one traversal call being handled by the VCS (applies only if Mode is set to Limited). Default: 1920
Zones LocalZone TraversalSubZone Bandwidth PerCall Mode:
Determines whether there is a limit on the bandwidth of any one traversal call being handled by the VCS. NoBandwidth: no bandwidth available. No traversal calls can be made. Default: Unlimited
Zones LocalZone TraversalSubZone Bandwidth Total Limit:
Specifies the total bandwidth (in kbps) allowed for all traversal calls being handled by the VCS (applies only if Mode is set to Limited). Default: 500000
Zones LocalZone TraversalSubZone Bandwidth Total Mode:
Determines whether or not there is a limit to the total bandwidth of all traversal calls being handled by the VCS. NoBandwidth: no bandwidth available. No traversal calls can be made. Default: Unlimited
Specifies the DNS zone to be appended to the transformed E.164 number to create an ENUM host name which this zone is then queried for.
Determines whether H.323 calls will be allowed to and from this zone. Default: On

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
Zones Zone [1..200] Match [1..5] Mode:
Determines if and when a query will be sent to this zone. Always: the zone will always be queried. Pattern: the zone will only be queried if the alias queried for matches the corresponding pattern. Disabled: the zone will never be queried. Default: AlwaysMatch (Match 1) Disabled (Matches 2-5)
Zones Zone [1..200] Match [1..5] Pattern Behavior:
(Applies only if the Match mode is Pattern Match.) Determines whether the matched part of the alias should be modified before an LRQ is sent to this zone. Leave: the alias will be unmodified. Strip: the matching prefix or suffix will be removed from the alias. Replace: the matching part of the alias will be substituted with the text in the Replace string. Default: Leave
Zones Zone [1..200] Match [1..5] Pattern Replace:
(Applies only if the Pattern Behavior is Replace.) Specifies the string to be used as a substitution for the part of the alias that matched the pattern.
Zones Zone [1..200] Match [1..5] Pattern String:
(Applies only if the Match mode is Pattern Match.) Specifies the pattern against which the alias is compared.
Zones Zone [1..200] Match [1..5] Pattern Type:
(Applies only if the Match mode is Match.) Determines the way in which the string must match the alias. 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: Prefix

Zones Zone [1..200] Match [1..5] Priority:
Determines the order in which the zone will be sent a search request. Zones with priority 1 matches are searched first, followed by priority 2, and so on. Default: 100
Assigns a name to this zone.
Zones Zone [1..200] Neighbor Alternate [1..5] Address:
Specifies the IP Addresses or Fully Qualified Domain Names (FQDNs) of any Alternates configured on this neighbor.
Zones Zone [1..200] Neighbor H323 Port:
Specifies the port on the neighbor to be used for H.323 calls to and from this VCS. Default: 1719
Zones Zone [1..200] Neighbor Primary Address:
Specifies the IP Address or Fully Qualified Domain Name (FQDN) of this neighbor.
Zones Zone [1..200] Neighbor SIP Port:
Specifies the port on the neighbor to be used for SIP calls to and from this VCS. Default: 5060
Zones Zone [1..200] Neighbor SIP Transport:
Determines which transport type will be used for SIP calls to and from this neighbor. Default: TCP
Determines whether SIP calls will be allowed to and from this zone. Default: On
Zones Zone [1..200] TraversalClient Alternate [1..5] Address:
Specifies the IP Address or Fully Qualified Domain Name (FQDN) of any Alternates of the traversal server.

Command Reference - xConfiguration
Zones Zone [1..200] TraversalClient H323 Port:
Specifies the port on the traversal server to be used for H.323 firewall traversal 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. Default: 2777
Zones Zone [1..200] TraversalClient H323 Protocol:
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
Zones Zone [1..200] TraversalClient Primary Address:
Specifies the IP Address or Fully Qualified Domain Name (FQDN) of the traversal server.
Zones Zone [1..200] TraversalClient RetryInterval:
Specifies the interval (in seconds) with which a failed attempt to establish a connection to the traversal server should be retried. Default: 120
Zones Zone [1..200] TraversalClient SIP Port:
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. Default: 5060
Zones Zone [1..200] TraversalClient SIP Transport:
Determines which transport type will be used for SIP calls to and from the traversal server. Default: TCP
Zones Zone [1..200] TraversalServer Authentication UserName:
The name used by the traversal client when authenticating with the traversal server. If the traversal client is a VCS, this must be the VCS’s Authentication User Name. If the traversal client is a gatekeeper, this must be the gatekeeper’s System Name.

Zones Zone [1..200] TraversalServer H323 H46019 Demultiplexing Mode:
Determines whether the VCS will operate in Demultiplexing mode for calls from the traversal client. On: allows use of the same two ports for all calls. Off: Each call will use a separate pair of ports for media. Default: Off
Zones Zone [1..200] TraversalServer H323 Port:
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.
Zones Zone [1..200] TraversalServer H323 Protocol:
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
Zones Zone [1..200] TraversalServer SIP Port:
Specifies the port on the VCS being used for SIP firewall traversal from this traversal client. Default: 7001, incrementing by 1 for each new zone.
Zones Zone [1..200] TraversalServer SIP Transport:
Determines which of the two transport types will be used for SIP calls between the traversal client and VCS. Default: TCP
Zones Zone [1..200] TraversalServer TCPProbe KeepAliveInterval:
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 firewall’s NAT bindings open. Default: 20
Zones Zone [1..200] TraversalServer TCPProbe RetryCount:
Sets the number of times the traversal client will attempt to send a TCP probe to the VCS. Default: 5

Zones Zone [1..200] TraversalServer TCPProbe RetryInterval:
Sets the frequency (in seconds ) with which the traversal client will send a TCP probe to the VCS. Default: 2
Zones Zone [1..200] TraversalServer UDPProbe KeepAliveInterval:
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 firewall’s NAT bindings open. Default: 20
Zones Zone [1..200] TraversalServer UDPProbe RetryCount:
Sets the number of times the traversal client will attempt to send a UDP probe to the VCS. Default: 5
Zones Zone [1..200] TraversalServer UDPProbe RetryInterval:
Sets the frequency (in seconds) with which the traversal client will send a UDP probe to the VCS. Default: 2
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.

The xCommand group of commands are used to add and delete items and issue system commands.
The valid values for this parameter are one of the options shown within the angle brackets.
The following pages list all the xCommand commands currently available on the VCS.
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; these are explained opposite.
The valid value for this parameter is an integer. The minimum and maximum values are shown within the angle brackets.
To obtain information about using each of the xCommand commands from within the CLI:
type • xCommand or xCommand ? to return all current xCommand commands available on the VCS.
type • xCommand or xCommand ? to return all parameters for that command, along with the valuespace and a description for each.
The valid value for this parameter is a string. The minimum and maximum number of characters is shown after the S.
When issuing this command, the string must be typed in double quotes.
(r) indicates that this is a required parameter. The (r) is not part of the command.

Adds an entry to the Allow List.
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:
Specifies whether the entry in the Allow List is a prefix, suffix, regular expression, or must be matched exactly.
Deletes an entry from the Allow List.
The index of the entry to be deleted.
Restarts the VCS.
This command has no parameters.
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.
The subzone or zone from which the call originates. Node2(r):
The subzone or zone at which the call terminates. Bandwidth(r):
The requested bandwidth of the call (in kbps). CallType(r):
Whether the call type is Traversal or Non Traversal.

A diagnostic tool that allows you to check the result of an alias transform (local or zone) before you configure it on the system. Note that this command does not change any existing system configuration.
The pattern against which the alias is to be compared. Type(r):
The way in which the pattern must match the alias in order for the transform to be applied. Behavior(r):
The way in which the alias will be modified. Replace:
(Applies only if Behavior is set to Replace.) The string to be substituted for the part of the alias that matched the pattern.
Example: xCommand CheckPattern Target: "john.smith@example.net" Pattern: "@example.net" Type: "suffix" Behavior: replace Replace: "@example.com"
Adds an entry to the local authentication database.
Defines the name for this entry in the local authentication database. CredentialPassword(r):
Defines the password for this entry in the local authentication database.
Deletes an entry from the local authentication database.
The index of the credential to be deleted.
Restores links between the Default Subzone, Traversal Subzone and the Default Zone.
This command has no parameters.

Resets system parameters to default values.
The level of system parameters to be reset. Level 1: will reset most parameters. Level 2: There are currently no level 2 parameters, so setting that level has the same effect as setting level 1. Level 3 resets all level 1 and 2 parameters as well as additional parameters. See the section Restoring Default Configuration for full details.
Adds an entry to the Deny List.
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:
Specifies whether the entry in the Deny List is a prefix, suffix, regular expression, or must be matched exactly.
Deletes an entry from the Deny List.
The index of the entry to be deleted.
Disconnects a call.
The index of the call to be disconnected. CallSerialNumber:
The serial number of the call to be disconnected. Note: you must specify either a call index or call serial number when using this command.
Adds a SIP domain for which this VCS is authoritative.
Specifies the name of the domain.


The ID of the feedback request to be deactivated.

Activates notifications on the event or status change(s) described by the Expression(s). Notifications are sent in XML format to the specified URL. Up to 15 Expressions may be registered for each of 3 feedback IDs.
The ID of this particular feedback request. URL(r):
The URL to which notifications are to be sent. Expression.1..15:
The events or status change to be notified. Valid Expressions are: Status/Ethernet Status/NTP Status/LDAP Status/Feedback Status/ExternalManager Status/Calls Status/Registrations Status/Zones Event/CallAttempt Event/CallConnected Event/CallDisconnected Event/CallFailure Event/RegistrationAdded Event/RegistrationRemoved Event/RegistrationFailure Event/RegistrationChanged Event/Bandwidth Event/Locate Event/ResourceUsage Event/AuthenticationFailure.
Example: xCommand FeedbackRegister ID: 1 URL: " http://192.168.0.1/submitfeedback/" Expression.1: "Status/Calls" Expression.2: "Event/ CallAttempt"
Returns information about the registration associated with the specified alias. The alias must be registered on the VCS on which the command is issued.
The alias that you wish to find out about.
FeedbackRegister · FindRegistration

Adds and configures a new link.
Assigns a name to this link. Node1:
Specifies the first zone or subzone to which this link will be applied. Node2:
Specifies the second zone or subzone to which this link will be applied. Pipe1:
Specifies the first pipe to be associated with this link. Pipe2:
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"
Deletes a link.
The index of the link to be deleted.
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).
The alias associated with the endpoint you wish to locate. HopCount(r):
The hop count to be used in the search. Protocol(r):
The protocol used to initiate the search.
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 TANDBERG representative for further information.
Specifies the option key of your software option.

Deletes a software option key from the VCS.
Specifies the ID of the software option to be deleted.
Adds and configures a new pipe.
Assigns a name to this pipe. TotalMode:
Determines whether or not this pipe is enforcing total bandwidth restrictions. NoBandwidth: no bandwidth available; no calls can be made using this pipe. Total:
If this pipe has limited bandwidth, sets the maximum bandwidth (in kbps) available at any one time on the pipe. PerCallMode:
Determines whether or not this pipe is limiting the bandwidth of individual calls. NoBandwidth: no bandwidth available; no calls can be made using this pipe. PerCall:
If this pipe has limited per-call bandwidth, sets the maximum amount of bandwidth (in kbps) available for any one call.
Deletes a pipe.
The index of the pipe to be deleted.
Removes a registration from the VCS.
The index number of the registration to be removed. RegistrationSerialNumber:
The serial number of the registration to be removed.

Adds and configures a new route.
Specifies an IP Address used in conjunction with the Prefix Length to determine the network to which this route applies. PrefixLength(r):
Specifies the number of bits of the IP Address which must match when determining the network to which this route applies. Gateway(r):
Specifies the IP Address of the Gateway for this route. Interface:
Specifies the LAN interface to use for this route. Auto: The VCS will select the most appropriate interface to use. Default: Auto
Adds and configures a new subzone.
Assigns a name to this subzone. Address:
Specifies an IP Address used (in conjunction with the IP Prefix Length) to identify a subnet to be assigned to this subzone. PrefixLength:
Specifies the number of bits of the Subnet IP Address which must match for an IP Address to belong in this subzone. TotalMode:
Determines whether the Default Subzone has a limit on the total bandwidth being used by its endpoints at any one time. Total:
Sets the total bandwidth limit (in kbps) of the Default Subzone (applies only if Mode is set to Limited). PerCallInterMode:
Determines whether there is a limit on the bandwidth for any one call to or from an endpoint in this subzone. PerCallInter:
Specifies 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). PerCallIntraMode:
Determines whether there is a limit on the bandwidth for any one call between two endpoints within this subzone. PerCallIntra:
Specifies the bandwidth limit (in kbps) for any one call between two endpoints within this subzone (applies only if Mode is set to Limited).
Example: xCommand SubZoneAdd SubZoneName: "BranchOffice" Address: "10.13.0.0" PrefixLength: 28 TotalMode: Limited Total: 1024 PerCallInterMode: Limited PerCallInter: 512 PerCallIntraMode: Limited PerCallIntra: 512
RouteAdd · SubZoneAdd

Deletes a subzone.
The index of the subzone to be deleted.
Adds and configures a new transform.
Specifies the pattern against which the alias is compared. Type:
Determines the way in which the string must match the alias. 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. Behavior:
Determines how the matched part of the alias will be modified. Strip: the matching prefix or suffix will removed from the alias. Replace: the matching part of the alias will be substituted with the text in the Replace string. Replace:
(Applies only if pattern behavior is set to Replace.) Specifies the string to be used as a substitution for the part of the alias that matched the pattern. Priority:
Assigns a priority to the specified transform. Transforms are applied in order of priority, and the priority must be unique for each transform.
Deletes a transform.
The index of the transform to be deleted.
Adds and configures a new zone.
Assigns a name to this zone. Type(r):
Determines the nature of the specified zone, in relation to the Local Zone. Neighbor: the new zone will be a neighbor of the Local Zone. TraversalClient: there is a firewall between the zones, and the Local Zone is a traversal client of the new zone. TraversalServer: there is a firewall between the zones and the Local Zone 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.


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.

The xStatus group of commands are used to return information about the current status of the VCS. Each xStatus element returns information about one or more sub-elements.
The following pages list all the xStatus commands currently available on the VCS, and the information that is returned by each.
To obtain information about the existing status on the VCS:
type • xStatus to return the current status of all status elements on the VCS.
type • xStatus to return the current status for that particular element and all its sub-elements.
type • xStatus 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.





Cause: {Visible if status is Failed}
External Manager:
Cause: {Visible if status is Failed}
Feedback [1..3]:












Cause: {Visible if Status is Failed}


Cause: {Visible if Status is Failed}











http://www.itu.int/rec/T-REC-H.235/en
5 RFC 3880: Call Processing Language (CPL): A Language for User Control of Internet Telephony Services http://www.ietf.org/rfc/rfc3880.txt
6 DNS and BIND Fourth Edition, Albitz and Liu, O’Reilly and Associates, ISBN: 0-596-00158-4
http://www.ietf.org/rfc/rfc3761.txt
9 Mastering Regular Expressions, Jeffrey E.F. Friedl, O’Reilly and Associates, ISBN: 1-56592-257-3
10 RFC 3327: Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts http://www.ietf.org/rfc/rfc3327.txt
11 Session Traversal Utilities for (NAT) (STUN) http://www.ietf.org/internet-drafts/draft-ietf-behave-rfc3489bis-06.txt
12 Obtaining Relay Addresses from Simple Traversal Underneath NAT (STUN) http://www.ietf.org/internet-drafts/draft-ietf-behave-turn-03.txt
21 RFC 3489: STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs) http://www.ietf.org/rfc/rfc3489.txt
22 XML and Writing CPL for TANDBERG Infrastructure products Rev 1.2 http://www.tandberg.com/collateral/documentation/Application_ Programmer_Interfaces/XML%20and%20Writing%20CPL%20for%20 TANDBERG%20Infrastructure%20Products.pdf
Reference Title Link

A record A type of DNS record that maps a domain name to an IPv4 address.
AAAA record A type of DNS record that maps a domain name to an IPv6 address.
Administrator Policy In relation to the VCS, the set of rules configured system-wide (either via the web interface or CPL script) that determine the action(s) to be applied to calls matching a given criteria.
Alias The name an endpoint uses when registering with the VCS. Other endpoints can then use this name to call it. An endpoint may register with more than one alias.
Alternate One or more VCSs configured to support the same zone in order to provide redundancy.
An endpoint RAS request to make or answer a call.
Assent TANDBERG’s proprietary protocol for firewall traversal.
Border Controller A TANDBERG device used to control multimedia networks and firewall traversal.
Call Policy The set of rules (administrator policy, user policy and transforms) that are applied to a single call to determine whether and how it is placed.
CLI Command Line Interface
A text-based user interface used to access the VCS.
CPL Call Processing Language
An XML-based language for defining call handling. Defined by RFC 3880 [5].
DNS Domain Name System
A distributed database linking domain names to IP addresses.
DNS zone On the VCS, a zone used to configure access to endpoints located via a DNS lookup.
E.164 An ITU standard for structured telephone numbers. Each telephone number consists of a country code, area code and subscriber number. For example, TANDBERG’s European Headquarters’ phone number is +47 67 125125, corresponding to a country code of 47 for Norway, area code of 67 for Lysaker and finally 125125 to determine which phone line in Lysaker.
ENUM tElephone NUmber Mapping
A means of mapping E.164 numbers to URIs using DNS.
ENUM zone On the VCS, a zone used to configure access to endpoints located via ENUM.
External Manager The remote system that is used to manage endpoints and network infrastructure. The TANDBERG Management Suite (TMS) is an example of an external manager.
Firewall traversal Crossing a firewall or NAT device.
FindMe™ A TANDBERG feature that allows users to have a single alias on which they can be reached regardless of the endpoint(s) they are currently using.
FQDN Fully Qualified Domain Name
A domain name that specifies the node’s position in the DNS tree absolutely, uniquely identifying the system or device. Note that in order to use FQDNs instead of IP Addresses when configuring the VCS, you must have at least one DNS server configured.
Gatekeeper A device used to control H.323 multimedia networks. An example is the TANDBERG Gatekeeper.
Gatekeeper Zone A collection of all the endpoints, gateways and MCUs managed by a single gatekeeper.
H.323 A standard that defines the protocols used for packet-based multimedia communications systems.
Term Definition · ARQ Admission Request

HTTP Hypertext Transfer Protocol
A protocol used for communications over the internet.
HTTPS Hypertext Transfer Protocol over Secure Socket Layer
A protocol used for secure communications over the internet, combining HTTP with TLS.
Hop count The maximum number of gatekeeper or SIP proxy devices (e.g. a VCS) that a message may be forwarded through before it is decided that its intended recipient is not reachable.
ICE Interactive Connectivity Establishment
A collaborative algorithm that works together with STUN services (and other NAT traversal techniques) to allow clients to achieve firewall traversal. This is the emerging traversal standard for use by SIP endpoints (although it could be used for other protocols).
IETF Internet Engineering Task Force
An organization that defines (via documents such as RFCs) the protocol standards and best practices relating to the design, use and management of the internet.
Interworking Allowing H.323 systems to connect to SIP systems.
IPv4 Internet Protocol version 4
Version 4 of the Internet Protocol, defined in RFC 791 [18].
IPv6 Internet Protocol version 6
Version 6 of the Internet Protocol, defined in RFC 2460 [19].
A request sent to an endpoint requesting information about its status.
LAN Local Area Network
A geographically limited computer network, usually with a high bandwidth throughput.
LDAP Lightweight Directory Access Protocol
A protocol for accessing on-line directories running over TCP/IP.
Link In relation to the VCS, a connection between two nodes.
Local Registration, Locally Registered Endpoint
A relative term used to refer to any endpoint or system that is registered with the Local VCS.
Local VCS A relative term used to refer to the particular VCS that you are currently administering, as opposed to other VCSs in your network.
Local Zone A relative term used to refer to the group of endpoints and other systems registered to a particular VCS.
A RAS query between gatekeepers to determine the location of an endpoint.
NAPTR record A type of DNS record.
NAT Network Address Translation
Also known as IP masquerading. Rewriting source and destination addresses as the IP packet passes through the NAT device.
Node In relation to the VCS, a node is one end of a link. A node can be a local subzone or a zone.
Term Definition · IRQ Information Request · LRQ Location Request

NTP Network Time Protocol
A protocol used for synchronizing clocks.
PEM Privacy-Enhanced Electronic Mail:
An IETF proposal for securing messages using public key cryptography.
Pipe In relation to the VCS, a means of controlling the bandwidth used on a link.
In SIP, an intermediary entity that acts as both a server and a client for the purpose of making requests on behalf of other clients. A proxy server primarily plays the role of routing, which means its job is to ensure that a request is sent to another entity “closer” to the targeted user. Proxies are also useful for enforcing policy (for example, making sure a user is allowed to make a call). A proxy interprets, and, if necessary, rewrites specific parts of a request message before forwarding it. While a proxy can set up calls between SIP endpoints, it does not participate in the call once it is set up.
RAS Registration, Admission and Status
A protocol used between H.323 endpoints and a gatekeeper to register and place calls.
Registrar In SIP, a server that accepts REGISTER requests and places the information it receives in those requests into the location service for the domain it handles. This information is used to advise other SIP Proxies/Registrars where to send calls for that endpoint.
A pattern used to match text strings according to a POSIX-defined syntax.
RFC Request for Comments
A process and result used by the IETF for Internet standards.
RS-232 A commonly used standard for computer serial ports.
RTCP RTP Control Protocol
A control protocol for RTP. Defined by RFC 3550 [17].
RTP Real-time Transport Protocol
Real time protocol designed for the transmission of voice and video. Defined by RFC 3550 [17].
An encrypted protocol used to provide a secure CLI.
SIP Session Initiation Protocol
IETF protocol for controlling multimedia communication. Defined by RFC 3261 [20].
SNMP Simple Network Management Protocol
A protocol used to monitor network devices.
Source Alias The alias present in the “source” field of a message.
SRV record Service record
A type of DNS record.
STUN Simple Traversal of UDP through NATs
Firewall NAT traversal for SIP. Defined by RFC 3489 [21].
Subzone A segment of a VCS zone.

TCP Transmission Control Protocol
A reliable communication protocol defined by RFC 791 [18].
Telnet A network protocol used on the internet or Local Area Networks (LANs).
TLS Transport Layer Security
A protocol that provides secure communications over the internet.
TMS TANDBERG Management Suite
A TANDBERG product used for the management of video networks.
Transform In relation to the VCS, the process of changing or replacing the alias being searched for.
Traversal call Any call where both signaling and media are routed through the VCS.
Traversal Client A traversal entity on the private side of a firewall. Examples are a TANDBERG Gatekeeper or TANDBERG VCS Control.
Traversal Server A traversal entity on the public side of a firewall. Examples are the TANDBERG Border Controller and the TANDBERG VCS Expressway.
Traversal-enabled endpoint Any endpoint that supports the Assent and/or ITU H.460.18 and H.460.19 standards for firewall traversal. This includes all TANDBERG MXP endpoints.
A SIP device used to make and receive calls.
UDP User Datagram Protocol
A communication protocol defined by RFC 791 [18]. It is less reliable than TCP.
URI Uniform Resource Identifier
A formatted string used to identify a resource, typically on the internet.
User Policy The set of rules that determine the action(s) to be applied to calls for a particular user or group.
VCS Video Communications Server
A generic term for the TANDBERG product which acts as a gatekeeper and SIP Proxy/Server.
VCS Control A VCS whose main function is to act as a gatekeeper, SIP proxy and firewall traversal client. This system will generally be located within the firewall.
VCS Expressway A VCS with the additional functionality of act as a firewall traversal server. This will generally be located outside the firewall.
Zone A collection of endpoints.
Term Definition · UA User Agent


Fax: +47 67 125 234 Video: +47 67 126 126 E-mail: [email protected]
U.S. HEADQUARTERS 1212 Avenue of the Americas 24th Floor, New York, NY 10036 Telephone: +1 212 692 6500
Pages referenced in this manual — manufacturer, support and downloads.
Owners and our team usually reply within a day — and your question helps the next person too.
Be the first to ask — other owners or our team will answer.