Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1)
BLF Presence
Download this chapter
BLF PresenceBLF Presence
Download the complete book
Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1)Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) (PDF - 20 MB)
 Feedback

BLF Presence

This chapter provides information about the Busy Lamp Field (BLF) Presence feature which allows a user to monitor the real-time status of another user at a directory number or SIP URI.

Configure BLF Presence

The BLF Presence feature allows a user (watcher) to monitor the real-time status of another user at a directory number or SIP URI from the device of the watcher. A watcher can monitor the status of the user by using the following options:

  • BLF/SpeedDial buttons
  • Missed call, placed call, or received call lists in the directories window
  • Shared directories, such as the corporate directory

Tip

The following information assumes that the phones and SIP trunks exist in the Cisco Unified Communications Manager database. For information on how to add a phone or SIP trunk, see the Cisco Unified Communications Manager Administration Guide.

Perform the following steps to configure BLF presence features:


Note

You do not need to configure BLF presence groups or the Default Inter-Presence Group Subscription parameter for BLF/SpeedDials.

Procedure
    Step 1   If you have not already done so, configure the phones and SIP trunks that you plan to use with the BLF presence feature.
    Step 2   Enable the BLF for Call Lists enterprise parameter.
    Step 3   Configure the clusterwide service parameters for BLF presence in Cisco Unified Communications Manager Administration.
    Step 4   To use BLF presence group authorization, configure BLF presence groups and permissions.
    Step 5   Apply a BLF presence group to the directory number, SIP trunk, phone that is running SIP, phone that is running SCCP, end user, and application user (for application users that are sending BLF presence requests over the SIP trunk) in Cisco Unified Communications Manager Administration.
    Step 6   To allow BLF presence requests from a SIP trunk, check the Accept Presence Subscription check box in the SIP Trunk Security Profile Configuration window.
    Step 7   To enable application-level authorization for a SIP trunk application in addition to trunk-level authorization, check the following check boxes in the SIP Trunk Security Profile Configuration window:
    • Enable Digest Authentication
    • Enable Application Level Authorization
    Note   

    You cannot check Enable Application Level Authorization unless Enable Digest Authentication is checked.

    Apply the profile to the trunk. Reset the trunk for the changes to take effect.

    If you checked Enable Application Level Authorization, check the Accept Presence Subscription check box in the Application User Configuration window for the application.

    Step 8   Configure the SUBSCRIBE Calling Search Space and apply the calling search space to the phone, trunk, or end user, if required.
    Step 9   Customize phone button templates for the BLF/SpeedDial buttons.
    Step 10   If you have not already done so, configure the phone where you want to add the BLF/SpeedDial buttons; make sure that you choose the phone button template that you configured for the BLF/SpeedDial lines.
    Step 11   Configure BLF/SpeedDial buttons for the phone or user device profile.
    Related Tasks
    Related References

    BLF presence feature

    When you configure BLF Presence in Cisco Unified Communications Manager Administration, an interested party, known as a watcher, can monitor the real-time status of a directory number or SIP URI, a BLF presence entity, from the device of the watcher.


    Note

    A SIP URI comprises a call destination configured with a user@host format, such as xten3@CompB.cisco.com or 2085017328@10.21.91.156:5060.

    A watcher can monitor the status of the BLF presence entity (also called presentity) with the following options:

    • BLF/SpeedDial buttons
    • Missed call, placed call, or received call lists in the directories window
    • Shared directories, such as the corporate directory

    Call lists and directories display the BLF status for existing entries. When you configure BLF/SpeedDial buttons, the BLF presence entity displays as a speed dial on the device of the watcher.


    Tip

    For BLF presence-supported phones that are running SIP, you can configure directory numbers or SIP URIs as BLF/SpeedDial buttons. For BLF presence-supported phones that are running SCCP, you can only configure directory numbers as BLF/SpeedDial buttons.


    Tip

    You configure BLF/SpeedDial buttons for a phone or user device profile. The BLF value does not have to be on the cluster. For information on the Busy Lamp Field (BLF) status icons that display on the phone, see the Cisco Unified IP Phone documentation that supports your phone. To identify whether your phone supports BLF presence, see the Cisco Unified IP Phone documentation that supports your phone and this version of Cisco Unified Communications Manager.

    To view the status of a BLF presence entity, watchers send BLF presence requests to Cisco Unified Communications Manager. After administrators configure BLF presence features, real-time status icons display on the watcher device to indicate whether the BLF presence entity is on the phone, not on the phone, status unknown, and so on.

    Extension mobility users can use BLF presence features on phones with extension mobility support.

    BLF presence group authorization ensures that only authorized watchers can access the BLF presence status for a destination. Because the administrator ensures that the watcher is authorized to monitor the destination when a BLF/Speed Dial is configured, BLF presence group authorization does not apply to BLF/Speed Dials.


    Note

    For phones that are running SIP, BLF presence group authorization also does not apply to any directory number or SIP URI that is configured as a BLF/Speed Dial that appears in a call list.

    To allow BLF presence requests from outside the cluster, administrators must configure the system to accept BLF presence requests from the external trunk or application. You can assign BLF presence groups to trunks and applications outside the cluster to invoke BLF presence group authorization.

    The SUBSCRIBE Calling Search Space determines how Cisco Unified Communications Manager routes BLF presence requests that come from the trunk or the phone. The SUBSCRIBE Calling Search Space that is associated with an end user gets used for extension mobility calls.

    BLF presence with phones and trunks


    Tip

    Use the information in this section with the BLF presence groups, the BLF presence authorization, theBLF presence with route lists, and the SUBSCRIBE Calling Search Space. The following information assumes that the phones and trunks have permission to view the status of the BLF presence entity, as configured through BLF presence groups.

    Cisco Unified Communications Manager handles all BLF presence requests for Cisco Unified Communications Manager users, whether inside or outside the cluster.

    For a Cisco Unified Communications Manager watcher that sends a BLF presence request through the phone, Cisco Unified Communications Manager responds with the BLF presence status directly if the phone and BLF presence entity are colocated.

    If the device exists outside of the cluster, Cisco Unified Communications Manager queries the external device through the SIP trunk. If the watcher has permission to monitor the external device, the SIP trunk sends the BLF presence request to the external device and returns BLF presence status to the watcher.

    For non-Cisco Unified Communications Manager watchers that send BLF presence requests through a Cisco Unified Communications Manager trunk, Cisco Unified Communications Manager responds with BLF presence status if Cisco Unified Communications Manager supports the BLF presence entity. If Cisco Unified Communications Manager does not support the BLF presence entity, the request gets rejected.

    The following examples demonstrate how BLF presence works for phones and trunks when the phones and trunks have permission to send and receive presence requests.

    A Cisco Unified Communications Manager User Queries the BLF Status of Another Cisco Unified Communications Manager User.

    A Cisco Unified Communications Manager user calls another Cisco Unified Communications Manager user only to find that the called party is not available. When available, the called party checks the missed call list, and the phone contacts Cisco Unified Communications Manager. Cisco Unified Communications Manager validates that the called party is a valid watcher and determines that the caller represents a Cisco Unified Communications Manager presence entity. The BLF status for the caller gets updated on the phone of the called party.

    A Cisco Unified Communications Manager User Queries the BLF Status of a Non-Cisco Unified Communications Manager User.

    A non-Cisco Unified Communications Manager user calls a Cisco Unified Communications Manager user only to find that the Cisco Unified Communications Manager user is unavailable. When available, the Cisco Unified Communications Manager user checks the missed call list, and the phone contacts Cisco Unified Communications Manager. Cisco Unified Communications Manager confirms that the Cisco Unified Communications Manager user is a valid watcher and determines that the non-Cisco Unified Communications Manager user represents a presence entity. A SIP trunk interacts with the non-Cisco Unified Communications Manager network and Cisco Unified Communications Manager, and status for the non-Cisco Unified Communications Manager user gets updated on the phone of the Cisco Unified Communications Manager user.

    A Non-Cisco Unified Communications Manager User Queries the BLF Presence Status of a Cisco Unified Communications Manager User.

    A non-Cisco Unified Communications Manager user queries the state of a Cisco Unified Communications Manager user. The request comes through a Cisco Unified Communications Manager SIP trunk. Cisco Unified Communications Manager verifies that the non-Cisco Unified Communications Manager user is a valid watcher and determines that the Cisco Unified Communications Manager user represents a Cisco Unified Communications Manager presence entity. Cisco Unified Communications Manager sends the status to phone of the non-Cisco Unified Communications Manager user.

    A Cisco Unified Communications Manager Accesses the Corporate Directory to Get BLF Status.

    A Cisco Unified Communications Manager user accesses the corporate directory on the phone. For each directory entry, BLF status displays.

    A Phone Monitors a BLF/SpeedDial.

    After an administrator configures the BLF presence feature and the BLF/SpeedDial buttons, a user can immediately begin to monitor the real-time status of a BLF presence entity.

    BLF presence with route lists


    Tip

    Use the information in this section with the BLF presence with phones and trunks, the BLF presence groups, the BLF presence authorization, and the SUBSCRIBE Calling Search Space.

    Cisco Unified Communications Manager receives BLF presence requests from watchers and status responses from BLF presence entities. Watchers and BLF presence entities can exist inside the cluster or outside of the cluster.

    Cisco Unified Communications Manager supports external incoming and outgoing BLF presence requests through the SIP trunk. SIP trunks can be members of route groups, which are members of route lists. When Cisco Unified Communications Manager receives a BLF presence request or notification status that is associated with an outbound SIP trunk or route group, Cisco forwards the request or status to a SIP trunk.


    Note

    BLF Presence requests and responses must route to SIP trunks or routes that are associated with SIP trunks. The system rejects BLF presence requests routing to MGCP/H323 trunk devices.

    When a request gets forwarded to a route group or list, any SIP trunk in the group or list can carry the request. Cisco Unified Communications Manager forwards the request to the next available or idle outbound SIP trunk in the group or list. This process repeats until Cisco Unified Communications Manager receives a successful response or the operation fails.

    After the BLF presence request to an external presentity is successful, the SIP trunk receives notification messages based on status changes for the presentity and sends the status to the route list/group to notify the watcher. When different watchers send BLF presence requests to the same presentity that is reached through the route list/group and SIP trunk, Cisco Unified Communications Manager sends the cached status for the presentity to the subscriber instead of creating another subscription.

    The presentity can terminate the subscription at any time due to time-out or other reasons. When the SIP trunk receives a termination status, the termination status gets passed to the route list or group to notify the watcher.

    See the SUBSCRIBE Calling Search Space chapter in the Cisco Unified Communications Manager Administration Guide for more information about configuring route lists.

    BLF presence groups


    Tip

    The Default Inter-Presence Group Subscription service parameter for the Cisco CallManager service sets the clusterwide permissions parameter for BLF presence groups to Allow Subscription or Disallow Subscription. This enables administrators to set a system default and configure BLF presence group relationships by using the default setting for the cluster. For information on configuring this service parameter, see the Configure Presence service parameters and enterprise parameters.

    Cisco Unified Communications Manager allows you to configure BLF presence groups to control the destinations that watchers can monitor. To configure a BLF presence group, create the group in Cisco Unified Communications Manager Administration and assign one or more destinations and watchers to the same group.


    Note

    The system always allows BLF presence requests within the same BLF presence group.

    You must also specify the relationships to other BLF presence groups by using one of the following permissions from the drop-down list in the BLF Presence Group Configuration window:

    • Use System Default - To use the Default Inter-Presence Group Subscription service parameter (Allow Subscription or Disallow Subscription) setting for the permission setting, select the group(s) and configure the Subscription Permission to Use System Default.
    • Allow Subscription - To allow a watcher in this group to monitor members in another group, select the group(s) and configure the Subscription Permission setting to Allow Subscription.
    • Disallow Subscription - To block a watcher in this group from monitoring members in another group, select the group(s) and configure the Subscription Permission setting to Disallow Subscription.

    Tip

    Whenever you add a new BLF presence group, Cisco Unified Communications Manager defines all group relationships for the new group with the default cluster setting as the initial permission setting.To apply different permissions, you configure new permissions between the new group and existing groups for each permission that you want to change.

    The permissions that are configured for a BLF presence group display in the BLF Presence Group Relationship pane. Permissions that use the system default permission setting for the group-to-group relationship do not display.

    Example: Configuring BLF Presence Group Permissions

    Assume the clusterwide setting for Default Inter-Presence Group Subscription is set to Disallow Subscription. You create two BLF presence groups: Group A (workers) and Group B (managers). If you want to allow Group B members to monitor Group A members but to block group A members from monitoring Group B members, you would configure Allow Subscription for Group B to Group A. (Because the system default is Disallow Subscription, Group A already disallows subscriptions to Group B, unless you change the Default Inter-Presence Group Subscription service setting.)

    Cisco Unified Communications Manager automatically creates the Standard BLF Presence Group at installation, which serves as the default group for BLF presence users. All BLF presence users (except application user) initially get assigned to the Standard BLF Presence group. You cannot delete this group.


    Note

    Because not all application users use the SIP trunk or initiate BLF presence requests, the default setting for application user specifies None. To assign an application user to the Standard BLF Presence Group, administrators must configure this option.

    For each BLF presence group that you create, you apply the BLF presence group to one or more of following items in Cisco Unified Communications Manager Administration (see the following table).

    Table 1 Applying BLF Presence Groups

    Apply BLF Presence Groups to

    Presence Entity or Watcher

    Comments

    Directory number

    Presence entity

    For phones that are running either SIP or SCCP

    Trunk

    Watcher and Presence Entity

    For external BLF presence servers that send presence requests via SIP trunk or a proxy server that is connected on SIP trunk (serving as watcher)

    For outgoing BLF presence requests to the SIP trunk (serving as presence entity)

    Phone

    Watcher

    For phones that are running either SIP or SCCP

    Application User

    Watcher

    For external applications that send BLF presence requests via SIP trunk or home on a proxy server that is connected on SIP trunk (for example Web Dial, IPPM, Meeting Place, conference servers, and presence servers)

    End User

    Watcher

    For user directories and call lists and to configure extension mobility settings.

    Note 1: A phone serves as a watcher; a line on a phone cannot serve as a watcher.

    Note 2: You do not need to provision BLF presence groups for BLF/SpeedDials.


    Tip

    See the BLF presence authorization, for additional requirements for BLF presence requests through the SIP trunk.

    The following examples describe how a phone or trunk obtains the destination status by using different BLF presence groups and permissions.

    A Phone Wants Status About a Directory Number That Is Assigned to BLF/SpeedDial.

    Phone A, which is colocated with Phone B, has directory number 1111 (Phone B) that is configured as a BLF/SpeedDial button to monitor BLF presence status for Phone B. Phone A receives real-time status for directory number 1111 and displays the status icon next to the BLF/SpeedDial button. The system does not invoke BLF presence group authorization.

    A Phone Wants Status About a Directory Number in a Call List.

    Phone A, which has the BLF presence group, User Group, that is configured for it, has directory number 1111 in the Missed Calls call list. Directory number 1111, which exists for Phone B, has the BLF presence group, Executive Group, that is configured for it. The BLF Presence Group Configuration window indicates that the relationship between the User Group and Executive Group is Disallow Subscription, as specified in the BLF Presence Group Relationship pane. Phone A cannot receive real-time status for directory number 1111, and Phone A does not display the real-status icon next to the Missed Call list entry.

    A SIP Proxy Server That Is Connected to a SIP Trunk Wants Status About a Cisco Unified Communications Manager Directory Number.

    The following example describes how a SIP trunk obtains the status of a directory number when different BLF presence groups are configured for the SIP trunk and directory number. SIP proxy server D uses SIP trunk C to contact Cisco Unified Communications Manager for the status of directory number 5555 because directory number 5555 exists as a BLF/SpeedDial button on phone E that is running SIP, which connects to the proxy server. The SIP trunk indicates that it has BLF presence group, Administrator Group, that is configured for it, and directory number 5555 is assigned to the Engineering Group. The BLF Presence Group Configuration window indicates that the relationship between the Administrator Group and Engineering Group is allowed, as specified in the BLF Presence Group Relationship pane. Cisco Unified Communications Manager sends the status of the directory number to the trunk, which passes the status to the SIP proxy server D. Phone E that is running SIP receives real-time status for directory number 5555, and the phone displays the real-time status icon next to the BLF/SpeedDial button.

    BLF presence authorization


    Tip

    Use the information in this section with the BLF presence with phones and trunks, the BLF presence groups, and the SUBSCRIBE Calling Search Space.

    To view the status of a presence entity, watchers send presence requests to Cisco Unified Communications Manager. The system requires watchers to be authorized to initiate status requests for a presence entity by using these mechanisms:

    • The watcher BLF presence group must possess authorization to obtain the status for the presence entity presence group, whether inside or outside of the cluster.
    • Cisco Unified Communications Manager must possess authorization to accept BLF presence requests from an external presence server or application.

    Note

    The authorization process remains independent of calling search space routing for BLF presence requests.

    To initiate BLF presence group authorization, you must configure one or more BLF presence groups and assign the appropriate permissions. Administrators configure permission settings for BLF presence groups, which specify when a BLF presence group for a watcher can monitor the status of members in other groups. To validate a BLF presence request, Cisco Unified Communications Manager performs a database lookup by using the permissions that are assigned to the BLF presence groups that are configured.

    If you choose not to use BLF presence group authorization, leave all presence users assigned to the default BLF presence group and do not configure additional groups or permissions. You will still need to configure authorization for a SIP trunk or application if you want to authorize Cisco Unified Communications Manager to accept incoming BLF presence requests from an external presence server or application.


    Tip

    When an administrator decides to add or change a BLF/SpeedDial button, the administrator ensures that the watcher is authorized to monitor that destination.

    Administrators configure the Cisco Unified Communications Manager system to accept BLF presence requests that come via the SIP trunk by configuring parameters for the SIP trunk and application user.

    To authorize the Cisco Unified Communications Manager system to accept incoming BLF presence requests from the SIP trunk, check the Accept Presence Subscription check box in the SIP Trunk Security Profile Configuration window. (To block incoming presence requests on a SIP trunk, uncheck the check box.) When SIP trunk BLF presence requests are allowed, Cisco Unified Communications Manager accepts requests from the SIP user agent (SIP proxy server or external BLF presence server) that connects to the trunk. Consider digest authentication as optional when Cisco Unified Communications Manager is configured to accept BLF presence requests from a SIP trunk.


    Tip

    To use BLF presence group authorization with incoming presence requests on a SIP trunk, configure a presence group for the trunk, such as External_Presence_Serv_Group1, and configure the appropriate permissions to other groups inside the cluster.

    To authorize the Cisco Unified Communications Manager system to accept BLF presence requests from an external application that connects on the SIP trunk, check the Enable Application Level Authorization check box in the SIP Trunk Security Profile Configuration window and the Accept BLF Presence Subscription check box in the Applications User Configuration window for the application. When you configure the Cisco Unified Communications Manager system to accept BLF presence requests from an application user, Cisco Unified Communications Manager validates each presence request that is received on the SIP trunk before accepting it.


    Tip

    To use presence group authorization with incoming presence requests from a SIP trunk application, configure a presence group for the application, such as Presence_User, and configure the appropriate permissions to other groups inside the cluster.

    If you configure both levels of authorization for SIP trunk presence requests, the BLF presence group for the SIP trunk gets used only when no BLF presence group is identified in the incoming request for the application.

    Before application authorization can occur, Cisco Unified Communications Manager must first authenticate the external application by using digest authentication. Enable Application Level Authorization cannot be checked unless Enable Digest Authentication is checked.


    Note

    The authorization could pass for the trunk but fail for the application. See the Presence group and Presence authorization tips, for additional considerations when configuring presence authorization.

    See the Cisco Unified Communications Manager Security Guide for more information about authentication and authorization.

    SUBSCRIBE Calling Search Space

    The SUBSCRIBE Calling Search Space determines how Cisco Unified Communications Manager routes BLF presence requests that come from the trunk or the phone. The SUBSCRIBE calling search space, which is associated with a watcher, specifies the list of partitions to search for routing information to a presence entity for BLF presence requests.

    To configure a calling search space specifically for this purpose, you configure a calling search space as you do all calling search spaces (Call Routing > Class of Control > Calling Search Space). For information on how to configure a calling search space, see the Cisco Unified Communications Manager Administration Guide.

    The SUBSCRIBE Calling Search space option allows you to apply a calling search space separate from the call-processing Calling Search Space for BLF presence requests. If you do not select a different calling search space for presence requests, the SUBSCRIBE Calling Search Space defaults to None.

    You apply the SUBSCRIBE Calling Search Space to the SIP trunk, phone, or end user. The SUBSCRIBE Calling Search Space that is associated with an end user gets used for extension mobility calls.

    BLF presence with extension mobility


    Tip

    Use the information in this section in conjunction with the BLF presence groups, the BLF presence authorization, and the SUBSCRIBE Calling Search Space.

    When you configure BLF/SpeedDial buttons in a user device profile in Cisco Unified Communications Manager Administration, a phone that supports Cisco Extension Mobility can display BLF presence status on the BLF/SpeedDial buttons after you log in to the device. The SUBSCRIBE calling search space and presence group that are configured for the user apply.

    When the extension mobility user logs out, a phone that supports Cisco Extension Mobility displays BLF presence status on the BLF/SpeedDial buttons for the log-out profile that is configured. When a user device profile is configured for the logout profile, the SUBSCRIBE calling search space and BLF presence group that are configured for the user apply.


    Tip

    See the Cisco Unified Communications Manager Administration Guide for more information about configuring device profiles.

    System requirements

    The following system requirements exist for the Busy Lamp Field (BLF) Presence feature in Cisco Unified Communications Manager:

    • Cisco Unified Communications Manager 8.0(2) (or higher) on each server in the cluster
    • To identify the Cisco Unified IP Phone models that support BLF Presence, generate the Unified CM Phone Features List report in Cisco Unified Reporting. To generate the report, choose BLF Speed Dial, BLF Speed Dial with URI, or BLF Presence Subscription.

    Interactions and restrictions

    The following interactions and restrictions apply to the BLF presence feature:

    • Cisco Unified Communications Manager Assistant does not support SIP presence.
    • Cisco Unified Communications Manager supports an inbound BLF presence request to a directory number that is associated with a hunt list.
    • Cisco Unified Communications Manager rejects BLF presence requests to a directory number that is associated with a hunt pilot.
    • The BLF on call list feature is not supported on the Cisco Unified IP Phone 7940 and Cisco Unified IP Phone 7960.
    • Because the administrator ensures that the watcher is authorized to monitor the destination when configuring a BLF/SpeedDial, BLF presence group authorization does not apply to BLF/SpeedDials. For phones that are running SIP, BLF presence group authorization also does not apply to any directory number or SIP URI that is configured as a BLF/Speed Dial that appears in a call list.
    • For Cisco Unified IP Phones with multiple lines, the phone uses the cached information that is associated with the line directory number for missed and placed calls to determine BLF presence authorization. If this call information is not present, the phone uses the primary line as the subscriber for BLF presence authorization. For BLF/SpeedDial buttons on Cisco Unified IP Phones with multiple lines, the phone uses the first available line as the subscriber.
    • When a user monitors a directory number that is configured for Cisco Unified IP Phones 7960, 7940, 7905, and 7912 that are running SIP, the system displays a status icon for ‘not on the phone’ on the watcher device when the presentity is off hook (but not in a call connected state). These phones do not detect an off hook status. For all other phone types, the system displays the status icon for ‘on the phone’ on the watcher device for an off-hook condition at the presentity.
    • You can configure BLF in the BAT phone template.

    The following restrictions apply to Presence BLF interaction with DNs on H.323 phones when the H.323 phone device serves as presentity:

    • When the H.323 phone is in the RING IN state, the BLF status gets reported as Busy. (For phone presentities of phones that are running either SCCP or SIP and that are in the RING IN state, the BLF status gets reported as Idle.)
    • When the H.323 phone is not connected to Cisco Unified Communications Manager for any reason, such as the Ethernet cable is unplugged from the phone, the BLF status gets reported as Idle all the time. (For presentities of phones that are running either SCCP or SIP and that are not connected to Cisco Unified Communications Manager, the BLF status gets reported as Unknown.)

    Presence configuration

    This section contains information to configure Presence.


    Tip

    Before you configure Presence, review the configuration summary task for this feature.

    Related Tasks

    Configure Presence service parameters and enterprise parameters

    To configure presence enterprise parameters, for example, the BLF for Call List parameter, in Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters. For information on the parameter, click the question mark that displays in the Enterprise Parameter Configuration window or click the link for the parameter name.

    To configure presence service parameters, for example, the Default Inter-Presence Group Subscription parameter, perform the following procedure:


    Tip

    The Default Inter-Presence Group Subscription parameter does not apply to BLF/SpeedDials.

    Procedure
      Step 1   In Cisco Unified Communications Manager Administration, choose System > Service Parameters.
      Step 2   From the Server drop-down list box, choose the server where you want to configure the parameter.
      Step 3   From the Service drop-down list box, choose the Cisco CallManager (Active) service.

      If the service does not display as active, ensure that the service is activated in Cisco Unified Serviceability.

      Step 4   Locate the clusterwide service parameters for the Presence feature.
      Tip   

      For information on the parameters, click the parameter name or click the question mark that displays in the Service Parameter Configuration window.

      Step 5   Update the parameter values.
      Step 6   Click Save.

      Configure and apply the SUBSCRIBE Calling Search Space

      All calling search spaces that you configure in Cisco Unified Communications Manager Administration display in the SUBSCRIBE Calling Search Space drop-down list box in the Trunk Configuration or Phone Configuration window.

      The SUBSCRIBE Calling Search Space determines how Cisco Unified Communications Manager routes presence requests that come from the trunk or the phone. If you do not select a different calling search space for presence requests, the SUBSCRIBE Calling Search Space defaults to None.

      To configure a calling search space specifically for this purpose, you configure a calling search space as you do all calling search spaces (Call Routing > Class of Control > Calling Search Space). For information on how to configure a calling search space, see the Cisco Unified Communications Manager Administration Guide.

      To apply a SUBSCRIBE Calling Search Space to the SIP trunk, phone, or end user, perform the following procedure:

      Procedure
        Step 1   Perform one of the following tasks:
        1. Find a phone, as described in the Cisco Unified Communications Manager Administration Guide.
        2. Find a SIP trunk, as described in the Cisco Unified Communications Manager Administration Guide.
        3. Find an end user, as described in the Cisco Unified Communications Manager Administration Guide.
        Step 2   After the configuration window displays, choose the calling search space from the SUBSCRIBE Calling Search Space drop-down list box.
        Step 3   Click Save.
        Step 4   Click Reset.

        Find Presence groups

        The Find and List window for presence groups allows you to search for presence groups, which are used with the presence feature for authorization. To find a presence group, perform the following procedure:

        Procedure
          Step 1   Choose System > Presence Group.

          The Find and List Presence Groups window displays. Records from an active (prior) query may also display in the window.

          Step 2   To filter or search records
          1. From the first drop-down list box, choose a search parameter.
          2. From the second drop-down list box, choose a search pattern.
          3. Specify the appropriate search text, if applicable.
            Note   

            To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the – button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.

          Step 3   To find all records in the database, ensure the dialog box is empty, click Find.

          All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.

          Note   

          You can delete multiple records from the database by checking the check boxes next to the appropriate record and clicking Delete Selected. You can delete all configurable records for this selection by clicking Select All and then clicking Delete Selected.

          Step 4   From the list of records that display, click the link for the record that you want to view.
          Note   

          To reverse the sort order, click the up or down arrow, if available, in the list header.

          The window displays the item that you choose.

          Configure Presence groups

          To add, update, or copy presence groups, perform the following procedure:

          Procedure
            Step 1   In Cisco Unified Communications Manager Administration, choose System > Presence Group.
            Step 2   Perform one of the following tasks:
            1. To add a new presence group, click the Add New button.
            2. To copy an existing presence group, locate the appropriate group as described in Find Presence groups, click the Copy button or Copy icon next to the presence group that you want to copy.
            3. To update an existing presence group, locate the appropriate group as described in Find Presence groups.
            4. To rename a presence group, locate the group as described in Find Presence groups, click the Name link for group on the list, enter the new name when the window displays.
            Step 3   Enter the appropriate settings as described in Presence group configuration.
            Step 4   Click Save.
            What to Do Next

            Additional Steps

            After you configure the presence groups, apply the presence group configuration to the phone that is running either SIP or SCCP, SIP trunk, directory number, application user (for application users sending presence requests over the SIP trunk), or end user in Cisco Unified Communications Manager Administration. See the Apply a Presence group.

            Presence group configuration

            Presence authorization works with presence groups. The following table describes the presence group configuration settings. Before you configure these settings, review the Presence group and Presence authorization tips.

            Table 2 Presence Group Configuration Settings

            Field

            Description

            Name

            Enter the name of the presence group that you want to configure; for example, Executive_Group.

            Description

            Enter a description for the presence group that you are configuring.

            Modify Relationship to Other Presence Groups

            Select one or more presence groups to configure the permission settings for the named group to the selected group(s).

            Subscription Permission

            For the selected presence group(s), choose one of the following options from the drop-down list box:

            • Use System Default - Set the permissions setting to the Default Inter-Presence Group Subscription clusterwide service parameter setting (Allow Subscription or Disallow Subscription).
            • Allow Subscription - Allow members in the named group to view the real-time status of members in the selected group(s).
            • Disallow Subscription - Block members in the named group from viewing the real-time status of members in the selected group(s).

            The permissions that you configure display in the Presence Group relationship pane when you click Save. All groups that use system default permission setting do not display.

            Delete a Presence group

            This section describes how to delete a presence group from the Cisco Unified Communications Manager database.

            Before You Begin

            Before you can delete a presence group from Cisco Unified Communications Manager Administration, you must apply another group to the devices/user or delete all devices/users that use the presence group.

            To find out which devices/users use the presence group, click the Name link for the presence group in the Find and List window; then, choose Dependency Records from the Related Links drop-down list box when the Presence Group Configuration window displays; click Go.

            If the dependency records feature is not enabled for the system, enable dependency records in the System > Enterprise Parameters window. For more information about dependency records, see the Cisco Unified Communications Manager System Guide.

            Procedure
              Step 1   Find the presence group by using the procedure in the Find Presence groups.
              Step 2   To delete multiple presence groups, check the check boxes next to the appropriate presence group in the Find and List window; then, click the Delete Selected icon or the Delete Selected button.
              Step 3   To delete a single presence group, perform one of the following tasks:
              1. In the Find and List window, check the check box next to the appropriate presence group; then, click the Delete Selected icon or the Delete Selected button.
              2. In the Find and List window, click the Name link for the presence group. After the specific Presence Group Configuration window displays, click the Delete icon or the Delete button.
              Step 4   When prompted to confirm the delete operation, click OK to delete or Cancel to cancel the delete operation.

              Apply a Presence group

              For information on configuring presence groups in Cisco Unified Communications Manager Administration, see the BLF presence groups. For information about configuring permission settings for presence authorization, see the BLF presence authorization. The system always allows presence requests between members in the same presence group.

              To apply a presence group to the directory number, SIP trunk, phone that is running SIP, phone that is running SCCP, application user (for application users that are sending presence requests over the SIP trunk), or end user, perform the following procedure:

              Procedure
                Step 1   Perform one of the following tasks:
                1. Find a SIP trunk, as described in the Cisco Unified Communications Manager Administration Guide.
                2. Find an application user, as described in the Cisco Unified Communications Manager Administration Guide.
                3. Find an end user, as described in the Cisco Unified Communications Manager Administration Guide.
                4. Find a phone that is running either SCCP or SIP, as described in the Cisco Unified Communications Manager Administration Guide.
                  Tip   

                  After the Phone Configuration window displays, you can access the Directory Number Configuration window by clicking the Line link in the Association Information pane. In the Directory Number Configuration window, you specify the presence group for the directory number.

                  Tip   

                  When an administrator decides to add or change a BLF/SpeedDial button, the administrator ensures that the watcher is authorized to monitor that destination.

                Step 2   After the configuration page displays, choose the group from the Presence Group drop-down list box. See the Presence group and Presence authorization tips for provisioning tips.
                Step 3   Click Save.
                Step 4   For devices, you must click Reset.
                Step 5   Repeat the procedure for all items that are listed.

                Presence group and Presence authorization tips

                Presence authorization works with presence groups. This section lists tips to use when you are configuring presence groups for presence authorization.

                • To allow a watcher to monitor a destination, make sure that the presence group that is applied to the watcher that is originating the request, including application users, has permission to monitor the group that is applied to the presence entity. End users for supported applications, for example, Cisco Unified Communications Manager Assistant end users, also serve as watchers because the user requests status about a presence entity that is configured on the application.
                • To allow Cisco Unified Communications Manager to receive and route presence requests from the SIP trunk application, make sure that the Accept Presence Subscription check box is checked in the Application User Configuration window to authorize incoming SUBSCRIBE requests. If no presence group is applied to the application user, Cisco Unified Communications Manager uses the presence group that is applied to the trunk.
                • If you check the Accept Presence Subscription check box for an application user, but do not check the Accept Presence Subscription check box (in the SIP Trunk Security Profile Configuration window) that is applied to the trunk, a 403 error message gets sent to the SIP user agent that is connected to the trunk.
                • If you check the Accept Presence Subscription check box for an application user, but do not check the Enable Application Level Authorization check box (in the SIP Trunk Security Profile Configuration window) that is applied to the trunk, a 403 error message gets sent to the SIP user agent that is connected to the trunk.
                • If digest authentication is not configured for the SIP trunk, you can configure the trunk to accept incoming subscriptions, but application-level authorization cannot be initiated, and Cisco Unified Communications Manager will accept all incoming requests before performing group authorization.
                • If the SIP trunk uses digest authentication, as configured in the SIP Trunk Security Profile Configuration window, incoming presence requests require authentication of the credentials from the sending device. When digest authentication is used with application-level authorization, Cisco Unified Communications Manager also authenticates the credentials of the application that is sending the presence requests.
                • After authorization and authentication is successful for a SIP trunk application, Cisco Unified Communications Manager performs group authorization to verify the group permissions that are associated with the SUBSCRIBE request before accepting the request.
                • When an administrator decides to add or change a BLF/SpeedDial button for a SIP URI, the administrator ensures that the watcher is authorized to monitor that destination. If the system uses a SIP trunk to reach a SIP URI BLF target, the presence group associated with the SIP trunk applies.
                • When configuring a SIP URI as BLF/SpeedDial button, make sure the routing patterns are appropriately configured. See the Cisco Unified Communications Manager Administration Guide for more information.

                Configure a customized phone button template for BLF/SpeedDial buttons

                Administrators can configure BLF/SpeedDial buttons for a phone, or user device profile. The Add a new BLF SD link does not display in the Association Information pane unless you configure a customized phone button template for BLF/SpeedDial buttons and apply the template to the phone or user device profile. After you apply the template to the phone or device profile (and save the phone or device profile configuration), the Add a new BLF SD link displays in the Association Information pane.


                Tip

                If the template does not support BLF/SpeedDials, the Add a new BLF SD link displays in the Unassigned Associated Items pane.

                To configure a customized phone button template for BLF/SpeedDial buttons, perform the following procedure:

                Procedure
                  Step 1   Find the phone button template for the device, as described in the Cisco Unified Communications Manager Administration Guide.
                  Step 2   After the Find/List window displays, click the Copy button or Copy icon for the phone button template.
                  Step 3   In the Button Template Name field, enter a new name for the template; for example, BLF SIP 7970.
                  Step 4   Click Save.
                  Step 5   After the Phone Button Template Configuration window displays, choose Speed Dial BLF from the Feature drop-down list box(es); that is, if you want the line to be configured as a BLF/SpeedDial button.
                  Step 6   Click Save.
                  Step 7   If you are updating an existing customized phone button template that you already applied to phones, click Reset.

                  Configure BLF/SpeedDial buttons

                  To configure BLF/SpeedDial buttons, perform the following procedure:

                  Procedure
                    Step 1   To configure the BLF/SpeedDial button in the Phone Configuration window, find a phone, as described in the Cisco Unified Communications Manager Administration Guide.
                    Step 2   To configure the BLF/SpeedDial button for user device profiles, find the user device profile as described in theCisco Unified Communications Manager Administration Guide.
                    Step 3   After the configuration window displays, click the Add a New BLF SD link in the Association Information pane.
                    Tip   

                    The link does not display in the Association Information pane if the phone button template that you applied to the phone or device profile does not support BLF/SpeedDials. The link displays in the Unassigned Associated Items pane if the phone button template does not support BLF/SpeedDials.

                    Step 4   Configure the settings, as described in BLF/SpeedDial configuration. Administrators must ensure that the watcher is authorized to monitor a destination that is configured as a BLF/SpeedDial button.
                    Step 5   After you complete the configuration, click Save and close the window.

                    The destination(s) and/or directory number(s) display in the pane.

                    BLF/SpeedDial configuration

                    With the presence feature, a watcher can monitor the status of the presence entity (also called presentity). When you configure BLF/SpeedDial buttons, the presence entity displays as a speed dial on the device of the watcher.

                    The following table describes the settings that you configure for BLF/SpeedDial buttons.

                    Table 3 BLF/SpeedDial Button Configuration Settings

                    Field

                    Description

                    Destination

                    Perform one of the following tasks to configure a SIP URI or a directory number as a BLF/SpeedDial button:

                    • Only for phones that are running SIP, enter the SIP URI. For phones that are running SCCP, you cannot configure SIP URI as BLF/SpeedDial buttons.
                    • For phones that are running either SCCP or SIP, enter a directory number in this field or go to the Directory Number drop-down list box. If you want to configure non-Cisco Unified Communications Manager directory numbers as BLF/SpeedDial buttons, enter the directory number in this field.

                    For this field, enter only numerals, asterisks (*), and pound signs (#).

                    If you configure the Destination field, do not choose an option from the Directory Number drop-down list box. If you choose an option from the Directory Number drop-down list box after you configure the Destination, Cisco Unified Communications Manager deletes the Destination configuration.

                    Directory Number

                    The Directory Number drop-down list box displays a list of directory numbers that exist in the Cisco Unified Communications Manager database. Configure this setting only if you did not configure the Destination field.

                    For phones that are running either SCCP or SIP, choose the number (and corresponding partition, if it displays) that you want the system to dial when the user presses the speed-dial button; for example, 6002-Partition 3. Directory numbers that display without specific partitions belong to the default partition.

                    Label

                    Enter the text that you want to display for the BLF/SpeedDial button.

                    This field supports internationalization. If your phone does not support internationalization, the system uses the text that displays in the Label ASCII field.

                    Label ASCII

                    Enter the text that you want to display for the speed-dial button.

                    The ASCII label represents the noninternationalized version of the text that you enter in the Label field. If the phone does not support internationalization, the system uses the text that displays in this field.

                    Tip    If you enter text in the Label ASCII field that differs from the text in the Label field, Cisco Unified Communications Manager Administration accepts the configuration for both fields, even though the text differs.