Export (0) Print
Expand All

Enable Remote Call Control (Office Communications Server 2007)

Lync Server 2010
 

Topic Last Modified: 2011-04-11

Remote call control enables users to control their desktop private branch exchange (PBX) phones by using Microsoft Lync 2010. If you deployed remote call control in your legacy environment and want to migrate it Microsoft Lync Server 2010, you need to perform the following tasks:

  1. Install a SIP/CSTA gateway and configure it to communicate with your PBX. You need to do this step when you deploy your Lync Server 2010 pilot pool. For details about SIP/CSTA gateways, see Deployment Tasks for Remote Call Control in the Planning documentation.

    noteNote:
    This step is a prerequisite to migration.
  2. After you merge your topology and migrate your policies and settings, configure Lync Server 2010 to route CSTA requests to the SIP/CSTA gateway. This step is a manual step that follows the automated migration. To configure routing for CSTA requests, do the following:

    • Remove legacy authorized host entries (known as trusted server entries in Lync Server 2010). If you are migrating users from your legacy deployment, ensure that you remove all existing authorized host entries that you created for the SIP/CSTA gateway before you configure new trusted application entries on the Lync Server 2010 pilot pool. For details about how to remove legacy authorized host entries, see Remove an Authorized Host Entry (Communications Server 2007) in this section.

    • Configure a static route for remote call control. You can configure a static route for individual pools that you want to support remote call control, or you can configure a global static route so that each pool that is not configured with a pool-level static route uses the global static route. For details about how to configure the static route, see Configure a Static Route for Remote Call Control in the Deployment documentation.

    • Configure a trusted application entry for remote call control on each pool that you want to support remote call control. For details about how to configure a trusted application entry, see Configure a Trusted Application Entry for Remote Call Control in the Deployment documentation.

  3. If you deployed a SIP/CSTA gateway that uses Transmission Control Protocol (TCP) to connect to Lync Server, define the IP address of the gateway in Topology Builder. For details about defining the IP address, see Define a SIP/CSTA Gateway IP Address in the Deployment documentation.

  4. Configure Lync 2010 users for remote call control by enabling remote call control and assigning a line server Uniform Resource Identifier (URI) and a line URI. When you migrate users from your legacy deployment to Lync Server, the remote call control settings are migrated along with the other user settings.

    For details about migrating users, see Move Multiple Users (Communications Server 2007 Migration). For details about configuring users for remote call control, see Enable Lync Users for Remote Call Control in the Deployment documentation.

  5. If you customized Address Book phone number normalization rules in your legacy deployment, you need to perform some manual tasks after the automated migration of policies and settings is complete to migrate the customized normalization rules. If you did not customize normalization rules, Address Book is migrated along with the rest of your topology. For details about manually migrating customized normalization rules, see Migrate Address Book.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft