Onnowpurbo: /* Pranala Menarik */

2019-03-20T03:24:15Z

Pranala Menarik

← Older revision		Revision as of 03:24, 20 March 2019
Line 116:		Line 116:
	==Pranala Menarik==		==Pranala Menarik==

	* [[SIP: OpenVSX Video Conference Server]]		* [[ SIP: OpenVSX Video Conference Server]]

Onnowpurbo: /* External links */

2019-03-20T03:23:26Z

External links

← Older revision		Revision as of 03:23, 20 March 2019
Line 112:		Line 112:
	* [http://www.sipknowledge.com/rfc3261_explained_light.zip Formatted and explained PDF version of RFC 3261 including IMS related comments]		* [http://www.sipknowledge.com/rfc3261_explained_light.zip Formatted and explained PDF version of RFC 3261 including IMS related comments]
	* [http://www.sipknowledge.com/SIP_RFC.htm The entire list of SIP IETF RFCs]		* [http://www.sipknowledge.com/SIP_RFC.htm The entire list of SIP IETF RFCs]


			==Pranala Menarik==

			* [[SIP: OpenVSX Video Conference Server]]

Onnowpurbo: /* SIP network elements */

2009-12-20T23:12:54Z

SIP network elements

← Older revision		Revision as of 23:12, 20 December 2009
Line 44:		Line 44:
	:Various types of ''[[Gateway (telecommunications)\|gateways]]'' at the edge between a SIP network and other networks (as a phone network)		:Various types of ''[[Gateway (telecommunications)\|gateways]]'' at the edge between a SIP network and other networks (as a phone network)

	[[Image:SIP signaling.~~png~~]]		[[Image:SIP-signaling.jpg]]

	===SIP Messages===		===SIP Messages===

Onnowpurbo: New page: The '''Session Initiation Protocol''' ('''SIP''') is a signaling protocol, widely used for controlling multimedia communication sessions such as...

2009-12-20T23:10:41Z

New page: The '''Session Initiation Protocol''' ('''SIP''') is a signaling protocol, widely used for controlling multimedia communication sessions such as...

New page

The '''Session Initiation Protocol''' ('''SIP''') is a [[Signalling (telecommunications)|signaling]] protocol, widely used for controlling [[multimedia]] [[communication session]]s such as [[Internet telephony|voice]] and video calls over Internet Protocol (IP). The protocol can be used for creating, modifying and terminating two-party ([[unicast]]) or multiparty ([[multicast]]) [[session]]s consisting of one or several media streams. The modification can involve changing addresses or ports, inviting more participants, adding or deleting media [[stream]]s, etc. Other feasible application examples include [[video conferencing]], [[streaming multimedia]] distribution, [[instant messaging]], [[presence information]] and [[online game]]s.

SIP was originally designed by [[Henning Schulzrinne]] and [[Mark Handley (computer scientist)|Mark Handley]] starting in 1996. The latest version of the specification is RFC 3261 from the [[IETF]] Network Working Group. In November 2000, SIP was accepted as a [[3GPP]] signaling protocol and permanent element of the [[IP Multimedia Subsystem]] (IMS) architecture for IP-based streaming multimedia services in cellular systems.

The SIP protocol is a [[TCP/IP]]-based [[Application Layer]] protocol. SIP is designed to be independent of the underlying transport layer; it can run on [[Transmission Control Protocol]] (TCP), [[User Datagram Protocol]] (UDP), or [[Stream Control Transmission Protocol]] ([[SCTP]]). It is a text-based protocol, incorporating many elements of the [[Hypertext Transfer Protocol]] ([[HTTP]]) and the [[Simple Mail Transfer Protocol]] (SMTP), allowing for direct inspection by administrators.

==Protocol design==
SIP employs design elements similar to [[HTTP]]-like request/response transaction model. Each transaction consists of a client request that invokes a particular method or function on the server and at least one response. SIP reuses most of the header fields, encoding rules and status codes of HTTP, providing a readable text-based format.

SIP works in concert with several other protocols and is only involved in the signaling portion of a communication session. SIP clients typically use TCP or UDP on [[port number]]s 5060 and/or 5061 to connect to SIP servers and other SIP endpoints. Port 5060 is commonly used for non-encrypted signaling traffic whereas port 5061 is typically used for traffic encrypted with [[Transport Layer Security]] (TLS). SIP is primarily used in setting up and tearing down voice or video calls. It has also found applications in messaging applications, such as [[instant messaging]], and event subscription and notification. There are a large number of SIP-related [[Internet Engineering Task Force]] (IETF) documents ([[Request for Comments]]) that define behavior for such applications. The voice and video stream communications in SIP applications are carried over another application protocol, the [[Real-time Transport Protocol]] (RTP). Parameters (port numbers, protocols, codecs) for these media streams are defined and negotiated using the [[Session Description Protocol]] (SDP) which is transported in the SIP packet body.

A motivating goal for SIP was to provide a signaling and call setup protocol for [[Internet Protocol|IP]]-based communications that can support a superset of the call processing functions and features present in the [[public switched telephone network]] (PSTN). SIP by itself does not define these features; rather, its focus is call-setup and signaling. However, it was designed to enable the construction of functionalities of network elements designated proxy servers and user agents. These are features that permit familiar telephone-like operations: dialing a number, causing a phone to ring, hearing ringback tones or a busy signal. Implementation and terminology are different in the SIP world but to the end-user, the behavior is similar.

SIP-enabled telephony networks can also implement many of the more advanced call processing features present in [[Signaling System 7]] (SS7), though the two protocols themselves are very different. SS7 is a centralized protocol, characterized by a complex central network architecture and dumb endpoints (traditional telephone handsets). SIP is a [[peer-to-peer]] protocol, thus it requires only a simple (and thus scalable) core network with intelligence distributed to the network edge, embedded in endpoints (terminating devices built in either hardware or software). SIP features are implemented in the communicating endpoints (i.e. at the edge of the network) contrary to traditional SS7 features, which are implemented in the network.

Although several other [[VoIP]] [[signaling protocol]]s exist, SIP is distinguished by its proponents for having roots in the IP community rather than the telecommunications industry. SIP has been standardized and governed primarily by the IETF, while other protocols, such as [[H.323]], have been traditionally been associated with the [[International Telecommunication Union]] (ITU).

The first proposed standard version (SIP 2.0) was defined by RFC 2543. This version of the protocol was further refined and clarified in RFC 3261, although some implementations are still relying on the older definitions.

==SIP network elements==
A ''SIP user agent'' (UA) is a logical network end-point used to create or receive SIP messages and thereby manage a SIP session. A SIP UA can perform the role of a ''User Agent Client'' (UAC), which sends SIP requests, and the ''User Agent Server'' (UAS), which receives the requests and returns a SIP response. These roles of UAC and UAS only last for the duration of a SIP transaction.

A SIP phone is a hardware-based or software-based SIP user agent, that provides call functions such as dial, answer, reject, hold/unhold, and call transfer. Examples include [[softphone]]s such as [[Ekiga]], [[KPhone]], [[Twinkle (software)|Twinkle]], [[Windows Live Messenger]], [[X-Lite]], and hardware phones from vendors such as [[Avaya]], [[Cisco]], [[Leadtek]], [[Polycom]], [[Snom]], and [[Nokia]].

Each resource of a SIP network, such as a User Agent or a voicemail box, is identified by a [[Uniform Resource Identifier]] (URI), based on the general standard syntax also used in Web services and e-mail. A typical SIP URI is of the form: sip:username:password@host:port. The URI scheme used for SIP is ''sip:''. If secure transmission is required, the scheme ''sips:'' is used and SIP messages must be transported over [[Transport Layer Security]] (TLS).

In SIP, as in HTTP, the [[User Agent]] may identify itself using a message header field 'User-Agent', containing a text description of the software/hardware/product involved. The User-Agent field is sent in request messages, which means that the receiving SIP server can see this information. SIP network elements sometimes store this information, and it can be useful in diagnosing SIP compatibility problems.

SIP also defines server network elements. Although two SIP endpoints can communicate without any intervening SIP infrastructure, which is why the protocol is described as peer-to-peer, this approach is often impractical for a public service.

RFC 3261 defines these server elements:

:A ''proxy'' server "is an intermediary entity that acts as both a server and a client for the purpose of making requests on behalf of other clients. A proxy server primarily plays the role of routing, which means its job is to ensure that a request is sent to another entity "closer" to the targeted user. Proxies are also useful for enforcing policy (for example, making sure a user is allowed to make a call). A proxy interprets, and, if necessary, rewrites specific parts of a request message before forwarding it."

:"A ''[[SIP registrar|registrar]]'' is a server that accepts REGISTER requests and places the information it receives in those requests into the location service for the domain it handles."

:"A ''redirect server'' is a user agent server that generates 3xx responses to requests it receives, directing the client to contact an alternate set of URIs.The redirect server allows SIP Proxy Servers to direct SIP session invitations to external domains."

The RFC specifies: "It is an important concept that the distinction between types of SIP servers is logical, not physical."

Other SIP related network elements are
:''Session border controllers (SBC)'', they serve as "man in the middle" between UA and SIP server, see the article [[Session_Border_Controller|SBC]] for a detailed description.

:Various types of ''[[Gateway (telecommunications)|gateways]]'' at the edge between a SIP network and other networks (as a phone network)

[[Image:SIP signaling.png]]

===SIP Messages===
SIP is a text-based protocol with syntax similar to that of HTTP. There are two different types of SIP messages: requests and responses. The first line of a request has a ''method'', defining the nature of the request, and a Request-URI, indicating where the request should be sent. The first line of a response has a ''response code''.

For SIP requests, RFC 3261 defines the following methods:
* REGISTER: Used by a UA to notify its current IP address and the URLs for which it would like to receive calls.
* INVITE: Used to establish a media session between user agents.
* ACK: Confirms reliable message exchanges.
* CANCEL: Terminates a pending request.
* BYE: Terminates a session between two users in a conference.
* OPTIONS: Requests information about the capabilities of a caller, without setting up a call.

The SIP response types defined in RFC 3261 fall in one of the following categories:
* Provisional (1xx): Request received and being processed.
* Success (2xx): The action was successfully received, understood, and accepted.
* Redirection (3xx): Further action needs to be taken (typically by sender) to complete the request.
* Client Error (4xx): The request contains bad syntax or cannot be fulfilled at the server.
* Server Error (5xx): The server failed to fulfill an apparently valid request.
* Global Failure (6xx): The request cannot be fulfilled at any server.

==Instant messaging (IM) and presence==
The [[SIMPLE|Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE)]] is the SIP-based suite of standards for [[instant messaging]] and [[presence information]]. During an instant message session, files can be transferred using, for example, MSRP ([[Message Session Relay Protocol]]).

Some efforts have been made to integrate SIP-based [[VoIP]] with the [[Extensible Messaging and Presence Protocol|XMPP]] specification. Most notably [[Google Talk]], which extends XMPP to support voice, plans to integrate SIP. Google's XMPP extension is called [[Jingle (protocol)|Jingle]] and, like SIP, it acts as a [[Session Description Protocol]] carrier.

==Conformance testing==
[[TTCN-3]] test specification language is used for the purposes of specifying conformance tests for SIP implementations. SIP test suite is developed by a Specialist Task Force at [[ETSI]] (STF 196).

==Applications==
Many [[VoIP]] phone companies allow customers to bring their own SIP devices, as SIP-capable telephone sets, or [[softphone]]s. The market for consumer SIP devices continues to expand, there are many devices such as SIP Terminal Adapters, SIP Gateways etc.

The [[free software community]] started to provide more and more of the SIP technology required to build both end points as well as proxy and registrar servers leading to a commodification of the technology, which accelerates global adoption. [[SIPfoundry]] has made available and actively develops a variety of SIP stacks, client applications and SDKs, in addition to entire [[IP PBX]] solutions that compete in the market against mostly [[proprietary software|proprietary]] IP PBX implementations from established vendors.

The National Institute of Standards and Technology ([[NIST]]), Advanced Networking Technologies Division provides a public domain implementation of the JAVA Standard for SIP [http://jain-sip.dev.java.net JAIN-SIP] which serves as a [[reference implementation]] for the standard. The stack can work in proxy server or user agent scenarios and has been used in numerous commercial and research projects. It supports RFC 3261 in full and a number of extension RFCs including RFC 3265 (Subscribe / Notify) and RFC 3262 (Provisional Reliable Responses) etc.

==SIP-ISUP interworking==
SIP-I, or the Session Initiation Protocol with encapsulated [[ISDN User Part|ISUP]], is a protocol used to create, modify, and terminate communication sessions based on ISUP using SIP and IP networks. Services using SIP-I include voice, video telephony, fax and data. SIP-I and SIP-T are two protocols with similar features, notably to allow ISUP messages to be transported over SIP networks. This preserves all of the detail available in the ISUP header, which is important as there are many country-specific variants of ISUP that have been implemented over the last 30 years, and it is not always possible to express all of the same detail using a native SIP message. SIP-I was defined by the ITU-T, where SIP-T was defined via the [[IETF]] [[Request_for_Comments|RFC]] route.

==See also==
*[[List of SIP request methods]]
*[[List of SIP response codes]]
*[[List of SIP software]]
*[[List of SIP development tools]]
*[[H.323]]
*[[IP phone]]
*[[Media Gateway Control Protocol]] (MGCP)
*[[MSCML]] (Media Server Control Markup Language)
*[[IP Multimedia Subsystem]]
*[[Voice over Internet Protocol]]
*[[Mobile VoIP]]
*[[Private branch exchange]] (PBX)
*[[Session Initiation Protocol (Java)]]
*[[SIGTRAN]]
*[[Skinny Client Control Protocol]] (SCCP)
*[[Secure Real-time Transport Protocol]] (SRTP)
*[[ZRTP]]
*[[Network convergence]]
*[[XIMSS]]
*[[RTP audio video profile]]
*[[Message Session Relay Protocol]] (MSRP)

==External links==

* [http://www.cs.columbia.edu/sip/ Henning Schulzrinne's SIP homepage] hosted by Columbia University
* [http://www.sipknowledge.com/rfc3261_explained_light.zip Formatted and explained PDF version of RFC 3261 including IMS related comments]
* [http://www.sipknowledge.com/SIP_RFC.htm The entire list of SIP IETF RFCs]

SIP - Revision history

Onnowpurbo: /* Pranala Menarik */

Onnowpurbo: /* External links */

Onnowpurbo: /* SIP network elements */

Onnowpurbo: New page: The '''Session Initiation Protocol''' ('''SIP''') is a signaling protocol, widely used for controlling multimedia communication sessions such as...