Reports highlight UC in business apps, centralized and distributed SIP trunking

Today, we'd like to point out some highlights from two recent reports. The first report, "UC Evolves to Enhance Business Applications," was written by industry analyst and UC expert (and Network World blogger) Zeus Kerravala. The second piece is a white paper provided by Oracle titled "Centralized vs. Distributed SIP Trunking: Making an Informed Decision."

In his research, Kerravala points out that while apps are "ubiquitous on personal devices, the promise of a similar variety of business applications is slower to emerge." He also notes the importance of enterprise mobility developing in parallel with the evolution of cloud computing, devices, and wireless technology creating what he considers "a perfect storm, driving businesses towards mobility and innovation at a rate never seen before."

Kerravala continues by suggesting that four evolutionary steps are needed to more fully enable UC--and to help it reach mass market attraction. He also reviews some of the challenges with UC integration, looking at the Avaya Aura Collaboration Environment addresses the issues. He concludes with three case studies that outline successful integration efforts.

The Oracle white paper explains the benefits of SIP trunking services -- also looking at deployment options and implementation challenges. The paper offers a detailed review of the pros and cons of a distributed vs. a centralized infrastructure. For example, a centralized topology offers the greatest potential cost savings, but requires more up-front analysis and network engineering. The distributed approach provides a simpler transition, but may not save as much money over the long run. The SIP trunking paper concludes with a discussion on how enterprise session border controllers (E-SBCs) streamline SIP trunk installations while ensuring high reliability and service quality for IP communications.

Both papers are available free of charge at Webtorials by clicking here. (Disclaimer:  I work as the Editorial Director at Webtorials, but did not have a hand in creating these reports. )