Forum Discussion
Force Teams-to-Teams calls to use Direct Routing SBC
Hi We're setting up SIP trunks for Teams, using Direct Routing. When a Teams user calls another Teams user, the call is handled "inside Teams" - it does not break out to our SBC. Is it possi...
We also need this.
We need the calls to the full E.164 number to route out to the SBC and not be handled within Teams. This is for the same reason as the OP, we have Teams "on-top" of our existing PBX and when someone in Teams dials the full E.164 number of another Teams user, it only rings in Teams. We need it to go out to the SBC and then to our PSTN so it can be presented on both Teams AND our existing PBX.
I was noodling on this earlier today, and the only way I could think of doing it for ALL PSTN calls would be to change the Teams users to not have the real number. In that, I mean do something like this:
- Assign Teams users something that can easily be manipulated to their real number, such as +1555555#### where #### is the real last 4 digits, and all 5s is made up.
- SBC routes calls to existing PBX or whatever handles the "multi-route" functionality
- Set "inbound" rules from MS Teams to SBC to change made up number to real number.
- Set "inbound" rules from MS Teams to SBC to change Caller ID from made up number to real number.
- Set "inbound" rules from SBC/PBX to Teams to change real number to made up number.
This would mean if a Teams user calls another Teams user PSTN number, there is no Teams based match, and the call will hit the SBC, where it is rewritten and passed onto the third party device. This won't fix Teams to Teams calls, and might not be worth the effort depending on the volume of your user-base.
It's absolutely not pretty, but might be workable. Has anybody checked UserVoice to see if there are any similar requests that can be voted on? If not, I'd suggest adding one, put links back here, and open a Support Ticket and ask if they have options as well.
jangliss I don't think our users would appreciate to see other/fake numbers, but that would actually work and I guess it would solve the issue for some providers. Not a pretty solution as you also mention, but technically it gives the functionality and the complete control of the call. +1 for creativity 😊
Most people find and click on a contact rather than dialing a phone number directly.
Even if the user enters another fake number and has it, we will have the same problem if we click on it to call.
