Cisco Unified Presence, Release 7.x -- How to Configure Microsoft Components for integration with Cisco Unified Presence

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified Presence, Release 7.x

Contents

Previous Topic

Line URI Configuration on Microsoft Active Directory

Before you configure the Line URI parameter on Microsoft Active Directory, note the following:

  • For the Line URI, we recommend that you use the format: tel:xxxx;phone-context=dialstring
    • xxxx also specifies the directory number that the CTI Manager reports to Cisco Unified Presence as the calling or called number when a call gets placed.
    • phone-context=dialstring enables the Microsoft Office Communicator client to control one of the devices that are associated with the directory number.
  • If you configure the device ID, the Microsoft Office Communicator client can only control that particular device; for example: tel:xxxx;phone-context=dialstring;device=SEP0002FD3BB5C5
  • If you configure the partition, the Microsoft Office Communicator client specifies the partition for the directory number; for example: tel:xxxx;phone-context=dialstring;device=SEP0002FD3BB5C5;partition=myPartition
  • Cisco Unified Presence will control a line appearance, overriding any line appearance that the user may have previously selected, if the following characteristics apply:
    • if the Line URI contains either the device ID parameter, the partition parameter, or both parameters, and
    • if the user is uniquely identified by a line appearance
  • If you do not configure the device ID in the Line URI, the CTI Gateway determines the devices that are associated with the line Directory Number (DN). If only one device is associated with the line DN, the CTI Gateway uses that device.
  • If you do not configure the device ID in the Line URI and two devices are associated with the line DN (shared line), the CTI Gateway uses the following rules to select a device:
    • If one of the two devices is Cisco IP Communicator and its status is registered, CTI Gateway uses that device.
    • If one of the two devices is Cisco IP Communicator, but it is not registered, CTI Gateway uses the alternate hard device.
    • If more than two devices are associated with a line DN, you must specify the desired device in the Line URI.


Related Topics



User Authentication on Cisco Unified Presence

When configuring the SIP URI on Microsoft Active Directory, consider how Cisco Unified Presence performs the user authentication checks. The user authentication logic is as follows:

  1. Cisco Unified Presence checks if the Microsoft Office Communicator (sign in) user ID matches the Cisco Unified Communications Manager user ID. If Cisco Unified Presence cannot find a match:
  2. Cisco Unified Presence checks if the Microsoft Office Communicator user email (the From header) matches the Cisco Unified Communications Manager user email. If Cisco Unified Presence cannot find a match:
  3. Cisco Unified Presence checks if the Microsoft Office Communicator user email matches the ocsPrimaryAddress value of a Cisco Unified Communications Manager user.


For example, a user Joe has the Microsoft Office Communicator user ID joe@someCompany.com. The From header in the SIP INVITE is sip:joe@someCompany.com.


In this case, Cisco Unified Presence checks the following:

  • If there is a user in the Cisco Unified Communications Manager database whose user ID is `joe'. If this user ID does not exist:
  • If there is a user in the Cisco Unified Communications Manager database whose mail is `joe@someCompany.com'. If this mail does not exist:
  • If there is a user in the Cisco Unified Communications Manager database whose ocsPrimaryAddress is `sip:joe@someCompany.com'.
Related Topics



Configuring Microsoft Active Directory

Before You Begin
  • Read the topic describing Line URI configuration on Microsoft Active Directory.
  • Read the topic describing the user authentication checks on Cisco Unified Presence.


Procedure

1. From the Microsoft Active Directory application window, add a user name and the telephone number that are associated with each particular user.

2. For each of in the users that you added, open the Properties window on Microsoft Active Directory and configure the following parameters:

  • Enable live communications.
  • Enter the SIP URI.
  • Enter the Microsoft OCS server name or pool.


Caution! Ensure the OCS server name or pool name does not contain the underscore character.
  • Check Remote User Access.
  • Check Remote Call Control.
  • Enter the Line URI value. When entering this value, note the following, enter the Remote Call Control SIP URI; for example, sip:8000@my-cups.my-domain.com, where my-cups.my-domain.com specifies the FQDN of the Cisco Unified Presence server that you configured for this integration.


Troubleshooting Tips
  • The SIP URI that you enter on Microsoft Active Directory must match the static route URI that you define when you are configuring static routes on Microsoft OCS.


Related Topics


What To Do Next

Microsoft OCS Configuration Overview



Microsoft OCS Configuration Overview

Note: This topic provides a brief outline of the configuration required on Microsoft OCS for this integration. A detailed description of Microsoft OCS configuration is out of the scope of this module. Please refer to the Microsoft OCS documentation for this information.


Make sure that the Microsoft OCS server is properly installed and activated. Make sure that the following items are configured on Microsoft OCS:

  • Certificate configuration
  • Static Routes
  • Authorized Host
  • Domain Name Server
  • Pool Properties
  • Server Properties
  • Pool Users
  • User Configuration
  • Microsoft Office Communicator (MOC) Configuration


Troubleshooting Tips

If you integrate Cisco Unified Presence with Microsoft LCS 2005, when you configure the static routes on LCS, you must configure all users for remote call control by defining the user value of the static route as '*' (star symbol). Note that if you integrate with Microsoft OCS, the user value of the static route is '*' by default and this value is not configurable.

Related Topics
http://office.microsoft.com/en-us/communicationsserver/FX101729111033.aspx

Rating: 0.0/5 (0 votes cast)

Personal tools