My Oracle Support Banner

Time Sync Configuration for OCSM 3.4 and later in Oracle Linux (Doc ID 2251096.1)

Last updated on JULY 03, 2019

Applies to:

Oracle Communications Session Monitor - Version 3.4.x and later
Information in this document applies to any platform.

Symptoms

It is important for ALL OCSM nodes (MECs, MEs, Probes) to be in sync, as the call data is heavily based in the timestamp each packet (SIP, RTP, etc.) is marked with. A time difference between ME and Probe may cause packets to get dropped and never get evaluated, RTP packets to not get accounted for in voice quality statistics evaluation, and voice quality Screen being empty, among others. 

Changes

Note that in OCSM 3.3.9x releases, Date and Time configuration was part of PSA. In OCSM 3.4.x and later, this is part of the Operating System configuration, and not OCSM application. 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
 Applies to:
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.