SIP Response - Revision history

Pchero at 13:46, 3 February 2020

2020-02-03T13:46:28Z

← Older revision		Revision as of 13:46, 3 February 2020
Line 258:		Line 258:
	<references />		<references />

	[[category:~~telephony~~]]		[[category:SIP protocol]]

Pchero: /* See also */

2017-06-14T10:26:25Z

Pchero: /* 5xx Server Failure */

2017-06-14T10:25:37Z

5xx Server Failure

← Older revision		Revision as of 10:25, 14 June 2017
Line 201:		Line 201:

	5xx responses are failure responses given when a server itself has erred.		5xx responses are failure responses given when a server itself has erred.

			* 500 Server Internal Error
			: The server could not fulfill the request due to some unexpected condition.

	* 501 Not Implemented		* 501 Not Implemented

Pchero: /* 6xx Global Failures */

2017-04-04T08:58:48Z

6xx Global Failures

@@ Line 227: / Line 227: @@
 == 6xx Global Failures ==
 xx responses indicate that a server has definitive information about a particular user, not just the particular instance indicated in the Request-URI.
 == See also ==

Pchero: /* 5xx Server Failure */

2017-04-04T08:41:50Z

5xx Server Failure

← Older revision		Revision as of 08:41, 4 April 2017
Line 215:		Line 215:

	: Servers MAY refuse the connection or drop the request instead of responding with 503 (Service Unavailable).		: Servers MAY refuse the connection or drop the request instead of responding with 503 (Service Unavailable).

			* 504 Server Time-out
			: The server did not receive a timely response from an external server it accessed in attempting to process the request. 408 (Request Timeout) should be used instead if there was no response within the period specified in the Expires header field from the upstream server.

			* 505 Version Not Supported
			: The server does not support, or refuses to support, the protocol version that was used in the erquest. The server is indicating it is unable or unwilling to complete the request using the same major version as the client, other than with this error message.

			* 513 Message Too Large
			: The server was unable to process the request since the message length exceeded its capabilities.

			== 6xx Global Failures ==
			6xx responses indicate that a server has definitive information about a particular user, not just the particular instance indicated in the Request-URI.

	== See also ==		== See also ==

Pchero: /* 4xx Request Failure */

2017-04-03T08:26:32Z

4xx Request Failure

@@ Line 196: / Line 196: @@
 : Request 에 암호화된 MIME 바디를 포함하고 있어 처리할 수 없음을 의미한다.
 : The request was received by a UAS that contained an encrypted MIME body for which  the recipient does not possess or will not provide an appropriate decryption key. This response MAY have a single body containing an appropriate public key that should be used to encrypt MIME bodies sent to this UA.
 == See also ==

Pchero: /* 4xx Request Failure */

2017-03-31T13:37:10Z

4xx Request Failure

← Older revision		Revision as of 13:37, 31 March 2017
Line 178:		Line 178:
	* 486 Busy Here		* 486 Busy Here
	: 상대방을 성공적으로 연결했지만, 현재 상대방이 응대가능하지 않음을 의미한다.		: 상대방을 성공적으로 연결했지만, 현재 상대방이 응대가능하지 않음을 의미한다.
			: The callee's end system was contacted successfully, but the callee is currently not willing or able to take additional calls at this end system. The response MAY indicate a better time to call in the Retry-After header field. The user could also be available elsewhere, such as through a voice mail service. Status 600 (Busy Everywhere) SHOULD be used if the client knows that no other end system will be able to accept this call.

	* 487 Request Terminated		* 487 Request Terminated
	: Request 는 BYE 나 CANCEL 요청에 의해 종료되었음을 의미한다. CANCEL 요청에 대한 응답으로 사용되지는 않는다.		: Request 는 BYE 나 CANCEL 요청에 의해 종료되었음을 의미한다. CANCEL 요청에 대한 응답으로 사용되지는 않는다.
			: The request was terminated by a BYE or CANCEL request. This response is never returned for a CANCEL request itself.

	* 488 Not Acceptable Here		* 488 Not Acceptable Here
	: Request-URI 에 명기된 특정 자원이나 코덱을 사요할 수 없음을 의미한다.		: Request-URI 에 명기된 특정 자원이나 코덱을 사요할 수 없음을 의미한다.
			: The response has the same meaning as 606 (Not Acceptable), but only applies to the specific resource addressed by the Request-URI and the request may succeed elsewhere.
			: A message body containing a description of media capabilities MAY be present in the response, which is formatted according to the Accept header field in the INVITE(or application/sdp if not present), the same as a message body in a 200 (OK) response to an OPTIONS request.

	* 491 Request Pending		* 491 Request Pending
	: UAS 는 같은 다이얼로그안에 펜딩된 요청을 가지고 있음을 의미한다.		: UAS 는 같은 다이얼로그안에 펜딩된 요청을 가지고 있음을 의미한다.
			: The request was received by a UAS that had a pedning request within the same dialog.

	* 493 Undecipherable		* 493 Undecipherable
	: Request 에 암호화된 MIME 바디를 포함하고 있어 처리할 수 없음을 의미한다.		: Request 에 암호화된 MIME 바디를 포함하고 있어 처리할 수 없음을 의미한다.
			: The request was received by a UAS that contained an encrypted MIME body for which the recipient does not possess or will not provide an appropriate decryption key. This response MAY have a single body containing an appropriate public key that should be used to encrypt MIME bodies sent to this UA.

	== See also ==		== See also ==

Pchero: /* 4xx Request Failure */

2017-03-28T15:11:20Z

4xx Request Failure

← Older revision		Revision as of 15:11, 28 March 2017
Line 138:		Line 138:
	* 423 Interval Too Brief		* 423 Interval Too Brief
	: Request 에 의해 자원을 확보하기 위한 시간이 너무 부족함을 의미한다.		: Request 에 의해 자원을 확보하기 위한 시간이 너무 부족함을 의미한다.
			: The server is rejecting the request because the expiration time of the resource refreshed by the request is too short. This response can be used by a registrar to reject a registration whose Contact header field expiration time was too small. The use of this response and the related Min-Expires header field are descrbed in RFC 3261.

	* 480 Temporarily Unavailable		* 480 Temporarily Unavailable
	: 상대방을 성공적으로 연결하였지만, 현재 상대방이 응대 가능하지 않음을 의미한다. 예를 들면, 로그인은 했지만 통화가 안되거나 Do no disturb 기능을 이용 중일 경우이다.		: 상대방을 성공적으로 연결하였지만, 현재 상대방이 응대 가능하지 않음을 의미한다. 예를 들면, 로그인은 했지만 통화가 안되거나 Do no disturb 기능을 이용 중일 경우이다.
			: The callee's end system was contacted successfully but the callee is currently unavailable(for example, is not logged in, logged in but in a state that precludes communication with the calle, or has activated the "do not disturb" feature). The response MAY indicate a better time to call in the Retry-After header field. The user could also be available elsewhere (unbeknownst to this server). The reason phrase SHOULD indicate a more precise cause as to why the callee is unavailable. This value SHOULD be settable by the UA. Status 486(Busy Here) MAY be used to more precisely indicate a particular reason for the call failure.
			: This status is also returned by a redirect or proxy server that recognizes the user identified by the Request-URI, but does not currently have a valid forwarding location for that use.

	* 481 Call/Transaction Does not Exist		* 481 Call/Transaction Does not Exist
	: UAS가 기존 다이얼로그나 트랜잭션과 매치되지 않는 요청을 받았음을 의미한다.		: UAS가 기존 다이얼로그나 트랜잭션과 매치되지 않는 요청을 받았음을 의미한다.
			: This status indicates that the UAS received a request that does not match any existing dialog or transaction.

	* 482 Loop Detected		* 482 Loop Detected
	: UAS 가 루프 상황을 검출하였음을 의미한다. Via 헤더의 값을 통해서 전 서버에서 보낸 요청이 다시 돌아왔음을 알 수 있다.		: UAS 가 루프 상황을 검출하였음을 의미한다. Via 헤더의 값을 통해서 전 서버에서 보낸 요청이 다시 돌아왔음을 알 수 있다.
			: The server has detected a loop.

	* 483 Too Many Hops		* 483 Too Many Hops
	: 서버는 Max-Forwards 헤더 값이 0인 Request 를 받았음을 의미한다.		: 서버는 Max-Forwards 헤더 값이 0인 Request 를 받았음을 의미한다.
			: The server received a request that contains a Max-Forwards header field with the value zero.

	* 484 Address Incomplete		* 484 Address Incomplete
	: 서버는 불완전한 Request-URI 를 가진 Request 를 받았음을 의미한다.		: 서버는 불완전한 Request-URI 를 가진 Request 를 받았음을 의미한다.
			: The server received a request with a Request-URI that was incomplete. Additional information SHOULD be provided in the reason phrase.
			: This status code allows overlapped dialing. With overlapped dialing, the client does not know the length of the dialing string. It sends strings of increasing lengths, prompting the user for more input, until it no longer receives a 484(Address Incomplete) status response.

	* 485 Ambiguous		* 485 Ambiguous
	: 서버는 애매모호한 Request-URI 를 가진 Request 를 받았음을 의미한다. 서버는 응답시에 Contact 헤더에 명확한 주소를 리스팅한다.		: 서버는 애매모호한 Request-URI 를 가진 Request 를 받았음을 의미한다. 서버는 응답시에 Contact 헤더에 명확한 주소를 리스팅한다.
			: The Request-URI was ambiguous. The response MAY contain a listing of possible unambiguous addresses in Contact header fields. Revealing alternatives can infringe on privacy of the user or the organization. It MUST be possible to configure a server to response with status 404(Not Found) or to suppress the listing of possible choices for ambiguous Request-URIs.
			: Example response to a request with the Request-URI.
			<pre>
			sip:lee@example.com:

			SIP/2.0 485 Ambiguous
			Contact: Carol Lee <sip:carol.lee@example.com>
			Contact: Ping Lee <sip:p.lee@example.com>
			Contact: Lee M. Foote <sips:lee.foote@example.com>
			</pre>
			: Some email and voice mail systems provide this functionality. A status code separate from 3xx is used since the semantics are different: for 300, it is assumed that the same person or service will be reached by the choices provieded. While an automated choice or sequential search makes sense for a 3xx response, user intervention is required for a 485 (Ambiguous) response.

	* 486 Busy Here		* 486 Busy Here

Pchero: /* 4xx Request Failure */

2017-03-28T14:25:39Z

4xx Request Failure

← Older revision		Revision as of 14:25, 28 March 2017
Line 114:		Line 114:
	* 413 Request Entity Too Large		* 413 Request Entity Too Large
	: Request 의 내용이 서버가 처리할 수 있는 것보다 너무 큼을 의미한다. 일시적인 상황일 경우 Retry-After 헤더로 UAC가 재시도 할 수 있음을 표시한다.		: Request 의 내용이 서버가 처리할 수 있는 것보다 너무 큼을 의미한다. 일시적인 상황일 경우 Retry-After 헤더로 UAC가 재시도 할 수 있음을 표시한다.
	: The server is refusing to process a request because the request entity-body is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request. ~~Ifthe~~ condition is temporary, the server SHOULD include a Retry-After header filed to indicate that it is temporary and after what time the client MAY try again.		: The server is refusing to process a request because the request entity-body is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request. If the condition is temporary, the server SHOULD include a Retry-After header filed to indicate that it is temporary and after what time the client MAY try again.

	*415 Unsupported Media Type		* 414 Request-URI Too Long
			: The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.

			* 415 Unsupported Media Type
	: 서버는 메시지 바디에 서버가 지원되지 않는 포멧으로 요청함을 의미한다. 서버는 반드시 Accept, Accept-Encoding, 또는 Accept-Language 헤더 등을 이용하여 응답해야 한다.		: 서버는 메시지 바디에 서버가 지원되지 않는 포멧으로 요청함을 의미한다. 서버는 반드시 Accept, Accept-Encoding, 또는 Accept-Language 헤더 등을 이용하여 응답해야 한다.
			: The server is refusing to service the request because the message body of the request is in a format not supported by the server for the requested method. The server MUST return a list of acceptable formats using the Accept, Accept-Encoding, or Accept-Language header field, depending on the specific problem with the content. UAC processing of this response.

	* 416 Unsupported URI Scheme		* 416 Unsupported URI Scheme
	: Request-URI 스킴을 서버가 해석할 수 없음을 의미한다.		: Request-URI 스킴을 서버가 해석할 수 없음을 의미한다.
			: The server cannot process the request because the scheme of the URI in the Request-URI is unkown to the server. Client processing of this response.

	* 420 Bad Extension		* 420 Bad Extension
	: 서버는 Proxy-Require 나 Require 헤더에 정의된 Extension (확장)을 이해하지 못함을 의미한다. 서버는 반드시 Unsupported Header에 지원하지 않는 Extension 을 명기하여 응답한다.		: 서버는 Proxy-Require 나 Require 헤더에 정의된 Extension (확장)을 이해하지 못함을 의미한다. 서버는 반드시 Unsupported Header에 지원하지 않는 Extension 을 명기하여 응답한다.
			: The server did not understand the protocol extension specified in a Proxy-Require or Require header field. The server MUST include a list of the unsupported extensions in an Unsupported header field in the response. UAC processing of this response.

	* 421 Extension Required		* 421 Extension Required
	: UAS는 Request 를 처리하기 위해 특정 Extension 이 필요하지만, Supported Header 에 명기되지 않았음을 의미한다. UAS는 응답시에 Require 헤더에 필요한 Extension 을 명기해야 한다.		: UAS는 Request 를 처리하기 위해 특정 Extension 이 필요하지만, Supported Header 에 명기되지 않았음을 의미한다. UAS는 응답시에 Require 헤더에 필요한 Extension 을 명기해야 한다.
			: The UAS needs a particular extension to process the request, but this extension is not listed in a Supported header field in the request. Responses with this status code MUST contain a Require header field listing the required extensions.
			: A UAS SHOULD NOT use this response unless it truly cannot provide any useful service to the client. Instead, if a desirable extension is not listed in the Supported header field, servers SHOULD process the request using baseline SIP capabilities and any extensions supported by the client.

	* 423 Interval Too Brief		* 423 Interval Too Brief

Pchero: /* 4xx Request Failure */

2017-03-28T14:10:16Z

4xx Request Failure

← Older revision		Revision as of 14:10, 28 March 2017
Line 106:		Line 106:
	* 408 Request Timeout		* 408 Request Timeout
	: 일정 시간안에 Request에 대한 응답을 할 수 없다.		: 일정 시간안에 Request에 대한 응답을 할 수 없다.
			: The server could not produce a response within a suitable amount of time, for example, if it could not determine the location of the user in time. The client MAY repeat the request without modifications at any later time.

	* 410 Gone		* 410 Gone
	: 요청한 자원이 서버에서 소정적으로 이용가능하지 않는다.		: 요청한 자원이 서버에서 소정적으로 이용가능하지 않는다.
			: The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404(Not found) SHOULD be used instead.

	* 413 Request Entity Too Large		* 413 Request Entity Too Large
	: Request 의 내용이 서버가 처리할 수 있는 것보다 너무 큼을 의미한다. 일시적인 상황일 경우 Retry-After 헤더로 UAC가 재시도 할 수 있음을 표시한다.		: Request 의 내용이 서버가 처리할 수 있는 것보다 너무 큼을 의미한다. 일시적인 상황일 경우 Retry-After 헤더로 UAC가 재시도 할 수 있음을 표시한다.
			: The server is refusing to process a request because the request entity-body is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request. Ifthe condition is temporary, the server SHOULD include a Retry-After header filed to indicate that it is temporary and after what time the client MAY try again.

	*415 Unsupported Media Type		*415 Unsupported Media Type

← Older revision		Revision as of 10:26, 14 June 2017
Line 252:		Line 252:

	== See also ==		== See also ==
			* https://en.wikipedia.org/wiki/List_of_SIP_response_codes - List of SIP response codes
	* http://www.nexpert.net/494 - 다시쓰는 SIP의 이해 - 10편 Chapter 4. SIP Response		* http://www.nexpert.net/494 - 다시쓰는 SIP의 이해 - 10편 Chapter 4. SIP Response