Cisco Unified Presence, Release 7.x -- Validating Cisco Unified Presence and MOC Interoperability after an IP Address Change

From DocWiki

Revision as of 13:52, 29 March 2009 by Sicoughl (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main page: Cisco Unified Presence, Release 7.x

Perform the steps in this procedure only if you change the hostname or IP address on a Cisco Unified Presence server that was previously integrated with Microsoft LCS/OCS. You need to do this to ensure the Microsoft Office Communicator (MOC) server and clients reflect the correct Cisco Unified Presence IP address (after your changes) and the new FQDN.

Contents

Previous Topic


Before You Begin

Complete the Post-Change Task List.


Procedure
  1. Log out of any existing MOC client session that you may have running.
  2. Log in to the OCS or LCS server.
  3. Edit the Front End properties, in the following tabs on the OCS or LCS server:
Tab Action

Routing Tab

  1. Update the renamed Cisco Unified Presence server with its new FQDN and IP address.
  2. Change the `Next Hop' IP address of the wild carded Cisco Unified Presence domain to be the new Cisco Unified Presence IP address.

Host Authorization Tab

Ensure that the new Cisco Unified Presence IP address and new FQDN is listed as follows:

  • Outbound only - N
  • Throttle As Server -Y
  • Treat As Authenticated - Y

4. Right-click on the LCS/OCS Users, and edit as follows:

  1. Change the 'Server URI' to be the new Cisco Unified Presence FQDN.
  2. Click OK.

5. Stop the OCS/LCS Front End Service.

6. Restart the OCS/LCS Front End Service.

7. Log in to the MOC client, and confirm control of a Cisco device.


Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools