r/MicrosoftTeams
Should I move to Direct Routing ?
- upvotes
- 5
- comments
- 12
Post
Hi All, For a 25-user SMB who heavily relies on phone calls, I have deployed Teams Phone using Operator Connect with Yealink MP54 E2 desk phones for a little under a year now, and the product's overall quality is clearly not up to the level of the good old Alcatel PBX it replaced (feeling shared both by the users and me alike). In this all-cloud context and after ruling out any on-prem network issues, it's hard to know whether the quality issues we face stem from (a) Teams (b) the phones (c) the telco provider or (d) all of the above. As an example, a common complaint we receive is that consult-transfer calls take at least 2 seconds to connect, while they were instant with our previous PBX: this may be due to the overall poor programming of Teams and the phone firmware, just as it could be due to a poor handling or performance on the telco provider's end, and we have no way of diagnosing it. Other issues include significant lag in calls despite the Teams network stats showing as perfect. I'm less likely to blame Teams or the phones on that one but... who knows ? I am inclined to get rid of the current Operator Connect solution and switch to Direct Routing given the numerous "pure SIP" issues we ran into and the very poor support we get from the current telco provider, but if I want to get the necessary budget (i.e. SBC and maintenance), I just can't say "it may or may...
Keep reading with a free account
The rest of this post, and every signal for Comcast, is in your free account.
Extracted from these lines
[comment u/Steve----O] I did direct routing with a Ribbon SWE Lite SBC VM and SIP service from Comcast Business. Way cheaper than OC, especially for international calls. The SIP service was only $500 a month for 300 DIDs and 30,000 minutes included per month.