Description: Defines the number of shortcuts (or corporate search entries) that trigger an automatic activation of the presence feature.
By default, the presence is only displayed on shortcuts if the shortcuts themselves, or a page containing them, has its presence attribute enabled. Presence is then monitored on each shortcut, showing the presence status of a user (not available, busy, free).
This setting, once enabled, allows the presence to be automatically activated and displayed on shortcuts, as soon as the current shortcut page, or search result, contains no more than a certain amount of entries.
This also applies to corporate searches.
Constraint: Positive numerical value, or 0.
0 means automatic presence is disabled.
Typically the size of a page is a good value (32 or 56 on a wide screen).
Related settings: Presence subscription garbage delay (profile.setting.presence.sub.terminate.delay) Dial plan - Internal extension length (profile.setting.dialingrule.internalnumberlength)
Description: Defines how long a presence subscription remains active once shortcut has been hidden
A presence subscription is only initiated when: - shortcut is shown - AND presence is activated - AND no subscription exists corresponding to the first shortcut extension.
Once a shortcut is hidden, the corresponding subscritpion may: - remain active until next logout, that may cause useless resource consumption - OR be terminated directly, that may increase charge on PBX for instance when a pop-up hide and show a shortcut panel - OR be terminated when the shortcut hasn't been shown for a while
By default subscription is terminated when the shortcut hasn't been shown for 30 seconds
Constraint: -1 : Presence subscription is only terminated on logout
0 : Presence subscription is terminated directly when shortcut is hidden
1 to 300000 : Presence subscription is terminated when the shortcut hasn't been shown for X seconds
Related settings: Automatic presence activation shortcuts/entries limit (profile.setting.presence.auto.max.shortcuts)
Description: A buffering mechanism has been implemented between SIP driver and upper layer to limit the number of SIP presence status messages which need to be processed. This option defines the maximum timeout a status message is held in the buffer before being delivered to the application.
The buffering mechanism is disabled if the specified value is lower than 10.
Constraint: Unsigned numeric value
Related settings: Registration state buffer (application.sip.reg.state.buffer.delay) DDI line registration state buffer (application.sip.ddiline.reg.state.buffer.delay)
