{"id":2402,"date":"2021-10-21T13:55:25","date_gmt":"2021-10-21T13:55:25","guid":{"rendered":"https:\/\/modern-workplace.uk\/?p=2402"},"modified":"2021-10-21T14:23:47","modified_gmt":"2021-10-21T14:23:47","slug":"teams-virtual-sbc-closing-azure-network-ports-warnings-for-azureloadbalancer-and-virtualnetwork-2-2-2-2-3-2-3-2-2-2-2-2-2","status":"publish","type":"post","link":"https:\/\/modern-workplace.uk\/?p=2402","title":{"rendered":"An Option for Voice Migration to Microsoft Teams – Direct Routing: Alternative Routing on the AudioCodes SBC"},"content":{"rendered":"\n

I found the Alternative Routing<\/em><\/strong> feature on the AudioCodes SBC really useful to accelerate the migration from a legacy PBX to Teams (with Direct Routing) in some scenarios.<\/p>\n\n\n\n

Typically we have a legacy PBX that has to live side-by-side with Teams Direct Routing for a period of time.<\/p>\n\n\n\n

Let’s say that the DDI numbers ranges in the legacy PBX change often and are not easy to define or that the DDIs are being migrated to Teams not in groups. <\/p>\n\n\n\n

In both the above situations, a large number of routing rules could be required to define where a telephone number is located (for a example, if it is in the legacy PBX or if it is a PSTN number).<\/p>\n\n\n\n

A possible solution is using Alternative Routing<\/strong>. <\/p>\n\n\n\n

What you will have is the main route (called “Route Row<\/em><\/strong>“) and one or more Alternative Routes<\/strong> that will be used in case the first route returns an error (like “404 – not found”).<\/p>\n\n\n\n

The whole process of trying a route, failing and moving to the next one usually does not add a perceptible delay and is transparent to the user.<\/p>\n\n\n\n

Let’s quickly depict an example scenario: <\/p>\n\n\n\n