Breeze Connect
Teams Direct Routing
Quickstart Guide

This document covers the basic steps required to enable MS Teams for Direct Routing.

Breeze Connect
Teams Direct Routing
Quickstart Guide

Prior knowledge and external documentation will assist with processes not covered in this guide and related to:

Adding users to your O365 environment

Assigning appropriate licences

Setting organisation policies

Configuring IVR’s, Ring Groups and complex call flows

If you need guidance on these prerequisites
please speak to the Leader Cloud Sales team to get started.

Important Notes

• You will require appropriate privileges in your Office365 environment in order to perform the required configuration steps

• On occasions, Microsoft cloud services, including MS Teams exhibit issues with synchronizing changes. If you are issuing commands that don’t seem to take effect, please wait a while (on occasions we have noticed it taking 1-2 hours) and then re-test. Unfortunately, this is not something within our control.

Breeze Teams QuickStart guide


If need any help during this process feel free to call us

Steps

Step 1

Contact Breeze connect and share your interests in MS Teams:

  • How many users
  • How many channels
  • Existing numbers / New numbers
  • Do you have appropriate Office365 licenses for end users
Step 2
  • New Breeze Customer:
    • Create a customer profile from your Representative portal – https://my.breezeconnect.com.au/
    • Create a new Trunk as a placeholder for the MS Teams service. (This trunk will only be used as a billing reference and does not have to be registered)
    • Use the Breeze Teams base product when creating your Trunk.
    • No add-on product required
  • Existing Breeze Customer:
    • Create a new Trunk as a placeholder for the MS Teams service. (This trunk will only be used as a billing references and does not have to be registered)
    • Use the Breeze Teams base product when creating your Trunk.

No add-on product required

Step 3
Step 4
Step 5
Step 6
  • Using PowerShell, connect a remote session for the tenant (This step requires O365 credentials with Admin privileges)
    • Import-Module SkypeOnlineConnector
    • $sfbSession = New-CsOnlineSession
    • Import-PSSession $sfbSession

  • Create a PSTN usage policy
    • Set-CsOnlinePstnUsage -Identity Global -Usage @{Add=”NetSIP_Usage”}

  • Create Voice Route and Associate with PSTN usage (You require the unique direct routing domain provided in step 3)
    • New-CsOnlineVoiceRoute -Identity “NetSIP_Route” -NumberPattern “.*” -OnlinePstnGatewayList p999999999999999P.teams.netsip.net.au -OnlinePstnUsages “NetSIP_Usage”

  • Create a voice routing policy
    • New-CsOnlineVoiceRoutingPolicy “NetSIP_Policy” -OnlinePstnUsages “NetSIP_Usage”

  • Enable Voice for your user, and assign a phone number
    • Set-CsUser -Identity [email protected] -EnterpriseVoiceEnabled $true -HostedVoiceMail $true -OnPremLineURI tel:“+61999999999” -AudioVideoDisabled $false

  • Assign the voice routing policy to your user
    • Grant-CsOnlineVoiceRoutingPolicy -Identity [email protected] -PolicyName NetSIP_Policy

  • Verify your user is configured as expected (optional)
    • Get-CsOnlineUser -Identity [email protected] | Format-List -Property FirstName, LastName, EnterpriseVoiceEnabled, HostedVoiceMail, LineURI, UsageLocation, UserPrincipalName, WindowsEmailAddress, SipAddress, OnPremLineURI, OnlineVoiceRoutingPolicy, TeamsCallingPolicy, dialplan, TeamsInteropPolicy

contact us

small_c_popup.png
account