Export (0) Print
Expand All

Required Lync Server Components for Devices

Lync Server 2010
 

Topic Last Modified: 2012-10-16

Before you deploy unified communications (UC) phones, ensure that the following required Lync Server components are in place.


The Device Update Web service, which is an automated way to update your IP phones, is installed with Web Services, on the Front End Server.

importantImportant:
In Lync Server Enterprise Edition, you may have multiple servers in the pool. For each instance of Web Services running on servers in a pool, there is a separate instance of Device Update Web service running in the pool. When you make a configuration change to the Device Update Web service, the changes are propagated to all the servers in that pool but not to servers in any other pool. For details about required configurations, see System and Infrastructure Requirements for Devices in the Planning documentation.

Enterprise Voice is the voice over IP (VoIP) solution in Lync Server that allows users to make calls and use rich communication and collaboration features, such as viewing enhanced presence information or location information for contacts in your organization’s address book.

Enterprise Voice must be enabled for each device user. To check whether Enterprise Voice is enabled for a user, in Lync Server Control Panel find the user, then view the user’s details. If the user is enabled for Enterprise Voice, the check box Enabled for Lync Server will be selected, and the Telephony drop down will have Enterprise Voice selected.

(Applies to Common area phones) Phones that are not associated with a specific user must be associated with an Active Directory contact object. Like user accounts, contact objects can be assigned policies and voice plans, thereby giving you a way to manage the device.

For details about creating contact objects for common area phones, see Configuring Common Area Phones in the Deployment documentation.

Dial plans, voice polices, and call routes must be set up for users. Dial plans are named sets of normalization rules that translate phone numbers for a named location, individual user, or contact object into a single standard (E.164) format, allowing UC device users to make calls to the public switched telephone network (PSTN). Voice policies are records that define call permissions for users, sites, or an entire organization and include various calling features that may be enabled or disabled as appropriate. Voice policies must be set up for device users. Call routes are rules that specify how Lync Server handles outbound calls from UC devices.

To verify whether dial plans, voice polices, and call routes are set up for users, or to set up or modify these user polices, see Planning Outbound Call Routing in the Planning documentation. For details about configuring policies for common area phones, see Configuring Common Area Phones in the Deployment documentation.

importantImportant:
We recommend that you also configure Exchange Unified Messaging (UM) and Lync Server to work together and that you enable users for Exchange UM call answering and Outlook Voice Access. For details, see the Exchange Server 2010 TechNet Library at http://go.microsoft.com/fwlink/p/?linkid=186202.

If you’re deploying phones from the new line of IP phones, you must enable personal identification number (PIN) authentication on Lync Server, and an appropriate PIN policy need to be in place. This allows authentication to be automatic when a user signs in on an Aastra 6721ip common area phone, Aastra 6725ip desk phone, HP 4110 IP Phone (common area phone), HP 4120 IP Phone (desk phone), Polycom CX500 IP common area phone, Polycom CX600 IP desk phone, or Polycom CX3000 IP conference phone. You set the PIN policy on the PIN Policy page of the Security group in Lync Server Control Panel. Also in Security, click Web Service, and verify that PIN authentication is enabled in the Global policy.

To do this is the Lync Server Management Shell, run the following command:

Set-CsWebServiceConfiguration -Identity "WebService:<FQDN of web service>" -UsePinAuth $true
 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft