Info

Teams is Microsoft’s hub for teamwork in Office 365, bringing together chat, meetings, calling, and collaboration
all in one place and accessible on a wide range of devices. It enables users to communicate with voice and video
across geographies, languages, and organisations. Users can work in confidence on a platform designed with
advanced security, control, and compliance features.

NOTE: These steps may change as Microsoft updates its menus; please refer to their support team if you have any questions.

Pre-requisite Licensing

• Business Basic + Teams Phone standard
• Business Standard + Teams Phone standard
• Business Premium + Teams Phone standard
• Office 365 E1 + Teams Phone standard
• Office 365 E3 + Teams Phone standard
• Office 365 E5
• Microsoft 365 E1 + Teams Phone standard
• Microsoft 365 E3 + Teams Phone standard
• Microsoft 365 E5

Please ensure that you have the appropriate licenses before you proceed.

Steps to Configure Direct Routing Connector Licences

Register a subdomain name in the tenant

1. Navigate to the Teams Admin Center, https://admin.microsoft.com/Adminportal/, and verify the SBC Domain

   • Working with Xima Software and Channel UC, you’ll receive an FQDN, which will be made within the Enablr platform for our use.
   • There may be some variation with this FQDN, but in the example below, we will go with "customername.teams.channeluc.com”.

2. Navigate to Settings > Domains > Add Domain and enter the FQDN provided within the "Domain Name" box

   

3. Click “Use this Domain”.

4. On the next page, select “Verify you own your domain”.

   • Video documentation here

5. By default, the top option, “Add a TXT record to the domain’s DNS records”, is selected.

   

6. Click continue and please note the three fields generated to verify the domain.

   

7. Working with the Xima team, please email the TXT value to [email protected], then wait for confirmation that the TXT value has been added.

   • Channel UC will input this information into the SBC (the Enablr platform) on Xima's behalf.
   • This will start the process of verifying the connection between the SBC and the Teams tenant.

8. Do NOT click “verify” until you’ve received word that this has been added. If you do, it will fail to be verified.

   • The best practice is to halt your progress at this point until you’ve received word that it has been added.
     • At which point, you can access this domain again and start where you’ve left off.

9. Once everything above is done, then continue to the next step.

Create temporary User to register & activate subdomain

1. Navigate to Users> Active Users > Add a user

   

2. When finalizing this page, be sure to select the new domain that you’ve just set up.

   • The user MUST contain this new domain.

3. Click "Next" and temporarily assign a paid license, then click “Next” again.

4. Enable “Admin Center Access” and “Global Administrator”, then click “Next”.

5. Finalize the user creation by clicking “Finish Adding” which will take you to a confirmation screen

   

6. Make a note of this user’s email address and password before proceeding.

7. Open an incognito window and login with this newly created user.

   • Logging in as this user will help the system recognize and initiate this new subdomain.

8. Once this is done you’ll be able to log back into the Teams Admin Center and add the FQDN as an SBC.

Connect the SBC to MS Teams

1. To pair Office 365 with Channel UC SBC infrastructure, access your Teams Admin Center with full
   administrative rights.

   • NOTE: These next steps must take place after once you’ve verified the the subdomain and created a user within that domain

2. Navigate to the Voice Menu > Direct Routing.

3. Create a new SBC by pressing Add.

4. Enter the SBC FQDN name received by Xima/Channel UC, and add a description.

5. Upon creation, toggle ON the “Enabled” option and add in the signaling port provided by Channel UC.

   

6. Leave the remaining settings as they are.

   • NOTE: One exception may be if you wish to configure a fail-over and/or you have multiple SBCs.

7. Once applied, the settings will be visible under SBCs.

   • Should you want to review these settings after saving, they can be found under Voice > Direct Routing > Settings

     
   
   

8. Click “save” and note your newly created SBC

   
   • You’ll also note that the TLS Connectivity Status says “Inactive”. This is normal and should not be a concern.
     • Once traffic starts to come through, the “SIP Options Status” will change

Voice Routes

To make a call, a PSTN usage rule and a Voice route policy are required.

1. On the “Direct Routing” page, click on Voice Routes > +Add

   

2. Provide your Route with a name, perhaps something like “LocalRoute”, providing a description if you wish

3. Give it a priority, such as “1”

   
   • NOTE: “Priority” applies if you have multiple routes or SBCs. For example, local numbers vs. International numbers.
     • In the example above, we have set up a simple routing rule of “.* “ which is a wild card.
       • This means that ALL traffic that comes into this routing rule will use this routing rule even if there is another rule under it.
       • Microsoft uses the priorities as they are listed, starting with 1. If it finds a match, it sends it.
     • In the example above, since we’ve also set a lower priority rule for international, since the Priority 1 rule is a wild card, all traffic on this SBC will use it and will not reach the international rule below it.
     • If you have customers dialing internationally and locally, you’ll need to set up routing rules to accommodate both.
     • We will make it “Priority 1” to resolve the issue in this example and match the international rule first.
       • This means that any time a 0011 is dialed, it does a number match and goes out.
       • If 0011 is NOT dialed, it then uses the wild card rule.
     • This can get complicated, especially with how dialing translation is expressed in routing tables like this.
     • Another example may include multiple SBCs or phone systems. In that case, maybe we should set up some short codes for number matching.
       • For instance, if .4000 is dialed, perhaps this goes out of our SBC and hits the Xima Contact Center.
       • Whereas every other type of call goes to the wild card.
       • Either way, make sure that anything that is NOT the wild card has a higher priority

4. Under “Dialed Number Pattern”, in order to keep it simple, put in “.* “.

   • This means that all traffic that comes through this SBC will cater to this rule.

5. Under "SBCs enrolled", click on “Add SBCs”.

   • A window will pop on the right-hand side that will show you the configured SBC.

     

6. Select it, and click “Apply” at the bottom.

Dial Plans

For utilizing short number calling through Channel UC, Teams service changes need to be applied to the Teams
DailPlan in Office365

1. Access the Teams Admin Centre as an administrator and navigate to Voice > Dial plans > Manage Policies

2. If you have a “Global (Org-wide default)” policy, select it.

3. If there are no "Normalization rules" configured for it, click the +Add button

   

4. Enter the new Name of the rule

   

5. Select the Advanced radio button.

6. Configure the IF condition field.

7. In the "The number dialed matches this regular expression" section, enter the following:

   • ^([0-9*#+]{1,10})$

8. Within the "Then do this" section, under the "Translate the number based..." section, enter the following:

   • $1

9. You can then test the rule by entering a phone number and selecting Test

10. Lastly, click Save

This will complete the basic setup of Microsoft Teams direct routing