User and device configuration on Cisco Unified Communications Manager
Before you configure
Cisco Unified Communications Manager for integration with
the IM and Presence Service, make sure that the following user and device configuration
is completed on
Cisco Unified Communications Manager.
This procedure
is only applicable if you are integrating with
Cisco Unified Communications Manager version 6.0 or a
later release.
We recommend
that you set an expiration date on the credential policy for users. The only
type of user that does not require a credential policy expiration date is an
Application user.
Cisco Unified Communications Manager does not use the credential policy if you are using an LDAP
server to authenticate your users on
Cisco Unified Communications Manager.
Configure the users, and associate a device with
each user
If you are
planning to deploy
Cisco Unified Personal Communicator, make sure that the user ID value is unique for each
user. The user ID is converted into the softphone device name, and if two users
have the same softphone device name
Cisco Unified Personal Communicator will not be able to derive the softphone device name,
and as a result, will not function properly.
Cisco Unified Communications Manager Administration > User Management > End User.
Associate a user with a line appearance
This procedure
is only applicable to
Cisco Unified Communications Manager version 6.0 or a
later release.
This procedure
is only applicable if you are planning to deploy
Cisco Unified Personal Communicator. To enable
Cisco Unified Personal Communicator desk phone control, you must add the
Cisco Unified Personal Communicator users to a CTI-enabled user group.
Cisco Unified Communications Manager Administration > User Management > User Group
Note
Note that because menu options and parameters may vary per
Cisco Unified Communications Manager releases, see the
Cisco Unified Communications Manager documentation
appropriate to your release.
Configure Inter-Presence Group Subscription parameter
You enable the Inter-Presence Group Subscription parameter to
allow users in one Presence Group to subscribe to the availability information
for users in a different presence group.
Restriction
You can only enable the Inter-Presence Group Subscription
parameter when the subscription permission for the default Standard Presence
Group, or any new Presence Groups, is set to
Use System Default. To configure Presence
Groups, select
Cisco Unified Communications Manager
Administration > System > Presence
Groups.
Procedure
Step 1
Select
Cisco Unified Communications Manager
Administration > System > Service
Parameters.
Step 2
Select
Cisco Unified Communications Manager server from the Server menu.
Step 3
Select Cisco CallManager
from the Service menu.
Step 4
Select
Allow Subscription
for Default Inter-Presence Group Subscription in the
Clusterwide Parameters (System - Presence) section.
Step 5
Select
Save.
Troubleshooting Tips
You no longer have to manually add
the IM and Presence Service as an Application Server on
Cisco Unified Communications Manager:
When you add or remove a node on the
system topology management GUI, the node is automatically added to or removed from
the Application Server list on
Cisco Unified Communications Manager.
When you configure the
Cisco Unified Communications Manager publisher on
IM and Presence from
Cisco Unified CM IM and Presence
Administration > System > CUCM
Publisher, the
IM and Presence node is automatically added to the Application
Server list on
Cisco Unified Communications Manager.
SIP Trunk configuration on Cisco Unified Communications Manager
Note
The port number that you configure for the SIP Trunk differs depending on the version of the IM and Presence Service that you are deploying. For IM and Presence release 9.0(x) and later, configure the port number 5060 for the SIP Trunk.
You only configure one SIP trunk between a
Cisco Unified Communications Manager cluster and an
IM and Presence cluster. After you configure the SIP trunk, you must assign
that SIP trunk as the IM and Presence Publish Trunk on
Cisco Unified Communications Manager by selecting
Cisco Unified Communications Manager
Administration > System > Service
Parameters.
If DNS SRV is an option in your network, and you want
availability messaging to be shared equally among all the servers used for
availability information exchange, you must configure the SIP trunk for the
IM and Presence server with a DNS SRV record of the
IM and Presence publisher and subscriber servers. You must also configure
the Presence Gateway on the
IM and Presence server with a DNS SRV record of the
Cisco Unified Communications Manager subscriber nodes.
Before You Begin
Configure the SIP Trunk
security profile on
Cisco Unified Communications Manager.
Read the Presence Gateway
configuration options topic.
In the SIP Information section at the bottom of the window,
configure the following values:
In the Destination Address field, enter the dotted IP address,
or the FQDN (Fully Qualified Domain Name), which can be resolved by DNS and must match the SRV Cluster Name configured on the IM and Presence server. For more information, see Configure cluster-wide IM and Presence address
Check
the Destination Address is an SRV
if you are configuring a multi-node deployment. In this scenario, Cisco Unified Communications Manager performs a DNS SRV record query to resolve the name, for example _sip._tcp.hostname.tld. If you are configuring a single-node deployment, leave this checkbox unchecked and Cisco Unified Communications Manager will perform a DNS A record query to resolve the name, for example hostname.tld.
In both scenarios, the Cisco Unified Communications SIP trunk Destination Address must resolve by DNS and match the SRV Cluster Name configured on the Cisco Unified Presence server. For more information, see Configure cluster-wide IM and Presence address.
Enter
5060 for the Destination Port.
Select
Non Secure SIP Trunk Profile from the SIP
Trunk Security Profile menu.
Select
Standard SIP Profile
from the SIP Profile menu.
Step 10
Select
Save.
Troubleshooting Tip
If you modify the DNS entry of the Publish SIP Trunk SRV record by
changing the port number or IP address, you must restart all devices that
previously published to that address and ensure each device points to the
correct
IM and Presence contact.