10 Troubleshooting a WebRTC Session Controller Installation

This chapter describes how to troubleshoot Oracle Communications WebRTC Session Controller installations.

Troubleshooting a Signaling Engine Installation

The WebRTC Session Controller Signaling Engine (Signaling Engine) installer and the Domain Configuration Wizard write information to log files. You can check those log files for information about errors and actions performed during the installation.

Signaling Engine Installation Log Files

The Signaling Engine installation logs can be found at Central_inventory_location/oraInventory/logs, where Central_inventory_location is the directory path to the oraInventory directory. If you do not know the location of your Oracle Inventory directory, you can find it in the oraInst.loc file in the directory, /etc/oraInst.loc.

The following install log files are written to the log directory:

• installdate-time-stamp.log

  This is the main log file.

• installdate-time-stamp.out

  This log file contains the output and error streams during the installation.

• installActionsdate-time-stamp.log

  This file is used by the installer GUI to keep track of internal information.

• installProfiledate-time-stamp.log

  This log file contains the overall statistics like time taken to complete the installation, as well as configuration, memory and CPU details.

• oraInstalldate-time-stamp.log

  This log file contains the output stream of the copy session.

• oraInstalldate-time-stamp.err

  This log file contains the error stream of the copy session.

Changing the Installer Logging Level

Use the -logLevel parameter from the command line when you start the installer. For example:

java -jar wsc_generic.jar -logLevel info

Valid value for -logLevel are listed below from most detailed to least detailed:

• debug

• info

• warning

• error

• fatal

Signaling Engine Domain Configuration Log Files

If you encounter errors when configuring a Signaling Engine domain, you can start the Fusion Middleware Configuration Wizard with the appropriate logging options.

To enable domain configuration logging, navigate to Oracle_home/oracle_common/common/bin and start config.sh with the -log and -log_priority options:

./config.sh -log=log_filename -log_priority=log_level

Table 10-1 describes the -log and -log_priority options.

Table 10-1 Configuration Wizard Log File Options

Parameter	Description
-log	Specify the location of your log file. If you specify a log file name, it is created in the same directory as the config.sh script unless you add a path component. Log files are otherwise created in Oracle_home/logs. Other values that can be specified with -log are: stdout This writes the error message to the standard output stream. stderr This writes the error messages to the standard error stream. disable This disables default logging so that no log files are generated in Oracle_home/logs.
-log_priority	Specify the level of detail you want included in your logs. The acceptable values are listed below, from most detailed to least detailed: debug info warning error fatal

Troubleshooting a Media Engine Installation

WebRTC Session Controller Media Engine (Media Engine) implements specialized troubleshooting commands that can be executed at the console command line interface (CLI).

For detailed troubleshooting instructions, see the discussion of Media Engine system monitoring in Oracle Communications Application Session Controller System Operations and Troubleshooting.

Checking Media Engine Event Logs

You can use the following CLI command to display events logged to the Media Engine's local database:

show event-log

Information in the Media Engine event log can provide details on software errors, connectivity issues, and incorrectly configured objects and properties.

Checking for Software Faults

You can use the following CLI command to display any software subsystem faults:

show faults

In conjunction with configuration files, traces and event logs, information for the show faults command can be used to troubleshoot system issues.

Checking for Hardware Issues

You can check the status of a Media Engine installation's hardware sensors using the CLI command:

show sensor-events

Likely failure points are power supplies and cooling fans.

Checking for Networking Issues

You can check Media Engine's network interface status using the CLI command:

show interfaces