SIP Trunking with Microsoft Teams (Beta)
Steps to Setup SIP Trunking with Microsoft Teams
NOTE: This is a beta service offered to early adopters. SkySwitch offers best efforts support for this feature only.
Step 1. Authorize Domain Name for TLS certificate validations
Add domain sbcXX.r-rtele.com and chose verification method as MX record. Send verification information to firstname.lastname@example.org.
|You must replace the 'XX' in the SBC domain with a value that is assigned to you. Please contact email@example.com to receive a dedicated SBC domain.|
Step 2. Create a User on newly verified Domain
User MUST use new domain name as Primary contact. This User can be removed at the end of setup.
- Wait 4 hours till Microsoft propagates new domain to all services –
Step 3. Pairing SBC
Login to Powershell
$userCredential = Get-Credential
$sfbSession = New-CsOnlineSession -Credential $userCredential
Import-PSSession $sfbSession –AllowClobber
New-CsOnlinePSTNGateway -Fqdn sbc05.r-rtele.com -SipSignallingPort 5061 -MaxConcurrentSessions 100 -Enabled $true
Allow calling for each User
Set-CsUser -ID “user@domain" -EnterpriseVoiceEnabled $true
Set-CsTeamsCallingPolicy -Identity Global -AllowPrivateCalling $true
Create Routing policies
check existing rules: Get-CSOnlineVoiceRoute
- Routing rules will depend on User requirements. Routing rules are needed for calls from Teams to PSTN. Inbound calls will work without rules
- Multiple routing profiles can be created and assigned individually to User
- If User subscribed to Microsoft Calling Plan it will be used as a route of last resort
Teams admin portals: