Deploying Remote Call Control



Configuring Lync 2010 Remote Call Control
This segment defines the deployment tasks that you must ample to allow remote call control for end users in your Lync 2010 infrastructure.

#1: Install/Configure the SIP/CSTA Gateway to Connect with Your PBX

You must install at least one SIP/CSTA gateway that can connect to both Lync and the existing (PBX) in your infrastructure in order to offer remote call control features to your end users. A SIP/CSTA gateway is a gateway among SIP and a computer-supported telecommunications application (CSTA). Whether you install multiple-gateways or single, each user can be configured with only one gateway or PBX. If your existing PBX does not have a SIP/CSTA interface, confirm you deploy a SIP/CSTA gateway that can support the PBX, including support for proprietary PBX vendor-specific signaling protocols.

When you are ready to deploy a SIP/CSTA gateway that can integrate with Lync 2010 for remote call control, also consult with your gateway vendor or the vendor’s gateway documentation regarding the syntax required by the gateway for the following information:

The preceding settings are required during user configuration and must be specified as expected by the gateway to route and connect to the PBX properly.


#2: Configure Lync 2010 to Route CSTA Requests to the SIP/CSTA Gateway

You must create static routes on Lync pools to the destination address (server URI) of all SIP/CSTA gateways in your deployment to which you intend to route remote call control requests. You must also create a trusted application entry that corresponds to each destination address. When you designate the gateway as a trusted application, it is given trusted status to run as part of the Lyncinfrastructure even though it is developed by a third party (and runs what is referred to as an external service because it is a service that is not a built-in part of the product). Finally, if Lync will connect to the SIP/CSTA gateway using a Transmission Control Protocol (TCP) connection instead of a Transport Layer Security (TLS) connection, you must also define the gateway IP address by using Topology Builder.

 

#3: Configure Lync 2010 End users for Remote Call Control

After end users have been enabled for Lync, you can use MS Lync 2010 Control Panel or Lync Management Shell to enable them for remote call control. It is during this deployment step that you assign each user a line server URI and a line URI. The line server URI is the SIP URI of the SIP/CSTA gateway that you plan to assign to the user. The line URI is the unique phone number assigned to the user.

 

#4: Define the Lync Phone Number Normalization Rules

In remote call control scenarios, Lync uses phone number normalization rules to convert phone numbers it receives from the SIP/CSTA gateway to E.164 format. Phone numbers must be in this standardized format for certain remote call control features to function properly. Remote call control uses the same phone number normalization rules that you configure for Address Book Service phone number normalization, which are different from the phone number normalization rules used for Enterprise Voice.