conformance.docs

Sofia SIP is an open-source SIP User-Agent library, compliant with the IETF RFC3261 specification.

    </th>
    <td>
	PUBLISH method is supported natively. The SIP headers
	explicitly supported (generating, parsing and syntax checking) are
	@ref sip_etag "SIP-ETag" and @ref sip_if_match "SIP-If-Match".

	The <a href="nua/index.html">user-agent engine</a> keep published
	data refreshed until nua_unpublish() is called.
    </td>
    <td>
        Application must take care of:
        - Including correct @ref sip_event "Event" in the request
        - Permanently storing @SIPETag
    </td>
</tr>

<a name="4028"></a>
<tr valign=top>
    <th align="left">
	@RFC4028: Session Timers
    </th>
    <td>
	The SIP session-timer ("timer") extension is supported.

        The session-expires value and refreshing party is negotiated in
	<a href="nua/index.html">user-agent engine</a>. When user-agent
	engine is responsible for refreshes, it will initiate re-INVITE or
	UPDATE transaction at regular intervals.

	If there has been no SIP activity in session during the refresh
	period, it will try to automatically terminate the call by sending a
	@b BYE request.

        The SIP headers explicitly supported (generating, parsing and
	syntax checking) are @ref sip_session_expires "Session-Expires" ("x") and
	@ref sip_min_se "Min-SE".
    </td>
    <td>
	&nbsp;
    </td>
</tr>

<a name="4168"></a>
<tr valign=top>
    <th align="left">
	@RFC4168: SCTP as Transport for SIP
    </th>
    <td>
	The transport=sctp URI parameter is supported. The SCTP transport
	protocol is supported as experimental. It is enabled with
	configure script argument --enable-sctp.

	The framing of SIP messages over SCTP is not specified clearly in
	@RFC4168. It is possible to send SIP messages smaller than 64K over
	SCTP.
    </td>
    <td>
	&nbsp;
    </td>
</tr>


<a name="4320"></a>
<tr valign=top>
    <th align="left">
	@RFC4320: Actions Addressing Identified Issues with SIP's Non-INVITE Transaction
    </th>
    <td>
	The action 1 (make the best use of provisional responses) is
	supported when NTATAG_EXTRA_100(1) is used with nua_create() or
	nta_agent_create(). The 100 Trying provisional response is sent
	after T2 is expired or when a retransmission is received after T2/2
        after the initial request.

	The action 2 (remove the useless late-response storm) is supported
	by default. The 408 timeout response is not forwarded by default (it's
	forwarding can be enabled with NTATAG_PASS_408(1), however).
    </td>
    <td>
        Application must include NTATAG_EXTRA_100(1) with nua_create() or
	nta_agent_create() tags.
    </td>
</tr>

<a name="4488"></a>
<tr valign=top>
    <th align="left">
	@RFC4488: Suppression of REFER Implicit Subscription
    </th>
    <td>
	Sofia-SIP supports @ref sip_refer_sub "Refer-Sub" header
	(generating, parsing and syntax checking).

        The implicit subscription is suppressed by @nua, if the @ReferSub:
        true header is included in the REFER 
	request (@ref nua_refer "on server side") or
	response (@ref nua_i_refer "on client side").

	@NEW_1_12_5
    </td>
    <td>
        The REFER client application must include SIPTAG_REFER_SUB_STR("true")
	in the nua_refer() tags.
    </td>
</tr>

<a name="5057"></a>
<tr valign=top>
    <th align="left">
	@RFC5057: Multiple Dialog Usages in SIP
    </th>
    <td>
	Sofia-SIP provides function sip_response_terminates_dialog() that
	can be used to determine the effect of error response with dialog.
	
	The nua UA engine uses sip_response_terminates_dialog().
    </td>
    <td>
        The client application must either use NUA or
        sip_response_terminates_dialog().
    </td>
</tr>

</table>

<table border=1 cellpadding=4 cellspacing=0>
<tr>
   <th>Feature</th>
   <th>Supported</td>
   <th>Notes</td>
</tr>

<a name="4566"></a>
<a name="2327"></a>
<a name="3266"></a>
<tr valign=top>
    <th align="left" align="left">
	@RFC4566: SDP: Session Description Protocol
    </th>
    <td>
	Generic support (generating, parsing and syntax checking) for SDP.
	The SDP
        @ref sdp_version_t "v=",
        @ref sdp_origin_t "o=",
	@ref sdp_connection_t "c=",
	@ref sdp_bandwidth_t "b=",
	@ref sdp_time_t "t=",
	@ref sdp_repeat_t "r=",
	@ref sdp_zone_t "z=",
	@ref sdp_key_t "k=",
	@ref sdp_attribute_t "a=", and
	@ref sdp_media_t "m="
        lines are separated and parsed. The "e=", "p=", "s=", and "i=" lines
	are separated.

	The attributes "a=sendrecv", "a=sendonly", "a=recvonly",
	"a=inactive", @ref sdp_rtpmap_s "a=rtpmap", and "a=fmtp" are parsed.

	The implementation partially implements @RFC4566. Note that
	definition of 'token' was updated in @RFC4566 and the parser has not
	been updated yet.
    </td>
    <td>
      @RFC4566 obsoletes
      - @RFC2327: SDP (Session Description Protocol)
      - @RFC3266: IP6 in SDP
    </td>
</tr>

<a name="3264"></a>
<tr valign=top>
    <th align="left">
	@RFC3264: SDP Offer/Answer Negotiation
    </th>
    <td>
	Generating and processing offers or answers.
    </td>
    <td>
	- "a=fmtp" parameters are not taken into account
          when generating or processing answer
    </td>
</tr>

<a name="3312"></a>
<tr valign=top>
    <th align="left">
	@RFC3312: Preconditions
    </th>
    <td>
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.

        Sofia-SIP supports handling SIP feature tags in
	@ref sip_proxy_require "Proxy-Require",
        @ref sip_require "Require",
        @ref sip_supported "Supported" ("k"),
        and
        @ref sip_unsupported "Unsupported" header.
    </td>
    <td>
	Application must take care of:
	- Semantics and handling of preconditions
	- Reservation of resources
    </td>
</tr>

<a name="3388"></a>
<tr valign=top>
    <th align="left">
	@RFC3388: Grouping of Media Lines
    </th>
    <td>
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.

	@RFC3388 defines mid, group, LS and FID are predefined strings to be
	used within attribute line
    </td>
    <td>
        Application must take care of:
	- Generating or processing the attribute lines
	- Grouping the media for transport accordingly
    </td>
</tr>


<a name="3407"></a>
<tr valign=top>
    <th align="left">
	@RFC3407: Capability Declaration
    </th>
    <td>
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
    </td>
    <td>
        Application must take care of:
	- Defining sqn, cdsc, cpar etc. strings needed in a= line
	- Generating or processing the attribute lines
	- Capability negotiation itself
    </td>
</tr>


<a name="3524"></a>
<tr valign=top>
    <th align="left">
	@RFC3524: SRF
    </th>
    <td>
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
    </td>
    <td>
        Application must take care of:
	- Defining SRF string needed in a= line
	- Generating or processing the attribute lines
    </td>
</tr>


<a name="3551"></a>
<tr valign=top>
    <th align="left">
	@RFC3551: RTP/AVP
    </th>
    <td>
	Sofia-SIP recognizes the RTP payload types for well-known audio and
	video codecs defined in @RFC3551.
    </td>
    <td>
        Application must take care of:
	- Audio or video processing
        - Generating a=rtpmap or a=fmtp lines when needed 
    </td>
</tr>

<a name="3556"></a>
<tr valign=top>
    <th align="left">
	@RFC3556: Bandwidth
    </th>
    <td>
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
    </td>
    <td>
        Application must take care of:
	- Generating or processing RS and RR bandwidth modifiers
	- Semantics of bandwidth allocation
    </td>
</tr>

<a name="3605"></a>
<tr valign=top>
    <th align="left">
	@RFC3605: RTCP attribute
    </th>
    <td>
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
    </td>
    <td>
        Application must take care of:
	- Discovering port numbers
	- Generating or processing the RTCP attribute lines
    </td>
</tr>

<a name="3890"></a>
<tr valign=top>
    <th align="left">
	@RFC3890: TIAS
    </th>
    <td>
	Sofia-SIP provides <a href="#2616">generic support</a> for attribute
	lines that conform to SDP syntax.
    </td>
    <td>
        Application must take care of:
	- Generating or processing TIAS bandwidth modifiers
	- Generating or processing the maxprate attribute lines
    </td>
</tr>

</table>


*/

/* Overflow:

<a name="4566"></a>
<tr valign=top>
    <th align="left">
	@RFC4566: SDP: Session Description Protocol
    </th>
    <td>
    Obsoletes RFC2327 and RFC3266.
    </td>
    <td>
	&nbsp;
    </td>
</tr>


<a name="3320"></a>
<tr valign=top>
    <th align="left">
	@RFC3320: SigComp
    </th>
    <td>
    	Support for using SigComp for compression and
	decompression of SIP/SDP messages. By default, dynamic
	compression is used.

	Decompression using UDVM
    </td>
    <td>
	&nbsp;
    </td>
</tr>

<a name="3321"></a>
<tr valign=top>
    <th align="left">
	@RFC3321: SigComp Extended operations
    </th>
    <td>
	Support for SigComp extended operations.
    </td>
    <td>
	- Explicit Acknowledgment Scheme
	- Shared Compression
	- Checkpoint State
	- Implicit Deletion for Dictionary Update
    </td>
</tr>

<a name="3325"></a>
<tr valign=top>
    <th align="left">
	@RFC3325: Asserted Identity
    </th>
    <td>
	Explicit support (generating, parsing and syntax checking) for the
	following SIP headers: P-Asserted-Identity, P-Preferred-Identity
    </td>
    <td>
	- Recognizing trust domains and enforcing handling of headers
	  based on those
    </td>
</tr>

<a name="3485"></a>
<tr valign=top>
    <th align="left">
	@RFC3485: SIP/SDP Dictionary
    </th>
    <td>
	Support for SigComp static compression using SIP/SDP
	dictionary.
    </td>
    <td>
	&nbsp;
    </td>
</tr>




	- Implicitly registered user identities

<a name="3959"></a>
<tr valign=top>
    <th align="left">
	@RFC3959: early-session
    </th>
    <td>
	Early-session value can be used within Content-Disposition,
	Supported and Require headers.
    </td>
    <td>
	- Generating of Content-Disposition, Supported and Require
	- Handling of multipart bodies with early and session SDP
    </td>
</tr>

*/