Never miss a call again with automatic failover for Microsoft Teams

Sometimes the cloud goes down. With Callroute’s automated failover for Microsoft Teams, you’ll never miss a call again!

Automated Failover for Microsoft Teams

Intelligent, automated, instant failover

For when 99.99% uptime is just not enough. Using Callroute’s automated failover for Microsoft Teams you can set alternative destinations on all your important inbound numbers so that if your phone system is experiencing difficulties, calls are automatically diverted to your alternative service such as mobile.

How it works

How call failover works with Callroute infographic

Callroute continually monitors its connection with your phone system. If a failure is detected, calls will automatically divert to the alternative destination configured for each number. Once the fault has been resolved, service is restored immediately.

Callroute AzureAD sync

Integrated with AzureAD

Using AzureAD integration Callroute synchronises mobile numbers found in the user’s contact details and automatically applies them as failover destinations on the user’s direct dial number.

By integrating Callroute with AzureAD, all you need to do is make sure user’s update their contact card details and Callroute will do the rest.

Manual Failover

Administrators can also manually configure failover destinations for users and resource accounts in the Callroute portal. These will override any configuration that has been applied automatically

Autoamted Failover for Microsoft Teams

Automated Failover FAQs

If you experience a phone system outage whilst on an active call, the call will disconnect.

 

Unfortunately, we are unable to automatically redial the caller into your failover service. However, they can call back and will immediately be diverted to your backup service.

When a call is forwarded to your backup service. If this service is an external service e.g. mobile number then normal call charges will apply for the duration of the call. If you have a Callroute calling plan, these calls will be deducted from your remaining minute balance.

 

If your backup service is another phone system connected to Callroute; such as a PBX then there is no additional cost while using the failover service.

When we route a call to your phone system we are looking for an acceptance message. If the acceptance message is not received or your phone system responds with a 4XX or 5XX SIP response error code, we treat this as a failure and will failover to your backup service automatically.

 

More information on SIP response codes can be found here https://en.wikipedia.org/wiki/List_of_SIP_response_codes

Once a secondary destination has been set for a user it is active and cannot be selectively disabled. However, you can choose to remove the destination and reapply it at any time to re-enable the service.

AzureAD synchronisation for automated failover can be administratively disabled or enabled.

 

You will need to perform an internal housekeeping task to sanitise your AzureAD information before enabling the sync to avoid problems during failover. AzureAD is the source of authority for this information when enabled and as a result must be accurately maintained.

Yes. As an administrator you can reconfigure any failover destination for any number.

For automatic failover to work, calls must transit the Callroute network. If you are using BYOC or Callroute Calling Plans there are no limitations of use.

 

We do not support automated failover for users with Microsoft Calling Plans or Operator Connect because Callroute is not party to the voice path. However, should these services fail, depending on the severity and urgency you can reconfigure users to use Callroute temporarily.