sip  1.12.11devel
 All Data Structures Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
Modules
Here is a list of all modules:
[detail level 12]
oSIP HeadersSIP headers and other SIP message elements
|oSIP 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:
|oRequest LineThe request line is first line in a SIP request message
|oStatus LineThe status line is first line in a response message
|oMessage BodyThe payload structure contains the optional message body
|oSeparator LineAn empty line separates message headers from the message body (payload)
|oUnknown HeadersThe unknown headers are handled with sip_unknown_t structure
|oErroneous HeadersThe erroneous headers are stored in sip_error_t structure
|oCall-ID HeaderThe Call-ID header uniquely identifies a particular invitation or all registrations of a particular client
|oCSeq HeaderThe CSeq header (command sequence) uniquely identifies transactions within a dialog
|oContact HeaderThe Contact header contain a list of URLs used to redirect future requests
|oContent-Length HeaderThe Content-Length header indicates the size of the message-body in decimal number of octets
|oDate HeaderThe Date header field reflects the time when the request or response was first sent
|oExpires HeaderThe Expires header field gives the date and time after which the message content expires
|oFrom HeaderThe From header indicates the initiator of the request
|oMax-Forwards HeaderThe Max-Forwards header is used to limit the number of proxies or gateways that can forward the request
|oMin-Expires HeaderThe Min-Expires header is used to limit the number of proxies or gateways that can forward the request
|oRetry-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
|oRoute HeaderThe Route headers is used to store the route set of a transaction
|oRecord-Route HeaderThe Record-Route headers are used to establish a route for transactions belonging to a session
|oTo HeaderThe To header field specifies the "logical" recipient of the request
|oVia HeaderThe Via header indicates the path taken by the request so far
|oRequest-Disposition HeaderThe Request-Disposition header syntax is defined in RFC 3841 section 10 as follows:
|oAccept-Contact HeaderThe Accept-Contact syntax is defined in RFC 3841 section 10 as follows:
|oReject-Contact HeaderThe Reject-Contact syntax is defined in RFC 3841 section 10 as follows:
|oEvent HeaderThe Event header is used to indicate the which event or class of events the message contains or subscribes
|oAllow-Events HeaderThe Allow-Events header is used to indicate which events or classes of events the notifier supports
|oSubscription-State HeaderThe Subscription-State header is used to indicate in which state a subscription is
|oCall-Info HeaderThe Call-Info header provides additional information about the caller or callee
|oError-Info HeaderThe Error-Info header provides a pointer to additional information about the error status response
|oAlert-Info HeaderWhen present in an INVITE request, the Alert-Info header field specifies an alternative ring tone to the UAS
|oReply-To HeaderThe Reply-To header field contains a logical return URI that may be different from the From header field
|oIn-Reply-To HeaderThe In-Reply-To request header field enumerates the Call-IDs that this call references or returns
|oOrganization HeaderThe Organization header field conveys the name of the organization to which the entity issuing the request or response belongs
|oPriority HeaderThe Priority request-header field indicates the urgency of the request as perceived by the client
|oServer HeaderThe Server response-header field contains information about the software used by the user agent server to handle the request
|oSubject HeaderThe Subject header provides a summary or indicates the nature of the request
|oTimestamp 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
|oUser-Agent HeaderThe User-Agent header contains information about the client user agent originating the request
|oSIP-ETag HeaderThe SIP-ETag header field identifies the published event state
|oSIP-If-Match HeaderThe SIP-If-Match header field identifies the specific entity of event state that the request is refreshing, modifying or removing
|oSuppress-Body-If-Match HeaderThe Suppress-Body-If-Match header field identifies a SIP event content already known by the watcher
|oSuppress-Notify-If-Match HeaderThe Suppress-Notify-If-Match header is used to suppress superfluous NOTIFY transactions
|oRemote-Party-ID HeaderThe syntax of the Remote-Party-ID header is described as follows:
|oP-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
|oP-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
|oAllow HeaderThe Allow header lists the set of methods supported by the user agent generating the message
|oProxy-Require HeaderThe Proxy-Require header is used to indicate proxy-sensitive features that MUST be supported by the proxy
|oRequire 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
|oSupported HeaderThe Supported header enumerates all the capabilities of the client or server
|oUnsupported HeaderThe Unsupported header lists the features not supported by the server
|oPath HeaderThe Path header field is a SIP extension header field (RFC 3327) with syntax very similar to the Record-Route header field
|oService-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
|oAccept HeaderThe Accept request-header field can be used to specify certain media types which are acceptable for the response
|oAccept-Encoding HeaderThe Accept-Encoding header is similar to Accept, but restricts the content-codings that are acceptable in the response
|oAccept-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
|oContent-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
|oContent-Encoding HeaderThe Content-Encoding header indicates what additional content codings have been applied to the entity-body
|oContent-Language HeaderThe Content-Language header RFC 2616 section 14.12 describes the natural language(s) of the intended audience for the enclosed entity
|oContent-Type HeaderThe Content-Type header indicates the media type of the message-body sent to the recipient
|oMIME-Version HeaderMIME-Version header indicates what version of the MIME protocol was used to construct the message
|oWarning HeaderThe Warning response-header field is used to carry additional information about the status of a response
|oRAck HeaderThe RAck header indicates the sequence number of the provisional response which is being acknowledged
|oRSeq HeaderThe RSeq header identifies provisional responses within a transaction
|oReason HeaderThe Reason header is used to indicate why a SIP request was issued or why a provisional response was sent
|oRefer-To HeaderThe Refer-To header provides a URI to reference
|oReferred-By HeaderThe Referred-By header conveys the identity of the original referrer to the referred-to party
|oReplaces 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
|oRefer-Sub HeaderSIP header field Refer-Sub is meaningful and MAY be used with a REFER request and the corresponding 2XX response only
|oAuthorization HeaderThe Authorization header consists of credentials containing the authentication information of the user agent for the realm of the resource being requested
|oProxy-Authenticate HeaderThe Proxy-Authenticate header consists of a challenge that indicates the authentication scheme and parameters applicable to the proxy
|oProxy-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
|oWWW-Authenticate HeaderThe WWW-Authenticate header consists of at least one challenge that indicates the authentication scheme(s) and parameters applicable to the Request-URI
|oAuthentication-Info HeaderThe Authentication-Info header contains either a next-nonce used by next request and/or authentication from server used in mutual authentication
|oProxy-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
|oSecurity-Client HeaderThe Security-Client header is defined by RFC 3329, "Security Mechanism Agreement for the Session Initiation Protocol (SIP)"
|oSecurity-Server HeaderThe Security-Server header is defined by RFC 3329, "Security Mechanism Agreement for the Session Initiation Protocol (SIP)"
|oSecurity-Verify HeaderThe Security-Verify header is defined by RFC 3329, "Security Mechanism Agreement for the Session Initiation Protocol (SIP)"
|oPrivacy HeaderThe Privacy header is used by User-Agent to request privacy services from the network
|oSession-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
oSIP 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.