hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.28 Rich Call Data | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.28.1 RCD info retrieval | The AS may support RCD and receive RCD server address, RCD information or RCD URL from the HSS via the Nhss_ImsSubscriberDataManagement (ImsSDM) service, as described in 3GPP TS 29.562 [274].
If the AS received the RCD URL from the HSS, the AS may, based on configuration, retrieve the RCD information from the RCD serve... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.28.2 Originating procedures | If the AS received an initial INVITE request or MESSAGE request, the RCD info as defined in draft-ietf-sipcore-callinfo-rcd [303] is not included in the received request, support of the RCD is required by the local policy and the AS retrieved the RCD info as described in subclause 5.7.1.28.1, the AS may insert in the i... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.1.28.3 Terminating procedures | If the AS supports RCD verification using assertion of RCD info as specified in subclause 3.1, required by the local policy, the AS received an initial INVITE request or MESSAGE request containing the Call-Info header field with RCD info and one or more Identity header fields, the AS may perform signature verification ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.2 Application Server (AS) acting as terminating UA, or redirect server | When acting as a terminating UA the AS shall behave as defined for a UE in subclause 5.1.4, with the exceptions identified in this subclause.
The AS, although acting as a UA, does not initiate any registration of its associated addresses. These are assumed to be known by peer-to-peer arrangements within the IM CN subsy... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.3 Application Server (AS) acting as originating UA | In order to support an AS acting as an originating UA, the AS has to be within the same trust domain as the S-CSCF to which requests will be sent.
When acting as an originating UA the AS shall behave as defined for a UE in subclause 5.1.3, with the exceptions identified in this subclause.
The AS, although acting as a U... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.4 Application Server (AS) acting as a SIP proxy | When the AS acting as a SIP proxy receives a request from the S-CSCF, prior to forwarding the request, the AS shall:
- remove its own URI from the topmost Route header field;
- if the request contains a "logme" header field parameter in the SIP Session-ID header field then log the request if required by local policy; a... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.5 Application Server (AS) performing 3rd party call control | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.5.1 General | The AS performing 3rd party call control acts as a B2BUA. There are two kinds of 3rd party call control:
- Routeing B2BUA: an AS receives a request, terminates it and generates a new request, which is based on the received request.
- Initiating B2BUA: an AS initiates two requests, which are logically connected together... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.5.2 Call initiation | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.5.2.1 Initial INVITE | When the AS acting as a Routeing B2BUA receives an initial INVITE request, the AS shall:
1) remove its own SIP URI from the topmost Route header field of the received INVITE request;
2) perform the AS specific functions. See 3GPP TS 23.218 [5];
3) if successful, generate and send a new INVITE request to establish a new... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.5.2.2 Subsequent requests | If the policy or service logic requires the AS to check whether the session is still alive, the AS shall send UPDATE requests periodically to the served UE. The UPDATE requests shall not contain SDP offer.
NOTE: The exact timing of sending the UPDATE requests is out of scope of this specification. Sending UPDATE reques... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.5.3 Call release | An AS may initiate a call release. See 3GPP TS 23.218 [5] for possible reasons. The AS shall simultaneously send the BYE request for both dialogs managed by the B2BUA. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.5.4 Call-related requests | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.5.5 Further initial requests | When the AS is acting as an Initiating B2BUA the AS shall apply the procedures described in subclause 5.7.3 for the requests. The AS shall either set the "icid-value" header field parameter in the P-Charging-Vector header field to be the same as received or different. The AS may initiate any number of requests, per ser... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.5.6 Transcoding services invocation using third-party call control | An AS may invoke transcoding at an MRFC by the use of RFC 4117 [166], if the MRFC supports acting as the transcoding server described in RFC 4117 [166].
During the call setup, an AS may decide proactively to invoke transcoding when receiving an INVITE request, or reactively when the callee rejects the call setup using ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.7.6 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8 Procedures at the MRFC | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.1 General | Although the MRFC is acting as a UA, it is outside the scope of this specification how the MRFC associated addresses are made known to other entities.
For all SIP transactions identified:
- if priority is supported, as containing an authorised Resource-Priority header field, or, if such an option is supported, relating... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.2 Call initiation | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.2.1 Initial INVITE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.2.1.1 MRFC-terminating case | 5.8.2.1.1.1 Introduction
The MRFC shall provide a P-Asserted-Identity header field in a response to the initial request for a dialog, or any response for a standalone transaction. It is a matter of network policy whether the MRFC expresses privacy according to RFC 3323 [33] with such responses.
When the MRFC receives a... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.2.1.2 MRFC-originating case | The MRFC shall provide a P-Asserted-Identity header field in an initial request for a dialog, or any request for a standalone transaction. It is a matter of network policy whether the MRFC expresses privacy according to RFC 3323 [33] with such requests.
When an MRFC generates an initial request for a dialog or a reques... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.2.2 Subsequent requests | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.2.2.1 Tones and announcements | When the MRFC receives an ACK request for a session, this may be considered as an event to direct the MRFP to start the playing of a tone or announcement. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.2.2.2 Transcoding | When the MRFC receives a PRACK request (in response to the 183 (Session Progress) response with an indicator for transcoding and codec supplied in SDP, the MRFC shall:
- after the MRFP indicates that the transcoding request is granted, send 200 (OK) response. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.3 Call release | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.3.1 S-CSCF-initiated call release | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.3.1.1 Tones and announcements | When the MRFC receives a BYE request for a session, the MRFC directs the MRFP to stop the playing of a tone or announcement. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.3.2 MRFC-initiated call release | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.3.2.1 Tones and announcements | When the MRFC has a timed session to play tones and announcements and the time expires, the MRFC shall:
- send a BYE request towards the UE.
When the MRFC is informed by the MRFP that tone or announcement resource has been released, the MRFC shall:
- send a BYE request towards the UE. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4 Call-related requests | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4.1 ReINVITE | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4.1.1 MRFC-terminating case | 5.8.4.1.1.1 Ad-hoc conferences
The MRFC can receive reINVITE requests to modify an ad-hoc conferencing session (for example a multiparty call) for purposes of floor control and for parties to leave and rejoin the conference.
When the MRFC receives a reINVITE request, the MRFC shall:
- send 100 (Trying) response; and
- ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4.1.2 MRFC-originating case | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4.2 REFER | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4.2.1 MRFC-terminating case | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4.2.2 MRFC-originating case | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4.2.3 REFER initiating a new session | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4.2.4 REFER replacing an existing session | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.4.3 INFO | Void. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.8.5 Further initial requests | When the MRFC responds to an OPTIONS request with a 200 (OK) response, the MRFC may include a message body with an indication of the supported tones/announcement packages, DTMF capabilities, supported codecs and conferencing options of the MRFC/MRFP.
NOTE: As specified in RFC 6230 [146] an MRFC supporting the use of th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.9 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.9.1 Void | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10 Procedures at the IBCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.1 General | As specified in 3GPP TS 23.228 [7] border control functions may be applied between two IM CN subsystems or between an IM CN subsystem and other SIP-based multimedia networks based on operator preference. The IBCF may act both as an entry point and as an exit point for a network. If it processes a SIP request received f... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.2 IBCF as an exit point | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.2.1 Registration | When IBCF receives a REGISTER request, the IBCF shall:
1) void;
2) if network topology hiding is required or IBCF is configured to perform application level gateway and/or transport plane control functionalities, then the IBCF shall add its own routeable SIP URI to the top of the Path header field; and
NOTE 1: The IBCF... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.2.2 Initial requests | Upon receipt of:
- an initial request for a dialog;
- a request for a standalone transaction, except the REGISTER method; or
- a request for an unknown method that does not relate to an existing dialog;
the IBCF shall:
1) if the request is an INVITE request, respond with a 100 (Trying) provisional response;
1A) remove ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.2.3 Subsequent requests | Upon receipt of a subsequent request, the IBCF shall:
1) if the request is an INVITE request, respond with a 100 (Trying) provisional response;
1A) if the request is a NOTIFY request with the Subscription-State header field set to "terminated" and the IBCF has retained the SIP dialog state information for the associate... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.2.4 IBCF-initiated call release | If the IBCF provides transport plane control functionality and receives an indication of a transport plane related error the IBCF 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 side based on the information sav... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.3 IBCF as an entry point | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.3.1 Registration | When IBCF receives a REGISTER request, the IBCF shall:
1) verify if it arrived from a trusted domain or not. If the request arrived from an untrusted domain, respond with 403 (Forbidden) response;
NOTE 1: The IBCF can find out whether the request arrived from a trusted domain or not, from the procedures described in 3G... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.3.2 Initial requests | Upon receipt of:
- an initial request for a dialog;
- a request for a standalone transaction except the REGISTER request; or
- a request for an unknown method that does not relate to an existing dialog;
the IBCF shall verify whether the request is arrived from a trusted domain or not. If the request arrived from an unt... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.3.3 Subsequent requests | Upon receipt of a subsequent request, the IBCF shall:
1) if the request is an INVITE request, then respond with a 100 (Trying) provisional response;
1A) if the request is a NOTIFY request with the Subscription-State header field set to "terminated" and the IBCF has retained the SIP dialog state information for the asso... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.3.4 IBCF-initiated call release | If the IBCF provides transport plane control functionality and receives an indication of a transport plane related error the IBCF 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 side based on the information sav... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.3.5 Abnormal cases | When the IBCF acting as an entry point in the originating home network is unable to forward a SIP request, as determined by one of the following:
NOTE 1: If IBCF supports indicating traffic leg associated with a URI as specified in RFC 7549 [225], the IBCF can determine that IBCF is acting as an entry point in the orig... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.4 THIG functionality in the IBCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.4.1 General | NOTE 1: THIG functionality is performed in I-CSCF in Release-5 and Release-6 and is compatible with the procedures specified in this subclause.
The following procedures shall only be applied if network topology hiding is required by the network. The network requiring network topology hiding is called the hiding network... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.4.2 Encryption for network topology hiding | Upon receiving an outgoing request/response from the hiding network the IBCF shall perform the encryption for network topology hiding purposes, i.e. the IBCF shall:
0) if applying encryption procedure on the Service-Route header field, exclude from the Service-Route header field the entry corresponding to its own SIP U... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.4.3 Decryption for network topology hiding | Upon receiving and incoming requests/response to the hiding network the IBCF shall perform the decryption for network topology hiding purposes, i.e. the IBCF shall:
1) identify hostnames encrypted by the network this IBCF belongs to within all header fields of the incoming message;
2) use those hostnames that carry the... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.5 IMS-ALG functionality in the IBCF | The IBCF shall only apply the following procedures if application level gateway functionality is required by the network.
The IBCF acts as a B2BUA when it performs IMS-ALG functionality. As an IMS-ALG, the IBCF will internally map the message header fields between the two dialogs that it manages. It is responsible for ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.6 Screening of SIP signalling | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.6.1 General | The IBCF may act as a B2BUA when it performs screening of SIP signalling functionality. In this case the B2BUA behaviour of the IBCF shall comply with the description given in subclause 5.10.5 for the IMS-ALG functionality.
NOTE: Many header fields are intended for end-to-end operation; removal of such header fields wi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.6.2 IBCF procedures for SIP header fields | If specified by local policy rules, the IBCF may omit or modify any received SIP header fields prior to forwarding SIP messages, with the following exceptions.
As a result of any screening policy adopted, the IBCF should not modify at least the following header fields which would cause misoperation of the IM CN subsyst... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.6.3 IBCF procedures for SIP message bodies | If the IBCF acts as a B2BUA, and the IBCF receives a message with a body part for a UE from an S-CSCF, and:
- if the body part is the 3GPP IM CN subsystem XML body (as indicated by the Content-Type header field, see subclause 7.6) and the body part is not optional (as indicated by the (absence of the) Content-Dispositi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.7 Media transcoding control | The IBCF may perform the media transcoding control in order to allow establishing communication between IM CN subsystems using different media codecs based on the interworking agreement and session information. When performing media transcoding control the IBCF acts as a special case of an IMS-ALG compliant with the de... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.8 Privacy protection at the trust domain boundary | In order to ensure privacy IBCF shall additionally to what is specified in subclause 4.4 and before sending the SIP requests or SIP responses outside the trust domain boundary perform the privacy protection as specified in RFC 3323 [33] and RFC 7044 [66] applicable to header fields with the clarifications in this subcl... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.9 Roaming architecture for voice over IMS with local breakout | The IBCF shall apply OMR as specified in 3GPP TS 29.079 [11D] and in accordance with the roaming architecture for voice over IMS with local breakout when a session is identified as a roaming architecture for voice over IMS with local breakout session.
A session can be identified as a potential roaming architecture for ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.10 HTTP procedures over the Ms reference point | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.10.1 General | General procedures over the Ms reference point are specified in clause V.2. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.10.2 Procedures for an IBCF acting as an entry point | When receiving an initial INVITE, re-INVITE or MESSAGE request containing one or more SIP Identity header fields, the IBCF shall determine the information (originating identity, diverting identities, contents of the Resource-Priority, Priority and Call-Info header fields) to be verified by decoding the Identity header ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.10.10.3 Procedures for an IBCF acting as an exit point | When receiving an initial INVITE or MESSAGE request containing:
NOTE 1: As part of the border control procedures the IBCF can apply privacy procedures and in these cases this procedure is not needed.
1) a "verstat" tel URI parameter in at least one of the SIP From header field or the SIP P-Asserted-Identity header fiel... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11 Procedures at the E-CSCF | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.1 General | The PSAP may either be directly connected to the IM CN subsystem or via the PSTN. Based on regional/national requirements and network operator policy, the PSAP may be connected to the IM CN subsystem of another network.
The E-CSCF can receive URIs for a domain for which the operator running the E-CSCF is not responsibl... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.2 UE originating case | The E-CSCF may forward an emergency request to a PSAP in the IM CN subsystem, a PSAP attached to another network, or a PSAP in the PSTN. If the PSAP is attached to another network, the requrest can pass IBCF(s) before entering the other network. If the PSAP is located in the PSTN, the request will pass a BGCF and a MGC... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.3 Use of an LRF | Where the network operator determines that an LRF is to be used, the E-CSCF shall route initial requests for a dialog and standalone requests that contain an emergency service URN, i.e. a service URN with a top-level service type of "sos" as specified in RFC 5031 [69], or an emergency number, to the LRF in accordance w... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.4 Subscriptions to E-CSCF events | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.4.1 Subscription to the event providing dialog state | When an incoming SUBSCRIBE request addressed to the E-CSCF arrives containing the Event header field with the dialog event package, the E-CSCF shall:
1) based on the local policy, check if the request was generated by a subscriber who is authorised to subscribe to the dialog state of this particular user. The authorize... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.4.2 Notification about dialog state | The E-CSCF shall send a NOTIFY request when an event pertaining to the dialog or dialogs occurs, as specified in RFC 6665 [28].
When generating NOTIFY requests, the E-CSCF shall not preclude any valid dialog event package parameters in accordance with RFC 4235 [171]. Where RFC 4235 [171] expresses an option or only a r... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.4.3 Subscription to the presence event package | When an incoming SUBSCRIBE request addressed to the E-CSCF arrives containing the Event header field with the presence event package and a Target-Dialog header field:
1) based on the local policy, the E-CSCF shall check if the request was generated by a subscriber who is authorised to subscribe to the presence state of... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.4.4 Notification about presence | Upon reception of a PUBLISH request in the dialog of the related emergency call as described in subclause 5.11.5.3, the E-CSCF shall send a NOTIFY request for the presence event package as specified in RFC 6665 [28]. The E-CSCF:
1) if the PUBLISH request contains a body of the "application/pidf+xml" MIME type, shall in... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.5 Current location discovery during an emergency call | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.5.1 General | The UE can be requested to provide the current location information during an emergency call. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.5.2 Requesting current location informaton | If:
1) the UE indicated a Recv-Info header field with the g.3gpp.current-location-discovery info package name in the dialog of the emergency call;
2) the UE indicated an Accept header field indicating the "application/vnd.3gpp.current-location-discovery+xml" MIME type in the dialog of the emergency call; and
3) the dia... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.11.5.3 Receiving current location informaton | Upon receiving a PUBLISH request as described in RFC 3903 [70] as in-dialog request of the dialog of the emergency call, with Event header field containing the presence event package name, the E-CSCF shall perform the procedures described in subclause 5.11.4.4. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.12 Location Retrieval Function (LRF) | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.12.1 General | The LRF can receive URIs for a domain for which the operator running the LRF is not responsible. Where RFC 3261 [26] specifies a requirement that the SIP entity has to be responsible for the domain for particular functionality to occur, the LRF may ignore this restriction.
NOTE: The LRF would normally implement this ov... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.12.2 Treatment of incoming initial requests for a dialog and standalone requests | The LRF shall respond to all received initial requests for a dialog, and to all standalone requests, as a redirect server as defined in subclause 8.3 of RFC 3261 [26] with the following additions:
1) the LRF shall generate a 300 (Multiple Choices) response to all such requests;
2) the LRF shall set the Contact header f... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.12.3 Subscription and notification | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.12.3.1 Notification about dialog state | Based on operator policy, the LRF can either subscribe to all dialog information on an E-CSCF or individually subscribe to each dialog as it receives the requests.
NOTE 1: Subscription to dialog information is dependent on the use of Le interface as described in subclause 5.12.2.
In the case that the LRF is subscribing... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.12.3.2 Notification about UE location | Based on operator policy, the LRF can subscribe to UE location as it receives the requests.
Upon generation of a 300 response to an incoming dialog forming request that contains a reference identifier, the LRF shall generate a SUBSCRIBE request to the presence event package in accordance with RFC 6665 [28] and RFC 3856... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13 ISC gateway function | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.1 General | As specified in 3GPP TS 23.218 [5] border control functions may be applied between the IM CN subsystem and an application server based on operator preference. The ISC gateway function may act both as an entry point and as an exit point for a network. If it processes a SIP request received from another network it functi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.2 ISC gateway function as an exit point | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.2.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.2.2 General | This subclause applies for requests sent from the S-CSCF to the AS via the ISC gateway function.
For all SIP transactions identified:
- if priority is supported, as containing an authorised Resource-Priority header field or a temporarily authorised Resource-Priority header field, or, if such an option is supported, rel... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.2.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:
1) if the request is an INVITE request, respond with a 100 (Trying) provisional response;
2) remove the topmost e... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.2.4 Subsequent requests | Upon receipt of a subsequent request, the ISC gateway function shall:
1) if the request is an INVITE request, 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 stat... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 5.13.2.5 Call release initiated by 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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.