Export (0) Print
Expand All

Migrate Dial-in Access Numbers

Lync Server 2010
 

Topic Last Modified: 2011-04-05

Migrating dial-in access numbers requires two steps: running the Import-CsLegacyConfiguration cmdlet (completed earlier in Import Policies and Settings) to migrate dial plans and other dial-in access number settings, and running the Move-CsApplicationEndpoint cmdlet to migrate the contact objects. After you run the Import-CsLegacyConfiguration cmdlet, the migrated dial-in access numbers exist both in your Microsoft Office Communications Server 2007 R2 pool and in your Microsoft Lync Server 2010 pool. During this coexistence period, dial-in access numbers that you created in Office Communications Server 2007 R2 behave differently from dial-in access numbers that you create in Lync Server 2010, as described in this section.

After you run Import-CsLegacyConfiguration but before you run Move-CsApplicationEndpoint

Dial-in access numbers that you created in Office Communications Server 2007 R2 have the following characteristics:

  • Appear on Office Communications Server 2007 R2 meeting invitations and the dial-in access number page.
  • Appear on Lync Server 2010 meeting invitations and the dial-in access number page.
  • Can be viewed and modified in the Office Communications Server 2007 R2 administrative tool.
    importantImportant:
    If you make changes to dial-in access numbers in your Office Communications Server 2007 R2 pool, you will need to rerun the Import-CsLegacyConfiguration cmdlet with the ReplaceExisting parameter to apply the same changes to your Lync Server 2010 pool. Re-importing with the ReplaceExisting parameter can overlay other changes you made in your Lync Server 2010 pool.
  • Cannot be viewed in Lync Server Control Panel, but can be viewed in Lync Server Management Shell (if you use the Get-CsDialinConferencingAccessNumber cmdlet with the Region parameter).
  • Cannot be modified in Lync Server Control Panel or in Lync Server Management Shell.
  • Cannot be re-sequenced within the region by using the Set-CsDialInConferencingAccessNumber cmdlet with the –Priority parameter.

After you run Move-CsApplicationEndpoint

Dial-in access numbers that you created in Office Communications Server 2007 R2 but moved to Lync Server 2010 have the following characteristics:

  • Appear on Office Communications Server 2007 R2 meeting invitations and the dial-in access number page.
  • Appear on Lync Server 2010 meeting invitations and the dial-in access number page.
  • Can be viewed in the Office Communications Server 2007 R2 administrative tool.
  • Cannot be modified in the Office Communications Server 2007 R2 administrative tool.
  • Can be viewed and modified in Lync Server Control Panel and in Lync Server Management Shell.
  • Can be re-sequenced within the region by using the Set-CsDialinConferencingAccessNumber cmdlet with the Priority parameter.

Dial-in access numbers that you create in Lync Server 2010

Dial-in access numbers that you create in Lync Server 2010 before, during, or after migration have the following characteristics:

  • Do not appear on Office Communications Server 2007 R2 meeting invitations and the dial-in access number page.
  • Appear on Lync Server 2010 meeting invitations and the dial-in access number page.
  • Cannot be viewed or modified in the Office Communications Server 2007 R2 administrative tool.
  • Can be viewed and modified in Lync Server Control Panel and in Lync Server Management Shell.
  • Can be re-sequenced within the region by using the Set-CsDialinConferencingAccessNumber cmdlet with the Priority parameter.

You must finish migrating dial-in access numbers that point to an Office Communications Server 2007 R2 pool before you decommission the Office Communications Server 2007 R2 pool. If you do not complete dial-in access number migration as described in the following procedure, incoming calls to the access numbers will fail.

importantImportant:
You must perform this procedure prior to decommissioning the Office Communications Server 2007 R2 pool.
noteNote:
We recommend that you move dial-in access numbers when network usage is low, in case there is a short period of service outage.

  1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group and open the Office Communications Server 2007 R2 administrative tool.

  2. In the console tree, right-click the forest node, click Properties, and then click Conferencing Attendant Properties.

  3. On the Access Phone Numbers tab, click Serviced by Pool to sort the access phone numbers by their associated pool, and identify all the access numbers for the pool from which you are migrating.

  4. To identify the SIP URI for each access number, double-click the access number to open the Edit Conferencing Attendant Number dialog box, and look under SIP URI.

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

  6. To move each dial-in access number to a pool hosted on Lync Server 2010, run:

    Move-CsApplicationEndpoint -Identity <SIP URI of the access number to be moved> -Target <FQDN of the pool to which the access number is moving>
    
  7. In the Office Communications Server 2007 R2 Administrative tool, on the Access Phone Numbers tab, verify that no dial-in access numbers remain for the Communications Server 2007 R2 pool from which you are migrating.

    noteNote:
    When no more dial-in access numbers point to the Office Communications Server 2007 R2 pool, you can decommission the Office Communications Server 2007 R2 pool.
 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft