This document provides release notes for Oracle Communications Session Monitor release 3.3.92.
Oracle Communications Session Monitor 3.3.92 includes new features, enhancements, and changed functionality including:
Session Monitor utilizes SNMP to integrate with other monitoring systems. SNMPv3 is supported in this release. SNMPv2 will continue to be supported.
SBCs now send interim media QoS messages during a call. The data is arranged and displayed in 10 second intervals. SBC voice quality reports now achieve parity with the Oracle Communications Operations Monitor (OCOM) probe which also displays QoS data at 10 second intervals.
You can create advanced filters to filter recent calls based on multiple criteria. You can save advanced filters after creation.
See "Advanced Filtering" in Oracle Communications Session Monitor User's Guide.
Table 1-1 lists the service request (SR) issues reported, bug number, and provides a brief description of the resolution.
Table 1-1 Fixes in This Release
| Service Request (SR) Number | Bug Number | Description |
|---|---|---|
|
Not applicable |
22151561 |
TCP traffic from SBC probes requires TCP quick push setting to be enabled. |
|
Not applicable |
22338356 |
SNMP traps for prefix tags KPI based alerts does not work. |
|
Not applicable |
22480582 |
Platform Setup Application complains about missing DNS config when using NTP server IP address. |
|
Not applicable |
22503035 22503061 22503095 |
User permissions for managing prefix tags and realm/snmp. |
|
Not applicable |
22503426 |
Packet Inspector source and destination columns are not properly sorted. |
|
Not applicable |
22503161 |
MEC user is unable to change its password when user permissions are too low. |
|
Not applicable |
22628017 |
Megaco legs are over correlated if the MGC uses the same transaction IDs for different MGs. |
|
Not applicable |
22671565 |
Change kernel script. |
|
Not applicable |
22200020 22332991 |
Improve the handling of concurrent trace runs. |
|
Not applicable |
Not applicable |
Added setup_delay attribute to CSV GUI exports. |
This section describes known problems and workarounds for release 3.3.92.
After you upgrade to 3.3.92.0.0, set the Mediation Engine Connector value for proxy_socket_timeout (configurable in /etc/iptego/masterweb.conf) to a value higher than the Timeout for Mediation Engine querying setting on the Mediation Engine. For example, 35 and 30 seconds, respectively. If the Mediation Engine takes up to 30 seconds to query its neighbors and compile the results, the Mediation Engine Connector will not drop the connection prematurely. Please refer to My Oracle Support for further assistance on setting these values.
This section describes workarounds for problems you may encounter when upgrading to release 3.3.90:
Upgrading from previous installations might take longer than expected.
Some parts of data migration runs in the background after an upgrade is applied.
Upgrading from Release 3.3.80 to 3.3.90
The procedure for setting a connection between Session Monitor probes and Mediation Engine has changed.
To retain the connections between your Session Monitor probes and Mediation Engine after an upgrade, do one the following:
If you are using standalone Session Monitor probes:
After the upgrade, manually repeat the setup to connect your Session Monitor probes and Mediation Engine. For more information, see "Mediation Engine Connection List" in Session Monitor Installation Guide.
Download and add the trusted certificates to Mediation Engine. For more information, see "Configuring Encrypted Communication" in Session Monitor Installation Guide.
Note:
By default, Mediation Engine rejects unencrypted connections.If you are using SBC probes, do one of the following:
If you require secure connections between SBC probes and Mediation Engine, download and add the trusted certificates to Mediation Engine. For more information, see "Configuring Encrypted Communication" in Session Monitor Installation Guide.
If you require unsecured connections between SBC probes and Mediation Engine, select the Accept insecure connections from remote probes check box in the Trusted Certificate page of Platform Setup Application.
The IPv6 protocol is supported and the default capturing filters have been modified. If you experience any capturing issues after an upgrade, review the new default filters and settings in the Media Protocols and Signaling Protocols pages in Platform Setup Application and make changes where applicable.
Upgrading from Release 3.3.70 to 3.3.90
The configuration to capture traffic has changed. Review the filters and settings in the Media Protocols page in Platform Setup Application and make changes where applicable.
By default the IPFIX connection between SBC probes and Operations Monitor machines enforces secure communication. Check your configuration in the Trusted Certificate page in Platform Setup Application and on your SBC probes.
Upgrading from Release 3.3.60 to 3.3.90
The RTP recording data retention system setting has been removed. The data retention of RTP recordings can be configured in the Data Retention page in Platform Setup Application.
Upgrading from Release 3.3.40 to 3.3.90
You cannot directly upgrade from a release older than 3.3.50. If you are using a 3.3.40 version, upgrade to a 3.3.50 version and then upgrade to release 3.3.90.
For security reasons, the user interface is available only over HTTPS. In some situations, after the upgrade is successfully completed the upgrade dialog will continue to show the running progress bar.
If the upgrade progress bar does not disappear after 30 minutes of starting the upgrade, refresh the browser window.
Upgrading from Release 3.0 to 3.3.90
You cannot directly upgrade from a release older than 3.3.50. If you are using a 3.0 version, upgrade to a 3.3.50 version and then upgrade to release 3.3.90.
The storing of data changed. All call and registration history will be ignored when you upgrade from release 3.0 to a later version.
When upgrading from a 3.1.X or 3.2.X version, it is possible that within a few hours after the upgrade the performance of the system will be lower and some calls may be lost.