Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1)
Configure IM and Presence to integrate with Interdomain Federation capability of Intradomain Lync/OCS/LCS
Download this chapter
Configure IM and Presence to integrate with Interdomain Federation capability of Intradomain Lync/OCS/LCSConfigure IM and Presence to integrate with Interdomain Federation capability of Intradomain Lync/OCS/LCS
Download the complete book
Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1) Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1) (PDF - 4 MB)
 Feedback

Configure IM and Presence to integrate with Interdomain Federation capability of Intradomain Lync/OCS/LCS

Microsoft Lync/OCS/LCS supports Interdomain Federation with remote enterprises or public IM providers. This Interdomain Federation capability is still available to Microsoft Lync or Microsoft Office Communicator users when Partitioned Intradomain Federation is configured between Lync/OCS/LCS and IM and Presence.

Furthermore, it is possible to configure IM and Presence so that users who migrate to an IM and Presence supported client can still use the Interdomain Federation capability that is configured on Lync/OCS/LCS.

This chapter describes the steps to integrate IM and Presence with Lync/OCS/LCS Interdomain Federation capability.

When Partitioned Intradomain Federation with Lync/OCS/LCS is enabled, it is also possible to configure both SIP-based and XMPP-based Interdomain Federation to remote domains on IM and Presence. However, this federation capability is available to users on IM and Presence supported clients only. For information about configuring Interdomain Federation on IM and Presence, see the document Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager.

Related Information

Configuration of remote domain as a SIP Federation domain

Because all requests to the remote domain are routed through the SIP interface between IM and Presence and Lync/OCS/LCS, you must first configure the remote domain on IM and Presence as a Lync/OCS/LCS SIP Federation domain. You must perform this procedure for each remote domain.

See the Adding a SIP Federated Domain procedure in the Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager for detailed instructions on how to configure a SIP Federation domain. Select the following options when you configure a SIP Federation domain:

  • For Domain Name, enter the remote domain.
  • For Integration Type, select Inter-domain to OCS/Lync
  • Ensure that Direct Federation is checked.

Note

If you have a multicluster deployment, you must perform this procedure on each cluster. These settings are cluster-wide; therefore you need to set them only on the IM and Presence publisher node within any given cluster.

What To Do Next

Configure static route for remote domain

Related Information

Configure static route for remote domain

When you integrate IM and Presence with Lync/OCS/LCS Interdomain Federation capability, you must configure static routes on IM and Presence for each remote domain.

For Standard Edition Lync/OCS/LCS, the static routes must point to the IP address of a specific Standard Edition server.

For Enterprise Edition Lync/OCS/LCS, the static routes must point to a specific Enterprise Edition front-end server or front-end load balancer (if you route through a Lync/OCS/LCS front-end load balancer).

If you are using a Lync/OCS/LCS front-end load balancer, note the following:

  • IM and Presence has been tested with the Cisco Application Control Engine (ACE) as the Lync/OCS/LCS front-end load balancer.
  • Other load balancers can be used in place of ACE; see the following URL for a list of alternative load balancers: http:/​/​technet.microsoft.com/​en-us/​office/​ocs/​cc843611. However, it is your responsibility to ensure that those load balancers are deployed and managed correctly. Cisco does not support the configuration of static routes to point to such load balancers.
  • In deployments in which ACE is not the configured front-end load balancer, Cisco recommends that you configure static routes to bypass the front-end load balancer.

For High Availability purposes, you can configure additional backup static routes for each remote domain. The backup route has a lower priority and is used only if the next hop address of the primary static route is unreachable.


Note

If you have a multicluster deployment, you must perform this procedure on each cluster. These settings are cluster-wide; therefore you need to set them only on the IM and Presence publisher node within any given cluster.

Procedure
    Step 1   Select Cisco Unified CM IM and Presence Administration > Presence > Routing > Static Routes.
    Step 2   Select Add New.
    Step 3   Enter the destination pattern value so that the domain, or FQDN, is reversed. For example, if the domain is remote.com, the Destination Pattern value must be .com.remote
    Step 4   Select domain for the Route Type.
    Step 5   In the Next Hop field, enter the IP address of the next hop.
    Step 6   Set the Next Hop Port and the Protocol Type as follows:
    • For TLS Encryption:
      • Next Hop Port number is 5061
      • Protocol Type is TLS
    • For TCP:
      • Next Hop Port number is 5060
      • Protocol Type is TCP
    Step 7   Enter the Priority value as follows:
    • For primary static routes, enter the default Priority value of 1.
    • For backup static routes, enter a Priority value of greater than 1. (The lower the value, the higher the priority of the static route.)
    Step 8   Select the default values for all other parameters.
    Step 9   Select Save.
    Related Information

    Remove IM and Presence integration with Lync/OCS/LCS Interdomain Federation capability

    At some stage, you may want to configure IM and Presence for Interdomain Federation with one of the remote domains that you previously configured on Lync/OCS/LCS. The most likely scenario for this is when all Microsoft Lync or Microsoft Office Communicator users have been migrated to IM and Presence. At this point, the Lync/OCS/LCS deployment can be shut down, and any Interdomain Federation capability can instead be enabled directly from IM and Presence.

    To remove IM and Presence integration with Lync/OCS/LCS Interdomain Federation capability, you must complete the following procedures:

    • Remove the static route to the remote domain
    • Remove all SIP Federation domains

    Remove static route for remote domain

    Procedure
      Step 1   Select Cisco Unified CM IM and Presence Administration > Presence > Routing > Static Routes.
      Step 2   Select the appropriate static route from the list provided. If no list is shown, select Find.
      Step 3   Select Delete Selected.
      Step 4   Select OK to confirm the deletion.
      What to Do Next

      Remove the SIP Federation domain

      Remove the SIP Federation domain


      Note

      If you have a multicluster deployment, you must perform this procedure on each cluster. These settings are cluster-wide; therefore you need to set them only on the IM and Presence publisher node within any given cluster.

      Procedure
        Step 1   Select Cisco Unified CM IM and Presence Administration > Presence > Inter-Domain Federation > SIP Federation.
        Step 2   Select the domain from the list provided. If no list is shown, select Find.
        Step 3   Select Delete Selected.
        Step 4   Select OK to confirm the deletion.
        What to Do Next

        After you remove the static route to the remote domain and remove the SIP Federation domain, you can proceed to configure IM and Presence for Interdomain Federation with the remote domain. See Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager for more information.