• Presence Group do not apply to presence-enabled speed dials i.e. BLF
• Watcher subscribes to status information of the presence entity

• Watcher can show the status of a presence entity using:
  • Presence enabled speed dials (BLF)
  • Presence enabled lists (call and directory lists)
• Only the Type B phone will show colour speed dial button for presence status
  • Red - off-hook
  • Green - on-hook

• Three possible states
  • Entity is unregistered
  • Entity is registered - on-hook
  • Entity is registered - off-hook

• We can limit visibility of presence information
• Presence enabled speed dials
  • Can only be defined by Administrator
  • Subscribe CSS applied to watcher
  • We are reusing the partition for the line
  • Presence Group has no effect for BLF speed dial
• Presence enabled call and directory lists
  • Subscribe CSS applied to watcher
  • We are reusing the partition for the line
  • Presence Group
• If no partition is assigned to a line or route pattern, it is available to all watchers

• Watchers and presence entities are put into presence group
• Subscriptions are permitted within presence groups
• Subscriptions can be allowed or denied between groups
  • Permission can be configured independently for each direction
• IP Phones have separate presence groups
  • Line presence group (presence entity)
    • Like partition applied to line, restrict who can subscribe to the presence status of this line
    • The presence group assign at the watcher device level must be allowed to subscribe to presence group assigned on the line to monitor its presence status
  • Phone presence group (watcher)
    • Like CSS, dictate which lines the device can subscribe to
• SIP trunks have only one presence group
  • As you cannot assign presence group to a route pattern
  • used for both watcher and presence entity
  • For SIP trunk to Presence server
    • Best to leave it in its own presence group e.g. Standard Presence Group and allow subscription to/from all other group
• End user can be assigned a presence group
  • Used when they are login using extension mobility
  • And when they are associated with a device

• If CUPC is configured for a particular line, the presence subscription to that line will be determined solely by the presence group assigned to the SIP trunk to the presence server.
• E.g. If line 5002 with CUPs enabled belongs to HQ group and the Presence SIP trunk belongs to Standard Presence group
  • For another group e.g. BR1 to see the presence status of line 5002, it must be allowed to subscribe to the standard presence group
  • It is not necessary to be subscribed to the HQ presence group. In fact it will not work if BR1 is subscribed to only the HQ group
• I think by having CUPS and CUPC configured, the control of the presence subscription is passed to the presence server and taken off the device.

• Both Presence Group and CSS can be combined.
• Useful in larger deployment
• Example
  • No subscriptions are allowed across department
  • 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

• Under Device > Device Settings > Phone Button Template
• Add BLF Speed Dial

• Under Device > Phone
• Assign Phone Button Template

• Under Device > Phone
• Add number to watch

• To enable presence enabled call list (call and directory list)
• Under System > Enterprise Parameters
• BLF for Call List = Enabled (default is disabled)

• To enable presence on SIP trunk e.g. to a presence server

• Under System > Security Profile > SIP Trunk Security Profile
• Accept Presence subscription
• Allow unsolicited notification

• Configure partition and CSS

• Assign partition to lines and route patterns

• Assign subscribe CSS to phones and trunks

• Configure Presence Group
• Setup permission between existing group or leave it to the default defined under service parameter
• Presence Group Relationship
  • SUBSCRIBE TO relationship
  • Define what group this presence group can subscribe or not subscribe to

• Under System > Service Parameter (Cisco CallManager)
• Set the default inter-presence group policy
• Default is disallow

• Assign presence group to lines, phones and SIP trunks

Assign to Phones/Lines

• Under Device > Phone
  • set the watcher group
  • Define who you can watch
• Under Call Routing > Directory Number
  • set the presence entity group
  • Define who can watch you

Assign to SIP trunk

• Under Device > Trunk
• The presence group configured on SIP trunk applies to both subscriptions being sent out and being received on the trunk