Session Initiation Protocol (SIP) Parameters2002-012015-07-07Header FieldsAdam RoachThe table below lists the header fields currently defined for the
Session Initiation Protocol (SIP) . Some headers have
single-letter compact forms (Section 7.3 of RFC 3261). Header field
names are case-insensitive.
Standard header fields and messages MUST NOT begin with the leading
characters "P-". Existing "P-" header field registrations are
considered grandfathered, but new registrations of Informational
header fields should not begin with the leading characters "P-"
(unless the "P-" would preserve compatibility with an pre-existing
unregistered usage of the header field, at the discretion of the
Designated Expert). Short forms of header fields MUST only be
assigned to standards track header fields. At the discretion of the
Designated Expert, a header registration may require a Standards
Action.
Session Initiation Protocol (SIP) Event Types NamespaceInformational HeaderExpert ReviewStandard HeaderStandards ActionAcceptAccept-ContactaAccept-EncodingAccept-LanguageAccept-Resource-PriorityAlert-InfoAllowAllow-EventsuAnswer-ModeAuthentication-InfoAuthorizationCall-IDiCall-InfoContactmContent-DispositionContent-EncodingeContent-LanguageContent-LengthlContent-TypecCSeqDateEncryption (Deprecated)Error-InfoEventoExpiresFeature-CapsFlow-TimerFromfGeolocationGeolocation-ErrorGeolocation-RoutingHide (Deprecated)History-InfoIdentityyIdentity-InfonInfo-PackageIn-Reply-ToJoinMax-BreadthMax-ForwardsMIME-VersionMin-ExpiresMin-SEOrganizationP-Access-Network-InfoP-Answer-StateP-Asserted-IdentityP-Asserted-ServiceP-Associated-URIP-Called-Party-IDP-Charging-Function-AddressesP-Charging-VectorP-DCS-Trace-Party-IDP-DCS-OSPSP-DCS-Billing-InfoP-DCS-LAESP-DCS-RedirectP-Early-MediaP-Media-AuthorizationP-Preferred-IdentityP-Preferred-ServiceP-Private-Network-IndicationP-Profile-KeyP-Refused-URI-ListP-Served-UserP-User-DatabaseP-Visited-Network-IDPathPermission-MissingPolicy-ContactPolicy-IDPriorityPriv-Answer-ModePrivacyProxy-AuthenticateProxy-AuthorizationProxy-RequireRAckReasonReason-PhraseReserved to avoid conflict with . Record-RouteRecv-InfoRefer-Events-AtRefer-SubRefer-TorReferred-BybReject-ContactjReplacesReply-ToRequest-DispositiondRequireResource-PriorityResponse-Key (Deprecated)Retry-AfterRouteRSeqSecurity-ClientSecurity-ServerSecurity-VerifyServerService-RouteSession-ExpiresxSession-IDSIP-ETagSIP-If-MatchSubjectsSubscription-StateSupportedkSuppress-If-MatchTarget-DialogTimestampTotTrigger-ConsentUnsupportedUser-AgentUser-to-UserViavWarningWWW-AuthenticateReason ProtocolsSpecification RequiredSIPStatus codeQ.850Cause value in decimal
representationITU-T Q.850PreemptionCause value in decimalsee the separate "Preemption" Registry for default reason-text strings Option TagsStandards ActionOption tags are used in header fields such as Require,
Supported, Proxy-Require, and Unsupported in support of
SIP compatibility mechanisms for extensions. The option
tag itself is a string that is associated with a particular
SIP option (that is, an extension).
It identifies the option to SIP endpoints.100relThis option tag is for reliability of
provisional responses. When present in a
Supported header, it indicates that the UA
can send or receive reliable provisional
responses. When present in a Require header
in a request it indicates that the UAS MUST
send all provisional responses reliably.
When present in a Require header in a
reliable provisional response, it indicates
that the response is to be sent reliably.199This option-tag is for indicating support
of the 199 Early Dialog Terminated
provisional response code. When present in a
Supported header of a request, it indicates
that the UAC supports the 199 response code.
When present in a Require or Proxy-Require
header field of a request, it indicates that
the UAS, or proxies, MUST support the 199
response code. It does not require the UAS,
or proxies, to actually send 199 responses.answermodeThis option tag is for support of the
Answer-Mode and Priv-Answer-Mode
extensions used to negotiate automatic
or manual answering of a request.early-sessionA UA adding the early-session option tag
to a message indicates that it understands
the early-session content disposition.eventlistExtension to allow subscriptions to lists
of resourcesexplicitsubThis option tag identifies an extension to REFER to
suppress the implicit subscription, and provide a URI for an explicit
subscription.from-changeThis option tag is used to indicate that
a UA supports changes to URIs in From and
To header fields during a dialog.geolocation-httpThe "geolocation-http" option tag signals
support for acquiring location information
via an HTTP . A location
recipient who supports this option can
request location with an HTTP GET and
parse a resulting 200 response containing
a PIDF-LO object. The URI schemes
supported by this option include "http"
and "https".geolocation-sipThe "geolocation-sip" option tag signals
support for acquiring location information
via the presence event package of SIP
. A location recipient who
supports this option can send a SUBSCRIBE
request and parse a resulting NOTIFY
containing a PIDF-LO object. The URI
schemes supported by this option include
"sip", "sips", and "pres".ginThis option tag is used to identify the
extension that provides Registration for
Multiple Phone Numbers in SIP. When present
in a Require or Proxy-Require header field of
a REGISTER request, it indicates that support
for this extension is required of registrars
and proxies, respectively, that are a party
to the registration transaction.gruuThis option tag is used to identify the Globally
Routable User Agent URI (GRUU) extension. When
used in a Supported header, it indicates that
a User Agent understands the extension.
When used in a Require header field of a REGISTER
request, it indicates that the registrar is
not expected to process the registration unless
it supports the GRUU extension.histinfoWhen used with the Supported header
field, this option tag indicates the UAC
supports the History Information to be
captured for requests and returned in
subsequent responses. This tag is not
used in a Proxy-Require or Require
header field, since support of
History-Info is optional.iceThis option tag is used to identify the
Interactive Connectivity Establishment (ICE)
extension. When present in a Require header
field, it indicates that ICE is required by
an agent.joinSupport for the SIP Join Headermultiple-referThis option tag indicates support
for REFER requests that contain a
resource list document describing
multiple REFER targets.norefersubThis option tag specifies a User Agent
ability of accepting a REFER request without
establishing an implicit subscription
(compared to the default case defined in
.nosubThis option tag identifies an extension to REFER to
suppress the implicit subscription, and indicate that no explicit
subscription is forthcoming.outboundThis option-tag is used to identify UAs and
Registrars which support extensions for
Client Initiated Connections. A UA places
this option in a Supported header to
communicate its support for this extension.
A Registrar places this option-tag in a
Require header to indicate to the
registering User Agent that the Registrar
used registrations using the binding rules
defined in this extension.pathA SIP UA that supports the Path extension
header field includes this option tag as a
header field value in a Supported header
field in all requests generated by that UA.
Intermediate proxies may use the presence
of this option tag in a REGISTER request to
determine whether to offer Path service for
for that request. If an intermediate proxy
requires that the registrar support Path for
a request, then it includes this option tag
as a header field value in a Requires
header field in that request.policyThis option tag is used to indicate that
a UA can process policy server URIs for
and subscribe to session-specific
policies.preconditionAn offerer MUST include this tag in the
Require header field if the offer contains
one or more "mandatory" strength-tags. If
all the strength-tags in the description are
"optional" or "none" the offerer MUST include
this tag either in a Supported header field
or in a Require header field.prefThis option tag is used to ensure that a
server understands the callee capabilities
parameters used in the request.privacyThis option tag indicates support for the
Privacy mechanism. When used in the
Proxy-Require header, it indicates that proxy
servers do not forward the request unless they
can provide the requested privacy service.
This tag is not used in the Require or
Supported headers. Proxies remove this option
tag before forwarding the request if the desired
privacy function has been performed.recipient-list-inviteThe body contains a list of URIs
that indicates the recipients of the
SIP INVITE requestrecipient-list-messageThe body contains a list of URIs
that indicates the recipients of
the SIP MESSAGE requestrecipient-list-subscribeThis option tag is used to ensure
that a server can process the
recipient-list body used in a
SUBSCRIBE request.replacesThis option tag indicates support for the
SIP Replaces header.resource-priorityIndicates or requests support for the
resource priority mechanism.sdp-anatThe option-tag sdp-anat is defined for use
in the Require and Supported SIP
header fields. SIP user agents that place this
option-tag in a Supported header field understand
the ANAT semantics as defined in .sec-agreeThis option tag indicates support for the
Security Agreement mechanism. When used in the
Require, or Proxy-Require headers, it indicates
that proxy servers are required to use the
Security Agreement mechanism. When used in
the Supported header, it indicates that the
User Agent Client supports the Security Agreement
mechanism. When used in the Require header
in the 494 (Security Agreement Required) or
421 (Extension Required) responses, it
indicates that the User Agent Client must
use the Security Agreement Mechanism.tdialogThis option tag is used to identify the target
dialog header field extension. When used in
a Require header field, it implies that the
recipient needs to support the Target-Dialog
header field. When used in a Supported header
field, it implies that the sender of the message
supports it.timerThis option tag is for support of the
session timer extension. Inclusion in a Supported
header field in a request or response indicates
that the UA is capable of performing refreshes
according to that specification. Inclusion
in a Require header in a request means that
the UAS must understand the session timer extension
to process the request. Inclusion in a Require
header field in a response indicates that the
UAC must look for the Session-Expires header
field in the response, and process accordingly.uuiThis option tag is used to indicate that
a UA supports and understands the User-to-User header field.Warning Codes (warn-codes)Section 27.2Warning codes provide information supplemental to the status code
in SIP response messages.300Incompatible network protocol: One or more network
protocols contained in the session description are
not available.301Incompatible network address formats: One or more
network address formats contained in the session
description are not available.302Incompatible transport protocol: One or more
transport protocols described in the session
description are not available.303Incompatible bandwidth units: One or more bandwidth
measurement units contained in the session
description were not understood.304Media type not available: One or more media types
contained in the session description are not
available.305Incompatible media format: One or more media formats
contained in the session description are not
available.306Attribute not understood: One or more of the media
attributes in the session description are not
supported.307Session description parameter not understood: A
parameter other than those listed above was not
understood.330Multicast not available: The site where the user is
located does not support multicast.331Unicast not available: The site where the user is
located does not support unicast communication
(usually due to the presence of a firewall).370Insufficient bandwidth: The bandwidth specified in
the session description or defined by the media
exceeds that known to be available.380SIPS Not Allowed: The UAS or proxy cannot process
the request because the SIPS scheme is not allowed
(e.g., because there are currently no registered
SIPS Contacts).381SIPS Required: The UAS or proxy cannot process the
request because the SIPS scheme is required.399Miscellaneous warning: The warning text can include
arbitrary information to be presented to a human user
or logged. A system receiving this warning MUST NOT
take any automated action.Methods and Response CodesStandards ActionACKBYECANCELINFOINVITEMESSAGENOTIFYOPTIONSPRACKPUBLISHREFERREGISTERSUBSCRIBEUPDATEResponse Codes All response codes below are defined by unless
otherwise noted.1xxProvisional100Trying180Ringing181Call Is Being Forwarded182Queued183Session Progress199Early Dialog Terminated2xxSuccessful200OK202Accepted (Deprecated)204No Notification3xxRedirection300Multiple Choices301Moved Permanently302Moved Temporarily305Use Proxy380Alternative Service4xxRequest Failure400Bad Request401Unauthorized402Payment Required403Forbidden404Not Found405Method Not Allowed406Not Acceptable407Proxy Authentication Required408Request Timeout410Gone412Conditional Request Failed413Request Entity Too Large414Request-URI Too Long415Unsupported Media Type416Unsupported URI Scheme417Unknown Resource-Priority420Bad Extension421Extension Required422Session Interval Too Small423Interval Too Brief424Bad Location Information428Use Identity Header429Provide Referrer Identity430Flow Failed433Anonymity Disallowed436Bad Identity-Info437Unsupported Certificate438Invalid Identity Header439First Hop Lacks Outbound Support440Max-Breadth Exceeded469Bad Info Package470Consent Needed480Temporarily Unavailable481Call/Transaction Does Not Exist482Loop Detected483Too Many Hops484Address Incomplete485Ambiguous486Busy Here487Request Terminated488Not Acceptable Here489Bad Event491Request Pending493Undecipherable494Security Agreement Required5xxServer Failure500Server Internal Error501Not Implemented502Bad Gateway503Service Unavailable504Server Time-out505Version Not Supported513Message Too Large580Precondition Failure6xxGlobal Failures600Busy Everywhere603Decline604Does Not Exist Anywhere606Not AcceptableSIP Privacy Header Field ValuesIETF ReviewuserRequest that privacy services
provide a user-level privacy functionheaderRequest that privacy services modify
headers that cannot be set arbitrarily
by the user (Contact/Via).sessionRequest that privacy services provide
privacy for session medianonePrivacy services must not perform any
privacy functioncriticalPrivacy service must perform the
specified services or fail the requestidPrivacy requsted for Third-Party
Asserted IdentityhistoryPrivacy requested for
History-Info header field(s)Security Mechanism NamesRFC3329 Section 6digesttlsipsec-ikeipsec-manipsec-3gppCompression SchemesRFC3486 Section 11Signaling CompressionsigcompSIP/SIPS URI ParametersStandards ActionaaiNobncNocauseYesccxmlNocompYescontent-typeNodelayNodurationNoextensionNogrNoiotlYeslocaleNolrNomYesmaddrNomaxageNomaxstaleNomethod"get" / "post"methodYesobNoparam[n]NoplayNopostbodyNorepeatNosgNosigcomp-idNotargetNotransportYesttlNouserYesvoicexmlNoHeader Field Parameters and Parameter ValuesPublished RFC (A standards-track RFC is NOT required)AcceptqNoAccept-EncodingqNoAccept-LanguageqNoAlert-InfoappearanceNoAnswer-ModerequireNoAuthorizationalgorithmYesAuthorizationautsNoAuthorizationcnonceNoAuthorizationncNoAuthorizationnonceNoAuthorizationopaqueNoAuthorizationqopYesAuthorizationrealmNoAuthorizationresponseNoAuthorizationuriNoAuthorizationusernameNoAuthentication-InfocnonceNoAuthentication-InfoncNoAuthentication-InfonextnonceNoAuthentication-InfoqopYesAuthentication-InforspauthNoCall-InfomYesCall-InfopurposeYesContactexpiresNoContactmpNoContactnpNoContactpub-gruuNoContactqNoContactrcNoContactreg-idNoContacttemp-gruuNoContacttemp-gruu-cookieNoContent-DispositionhandlingYesEventadaptive-min-rateNoEventbodyYesEventcall-idNoEventeffective-byNoEventfrom-tagNoEventidNoEventinclude-session-descriptionNoEventmax-rateNoEventmin-rateNoEventmodelNoEventprofile-typeYesEventsharedNoEventto-tagNoEventvendorNoEventversionNoFeature-Capsfcap-name NoFromtagNoGeolocation-ErrorcodeYesHistory-InfompNoHistory-InfonpNoHistory-InforcNoP-Access-Network-Infocgi-3gppNoP-Access-Network-Infoci-3gpp2NoP-Access-Network-Infoci-3gpp2-femtoNoP-Access-Network-Infodsl-locationNoP-Access-Network-Infodvb-rcs2-node-idNoP-Access-Network-Infoeth-locationNoP-Access-Network-Infofiber-locationNoP-Access-Network-Infogstn-locationNoP-Access-Network-Infoi-wlan-node-idNoP-Access-Network-Infolocal-time-zoneNoP-Access-Network-Infooperator-specific-GINoP-Access-Network-Infoutran-cell-id-3gppNoP-Access-Network-Infoutran-sai-3gppNoP-Charging-Function-AddressesccfNoP-Charging-Function-Addressesccf-2NoP-Charging-Function-AddressesecfNoP-Charging-Function-Addressesecf-2NoP-Charging-Vectoricid-valueNoP-Charging-Vectoricid-generated-atNoP-Charging-Vectororig-ioiNoP-Charging-Vectorrelated-icidNoP-Charging-Vectorrelated-icid-generated-atNoP-Charging-Vectorterm-ioiNoP-Charging-Vectortransit-ioiNoP-DCS-Billing-InfocalledNoP-DCS-Billing-InfocallingNoP-DCS-Billing-InfochargeNoP-DCS-Billing-InfojipNoP-DCS-Billing-InfolocrouteNoP-DCS-Billing-InforksgroupNoP-DCS-Billing-InforoutingNoP-DCS-LAESbcidNoP-DCS-LAEScccidNoP-DCS-LAEScontentNoP-DCS-LAESkey (OBSOLETED)NoP-DCS-RedirectcountNoP-DCS-Redirectredirector-uriNoP-DCS-Trace-Party-IDtimestampNoP-Refused-URI-ListmembersNoPolicy-Contactnon-cacheableYesPriv-Answer-ModerequireNoProxy-AuthenticatealgorithmYesProxy-AuthenticatedomainNoProxy-AuthenticatenonceNoProxy-AuthenticateopaqueNoProxy-AuthenticateqopYesProxy-AuthenticaterealmNoProxy-AuthenticatestaleYesProxy-AuthorizationalgorithmYesProxy-AuthorizationautsNoProxy-AuthorizationcnonceNoProxy-AuthorizationncNoProxy-AuthorizationnonceNoProxy-AuthorizationopaqueNoProxy-AuthorizationqopYesProxy-AuthorizationrealmNoProxy-AuthorizationresponseNoProxy-AuthorizationuriNoProxy-AuthorizationusernameNoReasoncauseYesReasontextNoRetry-AfterdurationNoSecurity-ClientalgYesSecurity-ClientealgYesSecurity-Clientd-algYesSecurity-Clientd-qopYesSecurity-Clientd-verNoSecurity-ClientmodYesSecurity-Clientport1NoSecurity-Clientport2NoSecurity-ClientprotYesSecurity-ClientqNoSecurity-ClientspiNoSecurity-ServeralgYesSecurity-ServerealgYesSecurity-Serverd-algYesSecurity-Serverd-qopYesSecurity-Serverd-verNoSecurity-ServermodYesSecurity-Serverport1NoSecurity-Serverport2NoSecurity-ServerprotYesSecurity-ServerqNoSecurity-ServerspiNoSecurity-VerifyalgYesSecurity-VerifyealgYesSecurity-Verifyd-algYesSecurity-Verifyd-qopYesSecurity-Verifyd-verNoSecurity-VerifymodYesSecurity-Verifyport1NoSecurity-Verifyport2NoSecurity-VerifyprotYesSecurity-VerifyqNoSecurity-VerifyspiNoSubscription-Stateadaptive-min-rateNoSubscription-StateexpiresNoSubscription-Statemax-rateNoSubscription-Statemin-rateNoSubscription-StatereasonYesSubscription-Stateretry-afterNoTarget-Dialoglocal-tagNoTarget-Dialogremote-tagNoTotagNoTrigger-Consenttarget-uriNoUser-to-UsercontentNoUser-to-UserencodingYesUser-to-UserpurposeNoViaaliasNoViabranchNoViacompYesViakeepNoViamaddrNoViaocYesViaoc-algoYesViaoc-seqYesViaoc-validityYesViareceivedNoViarportNoViasigcomp-idNoViattlNoWWW-AuthenticatealgorithmYesWWW-AuthenticatedomainYesWWW-AuthenticatenonceNoWWW-AuthenticateopaqueNoWWW-AuthenticateqopYesWWW-AuthenticaterealmNoWWW-AuthenticatestaleYes<fcap-name> denotes parameter names conforming to the
syntax <fcap-name> defined in .
Valid feature-capability indicators are registered in the
Proxy-Feature Feature-Capability Indicator Trees registry.URI PurposesSpecification RequiredparticipationThe URI can be used to join the conferencestreamingThe URI can be used to access the streamed
conference dataeventThe URI can be used to subscribe to the
conference event packagerecordingThe URI can be used to access the recorded
conference dataweb-pageThe URI can be used to access a web page
that contains additional information of
the conferenceccmpThe URI can be used to indicate that the
conference focus supports CCMP.grouptextchatThe URI can be used to join a multi-user chat directly
associated with the conferenceResource-Priority NamespacesIETF ReviewNamespace = the unique string identifying the namespace
Namespace Numerical Value = the unique numerical value identifying the namespace
Levels = the number of priority-values within the namespace
Algorithm = Intended operational behavior of SIP elements
implementing this namespace
New Warn code = New Warning Codes (warn-codes) introduced by this namespace
New Resp. code = New SIP response codes introduced by this namespace
Reference = IETF document reference for this namespace
Namespace Numerical Value = dsn05preemptionnonodrsn16preemptionnonoq73525preemptionnonoets35queuenonowps45queuenonodsn-000000510preemptionnonodsn-000001610preemptionnonodsn-000002710preemptionnonodsn-000003810preemptionnonodsn-000004910preemptionnonodsn-0000051010preemptionnonodsn-0000061110preemptionnonodsn-0000071210preemptionnonodsn-0000081310preemptionnonodsn-0000091410preemptionnonodrsn-0000001510preemptionnonodrsn-0000011610preemptionnonodrsn-0000021710preemptionnonodrsn-0000031810preemptionnonodrsn-0000041910preemptionnonodrsn-0000052010preemptionnonodrsn-0000062110preemptionnonodrsn-0000072210preemptionnonodrsn-0000082310preemptionnonodrsn-0000092410preemptionnonorts-0000002510preemptionnonorts-0000012610preemptionnonorts-0000022710preemptionnonorts-0000032810preemptionnonorts-0000042910preemptionnonorts-0000053010preemptionnonorts-0000063110preemptionnonorts-0000073210preemptionnonorts-0000083310preemptionnonorts-0000093410preemptionnonocrts-0000003510preemptionnonocrts-0000013610preemptionnonocrts-0000023710preemptionnonocrts-0000033810preemptionnonocrts-0000043910preemptionnonocrts-0000054010preemptionnonocrts-0000064110preemptionnonocrts-0000074210preemptionnonocrts-0000084310preemptionnonocrts-0000094410preemptionnonoesnet455queuenonoResource-Priority Priority-valuesIETF ReviewLegend:
Namespace Numerical Value = the unique numerical value identifying the namespace
Priority Numerical Value: Namespace: drsn"routine"5"priority"4"immediate"3"flash"2"flash-override"1"flash-override-override"0Namespace: dsn"routine"4"priority"3"immediate"2"flash"1"flash-override"0Namespace: q735"4"4"3"3"2"2"1"1"0"0Namespace: ets"4"4"3"3"2"2"1"1"0"0Namespace: wps"4"4"3"3"2"2"1"1"0"0Namespace: dsn-000000"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: dsn-000001"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: dsn-000002"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: dsn-000003"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: dsn-000004"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: dsn-000005"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: dsn-000006"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: dsn-000007"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: dsn-000008"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: dsn-000009"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000000"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000001"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000002"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000003"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000004"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000005"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000006"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000007"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000008"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: drsn-000009"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000000"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000001"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000002"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000003"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000004"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000005"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000006"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000007"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000008"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: rts-000009"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000000"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000001"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000002"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000003"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000004"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000005"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000006"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000007"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000008"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: crts-000009"0"9"1"8"2"7"3"6"4"5"5"4"6"3"7"2"8"1"9"0Namespace: esnet"0"4"1"3"2"2"3"1"4"0Identity-Info ParametersStandards Track RFCalgIdentity-Info Algorithm Parameter ValuesStandards Track RFCrsa-sha1rsa-sha256SIP Forum User Agent Configuration Parametersbegins with 'sfua-'RFC Requiredall other namesFirst Come First Servedsfua-idThe URN identifying the User Agent, constructed as specified
in section 4.1 of "Managing Client-Initiated
Connections in the Session Initiation Protocol (SIP)".
Since the procedure defined by allows any UA to
construct a value for this parameter, the sfua-id parameter
MUST always be included.
If the UA implements , and includes the
'+sip.instance' Contact header field parameter in any request,
when requesting configuration it MUST use the same value for
the sfua-id parameter.sfua-userAn identifier for a user associated with the configuration. Note
that this might be different than any SIP 'user' in the UA
configuration: it could, for example, be the login name of an
account on the service provider web site. The syntax of this
parameter is that of the 'userid'.
See Section 2.4.1, "Configuration Data Request Authentication" for
how this parameter relates to authentication of the configuration
data request.sfua-vendorAn identifier that specifies the vendor of the User Agent. The
syntax of the value of this parameter is that of a DNS domain.
The domain value MUST be that of a domain owned by the vendor.sfua-modelAn identifier that further specifies the User Agent from among
those produced by the vendor. The syntax of the value of this
parameter is the same as the 'token'. Values for this
parameter are selected by the vendor.sfua-revisionAn identifier that further specifies the User Agent from among
those produced by the vendor. The syntax of the value of this
parameter is the same as the 'token'. Values for this
parameter are selected by the vendor.Service-ID/Application-ID LabelsSpecification Required3gpp-serviceCommunication services defined by 3GPP for use by the IM CN
subsystem and its attached UAs. This value in itself does not define
a service and requires subsequent labels to define the service.3gpp-applicationApplications defined by 3GPP for use by UAs attached to the IM CN
subsystem. This value in itself does not define a service and
requires subsequent labels to define the service.Info Packages RegistrySpecification RequiredAdam Roachg.3gpp.access-transfer-events3GPP TS 24.237 v11.14.0SIP Configuration Profile TypesSpecification Requiredlocal-networkdeviceuserGeolocation-Error CodesSpecification Required100"Cannot Process Location"200"Permission to Use Location Information"201"Permission to Retransmit Location Information to a Third Party"202"Permission to Route Based on Location Information"300"Deference Failure"Reason CodesRFC RequireddeactivatedprobationrejectedtimeoutgiveupnoresourceinvariantbadfilterProxy-Feature Feature-Capability Indicator TreesStandards ActionSession Initiation Protocol (SIP) Event Types Namespaceg.Global Feature Capability Indicator Treesip.SIP Feature Capability Indicator TreeGlobal Feature-Capability Indicator Registration TreeSpecification RequiredPaul Kyzivat (primary), Christer Holmberg (secondary)g.3gpp.iut-focusThis feature-capability indicator when used in a Feature-Caps header
field of a SIP request or a SIP response indicates that the function which inserted
the Feature-Caps header field supports anchoring an IUT session.3GPP TS 24.337 10.7.0g.3gpp.mid-callThis feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that:
1. the functional entity including the feature-capability indicator in the SIP message supports the MSC server assisted mid-call feature; and
2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to
support the feature do support the MSC server assisted mid-call feature.3GPP TS 24.237 10.10.0g.3gpp.atcfThis feature-capability indicator when included in a Feature-Caps header field as specified in IETF RFC 6809 in a SIP
REGISTER request or a SIP response to the SIP REGISTER request indicates presence and support of a resource which is an Access
Transfer Control Function (ATCF) and also the session transfer number allocated to the ATCF.3GPP TS 24.237 10.10.0g.3gpp.srvcc-alertingThis feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that:
1. the functional entity including the feature-capability indicator in the SIP message supports access transfer for calls in alerting phase; and
2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to support
the feature do support access transfer for calls in alerting phase.3GPP TS 24.237 10.10.0g.3gpp.atcf-mgmt-uriThis feature-capability indicator when used in a Feature-Caps header field as specified in IETF RFC 6809 [60] in SIP REGISTER
request indicates presence and support of performing as a UAS for SIP requests for ATCF management received at this URI.3GPP TS 24.237 10.10.0g.3gpp.srvccThis feature-capability indicator when included in a Feature-Caps header field as specified in IETF RFC 6809 of:
- a SIP INVITE request; or
- a SIP INVITE response;
indicates presence and support of a resource capable of performing the SRVCC access transfer procedure as specified in 3GPP TS 24.237.3GPP TS 24.237 10.10.0g.3gpp.atcf-pathThis feature-capability indicator when used in a Feature-Caps header field as specified in IETF RFC 6809 in SIP REGISTER
request indicates capability of identifying the registration path and binding SRVCC related information to it.3GPP TS 24.237 10.10.0g.3gpp.cs2ps-srvccThis feature-capability indicator when included in Feature-Caps
header field as specified in IETF RFC 6809 [60] indicates support of the
CS to PS single radio voice call continuity as specified in 3GPP TS 24.237.3GPP TS 24.237 11.10.0g.3gpp.tiThis feature-capability indicator when used in a Feature-Caps
header field as specified in IETF RFC 6809 in SIP INVITE request or SIP
response to the SIP INVITE request indicates the capability of associating
a CS call with dialog created by the SIP INVITE request.3GPP TS 24.237 11.10.0g.3gpp.loopbackThis feature-capability indicator, when included in a
Feature-Caps header field as specified in RFC 6809 in a SIP INVITE
request, indicates the support of the roaming architecture for voice
over IMS with local breakout.3GPP TS 24.229g.3gpp.trfThis feature-capability indicator, when included in a
Feature-Caps header field as specified in RFC 6809 in a SIP INVITE
request, indicates that in a roaming scenario, the visited network
supports a transit and roaming functionality in order to allow loopback
of session requests to the visited network from the home network. When
used, it may indicate the URI of the transit and roaming functionality.3GPP TS 24.229 11.11.0g.3gpp.home-visitedThis feature-capability indicator, when included in a
Feature-Caps header field as specified in RFC 6809 in a SIP INVITE
request, indicates that the home network supports loopback to the
identified visited network for this session. The loopback is expected
to be applied at some subsequent entity to the insertion point. The
feature-capability indicator carries a parameter value which indicates
the visited network.3GPP TS 24.229g.3gpp.mrbThis feature-capability indicator when included in a
Feature-Caps header field as specified in RFC 6809in a SIP INVITE
request indicates that in a roaming scenario, the visited network
supports media resource broker functionality for the allocation of
multimedia resources in the visited network. When used, it indicates
the URI of the visited network MRB.3GPP TS 24.229 11.11.0g.3gpp.icsi-refEach value of the Service Reference feature-capability indicator
indicates the software applications supported by the entity. The values for
this feature-capability indicator equal the IMS communication Service
Identifier (ICSI) values supported by the entity.
Multiple feature-capability indicator values can be included in the Service
Reference feature-capability indicators.
When included in the Feature-Caps header field, according to RFC 6809, the value
of this feature-capability indicator contains the IMS communication service
identifier (ICSI) of the IMS communication service supported for use 1) in the
standalone transaction (if included in a request for a standalone transaction or
a response associated with it) or 2) in the dialog (if included in an initial request for dialog or a response associated with it) by the entity which included the Feature-Caps header field.3GPP TS 24.229 11.12.0g.3gpp.drvcc-alertingThis feature-capability indicator when included in a
Feature-Caps header field as specified in IETF RFC 6809 in a SIP INVITE
request or a SIP response to the SIP INVITE request indicates support of
PS to CS dual radio access transfer for calls in alerting phase.3GPP TS 24.237 12.8.0g.3gpp.dynamic-stnThis feature-capability indicator g.3gpp.dynamic-stn, when
included in a Feature-Caps header field as specified in IETF RFC 6809
in a SIP INVITE request or a SIP response to the SIP INVITE request,
indicates support to transfer the session to the circuit switched (CS)
domain using the dynamic STN (session transfer number) digit string.3GPP TS 24.237 12.8.0g.3gpp.ps2cs-drvcc-orig-pre-alertingThis feature-capability indicator
g.3gpp.ps2cs-srvcc-orig-pre-alerting when used in a Feature-Caps header
field of a SIP request or a SIP response indicates that:
1. the functional entity including the feature-capability indicator in the SIP
message supports the PS to CS SRVCC for originating calls in pre-alerting phase; and
2. all entities of which the functional entity including the feature-capability
indicator in the SIP message is aware of being requested to support the feature
do support the PS to CS SRVCC for originating calls in pre-alerting phase.3GPP TS 24.237 12.8.0g.3gpp.ps2cs-srvcc-orig-pre-alertingThis feature-capability indicator
g.3gpp.ps2cs-srvcc-orig-pre-alerting when used in a Feature-Caps header
field of a SIP request or a SIP response indicates that:
1. the functional entity including the feature-capability indicator in the SIP
message supports the PS to CS SRVCC for originating calls in pre-alerting phase;
and
2. all entities of which the functional entity including the feature-capability
indicator in the SIP message is aware of being requested to support the feature
do support the PS to CS SRVCC for originating calls in pre-alerting phase.3GPP TS 24.237 12.8.0SIP Feature-Capability Indicator Registration TreeIETF ReviewPriority Header Field ValuesIETF Reviewnon-urgentnormalurgentemergencypsap-callbackSIP TransportStandards ActionUDPTCPTLSSCTPTLS-SCTPWSWSSUUI PackagesStandards ActionUUI packages provide information about the usage of the UUI data in
a User-to-User header field .
isdn-uuiThe associated application is being used with
constraints suitable for interworking with the ISDN User-to-User
service, and therefore can be interworked at ISDN gateways.UUI Content ParametersStandards ActionUUI content provides information about the content of the UUI data in
a User-to-User header field .
isdn-uuiThe associated contents conforms to the content
associated with the ISDN User-to-User service. In the presence of
the "purpose" header field parameter set to "isdn-uui" (or the
absence of any "purpose" header field parameter) this is the
default meaning and therefore need not be included in this case.UUI Encoding ParametersStandards ActionUUI encoding provides information about the encoding of the UUI data in
a User-to-User header field .
hexThe UUI data is encoded using hexadecimalAdam Roachmailto:adam&nostrum.com2013-02-26Cullen Jenningsmailto:fluffy&cisco.comFrederic Firminmailto:frederic.firmin&etsi.org2015-04-09Jon Petersonmailto:jon.peterson&neustar.bizMary Barnesmailto:mary.ietf.barnes&gmail.com2013-06-18