hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.3 ISC gateway function as an entry point | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.3.1 Registration | There are no specific requirements for the REGISTER method, i.e. the REGISTER method is treated as for other SIP methods. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.3.2 General | This subclause applies for requests sent from the AS to the S-CSCF via the ISC gateway function. Such requests come from the AS as a result of a request received from the S-CSCF and forwarded by the ISC gateway function.
For all SIP transactions identified:
- if priority is supported (NOTE), as containing an authorised... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.3.3 Initial requests | Upon receipt of:
- an initial request for a dialog;
- a request for a standalone transaction; or
- a request for an unknown method that does not relate to an existing dialog;
the ISC gateway function shall verify whether the request is arrived from a trusted domain or not. If the request arrived from an untrusted domai... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.3.4 Subsequent requests | Upon receipt of a subsequent request, the ISC gateway function shall:
1) if the request is an INVITE request, then respond with a 100 (Trying) provisional response;
2) if the request is a NOTIFY request with the Subscription-State header field set to "terminated" and the ISC gateway function has retained the SIP dialog... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.3.5 Call release initiated by the ISC gateway function | If the ISC gateway function provides transport plane control functionality and receives an indication of a transport plane related error the ISC gateway function may:
1) generate a BYE request for the terminating side based on information saved for the related dialog; and
2) generate a BYE request for the originating s... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.4 THIG functionality in the ISC gateway function | The ISC gateway function shall act according to the procedures defined for the IBCF in subclause 5.10.4 with the following exceptions:
- there are no specific requirements for the REGISTER method, i.e. the REGISTER method is treated as for other SIP methods. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.5 IMS-ALG functionality in the ISC gateway function | The ISC gateway function shall act according to the procedures defined for the IBCF in subclause 5.10.5. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.6 Screening of SIP signalling | The ISC gateway function shall act according to the procedures defined for the IBCF in subclause 5.10.6.
NOTE 1: Subclause 5.10.6 identifies a number of header fields that should not be screened. It is not expected that the ISC gateway function will see these header fields.
NOTE 2: In identifying header fields to be sc... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6 Application usage of SDP | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.1 Procedures at the UE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.1.1 General | The "integration of resource management and SIP" extension is hereafter in this subclause referred to as "the precondition mechanism" and is defined in RFC 3312 [30] as updated by RFC 4032 [64].
In order to authorize the media streams, the P-CSCF and S-CSCF have to be able to inspect SDP message bodies. Hence, the UE s... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.1.2 Handling of SDP at the originating UE | An INVITE request generated by a UE shall contain a SDP offer and at least one media description. This SDP offer shall reflect the calling user's terminal capabilities and user preferences for the session.
If the desired QoS resources for one or more media streams have not been reserved at the UE when constructing the ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.1.3 Handling of SDP at the terminating UE | Upon receipt of an initial SDP offer in which no precondition information is available, the terminating UE shall in the SDP answer:
- if, prior to sending the SDP answer the desired QoS resources have been reserved at the terminating UE, set the related media streams in the SDP answer to:
- active mode, if the offered ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.1.4 Session modification | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.1.4.1 General | This subclause applies after the 2xx response to the initial INVITE request has been sent or received. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.1.4.2 Generating session modification request | If the precondition mechanism is used for the session modification, the following applies:
a) if the session modification does not increase the QoS requirement of the already established media stream (e.g., all the media streams in a call hold procedure, audio stream in a call upgrade procedure), in the SDP body of the... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.1.4.3 Receiving session modification request | If the precondition mechanism is used for the session modification, the settings of the current and desired QoS status shall be the same as specified in subclause 6.1.3. If the network cannot modify or reserve the required resources, the UE shall send a 580 (Precondition-Failure) response towards the UE that initiated ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.2 Procedures at the P-CSCF | The P-CSCF shall perform IMS-ALG functionality:
- when the P-CSCF needs to perform procedures for hosted NAT traversal according to Annex F; or
- when the P-CSCF needs to perform procedures for media plane security (see subclause 6.7.2.2);
- when required by the user-related policies provisioned to the P-CSCF (see subc... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.3 Procedures at the S-CSCF | When the S-CSCF receives any SIP request containing an SDP offer, the S-CSCF shall examine the media parameters in the received SDP offer. If the S-CSCF finds any media parameters which are not allowed based on local policy or subscription (i.e. the information in the instances of the Core Network Service Authorization... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.4 Procedures at the MGCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.4.1 Calls originating from circuit-switched networks | The usage of SDP by the MGCF is the same as its usage by the UE, as defined in the subclause 6.1 and A.3.2, with the following exceptions:
- in an initial INVITE request generated by a MGCF, the MGCF shall indicate the current status of the local precondition;
- end-to-access edge media security is not applicable to th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.4.2 Calls terminating in circuit-switched networks | The usage of SDP by the MGCF is the same as its usage by the UE, as defined in the subclause 6.1 and A.3.2, with the following exceptions:
a) when the MGCF sends a 183 (Session Progress) response with an SDP message body, the MGCF shall only request confirmation for the result of the resource reservation (as defined in... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.4.3 Optimal Media Routeing (OMR) | If the MGCF supports OMR it shall also perform the UA procedures described in 3GPP TS 29.079 [11D]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.4.4 Explicit congestion control support in MGCF | An MGW associated with an MGCF can support Explicit Congestion Notification (ECN) according to RFC 3168 [189], and can act as an ECN endpoint to enable ECN with a local ECN-capable terminal within a local network that properly handles ECN-marked packets.
If the MGCF receives a SDP offer containing ECN attribute "a=ecn-... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.5 Procedures at the MRFC | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.6 Procedures at the AS | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.6.1 General | Since an AS may provide a wide range of different services, procedures for the SDP usage for an AS acting as originating UA, terminating UA or third-party call control role are dependent on the service provided to the UA and on the capabilities on the remote UA. There is no special requirements regarding the usage of t... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.6.2 Transcoding | The AS shall send an SDP offer to the MRFC with the codecs supported by the caller and the codecs to be offered towards the callee, and the IP address and port information received from caller, in seperate media lines. When receiving an SDP answer from the MRFC, the AS shall forward the received selected codecs and IP ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.6.3 AS procedures to support WebRTC media optimization procedure | When an AS acts as a B2BUA, and it controls media resources using an MRF, it may support switching to transparent media for WebRTC when those media have been negotiated, as specified in annex U.2.4 of 3GPP TS 23.228 [7]. An AS that supports switching to transparent media for WebRTC shall apply the procedures in the pre... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7 Procedures at the IMS-ALG functionality | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1 IMS-ALG in IBCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.1 General | When the IBCF acts as an IMS-ALG, it makes procedures as for an originating UA and terminating UA. The IMS-ALG acts as a B2BUA. The general treatment of the SDP information between originating UA and terminating UA is described in 3GPP TS 29.162 [11A]. For the use of the IMS-ALG for specific capabilities, additional pr... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.2 IMS-ALG in IBCF for support of ICE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.2.1 General | This subclause describes procedures of an IBCF to support ICE as defined in RFC 8445 [289] and RFC 8839 [290].
If no TrGW is inserted, an IBCF may transparently pass ICE related SDP attibutes to support ICE. The remaining procedures in this subclause are only applicable if the IBCF is inserting a TrGW on the media plan... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.2.2 IBCF full ICE procedures for UDP based streams | 6.7.1.2.2.1 General
This subclause describes the IBCF full ICE procedures for UDP based streams.
6.7.1.2.2.2 IBCF receiving SDP offer
When the IBCF receives an SDP offer including ICE candidate information, the IBCF shall send the candidate information for each UDP based stream received in the SDP offer towards the TrG... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.2.3 IBCF ICE lite procedures for UDP based streams | When the IBCF is using ICE lite procedures for UDP based streams, the IBCF procedures are identical as described in subclause 6.7.1.2.2, with the following exceptions:
- The IBCF always acts as an ICE controlled entity towards the SDP offerer and towards the SDP answerer, and;
- The IBCF requests the TrGW to perform IC... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.2.4 ICE procedures for TCP based streams | 6.7.1.2.4.1 General
The IBCF shall terminate ICE procedures for TCP based streams. Instead the IBCF will use the mechanism defined in RFC 4145 [83] for establishing TCP based streams, as defined in RFC 6544 [131].
An entity that supports ICE continues the ICE procedures for UDP based streams, even if no candidates are ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.3 IMS-ALG in IBCF for transcoding | Before forwarding the SDP offer to the answerer, the IBCF may add to the selected media one or more codecs to the codec list contained in the SDP offer. The codecs added to the SDP offer are based on local policy and shall be in accordance with the requirements of clause T.2.
NOTE 1: The local policy can be based on su... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.4 IMS-ALG in IBCF for NA(P)T and NA(P)T-PT controlled by the IBCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.4.1 General | This subclause describes the IBCF procedures for supporting the scenario where IP address and/or port conversions occur at the TrGW level in the media path between the UE and the backbone. Two types of address conversions are covered:
- IP version interworking (NA(P)T-PT); and
- IP address/port translation (NA(P)T).
Wh... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.1.5 IMS-ALG procedure in IBCF to support WebRTC media optimization procedure | The IMS-ALG in the IBCF may support switching to transparent media for WebRTC when those media have been negotiated, as specified in annex U.2.4 of 3GPP TS 23.228 [7]. An IMS-ALG that supports switching to transparent media for WebRTC shall apply the procedures in the present subclause.
NOTE 1: The IMS-ALG can in addit... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2 IMS-ALG in P-CSCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.1 General | This subclause specifies the general procedures for the support of SDP in IMS-ALG within the P-CSCF. For the use of the IMS-ALG for specific capabilities, additional procedures are defined in subsequent subclauses.
When the IMS-ALG receives an SDP offer, it shall create a new SDP offer, based the contents of the receiv... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.2 IMS-ALG in P-CSCF for media plane security | When the P-CSCF acts as an IMS-ALG, it acts as a B2BUA and modifies the SDP as described as described in 3GPP TS 23.334 [7F].
If the P-CSCF indicated support for end-to-access-edge media security using SDES during registration:
1) upon receiving an SDP offer from the served UE containing an end-to-access-edge protected... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.3 IMS-ALG in P-CSCF for explicit congestion control support | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.3.1 General | An IMS-ALG may support ECN according to RFC 6679 [188].
Subject to local policy, an IMS-ALG shall prohibit the negotiation of ECN during SDP offer/answer exchanges associated with multimedia priority service by removing any ECN attribute "a=ecn-capable-rtp" from the SDP offer and shall not invoke ECN for SIP transactio... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.3.2 Incoming SDP offer with ECN | If the IMS-ALG receives an SDP offer containing the "a=ecn-capable-rtp" attribute as specified in RFC 6679 [188] and:
- the IMS-ALG knows via configuration that the IMS-AGW supports transparently forwarding of ECN bits according to RFC 3168 [189];
- the IMS-ALG knows via configuration that the (IMS) network handles ECN... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.3.3 Incoming SDP offer without ECN | If the IMS-ALG receives a SDP offer without the "a=ecn-capable-rtp" attribute and all of the following conditions apply:
- the IMS-ALG knows via configuration that the IMS-AGW supports acting as ECN endpoint; and
- the IMS-ALG knows via configuration that the succeeding network supports ECN,
then the IMS-ALG may includ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.4 IMS-ALG in P-CSCF for Optimal Media Routeing (OMR) | Based on operator policy, the P-CSCF shall remove OMR related SDP attributes before it sends an SDP offer or answer towards an UE, as specified in subclause 2.1.9 of 3GPP TS 29.079 [11D]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.5 IMS-ALG in P-CSCF for NA(P)T and NA(P)T-PT controlled by the P-CSCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.5.1 General | This subclause describes the P-CSCF procedures for supporting the scenario where IP address and/or port conversions occur at the IMS-AGW level in the media path between the UE and the backbone. Two types of address conversions are covered:
- IP version interworking (NA(P)T-PT); and
- IP address/port translation (NA(P)T... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.6 IMS-ALG in P-CSCF for support of hosted NAT | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.6.1 General | When the P-CSCF performs procedures for hosted NAT, it shall modify the IP address(es) and port numbers, based on the IP address(es) and number(s) received from the IMS-AGW, as described in subclause 6.7.2.1. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.6.2 Hosted NAT traversal for TCP based streams | When the P-CSCF acts as an IMS-ALG, it acts as a B2BUA and modifies the SDP as described as described in 3GPP TS 23.334 [7F]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.7 IMS-ALG in P-CSCF for support of ICE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.7.1 General | This subclause describes procedures of a P-CSCF to support ICE, as defined in RFC 8445 [289] and RFC 8839 [290].
NOTE 1: If no IMS-AGW is inserted on the media plane, a P-CSCF might transparently pass ICE related SDP attibutes, in order to support ICE between the UE and remote entities. The remaining procedures in this... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.7.2 P-CSCF full ICE procedures for UDP based streams | 6.7.2.7.2.1 General
This subclause describes the P-CSCF full ICE procedures for UDP based streams.
6.7.2.7.2.2 P-CSCF receiving SDP offer
When the P-CSCF receives an SDP offer including ICE candidate information, the P-CSCF shall send the candidate information for each UDP based stream received in the SDP offer towards... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.7.3 P-CSCF ICE lite procedures for UDP based streams | When the P-CSCF is using ICE lite procedures for UDP based streams, the P-CSCF procedures are identical as described in subclause 6.7.2.7.2, with the following exceptions:
- The P-CSCF always acts as an ICE controlled entity towards the offerer and towards the answerer; and
- The P-CSCF requests the IMS-ALG to perform ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.7.4 ICE procedures for TCP based streams | 6.7.2.7.4.1 General
The P-CSCF shall disable ICE procedures for TCP based streams, i.e. streams where TCP is indicated as transport protocol in the m-line. Instead the P-CSCF will use the mechanism defined in RFC 4145 [83] for establishing TCP based streams, as defined in RFC 6544 [131].
NOTE 1: Handling of TCP candida... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.2.8 IMS-ALG in P-CSCF for transcoding | An IMS-ALG may support procedures to modify SDP for transcoding purposes. The IMS-ALG shall only apply those transcoding procedures if an attached IMS-AGW supports transcoding.
Upon receipt of an SDP offer, based on local policy and SDP signalling inspection, the IMS-ALG may decide to offer transcoding.
To offer transc... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.3 IMS-ALG in ISC gateway function | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.3.1 General | When the ISC gateway function acts as an IMS-ALG, it makes procedures as for an originating UA and terminating UA. The IMS-ALG acts as a B2BUA. For the use of the IMS-ALG for specific capabilities, additional procedures are defined in subsequent subclauses.
NOTE: The internal function of the IBCF as an IMS-ALG is defin... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 6.7.3.2 IMS-ALG in application gateway function for support of ICE | The application gateway function shall act according to the procedures defined for the IBCF in subclause 6.7.1.2. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7 Extensions within the present document | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.1 SIP methods defined within the present document | There are no SIP methods defined within the present document over and above those defined in the referenced IETF specifications. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2 SIP header fields defined within the present document | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.0 General | This subclause defines additional header fields. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.1 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.2 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.3 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.4 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.5 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.6 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.7 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.8 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.9 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.10 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.11 Definition of Restoration-Info header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.11.1 Introduction | IANA registry: Header Fields registry for the Session Initiation Protocol (SIP)
Header field name: Restoration-Info
Usage: The Restoration-Info header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
In case of a n... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.11.2 Applicability statement for the Restoration-Info header field | The Restoration-Info header field is applicable within a single private administrative domain or between different administrative domains.
The Restoration-Info header field is applicable when:
1) a node has failed and the SIP node detecting this failure needs to inform a proxy in the administrative domain of the termin... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.11.3 Usage of the Restoration-Info header field | A SIP entity that does not receive a response from the next SIP node, may include a Restoration-Info header field in the error response to inform upstream nodes or networks about the downstream node failure. The upstream nodes or networks may use this information to either inform the originating user, to report the fai... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.11.4 Procedures at the UA | There are no specific procedures specified for a UA. A UAC in a B2BUA may use the information in the Restoration-Info header field for error reporting, or take this information into account when deciding on re-attempting the request. A UAS may include a Retoration-Info header field in an error respons to inform upstrea... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.11.5 Procedures at the proxy | A SIP proxy that supports this extension and receives a request may insert a Restoration-Info header field prior to forwarding the request. The header field is populated with the IMSI value received in the body of a DIAMETER request as per 3GPP TS 29.228 [14] within the quoted string .
A SIP proxy that supports this ex... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.11.6 Security considerations | The Restoration-Info header field can contain sensitive information. When the Restoration-Info header field contains the IMSI value, it shall be sent only to trusted entities.
A UE is not expected to receive this information. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.11.7 Syntax | The syntax for Restoration-Info header field is specified in table 7.2.11-1.
Table 7.2.11-1: Syntax of Restoration-Info
Restoration-Info = "Restoration-Info" HCOLON pcrf-token / reason / generic-param
pcrf-token = ("IMSI" / ext-type) EQUAL pcrf-param
pcrf-param = quoted-string
reason = "noresponse"
ext-type = token |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.11.8 Examples of usage | The Restoration-Info header field can be inserted by the neighbouring upstream SIP node to the SIP node that does not respond. The header field value "noresponse" can be used to inform the upstream SIP entity about the failure. The upstream SIP entity such as a 3GPP S-CSCF can use this information to initiate restorati... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.12 Relayed-Charge header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.12.1 Introduction | IANA registry: Header Fields registry for the Session Initiation Protocol (SIP)
Header field name: Relayed-Charge
Usage: The Relayed-Charge header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
The P-Charging-Vec... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.12.2 Applicability statement for the Relayed-Charge header field | The Relayed-Charge header field is applicable within a single private administrative domain or between different administrative domains where there is a trust relationship between the domains.
The Relayed-Charge header field is not included in a SIP message sent to another network if there is no trust relationship.
The... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.12.3 Usage of the Relayed-Charge header field | A SIP entity that receives a P-Charging-Vector header field may take appropriate fields from the received header field and encode them in the equivalent field within the Relayed-Charge header field, along with a value in the relay-source to indicate the relaying SIP entity.
A SIP UA or SIP proxy that receives a SIP req... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.12.4 Procedures at the UA | This document does not specify any procedure at a UA located outside the administrative domain of a private network (e.g., PSTN gateway or conference mixer), with regard to the Relayed-Charge header field. UAs need not understand this header field.
However, it might be possible that a UA be located within the administr... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.12.5 Procedures at the proxy | A SIP proxy that supports this extension and receives a request or response without the Relayed-Charge header field MAY insert a Relayed-Charge header field prior to forwarding the message. The header is populated with one or more parameters, as described in the syntax, including but not limited to, a globally unique c... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.12.6 Security considerations | It is expected as normal behavior that proxies within a closed network will modify the values of the Relayed-Charge header field and insert it into a SIP request or response. However, these proxies that share this information shall have a trust relationship.
If an untrusted entity were inserted between trusted entities... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.12.7 Syntax | The syntax for Relayed-Charge header field is specified in table 7.2.12.1
Table 7.2.12.1: Syntax of Relayed-Charge
relayed-charge = "Relayed-Charge" HCOLON relayed-charge-list
relayed-charge-list = relayed-charge-item *(COMMA relayed-charge-item)
relayed-charge-item = relay-source HCOLON charge-params *(SEMI charge-par... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.12.8 Examples of usage | The Relayed-Charge header field is used in situations where there is a need to carry charging information applicable to a dialog or transaction which is not directly pertinent to the next hop. So for example, at the S-CSCF the accumulation of the "transit-ioi" header field parameter for an incoming call is removed and ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13 Resource-Share header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.1 Introduction | IANA registry: Header Fields registry for the Session Initiation Protocol (SIP)
Header field name: Resource-Share
Usage: The Resource-Share header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
The P-CSCF in the ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.2 Applicability statement for the Resource-Share header field | The Resource-Share header field is applicable within a single private administrative domain or between different administrative domains. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.3 Usage of the Resource-Share header field | The P-CSCF can include the Resource-Share header field in the REGISTER request to indicate the support of receiving resource sharing information from application servers in the user's home network or in an subsequent request or response within an existing dialog created by an INVITE request to indicate that resource sh... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.