how do you deal or how would you deal with the routing strategy in enterprise world where you have multiple locations, Teams users from different countries and locations and based on the home location of the user you would like to route his/her outgoing calls from Teams through his/her home voice egress (might be PSTN gateway, SIP trunk,...).
I have basic setup of Teams Direct Routing, AudioCodes SBC and our internal Voice infrastructure - at this moment trunk to PBX. We have more PBXs but for time being I started with Unify Openscape Voice. There will be users e.g. from Germany with their own PSTN gateway connected to OSV and users from UK with their own different voice egress connected to OSV. If I move user's directory number to Teams and their incoming calls are routed to Teams, I would like to still have possibility to route the outgoing calls for them based on their home DID (so might be based on Calling number choose the right path on OSV). But I cannot come with tools that would make this possible on side of OSV.
Does anybody have simillar setup or wider setup where e.g. Teams SBC is connected to more PBXs and serve the Teams connection for more locations?
I do read articles and posts and all the people deal with very simple scenario of one trunk for everybody or more trunks but connected directly to SBC.
I understand that this is about capabilities of used PBX but might be somebody has own experience already and might give me hints how to deal with complex setup.
It is possible to connect multiple SBCs with Direct Routing and have them placed in different locations. One example is a customer with SBC in USA, Europe and Asia, they have local SIP trunks in each country and when a Teams user do an outbound call to Japan it will go via the Asia SBC. You set this with different Voice Routing Policies.
When Location-Based Routing is released (Q1 2019 in roadmap) you will able to route calls to different SBC/SIP trunk based on where the calling user is connected at the moment. This can be useful if you need to route all outbound calls on a location gateway, maybe due regulatory reasons.
Another reason for local SBC in a geographic area could be that you need to connect a local analog device to Teams, you can connect that to your SBC and you will be able to call that from your Teams client. When you can bypass media in the SBC so when a user close to the SBC dials out to PSTN the media traffic (audio) will not be sent to Microsoft Phone System in the cloud it will go directly from client to SBC to SIP trunk.
thank you for your response. It seems to me that SBC in each location is the only way :(
I was first thinking about central service where interconnection with Teams would be done by central SBC located in Data Center. It shapes to an idea of having this connection only for locations with central SIP trunk break out and the other locations would need to install new SBC. I do believe that for such scenario vendors also provides floating license.
Thank you about info about location based routing, seems like something that would work for our travellers. Also make me believe that the topic about emergency calls would be also actual and easier with such setup. Media Bypass is definitely the feature I am looking forward :)
@DaveChomi Hi Dave, I've only just come across your post. However; this is something we can definitely assist you with. Please email firstname.lastname@example.org and we would be delighted to discuss your requirements further.