149
D14049.05
February 2009
Grey Headline
(continued)
TANDBERG
VIDEO COMMUNICATIONS SERVER
ADMINISTRATOR GUIDE
Introduction
Getting started
Overview and
status
System
configuration
VCS
configuration
Zones and
neighbors
Call
processing
Bandwidth
control
Firewall
traversal
Appendices
Applications
Maintenance
FindMe™ (User Policy)
What is FindMe?
FindMe is a form of User Policy, which is the set of rules that
determines what happens to a call for a particular user or group
when it is received by the TANDBERG VCS.
The FindMe 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 dialed,
and can also specify what happens if those devices are busy or
go unanswered.
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.
To enable this feature you must purchase and install the
appropriate option key. Contact your TANDBERG representative
for information.
How are devices specified?
When configuring their FindMe account, users are asked to
specify the devices to which calls to their FindMe name will be
routed.
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.
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.
Process overview
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.
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.
User Policy is invoked after any Call 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?
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 following steps are required for the use of FindMe once the
feature has been installed:
A VCS administrator
1.
enables and configures FindM
e
.
A 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
.
Recommendations when deploying FindMe
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.
Example
Users at Example Corp. have a FindMe name in the format
john.
. 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
and their home endpoint
as
. Both of these endpoints are
included in the list of devices to ring when the FindMe name is
dialed. The alias
is added to the Deny
List, to prevent an individual endpoint registering with that alias.
FindMe is supported by clustering. For specific
information about how FindMe information is managed
across peers in a cluster, refer to the section
Clustering
and FindMe
.
User Policy Manager
The User Policy Manager is the application that manages the
FindMe user accounts.
The VCS has its own local User Policy Manager. However, it also
provides the ability to use a User Policy Manager on a remote
system; this feature is intended for future third party integration.
Overview
