Session Monitor Post-Installation Tasks

This section provides instructions for the post-installation tasks for Session Monitor.

Before starting the post-installation tasks, verify that Session Monitor installation tasks are completed and all components are installed. See Installing Session Monitor Using the RPM.

About the Platform Setup Application

The Platform Setup Application guides you through the Session Monitor configuration steps, including configuring the machine type, capture settings, and simple mail transfer protocol (SMTP) settings as follows:

  1. Accept the license agreement to proceed with the Platform Setup Application.
  2. The menu on the right shows your progress during configuration.
  3. The Machine Type page sets which licensed Session Monitor applications are installed. In the Server Certificate page, you can upload your signed certificate for secure HTTPS connections.
  4. Subsequent sections configure the Session Monitor server for your network. These steps are optional.

    Except for Machine Type and Extensions, you can review and change settings at any time by visiting the Platform Setup Application at https:// ip_address /setup/, where ip_address is the IP address of the server that hosts a Session Monitor application. This URL is valid for any Session Monitor server.

  5. In the final step, each selected Session Monitor application is installed.

After a successful installation, the log in page appears for each of your licensed Session Monitor application.

Platform Setup Application Initial Log In

All the Session Monitor application interfaces are accessed through encrypted HTTPS connections. At the initial login, your web browser may not recognize the server and displays the This Connection is Untrusted warning message. Click Confirm Security Exception to proceed.

For information about how to protect connections to the system and avoid the untrusted certificate warning in the future, see Oracle Communications Session Monitor Security Guide.

This section describes how to configure Session Monitor using the Platform Setup Application.

To configure Session Monitor:

  1. In a web browser, go to https://<ip_address>/setup.
    The Platform Setup Application Log in page appears.
  2. In the Username field, enter sysadmin and; in the Password field, enter oracle.
    The License Terms agreement page appears.
  3. Accept each Session Monitor application license terms agreement, by selecting the I agree to the license terms check box.
  4. Click Proceed.

    The Change Password dialog box appears.

    The Platform Setup Application page appears.

  5. Change the password by doing the following:
    1. In the Set password field, enter a new password.


      The password must have at least 8 characters. The password must contain at least one uppercase character. The password must contain a number. The password must contain a special character (@, #, -, _, .).
    2. In the Repeat password field, re-enter the password used in the previous step, which verifies that the password value was entered correctly.
    3. Click Change.
    The Machine Type page appears.
  6. On the Machine Type page, select the machine type on which to install your licensed Session Monitor applications and components:
    • To install an Operations Monitor probe, select standalone Probe.
    • To choose different Session Monitor applications, select the Mediation Engine and then select the required product (or applications) as per the license:
      • To install Oracle Communications Operations Monitor, select the Communications Operations Monitor check box.
      • To install Oracle Communications Control Plane Monitor, select the Control Plane Monitor check box.
      • To install an Operations Monitor embedded probe, select the Probe (embedded) check box.

    Only the checked items are included in the installation.


    The Machine Type page only appears the first time you configure Session Monitor prior to the products installation. Machine type cannot be changed after the PSA installation is completed.

    You can select only one machine type for each installation process.

    Packet Inspector probe is not supported on a Session Monitor probe with SIP/RTP sniffing for the calls and VQ analysis.

    The products are machine-type specific and cannot be interchanged between machine types.

    For example, the Probe machine type requires a probe product, and the Mediation Engine machine type requires the Operations Monitor product.

    The machine type Mediation Engine Probe (embedded) must be chosen either with Operation Monitor or with Control Plane Monitor option selected.

  7. Click Continue.

    The machine type and application information appear in the status panel located on the right under the navigation list.

    The Configuration page appears.

  8. Configure the Session Monitor settings for the machine type you chose in step 5 in accordance with the terms of your license as follows:
    1. From the Capacity section in the Concurrent calls field, enter the number of concurrent calls printed on your license.
    2. If you have licensed RTP recording, select the RTP Recording check box.
    3. From the Capacity section in the Concurrent RTP streams field, enter the number of concurrent RTP streams printed on your license.


      The number entered in the Concurrent RTP streams field can cause performance and stability issues if it is set higher than what your network hardware supports. Values above 20 are not recommended. Changes to the RTP recording setting take effect only after restarting the system.
    4. From the Extensions section, select all the product extensions you have licensed.


      You cannot change the configured extensions after the installation. All Oracle Communications Session Monitor Enterprise users should select Media quality .
  9. Click Continue.
    The Disk Usage page appears.
  10. On the Disk Usage page, specify the maximum disk usage partition for the Packet Inspector.


    On the Disk Usage page, specify the maximum disk usage partition for the shared filesystem containing the database/data storage (single raid systems). For systems with two raid arrays you can select the usage independently for both filesystems. For Probes with Packet Inspector feature you would be able to select the maximum storage capacity.

    The ME Connection List page appears.


    The ME Connection List page appears only if you have selected machine type as Probe or Mediation Engine and Probe.
  11. (Optional) If you selected Probe on the Machine Type page, set which mediation engines are connected to the Operations Monitor probe.
    1. Click Add a new ME.
    2. In the Hostname or IP field, enter the IP address of the machine that hosts the mediation engine.
    3. In the Port field, enter the port number of the mediation engine. For a Cleartext transmission enter 4741 and for TLS enter 4742.
    4. In the Name field, enter a name for the mediation engine.
    5. In the TLS field, select the checkbox for TLS transmissions or leave the checkbox unchecked for Cleartext.
      The Operations Monitor Probe can transmit data to one or more mediation engines with either transport layer security (TLS) encryption, or with un-encrypted Cleartext. A mediation engine can connect to more than one Operations Monitor Probe or more than one Session Border Controller Probe.
  12. Click Continue.
    The Trusted Certificate page appears.
  13. In the Upload signed certificate field, select Browse and locate the signed certificate file. Click Continue.

    (Optional) By default, the mediation engine machine accepts only encrypted transmissions, (unless the mediation engine and probe are on the same machine); for Cleartext transmissions select the Accept insecure connections from remote probes check box.

    Click Continue.

    The Server Certificate page appears.

  14. All Session Monitor interfaces are accessed through encrypted (secure) HTTPS connections. Each Session Monitor machine uses a unique certificate to establish secure connections and to guarantee its authenticity and protect users' data.
    Do one of the following:
    • To use the self-signed certificate, click Continue.
    • To sign the server certificate with your organization's Public Key Infrastructure (PKI):
      1. Select Download request.
      2. Sign the certificate with the X.509 format.
      3. In the Upload signed certificate field, select Browse and locate the signed certificate file.
      4. Click Continue. The SMTP Configuration page appears.


      • To regenerate a key and certificate on install, select Regenerate key and self-signed certificate on install and click Continue.
      • (Optional) Click Download current certificate to download the current self-signed certificate.
  15. Session Monitor can send notifications and alerts directly to a user's email address. If you require notifications or alerts, select the Enable SMTP check box and fill in the relevant fields with your SMTP server details.
  16. Click Continue.

    The Capture Settings page appears.

  17. The Capture Settings page contains a list of configured network interfaces. Monitoring can be enabled and disabled. You should have configured network devices while installing Oracle Linux 7.
  18. Click Continue.
    The Data Retention page appears.
  19. Click Continue.
    The Install page appears.
  20. (Optional) Click Download Configuration, which downloads your configuration settings file in the default download location of your system.
  21. Open the psa_conf.json configuration file and verify your settings.
  22. Click Install.
    The Did you select the right applications dialog box appears.
  23. Verify that you have chosen the correct Session Monitor applications and components for installation; after installation is complete, the selected applications and components cannot be changed.

    Click OK.

    The Platform Setup Application initiates the installation and reports its progress.

    The Installation Complete dialog box appears.

  24. Do one of the following:
    • To go back to the Platform Setup Application, click Back to Setup.
    • To go to a Session Monitor application dashboard, click Go to Application.
  25. The credentials for logging in to Session Monitor are:
    • For Platform Setup Application, enter the user name provided by Oracle and the password you set up in step 5.
    • For Operations Monitor and Control Plane Monitor, enter the login credentials provided by Oracle Sales Consultant.

Changing Community MySQL Edition to Enterprise Edition

Change the edition of MySQL by doing the following:
  1. From My Oracle Support (MOS), download the patch from Patches and Updates section:

    p28822761: MySQL Database 5.7.24 RPM for Oracle Linux / RHEL 7 x86 (64bit).

  2. Download the zip file and place it under /root or any directory on the system.
  3. Download the latest Enterprise edition of MySQL in version 5.7.38.
  4. Uninstall the Community edition of MySQL by running the following command:
    yum remove -y mysql-community-common
  5. List the MySQL packages that may have remained using this command:
    yum list installed mysql*
  6. If you are running mysql community version 8.0, then run this command to remove mysql-community-client-plug-ins:
    yum remove -y package mysql-community-client-plugins
  7. Install the Enterprise edition of MySQL by running the following command:
    yum install mysql-commercial-*.x86_64.rpm
  8. Install the yum utils by running the following command:
    yum -y install yum-utils
  9. Enable the latest Oracle Linux 7 add-on's by running the following command:
    yum-config-manager --enable ol7_latest ol7_UEKR4 ol7_developer_EPEL ol7_
    optional_latest ol7_addons ol7_UEKR3 ol7_UEKR5


Latest Public Yum Repo has to be downloaded for enabling the repo if you have not downloaded as part of Configuring Repos and Proxies.

Virtual Machine Probe Cloning

A cloned probe is an exact replica of the original probe having the same UUID as the original probe. However, each probe requires a unique UUID to establish a connection with the Mediation Engine. If the Probe Virtual Machine has been cloned, you must change the Unique ID of the probe after cloning and before connecting the cloned probe. Follow the instructions after cloning the probe to generate random UUID.

Ensure that the following prerequisites are taken care of:
  • Cloning of the probe has been successful.
  • Cloned probe is not connected to the Mediation Engine. If it was connected, remove:
    • Mediation Engine details on the probe
    • Probe details on the Mediation Engine
  1. Check for the UUID of both the probes under:
  2. Run the script to change the UUID of cloned probe:
  3. Check the UUID and make sure that the UUID of the cloned probe has been changed after running the script in the probe_uuid.conf file
  4. Connect the cloned probe to the Mediation Engine and make sure that the connection is successful.


    Connect the cloned probe to the Mediation Engine only after changing the UUID.