Presence is a real-time indicator of user availability that’s often integrated with a Cisco Unified Communication (UC) cluster. It integrates with calendaring, location, and workflow systems, allowing users to automatically share their status with others. Presence resides on a single or multiple servers depending on the number of users you want to provide presence capabilities for.
Presence is usually integrated with Cisco’s Commnication Manager which provides the call control for a UC cluster. Typically, Communication Managers are used in larger deployments when there are 300 or more phones. However, Presence features aren’t just for deployments that include a CUCM and Presence, it can also be incorporated in a Cisco Communication Manager Express (CME or simply “Express”) system.
CME is usually deployed for single or remote sites with under 100 phones, but it can expand to 700 phones (though I wouldn’t recommended it). When using Express, most of the configuration is done by command line or the rudimentary GUI interface. What many people don’t realize is that CUCME can be configured with Presence features, without the use of a MCS server.
With just a few simple commands and the use of SIP, CUCME can support presence. The configuration is simple but will require the configuration of sip phones, h.323 and sccp is not supported is this configuration. So how do you do it?
- Enable presence for internal lines
- Enable a directory number to be watched
- Enable a SCCP or SIP phone to monitor BLF status for speed dials and call llists
- Configure presence to watch external lines
- Verify and troubleshoot presence configurations
Step 1: Enable presence for internal lines
routerA(config-sip-ua)# presence enable
Step 2: Enable a directory number to be watched
routerA(config-ephone-dn # or router(config-register-dn ) allow watch
Step 3: Enable a phone to monitor BLF status
routerA(config-ephone)# or router(config-register-pool)# blf-speed-dial tag number label string
Step 4: Configure presence to watch external lines
Step 5: Verify and troubleshoot
Author: Chris Foster