ETSI TS 126 113 V19.2.0 (2026-04)

LTE; 5G; Real-Time Media Communication; Protocols and APIs (3GPP TS 26.113 version 19.2.0 Release 19)

RTS/TSGS-0426113vj20

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 4 - Codec
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 02-Apr-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
LTE;
5G;
Real-Time Media Communication;
Protocols and APIs
(3GPP TS 26.113 version 19.2.0 Release 19)


3GPP TS 26.113 version 19.2.0 Release 19 1 ETSI TS 126 113 V19.2.0 (2026-04)

Reference
RTS/TSGS-0426113vj20
Keywords
5G,LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2026.
All rights reserved.
ETSI
3GPP TS 26.113 version 19.2.0 Release 19 2 ETSI TS 126 113 V19.2.0 (2026-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found at 3GPP to ETSI numbering cross-referencing.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 26.113 version 19.2.0 Release 19 3 ETSI TS 126 113 V19.2.0 (2026-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 7
1 Scope . 9
2 References . 9
3 Definitions of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 11
3.3 Abbreviations . 11
4 Procedures for real-time media communication . 12
4.1 General . 12
4.2 Procedures for media session handling . 12
4.2.1 Provisioning (RTC-1) procedures . 12
4.2.2 Network media session handling (RTC-3, RTC-5) procedures . 13
4.2.3 UE media session handling (RTC-6, RTC-11) procedures . 13
4.3 Procedures for media content and signalling transport . 14
4.3.1 Media transport (RTC-4m, RTC-12) procedures . 14
4.3.1.1 General . 14
4.3.1.2 Media transport procedures at RTC-4m and RTC-12 . 14
4.3.2 Signalling (RTC-4s) procedures . 14
4.3.3 Application interaction (RTC-7) procedures . 15
5 General aspects of APIs . 15
5.1 Usage of HTTP . 15
5.1.1 HTTP protocol version . 15
5.1.1.1 RTC AF . 15
5.1.2 HTTP message bodies for API resources . 15
5.1.3 Usage of HTTP headers . 15
5.1.3.1 General . 15
5.1.3.2 Media Session Handler identification . 15
5.1.3.3 RTC AF identification. 15
5.1.3.4 Support for conditional HTTP GET requests . 16
5.1.3.5 Support for conditional HTTP POST, PUT, PATCH and DELETE requests . 16
6 Provisioning interface (RTC-1) . 16
6.1 General . 16
6.2 Provisioning Sessions API . 16
6.3 Real-time Media Communication provisioning API . 17
6.4 Server Certificates Provisioning API . 17
6.5 Edge Resources Provisioning API . 17
6.6 Policy Templates Provisioning API . 17
6.7 Metrics Reporting Provisioning API . 17
6.8 Consumption Reporting Provisioning API . 17
7 Media hosting interface (RTC-2) . 18
8 RTC AS to RTC AF APIs (RTC-3) . 18
9 Media-centric transport interface (RTC-4, RTC-12) . 18
9.1 General . 18
9.2 Media transport (RTC-4m, RTC-12) . 18
9.3 Signalling exchange (RTC-4s) . 18
10 Media Session Handling interface (RTC-5, RTC-3) . 19
10.1 General . 19
ETSI
3GPP TS 26.113 version 19.2.0 Release 19 4 ETSI TS 126 113 V19.2.0 (2026-04)
10.2 Service Access Information API . 19
10.3 Dynamic Policy API . 19
10.3.1 Introduction. 19
10.3.2 Enabling PDU Set handling in dynamic policies . 20
10.3.3 Enabling dynamically changing traffic characteristics marking in dynamic policies . 22
10.3.3.1 Dynamically changing traffic characteristics marking for data bursts . 22
10.3.3.2 Dynamically changing traffic characteristics marking for expedited data transfers. 23
10.3.4 Enabling multiplexed media flow handling in dynamic policies . 23
10.4 Network Assistance API . 24
10.5 Metrics Reporting API . 25
10.6 Consumption Reporting API . 25
10.6.1 General . 25
10.6.2 ConsumptionReport data type. 25
10.6.3 ConsumptionReportingUnit type . 25
11 Media session handling client API (RTC-6, RTC-11) . 26
12 Media access client API (RTC-7, RTC-11) . 26
13 Protocols of real-time media communication. 26
13.1 General . 26
13.2 WebRTC signalling protocol . 26
13.2.1 General . 26
13.2.2 Protocol and version identification . 27
13.2.3 WebSocket URI structure . 27
13.2.4 SWAP . 27
13.2.4.1 Protocol and version identification . 27
13.2.4.2 Transport . 27
13.2.4.3 State machine . 29
13.2.4.4 Message syntax and semantics . 30
13.2.4.4.1 Common message fields . 30
13.2.4.4.1.1 Source (source) . 30
13.2.4.4.1.2 Message Identifier (messge_id) . 30
13.2.4.4.1.3 Message Type (message_type) . 31
13.2.4.4.2 Register message . 31
13.2.4.4.2.1 Description . 31
13.2.4.4.2.2 Parameters . 31
13.2.4.4.3 Response message . 32
13.2.4.4.3.1 Description . 32
13.2.4.4.3.2 Parameters . 32
13.2.4.4.4 Connect message . 32
13.2.4.4.4.1 Description . 32
13.2.4.4.4.2 Parameters . 32
13.2.4.4.5 Accept message . 32
13.2.4.4.5.1 Description . 32
13.2.4.4.5.2 Parameters . 32
13.2.4.4.6 Update message . 33
13.2.4.4.6.1 Description . 33
13.2.4.4.6.2 Parameters . 33
13.2.4.4.7 Reject message . 33
13.2.4.4.7.1 Description . 33
13.2.4.4.7.2 Parameters . 33
13.2.4.4.8 Close message . 33
13.2.4.4.8.1 Description . 33
13.2.4.4.8.2 Parameters . 33
13.2.4.4.9 Application message . 33
13.2.4.4.9.1 Description . 33
13.2.4.4.9.2 Parameters . 33
13.2.4.5 Integrity and security. 34
13.2.4.6 JSON schema . 34
13.2.4.7 Protocol operation . 36
14 Packet loss handling . 36
ETSI
3GPP TS 26.113 version 19.2.0 Release 19 5 ETSI TS 126 113 V19.2.0 (2026-04)
14.1 Packet loss handling mechanisms in RTC endpoints . 36
14.1.1 Video . 36
14.1.1.1 General . 36
14.1.1.2 NACK messages . 37
14.1.1.3 PLI message . 37
14.1.1.4 SLI message . 37
14.1.1.5 FIR message . 37
14.1.1.6 Temporal-Spatial Trade-Off Request (TSTR). 37
14.1.1.7 Temporary Maximum Media Stream Bit Rate Request (TMMBR) . 37
14.1.1.8 RTP retransmission . 37
14.2 Packet-loss handling mechanisms supported in RTC endpoint . 38
14.2.1 General . 38
14.2.2 Video . 38
14.2.2.1 General . 38
14.2.2.2 NACK, PLI, SLI and FIR messages . 38
14.2.2.3 TMMBR and TMMBN messages . 39
14.2.2.4 RTP retransmission . 39
15 RTC QoE metrics reporting protocol . 39
15.1 General . 39
15.2 Quality of Experience metrics definition . 39
15.2.1 Introduction. 39
15.2.2 Corruption duration metric . 40
15.2.3 Successive loss of RTP packets . 41
15.2.4 Frame rate . 41
15.2.5 Jitter duration . 42
15.2.6 Sync loss duration . 42
15.2.7 Round-trip time . 43
15.2.8 Average codec bit rate . 43
15.3 Quality metrics reporting protocol . 44
15.3.1 General . 44
15.3.2 Report format . 44
15.3.3 Reporting protocol . 45
16 Media capabilities . 47
Annex A (informative): RTC client in terminal . 48
A.1 Overview of high-level RTC data flow . 48
A.2 Reference RTC endpoint model . 49
A.2.0 General . 49
A.2.1 Audio . 51
A.2.1.2 Microphone . 51
A.2.1.2 Pre/post-processor . 51
A.2.2 Video . 52
A.2.2.1 Camera . 52
A.2.2.2 Pre/post-processor . 53
A.2.3 Sensor . 53
A.2.3.1 General . 53
A.2.3.2 Measure . 53
Annex B (normative) OpenAPI representation of HTTP REST APIs . 54
B.1 General . 54
B.2 OpenAPI representation of RTC-1 APIs . 54
B.2.0 Maf_Provisioning API . 54
B.3 OpenAPI representation of RTC-3 APIs . 54
B.4 OpenAPI representation of RTC-5 APIs . 54
B.4.0 Maf_SessionHandling API . 54
Annex C (normative): Controlled vocabularies of RTC Client configuration parameters . 55
ETSI
3GPP TS 26.113 version 19.2.0 Release 19 6 ETSI TS 126 113 V19.2.0 (2026-04)
C.1 Controlled vocabulary of RTC QoE metrics reporting parameters . 55
Annex D (informative): Change history . 56
History . 57

ETSI
3GPP TS 26.113 version 19.2.0 Release 19 7 ETSI TS 126 113 V19.2.0 (2026-04)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
3GPP TS 26.113 version 19.2.0 Release 19 8 ETSI TS 126 113 V19.2.0 (2026-04)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.

ETSI
3GPP TS 26.113 version 19.2.0 Release 19 9 ETSI TS 126 113 V19.2.0 (2026-04)
1 Scope
The present document specifies the set of stage-3 procedures, APIs, and protocols for the reference points defined in
Real-Time Media Communication (RTC) architecture. While TS 26.510 defines the common set of APIs and
interactions, this document refers to TS 26.510 for the general aspects and primarily deals with RTC-specific aspects to
support WebRTC-based real-time media transport over 5G.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 26.506: "5G Real-time Media Communication Architecture (Stage 2)".
[3] 3GPP TS 26.510: "Media delivery; interactions and APIs for provisioning and media session
handling".
[4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] IETF RFC 9110 (2022): "HTTP Semantics".
[6] 3GPP TS 26.512: "5G Media Streaming (5GMS); Protocols".
[7] IETF RFC 8834 (2021): "Media Transport and Use of RTP in WebRTC".
[8] IETF RFC 8835 (2021): "Transports for WebRTC".
[9] 3GPP TS 23.003: "Numbering, addressing and identification".
[10] IETF RFC 8829 (2021): "JavaScript Session Establishment Protocol (JSEP)".
[11] IETF RFC 7807 (2016): "Problem Details for HTTP APIs".
[12] IETF RFC 8825 (2021): "Overview: Real-Time Protocols for Browser-Based Applications".
[13] IETF RFC 5124 (2008): "Extended Secure RTP Profile for Real-time Transport Control Protocol
(RTCP)-Based Feedback (RTP/SAVPF)".
[14] IETF RFC 7007 (2013): "Update to Remove DVI4 from the Recommended Codecs for the RTP
Profile for Audio and Video Conferences with Minimal Control (RTP/AVP)".
[15] IETF RFC 3551 (2003): "RTP Profile for Audio and Video Conferences with Minimal Control".
[16] IETF RFC 4585 (2006): "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-
Based Feedback (RTP/AVPF)".
[17] IETF RFC 3711 (2004): "The Secure Real-time Transport Protocol (SRTP)".
[18] IETF RFC 5104 (2008): "Codec Control Messages in the RTP Audio-Visual Profile with
Feedback (AVPF)".
[19] IETF RFC 4588 (2006): "RTP Retransmission Payload Format".
ETSI
3GPP TS 26.113 version 19.2.0 Release 19 10 ETSI TS 126 113 V19.2.0 (2026-04)
[20] 3GPP TS 26.114: " IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and
interaction".
[21] IETF RFC 9112 (2022): "HTTP/1.1".
[22] IETF RFC 7478 (2015): "Web Real-Time Communication Use Cases and Requirements".
[23] 3GPP TS 26.119: "Media Capabilities for Augmented Reality"
[24] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[25] Apple: "Getting Raw Accelerometer Events",
https://developer.apple.com/documentation/coremotion/getting_raw_accelerometer_events.
[26] Google: "Sensor Coordinate System", https://developer.android.com/develop/sensors-and-
location/sensors/sensors_overview.
[27] ITU-R Recommendation BT.601-7 (03/2011): "Studio encoding parameters of digital television
for standard 4:3 and wide screen 16:9 aspect ratios".
[28] Microsoft: "Microphone Array Geometry Descriptor Format", https://learn.microsoft.com/en-
us/windows-hardware/drivers/audio/microphone-array-geometry-descriptor-format.
[29] IETF RFC 8831 (2021): "WebRTC Data Channels".
[30] IETF RFC 8261 (2017): "Datagram Transport Layer Security (DTLS) Encapsulation of SCTP
Packets".
[31] W3C Recommendation: WebRTC: Real-Time Communication in Browsers, March 2023.
https://www.w3.org/TR/webrtc/
[32] IETF RFC 7874 (2016): "WebRTC Audio Codec and Processing Requirements"
[33] IETF RFC 7742 (2016): "WebRTC Video Processing and Codec Requirements"
[34] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Services (PSS); Progressive
Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".
[35] OpenAPI: "OpenAPI 3.0.0 Specification", https://github.com/OAI/OpenAPI-
Specification/blob/master/versions/3.0.0.md.
[36] 3GPP TS 26.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[37] 3GPP TS 26.522: "5G Real-time Media Transport Protocol Configurations".
[38] 3GPP TS 29.514: "5G System; Policy Authorization Service".
[39] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane nodes".
3 Definitions of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in
the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
RTC Application: A Native WebRTC Application or a Web App that is compliant with the profile of a WebRTC-
based application defined in the present document.
RTC endpoint: A WebRTC endpoint incorporating an instance of the WebRTC Framework that is capable of
participating in an RTC session and which is deployed either in the RTC Access Function of a UE or in the Media
Function of an RTC AS.
ETSI
3GPP TS 26.113 version 19.2.0 Release 19 11 ETSI TS 126 113 V19.2.0 (2026-04)
RTC Client: UE function comprising an RTC Access Function and an RTC Media Session Handler which interacts
with functions in the network and UE applications.
RTC Access Function: A set of functions including an instance of the WebRTC Framework. The RTC Access
Function exchanges real-time media with one or more RTC endpoints via reference point RTC-4m or RTC-12, and the
RTC Access Function exchanges signalling messages with WebRTC Signalling Function via reference point RTC-4s.
Also, the RTC Access Function exposes client APIs defined in the present document to the RTC Application at
reference point RTC-7 and to the RTC Media Session Handler at reference point RTC-11.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
API Application Programming Interface
AR Augmented Reality
DTLS Datagram Transport Layer Security
FFS For Further Study
FoV Field of View
HTTP Hyper-Text Transfer Protocol
ICE Interactive Connectivity Establishment
IMU Inertial Measurement Unit
MNO Mobile Network Operator
NAT Network Address Translation
OTT Over-The-Top
PSI PDU Set Importance
RGB Red-Green-Blue colour space
RTC Real-Time Communication
RTP Real-time Transport Protocol
RWT Response Wait Time
SCTP Stream Control Transmission Protocol
SRTCP Secure Real-time Transport Control Protocol
SRTP Secure Real-time Transport Protocol
SSE Server-Sent Events
STUN Session Traversal Utilities for NAT
SWAP Simple WebRTC Application Protocol
TLS Transport Layer Security
TURN Traversal Using Relays around NAT
UPF User Plane Function
WebRTC Web Real-Time Communication
XR Extended Reality
ETSI
3GPP TS 26.113 version 19.2.0 Release 19 12 ETSI TS 126 113 V19.2.0 (2026-04)
4 Procedures for real-time media communication
4.1 General
This clause defines all procedures for real-time media communication using the different RTC reference points.
Table 4.1-1 summarises the APIs used to provision and use RTC features specified in TS 26.506 [2].
Table 4.1-1: Summary of APIs relevant to RTC features
RTC Abstract Relevant APIs
feature Interface API name Clause
Content Content delivery is configured Provisioning Sessions API 6.2
configuration according to Configuration
RTC-1 Real-time Media Communication 6.3
Provisioning associated with a provisioning API
Provisioning Session.
Service Access Information API 10.2
RTC-5
Metrics The RTC endpoint uploads metrics Provisioning Sessions API 6.2
RTC-1
reporting reports to the RTC AF according to
Metrics Reporting Provisioning API 6.7
a provisioned Metrics Reporting
Service Access Information API 10.2
Configuration it obtains from the
Metrics Reporting API 10.5
RTC-5
Service Access Information for its
Provisioning Session.
Consumption The RTC endpoint provides Provisioning Sessions API 6.2
reporting feedbac
...