In previous releases, the
would be triggered for every Delay-Response message not received or received too
late - so triggers a timeout. Because missing the occasional Delay-Response message
should not adversely affect the synchronization accuracy or performance, in the
3.2.6 release, the alarm will only trigger after three consecutive Delay-Response
messages are not received.
For a full description of behavior changes and bug fixes, refer to the ChangeLog
section of the