Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Applications
Cisco VCS Administrator Guide (X7.0)
Page 257 of 488
n
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.
is forwarded to the aliases associated with the active location for that user's FindMe configuration.
n
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.
the usual manner.
Note that User Policy is invoked after any Call Policy configured on the VCS has been applied. See
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:
a.
b. Must define a
(even if the VCS is not part of a cluster).
c. Decides whether to use a local or a remote
service.
If remote authentication is being used, the VCS administrator must also set up User groups.
d. Creates a
for each user or team of people who require a FindMe ID.
2. The owner of the FindMe ID configures their account settings.
See the FindMe deployment guide [
] for more details on setting up FindMe accounts.
Recommendations when deploying FindMe
n
The FindMe ID should be in the form of a URI, and should be the individual’s primary URI.
n
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.
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
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
john.smith@example.com
is added to the Deny List, to prevent an individual endpoint registering
with that alias.
Note: FindMe is supported by clustering. For information about how FindMe information is managed
across peers in a cluster, refer to
across peers in a cluster, refer to
.