[TABS_R id=10143]
Which of the following interfaces handles the exchange of availability information between UCM and CUPS?
- AXL/SOAP
- LDAP
- SIP
- XMPP
Explanation:
A Session Initiation Protocol (SIP) interface handles the exchange of availability information between Cisco Unified Communications Manager (UCM) and Cisco Unified Presence Server (CUPS). UCM and a CUPS server together are the primary components of a Cisco Presence deployment. A UCM SIP trunk interface must point to the CUPS server in order for availability information to be exchanged between the two systems. CUPS is also capable of sending SIP subscribe messages to UCM over the SIP trunk if UCM is configured as a Presence gateway.
The Extensible Messaging and Presence Protocol (XMPP) interface does not handle the exchange of availability information between UCM and CUPS. However, the XMPP interface is used to handle the exchange of availability information between UCM and XMPP clients, such as instant messaging (IM) clients that are developed by third parties.
The Lightweight Directory Access Protocol (LDAP) interface does not handle the exchange of availability information between UCM and CUPS. However, the LDAP interface is used to synchronize user information between UCM and CUPS in order to create a single sign-on (SSO) user experience or to perform contact searches. For example, a Cisco Unified Personal Communicator user can be authenticated to both the CUPS server and UCM by connecting directly to the CUPS server. LDAP is a directory protocol that is used by other servers, such as CUPS, to perform contact lookups. LDAP listens on Transmission Control Protocol (TCP) port 389 unencrypted or on port 636 over Secure Sockets Layer (SSL). Third-party XMPP clients can also use LDAP to search the database and add users as contacts.
The Cisco Administrative Extensible Markup Language (AXL)/Simple Object Access Protocol (SOAP) interface does not handle the exchange of availability information between UCM and CUPS. However, the AXL/SOAP interface is used to handle database synchronization tasks from UCM to the CUPS database. For synchronization to start, the Sync Agent service must be started on the CUPS server.
[TABS_R id=10143]