Bad/Incorrect MOS Values Only At a Particular/Regular Time(s) every Day
Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications Session Monitor - Version 3.3.90 to 3.3.90 [Release 3.0]
Information in this document applies to any platform.
Any timing-related issues, especially problems with the NTP server, can cause voice quality issues such as the system reporting incorrectly bad MOS. This happens because the MOS values are calculated per 10-second chunks in realtime, so any slight change or issue with the system time can affect these calculations.
The following items are potential signs that there might be issues with the NTP servers used in the system:
1. Massive increase in bad voice quality (bad MOS) for a particular time interval everyday - at relatively regular time intervals.
2. Chrony logfile /var/log/chrony/tracking.log.* shows repeated problems in the time synchronization (the IP Address is 0.0.0.0 -which means the server could not synchronize its time with the NTP server - more than one row at a time)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms