Configuring Presence - Cisco TelePresence Video Communication Server Administrator's Manual

online (registered but not in a call)
n
in call (registered and currently in a call)
n
Aggregation of presence information
When enabled, the PUA generates presence information for all endpoints registered to the VCS,
including those which already support presence. However, endpoints that support presence may
provide other, more detailed status, for example away or do not disturb. For this reason, information
provided by the PUA is used by the Presentity Manager as follows:
Where presence information is provided by the PUA and one other source, the non-PUA presence
n
information will always be used in preference to the PUA presence information. This is because it is
assumed that the other source of information is the presentity itself, and this information is more
accurate.
Where presence information is provided by the PUA and two or more other sources, the Presence
n
Server will aggregate the presence information from all presentities to give the "highest interest"
information, e.g. online rather than offline, and in call rather than away.
If no information is being published about an endpoint, either by the endpoint itself or by the PUA,
n
the endpoint's status will be offline. If the PUA is enabled, the offline status indicates that the
endpoint is not currently registered.
FindMe presence
When the Presentity Manager receives a request for information about the presences of a FindMe
alias, it looks up the presence information for each endpoint that makes up that FindMe alias. It then
aggregates this information as follows:
If the FindMe alias is set to Individual mode, if any one of the endpoints making up that FindMe is in
n
a call the FindMe presentity's status will be reported as in call.
If the FindMe alias is set to Group mode, if any one of the endpoints is online (i.e. not in call or
n
offline) then the FindMe presentity's status will be reported as online.
Registration refresh period
The PUA will update and publish presence information on receipt of:
a registration request (for new registrations)
n
a registration refresh (for existing registrations)
n
a deregistration request
n
call setup and cleardown information
n
For non-traversal H.323 registrations the default registration refresh period is 30 minutes. This means
that when the PUA is enabled on a VCS with existing registrations, it may take up to 30 minutes
before an H.323 registration refresh is received and available presence information is published for that
endpoint.
It also means that if an H.323 endpoint becomes unavailable without sending a deregistration
message, it may take up to 30 minutes for its status to change to offline. To ensure more timely
publication of presence information for H.323 endpoints, you should decrease the H.323 registration
refresh period (using VCS configuration > Protocols > H.323 > Gatekeeper > Time to
The default registration refresh period for SIP is 60 seconds, so it will take no more than a minute for
the PUA to publish updated presence information on behalf of any SIP endpoints.

Configuring Presence

The Presence page (Applications >
services on the VCS.
Cisco VCS Administrator Guide (X6.1)
Presence) allows you to enable and configure Presence
Applications
live).
Page 184 of 401