2 Configuring WebRTC Session Controller Signaling Properties and Media Nodes

This chapter describes the Signaling Engine and Media Engine configurations you perform in the Oracle Communications WebRTC Session Controller web console.

About WebRTC Session Controller Console Configuration

You use the WebRTC Session Controller console for configuring Signaling Engine properties and Media Engine nodes. Additionally, you manage WebRTC applications, packages, and scripts in the console. See WebRTC Session Controller Extension Developer's Guide for more information on managing applications, packages, and scripts.

You can also configure WebRTC Session Controller console options using configuration Mbeans. See the oracle.wsc.core.configuration.admin.mbean package page for more information on using these MBeans in Oracle Communications WebRTC Session Controller Configuration API Reference.

About Signaling Engine Properties

You configure the Signaling Engine run-time parameters in the WebRTC Session Controller console. Table 2-1 describes the configurable Signaling Engine parameters.

Table 2-1 Configurable Signaling Engine Run-time Parameters

Parameter	Description
Glare Handling	Selecting glare handling enables the Signaling Engine to avoid race conditions that arise when a caller and callee send simultaneous invitations, re-invitations, or session updates. By default, glare handling is selected and enabled.
Sip Session Default Time	The default SIP session time (in seconds). The default value is 3600 seconds.
Sip Session Minimum Time	The minimum SIP session time (in seconds). The default value is 90 seconds.
WebSocket Disconnect Time Limit	The time interval after which the websocket times out (in milliseconds). The defalt value is 60000 milliseconds.
WebSocket Idle Time Limit	The idle time interval after which the websocket times out (in seconds). The default value is 30 seconds.
WebSocket Maximum Connections	The maximum number of websocket connections allowed. Set this value to -1 for unlimited connections. The default value is -1.

About Media Engine Nodes Configuration and Status

You configure, remove, and manage Media Engine nodes in the WebRTC Session Controller console. Managing Media Engine nodes includes blocking and unblocking WebRTC network traffic to media nodes, monitoring their availability and ensuring the their load factor remains within acceptable limits.

Table 2-2 describes the configurable and viewable media node properties in the WebRTC Session Controller console.

Table 2-2 Media Node Properties

Property	Description
User	The user name required to connect to the Media Engine server.
Password	The password require to connect to the Media Engine server.
Address	The IP address of the Media Engine server.
Port	The port number of the media server connection.
Media Node Traffic Enabled	Whether traffic is enabled to the media node.
Media Node Status	Whether a connection to the media node is active.
Load Factor	The load percentage on a node controlled by the internal load balancer that attempts to distribute load evenly to available media nodes. WebRTC Session Controller will stop sending requests to media nodes with a Load Factor of 100%.

Accessing the WebRTC Session Controller Console Configuration Tab

The WebRTC Session Controller console resides on the same domain as your WebRTC Session Controller installation. When you start your domain, both the Oracle WebLogic Administration Console an the WebRTC Session Controller console become available.

You configure Signaling Engine and Media Engine parameters in the Configuration tab of the WebRTC Session Controller console. To access the WebRTC Session Controller console Configuration tab:

Start the WebRTC Session Controller domain server.
Open a web browser.
Access this URL:

http://host:port/wsc-console

where host:port represents the server and administration port number used by your domain server. If your environment uses HTTP security, use https.

The WebLogic user login screen appears.
Enter the Username and Password you set when creating the WebLogic domain.
Click Login.

The WebRTC Session Controller console window appears.
Select the Configuration tab.

The Signaling Engine parameters and Media Engine node window are displayed as shown in Figure 2-1.

Figure 2-1 WebRTC Session Controller Console Configuration Tab

Description of "Figure 2-1 WebRTC Session Controller Console Configuration Tab"

Configuring Signaling Engine Parameters

To configure Signaling Engine parameters:

Click Lock and Edit in the upper right corner of the screen.
Alter the Signaling Engine parameters listed in Table 2-1 as needed for your environment.
Click Commit.

Configuring Media Engine Nodes

You can perform the following media node configuration actions in the WebRTC Session Controller console in the Media Engine window:

Adding Media Engine Nodes
Removing Media Engine Nodes
Blocking and Unblocking Media Node Traffic
Setting Media Node Information Auto Refresh

Adding Media Engine Nodes

To add a Media Engine node:

Click Lock and Edit in the upper right corner of the screen.
Click Add.
Enter the Address and Port of the media server node.
Click OK.
Enter a User name and Password.
Click Commit.

Removing Media Engine Nodes

To remove a Media Engine node:

Click Lock and Edit in the upper right corner of the screen.
Select the row with the media node you want to remove.
Click Block Traffic.
Click Remove.

The Remove Media Node window appears.
Click OK.
Click Commit.

Blocking and Unblocking Media Node Traffic

To block or unblock traffic to a media node:

Click Lock and Edit in the upper right corner of the screen.
Select the row with the media node you want to block or unblock traffic to.
Click Unblock Traffic or Block Traffic.
Click Commit.

Setting Media Node Information Auto Refresh

You can configure media node information to auto refresh at specified time intervals.

To enable media node data auto refresh and set the refresh interval:

Select the Auto Refresh check box in the Media Engine window.
Select the interval in the drop-down menu.