Configuring Directory URI Dialing for Cisco Jabber

Step-1 Associate URIs to DNs. This can be done automatically or manual

Note: You can create up to 5 directory URIs per user and nominate a primary one.

a. Automatically Populate Directory Numbers with URIs - Manual User Creation
When create end users in CUCM, you can associate devices to them as well as primary extensions. Also, you can populate directory URI field for end users. Configuring directory URI for end user with primary extension associated will populate the directory URI field for this DN automatically

The directory URI in the DN will be automatically assigned to 'Directory URI' partition. This partition is automatically created by CUCM and can't be modified or deleted. 'Directory URI' partition created by CUCM and assigned automatically to directory URIs is an alias and the actual partition mapped to it is controlled by the enterprise service parameter 'Directory URI Alias Partition'

The calling party CSS should include 'Directory URI Alias Partition' to be able to dial directory URIs

b. Automatically Populate Directory Numbers with URIs - LDAP Integration 
In this case, end users will be synchronized from LDAP server with 'directory URI' field pre-filled with LDAP attribute. Once you assign primary extensions to synchronized end users, 'directory URI' for DNs will be automatically populated.

Directory URI field can be filled with 'mail' LDAP attribute or 'msRTCSIP-PrimaryUserAddress' LDAP attribute
 

c. Manually create directory URIs in DNs 
In this case, as a part of creating DNs, you can assign directory URI to the DN along with respective partition. Calling parties should contain 'directory URI' PT in their CSSes.

Step-2 Add a valid Fully Qualified Domain Name (FQDN) into the enterprise service parameter “Clusterwide Domain Configuration”

Step-3 Enable FQDN in SIP Requests for Contact Resolution - Device > Device Settings > SIP Profile > Use Fully Qualified Domain Name in SIP Requests 

Step-4 Enable Directory URI in Jabber Client XML file - true

CUCM and Instant Messaging & Presence Integration

IMP Configuration

1. 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.
2. Enable the following services:

• Cisco SIP Proxy
• Cisco Presence Engine
• Cisco Sync Agent
• Cisco Unified Presence XCP (Extensible Communications Platform) Connection Manager. This service is used to facilitate services communication.
• Cisco Unified Presence XCP Directory Service
• Cisco Unified Presence XCP Authentication Service

3. 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.
4. Navigate to System > Settings. Configure cluster ID Name  and Domain Name. The cluster ID name is just a descriptive name.
5. Navigate to System > CUCM Publisher. Configure CUCM Publisher IP, DB secret, AXL username, AXL password.
6. Navigate to System > Settings. Make sure to enable XMPP Client to IMP
7. Navigate to System > Service Parameters. Change the CUCM domain to match the IMP domain configured in step 4.
8. Navigate to Application > Legacy Settings > CCMIP Profile and add CUCM Groups to be used by clients. This defines the primary and secondary CUCM servers as desired. You can create multiple CCMIP profiles and assign different users to different profiles (e.g. Dubai users to DXBCCM01 as primary while Mumbai user to BOMCCM01 as primary).
9. Navigate to Presence > Gateways and add CUCM as gateway to be used for call control.
10. Navigate to Presence > Settings and select the SIP trunk created in CUCM. This is the trunk to be used by IMP for CUCM communication (SUBSCRIBE, NOTIFY, REFER, etc)
11. Navigate to Presence > Routing > Settings. Select the Preferred Proxy Listener as Default SIP Proxy TCP Listener.
12. Navigate to Messaging > Settings and enable instant messaging

Notes:

• No need to configure IMP in CUCM similar to old version of presence
• The moment IMP sync with CUCM, incoming and outgoing ACLs will be added in IMP allowing all CUCM servers.
• Although CCMIP Profile should be configured for Jabber prior to 8.x as per Cisco doc, practically it is needed for new versions as well.

CUCM Configuration

1. Create UC services to be used on IMP clients by navigating to User Management > User Settings > UC Service. You can create UC Service to point to IMP server, to point to CTI server, to point to Voice Mail Server and to point to Directory Server.
2. Create UC Profile to combine all the services to be used by IMP clients in one profile. Navigate to User Management > User Settings > UC Profile.
3. Assign UC Profile to end users who are using IMP clients. Also, you need to enable IMP capability for these users.
4. Configure SIP trunk pointing to IMP. This trunk should have a security profile with Accept Presence Subscription, Accept out-of-dialog Refer, Accept Unsolicited Notification, Accept Replaces Header enabled.
5. Create CSF devices for soft clients (CUPC and Jabber). Assign the owner user ID, primary phone, and tune options.
6. On the end user page, assign the CSF device to the controlled devices, assign primary extension, and assign CTI privileges (CTI Control Devices/CTI Enabled).