sip  1.12.11devel
Modules
Here is a list of all modules:
[detail level 12]
 SIP HeadersSIP headers and other SIP message elements
 SIP Header X - ConventionsFor a SIP header X, there are types, functions, macros and global data declared in <sofia-sip/sip_protos.h> and <sofia-sip/sip_hclass.h> as follows:
 Request LineThe request line is first line in a SIP request message
 Status LineThe status line is first line in a response message
 Message BodyThe payload structure contains the optional message body
 Separator LineAn empty line separates message headers from the message body (payload)
 Unknown HeadersThe unknown headers are handled with sip_unknown_t structure
 Erroneous HeadersThe erroneous headers are stored in sip_error_t structure
 Call-ID HeaderThe Call-ID header uniquely identifies a particular invitation or all registrations of a particular client
 CSeq HeaderThe CSeq header (command sequence) uniquely identifies transactions within a dialog
 Contact HeaderThe Contact header contain a list of URLs used to redirect future requests
 Content-Length HeaderThe Content-Length header indicates the size of the message-body in decimal number of octets
 Date HeaderThe Date header field reflects the time when the request or response was first sent
 Expires HeaderThe Expires header field gives the date and time after which the message content expires
 From HeaderThe From header indicates the initiator of the request
 Max-Forwards HeaderThe Max-Forwards header is used to limit the number of proxies or gateways that can forward the request
 Min-Expires HeaderThe Min-Expires header is used to limit the number of proxies or gateways that can forward the request
 Retry-After HeaderThe Retry-After response-header field RFC 3261 section 20.33 can be used to indicate how long the service is expected to be unavailable or when the called party anticipates being available again
 Route HeaderThe Route headers is used to store the route set of a transaction
 Record-Route HeaderThe Record-Route headers are used to establish a route for transactions belonging to a session
 To HeaderThe To header field specifies the "logical" recipient of the request
 Via HeaderThe Via header indicates the path taken by the request so far
 Request-Disposition HeaderThe Request-Disposition header syntax is defined in RFC 3841 section 10 as follows:
 Accept-Contact HeaderThe Accept-Contact syntax is defined in RFC 3841 section 10 as follows:
 Reject-Contact HeaderThe Reject-Contact syntax is defined in RFC 3841 section 10 as follows:
 Event HeaderThe Event header is used to indicate the which event or class of events the message contains or subscribes
 Allow-Events HeaderThe Allow-Events header is used to indicate which events or classes of events the notifier supports
 Subscription-State HeaderThe Subscription-State header is used to indicate in which state a subscription is
 Call-Info HeaderThe Call-Info header provides additional information about the caller or callee
 Error-Info HeaderThe Error-Info header provides a pointer to additional information about the error status response
 Alert-Info HeaderWhen present in an INVITE request, the Alert-Info header field specifies an alternative ring tone to the UAS
 Reply-To HeaderThe Reply-To header field contains a logical return URI that may be different from the From header field
 In-Reply-To HeaderThe In-Reply-To request header field enumerates the Call-IDs that this call references or returns
 Organization HeaderThe Organization header field conveys the name of the organization to which the entity issuing the request or response belongs
 Priority HeaderThe Priority request-header field indicates the urgency of the request as perceived by the client
 Server HeaderThe Server response-header field contains information about the software used by the user agent server to handle the request
 Subject HeaderThe Subject header provides a summary or indicates the nature of the request
 Timestamp HeaderThe Timestamp header describes when the client sent the request to the server, and it is used by the client to adjust its retransmission intervals
 User-Agent HeaderThe User-Agent header contains information about the client user agent originating the request
 SIP-ETag HeaderThe SIP-ETag header field identifies the published event state
 SIP-If-Match HeaderThe SIP-If-Match header field identifies the specific entity of event state that the request is refreshing, modifying or removing
 Suppress-Body-If-Match HeaderThe Suppress-Body-If-Match header field identifies a SIP event content already known by the watcher
 Suppress-Notify-If-Match HeaderThe Suppress-Notify-If-Match header is used to suppress superfluous NOTIFY transactions
 Remote-Party-ID HeaderThe syntax of the Remote-Party-ID header is described as follows:
 P-Asserted-Identity HeaderThe P-Asserted-Identity header is used used among trusted SIP entities (typically intermediaries) to carry the identity of the user sending a SIP message as it was verified by authentication
 P-Preferred-Identity HeaderThe P-Preferred-Identity header is used used among trusted SIP entities (typically intermediaries) to carry the identity of the user sending a SIP message as it was verified by authentication
 Allow HeaderThe Allow header lists the set of methods supported by the user agent generating the message
 Proxy-Require HeaderThe Proxy-Require header is used to indicate proxy-sensitive features that MUST be supported by the proxy
 Require HeaderThe Require header is used by clients to tell user agent servers about options that the client expects the server to support in order to properly process the request
 Supported HeaderThe Supported header enumerates all the capabilities of the client or server
 Unsupported HeaderThe Unsupported header lists the features not supported by the server
 Path HeaderThe Path header field is a SIP extension header field (RFC 3327) with syntax very similar to the Record-Route header field
 Service-Route HeaderThe "Service-Route" is a SIP extension header field (RFC 3608), which can contain a route vector that will direct requests through a specific sequence of proxies
 Accept HeaderThe Accept request-header field can be used to specify certain media types which are acceptable for the response
 Accept-Encoding HeaderThe Accept-Encoding header is similar to Accept, but restricts the content-codings that are acceptable in the response
 Accept-Language HeaderThe Accept-Language header can be used to allow the client to indicate to the server in which language it would prefer to receive reason phrases, session descriptions or status responses carried as message bodies
 Content-Disposition HeaderThe Content-Disposition header field describes how the message body or, in the case of multipart messages, a message body part is to be interpreted by the UAC or UAS
 Content-Encoding HeaderThe Content-Encoding header indicates what additional content codings have been applied to the entity-body
 Content-Language HeaderThe Content-Language header RFC 2616 section 14.12 describes the natural language(s) of the intended audience for the enclosed entity
 Content-Type HeaderThe Content-Type header indicates the media type of the message-body sent to the recipient
 MIME-Version HeaderMIME-Version header indicates what version of the MIME protocol was used to construct the message
 Warning HeaderThe Warning response-header field is used to carry additional information about the status of a response
 RAck HeaderThe RAck header indicates the sequence number of the provisional response which is being acknowledged
 RSeq HeaderThe RSeq header identifies provisional responses within a transaction
 Reason HeaderThe Reason header is used to indicate why a SIP request was issued or why a provisional response was sent
 Refer-To HeaderThe Refer-To header provides a URI to reference
 Referred-By HeaderThe Referred-By header conveys the identity of the original referrer to the referred-to party
 Replaces HeaderThe Replaces header indicates that a single dialog identified by the header field is to be shut down and logically replaced by the incoming INVITE in which it is contained
 Refer-Sub HeaderSIP header field Refer-Sub is meaningful and MAY be used with a REFER request and the corresponding 2XX response only
 Authorization HeaderThe Authorization header consists of credentials containing the authentication information of the user agent for the realm of the resource being requested
 Proxy-Authenticate HeaderThe Proxy-Authenticate header consists of a challenge that indicates the authentication scheme and parameters applicable to the proxy
 Proxy-Authorization HeaderThe Proxy-Authorization header consists of credentials containing the authentication information of the user agent for the proxy and/or realm of the resource being requested
 WWW-Authenticate HeaderThe WWW-Authenticate header consists of at least one challenge that indicates the authentication scheme(s) and parameters applicable to the Request-URI
 Authentication-Info HeaderThe Authentication-Info header contains either a next-nonce used by next request and/or authentication from server used in mutual authentication
 Proxy-Authentication-Info HeaderThe Proxy-Authentication-Info header contains either a next-nonce used by next request and/or authentication from proxy used in mutual authentication
 Security-Client HeaderThe Security-Client header is defined by RFC 3329, "Security Mechanism Agreement for the Session Initiation Protocol (SIP)"
 Security-Server HeaderThe Security-Server header is defined by RFC 3329, "Security Mechanism Agreement for the Session Initiation Protocol (SIP)"
 Security-Verify HeaderThe Security-Verify header is defined by RFC 3329, "Security Mechanism Agreement for the Session Initiation Protocol (SIP)"
 Privacy HeaderThe Privacy header is used by User-Agent to request privacy services from the network
 Session-Expires HeaderThe Session-Expires header is used to convey the lifetime of the session
 Min-SE HeaderThe Min-SE header is used to indicate the minimum value for the session interval
 SIP Status Codes and Reason PhrasesThe macros and variables for the standard SIP status codes and reason phrases are defined in <sofia-sip/sip_status.h>
 SIP TagsSIP headers in tag item lists and tagged argument lists

Sofia-SIP 1.12.11devel - Copyright (C) 2006 Nokia Corporation. All rights reserved. Licensed under the terms of the GNU Lesser General Public License.