Cisco Cisco TelePresence Video Communication Server Expressway
Therefore, care must be taken in designing system topologies to ensure that caller ID can always be
overwritten.
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):
endpoints that are registered to a VCS Expressway (which has a traversal zone to the VCS Control):
n
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).
n
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.)
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.)
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.
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.
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.
cluster) that you 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.
n
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.
the on-busy devices.
n
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.
the on-no-answer devices.
Group
Group mode assumes that more than one person can take calls to this FindMe.
n
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.
immediately forwarded to the on-busy devices only if all devices in the current active location are busy.
n
If any device in the current active location is not busy, after the specified ring duration FindMe will route the
call to the:
call to the:
l
on-busy devices if any current active location device was busy
l
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 / "-" / "_" / "." / "!" / "~" / "*" / "'"/ "(" / ")" "&" / "=" / "+" / "$" / "," / ";" / "?" / "/"
If other characters are needed they must be “escaped” using "%" followed by a pair of hexadecimal digits that
represents the ASCII value for the required character.
represents the ASCII value for the required character.
Cisco TelePresence FindMe (VCS Express) Deployment Guide (X8.2)
Page 12 of 18
Additional information