A user can’t sign in on an analog device, so the device cannot be associated to a user. Creating a new contact object in Active Directory for an analog device gives you a way to manage the device, even though the device isn’t associated with an individual user. This is because, like a user account, a contact object can be assigned policies and voice plans.

To create a new instance of an analog device that you can manage with Microsoft Communications Server 2010, use the New-CsAnalogDevice cmdlet. For example:

New-CsAnalogDevice -LineUri tel:+14255556001 -DisplayName "Building 14 Receptionist" -RegistrarPool redmond-Cs-001.litwareinc.com -AnalogFax $False -Gateway 192.168.0.240 -OU "ou=Telecommunications,dc=litwareinc,dc=com"

This command creates a new analog device with the phone number (LineUri) 1-425-555-6001. (Note that the phone number must be specified using the E.164 format.) In addition to the -LineUri parameter, the other parameters used in this command are -DisplayName (to set the Active Directory display name of the device); -RegistrarPool (to specify the registrar pool); -AnalogFax (set to $False, to indicate that this is a phone and not a fax machine); -Gateway (set to the IP address of the gateway); and -OU (the distinguished name of the Active Directory OU where the device's contact object should be created).

For more information about creating contact objects for analog devices, run Get-Help New- CsAnalogDevice –Full | more from the Communications Server Management Shell.

If you are deploying many analog devices, you may want to write a Windows PowerShell script to create multiple new objects at the same time by using a table as an input for batch processing. Include entries for phone number, location, voice policy, and any other applicable policies such as voice policy and other settings that you want applied.

Note:
For more information about the Shell and individual cmdlets, see the RTCCmdlet.chm.

Creating specific policies for analog devices is optional. If you do not create a new policy for an analog device, the device will automatically use the policy defined for the site that the device contact object is homed on. If no site policy exists, the global policy will be used. But if your organization has specific requirements for analog devices, use the Shell cmdlets described below to create the voice and conferencing policies (these policies most relevant to analog devices) that will apply to the analog device account being created. Create a policy for each usage scenario.

If you create a new policy or want to use an existing per-user policy, you must grant that policy to any contact objects (phones) that you want that policy applied to. To do this, call the Grant- cmdlet of the policy. For example, to grant the client policy that we created earlier in this section to the phone created in Step 1, run the following command:

Grant-CsClientPolicy –Identity "Building 30 Lobby" -PolicyName ADClientPolicy

Note:
For more information about granting client policies, run Get-Help Grant-CsClientPolicy –Full | more, from the Shell. For information about additional polices, see the RTCCmdlet.chm.

Voice Policy

To create a new voice policy, use the New-CSVoicePolicy cmdlet. For example:

New-CsVoicePolicy -Identity ADvoicepolicy –PstnUsages @{add="Internal","Local"} -allowsimulring $False -Allowcallforwarding $False -Name ADvoicepolicy -EnableDelegation $False -EnableTeamCall $FALSE -EnableCallTransfer $FALSE

This example creates a new voice policy with the Identity ADvoicepolicy. This new policy sets several properties that would most likely apply to analog devices. It turns off simultaneous ring (-AllowSimulRing $False), which makes it so that calls to the phone that this policy is applied to cannot simultaneously ring on another phone, such as a mobile phone. It also turns off call forwarding (-AllowCallForwarding $False), call delegation (-EnableDelegation $False), the ability to transfer calls (-EnableCallTransfer $False), and the ability to set up a team of users whose phones will ring when this phone does (-EnableTeamCall $False).

Note:
As shown in the preceding example, the following voice policy settings are recommended for analog devices: AllowCallForwarding : False EnableDelegation : False EnableTeamCall : False EnableCallTransfer : False To see a list of all available voice policy properties and their descriptions, run Get-Help New-CsVoicePolicy –Full from the Shell.

Conferencing Policy

To create a new conferencing policy, use the New-CSConferencingPolicy cmdlet. For example:

new-csconferencingpolicy -identity ADconferencingpolicy -allowIPAudio $false -allowIPvideo $False -EnableFileTransfer $False -EnableP2PFileTransfer $False -EnableDataCollaboration $False

This is an example of a conferencing policy with settings that could be applicable to an analog device. This example creates a conferencing policy with an Identity ADconferencingpolicy. This new policy disables the following:

• The ability to use computer audio in a meetings (-AllowIPAudio $False)
  
  
• The ability to use computer video (-AllowIPVideo $False)
  
  
• The ability to transfer files as part of the conference (-EnableFileTransfer $False)
  
  
• Peer-to-peer file transfers during the conference (-EnableP2PFileTransfer)
  
  
• The ability to join the conference over the Internet (-EnableDataCollaboration $False)
  
  

Note:

The following conferencing policy settings are typically set for analog devices, but these and others can be changed depending on enterprise needs:AllowIPAudio : False AllowIPVideo : False EnableFileTransfer : False EnableP2PFileTransfer : False EnableDataCollaboration : False To see a list of all available voice policy properties and their descriptions, run Get-Help New-CsConferencingPolicy –Full | more from the Shell.