Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
15Activity
0 of .
Results for:
No results containing your search query
P. 1
Sip Error Codes

Sip Error Codes

Ratings:

5.0

(3)
|Views: 5,223|Likes:
Published by api-3696704

More info:

Published by: api-3696704 on Oct 14, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

 
5. Response
After receiving and interpreting a request message, the recipientresponds with a SIP response message. The response message formatis shown below:
:=
*(
|
|
)
[ message-body ]SIP's structure of responses is similar to [H6], but is defined explicitlyhere.
5.1. Status-Line
 The first line of a Response message is the Status-Line, consisting of the protocol version (Section 4.3.1) followed by a numeric Status-Codeand its associated textual phrase, with each element separated by SPcharacters. No CR or LF is allowed except in the final CRLF sequence.
:= SIP-version
SP
 
 
SP
 
5.1.1. Status Codes and Reason Phrases
 The Status-Code is a 3-digit integer result code that indicates theoutcome of the attempt to understand and satisfy the request. TheReason-Phrase is intended to give a short textual description of theStatus-Code. The Status-Code is intended for use by automata,whereas the Reason-Phrase is intended for the human user. The clientis not required to examine or display the Reason-Phrase.
:=
|
|
|
|
|
|
:= 3DIGIT
:= *
, excluding
,
We provide an overview of the Status-Code below, and provide fulldefinitions in Section 7. The first digit of the Status-Code defines theclass of response. The last two digits do not have any categorizationrole. SIP/2.0 allows 6 values for the first digit:
1xx: Informational -- request received, continuing to process therequest;2xx: Success -- the action was successfully received, understood, andaccepted;
 
3xx: Redirection -- further action needs to be taken in order tocomplete the request;4xx: Client Error -- the request contains bad syntax or cannot befulfilled at this server;5xx: Server Error -- the server failed to fulfill an apparently validrequest;6xx: Global Failure -- the request cannot be fulfilled at any server.
Figures 5 through 9 present the individual values of the numericresponse codes, and an example set of corresponding reason phrasesfor SIP/2.0. These reason phrases are only recommended; they may bereplaced by local equivalents without affecting the protocol. Note thatSIP adopts many HTTP/1.1 response codes. SIP/2.0 adds responsecodes in the range starting at x80 to avoid conflicts with newly definedHTTP response codes, and adds a new class, 6xx, of response codes.SIP response codes are extensible. SIP applications are not required tounderstand the meaning of all registered response codes, though suchunderstanding is obviously desirable. However, applications MUSTunderstand the class of any response code, as indicated by the firstdigit, and treat any unrecognized response as being equivalent to thex00 response code of that class, with the exception that anunrecognized response MUST NOT be cached. For example, if a clientreceives an unrecognized response code of 431, it can safely assumethat there was something wrong with its request and treat theresponse as if it had received a 400 (Bad Request) response code. Insuch cases, user agents SHOULD present to the user the messagebody returned with the response, since that message body is likely toinclude human-readable information which will explain the unusualstatus.
:= "100" | "180" | "181" | "182"
:= "200"
Informational = "100" ; Trying| "180" ; Ringing| "181" ; Call Is Being Forwarded| "182" ; QueuedSuccess = "200" ; OKFigure 5: Informational and success status codes
:= "300" | "301" | "302" | "303" | "305" | "380"
Redirection = "300" ; Multiple Choices| "301" ; Moved Permanently| "302" ; Moved Temporarily| "303" ; See Other| "305" ; Use Proxy
 
| "380" ; Alternative ServiceFigure 6: Redirection status codes
:= "400" | "401" | "402" | "403" | "404" | "405" | "406" |"407" | "408" | "409" | "410" | "411" | "413" | "414" | "415" | "420" |"480" | "481" | "482" | "483" | "484" | "485" | "486"
Client-Error = "400" ; Bad Request| "401" ; Unauthorized| "402" ; Payment Required| "403" ; Forbidden| "404" ; Not Found| "405" ; Method Not Allowed| "406" ; Not Acceptable| "407" ; Proxy Authentication Required| "408" ; Request Timeout| "409" ; Conflict| "410" ; Gone| "411" ; Length Required| "413" ; Request Entity Too Large| "414" ; Request-URI Too Large| "415" ; Unsupported Media Type| "420" ; Bad Extension| "480" ; Temporarily not available| "481" ; Call Leg/Transaction Does Not Exist| "482" ; Loop Detected| "483" ; Too Many Hops| "484" ; Address Incomplete| "485" ; Ambiguous| "486" ; Busy HereFigure 7: Client error status codes
:= "500" | "501" | "502" | "503" | "504" | "505"
Server-Error = "500" ; Internal Server Error| "501" ; Not Implemented| "502" ; Bad Gateway| "503" ; Service Unavailable| "504" ; Gateway Time-out| "505" ; SIP Version not supportedFigure 8: Server error status codes
6. Header Field Definitions
SIP header fields are similar to HTTP header fields in both syntax andsemantics. In particular, SIP header fields follow the syntax formessage-header as described in [H4.2]. The rules for extending headerfields over multiple lines, and use of multiple message-header fieldswith the same field-name, described in [H4.2] also apply to SIP. The

Activity (15)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Gol D Roger liked this
Youssef Aoufi liked this
Jose Gonzalez liked this
concourscarto liked this
jrmirandac liked this
Bishnu Choudhury liked this
gudayarajan liked this
no pogas nombre liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->