IM and Presence Release 8.5(2) or later supports interdomain
federation with Microsoft Lync. For
IM and Presence Release 8.5(2) or later, any reference to
interdomain federation with OCS also includes Microsoft Lync, unless explicitly
stated otherwise.
Cisco Adaptive Security Appliance acts as a TLS proxy between the IM and Presence and the foreign server. This allows Cisco Adaptive Security Appliance to proxy TLS messages on behalf of the server (that initiates the TLS connection), and route the TLS messages from the proxy to the client. The TLS proxy decrypts, inspects and modifies the TLS messages as required on the incoming leg, and then re-encrypts traffic on the return leg.
Note
Before configuring the TLS proxy, you must configure the Cisco Adaptive Security Appliance security certificates between Cisco Adaptive Security Appliance and IM and Presence, and Cisco Adaptive Security Appliance and the foreign server. Complete the procedures in the following sections to accomplish this:
This section lists the access list configuration requirements
for a single
IM and Presence deployment.
Note
For each access list,
you must configure a corresponding class-map, and configure an entry in the
policy-map global policy.
You can check the peer auth listener port on
IM and Presence by selecting
Cisco Unified CM IM and Presence
Administration > System > Application
Listeners.
Deployment Scenario:
AnIM and Presence server federating with one or more foreign domains
Configuration Requirement:
Configure the following two access lists for each
foreign domain that
IM and Presence is federates with:
Configure an access
list to allow
IM and Presence to send messages to the foreign domain on port 5061.
Configure an access
list to allow
IM and Presence to receive messages from the foreign domain on port
5061, or if you use
Cisco Adaptive Security Appliance Release 8.3, the actual port that
IM and Presence listens on for SIP federation (check the peer auth
listener port on
IM and Presence).
Configuration Example:
access-list ent_cup_to_foreign_server extended permit tcp host <routing cup private address> host <foreign public address> eq 5061
Cisco Adaptive Security Appliance Release 8.2:
access-list ent_foreign_server_to_cup extended permit tcp host <foreign public address> host < CUP public address> eq 5061
In the access list above 5061 is the port that
IM and Presence listens on for SIP messaging. If
IM and Presence listens on port 5062, specify 5062 in the access
list.
Deployment Scenario:
Intercluster deployment
(This also applies to a multi-node deployment)
Configuration Requirement:
Configure the following two access lists for each
intercluster
IM and Presence server.
Configure an access
list to allow
IM and Presence to send messages to the foreign domain on port 5061.
Configure an access
list to allow
IM and Presence to receive messages from the foreign domain on the
arbitrary port 5061, or if you use
Cisco Adaptive Security Appliance Release 8.3, the actual port that
IM and Presence listens on for SIP federation (check the peer auth
listener port on
IM and Presence)
Configuration Example:
access-list ent_intercluster_cup_to_foreign_server extended permit tcp host <intercluster cup private address> host <foreign public address> eq 5061
Cisco Adaptive Security Appliance Release 8.2:
access-list ent_foreign_server_to_intercluster_cup extended permit tcp host <foreign public address> host <cup public address> eq <arbitrary port>
Cisco Adaptive Security Appliance Release 8.3:
ent_foreign_server_to_intercluster_cupextended permit tcp host <foreign public address> host <cup private address> eq 5061
In the access list above 5061 is the port that IM and Presence listens on for SIP messaging. If IM and Presence listens on port 5062, specify 5062 in the access list.
For this integration, you need to create two TLS proxy
instances. The first TLS proxy handles the TLS connections initiated by
IM and Presence, where
IM and Presence is the client and the foreign domain is the server. In this
case, the
Cisco Adaptive Security Appliance acts as the TLS server facing the "client" which is
IM and Presence. The second TLS Proxy handles the TLS connections initiated
by the foreign domain, where the foreign domain is the client and
IM and Presence is the server.
The TLS proxy instance defines
"trustpoints" for both the server and the client. The direction
from which the TLS handshake is initiated determines the trustpoint defined in
the server and client commands:
If the TLS handshake
initiates from
IM and Presence to the foreign domain, the server command specifies
the trustpoint that contains the
Cisco Adaptive Security Appliance self-signed certificate. The client command specifies the
trustpoint that contains the
Cisco Adaptive Security Appliance certificate that is used in the TLS handshake between
Cisco Adaptive Security Appliance and the foreign domain.
If the handshake initiates
from the foreign domain to
IM and Presence, the server command specifies the trustpoint that
contains the
Cisco Adaptive Security Appliance certificate the TLS handshake uses between
Cisco Adaptive Security Appliance and the foreign domain. The client command specifies the
trustpoint that contains the
Cisco Adaptive Security Appliance self-signed certificate.
Associate each of your access lists with the TLS proxy instance
that the class map uses. The TLS proxy you select depends on whether the
class-map is for messages from
IM and Presence to a foreign domain, or from a foreign domain to
IM and Presence.
In the example below, the access list for messages sent from
IM and Presence to a foreign domain is associated with the TLS proxy
instance for TLS connections initiated by
IM and Presence called
"ent_cup_to_foreign":
In the example below, the access list for messages sent from a
foreign domain to
IM and Presence is associated with the TLS proxy instance for TLS
connections initiated by the foreign server called "ent_foreign_to_cup":
If you are have an intercluster
IM and Presence deployment, configure a class map for each
IM and Presence server, and associate this with the appropriate
access-list for the server that you defined previously, for example:
class-map ent_second_cup_to_foreignmatch access-list ent_second_cup_to_foreign
class-map ent_foreign_to_second_cup
match access-list ent_foreign_to_second_cup
Using the policy map command, you need to enable the TLS
proxy for each class map you created in the previous section.
Note
You cannot use a High security sip-inspect policy map on
Cisco Adaptive Security Appliance for a federated deployment because the configuration will
fail. You must use a Low/Medium security policy map.
Configure Cisco Adaptive Security Appliance for an intercluster deployment
For an intercluster IM and Presence deployment, you must perform the following configuration on the Cisco Adaptive Security Appliance for each additional IM and Presence server.
Procedure
Step 1
Create an additional access list for the IM and Presence server.
Step 2
Generate and import the Cisco Adaptive Security Appliance security certificate onto the IM and Presence server.
Step 3
Generate and import the IM and Presence security certificate onto Cisco Adaptive Security Appliance.