22-04-2011, 10:48 AM
Presented by:
Ramesh G. Shihora
SIP - Session Initiation Protocol.doc (Size: 133.5 KB / Downloads: 128)
ABSTRACT
Session Initiation Protocol (SIP) is quickly gaining popularly with application service providers (ASPs), communication service providers(CSPs), and network service providers (NSPs) focused on offering their customers innovative, new IP - based services . Adopted in 1999 by the Internet Engineering Task Force (IETF) , SIP provides for the seamless transmission of voice, fax ,and data across IP and traditional telephone networks. The IETF defines SIP as “a text- based protocol, similar to HTTP and SMTP, for initiating interactive communication sessions between users. Such sessions include voice, video, chat, interactive games, and virtual reality.” SIP is used to establish peer-to-peer media sessions on an IP network including Internet telephony, conferencing ,instant messaging, and unified messaging. SIP has become a standard IETF protocol for signaling in third-generation mobile networking because it is able to initiate, modify “terminal independent.” This seminar report deals with basic overview of SIP: Session Initiation Protocol.
1.Introduction
SIP – A protocol that allows voice, data, fax, video, instant messaging and even online gaming to be integrated with web-based applications. The session initiation protocol (SIP) is emerging as the favored standard for setting up, modifying and terminating telephone calls over the internet. Its main things on the fly-in the hands of the user.
1.1 Definition
The Session Initiation Protocol (SIP) is an application –layer control (signaling) protocol for creating, modifying and terminating sessions with one or more participants.
These sessions include internet multimedia conferences, Internet telephone calls and multimedia distribution. A multimedia session is a set of multimedia senders and receivers and the data streams flowing from senders to receivers. Members in a session can communicate via multicast or via a mesh of unicast relations, or a combination of these.
1.2 History
SIP has its origins in late 1996 as a component of the “Mbones” set of utilities and protocols. The Mbone or multicast backbone was an experimental multicast network overplayed on top of the public internet. It was used for distribution of multimedia content, including talks and seminars, broadcasts of space shuttle launches and IETF meetings. One of its essential component was a mechanism for inviting users to listen an ongoing or future multimedia session on the internet. Basically – a session ignition protocol. Thus SIP was born.
As an Mbone tool, SIP was designed with certain assumptions in mind.
First was scalability ► Since users could reside anyware on the internet, the protocol needed to work wide-area from day one. User could be invited to lots of sessions, so the protocol needed to scale in both directions.
A second assumption was component reuse ► Rather than inventing new protocol tools those already developed within the IETF would be used. That includes things like MIME, URLS and SDP. This resulted in a protocol that integrated well with other IP applications(such as web and e-mail).
Despite its historical strengths SIP saw relatively slow progress thought 1999. That’s about when interest in internet telephony began to take off. People began to see SIP as a technology that would also work for VoIP, not just Mbone sessions. The result was an intensified effort towards completing the specification in late 1998, and completion by the end of the year. It received official approval as RFC (Request for Comments, the official term for an IETF standard) in February and issuance of an RFC number, 2543, in March.
Form there, industry acceptance of SIP grew exponentially. Its scalability, extensibility, and most important flexibility appealed to service providers and vendors who had needs that a vertically integrated protocol, such as H.323, could not address. Among services MIC ( particularly MIC’s Henry Sinnreich, regarded as the “Pope” of SIP ) led the evangelical charge. Throughout 1999 and 2000, it saw adoption by most major vendors, and announcements of networks by service providers. Interoperability bake offs were held thought 1999, attendance doubling at each successive event. Tremendous success was achieved in interoperability among vendors. Other standard bodies began to look at SIP as well, including ITU and ETSI, TIPHON, IMTC, soft switch consortium, and JAIN. Looking forward, 2000 will be a year in which real SIP networks are deployed, SIP vendors step forward to announce real products, and applications and services began to appear.
An Internet Engineering Task Force (IETF) standard, SIP is an open, internet genuine protocol for establishing and managing multi party, mixed media sessions over converged networks. SIP enables the creation and deployment of feature rich services that go far beyond simple VoIP calls.
Ramesh G. Shihora
SIP - Session Initiation Protocol.doc (Size: 133.5 KB / Downloads: 128)
ABSTRACT
Session Initiation Protocol (SIP) is quickly gaining popularly with application service providers (ASPs), communication service providers(CSPs), and network service providers (NSPs) focused on offering their customers innovative, new IP - based services . Adopted in 1999 by the Internet Engineering Task Force (IETF) , SIP provides for the seamless transmission of voice, fax ,and data across IP and traditional telephone networks. The IETF defines SIP as “a text- based protocol, similar to HTTP and SMTP, for initiating interactive communication sessions between users. Such sessions include voice, video, chat, interactive games, and virtual reality.” SIP is used to establish peer-to-peer media sessions on an IP network including Internet telephony, conferencing ,instant messaging, and unified messaging. SIP has become a standard IETF protocol for signaling in third-generation mobile networking because it is able to initiate, modify “terminal independent.” This seminar report deals with basic overview of SIP: Session Initiation Protocol.
1.Introduction
SIP – A protocol that allows voice, data, fax, video, instant messaging and even online gaming to be integrated with web-based applications. The session initiation protocol (SIP) is emerging as the favored standard for setting up, modifying and terminating telephone calls over the internet. Its main things on the fly-in the hands of the user.
1.1 Definition
The Session Initiation Protocol (SIP) is an application –layer control (signaling) protocol for creating, modifying and terminating sessions with one or more participants.
These sessions include internet multimedia conferences, Internet telephone calls and multimedia distribution. A multimedia session is a set of multimedia senders and receivers and the data streams flowing from senders to receivers. Members in a session can communicate via multicast or via a mesh of unicast relations, or a combination of these.
1.2 History
SIP has its origins in late 1996 as a component of the “Mbones” set of utilities and protocols. The Mbone or multicast backbone was an experimental multicast network overplayed on top of the public internet. It was used for distribution of multimedia content, including talks and seminars, broadcasts of space shuttle launches and IETF meetings. One of its essential component was a mechanism for inviting users to listen an ongoing or future multimedia session on the internet. Basically – a session ignition protocol. Thus SIP was born.
As an Mbone tool, SIP was designed with certain assumptions in mind.
First was scalability ► Since users could reside anyware on the internet, the protocol needed to work wide-area from day one. User could be invited to lots of sessions, so the protocol needed to scale in both directions.
A second assumption was component reuse ► Rather than inventing new protocol tools those already developed within the IETF would be used. That includes things like MIME, URLS and SDP. This resulted in a protocol that integrated well with other IP applications(such as web and e-mail).
Despite its historical strengths SIP saw relatively slow progress thought 1999. That’s about when interest in internet telephony began to take off. People began to see SIP as a technology that would also work for VoIP, not just Mbone sessions. The result was an intensified effort towards completing the specification in late 1998, and completion by the end of the year. It received official approval as RFC (Request for Comments, the official term for an IETF standard) in February and issuance of an RFC number, 2543, in March.
Form there, industry acceptance of SIP grew exponentially. Its scalability, extensibility, and most important flexibility appealed to service providers and vendors who had needs that a vertically integrated protocol, such as H.323, could not address. Among services MIC ( particularly MIC’s Henry Sinnreich, regarded as the “Pope” of SIP ) led the evangelical charge. Throughout 1999 and 2000, it saw adoption by most major vendors, and announcements of networks by service providers. Interoperability bake offs were held thought 1999, attendance doubling at each successive event. Tremendous success was achieved in interoperability among vendors. Other standard bodies began to look at SIP as well, including ITU and ETSI, TIPHON, IMTC, soft switch consortium, and JAIN. Looking forward, 2000 will be a year in which real SIP networks are deployed, SIP vendors step forward to announce real products, and applications and services began to appear.
An Internet Engineering Task Force (IETF) standard, SIP is an open, internet genuine protocol for establishing and managing multi party, mixed media sessions over converged networks. SIP enables the creation and deployment of feature rich services that go far beyond simple VoIP calls.