406 - CM should buffer CMS interval data for PUMP-UP
Sam Osheroff
Currently if CMS goes offline, say for a patch, server reboot or network issue, data for the time it's offline is lost, even if it's entirely within an interval. When CMS comes back online, it gets a translations PUMP-UP from CM but that does not include any interval data. Ideally CM would buffer interval data and make that part of the PUMP-UP.
IAUG
Submitted to Avaya, 10/24/2025
J
John O'Brien
When a Skill's Real-Time 'Oldest Call Waiting' gets 'stuck' and shows lengthy time in queue when agents are available, using CMS Supervisor, we shut off data collection for a minute and then turn it back on. This triggers a translation PUMP-UP to resynch with the current state of measured targets. This clears the stuck OCW problem. We do this early in the morning (non busy-hours) to minimize impact on reports. You still get interval data, but it gets tagged as INCOMPLETE = "y". The PUMP-UP appears to be working logically. Perhaps a High Availability design would address your data integrity concerns.