Jump to content

List of SIP response codes: Difference between revisions

Edit links
From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
No edit summary
(One intermediate revision by the same user not shown)
Line 2: Line 2:


== 1xx—Informational Responses ==
== 1xx—Informational Responses ==
* 100 Trying (Extended search being performed may take a significant time so a forking proxy must send a 100 Trying response)
;{{anchor |100}}100 Trying
: Extended search being performed may take a significant time so a forking proxy must send a 100 Trying response
* 180 Ringing
;{{anchor |180}}180 Ringing
: Destination user agent received INVITE, and is alerting user of call.<ref name="RFC_3261">{{cite IETF
⚫
* 181 Call is Being Forwarded
| title = SIP: Session Initiation Protocol
⚫
* 182 Queued
| rfc = 3261
⚫
* 183 Session in Progress
| last1 = Rosenberg
| first1 = J.
| last2 = Schulzrinne
| first2 = H.
| last3 = Camarillo
| first3 = G.
| last4 = Johnston
| first4 = A.
| last5 = Peterson
| first5 = F.
| last6 = Sparks
| first6 = R.
| last7 = Handley
| first7 = M.
| last8 = Schooler
| first8 = E.
| year = 2002
| month = June
| publisher = [[Internet Engineering Task Force|IETF]]
| accessdate = January 20, 2012
}}</ref>
⚫
;{{anchor |181}}181 Call is Being Forwarded
: Servers can optionally send this response to indicate a call is being forwarded.<ref name="RFC_3261"/>
⚫
;{{anchor |182}}182 Queued
: Indicates that the destination was temporarily unavailable, so the server has queued the call until the destination is available. A server may send multiple 182 responses to update progress of the queue.<ref name="RFC_3261"/>
⚫
;{{anchor |183}}183 Session in Progress
: This response may be used to send extra information for a call which is still being setup.<ref name="RFC_3261"/>


== 2xx—Successful Responses ==
== 2xx—Successful Responses ==
Line 82: Line 110:
==See also==
==See also==
* [[List of HTTP status codes]]
* [[List of HTTP status codes]]

==References==
{{reflist|2}}


==External links==
==External links==

Revision as of 02:33, 21 January 2012

SIP responses are the codes used by Session Initiation Protocol for communication. They complement the SIP Requests, which are used to initiate action such as a phone conversation. Note that the Reason Phrases of the responses listed below are only the recommended examples, and can be replaced with local equivalents without affecting the protocol.

1xx—Informational Responses

100 Trying
Extended search being performed may take a significant time so a forking proxy must send a 100 Trying response
180 Ringing
Destination user agent received INVITE, and is alerting user of call.[1]
181 Call is Being Forwarded
Servers can optionally send this response to indicate a call is being forwarded.[1]
182 Queued
Indicates that the destination was temporarily unavailable, so the server has queued the call until the destination is available. A server may send multiple 182 responses to update progress of the queue.[1]
183 Session in Progress
This response may be used to send extra information for a call which is still being setup.[1]

2xx—Successful Responses

  • 200 OK
  • 202 accepted: It Indicates that the request has been understood but actually can't be processed
  • 204 No Notification [RFC5839]

3xx—Redirection Responses

  • 300 Multiple Choices
  • 301 Moved Permanently
  • 302 Moved Temporarily
  • 305 Use Proxy
  • 380 Alternative Service

4xx—Client Failure Responses

  • 400 Bad Request
  • 401 Unauthorized (Used only by registrars or user agents. Proxies should use proxy authorization 407)
  • 402 Payment Required (Reserved for future use)
  • 403 Forbidden
  • 404 Not Found (User not found)
  • 405 Method Not Allowed
  • 406 Not Acceptable
  • 407 Proxy Authentication Required
  • 408 Request Timeout (Couldn't find the user in time)
  • 409 Conflict
  • 410 Gone (The user existed once, but is not available here any more.)
  • 412 Conditional Request Failed
  • 413 Request Entity Too Large
  • 414 Request-URI Too Long
  • 415 Unsupported Media Type
  • 416 Unsupported URI Scheme
  • 417 Unknown Resource-Priority
  • 420 Bad Extension (Bad SIP Protocol Extension used, not understood by the server)
  • 421 Extension Required
  • 422 Session Interval Too Small
  • 423 Interval Too Brief
  • 424 Bad Location Information
  • 428 Use Identity Header
  • 429 Provide Referrer Identity
  • 433 Anonymity Disallowed
  • 436 Bad Identity-Info
  • 437 Unsupported Certificate
  • 438 Invalid Identity Header
  • 479 Regretfully, we were not able to process the URI (479/SL)
  • 480 Temporarily Unavailable
  • 481 Call/Transaction Does Not Exist
  • 482 Loop Detected
  • 483 Too Many Hops
  • 484 Address Incomplete
  • 485 Ambiguous
  • 486 Busy Here
  • 487 Request Terminated
  • 488 Not Acceptable Here
  • 489 Bad Event
  • 491 Request Pending
  • 493 Undecipherable (Could not decrypt S/MIME body part)
  • 494 Security Agreement Required

5xx—Server Failure Responses

  • 500 Server Internal Error
  • 501 Not Implemented: The SIP request method is not implemented here
  • 502 Bad Gateway
  • 503 Service Unavailable
  • 504 Server Time-out
  • 505 Version Not Supported: The server does not support this version of the SIP protocol
  • 513 Message Too Large
  • 580 Precondition Failure

6xx—Global Failure Responses

  • 600 Busy Everywhere
  • 603 Decline
  • 604 Does Not Exist Anywhere
  • 606 Not Acceptable

See also

References

  1. ^ a b c d Rosenberg, J.; Schulzrinne, H.; Camarillo, G.; Johnston, A.; Peterson, F.; Sparks, R.; Handley, M.; Schooler, E. (2002). SIP: Session Initiation Protocol. IETF. doi:10.17487/RFC3261. RFC 3261. Retrieved January 20, 2012. {{citation}}: Unknown parameter |month= ignored (help)
Retrieved from "https://en.wikipedia.org/w/index.php?title=List_of_SIP_response_codes&oldid=472365932"