Oracle® Communications WebRTC Session Controller Installation Guide Release 7.0 E40974-02 |
|
|
PDF · Mobi · ePub |
This chapter provides instructions for Oracle Communications WebRTC Session Controller Signaling Engine (Signaling Engine) post-installation tasks.
Before continuing, you must complete the tasks in the following chapters:
After installing Signaling Engine, you must complete the following post-installation tasks:
Before continuing, you must start your Signaling Engine servers. See "Starting the Signaling Engine Servers" for more information.
You must enable DNS server lookup on your Signaling Engine installation to ensure that the maddr parameter in SIP headers is processed properly.
To enable DNS server lookup:
Start your Signaling Engine servers if they are not already running. See "Starting the Signaling Engine Servers" for more information.
Navigate to the WebLogic Server administration console and log in with your administrator username and password:
http://hostname:port/console
Note:
The default administration console port is 7001.In the Domain Structure pane, select SipServer.
Select the Configuration tab and then select the General sub tab.
In the General sub tab, scroll down and select the Enable DNS Server Lookup option.
Click Save.
Log out of the administration interface.
To set the SIP proxy server and registrar IP address:
Start your Signaling Engine servers if they are not already running. See "Starting the Signaling Engine Servers" for more information.
Navigate to the WebRTC Session Controller Signaling Engine console and log in with your administrator username and password:
http://hostname:port/wsc-console
Note:
The default Signaling Engine console port is 7001.Select the Script Library tab.
Click Lock and Edit.
In the Script Library pane, find the following lines and replace hostname and port with the hostname and port of your SIP proxy server and registrar:
/** Proxy/Registrar URI. */ public static final PROXY_SIP_URI = "sip:hostname:port"
Click Validate Library to ensure you introduced no errors. Fix any errors that are reported.
Click Commit to save your changes.
You must configure WebRTC Session Controller to provide authentication for WebRTC clients, even if you only want to allow unauthenticated access. For more information, see the discussion on configuring WebRTC Session Controller authentication in Oracle Communications WebRTC Session Controller System Administrator's Guide.
If you have created a clustered domain, you must enable the Coherence Security Framework. For instructions, see "Enabling the Oracle Coherence Security Framework
" in Securing Oracle Coherence.
You must install WebRTC Session Controller Media Engine servers. See "Installing WebRTC Session Controller Media Engine" for instructions.