Unifying Unified Communications

The concept of unified communications is one of simplification: The goal is to maximize communications by making it easier for users to move between voice, video and data-based services. Most definitions of UC include presence – the platform’s awareness of where group members are and what communications tools they have access to -- and the ability to change which channel is being used during the session.

“Put yourself in the shoes of a typical IT department and think of the pressure of what they are dealing with today and whether they want to deal with it or seek outside help.”

     
Erik Rudin
NetIQ

The result, for the end user, is a far more organized and directed way of communicating with employees, partners and customers. But, as often is the case in technology, simplifying things for customers leads to an increase in complexity for those providing the service. The drive to efficiently provide these services is deeply interconnected with the need for standards and other ways of linking and organizing these disparate elements – which are at different points in their internal evolution – into a coherent whole.

In a general sense, there are three levels at which UC tools and systems must be able to efficiently work together:

* The first level is the different communications channels themselves. This level of standards already is established, even if some firms still work in a non-standard – proprietary – fashion. For instance, the world of VoIP increasingly is adopting the Session Initiation Protocol (SIP) as a means of establishing, managing voice calls. Likewise, the video world uses the H.323 standard as a way to traffic video. These disparate standards efforts are independent of any holistic UC structure.

* The middle level of UC standards deals with the amalgamation of the different communications channels, “modalities,” in the fancy vernacular used by some in the UC field, into systems that work together efficiently. This can be called the “intra vendor” level. A UC platform from a vendor can either be cobbled together superficially or linked at a deeper level. The latter is far more efficient in terms of management capabilities and eliminating redundancies.

* The highest level is enabling UC systems from different vendors to communicate with each other. There are many instances in which it behooves organizations to link systems together. For instance, companies suddenly married via an acquisition are as likely as not to have different UC vendors. Likewise, companies embarking on long-term relationships requiring close cooperation would benefit from UC connectivity. These firms also may have different UC vendors.

Comments

To your point of trading traffic being vital, we make our living normalizing "standards" based solution that are masking pockets of propriety. As an example, we sit in the cloud - outside the customer network - and move real-time routing, control, monitoring and interoperability out of the LAN-based PBXs. It is essential to normalize the traffic into a common SOA-based session layer. Our goal, with our interface on the far-side of the customer cloud, is to provide normalization and eliminate the challenge inherent in direct point-to-point communications between the clients and servers. So my view is that the future of UC will depend on the extending the solution into a cloud, with a primary objective of making two pieces of gear speak with one another. We have found that this approach and capability makes it much easier for organizations to reduce costs further. Customer do this by leveraging the cloud to provide the necessary interoperability of mission-critical communication services, between disparate components, that would be unattainable in the short-term on the enterprise network. How would you make a Cisco talk to a ShoreTel? If you asked me, I'd simply point at the cloud. I think organizations like the SIP Forum with the SIP Connect are providing the dialog and the roadmap necessary to sort this mess out - but in the mean time, firms like EtherSpeak are here, making our business to develop the cloud to normalize the "interoperability" problem that you describe as it is a serious issue for both customers and manufacturers alike. The future is in the cloud - not on the LAN. Sincerely, Neil Darling EtherSpeak

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
  • Allowed HTML tags: <b> <i>

More information about formatting options