Lesson 3

Configuring Cisco Unified

Presence-Enabled Speed
Dials and Lists
Overview
Today, users are mobile, working from homes, in the office, in airport lounges, or while
traveling. In order to be able to communicate with others efficiently, it is helpful to know about
their current availability. Can they be reached by phone, by instant messaging, or e-mail, and
are they ready to communicate at this point in time? Cisco Unified Communications solutions
offer presence information about the reachability and status of a user.
Cisco Unified Communications Manager Presence, an integrated part of Cisco Unified
Communications Manager, allows IP phone users to monitor the status of directory numbers.
This lesson describes how Cisco Unified Communications Manager Presence works and how it
is configured.

Objectives
Upon completing this lesson, you will be able to describe and configure Cisco Unified
Presence-enabled speed dials and lists. This ability includes being able to meet these objectives:
Introduce the Cisco Unified Presence feature, which is part of Cisco Unified
Communications Manager
Describe how Cisco Unified Communications Manager natively supports Cisco Unified
Presence
Describe how to configure Cisco Unified Presence in Cisco Unified Communications
Manager
Describe how access control for Cisco Unified Presence subscription is supported by Cisco
Unified Communications Manager
Describe how to configure Cisco Unified Presence access control in Cisco Unified
Communications Manager
Cisco Unified Presence Essentials
This topic describes the essentials of Cisco Unified Communications Manager Presence.

Cisco Unified Presence Solutions

Multiple options to integrate presence:

Cisco Unified Communications Manager Presence
Speed-dial presence
Call history presence
Presence policy
Cisco Unified Presence Server
User status information
Cisco IP Phone Messenger application
Cisco Unified Personal Communicator
Third-Party Presence Server Integration

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-4

Cisco Unified Communications includes multiple options to integrate presence information.

Cisco Unified Communications Manager Presence, a native presence feature of Cisco Unified
Communications Manager, includes the following capabilities:
Presence-enabled speed dials: Speed-dial buttons that indicate the status of the target of
the speed dial.
Presence-enabled call and directory lists: Call lists and directory entries that indicate the
status of each list entry.
Presence policy: Tools allowing access control to presence information.
When you use Cisco Unified Presence, many features are added to those provided by the native
Cisco Unified Communications Manager Presence feature, including:
Standards-based session initiation protocol (SIP) and SIP for Instant Messaging and
Presence Leveraging Extensions (SIMPLE) network interface
User status information, not only device (line) status information
Instant messaging capabilities, including integration with third-party servers
Cisco Unified Personal Communicator: A client tool that integrates voice, video, and
instant messaging communications

Note This lesson covers Cisco Unified Communications Manager Presence only.

5-122 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Cisco Unified Communications Manager
Presence Characteristics
This subtopic describes the characteristics of Cisco Unified Communications Manager
Presence.

Cisco Unified Communications Manager

Presence Characteristics

Natively supported by Cisco Unified Communications Manager

Allows an interested party (a watcher) to monitor the real-time
status of a directory number (a presence entity)
Watcher subscribes to status information of the presence entity
Watcher can show the status of a presence entity using:
Presence-enabled speed dials
Presence-enabled lists (call and directory lists)
Three possible states of watched directory number:
Entity is unregistered
Entity is registeredon-hook
Entity is registeredoff-hook

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-5

Cisco Unified Communications Manager Presence is natively supported by Cisco Unified

Communications Manager, and no extra products or servers are required. It allows an interested
party, the watcher or subscriber, to monitor the real-time status of a directory number, a
presence entity, or subscribee.
A watcher subscribes to the status information of one or more presence entities. The status
information of a presence entity can be viewed using presence-enabled speed dials or presence-
enabled listscall lists such as placed, received, or missed calls and public directory lists.
The status can be one of the following:
Unknown: This status is shown when the watched device is unregistered.
On-hook
Off-hook

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-123
Cisco Unified Communications Manager Presence Operation
The figure shows an example of the operation of Cisco Unified Presence.

In the example, Johns phone subscribes to the status of Bryans phone (more precisely, to the
status of Bryans directory number). Johns phone is doing that because the Cisco Unified
Communications Manager Administrator configured a presence-enabled speed dial for Bryans
extension, or because John is browsing through a call list that includes Bryans directory
number. Johns phone also subscribes to the status of the other entries of the call list; this is
done automatically as soon as the call list is viewed.
Cisco Unified Communications Manager Presence will now keep Johns phone updated about
the status of the subscribed presence entity, which means, if Bryan goes off-hook while John is
browsing the call list that includes Bryans directory number, the status information is
displayed.
If John had a presence-enabled speed dial for Bryans directory number, the speed dial would
permanently display the current status of Bryans directory number.

5-124 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Cisco Unified Presence Support in Cisco Unified
Communications Manager
This topic describes how Cisco Unified Communications Manager supports presence with the
Cisco Unified Communications Manager Presence feature.

Cisco Unified Communications Manager

Support for Presence

Directory numbers (lines) of Cisco IP phones can be watched

By Cisco IP phones
By SIP devices through a SIP trunk
Directory numbers (lines) of Cisco IP phones, and endpoints that
are reached via SIP trunks, can be watched by the following:
Cisco IP phones
SIP devices through a SIP trunk

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-8

Cisco Unified Communications Manager Presence allows directory numbers to be watched by

Cisco IP phones and by SIP devices through a SIP trunk. Endpoints that can be reached through
a SIP trunk can be watched by Cisco IP phones and by SIP devices through other trunks. Both
Cisco IP phones running Skinny Client Control Protocol (SCCP) and Cisco IP phones running
SIP can watch presence entities and can be watched. If presence subscriptions are sent over a
SIP trunk, Cisco Unified Communications Manager takes care about protocol conversion
between SCCP and SIP. If only IP phones that are registered within the Cisco Unified
Communications Manager cluster are involved, there is no need for endpoint-to-endpoint
communication because Cisco Unified Communications Manager is aware of the state of all
registered IP phones.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-125
Watching Presence Status on Cisco IP Phones
This subtopic describes how presence information can be watched on a Cisco IP phone.

Watching Presence Status on Cisco IP

Phones

Presence status can be seen on speed-dial buttons, call

lists and directories.

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-9

Cisco IP phones can display status information (unknown, on-hook, or off-hook) of presence
entities by presence-enabled speed dials or call and directory list entries.
Presence-enabled speed dials show a symbol in the screen of the IP phone, located at the
appropriate speed dial button. Some phone models (type B Cisco Unified IP phones) have an
LED inside the speed dial button and indicate the status by red (off-hook) or green (on-hook)
lights.
When browsing through a directory or call list, each entry displays a symbol indicating its
current status.

5-126 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Cisco IP Phones That Support Viewing Presence Status
The table shows which type of status information is supported on Cisco IP phone models.

Cisco IP Phones That Support Viewing

Presence Status

Cisco
Presence-Enabled Speed Presence-Enabled Call
Unified IP Phone
Dials Support and Directory Lists Support
Models
794[125], 796[125],
797[015] Yes Yes
SIP and SCCP
7914, 7940, 7960
Yes No
SCCP
7914, 7940, 7960
No No
SIP

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-10

As shown in the table, Cisco Unified IP Phone 7914, 7940, and 7960 do not support presence at
all when running SIP; when running SCCP, they support only presence-enabled speed dials but
no presence-enabled call and directory lists. Type B Cisco Unified IP Phone 794[125],
796[125], and 797[015] support both presence-enabled call and directory lists and presence-
enabled speed dials, regardless of the protocol (SIP or SCCP).

Note Cisco IP Communicator also supports both presence-enabled speed dials and presence-
enabled call and directory lists.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-127
Cisco Unified Presence Configuration
This topic describes how to configure Cisco Unified Communications Manager Presence.

Cisco Unified Communications Manager

Presence Configuration Procedure

To enable presence-enabled speed dials:

1. Customize phone button templates to include presence-enabled
speed-dial buttons
2. Apply phone button templates to phones
3. Configure presence-enabled speed-dial buttons
4. Apply subscribe CSS to phones
To enable presence-enabled call lists:
Enable the BLF For Call Lists enterprise parameter
To allow presence subscriptions through SIP trunks:
Enable Cisco Unified Communications Manager Presence on
SIP trunks

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-12

The Cisco Unified Communications Manager Presence configuration procedure includes the
following three parts:
Enabling presence-enabled speed dials:
Step 1 Customize phone button templates to include presence-enabled speed-dial buttons.
Step 2 Apply phone button templates to phones.
Step 3 Configure presence-enabled speed-dial buttons.
Step 4 Apply subscribe Calling Search Space (CSS) to phones.

Caution If partitions are used, so-called subscribe CSSs are required for subscriptions to succeed
when trying to watch an entity that has a partition assigned.

Enabling presence-enabled call lists: Enable the BLF For Call Lists enterprise parameter.

Note In Cisco Unified Communications Manager configuration, presence-enabled call lists are
referred to as busy lamp field (BLF) call lists.

Allowing presence subscriptions through SIP trunks: Enable Cisco Unified

Communications Manager Presence on SIP trunks.

Note The first two features are independent of each other. The third feature is an optional add-on
to both presence-enabled speed dials and presence-enabled call lists (if used).

5-128 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Step 1: Customizing Phone Button Templates
This subtopic shows how to implement presence-enabled speed dials. The first step is the
configuration of a phone button template as shown in the figure.

Step 1: Customizing Phone Button

Templates
Device > Device Settings > Phone Button Template

Configure presence-enabled
speed-dial buttons in phone button
template

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-13

The first step for implementing presence-enabled speed dials is to configure a phone button
template that includes presence-enabled speed dials. To configure a phone button template, go
to Device > Device Settings > Phone Button Template and either add a new template or copy
one of the default phone button templates and save it with a new name. Configure the phone
button template with the desired number of presence-enabled speed dials.

Note In Cisco Unified Communications Manager Administration, presence-enabled speed dials

are called speed-dial BLF.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-129
Step 2: Applying the Phone Button Template to IP Phones
The figure shows how a phone button template is applied to an IP phone.

Step 2: Applying the Phone Button

Template to IP Phones
Device > Phone

Assign phone button

template to phone

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-14

Assign the previously configured phone button template to the IP phone that should be
configured for presence-enabled speed dials. Go to the phone configuration page and select the
appropriate template from the Phone Button Template drop-down list.

5-130 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Step 3: Configuring Cisco Unified Presence-Enabled Speed-
Dial Buttons
The figure shows the configuration of a presence-enabled speeddial button.

Step 3: Configuring Presence-Enabled

Speed Dial Buttons
Device > Phone

At the phone configuration

page, click links to add a
presence-enabled speed dial.

Enter presence-enabled speed-

dial configuration: presence
entity to watch and label to be
displayed on phone

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-15

After applying the new phone button template, the presence-enabled speed dials are displayed
in the Association Information area of the phone configuration window. The phone now has the
capability to use buttons for presence-enabled speed dials, but in order to use the buttons that
way, the buttons have to be configured appropriately. To configure presence-enabled speed
dials, click on the Add a new BLF-SD link. The Busy Lamp Field Speeddial Configuration
window appears. In this window configure the target (the presence entity to be watched) of the
presence-enabled speed-dial button and a label which will be displayed on the phone screen
next to the corresponding button.

Note In Cisco Unified Communications Manager configuration, presence-enabled speed dials are
referred to as BLF speed dials.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-131
Enabling Cisco Unified Presence-Enabled Call Lists
This subtopic shows how to enable presence-enabled call lists.

Enabling Presence-Enabled
Call Lists
System > Enterprise Parameters

Enable presence-
enabled call lists

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-16

If call lists should also provide presence information, the appropriate enterprise parameter has
to be enabled, as shown in the figure. After changing the BLF For Call Lists enterprise
parameter to Enabled, all phones that support presence-enabled call lists must be reset in order
for the change to become effective

Note In Cisco Unified Communications Manager configuration, presence-enabled call lists are
referred to as BLF call lists.

5-132 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Enabling Cisco Unified Presence on SIP Trunks
This subtopic shows how to allow presence subscriptions over SIP trunks.

Enabling Presence on SIP Trunks

System > Security Profile > SIP Trunk Security Profile
Assign SIP Trunk
Security Profile to
SIP Trunk

Device > Trunk

Configure SIP Trunk

Security Profile for
presence

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-17

If presence subscriptions are possible over a SIP trunk, presence needs to be enabled on the SIP
trunk. Presence is not enabled directly at the SIP trunk but via a SIP Trunk Security Profile.
Therefore configure a SIP trunk security profile from System > Security Profile > SIP Trunk
Security Profile, where the Accept Presence Subscriptions and the Accept Unsolicited
Notification check boxes are activated. Then apply the SIP trunk security profile to the SIP
trunk, as shown in the figure.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-133
Cisco Unified Presence Policies
This topic describes how to implement Cisco Unified Presence policies in order to control
which presence entities can be monitored by which watcher.

Limiting Presence Visibility

Cisco Unified Communications Manager Presence offers

different ways to limit visibility of presence information:
Presence-enabled speed dials
Are statically configured by Cisco Unified Communications
Manager Administrator (cannot be configured by users)
Subscribe Calling Search Space and (standard) partitions
Presence-enabled call and directory lists
Subscribe Calling Search Space and (standard) partitions
Presence groups

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-19

Cisco Unified Communications Manager Presence can limit visibility of presence information
in the following ways:
Presence-enabled speed dials are configured statically by the Cisco Unified
Communications Manager administrator and cannot be configured or modified by a user. In
this way, the administrator has control over the monitored presence entities for each
individual watcher. However, partitions and subscribe calling search spaces also apply to
presence-enabled speed dials.
Access control for presence-enabled call and directory lists can be provided by partitions
and subscribe calling search spaces and by presence groups. Each of the two methods can
be used independently of each other. If both are used, both have to permit a subscription for
successful watching of the presence entity status.

5-134 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Subscribe CSS and Partitions
This subtopic describes how to use subscribe CSS and partitions to implement presence
policies.

Subscribe CSS and Partitions

Separate CSSsare applied for calling privileges and presence: the

(standard) CSS for calling privileges and a subscribe CSS for
presence.
A subscribe CSS is applied to a watcher: a SIP trunk, a phone, or
an end user.
The subscribe CSS determines which presence entities a watcher
is allowed to monitor.
Similar to with traditional CSSs, a presence entity can only be
watched if the watcher has the presence entitys partition in its
subscribe calling search space.
The (standard) partition that is applied to a line or a route pattern
referring to a trunk is used for both calling privileges and
presence.
If no partition is applied to a line or route pattern, it is available to
all watchers.

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-20

Calling privileges are implemented using partitions and CSSs. Presence policies are
implemented by using the same partitions (applied to directory numbers and route patterns) that
are used for calling privilege configuration; the CSSs, however, are separated. Rather than the
(standard) CSS configured on IP phones, lines, and trunks, dedicated subscribe CSSs are used.
A subscribe CSS is applied to a watcher. This can be a SIP trunk (assuming that subscriptions
have been enabled in general on the trunk), a phone, or an end user. Subscribe CSSs do not use
the concept of a device CSS and a line CSS. Watching a presence entity is always a global
function of the IP phone, not of a certain line. Therefore, subscribe CSSs are only applied to IP
phones and not to lines. When a subscribe CSS is applied to an end user, this subscribe CSS is
used in case of extension mobility or if the end user is associated with a device.
Similar to standard CSSs, the subscribe CSS determines which presence entities a watcher is
allowed to monitor. A subscription is only permitted if the watcher has the partition of the
desired presence entity in its subscribe CSS.
The (standard) partition which is applied to a line or a route pattern that refers to a SIP trunk is
used for both calling privileges and presence policies. If no partition is applied to the desired
presence entity, the presence entity is available to all watchers.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-135
Subscribe CSS and Partition Considerations
This subtopic describes what needs to be considered when implementing calling privileges or
presence policies using partitions.

Subscribe CSS and Partition

Considerations

Presence policies and calling privileges share some configuration

settings:
Partitions on lines and route patterns
Implementing presence policies impacts calling privileges and
vice versa
Any changes to partition configuration affects calling privileges
(standard CSSs) and presence policies (subscribe CSSs)
Design and implementation of calling privileges and presence
policies have to be performed together!

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-21

Presence policies and calling privileges share a configuration element. The partitions that are
applied to lines or route patterns apply to both. Therefore implementing presence policies
impacts existing calling privileges, and vice versa.
Whenever partition configuration is changed because of the implementation of one of the two
features (calling privileges and presence policies), the other feature is affected. Therefore,
calling privileges and presence policies have to be designed and implemented together.

5-136 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Subscribe CSS and Partition Considerations: Sample Scenario
This subtopic provides a sample scenario illustrating the dependencies of calling privilege
implementation and presence policies implementation.

Subscribe CSS and Partition

Considerations Sample Scenario

Baseline configuration does not include any partitions (no calling

privileges and no presence policies are in place).
If partitions and (standard) CSSs are implemented for calling
privileges, subscriptions will fail:
Lines and route patterns now have partitions.
Devices (phones and trunks) do not have subscribe CSSs
If partitions and subscribe calling search spaces are implemented
for presence policies, calls will fail:
Lines and route patterns now have partitions.
Devices (phones, lines, and trunks) do not have CSSs.

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-22

In the example scenario, the baseline configuration does not include any partitions and calling
search spaces. Neither calling privileges nor presence policies are in place. All directory
numbers and route patterns are in the null partition and can be accessed by all devices. All
devices can place calls to all destinations. Presence subscriptions are also possible to all
supported targets such as directory numbers and devices reached through SIP trunks.
If calling privileges (partitions and CSS) are implemented without considering presence (also
adding subscribe CSSs), presence subscriptions will not work anymore for all presence entities
that have been put into partitions when implementing calling privileges.

Note The recommendation when implementing partitions and CSS is not to leave any targets in
the null partition, but to assign a partition to all call destinations. Therefore, in the above
scenario, usually there will be no targets left where subscriptions would still work.

Or, if the baseline configuration is modified in the way that presence policies (partitions and
subscribe CSSs) are implemented, without considering calling privileges (also adding standard
CSSs), all calls will fail. This will happen because lines and route patterns now have partitions
but calling devices do not have CSSs that would allow access to some partitions. The devices
only have subscribe CSSs, so only presence information can be obtained, but no calls can be
placed.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-137
 Presence Policy Example: Subscribe CSS
The figure illustrates a presence policy example based on partitions and subscribe CSSs.

The configuration consists of three CSSs: C-1 contains partitions P-1 and P-2. C-2 contains
partitions P-1, P-2, and P-3. C-3 contains partition P-1 only.
Phone1 has partition P-1 applied to its line, which is configured with directory number 1001.
CSS C-1 is assigned to Phone1.
Phone2 has partition P-2 applied to its line, which is configured with directory number 1002.
CSS C-2 is assigned to Phone2.
A SIP phone with number 1003 can be reached through a SIP trunk. The corresponding route
pattern 8.1003 is in partition P-3. CSS C-3 is assigned to the SIP trunk.
The effective permissions for presence subscriptions are as follows:
Phone1 is allowed to watch the status of 1002 but not of 1003. Phone2 is allowed to watch both
other phones. Phone 3 is allowed to subscribe to presence information of 1001 but not of 1002.

Note The (CSS) in the figure refers to the standard CSS used for the implementation of calling
privileges. They are not relevant for the discussion of presence subscription permissions but
because they also depend on the configured partitions, they are added to illustrate that they
have to be considered in the overall configuration.

Note Partitions and subscribe CSSs apply to both presence features: presence-enabled speed
dials and presence-enabled call lists.

5-138 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Presence Groups
Presence policies can be implemented by partitions and subscribe CSSs, or by presence groups.
This subtopic describes how presence policies are implemented using presence groups.

Presence Groups

Presence groups can be used to implement presence

policies:
Watchers and presence entities are put into presence groups.
Subscriptions are permitted within presence groups.
Subscriptions can be allowed or denied between presence groups.
Permission can be configured independently for each direction
IP phones have separate presence groups.
Line presence group (presence entity)
Phone presence group (watcher)
SIP trunks have only one presence group.
used for both watcher and presence entity
Presence groups only apply to presence-enabled call lists they
do not apply to presence-enabled speed dials
2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-24

When implementing presence policies, watchers and presence entities are put into presence
groups. Subscriptions can be allowed or denied at an intergroup level; within a presence group,
subscriptions are always permitted (unless denied by partitions and subscribe CSSs).
IP phones are configured with two or more presence groups. One presence group is applied to
the device (in the role as a watcher), and each line can be configured with a presence group in
its role as a presence entity.
On SIP trunks, only one presence group is configured, which is used in both roles, as a watcher
and as a presence entity. You cannot assign a presence group to a route pattern.
Like subscribe CSSs, presence groups can also be assigned to end users. They are used when
the end users are logging into the phone using extension mobility or when the users are
associated with a device.

Note Presence groups only apply to presence-enabled call lists they do not apply to presence-
enabled speed dials.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-139
Presence Policy Example: Presence Groups
The figure illustrates a presence policy example based on presence groups.

The configuration uses three presence groups: G-1, G-2, and G-3. Inter-presence group
subscriptions are permitted from G-2 to G-3 and G-3 to G-1. All other inter-presence group
subscriptions are denied.
Phone1 has presence group G-1 applied to its line, which is configured with directory number
1001. Presence group G-2 is assigned to Phone1.
Phone2 has presence group G-2 applied to its line, which is configured with directory number
1002. Presence group G-2 is also assigned to Phone2.
A SIP phone with number 1003 can be reached through a SIP trunk. Presence group G-3 is
assigned to the SIP trunk.
The effective permissions for presence subscriptions are as follows:
Phone1 is allowed to watch the status of 1002 and 1003. Phone2 is allowed to watch 1003 but
not 1001. Phone 3 is allowed to subscribe to presence information of 1001 but not of 1002.

Note Presence groups apply only to presence-enabled call lists. Presence-enabled speed dials
are not affected by presence groups.

5-140 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Interaction of Presence Groups, Partitions, and Subscribe
CSSs
This subtopic describes the interaction of presence groups, subscribe CSSs, and partitions.

Interaction of Presence Groups and

Partitions and Subscribe CSSs

Presence groups, partitions, and subscribe CSSs can be combined.

Both have to permit subscription for successful watching
Provides 2 levels of hierarchy useful in larger deployments
Example:
Requirements:
No subscriptions are allowed across departments.
Within a department, managers can only be watched by their
assistants.
Solution:
Use one presence group per department.
Deny inter-presence group subscriptions.
Include manager partition only in the subscribe CSS of their
assistant.

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-26

Each feature can be used standalone or they can be combined. If both uses are implemented,
both mechanisms have to permit the subscription in order to allow successful watching.
Combining both presence policy mechanisms provides two hierarchy levels, which is useful in
larger deployments or complex scenarios.
The following example illustrates how subscribe CSSs and partitions and presence groups can
be effectively combined to fulfill the given requirements:
Requirements: No subscriptions are allowed between different
departments. Within a department, managers can only be watched
by their assistants. All other subscriptions within a
department should be possible.
Solution: One presence group is configured per department.
Inter-presence group subscriptions are denied by setting the
default inter-presence group policy accordingly. One partition
is configured per manager. Each of these partitions is only
listed in the subscribe CSS of the respective manager
assistant.
In the example, presence groups are used for the first level of presence policies (at department
level) and subscribe CSSs and partitions are used for additional access control within a
department (or presence group).

Note Presence groups only apply to presence-enabled call lists. They do not apply to presence-
enabled speed dials.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-141
Cisco Unified Presence Policy Configuration
This topic describes how to implement presence policies in Cisco Unified Communications
Manager.

Unified CM Presence Policies

Configuration Procedure

To implement presence policies based on partitions and

CSSs:
1. Configure partitions and CSSs
2. Assign partitions to lines and route patterns
3. Assign subscribe CSSs to phones and trunks
To implement presence policies based on presence
groups:
1. Configure presence groups
2. Set the default inter-presence group policy
3. Assign presence groups to lines, phones, and SIP trunks

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-28

The Cisco Unified Communications Manager presence policy configuration procedure includes
the following parts:
Implement presence policies based on partitions and CSSs:
Step 1 Configure partitions and CSSs
Step 2 Assign partitions to lines and route patterns
Step 3 Assign subscribe CSSs to phones and trunks
Implement presence policies based on presence groups:
Step 1 Configure presence groups
Step 2 Set the default inter-presence group policy
Step 3 Assign presence groups to lines, phones, and SIP trunks

Note These two procedures can be independently configured. Presence groups only apply to
presence-enabled call lists and subscribe CSSs. Partitions apply to presence-enabled call
lists and presence-enabled speed dials.

5-142 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Implementing Presence Policies Based on Partitions and CSS:
Step 3 Assigning Subscribe CSSs to Phones and SIP Trunks
The first two steps of implementing presence policies based on partitions and subscribe CSSs
are not shown because they have been covered in earlier lessons of this course.

Step 3: Assigning Subscribe Calling Search

Spaces to Phones and SIP Trunks

Apply Subscribe Device > Phone

CSS to trunks and
phones

Device > Trunk

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-29

The figure shows how CSSs are assigned to IP phones and SIP trunks as SUBSCRIBE Calling
Search Spaces.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-143
Implementing Presence Policies Based on Presence Groups:
Step 1 Configuring Presence Groups
This subtopic shows how to implement presence policies based on presence groups. Note that
presence groups only apply to presence-enabled call lists and are ignored by presence-enabled
speed dials. The first step when implementing presence groups is to add and configure presence
groups, as shown in the figure.

Step 1: Configuring Presence Groups

Enter Name and
System > Presence Group Description for
presence group

Individually
configured
permission towards
listed presence
group

Permission to
unlisted presence
groups is determined
by service parameter

For
Forindividual
individualconfiguration towards
configuration, another presence
select presence group andgroup,
set
select destination
permission presence group
for subscriptions andselected
towards select type of permission
presence group

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-30

Presence groups can be added and configured from System > Presence Group. One presence
group exists by default and cannot be deleted; it is called Standard Presence group. All phones,
lines, and SIP trunks, by default, are members of the Standard Presence group. The Standard
Presence group can be modified in the way that the permissions to other groups can be set, but
it cannot be deleted.
When adding a new presence group, enter a Name and Description and configure the
permission for subscriptions toward other presence groups. The permission does not have to be
entered toward all other presence groups; the permission for subscriptions towards
unconfigured presence groups will be determined by system default, which is configurable as a
Cisco CallManager service parameter.

Note Subscription Permissions are configured in a unidirectional manner between pairs of

presence groups. It is possible to permit subscriptions from one group to another but to deny
subscriptions in the opposite direction.

5-144 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Step 2: Setting the Default Inter-Presence Group Policy
The figure shows the configuration of the default inter-presence group policy.

Step 2: Setting the Default Inter-Presence

Group Policy

System > Service Parameter (Cisco CallManager)

Set the Default Inter-

Presence Group
Subscription

The Default Inter-Presence Group Subscription specifies the system

default for presence subscriptions towards presence groups for
which no explicit permission has been configured.

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-31

The Default Inter-Presence Group Subscription service parameter specifies the system default
for presence subscriptions. The system default is applied for subscriptions toward presence
groups for which no explicit permission has been set in the configuration of the presence group
from which the subscription request has been sourced.
The Default Inter-Presence Group Subscription parameter is a service parameter of the Cisco
CallManager service and is therefore configured from System > Service Parameter.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-145
Step 3a: Assigning Presence Groups to Lines and Phones
The figure shows how a presence group is applied to lines and phones.

Step 3a: Assigning Presence Groups to

Lines and Phones
Device > Phone

Assign presence
group to phone (in
subscriber role)

Call Routing > Directory Number

Assign presence
group to directory
number (in presence
entity role)

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-32

Presence groups allow the implementation of presence policies by checking the permission for
subscriptions going from one presence group to another presence group. This means that each
subscriber and each presence entity must be in a presence group.
IP phones (and their lines) act as both: the IP phone itself generates subscriptions (when using
presence-enabled speed dials or presence-enabled call lists) and their directory numbers can be
watched by other subscribers. Therefore, presence groups are applied to both: the phone (in the
role as a subscriber) and all phone lines (in the role as a presence entity).

Note By default, all phones and all lines are in the Standard Presence group.

Note Remember that presence groups apply to presence-enabled call lists only. Therefore,
subscriptions caused by presence-enabled speed dials are ignoring all presence group-
based policies.

5-146 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.
Step 3b: Assigning a Presence Group to a SIP Trunk
The figure shows how a presence group is applied to a SIP trunk.

Step 3b: Assigning a Presence Group to

a SIP Trunk
Device > Trunk

Assign presence
group to SIP trunk

Same presence
group is used in
subscriber and
presence entity role

The presence group configured on a SIP trunk applies to both

subscriptions being sent out and being received on the trunk.

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-33

Cisco Unified Communications Manager can send subscribe messages out on a SIP trunk
(when watching a presence entity located on the other side of the trunk) and can receive
subscriptions on a SIP trunk (when a local directory number is watched over the SIP trunk by a
subscriber located on the other side of the trunk). The trunk, therefore, can act in both
subscriber and presence entity roles. However, on a SIP trunk, only one presence group can be
configured and therefore this single presence group applies to sent subscriptions as well as to
received subscriptions.

2008 Cisco Systems, Inc. Implementation of Media Resources, Features, and Applications 5-147
Summary
This topic summarizes the key points that were discussed in this lesson.

Summary

Cisco Unified Communications Manager Presence allows lines or

endpoints reachable through SIP trunks to be monitored for their
status (on-hook versus off-hook).
Most IP phones support presence-enabled speed dials; type B
Cisco IP phones using SIP also support presence-enabled call
and directory lists.
Cisco Unified Communications Manager Presence configuration
includes implementing presence-enabled speed dials and
enabling presence-enabled call and directory lists.
Cisco Unified Presence policies can be applied for controlling
presence subscriptions.
Cisco Unified Communications Manager Presence policy
configuration includes implementing partitions and subscribe
calling spaces and presence groups.

2008 Cisco Systems, Inc. All rights reserved. CIPT1 v6.05-34

References
For additional information, refer to these resources:
Cisco Unified Communications Manager Features and Services Guide, Release 6.0(1)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmfeat/fsgd.pdf
Cisco Unified Communications Manager Administration Guide, Release 6.0(1)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmcfg/bccm.pdf
Cisco Unified Communications SRND Based on Cisco Unified Communications
Manager 6.x
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design
_guide_book09186a008085eb0d.html

5-148 Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0 2008 Cisco Systems, Inc.