Configure your ACP to support regionally hosted meetings

 

上次修改主題的時間:2017-06-28

Read this topic to learn how to configure your audio conferencing provider (ACP) to work with regionally hosted meetings.

註記注意事項:
Regionally hosted meetings is available for limited release only. For more information about the limited release, please contact your Microsoft representative.

For more information about regionally hosted meetings, see Plan for regionally hosted meetings in Skype for Business Online and Set up and configure regionally hosted meetings in Skype for Business Online.

Dial-in conferencing for Skype for Business Online is a service made available by Microsoft and by third party audio conferencing providers (ACPs). To support cross region moves, modifications are made to dial-in coordinates during the process; these changes are automatic when using Microsoft dial-in conferencing, but require several manual processes for ACPs.

There are many ACP vendors. These topics describe how to configure dial-in conferencing for BT MeetMe, InterCall, and PGi.

註記注意事項:
AT&T has a dial-in conferencing offering for Skype for Business Online, but it is only available in North America and, therefore, does not currently support regionally hosted meetings.

When a tenant is enabled for regionally hosted meetings, users can be moved between regions to an Office 365 data center closest to where they live; for example, North America to Asia. Once moved cross region, dial-in coordinates in unexpired or newly created meetings will no longer function without modification of the AcpInfo XML data. You will need to coordinate with your ACP vendor to ensure that dial-in conferencing works with regionally hosted meetings.

The terms default, source, and target region are used throughout this document and are defined as follows:

  • Default region – The region where the tenant is located.

  • Source region – The region where the user is currently (usually the same as the default region).

  • Target region – The region the user is being moved to (usually a non-default region).

This topic contains the following sections:

The following table summarizes ACP vendor support by region:

 

Vendor

Regions Supported

Requires Manual Configuration

Scriptable with PowerShell

AT&T

NAM

N/A

N/A

BT MeetMe*

EUR, NAM

Yes

Yes

InterCall

APC, EUR, NAM

Yes

Yes

Microsoft CPC

APC, EUR, NAM

No

N/A

PGi

APC, EUR, NAM

Yes

Yes

*BT MeetMe support for APC is expected soon.

註記注意事項:
Support for regions that aren’t listed varies by vendor. For example, if users are homed in a data center in Canada, Toll / Toll Free numbers for Canada, combined with a Domain attribute that maps to North America, may enable users dialing in to a meeting organized in Canada to bridge to the meeting from North America. For details, contact your ACP vendor.

Dial-in coordinates are stored in the AcpInfo XML setting on the user object. You can collect all AcpInfo related details by using the following cmdlet:

Get-CsUserAcp -Identity <SipAddress>

To see just the AcpInfo XML settings, use the following cmdlet:

Get-CsOnlineUser -Identity <SipAddress> | fl AcpInfo

The following example shows AcpInfo settings for Microsoft Cloud PSTN conferencing:

AcpInfo        : {<acpInformation>
                                      <tollNumber>+5031232222</tollNumber>
                                      <tollFreeNumber>+18001232222</tollFreeNumber>
                                      <participantPassCode>0</participantPassCode>
                                      <domain>resources.lync.com</domain>
                                      <name>Microsoft</name>
                                      <url>https://dialin.lync.com/71458546-544d-4fbf-827c-8500250aff4b</url>
                     </acpInformation>} 

Each ACP vendor requires slightly different attribute changes to accommodate cross-region moves. These changes are summarized in the following table:

 

Feature / Vendor

AT&T

BT MeetMe

InterCall

PGi

TollNumber

N/A

Yes

Yes

Yes

TollFreeNumber

N/A

Yes

Yes

Yes

ParticipantPassCode

N/A

No

No

No

Domain

N/A

Yes

No

Yes

Name

N/A

Yes

No

Yes

URL

N/A

Yes

No

Yes

There are seven basic steps involved in moving a user cross region and updating dial-in coordinates for unexpired and new meetings. Several of the steps occur once per customer, while others occur for each user moved cross region:

  1. Work with the ACP vendor to set up licensing in the new region.

  2. Provide the ACP vendor with a list of names of the user(s) being moved; typically, a list of Sip Addresses and preferred data location in CSV format. For details, contact your ACP vendor.

  3. Ask the ACP vendor to map the user names to the target region that aligns closest to the specified preferred data location, and provide a CSV file with the new dial-in coordinates.

  4. Next, run the Set-CsOnlineDialInConferencingTenantSettings cmdlet, and set the ACPMeetingMigrationTriggerEnabled attribute to $True.

    註記注意事項:
    This is a tenant level setting and requires Skype for Business or Global administrator privileges to enable.
  5. Remove the existing AcpInfo settings from the user object.

  6. Set the new dial-in coordinates for the target region based on the ACP vendor's CSV file.

    註記注意事項:
    If ACPMeetingMigrationTriggerEnabled = $True, the meeting migration service will automatically update all unexpired and new meetings with the new ACP dial-in coordinates if the users Exchange mailbox is hosted in Exchange Online.
  7. Confirm that the meeting migration service has completed successfully, then populate an unused attribute in the on-premises Active Directory with the 3-digit preferred data location code for the target region (for example, APC, EUR or NAM). When Azure AD Connect DirSync runs (delta or full), the change is synchronized with the PreferredDataLocation attribute in Azure AD to trigger the cross-region move.

There are two methods for triggering the meeting migration service to update unexpired and new meetings with dial-in coordinate changes:

  • Tenant-level cmdlet (recommended). If configured at the tenant level, the meeting migration service is called automatically when Set-CsUserAcp is run:

    Set-CsOnlineDialInConferencingTenantSettings -ACPMeetingMigrationTriggerEnabled = $True
    
  • User-level setting cmdlet. If configured at the user level, the meeting migration service must be triggered manually after running Set-CsUserAcp:

    Start-CsExMeetingMigration -Identity <SipAddress>
    
 
顯示: