response.html

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

CALL_IS_BEING_FORWARDED</H3>
<PRE>
static final int <B>CALL_IS_BEING_FORWARDED</B></PRE>
<DL>
<DD>A server MAY use this status code to indicate that the call is being 
 forwarded to a different set of destinations.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.CALL_IS_BEING_FORWARDED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="QUEUED"><!-- --></A><H3>
QUEUED</H3>
<PRE>
static final int <B>QUEUED</B></PRE>
<DL>
<DD>The called party is temporarily unavailable, but the server has decided 
 to queue the call rather than reject it. When the callee becomes 
 available, it will return the appropriate final status response. The 
 reason phrase MAY give further details about the status of the call, 
 for example, "5 calls queued; expected waiting time is 15 minutes". The 
 server MAY issue several 182 (Queued) responses to update the caller 
 about the status of the queued call.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.QUEUED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="SESSION_PROGRESS"><!-- --></A><H3>
SESSION_PROGRESS</H3>
<PRE>
static final int <B>SESSION_PROGRESS</B></PRE>
<DL>
<DD>The 183 (Session Progress) response is used to convey information about 
 the progress of the call that is not otherwise classified. The 
 Reason-Phrase, header fields, or message body MAY be used to convey more 
 details about the call progress.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.SESSION_PROGRESS">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="OK"><!-- --></A><H3>
OK</H3>
<PRE>
static final int <B>OK</B></PRE>
<DL>
<DD>The request has succeeded. The information returned with the response 
 depends on the method used in the request.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.OK">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="ACCEPTED"><!-- --></A><H3>
ACCEPTED</H3>
<PRE>
static final int <B>ACCEPTED</B></PRE>
<DL>
<DD>The Acceptable extension response code signifies that the request has 
 been accepted for processing, but the processing has not been completed. 
 The request might or might not eventually be acted upon, as it might be 
 disallowed when processing actually takes place. There is no facility 
 for re-sending a status code from an asynchronous operation such as this.
 The 202 response is intentionally non-committal. Its purpose is to allow 
 a server to accept a request for some other process (perhaps a 
 batch-oriented process that is only run once per day) without requiring 
 that the user agent's connection to the server persist until the process 
 is completed. The entity returned with this response SHOULD include an 
 indication of the request's current status and either a pointer to a 
 status monitor or some estimate of when the user can expect the request 
 to be fulfilled. This response code is specific to the event notification 
 framework.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.ACCEPTED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="MULTIPLE_CHOICES"><!-- --></A><H3>
MULTIPLE_CHOICES</H3>
<PRE>
static final int <B>MULTIPLE_CHOICES</B></PRE>
<DL>
<DD>The address in the request resolved to several choices, each with its
 own specific location, and the user (or UA) can select a preferred 
 communication end point and redirect its request to that location.
 <p>
 The response MAY include a message body containing a list of resource
 characteristics and location(s) from which the user or UA can choose
 the one most appropriate, if allowed by the Accept request header field. 
 However, no MIME types have been defined for this message body.
 <p>
 The choices SHOULD also be listed as Contact fields. Unlike HTTP, the 
 SIP response MAY contain several Contact fields or a list of addresses 
 in a Contact field. User Agents MAY use the Contact header field value 
 for automatic redirection or MAY ask the user to confirm a choice. 
 However, this specification does not define any standard for such 
 automatic selection.
 <p>
 This status response is appropriate if the callee can be reached at 
 several different locations and the server cannot or prefers not to 
 proxy the request.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.MULTIPLE_CHOICES">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="MOVED_PERMANENTLY"><!-- --></A><H3>
MOVED_PERMANENTLY</H3>
<PRE>
static final int <B>MOVED_PERMANENTLY</B></PRE>
<DL>
<DD>The user can no longer be found at the address in the Request-URI, and 
 the requesting client SHOULD retry at the new address given by the 
 Contact header field. The requestor SHOULD update any local directories, 
 address books, and user location caches with this new value and redirect 
 future requests to the address(es) listed.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.MOVED_PERMANENTLY">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="MOVED_TEMPORARILY"><!-- --></A><H3>
MOVED_TEMPORARILY</H3>
<PRE>
static final int <B>MOVED_TEMPORARILY</B></PRE>
<DL>
<DD>The requesting client SHOULD retry the request at the new address(es)
 given by the Contact header field. The Request-URI of the new request 
 uses the value of the Contact header field in the response.
 <p>
 The duration of the validity of the Contact URI can be indicated through 
 an Expires header field or an expires parameter in the Contact header 
 field. Both proxies and User Agents MAY cache this URI for the duration 
 of the expiration time. If there is no explicit expiration time, the 
 address is only valid once for recursing, and MUST NOT be cached for 
 future transactions.
 <p>
 If the URI cached from the Contact header field fails, the Request-URI 
 from the redirected request MAY be tried again a single time. The 
 temporary URI may have become out-of-date sooner than the expiration 
 time, and a new temporary URI may be available.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.MOVED_TEMPORARILY">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="USE_PROXY"><!-- --></A><H3>
USE_PROXY</H3>
<PRE>
static final int <B>USE_PROXY</B></PRE>
<DL>
<DD>The requested resource MUST be accessed through the proxy given by the 
 Contact field.  The Contact field gives the URI of the proxy. The 
 recipient is expected to repeat this single request via the proxy. 
 305 (Use Proxy) responses MUST only be generated by UASs.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.USE_PROXY">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="ALTERNATIVE_SERVICE"><!-- --></A><H3>
ALTERNATIVE_SERVICE</H3>
<PRE>
static final int <B>ALTERNATIVE_SERVICE</B></PRE>
<DL>
<DD>The call was not successful, but alternative services are possible. The 
 alternative services are described in the message body of the response. 
 Formats for such bodies are not defined here, and may be the subject of 
 future standardization.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.ALTERNATIVE_SERVICE">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="BAD_REQUEST"><!-- --></A><H3>
BAD_REQUEST</H3>
<PRE>
static final int <B>BAD_REQUEST</B></PRE>
<DL>
<DD>The request could not be understood due to malformed syntax. The  
 Reason-Phrase SHOULD identify the syntax problem in more detail, for 
 example, "Missing Call-ID header field".
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.BAD_REQUEST">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="UNAUTHORIZED"><!-- --></A><H3>
UNAUTHORIZED</H3>
<PRE>
static final int <B>UNAUTHORIZED</B></PRE>
<DL>
<DD>The request requires user authentication. This response is issued by 
 UASs and registrars, while 407 (Proxy Authentication Required) is used 
 by proxy servers.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.UNAUTHORIZED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="PAYMENT_REQUIRED"><!-- --></A><H3>
PAYMENT_REQUIRED</H3>
<PRE>
static final int <B>PAYMENT_REQUIRED</B></PRE>
<DL>
<DD>Reserved for future use.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.PAYMENT_REQUIRED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="FORBIDDEN"><!-- --></A><H3>
FORBIDDEN</H3>
<PRE>
static final int <B>FORBIDDEN</B></PRE>
<DL>
<DD>The server understood the request, but is refusing to fulfill it.
 Authorization will not help, and the request SHOULD NOT be repeated.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.FORBIDDEN">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="NOT_FOUND"><!-- --></A><H3>
NOT_FOUND</H3>
<PRE>
static final int <B>NOT_FOUND</B></PRE>
<DL>
<DD>The server has definitive information that the user does not exist at
 the domain specified in the Request-URI.  This status is also returned 
 if the domain in the Request-URI does not match any of the domains 
 handled by the recipient of the request.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.NOT_FOUND">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="METHOD_NOT_ALLOWED"><!-- --></A><H3>
METHOD_NOT_ALLOWED</H3>
<PRE>
static final int <B>METHOD_NOT_ALLOWED</B></PRE>
<DL>
<DD>The method specified in the Request-Line is understood, but not allowed 
 for the address identified by the Request-URI. The response MUST include 
 an Allow header field containing a list of valid methods for the 
 indicated address
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.METHOD_NOT_ALLOWED">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="NOT_ACCEPTABLE"><!-- --></A><H3>
NOT_ACCEPTABLE</H3>
<PRE>
static final int <B>NOT_ACCEPTABLE</B></PRE>
<DL>
<DD>The resource identified by the request is only capable of generating
 response entities that have content characteristics not acceptable
 according to the Accept header field sent in the request.
<P>
<DL>
<DT><B>See Also:</B><DD><A HREF="../../../constant-values.html#javax.sip.message.Response.NOT_ACCEPTABLE">Constant Field Values</A></DL>
</DL>
<HR>

<A NAME="PROXY_AUTHENTICATION_REQUIRED"><!-- --></A><H3>
PROXY_AUTHENTICATION_REQUIRED</H3>
<PRE>
static final int <B>PROXY_AUTHENTICATION_REQUIRED</B></PRE>
<DL>
<DD>This code is similar to 401 (Unauthorized), but indicates that the client 
 MUST first authenticate itself with the proxy. This status code can be 
 used for applications where access to the communication channel (for 
 example, a telephony gateway) rather than the callee requires