This AbsoluteCounter32, in milliseconds, measures audio played out using signal reconstructed from redundancy parameters available when voice data was late or lost, and it locks at its two-day maximum value. Administrators look at it to confirm whether a redundancy-based loss recovery scheme (rather than prediction or interpolation) actually engaged during the call. For example, nonzero redundancy gap-fill time on a call would indicate the codec's redundant-data recovery path was actively compensating for packet loss on that leg.