Aside from SIP, what are the other key architectural attributes for a successful unified communicati

Aside from SIP, what are the other key architectural attributes for a successful unified communicati

Aside from SIP, what are the other key architectural attributes for a successful unified communications (UC) deployment?

    Requires Free Membership to View

    SearchUnifiedCommunications.com members gain immediate and unlimited access breaking industry news, expert advice on UC, technical guides, and more -- all at no cost. Join me on SearchUnifiedCommunications.com today!

    Kate Gerwig, Editorial Director

    By submitting your registration information to SearchUnifiedCommunications.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchUnifiedCommunications.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

There are three main architectural attributes that I believe enable a solid foundation for unified communications (UC).

Session Initiation Protocol (SIP) is first, due to its open standards-approach and extensibility for multimodal/multimedia communications. In addition to SIP, service-oriented architecture (SOA) is a key building block for any UC software platform. SOA emphasizes a loosely coupled, re-usable service approach. In short, SOA helps ensure an open approach to constructing your software platform.

The building of services that can be re-used also sets the stage for the third attribute, which is web services. Web services with well-defined application programming interfaces (APIs) allow customers to realize the more advanced functions of UC, such as communications-enabled business processes (CEBPs) or workflows. This embedded approach tightly aligns the telephony and IT domains into a single entity.

The combination of the above really forms the basis for an open, flexible and easily integrated UC architecture. Ultimately, customers adopt UC to enhance the productivity and automate processes when possible. The architectural tenets above play a key role in ensuring that your UC platform is able to perform these functions.

This was first published in March 2009