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

Field Description
Template The alias that the VCS tells
the endpoint to dial to create a
Multiway conference on the
MCU.
Number The first and last numbers in
range the range that replaces %% in
start / the template used to generate
end a conference alias.
Note that:
You must use a different Template on each VCS in your network that has the Conference Factory
n
application enabled. If your VCS is part of a cluster, the Template must be different for each peer in
the cluster.
The alias generated by the Template must be a fully-qualified SIP alias and must route to the MCU.
n
The MCU must be configured to process this alias. No other special configuration is required on the
MCU in order to support the Conference Factory application.
SIP mode must be set to On
n
Conference Factory application to function. If you want to be able to initiate calls to the Conference
Factory from H.323 endpoints, you must also set H.323 mode to On
Protocols > H.323), and ensure that H.323 <-> SIP interworking mode is set to Registered only
or On (VCS configuration > Protocols >
Refer to the Multiway deployment guide [25] for full details on how to configure individual components
of your network (endpoints, MCUs and VCSs) in order to use Multiway in your deployment.

About Presence

Presence is the ability of endpoints to provide information to other users about their current status -
such as whether they are offline, online, or in a call. Any entity which provides presence information, or
about whom presence information can be requested, is known as a presentity. Presentities publish
information about their own presence status, and also subscribe to the information being published by
other presentities and FindMe users.
Endpoints that support presence, such as Movi™ v2.0 (or later) clients, can publish their own status
information. The VCS can also provide basic presence information on behalf of endpoints that do not
support presence, including H.323 endpoints, as long as they have registered with an alias in the form
of a URI.
If FindMe is enabled, the VCS can also provide presence information about FindMe users by
aggregating the information provided by each presentity configured for that FindMe user.
The Presence application on the VCS supports the SIP-based SIMPLE standard and is made up of
two separate services. These are the
services can be enabled and disabled
Cisco VCS Administrator Guide (X6.1)
Usage tips
To ensure that each conference has a different alias,
you should use %% as a part of the template. The %%
will be replaced by a unique number each time the VCS
receives a new conference request.
For example, your Template could be
563%%@example.com with a range of 10 - 999. The
first conference will use the alias
563010@example.com, the next conference will use
563011@example.com and so on up to
563999@example.com, after which it will loop round
and start again at 563010@example.com. (Note that
the %% represents a fixed number of digits based upon
the upper range limit.)
(VCS configuration > Protocols > SIP >
Interworking).
Presence Server and the
separately.
Configuration) for the
(VCS configuration >
Presence User Agent (PUA). These
Applications
Page 182 of 401