Presence is the ability to show the status of a user; idle/busy/away, devices they are contactable on and how best to contact them. Simply put it “is the aggregation point of availability represented by a single or multiple devices associated with a user account that can be monitored by users”
At the core, presence is a person’s willingness and ability to communicate utilising all network connected mediums available to them to make them more contactable and productive.
Available mediums are integrations to conferencing resources, calendar, email & IM clients. Utilising these one can make an informed decision as to what maybe the best method of contacting a user. On the other end, users can set their status and also enable features such as SNR that allows them to advertise a single number and be contactable on multiple devices; when a user is called on a deskphone; their home phone/cell phone can simultaneously ring and when connected the call can be transferred to the deskphone/remote phone without any or very little media interruption. Users can also have voice messages delivered to their email inbox, can visually chose what message they wish to listen to and so on.
Cisco UC clients consists of the following;
Cisco IP Communicator (CICP). A windows application that offers softphone capabilities, the same as a deskphone would
Cisco UC Integration for MS Office Communicator (CUCIMOC)- An Client service Framework (CSF) application that provides services such as softphone, mid-call control, desktphone control, IM
Cisco Unified Mobile Communicator (CUMC)- an application for mobile phones and smartphones that allows users to place/receive calls, access corporate directory, view user status, access voicemails, utilise MeetingPlace and Webex conferencing etc.
Cisco Unified Personal Communicator (CUPC) – this provides integration and a single interface to a wide variety of services such as call control, video, im, web conferencing, voicemail. it also allows you the ability to Click-to-dial from MS Excel/Outlook/Word and even the web
Cisco unified Video Advantage (CUVA)- adds video functionality to an ip phone by utilisng deskphones or CIPC utilising existing network infrastructure.
Cisco Presence Server
Cisco Unified Presence Server (CUPS) is the core component of the Cisco Presence solution, it is a separate product integrates directly into CUCM as an extended application. As outlined in RFC 2778 there are 3 basic components to a presence solution;
- [Collect Status] Presence Service: This service aggregates and distributes presence information between clients
- [Publish Status] Presentities: Clients that provide presence information to the presence service to be stored and delivered. Presentities publish their service to the presence server using a PUBLISH or REGISTER message for SIP/SIMPLE Clients or XML Presence Stanza for XMPP clients. It can be DN or SIP uniform resource identifier (URI) that resides outside or within a cluster
- [Consume Information] Watchers: these are Presence clients that receive presence information from the presence service. They do this by
- Fetching: retrieves current presence information from presence service about a presentity; done upon user request
- Subscribing: retrieves current and future presence information from the presence service about a presentity. Provides ongoing subscription to receive status updates
Components of Cisco Unified Presence
- Cisco IM and Presence Service
- Unified Communications Manager (CUCM)
- Cisco Jabber
- Meetingplace or MeetingPlace Express
- Unity or Unity Connection
- Unified Video Conferencing or meeting place Express VT
- UCCE / UCCX /CVP
- Cisco IP Phones
- LDAP Svr 3.0
- Third Party Presence Server/XMPP Clients/Applications
An Illustration of Components;
CM Presence Capabilities
When a IP Phone sends a watcher request, CUCM manages the request locally and if the presentity is located on a separate CUCM cluster or CUPS it forwards the request across the SIP trunk to the external service (provided the user is in the SUBSCRIBE CSS & Presence group that allows the watcher to monitor the requested presentity).When CUCM receives a SIP NOTIFY response on thr trunk it responds to the SIP Line-side presence request by sending a SIP NOTIFY message to the watcher indicating the current status of the presence entity. The services that are natively supported on CUCM are BLF/SpeedDials and Call history logs
CM Presence with SCCP
since CUCM supports SCCP endpoints as presence watchers and there are no SCCP trunks, SCCP endpoints can request the presence status of a presentity to the CUCM by sending SCCP Messages. If the presentity resides within the same cluster CUCM responds back indicating the current status of the Presentity. If it resides outside the CUCM Cluster, CM routes a SUBSCRIBE request out a appropriate SIP trunk based on the SUBSCRIBE css, Presence Group & SIP Route Pattern. When CUCM receives a SIP NOTIFY it responds to the SCCP line-side presence request bysending SCCP messages to the presence watcher, indicating the current status of the presence watcher.
CM Presence Policy
you can create a policy in CM for users who request presence status, inorder to do this you will need to configure a CSS specifically to route SIP SUBSCRIBE messages for presence status and status of users in another group.
CM Subscribe Calling Search Space
The first thing to do is to define a SUBSCRIBE css. CM uses this to determine how to route this request from a watcher (a phone or a Trunk) The SUBSCRIBE css is associated to the watcher and lists the partitions the watcher is allowed to ‘see’. This operates independently of normal CP routing.
This can be assigned on Devices or on a User (EM). A SUBSCRIBE with a CSS set to <None> will reject subscription messages as unknown. If a valid CSS is specified, SUBSCRIBE Messages are routed properly./
The second aspect of the presence policy is presence groups. By default they are all assigned to the Standard Presence Group. A Presence group controls the destination a watcher can monitor
Cisco IM & Presence Cluster
Cisco IM and Presence Cluster consist of upto 6 server’s incl one designated as a publisher . The architecture being the same as a CUCM cluster. Within a cluster you can have a subcluster which can have upto 2 servers upto 3 clusters in a CUP Server cluster without redundancy. The CUP Server publisher uses the database of the CUCM Publisher and can support only one CUCM cluster. User assignment is done automatically using Sync Agent. Synchronisation can be anything between 5 mins for 500/1000 users upto 70 minutes for 70000 users (platform dependant) – this takes alittle longer when CUCM is integrated to CUP cluster and not CUPS Publisher
Computer Telephony Integration Quick buffer Encoding (CTI-QBE) is used between the CUCM & CUP Clusters for CTI Functionality at user level. This allows CUP Server to control phones and provide functionality such as deskphone control from a software client. LDAP integration is via the CUCM and not with the external LDAP Server. AXL/SOAP on CUPS is used to provide database synchronisation from the CUCM Cluster.
Federation to other CUCM Clusters and MS Lync/OCS Server is done via the same CUP Server.
Cisco Unified Presence Fundamentals – Cisco Press
UC SRND 9.x – Update new info