hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.2.3.1 Originating procedures
| Upon receipt of a "SIP INVITE request for originating participating MCPTT function" for a private call or first-to-answer call with an SDP offer not including a media-level section for media plane control messages, the participating MCPTT function shall consider it as a request for a private call without floor control ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.2.3.2 Terminating procedures
| Upon receipt of a "SIP INVITE request for terminating participating MCPTT function" for the private call or first-to-answer call with SDP offer not including media-level section for media-floor control entity, the participating MCPTT shall consider it as the request for the private call without floor control or first-t... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.2.4 Controlling MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.2.4.1 Originating procedures
| The controlling MCPTT function shall follow the procedures as specified in clause 11.1.1.4.1.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.2.4.2 Terminating procedures
| Upon receiving of a "SIP INVITE request for controlling MCPTT function of a private call" or a "SIP INVITE request for controlling MCPTT function of a first-to-answer call", with SDP offer not including media-level section for media-floor control entity, the controlling MCPTT function shall consider it as the request f... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3 Ending the private call initiated by MCPTT client
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.1 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.1.1 On-demand private call
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.1.1.1 Client originating procedures
| Upon receiving a request from an MCPTT user to release an MCPTT private call session established using on-demand session signalling, the MCPTT client shall follow the procedures as specified in clause 6.2.5.1.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.1.1.2 Client terminating procedures
| Upon receiving a SIP BYE request for private call session, the MCPTT client shall follow the procedures as specified in clause 6.2.6.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.1.2 Private call using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.1.2.1 Client originating procedures
| Upon receiving a request from an MCPTT user to release an MCPTT private call within a pre-established session, the MCPTT client shall follow the procedures as specified in clause 6.2.5.2.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.1.2.2 Client terminating procedures
| The MCPTT client shall follow the procedures for terminating of request for MCPTT private call release as specified in clause 6.2.6.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.2 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.2.1 Originating procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.2.1.1 Receipt of SIP BYE request for on-demand private call
| Upon receiving from the MCPTT client a SIP BYE request the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.6.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.2.1.2 Receipt of REFER "BYE" request for private call using pre-established session
| Upon receiving from the MCPTT client a SIP REFER request when using a pre-established session with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.7.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.2.2 Terminating procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.2.2.1 Receipt of SIP BYE request for private call on-demand
| Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.1.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.2.2.2 Receipt of SIP BYE request when ongoing pre-established session
| Upon receiving a SIP BYE request from the controlling MCPTT function and if the MCPTT session id refers to an MCPTT user that has a pre-established session with the participating MCPTT function, the participating MCPTT function:
1) shall interact with the media plane as specified in clause 9.3 in 3GPP TS 24.380 [5] fo... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.3 Controlling MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.3.3.1 Terminating procedures
| Upon receiving a SIP BYE request the controlling MCPTT function shall follow the procedures as specified in clause 6.3.3.2.4.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.4 Ending the private call initiated by the MCPTT server
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.4.1 General
| This clause describes the procedures of each functional entity for ending the private call initiated by the MCPTT server.
NOTE: For private call without floor control, ending the private call is initiated only by the MCPTT client.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.4.2 MCPTT client procedures
| Upon receiving a SIP BYE request for private call session, the MCPTT client shall follow the procedures as specified in clause 6.2.6.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.4.3 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.4.3.1 Originating procedures
| When the MCPTT session for private call needs to be released as specified in clause 6.3.8.2, the participating MCPTT function shall follow the procedures in clause 6.3.3.1.5.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.4.3.2 Terminating procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.4.3.2.1 Receipt of SIP BYE request for private call on-demand
| Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.1.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.4.3.2.2 Receipt of SIP BYE request when ongoing pre-established session
| Upon receiving a SIP BYE request from the controlling MCPTT function and if the MCPTT session id refers to an MCPTT user that has a pre-established session with the participating MCPTT function, the participating MCPTT function shall follow the procedures in clause 11.1.3.2.2.2.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.4.4 Controlling MCPTT function procedures
| When the MCPTT session for private call needs to be released as specified in clause 6.3.8.2, the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.5.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5 Private call call-back
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5.1 General
| Clause 11.1.5 describes the MCPTT client procedures, the participating MCPTT function procedures and the controlling MCPTT function procedures for private call call-back.
In the procedures in clause 11.1.5.2:
- the term "requesting MCPTT client" is used to refer to the client that initiates a private call call-back r... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5.2 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5.2.1 Requesting client procedures for call-back requests
| Upon receiving a request from the MCPTT user to send a private call call-back request, if the <allow-request-private-call-call-back> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a value of "false", the MCPTT ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5.2.2 Target client procedures for handling call-back requests
| Upon receiving a "SIP MESSAGE request for private call call-back request for terminating client", the MCPTT client:
1) shall store a "PCCB target client entry" entry with:
a) the MCPTT ID set to the MCPTT ID contained in the <mcptt-calling-user-id> element in the application/vnd.3gpp.mcptt-info+xml MIME body;
b) the... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5.2.3 Private call call-back fulfilment
| When the target MCPTT user wants to make a private call call-back, the target MCPTT client shall initiate a private call in manual commencement mode towards the requesting MCPTT client using the MCPTT ID of the requesting MCPTT user as found in the "PCCB target client entry" stored on the UE, by following the procedure... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5.3 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5.3.1 Originating procedures
| Upon receiving a "SIP MESSAGE request for private call call-back for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) respo... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5.3.2 Terminating procedures
| Upon receiving a "SIP MESSAGE request for private call call-back for terminating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) respo... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.5.4 Controlling MCPTT function procedures
| Upon receiving a:
- "SIP MESSAGE request for private call call-back request for controlling MCPTT function";
- "SIP MESSAGE request for private call call-back cancel request for controlling MCPTT function"; or
- "SIP MESSAGE request for private call call-back responses for controlling MCPTT function";
the controlli... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6 Ambient listening call
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.1 General
| Clause 11.1.6 specifies the MCPTT client procedures, participating MCPTT function procedures and controlling MCPTT function procedures for on-network ambient listening calls. The procedures as specified are applicable to both locally initiated and remotely initiated ambient listening call.
The procedures for originati... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2 MCPTT client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.0 Ambient listening handling at the MCPTT client
| The MCPTT client takes the actions needed to avoid letting the user detect that an ambient listening call is active. This includes:
- avoiding that the user is aware of the beginning of an ambient listening call, except an ambient listening call initiated by the user;
- avoiding that the user is aware of the end of a... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.1 On-demand ambient listening call
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.1.1 Client originating procedures
| Upon receiving a request from the MCPTT user to originate a remote initiated ambient listening call, if the <allow-request-remote-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a va... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.1.2 Client terminating procedures
| Upon receipt of an initial SIP INVITE request, the MCPTT client shall follow the procedures for termination of multimedia sessions in the IM CN subsystem as specified in 3GPP TS 24.229 [4] with the clarifications below.
The MCPTT client:
1) may reject the SIP INVITE request if either of the conditions in step a) or b... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.1.3 Client release origination procedure
| Upon receiving a request from an MCPTT user to release an MCPTT ambient listening call:
The MCPTT client:
1) if the MCPTT client has not received a g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header field according to IETF RFC 6809 [93] in:
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.1.4 Client session release termination procedure
| This clause is referenced from other procedures.
Upon receipt of a SIP BYE request in the dialog of an ambient listening session, the MCPTT client:
1) shall comply with the procedures of clause 6.2.6;
2) if the cached ambient listening client role is equal to "listened-to MCPTT user", shall provide no indication tha... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.2 Ambient listening call using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.2.1 Client originating procedures
| Upon receiving a request from the MCPTT user to originate a remote initiated ambient listening call, if the <allow-request-remote-initiated-ambient-listening> element of the <ruleset> element is not present in the MCPTT user profile document (see the MCPTT user profile document in 3GPP TS 24.484 [50]) or is set to a va... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.2.2 Client terminating procedures
| The MCPTT client shall follow the procedures for termination of multimedia sessions for ambient listening calls as specified in clause 11.1.6.2.1.2.
NOTE: The terminating MCPTT client in an ambient listening call receives a SIP INVITE request with Replaces header field when using a pre-established session.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.2.3 Client release origination procedure
| Upon receiving a request from an MCPTT user to release an MCPTT ambient listening call when using a pre-established MCPTT session:
The MCPTT client:
1) if the MCPTT client has not received a g.3gpp.mcptt.ambient-listening-call-release feature-capability indicator as described in clause D.3 in the Feature-Caps header ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.2.4 Reception of SIP INFO request with release-reason
| Upon receiving a SIP INFO request containing an application/vnd.3gpp.mcptt-info+xml MIME body containing a <release-reason> element, the MCPTT client:
1) if the cached ambient listening client role is equal to "listened-to MCPTT user", shall provide no indication that an ambient listening call is being terminated;
2)... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.2.2.5 Client session release termination procedure
| This clause is referenced from other procedures.
Upon receiving an interaction with the media plane indicating release of the ambient listening call but preservation of the pre-established session as specified in clause 9.2 of 3GPP TS 24.380 [5], the MCPTT client:
1) if the cached ambient listening client role is equ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3.1 Originating procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3.1.1 On-demand ambient listening call
| Upon receipt of a "SIP INVITE request for originating participating MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "ambient-listening", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a ri... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3.1.2 Receipt of SIP BYE request for on-demand ambient listening call
| Upon receiving from the MCPTT client a SIP BYE request the participating MCPTT function:
1) shall follow the procedures as specified in clause 11.1.3.2.1.1.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3.1.3 Receipt of REFER "BYE" request for private call using pre-established session
| Upon receiving from the MCPTT client a SIP REFER request when using a pre-established session with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.7.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3.1.4 Ambient listening call initiation using pre-established session
| Upon receipt of a "SIP REFER request for a pre-established session", with:
1) the Refer-To header field containing a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that points to an application/resource-lists+xml MIME body as specified in IETF RFC 5366 [20] containing one <entry> ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3.2 Terminating procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3.2.1 Terminating procedures for ambient listening call
| Upon receipt of a "SIP INVITE request for terminating participating MCPTT function", the participating MCPTT function:
NOTE: The procedures in the present clause are applicable for both on-demand and pre-established sessions.
1) if unable to process the request due to a lack of resources or a risk of congestion exist... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3.2.2 Receipt of SIP BYE request for on-demand ambient listening call
| Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 11.1.3.2.2.1.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.3.2.3 Receipt of SIP BYE request for an ongoing pre-established session
| Upon receiving a SIP BYE request from the controlling MCPTT function for an ambient listening call and if the MCPTT session id refers to an MCPTT user that has a pre-established session with the participating MCPTT function, the participating MCPTT function:
1) if the SIP BYE request contains an application/vnd.3gpp.m... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.4 Controlling MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.4.1 Originating procedures
| This clause describes the procedures for inviting an MCPTT user to an MCPTT ambient listening session. The procedure is initiated by the controlling MCPTT function as the result of an action in clause 11.1.6.4.2
The controlling MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2;
... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.4.2 Terminating procedures
| Upon receiving of a "SIP INVITE request for controlling MCPTT function of an ambient listening call" the controlling MCPTT function:
1) shall check whether the public service identity contained in the Request-URI is allocated for ambient listening call and perform the actions specified in clause 6.3.7.1 if it is not a... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.4.3 Server initiated ambient call release
| The ambient listening call release is triggered by an MCPTT administrator by a mechanism outside of the scope of the standard, or directly by the controlling MCPTT function as a result of an event as specified in clause 10.14.3.3 of 3GPP TS 23.379 [3].
This clause is referenced from other procedures.
Upon receipt of ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.6.4.4 Reception of a SIP BYE request
| Upon receipt of a SIP BYE request for an ambient listening session the controlling MCPTT function:
1) shall interact with the media plane as specified in clause 6.3 in 3GPP TS 24.380 [5] for releasing the media plane resource associated with the SIP session towards the MCPTT client;
2) shall generate a SIP BYE reques... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.7 Remotely initiated private call
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.7.1 General
| Clause 11.1.7 describes the MCPTT client procedures, the participating MCPTT function procedures and the controlling MCPTT function procedures for the on-network remotely initiated private call functionality.
In the procedures of clause 11.1.7.2, clause 11.1.7.3, and clause 11.1.7.4:
- the term "requesting MCPTT user... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.7.2 Client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.7.2.1 Remotely initiated private call initiation request procedures
| Upon receiving a request from the requesting MCPTT user to send a remotely initiated private call request to the remote MCPTT user to originate a private call to an identified MCPTT user, the MCPTT client:
1) if:
a) the <allow-request-remote-init-private-call> element of the <ruleset> element is not present in the re... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.7.2.2 Remote client procedures for handling remotely initiated private call request
| Upon receiving a "SIP MESSAGE request for remotely initiated private call request for terminating client", the MCPTT client:
1) if the <notify-remote-user> element contained in the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request is set to a value of "true", may indicate to t... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.7.3 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.7.3.1 Originating procedures
| Upon receiving a "SIP MESSAGE request for remotely initiated private call for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Err... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.7.3.2 Terminating procedures
| Upon receiving a "SIP MESSAGE request for remotely initiated private call for terminating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Err... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.7.4 Controlling MCPTT function procedures
| Upon receiving a:
- "SIP MESSAGE request for remotely initiated private call request for controlling MCPTT function"; or
- "SIP MESSAGE request for remotely initiated private call response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8 Private call transfer
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8.1 General
| In the procedures of clause 11.1.8:
- the term "requesting MCPTT user" is used to refer to the MCPTT user who sent a request to initiate a private call transfer;
- the term "transferred MCPTT user" is used to refer to the MCPTT user who is being transferred to the new target MCPPT user; and
- the term "target MCPTT ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8.2 Client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8.2.1 Private call transfer request procedures
| Upon receiving a request from an MCPTT user to transfer an ongoing MCPTT private call to a target MCPTT user, the MCPTT client:
1) if:
a) the <allow-call-transfer> element of the <ruleset> element is not present in the requesting MCPTT user's MCPTT user profile document (see the MCPTT user profile document in 3GPP TS... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8.2.2 Client procedures for handling incoming private call transfer request
| Upon receiving a "SIP MESSAGE request for transfer private call request for terminating client", the MCPTT client:
1) should indicate to the transferred MCPTT user that a request to transfer the previously ongoing call to a new target MCPTT user has been received;
2) shall extract the MCPTT ID of the target MCPTT use... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8.2.3 Announced private call transfer
| This clause describes the procedures for transferring an MCPTT private call for both cases if a call to the target MCPTT user is already established or not.
When the MCPTT user requests an announced private call transfer of an ongoing private MCPTT call, the MCPTT client:
1) shall put the ongoing MCPTT private call w... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8.3 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8.3.1 Originating procedures
| Upon receiving a "SIP MESSAGE request for transfer private call for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) respon... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8.3.2 Terminating procedures
| Upon receiving a
- "SIP MESSAGE request for transfer private call request for terminating participating MCPTT function"; or
- "SIP MESSAGE request for transfer private call response for terminating participating MCPTT function";
the participating MCPTT function:
1) if unable to process the request due to a lack of... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.8.4 Controlling MCPTT function procedures
| Upon receiving a:
- "SIP MESSAGE request for transfer private call request for controlling MCPTT function"; or
- "SIP MESSAGE request for transfer private call response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of conges... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.9 Private call forwarding
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.9.1 General
| In the procedures of clause 11.1.9:
- the term "forwarded-calling-client" is used to refer to the originating MCPTT client who has made a private call attempt that is being forwarded;
- the term "forwarded-by-client" is used to refer to the MCPTT client to whom a private call has been placed and who has requested th... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.9.2 Client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.9.2.1 Private call forwarding request based on manual user input procedure
| The following procedure covers the case when an MCPTT user decides to forward an incoming MCPTT private call to a new target MCPTT ID or functional alias based on manual user input instead of accepting the incoming MCPTT private call. If the MCPTT user decides to forward an incoming MCPTT private call to a new target M... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.9.2.2 Client procedures for handling incoming private call forwarding request
| Upon receiving a "SIP MESSAGE request for forwarding private call request for terminating client", the MCPTT client:
1) should indicate to the forwarded MCPTT user that a request to forward the previously initiated call to a new target MCPTT user has been received;
2) shall extract the MCPTT ID of the target MCPTT us... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.9.3 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.9.3.1 Originating procedures
| Upon receiving a "SIP MESSAGE request for forwarding private call for originating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) resp... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.9.3.2 Terminating procedures
| Upon receiving a
- "SIP MESSAGE request for forwarding private call request for terminating participating MCPTT function"; or
- "SIP MESSAGE request for forwarding private call response for terminating participating MCPTT function";
the participating MCPTT function:
1) if unable to process the request due to a lac... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.1.9.4 Controlling MCPTT function procedures
| Upon receiving a:
- "SIP MESSAGE request for forwarding private call request for controlling MCPTT function"; or
- "SIP MESSAGE request for forwarding private call response for controlling MCPTT function";
the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of co... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 11.2 Off-network private call
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.