All too often, SIP (Session Initiation Protocol) is associated only with VoIP.  It’s understandable, as the largest SIP deployments to date were done to move voice products (long distance, call centers, IVR, etc) from a TDM-based circuit-switch, to a packet-based IP architecture.  But voice is representative of a single example of what defines a “Session” in SIP.  SIP handles multiple forms of communications.  From quasi-realtime Instant Messaging to live video communications, all leveraging packet-based communications. 

The point above is very important to understand because SIP, as well as SIP Trunking provides the key foundational element to Unified Communications/Unified Collaboration (UC). In addition to cost savings and improved ROI as initial attractions, SIP Trunking’s ability to handle multiple communication strategies permits hybrid deployment models of solutions built for business communications, across both premised-based and hosted designs. 

UC (a present “buzz word” in the industry) is a prime example to show SIP Trunking’s capabilities.  UC designs are either premise-based (MS OCS, Sametime, etc), or hosted in a Service Provider’s network (i.e. Broadsoft’s Broadworks).  SIP Trunking enables a hybrid approach, which allows the Enterprise to leverage existing communication capabilities they may have (like email), with newer functionality, regardless of where it may reside.  Let’s take, for instance, an Enterprise that has premise-based messaging/collaboration tools (email, calendar, etc), and has recognized the demand to layer on voice conferencing capabilities.  Integrating the voice solution (either premise-based or hosted), via SIP Trunking into a hosted conferencing platform “in the sky” as in a “cloud” is not only possible, but makes sense.

Here’s an example of a business that uses Unified Communications to get work done.

 (Try to get around the MS utopian “koolaid” aspect of this promotional video, and focus on the modes of communication occurring)

http://www.youtube.com/watch?v=Ue8vow1Ficc

Though the solution here is MS-based, and a solution that is designed to be on a premise, note the gentlemen that dials into the initil ad hoc conference – this could (and is indeed nowadays happening) through SIP Trunking. I subtle and simple example of the hybrid approach, but one nonetheless.

SIP, and SIP Trunking lays the foundation for not only a more unified form of communications and collaboration, but also removes the barrier of a single-vendor approach.  Think “best of breed” solution building for communications.  SIP permits that possibility.

 Adam  Uzelac