[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-15

Before you deploy UC phones, ensure that the following required Microsoft Communications Server 2010 components are in place.

Web Services

The Device Update service, which is an automated way to update your IP phones, is installed with Web Services, on the Front End Server. To check whether Web Services has been started or to start Web Services, see Start or Stop Communications Server Services, in the Communications Server Control Panel Help.

In Communications Server 2010 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 service running in the pool. When you make a configuration change to the Device Update service, the changes are propagated to all the servers in that pool but not to servers in any other pool. For information about required configurations, see System and Infrastructure Requirements for Devices.

Enterprise Voice

Enterprise Voice is the voice over IP (VoIP) solution in Communications Server 2010 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 the Control Panel find the user, then view the user’s details. The check box Enabled for Communications Server will be checked, and the Telephony drop down will have Enterprise Voice selected, if the user is enabled for Enterprise Voice.

Contact Objects

(Common area phones and analog devices only) 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 information about creating contact objects for common area phones and analog devices, see Appendices: Planning for Devices.

When creating a contact object for an analog device for example, when using the New-CSAnalogDevice command, make sure to correctly specify the correct categorization of the analog device. This needs to be a fax machine, such as fax, modem, TTY or not (in other words, a voice device). The correct designation of fax impacts how the call will be routed.

Dial Plans, Voice Polices, and Outbound Call Routes

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 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 Communications Server 2010 handles outbound calls from UC devices.

To check whether dial plans, voice polices, and call routes are set up for users, or to set up or modify these user polices, see Configuring Voice Dial Plans, Policies, and Outbound Call Routes_NIB, in the Communications Server Control Panel Help. For information about configuring polices for common area phones or analog devices, see Appendices: Planning for Devices..

We recommend that you also configure Exchange Unified Messaging (UM) and Communications Server 2010 to work together and that you enable users for Exchange UM call answering and Outlook Voice Access. For more information, see the Exchange Server 2010 product documentation.

PIN Authentication and Policy

If you’re deploying phones from the new line of IP phones, you must enable PIN authentication on Communications 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, Polycom CX600, Polycom CX500, or Polycom CX3000 phone. To set the PIN policy, in the PIN Policy header of the Security tab of Communications Server Control Panel. Also on the Security tab, select the Web Service header, and make sure that the PIN authentication is enabled in the Global policy.