Share via

  • Article

Create Contact Objects for Hosted Exchange UM

 

Topic Last Modified: 2012-01-24

The following procedure explains how to create Auto Attendant (AA) or Subscriber Access (SA) contact objects for hosted Exchange Unified Messaging (UM).

For details, see Hosted Exchange Contact Object Management in the Planning documentation.

For details about configuring contact objects, see the Lync Server Management Shell documentation for the following cmdlets:

  • New-CsExUmContact

  • Set-CsExUmContact

Important

Before Lync Server contact objects can be enabled for hosted Exchange UM, a hosted voice mail policy that applies to them must be deployed. For details, see Hosted Voice Mail Policies.

To create AA or SA contact objects for hosted Exchange UM

  1. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

  2. Run the New-CsExUmContact cmdlet to create any contact objects required for your deployment. For example, run the following to create an AA and an SA contact object:

    New-CsExUmContact -SipAddress "sip:exumaa1@fabrikam.com" -RegistrarPool "RedmondPool.litwareinc.com" -OU "HostedExUM Integration" -DisplayNumber "+14255550101" -AutoAttendant $True

New-CsExUmContact -SipAddress "sip:exumsa1@fabrikam.com" -RegistrarPool " RedmondPool.litwareinc.com" -OU "HostedExUM Integration" -DisplayNumber "+14255550101"

    These examples set the following parameters:

    • SipAddress specifies the SIP address of the contact object. This must be an address that has not already been used to configure a user or contact object in Active Directory Domain Services. This value must be in the format “sip:<SIP address>“ as shown in the previous examples.

    • RegistrarPool specifies the fully qualified domain name (FQDN) of the pool on which the Registrar service is running.

      Note

      Exchange UM contact objects cannot be moved to pools that are part of Lync Server deployments prior to Lync Server 2010.

    • OU specifies the Active Directory organizational unit where this contact object will be located.

    • DisplayNumber specifies the telephone number of the contact object. The phone number for each contact object must be unique.

    • AutoAttendant specifies whether the Contact object is an Auto Attendant. Auto Attendant provides a set of voice prompts that allow callers to navigate the phone system and reach the party that they want to contact. A value of False (the default) for this parameter indicates a Subscriber Access contact object.