Your SBCs get added to a gateway list in Office 365. You can assign them a priority if you wish. When a priority is set, calls from Teams will attempt to be routed to the SBC with the highest priority if it is available. If no priority is set, or Continue Reading
Yes. You can have as many as you want. All you need to consider is how you handle fail over if a particular SIP trunk is down
Microsoft have a handful of destinations your SBCs must be able to reach over the internet. Your SBC must be able to reach the following IPs on target port 5061/tcp 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199 They must also be able to connect media ports to 188.8.131.52/14 on 49152:53247/udp In Continue Reading
Strictly here in the context of the common area phone Office 365 SKU, the answer is no. However, you can use normal accounts with E1+Phone System Licenses or even direct SIP registration to the SBC itself for common area phone usage.
Call Queues and Auto Attendant services are a cloud supplied solution. At the moment there is no support to allow numbers assigned to these services to route through Direct Routing. They must be ported into Microsoft Phone System or use the default Microsoft number allocation.
Yes. You need a public certificate for your SBCs to communicate with Microsoft Teams. This is because encrypting signalling and media traffic over the internet is important to prevent eves dropping / wire tapping. You can obtain certificates from any of the common signing authorities e.g. GoDaddy, GlobalSign etc. But Continue Reading
Well this depends. In theory this is possible, but not practical in many cases. In order to get voicemail services to work, the user requires a phone system license. You would need to enable the user with a number in Microsoft Teams that doesn’t need to be a real number Continue Reading
Currently as of this moment, the answer here is no. Service numbers including conferencing numbers are not supported via Direct Routing. Conferencing numbers must be ported into Microsoft or use the default service number allocation that Microsoft provide for conferencing with respect to Microsoft Teams
No. Currently Microsoft Support only Audiocodes and Sonus / Ribbon SBCs for Direct Routing. This is not to say you may get some success with others, but they’re not officially supported. Microsoft are implementing media bypass support and this requires the SBC to support ICE Lite. Currently only Audiocodes and Continue Reading
The answer is “it depends on your use case” If you need to connect your on-premises VoIP solution to Teams so that your users can call between systems without breaking out over the PSTN, then yes you need direct routing for those internal voice calls. If you are moving to Continue Reading