Statement of Compliance
Release 7.1
E55132-02
April 2015
This document is a statement of compliance for the communications protocols supported by Oracle Communications WebRTC Session Controller.
The WebRTC Session Controller complies with the following standards, which are defined in the Internet Engineering Task Force specification https://tools.ietf.org/html/draft-ietf-rtcweb-overview-12:
The WebRTC Session Controller JavaScript API supports any WebRTC user agent.
The WebRTC Session Controller server is a compliant WebRTC gateway.
The WebRTC Session Controller media engine is a WebRTC compatible endpoint.
The WebRTC Session Controller Android and IOS SDKs support any WebRTC device.
WebRTC Session Controller is compliant with the following Internet Engineering Task Force (IETF) standards and protocols Request for Comments (RFCs):
Overview: Real Time Protocols for Browser-based Applications. See https://tools.ietf.org/html/draft-ietf-rtcweb-overview-12.
Javascript Session Establishment Protocol. See http://tools.ietf.org/html/draft-ietf-rtcweb-jsep-08.
RFC 5245: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols. See http://tools.ietf.org/html/rfc5245.
RFC 5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN). See http://tools.ietf.org/html/rfc5766.
RFC 5389: Session Traversal Utilities for NAT (STUN). See http://tools.ietf.org/html/rfc5389.
RFC 3711: The Secure Real-time Transport Protocol (SRTP). See http://www.ietf.org/rfc/rfc3711.txt.
RFC 4568: Session Description Protocol (SDP) Security Descriptions for Media Streams. See http://tools.ietf.org/html/rfc4568.
RFC 5763: Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS). See http://tools.ietf.org/html/rfc5763.
RFC 5124: Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-based Feedback (RTP/SAVPF). See http://tools.ietf.org/html/rfc5763.
RFC 3261: SIP: Session Initiation Protocol. See http://www.ietf.org/rfc/rfc3261.txt.
RFC 4975: The Message Session Relay Protocol (MSRP). See https://tools.ietf.org/html/rfc4975.
This section lists the Diameter Rx commands and AVPs that Oracle Communication WebRTC Session Controller supports. The supported protocol specification is Policy and Charging Control over Rx reference point 3GPP TS 29.214 V.9.9.0 (2011-12) (Release 9).
Table 1 lists the Rx commands supported by Policy Controller.
| Command | Status | Link to List of Supported AVPs |
|---|---|---|
|
AA-Request (AAR) |
Supported |
|
|
AA-Answer (AAA) |
Supported |
|
|
Re-Auth-Request (RAR) |
Supported |
|
|
Re-Auth-Answer (RAA) |
Supported |
|
|
Session-Termination-Request (STR) |
Supported |
|
|
Session-Termination-Answer (STA) |
Supported |
|
|
Abort-Session-Request (ASR) |
Supported |
|
|
Abort-Session-Answer (ASA) |
Supported |
Table 2 lists the supported Diameter Rx AA-Request AVPs.
Table 2 Supported AA-Request AVPs
| AVP | Status |
|---|---|
|
Auth-Application-Id |
Supported |
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Destination-Realm |
Supported |
|
Destination-Host |
Supported |
|
AF-Application-Identifier |
Supported |
|
---- Media-Component-Description |
Supported |
|
---- ---- Media-Component-Number |
Supported |
|
---- ---- Media-Sub-Component |
Supported |
|
---- ---- AF-Application-Identifier |
Supported |
|
---- ---- Media-Type |
Supported |
|
---- ---- Max-Requested-Bandwidth-UL |
Supported |
|
---- ---- Max-Requested-Bandwidth-DL |
Supported |
|
---- ---- Flow-Status |
Supported |
|
---- ---- Reservation-Priority |
Supported. Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
---- ---- RS-Bandwidth |
Supported |
|
---- ---- RR-Bandwidth |
Supported |
|
---- ---- Codec-Data |
Supported |
|
---- Media-Component-Number |
Supported |
|
---- Media-Sub-Component |
Supported |
|
---- ---- Flow-Number |
Supported |
|
---- ---- Flow-Description |
Supported |
|
---- ---- Flow-Status |
Supported |
|
---- ---- Flow-Usage |
Supported |
|
---- ---- Max-Requested-Bandwidth-UL |
Supported |
|
---- ---- Max-Requested-Bandwidth-DL |
Supported |
|
---- ---- AF-Signalling-Protocol |
Supported |
|
---- AF-Application-Identifier |
Supported |
|
---- Media-Type |
Supported |
|
---- Max-Requested-Bandwidth-UL |
Supported |
|
---- Max-Requested-Bandwidth-DL |
Supported |
|
---- Flow-Status |
Supported |
|
---- Reservation-Priority |
Supported |
|
---- RS-Bandwidth |
Supported Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
---- RR-Bandwidth |
Supported |
|
---- Codec-Data |
Supported |
|
Service-Info-Status |
Supported |
|
AF-Charging-Identifier |
Supported |
|
SIP-Forking-Indication |
Supported |
|
Specific-Action |
Supported |
|
Subscription-Id |
Supported Reused from RFC 4006. |
|
---- Subscription-Id-Type |
Supported Reused from RFC 4006. |
|
---- Subscription-Id-Data |
Supported Reused from RFC 4006 |
|
Supported-Features |
Supported Reused from 3GPP TS 29.229 |
|
---- Vendor-Id |
Supported Reused from 3GPP TS 29.229 |
|
---- Feature-List-ID |
Supported Reused from 3GPP TS 29.229 |
|
---- Feature-List |
Supported Reused from 3GPP TS 29.229 |
|
Reservation-Priority |
Supported Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
Framed-IP-Address |
Supported Reused from RFC 4005 |
|
Framed-IPv6-Prefix |
Supported Reused from RFC 4005 |
|
Called-Station-Id |
Supported Reused from RFC 4005 |
|
Service-URN |
Supported |
|
Origin-State-Id |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
|
Route-Record |
Supported |
Table 3 lists the supported Diameter Rx AA-Answer AVPs.
Table 3 Supported AA-Answer AVPs
| AVP | Status |
|---|---|
|
Auth-Application-Id |
Supported |
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Result-Code |
Supported |
|
Experiment-Result |
Supported |
|
Access-Network-Charging-Identifier |
Supported |
|
---- Access-Network-Charging-Identifier-Value |
Supported |
|
---- Access-Network-Charging-Identifier-Value |
Supported |
|
---- Flows |
Supported |
|
---- ---- Media-Component-Number |
Supported |
|
---- ---- Flow-Number |
Supported |
|
---- ---- Final-Unit-Action |
Supported Reused from RFC 4006 |
|
Access-Network-Charging-Address |
Supported |
|
Acceptable-Service-Info |
Supported |
|
---- Media-Component-Description |
Supported |
|
---- ---- Media-Component-Number |
Supported |
|
---- ---- Media-Sub-Component |
Supported |
|
---- ---- Flow-Number |
Supported |
|
---- ---- Flow-Description |
Supported |
|
---- ---- Flow-Status |
Supported |
|
---- ---- Flow-Usage |
Supported |
|
---- ---- Max-Requested-Bandwidth-UL |
Supported |
|
---- ---- Max-Requested-Bandwidth-DL |
Supported |
|
---- ---- AF-Signalling-Protocol |
Supported |
|
---- ---- AF-Application-Identifier |
Supported |
|
---- ---- Media-Type |
Supported |
|
---- ---- Max-Requested-Bandwidth-UL |
Supported |
|
---- ---- Max-Requested-Bandwidth-DL |
Supported |
|
---- ---- Flow-Status |
Supported |
|
---- ---- Reservation-Priority |
Supported Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
---- ---- RS-Bandwidth |
Supported |
|
---- ---- RR-Bandwidth |
Supported |
|
---- ---- Codec-Data |
Supported |
|
---- Max-Requested-Bandwidth-DL |
Supported |
|
---- Max-Requested-Bandwidth-UL |
Supported |
|
IP-CAN-Type |
Supported Reused from 3GPP TS 29.212 |
|
RAT-Type |
Supported Reused from 3GPP TS 29.212 |
|
Supported-Features |
Supported Reused from 3GPP TS 29.229 |
|
---- Vendor-Id |
Supported Reused from 3GPP TS 29.229 |
|
---- Feature-List-ID |
Supported Reused from 3GPP TS 29.229 |
|
---- Feature-List |
Supported Reused from 3GPP TS 29.229 |
|
Class |
Supported |
|
Error-Message |
Supported |
|
Error-Reporting-Host |
Supported |
|
Failed-AVP |
Supported |
|
---- AVP |
Yes |
|
Origin-State-Id |
Supported |
|
Redirect-Host |
Supported |
|
Redirect-Host-Usage |
Supported |
|
Redirect-Max-Cache-Time |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy State |
Supported |
Table 4 lists the supported Diameter Rx Re-Auth-Request AVPs.
Table 4 Supported Re-Auth-Request AVPs
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Destination-Realm |
Supported |
|
Destination-Host |
Supported |
|
Auth-Application-Id |
Supported |
|
Specific-Action |
Supported |
|
Access-Network-Charging-Identifier |
Supported |
|
---- Access-Network-Charging-Identifier-Value |
Supported |
|
---- Access-Network-Charging-Identifier-Value |
Supported |
|
---- Flows |
Supported |
|
---- ---- Media-Component-Number |
Supported |
|
---- ---- Flow-Number |
Supported |
|
---- ---- Final-Unit-Action |
Supported Reused from RFC 4006 |
|
Access-Network-Charging-Address |
Supported |
|
Flows |
Supported |
|
---- Media-Component-Number |
Supported |
|
---- Flow-Number |
Supported |
|
---- Final-Unit-Action |
Supported Reused from RFC 4006 |
|
Subscription-Id |
Supported Reused from RFC 4006 |
|
---- Subscription-Id-Type |
Supported Reused from RFC 4006 |
|
---- Subscription-Id-Data |
Supported Reused from RFC 4006 |
|
Abort-Cause |
Supported |
|
IP-CAN-Type |
Supported Reused from 3GPP TS 29.212 |
|
RAT-Type |
Supported Reused from 3GPP TS 29.212 |
|
Origin-State-Id |
Supported |
|
Class |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
|
Route-Record |
Supported |
Table 5 lists the supported Diameter Rx Re-Auth-Answer AVPs.
Table 5 Supported Re-Auth-Answer (RAA) AVPs
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Experimental-Result |
Supported |
|
---- Vendor-Id |
Supported |
|
---- Experimental-Result-Code |
Supported |
|
Media-Component-Description |
Supported |
|
---- Media-Component-Number |
Supported |
|
---- Media-Sub-Component |
Supported |
|
---- AF-Application-Identifier |
Supported |
|
---- Media-Type |
Supported |
|
---- Max-Requested-Bandwidth-UL |
Supported |
|
---- Max-Requested-Bandwidth-DL |
Supported |
|
---- Flow-Status |
Supported |
|
---- Reservation-Priority |
Supported Reused from ETSI TS 183 017 V2.3.1 (2008-9) |
|
---- RS-Bandwidth |
Supported |
|
---- RR-Bandwidth |
Supported |
|
---- Codec-Data |
Supported |
|
Service-URN |
Supported |
|
Origin-State-Id |
Supported |
|
Class |
Supported |
|
Error-Message |
Supported |
|
Error-Reporting-Host |
Supported |
|
Redirect-Host |
Supported |
|
Redirect-Host-Usage |
Supported |
|
Redirect-Max-Cache-Time |
Supported |
|
Failed-AVP |
Supported |
|
---- AVP |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
Table 6 lists the supported Diameter Rx Session-Termination-Request AVPs.
Table 6 Supported Session-Termination-Request AVPs
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Destination-Realm |
Supported |
|
Auth-Application-Id |
Supported |
|
Termination-Cause |
Supported |
|
Destination-Host |
Supported |
|
Class |
Supported |
|
Origin-State-Id |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
|
Route-Record |
Supported |
Table 7 lists the supported Diameter Rx Session-Termination-Answer (STA) AVPs.
Table 7 Supported Session-Termination-Answer AVPs
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Result-Code |
Supported |
|
Error-Message |
Supported |
|
Error-Reporting-Host |
Supported |
|
Failed-AVP |
Supported |
|
Origin-State-Id |
Supported |
|
Class |
Supported |
|
Redirect-Host |
Supported |
|
Redirect-Host-Usage |
Supported |
|
Redirect-Max-Cache-Time |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy-State |
Supported |
Table 8 lists the supported Diameter Rx Abort-Session-Request (ASR) AVPs.
Table 8 Supported Abort-Session-Request AVPs
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Destination-Realm |
Supported |
|
Destination-Host |
Supported |
|
Auth-Application-Id |
Supported |
|
Abort-Cause |
Supported |
|
Origin-State-Id |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy State |
Supported |
|
Route-Record |
Supported |
Table 9 lists the supported Diameter Rx Abort-Session-Answer (ASA) AVPs.
Table 9 Supported Abort-Session-Answer AVPs
| AVP | Status |
|---|---|
|
Origin-Host |
Supported |
|
Origin-Realm |
Supported |
|
Result-Code |
Supported |
|
Origin-State-Id |
Supported |
|
Error-Message |
Supported |
|
Error-Reporting-Host |
Supported |
|
Failed-AVP |
Supported |
|
Redirect-Host |
Supported |
|
Redirect-Host-Usage |
Supported |
|
Redirect-Max-Cache-Time |
Supported |
|
Proxy-Info |
Supported |
|
---- Proxy-Host |
Supported |
|
---- Proxy State |
Supported |
Oracle Communications WebRTC Session Controller supports the following Rich Communications Services as defined by the Groupe Speciale Mobile Association (GSMA), http://www.gsma.com/network2020/rcs/:
Capabilities Exchange: Determine the capabilities of a remote endpoint, such as audio, video or file transfer support.
Stand Alone Messaging: Send simple messages between two endpoints.
One on One and Group Chat: Create real-time chat sessions between one or more participants.
File Transfer: Transfer files of any type between two endpoints.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Communications WebRTC Session Controller Statement of Compliance, Release 7.1
E55132-02
Copyright © 2013, 2015, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.