Big Yellow Bee - Fully integrate your business telephony into Microsoft Teams.

Frequently Asked Questions

Our experts can answer questions, provide more information, and help you understand what Big Yellow Bee can do for your business.

What’s Direct Routing?

Microsoft Phone System Direct Routing lets you connect a supported Session Border Controller (SBC) to Microsoft Phone System. Direct Routing allows you to decide how to provide voice to Office 365. You can bring your own carrier or leverage our carrier services knowing you are safe, certified and secure.

Can I still use my 3rd -party system?

Yes! Direct Routing and Big Yellow Bee allows you to leverage Microsoft Teams and continue to realize the investment and value of 3rd-party systems including PBX, call center features and analog devices.

How do you handle analog?

We recommend electronic faxing if you are able to switch over because analog was not built for the internet. Our hosted solution is 100% running on Yealink and Microsoft. They offer gateways for various business purposes such as e-fax, elevators, door locks, etc. Yealink offers a series of Teams enabled and Teams native phones; these can be procured from them via standard Capex or as a device-as-a-service (DaaS) on the same monthly billing as the Big Yellow Bee Service.

Does Big Yellow Bee offer number porting, emergency services and toll-free support?

Yes. Absolutely.

Big Yellow Bee vs. another Calling Plan

We keep it simple. We offer a flexible and economical calling plan with a vast international footprint. Our calling plans are simple, and we have no upfront, carrier service or monthly commit. You simply pay for what you use.

What do I need to get started?

In order to enable calling services in Microsoft Teams with Big Yellow Bee, you will need a Phone System License or have E5/A5 as part of your Microsoft 365 bundle. We can help with all of this.

How does fail-over work?

Our solution is built in Azure and benefits from all the availability and redundancy features that comes with it. Big Yellow Bee’s failover can be covered in different areas:
‍
Geographical Presence: Servers in 5 different Azure regions and will grow according to business grow. All the components have direct connection with each other on the Azure backend network, which according to Microsoft has less than 15ms round trip time.

Redundancy and failover on carrier: All our SBCs are connected to several careers allowing us to have failover and redundancy at career level. If a career fails the system will automatically route the calls to the other careers.

Redundancy and failover on routes: An advanced mechanism for selecting the best and most efficient route for calls. By leveraging Audio codes ARM servers and geographically spreading them in different regions we can make sure that all the SBC have access to their closest routing manager.

Redundancy and failover on SBC: We currently have 5 dynamic SBC in 5 Azure regions and will expand with business grow. Our AudioCodes SBCs are dynamic in a way that they expand and shrink with the traffic load. All the connections to the SBCs are based on Names and FQDN. This will allow our system to automatically connect the end points to another SBC if an entire Azure region goes down.

Redundancy and failover at Teams: By using us, customers are connecting their tenant to an FQDN which is pointing to our SBC. In the back end we are leveraging advanced DNS features to handle the traffic and connect customers to the closest SBC. If one SBC goes down, it will automatically connect customers to other available SBCs.

Will this work with AudioCodes, Polycom, Yealink, etc. handsets?

Yes, but they need to be Microsoft Teams compatible.

Do you support cell phones, soft clients, desk phones and all combinations?

Yes! Today’s users mix and match their communication and collaboration ‘devices’ based on where they are, what they are doing and even whom they might be talking with. Users can make and take calls however they choose.

Frequently Asked Questions

Complete your communications hub with Voice for Teams.