Findme; Overview; Firewall; What Is Findme - Cisco TelePresence Administrator's Manual

Grey Headline (continued)

FindMe™

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 VCS.
The FindMe feature lets you assign a single FindMe ID to
individuals or teams in your enterprise. Users can set up a list
of locations such as "at home" or "in the office" and associate
their devices with those locations. They can then specify which
devices are called when their FindMe ID is dialed, and what
happens if those devices are busy or go unanswered. Each user
can specify up to 15 devices and 10 locations.
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 FindMe
option key.
Standard operation is to use the VCS's own FindMe manager.
However, you can use an off-box FindMe manager; this feature is
intended for future third-party integration.
Users configure their FindMe settings by logging into their user
account.

How are devices specified?

When configuring their user account, users are asked to specify
the devices to which calls to their FindMe ID are routed.
It is possible to specify aliases and even other FindMe IDs as
one or more of the devices. However, care must be taken in these
situations to avoid circular configurations.
For this reason, it is recommended that users specify the
physical devices they want to ring when their FindMe ID is called
by entering the alias with which that device has registered.
Overview and System
Introduction
status configuration
D14049.08
November 2010

Process overview

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

Who must do what before FindMe can be used?

The following steps are required for the use of FindMe after the
feature has been installed:
1. The VCS administrator
2. The VCS administrator must define a
VCS is not part of a cluster).
3. The VCS administrator decides whether to use a local or a
remote login account authentication
4. The VCS administrator
team of people who require a FindMe ID.
5. If remote authentication is being used, the VCS administrator
must also set up User
6. The owner of the FindMe ID
See the VCS Deployment Guide - FindMe [29]
details on setting up FindMe accounts.
Cisco VCS Zones and Clustering and
configuration neighbors peers

Overview

Search process
enables and configures FindMe.
Cluster name (even if the
service.
creates a user account for each user or
groups.
configures their account settings.
for more
Call Bandwidth
processing control
146
CISCO TELEPRESENCE VIDEO COMMUNICATION SERVER

Recommendations when deploying FindMe

•
The FindMe ID 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 ID. You can prevent this by including all
FindMe IDs on the Deny List.
Example
Users at Example Corp. have a FindMe ID in the format
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 ID is dialed. The alias john.smith@example.com is added
to the Deny List, to prevent an individual endpoint registering with
that alias.
FindMe is supported by clustering. For information about
how FindMe information is managed across peers in a
cluster, refer to the Clustering and FindMe

Firewall

Applications Maintenance
traversal
ADMINISTRATOR GUIDE
section.
Appendices