This chapter describes the software, hardware, and information requirements for Oracle Communications WebRTC Session Controller.
This section describes the required software for the two WebRTC Session Controller sub components, Signaling Engine and Media Engine.
Signaling Engine is certified on Oracle Linux x64 versions 6 and 7, running either natively or as a part of Oracle VM Server.
In addition, Signaling Engine requires a 64-bit Java Development Kit (JDK) version 1.8 plus the latest security update.
Note:
OpenJDKs of any version are not supported.The following platforms have been certified for use with the Signaling Engine:
Kernel-based Virtual Machine (KVM)
VMware ESXi
Oracle Virtual Machine (OVM)/Oracle Enterprise Linux (OEL)
Media Engine is certified to run on Oracle Linux version 7.0 or higher and uses yum to install and update RPM files. For more information, see "WebRTC Session Controller Media Engine Installation Overview".
The following platforms have been certified for use with the Media Engine:
Sun Netra X5-2
Sun Server X5-2
Sun Netra X3-2
HP DL160 G9
NN2610
NN2620
The following VM platforms have been certified for use with the Media Engine:
OVM 3.3.1
VMware ESXi 5.5
Xen 3.4.3
KVM on OL7
WebRTC Session Controller requires access to the following port types:
WebRTC client ports: Ports that WebRTC applications use to communicate with WebRTC Session Controller. Client ports must be exposed through a firewall to client applications.
SIP network ports: Ports that WebRTC Session Controller uses to communicate with the SIP network. The SIP network is usually internal.
Media ports: Ports used for media anchoring; exposed to both WebRTC clients and the SIP network. Media ports must be exposed through a firewall to client applications.
Internal administration ports: Ports used for administration of WebRTC Session Controller. Internal administration ports need not be exposed externally, but must be accessible between Signalling Engine and Media Engine instances.
Table 3-1 lists the Signalling Engine port requirements.
Table 3-1 Signalling Engine Port Requirements
| Port | Port Type | Description |
|---|---|---|
|
80 |
WebRTC client port |
The default port for WebRTC client communication (TCP). This port is not required if you are using Websockets Secure (WSS), 443. |
|
443 |
WebRTC client port |
The port for WebRTC client communication if you are using WSS (TCP). If you are using WSS you do not need port 80 open. |
|
4057 |
Internal administration port |
WebRTC Session Controller Media Engine HTTP callback port. Used for Signalling Engine/Media Engine communications. |
|
5060 |
SIP network port |
SIP network port. The default Session Initiation Protocol (SIP) port used to communicate with the SIP network. Not required if you are using Secure SIP (SIPS). |
|
5061 |
SIP network port |
The default Secure SIP (SIPS) port used to communicate with the SIP network. Not required if you are using the regular SIP port. |
|
7001 |
Internal administration port |
The default Signalling Engine Administration HTTP port. Not required if you are using the Secure Sockets Layer (SSL) administration port, 7002. |
|
7002 |
Internal administration port |
The default SSL Signalling Engine Administration HTTPS port. Not required if you are using the non-SSL port. |
|
8443 |
WebRTC client port |
The port for communication between the Signaling Engine and the Media Engine. |
Table 3-2 lists the Media Engine port requirements.
Table 3-2 Media Engine Port Requirements
| Port | Port Type | Description |
|---|---|---|
|
8080 |
Internal administration port |
The Media Engine load factor application port, used for Signalling Engine/Media Engine communications. The load factor application reports to the Signalling Engine on the status of connected Media Engine instances. |
|
Media port range (default 20000-24999) |
Media ports |
The UDP Media Engine media anchoring ports (SRTP and DTLS) |
|
3478 |
WebRTC client port |
The Traversal Using Relays around NAT (TURN) or Session Traversal Utilities for NAT (STUN) port (UDP, TCP, and TLS). |
WebRTC Session Controller is supported on all Oracle Critical Patch Updates. You should install all Critical Patch Updates as soon as possible.
To download Critical Patch Updates, find out about security alerts, and enable email notifications about Critical Patch Updates, see the Security topic on Oracle Technology Network:
http://www.oracle.com/technetwork/topics/security/whatsnew/index.html
This section describes the required hardware for the two WebRTC Session Controller sub components, Signaling Engine and Media Engine.
The number and configuration of the computers that you employ for your Signaling Engine installation depend on the scale and the kind of deployment you have planned according to your charging requirements. You will need to work with your performance team to determine your sizing requirements.
Signaling Engine has similar requirements to Oracle WebLogic Server 12c. The following items are required in addition to the basic WebLogic Server requirements:
Gigabit Ethernet connections are required between engine servers for all production deployments.
Dual network interface cards (NICs) are required to provide fail-over capabilities in a production environment.
Additional RAM is required to support the throughput requirements of most production installations.
Note:
Each Transport Control Protocol (TCP) WebSocket connection requires approximately 14 kilobytes of RAM.Media Engine is certified to run on several hardware platforms. For a complete list, see "Media Engine Hardware Requirements".
While Media Engine may run on other configurations, you are likely to run into disk controller as well as networking controller issues.
The number of physical or virtual servers will depend upon your particular environment load, but at a minimum each Media Engine server requires:
Gigabit Ethernet connections
4 GB of RAM
At least 50 GB of free hard disk space
64-bit Intel processor with two CPU cores