Integration with Microsoft Teams

updated 2 yrs ago
13replies

CarrierTenant - CONFIGURATION GUIDE CustomerTenant - CONFIGURATION GUIDE VSXi MS Teams Direct Routing - Configuration Guide

The VSXi supports Microsoft's new Teams Direct Routing. The Direct Routing capability allows Service Providers to offer their SIP Trunking services to organizations using Teams for inbound and outbound calling, this offering is in addition to Microsoft's own calling plans.

The VSXi provides SIP/TLS, SRTP and signaling adaptations using the VSXi's SMC (SIP Message Conversion) engine to interface with Microsoft Team's Direct Routing servers.

See the attached document for additional configuration reference.

Multitenant Configuration Example:

We have built a working Microsoft Teams Multitenant configuration example at one of our Test VSXi so you can explore and replicate:

You can log into https://teams.sansay.support:8888/
user: msteams
pass: teamssansay

This example configuration consist of:

1 Carrier Tenant
-> TID 1000 - MS Teams domain: teams.sansay.support
DID assigned: +18582056242

3 Customer Tenant
-> TID 1001 - MS Teams domain: 1001.teams.sansay.support
-> TID 1002 - MS Teams domain: 1002.teams.sansay.support
-> TID 1003 - MS Teams domain: 1003.teams.sansay.support

TLS Certificate to support this multitenant implementation has:
CN: *.teams.sansay.support
SAN: *.teams.sansay.support, teams.sansay.support

You can make a test call from your mobile or desk phone to: +18582056242.
This call will reach MS Teams Carrier Tenant user (linked to domain teams.sansay.support) at MS Teams.

This call will generate a CDR which you can use to explore call flow:
PSTN TID 100 -> TID 1000
TID 1000 -> MS Teams TID 2000

where TID 1000 belongs to the Carrier Tenant.

- Ken_Ryon
- 4 yrs ago
- Reported - view
Does the Inbound peering resource also uses the SIP/TLS service port applied to the outbound peering resource?
- Miguel_Salcedo
- 4 yrs ago
- Reported - view
Correct Ken. Both Peering Resources (Inbound and Outbound) should be linked with the same SIP/TLS Service Port.
- Jason_Cummins
- 4 yrs ago
- Reported - view
Does the integration support multitenancy using Teams ability for subdomains in the contact header?
- Miguel_Salcedo
  
  4 yrs ago
  
  Reported - view
  Jason Cummins Yes, You can have different customer configured with Teams, each of them with it own TLS certificate and Service Port.
- miguel_mendoza
- 3 yrs ago
- Reported - view
Can we use wildcard SSL for the domains?
- Miguel_Salcedo
  
  3 yrs ago
  
  Reported - view
  miguel. mendoza Hi Yes, Wildcard certificate is supported by MS Teams.
- jhansen
- 3 yrs ago
- Reported - view
we got it working with a wildcard.
- Brian_Paboojian
- 3 yrs ago
- Reported - view
Everything on the checklist makes sense except the second step "Load Microsoft Root Certificate (Baltimore CyberTrust Root) ". Where do we get this?
- cperez
  
  3 yrs ago
  
  Reported - view
  Brian Paboojian Miguel Salcedo
- Miguel_Salcedo
  
  3 yrs ago
  
  Reported - view
  Brian Paboojian Hi Brian. We have updated this article with a configuration guide where you can find/download the BaltimoreCyberTrustRoot Cert and full configuration checklist. To reduce configuration time and speed up MS Teams integration you can open a new ticket with us and we will take care of it for you.
- mark_hayes
  
  2 yrs ago
  
  Reported - view
  Miguel Salcedo
- mark_hayes
- 2 yrs ago
- Reported - view
Miguel, is there a configuration to allow MS Teams to use alternative 911 Emergency provider like Bandwidth's DLR - Dynamic Location Routing? Bandwidth is interop'd with MS Teams
- cperez
  
  1 yr ago
  
  Reported - view
  mark. hayes Sansay supports all E911 providers, Bandwidth, Inteliquent and Intrado.