response.html

jsip开发文档,对于开发SIP软电话和presence服务很有用

 authentication.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.PROXY_AUTHENTICATION_REQUIRED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="REQUEST_TIMEOUT"><!-- --></A><H3>
REQUEST_TIMEOUT</H3>
<PRE>
static final int <B>REQUEST_TIMEOUT</B></PRE>
<DL>
<DD>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.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.REQUEST_TIMEOUT">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="GONE"><!-- --></A><H3>
GONE</H3>
<PRE>
static final int <B>GONE</B></PRE>
<DL>
<DD>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.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.GONE">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="CONDITIONAL_REQUEST_FAILED"><!-- --></A><H3>
CONDITIONAL_REQUEST_FAILED</H3>
<PRE>
static final int <B>CONDITIONAL_REQUEST_FAILED</B></PRE>
<DL>
<DD>The server is refusing to service the PUBLISH request because the 
 entity-tag in the SIP-If-Match header does not match with existing 
 event state.
<P>
<DL>
<DT><B>Since:</B></DT>
  <DD>v1.2</DD>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.CONDITIONAL_REQUEST_FAILED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="REQUEST_ENTITY_TOO_LARGE"><!-- --></A><H3>
REQUEST_ENTITY_TOO_LARGE</H3>
<PRE>
static final int <B>REQUEST_ENTITY_TOO_LARGE</B></PRE>
<DL>
<DD>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 field to indicate that it is temporary and after what
 time the client MAY try again.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.REQUEST_ENTITY_TOO_LARGE">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="REQUEST_URI_TOO_LONG"><!-- --></A><H3>
REQUEST_URI_TOO_LONG</H3>
<PRE>
static final int <B>REQUEST_URI_TOO_LONG</B></PRE>
<DL>
<DD>The server is refusing to service the request because the Request-URI
 is longer than the server is willing to interpret.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.REQUEST_URI_TOO_LONG">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="UNSUPPORTED_MEDIA_TYPE"><!-- --></A><H3>
UNSUPPORTED_MEDIA_TYPE</H3>
<PRE>
static final int <B>UNSUPPORTED_MEDIA_TYPE</B></PRE>
<DL>
<DD>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.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.UNSUPPORTED_MEDIA_TYPE">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="UNSUPPORTED_URI_SCHEME"><!-- --></A><H3>
UNSUPPORTED_URI_SCHEME</H3>
<PRE>
static final int <B>UNSUPPORTED_URI_SCHEME</B></PRE>
<DL>
<DD>The server cannot process the request because the scheme of the URI in 
 the Request-URI is unknown to the server.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.UNSUPPORTED_URI_SCHEME">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="BAD_EXTENSION"><!-- --></A><H3>
BAD_EXTENSION</H3>
<PRE>
static final int <B>BAD_EXTENSION</B></PRE>
<DL>
<DD>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.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.BAD_EXTENSION">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="EXTENSION_REQUIRED"><!-- --></A><H3>
EXTENSION_REQUIRED</H3>
<PRE>
static final int <B>EXTENSION_REQUIRED</B></PRE>
<DL>
<DD>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.
 <p>
 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.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.EXTENSION_REQUIRED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="INTERVAL_TOO_BRIEF"><!-- --></A><H3>
INTERVAL_TOO_BRIEF</H3>
<PRE>
static final int <B>INTERVAL_TOO_BRIEF</B></PRE>
<DL>
<DD>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.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.INTERVAL_TOO_BRIEF">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="TEMPORARILY_UNAVAILABLE"><!-- --></A><H3>
TEMPORARILY_UNAVAILABLE</H3>
<PRE>
static final int <B>TEMPORARILY_UNAVAILABLE</B></PRE>
<DL>
<DD>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 callee, 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.
 <p>
 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 user.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.TEMPORARILY_UNAVAILABLE">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="CALL_OR_TRANSACTION_DOES_NOT_EXIST"><!-- --></A><H3>
CALL_OR_TRANSACTION_DOES_NOT_EXIST</H3>
<PRE>
static final int <B>CALL_OR_TRANSACTION_DOES_NOT_EXIST</B></PRE>
<DL>
<DD>This status indicates that the UAS received a request that does not 
 match any existing dialog or transaction.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.CALL_OR_TRANSACTION_DOES_NOT_EXIST">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="LOOP_DETECTED"><!-- --></A><H3>
LOOP_DETECTED</H3>
<PRE>
static final int <B>LOOP_DETECTED</B></PRE>
<DL>
<DD>The server has detected a loop.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.LOOP_DETECTED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="TOO_MANY_HOPS"><!-- --></A><H3>
TOO_MANY_HOPS</H3>
<PRE>
static final int <B>TOO_MANY_HOPS</B></PRE>
<DL>
<DD>The server received a request that contains a Max-Forwards header field 
 with the value zero.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.TOO_MANY_HOPS">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="ADDRESS_INCOMPLETE"><!-- --></A><H3>
ADDRESS_INCOMPLETE</H3>
<PRE>
static final int <B>ADDRESS_INCOMPLETE</B></PRE>
<DL>
<DD>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.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.ADDRESS_INCOMPLETE">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="AMBIGUOUS"><!-- --></A><H3>
AMBIGUOUS</H3>
<PRE>
static final int <B>AMBIGUOUS</B></PRE>
<DL>
<DD>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 respond with status 404
 (Not Found) or to suppress the listing of possible choices for ambiguous 
 Request-URIs. 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 provided. While an automated 
 choice or sequential search makes sense for a 3xx response, user 
 intervention is required for a 485 (Ambiguous) response.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.AMBIGUOUS">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="BUSY_HERE"><!-- --></A><H3>
BUSY_HERE</H3>
<PRE>
static final int <B>BUSY_HERE</B></PRE>
<DL>
<DD>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.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.BUSY_HERE">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="REQUEST_TERMINATED"><!-- --></A><H3>
REQUEST_TERMINATED</H3>
<PRE>
static final int <B>REQUEST_TERMINATED</B></PRE>
<DL>
<DD>The request was term