What’s the Next Big Thing in Unified Communications? Software-Defined WANs!
**Note: Mitel market cap calculated post acquisition price
In UC, UCaaS is where the growth is and it’s going to pull SD-WAN along for the ride. One reason why there wasn’t much interest in networking by the UC audience before is that VoIP and video were primarily LAN-based technologies, where bandwidth was abundant. In many cases, organizations would replicate their older TDM architectures when they moved to IP. All locations with a large number of users had their own call control platform, making it easy to control quality on the network.
With UCaaS, voice and video come from the cloud. The inefficiencies of hub-and-spoke are magnified with real time traffic. Consider migrating to UCaaS without evolving the WAN. Traffic from a UCaaS provider to a branch worker would enter into the organization at its single point of ingress with every other users’ traffic, travel across the WAN to the branch, then hairpin in the branch, head down the same WAN path and back out where it entered. This is the most inefficient network design for the cloud possible. With non-real time traffic, like e-mail or document sharing, the latency this architecture introduces might be annoying, but doesn’t impair worker productivity in any dramatic way — although it is a waste of bandwidth, but that’s a topic of another discussion. Don’t Let Your Cloud UC Migration Backfire
With real-time traffic, the inefficiencies of the network can cause voice to be choppy and unintelligible, and video to be unusable. Companies spend a significant amount of time, money, and energy migrating from a legacy, on-premise solution to the cloud, and not having the right network underneath it can obviate much of the ROI that businesses are hoping to achieve. I’ve talked to many organizations that migrated their UC to the cloud without changing the underlying network, and they wound up quickly reverting to an on-premise solution.
While this is certainly a choice, it’s the wrong one. The future of UC lies in artificial intelligence, mobility, and predictive communications, and that’s best done in the cloud since most organizations don’t have either the data or the compute capacity to fuel initiatives like AI. The better choice would have been to transition to an SD-WAN designed to support the next generation communications solution.
With an SD-WAN, businesses can easily move to a split tunnel architecture with local internet breakout , enabling users to access UCaaS services directly from the branch in a single hop. This is dramatically more efficient than having to traverse the corporate WAN multiple times. The reduction of WAN traffic also means that branch-to-branch calls that do need to cross the company network won’t be competing with external calls, improving those calls’ performance as well. Also, the direct-to-branch approach means businesses with a large number of branch offices won’t require as large an internet pipe as they previously did.
UCaaS is certainly the way of the future, and businesses of all sizes should be aggressive in executing their migration plans. However, it’s important to understand the role of the network — particularly the WAN — and migrate to an SD-WAN in conjunction with any cloud-planned UC deployment.
(This article first appeared here ). Categories