My SIP notes - Revision history

Paul: Added RTP Payload for Text Conversation RFC

2019-10-31T21:56:11Z

Added RTP Payload for Text Conversation RFC

← Older revision		Revision as of 16:56, 31 October 2019
Line 217:		Line 217:

	SDP: Session Description Protocol [https://tools.ietf.org/html/rfc4566 RFC 4566]		SDP: Session Description Protocol [https://tools.ietf.org/html/rfc4566 RFC 4566]

			RTP Payload for Text Conversation [https://tools.ietf.org/html/rfc4103 RFC 4103]

	[https://thanhloi2603.wordpress.com/2017/05/28/introduction-to-sip-bye-cancel-and-hop-by-hop-messages/ Introduction to SIP BYE CANCEL and hop-by-hop messages]		[https://thanhloi2603.wordpress.com/2017/05/28/introduction-to-sip-bye-cancel-and-hop-by-hop-messages/ Introduction to SIP BYE CANCEL and hop-by-hop messages]

Paul: added SDP RFC

2019-10-31T19:45:11Z

added SDP RFC

← Older revision		Revision as of 14:45, 31 October 2019
Line 215:		Line 215:

	SIP: Session Initiation Protocol [https://tools.ietf.org/html/rfc3261 RFC 3261]		SIP: Session Initiation Protocol [https://tools.ietf.org/html/rfc3261 RFC 3261]

			SDP: Session Description Protocol [https://tools.ietf.org/html/rfc4566 RFC 4566]

	[https://thanhloi2603.wordpress.com/2017/05/28/introduction-to-sip-bye-cancel-and-hop-by-hop-messages/ Introduction to SIP BYE CANCEL and hop-by-hop messages]		[https://thanhloi2603.wordpress.com/2017/05/28/introduction-to-sip-bye-cancel-and-hop-by-hop-messages/ Introduction to SIP BYE CANCEL and hop-by-hop messages]

Paul: /* A unified communications blog by Andrew Prokop */

2019-10-31T18:08:20Z

A unified communications blog by Andrew Prokop

← Older revision		Revision as of 13:08, 31 October 2019
Line 219:		Line 219:

	=== A unified communications blog by Andrew Prokop ===		=== A unified communications blog by Andrew Prokop ===
	A good resource for all things SIP.		'''A good resource for all things SIP.'''

	[https://andrewjprokop.wordpress.com/ SIP Adventures]		[https://andrewjprokop.wordpress.com/ SIP Adventures]

	Articles of interest		Articles of interest

	[https://andrewjprokop.wordpress.com/2013/09/27/dtmf-and-rfc-2833-4733/ DTMF AND RFC 2833 / 4733]		[https://andrewjprokop.wordpress.com/2013/09/27/dtmf-and-rfc-2833-4733/ DTMF AND RFC 2833 / 4733]


	<center>[[Networking\|To Networking]]</center>		<center>[[Networking\|To Networking]]</center>

Paul: added SIP Adventures blog section

2019-10-31T17:40:08Z

added SIP Adventures blog section

← Older revision		Revision as of 12:40, 31 October 2019
Line 217:		Line 217:

	[https://thanhloi2603.wordpress.com/2017/05/28/introduction-to-sip-bye-cancel-and-hop-by-hop-messages/ Introduction to SIP BYE CANCEL and hop-by-hop messages]		[https://thanhloi2603.wordpress.com/2017/05/28/introduction-to-sip-bye-cancel-and-hop-by-hop-messages/ Introduction to SIP BYE CANCEL and hop-by-hop messages]

			=== A unified communications blog by Andrew Prokop ===
			A good resource for all things SIP.
			[https://andrewjprokop.wordpress.com/ SIP Adventures]
			Articles of interest
			[https://andrewjprokop.wordpress.com/2013/09/27/dtmf-and-rfc-2833-4733/ DTMF AND RFC 2833 / 4733]


	<center>[[Networking\|To Networking]]</center>		<center>[[Networking\|To Networking]]</center>

Paul: /* SIP messages */

2019-03-23T23:00:25Z

SIP messages

← Older revision		Revision as of 18:00, 23 March 2019
Line 122:		Line 122:
	<pre>Request-Line = Method SP Request-URI SP SIP-Version CRLF</pre>		<pre>Request-Line = Method SP Request-URI SP SIP-Version CRLF</pre>

			'''SIP Requests'''
			<pre>INVITE = establishes a session
			ACK = confirms INVITE request
			BYE = ends a session
			CANCEL = cancels establishing of a session
			REGISTER = communicates user location (host name, IP)
			OPTIONS = communicates information about the capabilities of the calling and receiving SIP phones
			PRACK = provisional acknowledgement
			SUBSCRIBE = subscribes for notification from the notifier
			NOTIFY = notifies the subscriber of a new event
			PUBLISH = publishes an event to server
			INFO = sends mid-session information
			REFER = asks recipient to issue call transfer
			MESSAGE = transports instant messages
			UPDATE = modifies the state of a session</pre>
	=== Responses ===		=== Responses ===

Line 136:		Line 151:
	The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role. For this reason, any response with a status code between 100 and 199 is referred to as a "1xx response", any response with a status code between 200 and 299 as a "2xx response", and so on. SIP/2.0 allows six values for the first digit:		The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role. For this reason, any response with a status code between 100 and 199 is referred to as a "1xx response", any response with a status code between 200 and 299 as a "2xx response", and so on. SIP/2.0 allows six values for the first digit:

	<pre>1xx: Provisional -- request received, continuing to process the request;		'''SIP Responses'''
			<pre>1xx: Provisional -- request received, continuing to process the request
	2xx: Success -- the action was successfully received, understood, and accepted;		2xx: Success -- the action was successfully received, understood, and accepted
			3xx: Redirection -- further action needs to be taken in order to complete the request
	3xx: Redirection -- further action needs to be taken in order to complete the request;		4xx: Client Error -- the request contains bad syntax or cannot be fulfilled at this server
			5xx: Server Error -- the server failed to fulfill an apparently valid request
	4xx: Client Error -- the request contains bad syntax or cannot be fulfilled at this server;		6xx: Global Failure -- the request cannot be fulfilled at any server</pre>

	5xx: Server Error -- the server failed to fulfill an apparently valid request;

	6xx: Global Failure -- the request cannot be fulfilled at any server.</pre>

	[https://tools.ietf.org/html/rfc3261#section-21 Section 21] defines these classes and describes the individual codes.		[https://tools.ietf.org/html/rfc3261#section-21 Section 21] defines these classes and describes the individual codes.

Paul: /* SIP Resources */

2018-10-12T23:29:43Z

SIP Resources

← Older revision		Revision as of 18:29, 12 October 2018
Line 205:		Line 205:
	SIP: Session Initiation Protocol [https://tools.ietf.org/html/rfc3261 RFC 3261]		SIP: Session Initiation Protocol [https://tools.ietf.org/html/rfc3261 RFC 3261]

			[https://thanhloi2603.wordpress.com/2017/05/28/introduction-to-sip-bye-cancel-and-hop-by-hop-messages/ Introduction to SIP BYE CANCEL and hop-by-hop messages]


	<center>[[Networking\|To Networking]]</center>		<center>[[Networking\|To Networking]]</center>

Paul: /* Header fields */

2018-08-06T23:12:58Z

Header fields

@@ Line 150: / Line 150: @@
 [https://tools.ietf.org/html/rfc3261#section-21 Section 21] defines these classes and describes the individual codes.
-=== Header fields ===
+=== Header Fields ===
 == SIP Resources ==

Paul: /* Responses */

2018-08-06T18:55:15Z

Responses

← Older revision		Revision as of 13:55, 6 August 2018
Line 149:		Line 149:

	[https://tools.ietf.org/html/rfc3261#section-21 Section 21] defines these classes and describes the individual codes.		[https://tools.ietf.org/html/rfc3261#section-21 Section 21] defines these classes and describes the individual codes.

			=== Header fields ===

	== SIP Resources ==		== SIP Resources ==

Paul: /* Responses */

2018-08-06T18:54:20Z

Responses

← Older revision		Revision as of 13:54, 6 August 2018
Line 133:		Line 133:

	The Status-Code is a 3-digit integer result code that indicates the outcome of an attempt to understand and satisfy a request. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use by automata, whereas the Reason-Phrase is intended for the human user. A client is not required to examine or display the Reason-Phrase.		The Status-Code is a 3-digit integer result code that indicates the outcome of an attempt to understand and satisfy a request. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use by automata, whereas the Reason-Phrase is intended for the human user. A client is not required to examine or display the Reason-Phrase.

			The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role. For this reason, any response with a status code between 100 and 199 is referred to as a "1xx response", any response with a status code between 200 and 299 as a "2xx response", and so on. SIP/2.0 allows six values for the first digit:

			<pre>1xx: Provisional -- request received, continuing to process the request;

			2xx: Success -- the action was successfully received, understood, and accepted;

			3xx: Redirection -- further action needs to be taken in order to complete the request;

			4xx: Client Error -- the request contains bad syntax or cannot be fulfilled at this server;

			5xx: Server Error -- the server failed to fulfill an apparently valid request;

			6xx: Global Failure -- the request cannot be fulfilled at any server.</pre>

			[https://tools.ietf.org/html/rfc3261#section-21 Section 21] defines these classes and describes the individual codes.

	== SIP Resources ==		== SIP Resources ==

Paul: /* SIP messages */

2018-08-06T18:52:00Z

SIP messages

← Older revision		Revision as of 13:52, 6 August 2018
Line 111:		Line 111:

	However, SIP is not an extension of HTTP.		However, SIP is not an extension of HTTP.

			=== Requests ===

			[https://tools.ietf.org/html/rfc3261#section-7.1 SIP Requests]

			SIP requests are distinguished by having a Request-Line for a start-line. A Request-Line contains a method name, a Request-URI, and the protocol version separated by a single space (SP) character.

			The Request-Line ends with CRLF. No CR or LF are allowed except in the end-of-line CRLF sequence. No linear whitespace (LWS) is allowed in any of the elements.

			<pre>Request-Line = Method SP Request-URI SP SIP-Version CRLF</pre>

			=== Responses ===

			[https://tools.ietf.org/html/rfc3261#section-7.2 SIP Responses]

			SIP responses are distinguished from requests by having a Status-Line as their start-line. A Status-Line consists of the protocol version followed by a numeric Status-Code and its associated textual phrase, with each element separated by a single SP character.

			No CR or LF is allowed except in the final CRLF sequence.

			<pre>Status-Line = SIP-Version SP Status-Code SP Reason-Phrase CRLF</pre>

			The Status-Code is a 3-digit integer result code that indicates the outcome of an attempt to understand and satisfy a request. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use by automata, whereas the Reason-Phrase is intended for the human user. A client is not required to examine or display the Reason-Phrase.

	== SIP Resources ==		== SIP Resources ==