Cisco Cisco TelePresence Management Suite (TMS) Version 15
FindMe Accounts Hosted on Hifferent Cisco VCSs in a Network
FindMe accounts can be distributed across multiple Cisco VCSs (or Cisco VCS clusters), but each individual account
can be hosted on only one Cisco VCS (or Cisco VCS cluster).
can be hosted on only one Cisco VCS (or Cisco VCS cluster).
For FindMe to overwrite a caller ID with the caller's FindMe ID, the call signaling must pass through the Cisco VCS (or
Cisco VCS cluster) that hosts the relevant account.
Cisco VCS cluster) that hosts the relevant account.
Therefore, care must be taken in designing system topologies to ensure that caller ID can always be overwritten.
For example, if two users have their accounts on a VCS Control, but both are working from home on endpoints that are
registered to a VCS Expressway (which has a traversal zone to the VCS Control):
registered to a VCS Expressway (which has a traversal zone to the VCS Control):
■
If one user calls the other user's FindMe ID, their caller ID will be overwritten by their FindMe ID, as the call
signaling will go via the VCS Control (where the user account is hosted).
signaling will go via the VCS Control (where the user account is hosted).
■
If one caller calls the other user's endpoint URI directly, the call signaling will go through the VCS Expressway,
but not the VCS Control. In this scenario the caller ID will not be overwritten with the FindMe ID as the signaling
would not pass through the VCS Control. (It is recommended that users call FindMe IDs rather than individual
device URIs.)
but not the VCS Control. In this scenario the caller ID will not be overwritten with the FindMe ID as the signaling
would not pass through the VCS Control. (It is recommended that users call FindMe IDs rather than individual
device URIs.)
FindMe and Presence
The Cisco VCS aggregates presence for each of the devices associated with a user's current active FindMe location.
However, it can only do this for devices whose presence is managed by a Presence Server that resides on the same
Cisco VCS (or Cisco VCS cluster) that hosts the relevant FindMe account.
However, it can only do this for devices whose presence is managed by a Presence Server that resides on the same
Cisco VCS (or Cisco VCS cluster) that hosts the relevant FindMe account.
Therefore, we recommend that you enable the Presence Server on the same Cisco VCS (or Cisco VCS cluster) that you
use to manage your FindMe accounts.
use to manage your FindMe accounts.
Individual and Group FindMe Types
Every FindMe profile is configured as either
Individual or Group.
Individual
Individual mode assumes that the individual can only take a call on one device at a time.
■
If any device in the current active location is busy, a call to this FindMe ID will be immediately forwarded to the on-
busy devices.
busy devices.
■
If no devices (in the current active location) were busy, after the specified ring duration the call will route to the on-
no-answer devices.
no-answer devices.
Group
Group mode assumes that more than one person can take calls to this FindMe.
■
If any device in the current active location is not busy, the non-busy devices will ring. The call is immediately
forwarded to the on-busy devices only if all devices in the current active location are busy.
forwarded to the on-busy devices only if all devices in the current active location are busy.
■
If any device in the current active location is not busy, after the specified ring duration FindMe will route the call to
the:
the:
—
on-busy devices if any current active location device was busy
—
on-no-answer devices if none of the current active location device were busy
Characters Allowed in SIP URIs
The following character set is allowed in SIP URIs (further details may be found in RFC 3261):
a-z / A-Z / 0-9 / "-" / "_" / "." / "!" / "~" / "*" / "'"/ "(" / ")" "&" / "=" / "+" / "$" / "," / ";" / "?" / "/"
81
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide