Direct Routing as a Service Onboarding Setup Steps

This is a guide for customer who are looking to deploy LoopUp's Direct Routing as a Service for their organisation.


In this article

Introduction

You will need the following information before you proceed. If you have any questions, please contact your project team.

  • Your LoopUp Customer Prefix
    • Provided by the project team, this is used to construct the domains for providing the LoopUp Cloud Telephony into your Teams environment.
  • Activation Account names & licenses
    • 8 accounts need to be created in Microsoft 365 with Teams Phone Standard licenses as part of the process to provision Microsoft’s back-end services, they can be removed afterwards

For these steps you will need to use your Global Administrator account.

Log in to https://admin.microsoft.com

Domains

In the Microsoft 365 Admin Center, expand Settings on the navigation panel on the left. And click on Domains.

(If Settings is not pinned it may not be visible, click ‘show all’ at the bottom of the menu)

The domain is comprised of your customer-specific prefix, and each of our regional subdomains “<prefix>.<region>.pstn.for-teams.com”. e.g., contoso.emea1.pstn.for-teams.com

The following 8 domains all need to be added to your tenant in the next step to authorize the use of LoopUp Cloud Telephony platform for PSTN calling.

  • contoso.amer1.pstn.for-teams.com
  • contoso.latam1.pstn.for-teams.com
  • contoso.emea1.pstn.for-teams.com
  • contoso.emea2.pstn.for-teams.com
  • contoso.sthaf1.pstn.for-teams.com
  • contoso.apac1.pstn.for-teams.com
  • contoso.austl1.pstn.for-teams.com
  • contoso.china1.pstn.for-teams.com

Add All Domains

Repeat this section for each domain listed above.

On the Domains page, click on Add Domain in the actions bar.

Enter the domain in the Domain name text box, and click the blue Use this domain button

After a moment, the page will refresh and ask you how you would like to verify the domain.

If required, click the More options link to see all verification methods.

Select Add a TXT record to the domain’s DNS records and click the blue Continue button.

Click the Copy button next to the TXT value (starts with MS=) and share with your dedicated LoopUp contact for verification.

Click the grey Close button on the right, we will revisit this page later in the process.

When you have added all 8 domains each row should have the Status being Incomplete setup. But with your customer prefix instead of contoso.

Verification

LoopUp requires each of the TXT values you created in the previous steps for each of the 8 domains. You can share this with your LoopUp project manager for verification.

Below is a table for reference if you require:

Domain

TXT Value

contoso.amer1.pstn.for-teams.com

MS=ms??????

contoso.latam1.pstn.for-teams.com

MS=ms??????

contoso.emea1.pstn.for-teams.com

MS=ms??????

contoso.emea2.pstn.for-teams.com

MS=ms??????

contoso.sthaf1.pstn.for-teams.com

MS=ms??????

contoso.apac1.pstn.for-teams.com

MS=ms??????

contoso.austl1.pstn.for-teams.com

MS=ms??????

contoso.china1.pstn.for-teams.com

MS=ms??????

 

Activate Domains

Once the domains and TXT verification records have been added into our system you will need to verify each of the domains in turn in the M365 Admin Center.

Click on the domain, and then click on Start setup this will take you back to the verification step above. Again, click Add a TXT record to the domain’s DNS records, click the blue Continue button, and this time click the blue Verify button.

If this step fails it may take longer for the DNS records we have implemented to propagate, wait some time, and click the blue Try again button, if this step still fails, contact your project team to investigate.

Once verified, the M365 Admin Center will ask you which services you want to host on the domain. Click on More options and choose Skip and do this later since we will not be hosting any M365 services on this domain.

Click the blue Continue button to finish the process.

The domain list should update to show No services selected next to each of the domains.

Activation Accounts

Now that the domains have been added and verified, we need to trigger Microsoft to provision the relevant back-end services against those new domains. The following paragraph is from Microsoft’s documentation.

Create Activation Accounts

In the Microsoft 365 Admin Center, expand Users in the navigation panel on the left and click on Active Users.

Click on Add a user in the action panel.

We suggest calling the user LoopUp Activation, but you are free to call them anything else. The important part is that each activation account is setup to use each of the domains added in the previous steps.

Enter LoopUp in the First name text box.

Enter Activation 1 in the Last name text box.

The Display Name will automatically generate based on the First name and Last name values.

Enter loopup.activation1 in the Username text box.

Select the correct domain in the Domains dropdown list.

Click the blue Next button to continue.

Assign Licenses to Activation Accounts

Ensure Assign user a product license is selected and pick a suitable license from what is available in your tenant, for example Office 365 E5, since the Office 365 E5 includes the Teams Phone Standard license required for this step.

If you do not have any Office 365 E5 licenses available, then an Office 365 E1, E3 or equivelent can be used.

Click the blue Next button to continue.

No roles are required for this standard user account, click the blue Next button to continue.

Click Finish adding to complete this action.

Repeat the last two steps with the other domains you’ve just added, with loopup.activation2, loopup.activation3, etc.

As stated by Microsoft, this step may take up to 24 hours to take effect, but is usually much quicker.

  • Direct Routing as a Service
  • Tenant
  • Customer configuration