Posts

Showing posts from February, 2015

CUCM and Instant Messaging & Presence Integration

IMP Configuration
Navigate to System > Cluster Topology.Edit the IMP server to change the node name from domain to IP. Important to restart the server after the change.Enable the following services:
Cisco SIP ProxyCisco Presence EngineCisco Sync AgentCisco Unified Presence XCP (Extensible Communications Platform) Connection Manager. This service is used to facilitate services communication.Cisco Unified Presence XCP Directory ServiceCisco Unified Presence XCP Authentication Service
Add CUCM TFTP Servers in Application > Legacy Clients > Settings. As the clients first connect to IMP server, the TFTP servers are provided by IMP to CUPC and Jabber Clients to register with CUCM servers.Navigate to System > Settings. Configure cluster ID Nameand Domain Name. The cluster ID name is just a descriptive name.Navigate to System > CUCM Publisher. Configure CUCM Publisher IP, DB secret, AXL username, AXL p…

Cisco Instant Messaging & Presence Clustering

In one presence cluster you can have up to 6 servers (1 publisher and 5 subscribers). A presence cluster can be divided into subclusters (Max of 2 servers per subcluster which provide a max of 3 subclusters).
The subclusters can be configured in 3 modes:
Active/Active In this mode the users are distributed across both nodes in the subcluster. Assuming that we have 3 subclusters with servers names as A1/B1, A2/B2, A3/B3, the distribution algorithm will distribute the users as A1 -> A2 -> A3 -> B1 -> B2 -> B3. Active/Standby In this mode the users are distributed to the first server in each subcluster with second server as backup. Assuming that we have 3 subclusters with servers names as A1/B1, A2/B2, A3/B3, the distribution algorithm will distribute the users as A1 -> A2 -> A3. None In this mode the users should be assigned to servers and subclusters manually instead of sync agent.
IMP publisher will sync with CUCM publisher to get all IMP enabled users and their i…