📄 overview-summary.html
字号:
<p>Provisional Response</p>
</td>
<td>
<p>A response used by the server to indicate
progress, but that does not terminate a SIP transaction. 1xx
responses are provisional, other responses are considered
final.
</p>
</td>
</tr>
<tr>
<td valign="top">
<p>Final Response</p>
</td>
<td>
<p>A response that terminates a SIP transaction, as
opposed to a provisional response that does not. All 2xx, 3xx,
4xx, 5xx and 6xx responses are final.
</p>
</td>
</tr>
</table>
<p></p>
<h3>SIP method support</h3>
<p>
All compliant implementations MUST support at least the methods defined in
RFC 2976, RFC 3261, RFC 3262, RFC 3265, RFC 3311, RFC 3428, RFC 3515, and
RFC 3903.
In particular, implementations MUST support:
<ul>
<li>Sending INFO, REGISTER, OPTIONS, INVITE, CANCEL, BYE, ACK, PRACK,
SUBSCRIBE, NOTIFY, UPDATE, MESSAGE, REFER, and PUBLISH requests on
the SipClientConnection interface</li>
<li>Receiving INFO, OPTIONS, INVITE, CANCEL, BYE, ACK, PRACK, SUBSCRIBE,
NOTIFY, UPDATE, MESSAGE, and REFER requests on the
SipServerConnection interface</li>
<li>Implementations MUST also freely allow sending and receiving of
any other non-dialog-creating requests, whether in-dialog or
out-of-dialog, as described in RFC3261</li>
</ul>
<p></p>
The API contains dedicated methods for initiating some of these requests.
Each request type is only required to be supported using the appropriate
API method (as defined in the JSR 180 specification).
<p>These RFCs have requirements for both the SIP protocol stack underneath
the JSR 180 API as well as for the application level corresponding
to the applications using the API. The SIP protocol stack MUST
implement those requirements of the RFCs that are relevant for the
stack, but following the application level requirements is the
responsibility of the applications using the JSR 180 API. The
responsibilities are approximately divided as follows:
<p></p>
Following are the requirements of the SIP protocol stack:
<ul>
<li>Support the defined method type</li>
<li>Support possible new header types defined in the RFC</li>
<li>Support the responses defined in the RFC</li>
<li>Manage basic transactions for new requests and responses</li>
<li>Create and manage the dialog, if the request creates a dialog</li>
</ul>
Following are the requirements of the application level:
<ul>
<li>Send appropriate requests and responses in the correct order</li>
<li>Fill required user headers</li>
<li>Fill required content with the required content type</li>
<li>Maintain and provide event states and content for the PUBLISH method,
as defined in RFC 3903</li>
<li>Other application-specific requirements defined by the RFC that are
not directly related to the SIP protocol</li>
</ul>
<A NAME="AUTH_REQ"> </A>
<h3>Requirements for authentication</h3>
The implementations MUST support at least the Digest authentication, as defined
in RFC 3261.<p></p>
Implementations that interface with a GSM or IMS/MMD identity module MUST
also support Digest-AKA authentication.<p></p>
Implementations MUST handle both 401 and 407 responses if the required
authentication mechanism is supported.
<h3>Notation used</h3>
This specification uses the following terms as they
are defined in the table below:
<table border="1">
<tr>
<th>
<p>Term</p>
</th>
<th>
<p>
Definition</p>
</th>
</tr>
<tr>
<td>
<p>MUST</p>
</td>
<td>
<p>The associated definition is an absolute
requirement of this specification.</p>
</td>
</tr>
<tr>
<td>
<p>MUST NOT</p>
</td>
<td>
<p>The definition is an absolute prohibition
of this specification.</p>
</td>
</tr>
<tr>
<td>
<p>SHOULD</p>
</td>
<td>
<p>Indicates a recommended practice. There
may exist valid reasons in particular circumstances to ignore
this recommendation, but the full implications must be
understood and carefully weighed before choosing a different
course.</p>
</td>
</tr>
<tr>
<td>
<p>SHOULD NOT</p>
</td>
<td>
<p>Indicates a non-recommended
practice. There may exist valid reasons in particular
circumstances when the particular behavior is acceptable or
even useful, but the full implications should be understood
and the case carefully weighed before implementing any
behavior described with this label.</p>
</td>
</tr>
<tr>
<td>
<p>MAY</p>
</td>
<td>
<p>Indicates that an item is truly optional.</p>
</td>
</tr>
</table>
<h3>References</h3>
<table border="1">
<tr>
<td valign="top">
[1]
</td>
<td>SIP: Session Initiation Protocol, RFC 3261, June 2002
</td>
</tr>
<tr>
<td valign="top">
[2]
</td>
<td>Session Initiation Protocol (SIP)-Specific Event Notification, RFC 3265, June 2002
</td>
</tr>
<tr>
<td valign="top">
[3]
</td>
<td>Session Initiation Protocol (SIP) Extension for Instant Messaging, RFC 3428, December 2002
</td>
</tr>
<tr>
<td valign="top">
[4]
</td>
<td>Indicating User Agent Capabilities in the Session Initiation Protocol (SIP), RFC 3840, August 2004
</td>
</tr>
<tr>
<td valign="top">
[5]
</td>
<td>Caller Preferences for the Session Initiation Protocol (SIP), RFC 3841, August 2004
</td>
</tr>
<tr>
<td valign="top">
[6]
</td>
<td>The Session Initiation Protocol (SIP) REFER Method, RFC 3515, April 2003
</td>
</tr>
</table>
<P>
<P>
<HR>
<P>
<P>
<HR>
<!-- ======= START OF BOTTOM NAVBAR ====== -->
<A NAME="navbar_bottom"><!-- --></A><A HREF="#skip-navbar_bottom" title="Skip navigation links"></A><TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
<TR>
<TD COLSPAN=3 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
<A NAME="navbar_bottom_firstrow"><!-- --></A><TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
<TR ALIGN="center" VALIGN="top">
<TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> <FONT CLASS="NavBarFont1Rev"><B>Overview</B></FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <FONT CLASS="NavBarFont1">Package</FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <FONT CLASS="NavBarFont1">Class</FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="javax/microedition/sip/package-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A> </TD>
</TR>
</TABLE>
</TD>
<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
</EM>
</TD>
</TR>
<TR>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
PREV
NEXT</FONT></TD>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
<A HREF="index.html" target="_top"><B>FRAMES</B></A>
<A HREF="overview-summary.html" target="_top"><B>NO FRAMES</B></A>
<SCRIPT type="text/javascript">
<!--
if(window==top) {
document.writeln('<A HREF="allclasses-noframe.html"><B>All Classes</B></A>');
}
//-->
</SCRIPT>
<NOSCRIPT>
<A HREF="allclasses-noframe.html"><B>All Classes</B></A>
</NOSCRIPT>
</FONT></TD>
</TR>
</TABLE>
<A NAME="skip-navbar_bottom"></A><!-- ======== END OF BOTTOM NAVBAR ======= -->
<HR>
<font size=-1>Copyright © 2003-2007 Nokia Corporation. All Rights Reserved.<br/> Java is a trademark of Sun Microsystems, Inc.
</BODY>
</HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -