What does it mean to be truly SIP based?
Session Initiation Protocol (SIP), a data-centric protocol, is designed for flexibility in the enablement of unified communication solutions, including those that can be tied to specific business processes. But SIP today still comes in two fundamental architectural configurations. For example, many so-called SIP network platforms still use proprietary call control protocols. With such systems, SIP compliance or interoperability is merely added on to the back end, requiring that a third-party communication application must always report back to a proprietary, computer-telephony integration (CTI) interface (H.323, for example) for call control.
However, a truly native SIP communication solution is built – from the ground up – with SIP as the underlying call control protocol. In other words, a true SIP system is built completely open to other standards-based architectures and applications such as those built on Extensible Markup Language (XML) and Simple Object Access Protocol (SOAP).
This Content Component encountered an error
How many user agents (both clients and server) can participate in a SIP conference? And how many in an H.323 conference?continue reading
Can you provide some real-world benefits of deploying SIP?continue reading
Will vendors really give up proprietary protocols in support of SIP or at least find a way to coexist? Expert Bob Thompson offers his perspective.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.