Topic Last Modified: 2010-07-14
When planning to deploy IP phones in an enterprise, use this checklist to guide you through the process.
Confirm Prerequisites
- Start Web Services. (See Start or Stop
Communications Server Services, in the Communications Server
Control Panel Help.)
- Enable Enterprise Voice for users. (See Deploying the Enterprise
Voice Workload, in the Deployment Guide.)
- Deploy the mediation server/gateways for telephony. (See
Deploying the
Enterprise Voice Workload, in the Deployment Guide)
- Set up your network for external access, if you’re allowing it.
(See System and
Infrastructure Requirements for Devices, in the Planning
Guide.)
- Identify and purchase the devices that you want to deploy. (See
Choosing New
Devices, in the Planning Guide.)
- Identify the information that users can read to guide them
through setup, and use and the medium through which the information
will be delivered. (See your UC Connect site for end user training
and documentation.)
Perform Pre-Deployment Tasks
- Create the required DNS and DHCP records. (See System and
Infrastructure Requirements for Devices, in the Planning
Guide.)
- Set up or adjust dial plans, voice policies, and outbound call
routes for users. (See Create a Dial Plan
and Configuring
Voice Policies, PSTN Usage Records, and Voice Routes, in the
Communications Server Control Panel Help.)
- Configure common area phones, if deploying them. (See Provisioning
Phones.)
- Set up test devices. (See Add a Device to Test
Update Functionality, in the Communications Server Control
Panel Help.)
- Download the latest firmware updates from Microsoft.com, and
deploy them to test devices. (See View Software Updates
for Devices in Your Organization, in the Communications Server
Control Panel Help.)
Provision and Prepare Users
- Run a script to verify that users are enabled correctly for
Enterprise Voice, if you’re using it. For a list of all enabled
users, at the command prompt, type
Get-CsUser | Where-Object {$_.EnterpriseVoiceEnabled –eq $True} | Select Identity, EnterpriseVoiceEnabled
. For a list of all users that includes information about which users are enabled, at the command prompt, typeGet-CsUser | select DisplayName, EnterpriseVoiceEnabled
.
- Set the in-band policies, with logging levels, for devices.
(See Modify
Settings for Log Files of Device Update Activity, in the
Communications Server Control Panel Help.)
- Assign user PIN or credentials. The user's PIN can be
configured by an administrator or set by the user. An administrator
can set the PIN from Communications Server 2010 Control Panel or
from Office Communications Server Management Shell (Set
-CSClientPIN). (See Set-CsClientPin, in the RTCCmdlets.chm,
or, Set a User's
Dial-in Conferencing PIN in in the Communications Server
Control Panel Help.) A user can set the PIN by visiting the Dial-in
Conferencing Settings and PIN Management page.
- Ensure that users can access the end-user documentation that
you are providing. (See the Devices section on your UC Connect site
for end user training and documentation.)
Set up Devices
- Give the user the device and documentation. (See the Devices
section on your UC Connect site for end user training and
documentation.)
- Check call detail recording (CDR) to make sure that the user
has received and made calls and successfully logged in, while in
the corporate environment. (See Call Detail Recording
(CDR) Database Schema, in the OCS_14_ITPro.chm.)
- Check CDR to make sure that the user has successfully logged
in, while in the corporate environment.
Support and monitor the deployment
- Use Quality of Experience (QoE) reports. (See Quality of Experience
(QoE) Database Schema, in the OCS_14_ITPro.chm.)
- Generate IP Phone Inventory reports. (In Monitoring Server
Reports).
- Use other monitoring tools, including CDR reports. (See
Call Detail
Recording (CDR) Database Schema, in the OCS_14_ITPro.chm.)
Note: |
---|
Note that this guide covers how to provision and prepare users on the Polycom CX600, Polycom CX500, Aastra 6725ip, and Aastra 6121ip phone. For more information on the checklist, see Planning for Devices, in the Planning Guide. |