Session Initiation Protocol (SIP)
Metreos offers a number of products that will help your organization get the most out of its IP telephony investment using SIP and other protocols.
SIP Applications
Metreos offers a number of packaged applications that use SIP such as:
- RapidRecord
Records all calls placed to and from a specified set of IP phones, and can also be used by end users to selectively record calls they make or receive. - More
Other Metreos packaged applications such as Click-to-Talk and Paging & Intercom also can be easily deployed using SIP.
SIP Developer Tools
The Metreos Visual Designer is a visual integrated development environment (IDE) for rapid VoIP development. It enables developers from the data center (who may lack IP telephony development experience) to easily and rapidly develop applications - using SIP and other major protocols - to converge voice with enterprise applications and data. Using this approach, development time for new VoIP applications is dramatically reduced to days rather than weeks or months, and maintenance of applications is made much faster and easier.
SIP Application Environment
The Metreos Application Environment is the industry's first and only complete application environment for VoIP. It includes the Metreos Application Runtime, Metreos Media Engine, Metreos Management Console and Metreos Visual Designer. The Metreos Application Environment includes support for SIP, as well as a variety of other protocols such as JTAPI, SCCP, H.323, Cisco Extension Mobility and Cisco IP Phone Services.
About the SIP Protocol
The SIP protocol is an IETF standard for establishing multimedia sessions. These sessions may be used for audio, video, instant messaging, or other real-time data communication sessions.
Building a complete system that uses the SIP protocol requires the application developer to read and understand the base SIP protocol specification plus any number of protocol documents that are targeted for a particular application. For example, the use of the SIP protocol for instant messaging is defined separately from the use of the SIP protocol within VoIP, which requires the developer to be familiar with the SDP protocol รณ an entirely separate RFC.
The scope of the SIP protocol is relatively broad, including establishing virtually any kind of session between two parties. The SIP protocol is also entirely independent of the underlying transport, although TCP and UDP are used almost exclusively.
The SIP protocol was initially published as an Internet Draft by the IETF in 1996, with the first RFC in 1999. As of this writing, the most recent SIP specification is published in RFC 3261.
