I think you've glossed over a couple of items Mike.. Operator Connect Carriers are peered directly with Microsoft using MAPS, meaning that it's generally a better quality of service compared to DR providers. This can be offset with the DRaaS provider being connected via Express Route though.. Also, you mentioned pricing - I beg to differ.. at least from a provisioning perpsective, you are likely to get a higher establishment fee from a DR provider, over a OC. That's due to the fact that many DR providers use a manual process to deploy the service. Whilst OC providers must leverage Microsoft's extensive API library, which generally means faster provisioning times. There are further nuances, such as pushing numbers into a customer's tenancy without consent with OC, and not available through DR as it requires Powershell scripting. This is a great option for customers that don't want their carrier to have access to their tenancy. Happy to chat further on this topic, as it's something I've been immersed in for quite some time as well..
A lot of Operator Connect providers do offer redundancy/continuity in their package. Where as if you might have an issue on Teams, you can forward DID's to other numbers, fe mobile numbers. it also works with the MBN.
I agree, Henry, that OC providers can forward DID's to other numbers but they usually charge on a per DID basis. This is much different than DRaaS providers that provide their own cloud phone system software as an active-active backup for the entire solution, auto attendant, ring groups, and every user in the company, automatically. Those DRaaS providers are powering Teams Phone with their own cloud phone system... so the customer is essentially getting two (active) cloud phone systems (and paying for it... which is the downside to all that redundancy).
If you go with OC or DRaaS: No, you do not need an SBC at any site; Yes, the OC/DRaaS provider will port your existing company's DID's... or they can issue you new DID's if you prefer; No, you do not need SIP trunks. I hope that helps! Feel free to email me for more specific recommendations: AskMike@aerocominc.com
By using an Operator Connect provider (instead of Microsoft Calling Plan), Mid-large size companies will receive better pricing, more personalized support, access to additional features (i.e. SMS, reporting, recording, etc.), and the ability to support analog signaling. Microsoft doesn't try very hard to earn that business and would rather hand it off to their Operator Connect partners, as opposed to adding the additional benefits to support them. Micro-sized organizations, however, are best-suited buying the calling plans from Microsoft, directly, because most Operator Connect providers have a minimum of around 25-or-so seats.
Hello, We are using teams phone system with an Operator connect Setup. We are trying to dial a non emergency number but it keeps on failing, Does it have something to do with additional feature you mentioned in DRAAS?
For microsoft teams direct routing inbound calls, I am getting multiple 180 ringings from Microsoft teams side( that too with different tags) despite user is logged in at single device(no forking) ..Is there a way to restrict multiple 180 ringings to just one ?? i am expecting 180 ringing only once from microsoft teams side which is not happening.
I think you've glossed over a couple of items Mike.. Operator Connect Carriers are peered directly with Microsoft using MAPS, meaning that it's generally a better quality of service compared to DR providers. This can be offset with the DRaaS provider being connected via Express Route though.. Also, you mentioned pricing - I beg to differ.. at least from a provisioning perpsective, you are likely to get a higher establishment fee from a DR provider, over a OC. That's due to the fact that many DR providers use a manual process to deploy the service. Whilst OC providers must leverage Microsoft's extensive API library, which generally means faster provisioning times. There are further nuances, such as pushing numbers into a customer's tenancy without consent with OC, and not available through DR as it requires Powershell scripting. This is a great option for customers that don't want their carrier to have access to their tenancy. Happy to chat further on this topic, as it's something I've been immersed in for quite some time as well..
Yes, agree with everything you mentioned. Thanks for further elaborating!
A lot of Operator Connect providers do offer redundancy/continuity in their package. Where as if you might have an issue on Teams, you can forward DID's to other numbers, fe mobile numbers. it also works with the MBN.
I agree, Henry, that OC providers can forward DID's to other numbers but they usually charge on a per DID basis. This is much different than DRaaS providers that provide their own cloud phone system software as an active-active backup for the entire solution, auto attendant, ring groups, and every user in the company, automatically. Those DRaaS providers are powering Teams Phone with their own cloud phone system... so the customer is essentially getting two (active) cloud phone systems (and paying for it... which is the downside to all that redundancy).
Who I need a SBC at each site? Would I need to port my existing DIDs using OC and/or DRaaS? Would I need SIP trunks as well?
If you go with OC or DRaaS: No, you do not need an SBC at any site; Yes, the OC/DRaaS provider will port your existing company's DID's... or they can issue you new DID's if you prefer; No, you do not need SIP trunks. I hope that helps! Feel free to email me for more specific recommendations: AskMike@aerocominc.com
Your videos are on point and bring great clarity to this process!
Thanks for the kind words, Dean!
How can one tell if the telecoms support or can offer "Operator Connect" or "Direct Routing" in my country?
Hi Smith which one service is direct routing or operator connect
So why would a company choose operator connect, instead of just using Microsoft as the cloud pbx? What's the advantage?
By using an Operator Connect provider (instead of Microsoft Calling Plan), Mid-large size companies will receive better pricing, more personalized support, access to additional features (i.e. SMS, reporting, recording, etc.), and the ability to support analog signaling. Microsoft doesn't try very hard to earn that business and would rather hand it off to their Operator Connect partners, as opposed to adding the additional benefits to support them. Micro-sized organizations, however, are best-suited buying the calling plans from Microsoft, directly, because most Operator Connect providers have a minimum of around 25-or-so seats.
can you probide the contact details of service proder for operator connect
straight forward simple explanation
thanks!
How about call quality? Is there a difference?
Good question! No difference in call quality. Same exact technology being used.
Hello, We are using teams phone system with an Operator connect Setup. We are trying to dial a non emergency number but it keeps on failing, Does it have something to do with additional feature you mentioned in DRAAS?
No, that shouldn't have an affect. Sounds like you'll have to do some troubleshooting with your OC provider.
- How many times have Microsoft Teams service gone down, and for how long did it stay down?
That's a stat that I don't have, but some outages are regional vs. national, vs. global, so you'd have to dissect all those.
how to create extention number in operator connect
Thanks for explaining
For microsoft teams direct routing inbound calls, I am getting multiple 180 ringings from Microsoft teams side( that too with different tags) despite user is logged in at single device(no forking) ..Is there a way to restrict multiple 180 ringings to just one ?? i am expecting 180 ringing only once from microsoft teams side which is not happening.
i hate teams phone
Why?