Limitations

(1)All turrets belonging to the same group must have their internal clock synchronized in order to display timers consistently. This can be ensured by enabling the option profile.setting.proxytime.enabled, (specify that the internal clock must be synchronized based on the PBX time); If the call is DDI, TPO internal clock must be synchronized with turrets as well.

(2)A duration timer that is currently paused is displayed steady (not incrementing). This is, for example, when a call is on hold on a shortcut, and the configuration specifies that alive timers must be displayed on such calls. However, a timer that is not yet started is never displayed. This is when, for example, a call on a handset has never been put on hold and the configuration specifies that hold timers must be displayed on the handset.

(3)The global duration is preserved only when a held call is resumed on another turret, or when an incoming call is picked up by another turret. The information is lost (timers are reset) when a call is transferred, dispatched, diverted, or parked. With PBX calls, it is also lost when a conference is created or destroyed.

(4)On PBX lines, the floating keys display duration timers for calls which match with another contact/shortcut/line key.  No timer is displayed for anonymous calls in the float area.

(5)On DDI lines, call timer information are reset in case of TPO Hot Backup occurrence. All calls hosted on the faulty TPO are reset to zero.