Presence#
Presence combines all available information about the presence of the user.
This contains:
-
Sip subscriptions
-
Missed calls
Example: The following example presents the combination of presence and invite.
<key>
<keyConfiguration>
<function>
<invocations>
<invocation>
<invite>
<uri>77</uri>
</invite>
</invocation>
</invocations>
<reactions>
<reaction>
<presence>
<subscribe type="dialog">
<uri>77</uri>
</subscribe>
</presence>
</reaction>
</reactions>
</function>
</keyConfiguration>
</key>
Sip Subscriptions#
Sip subscriptions are one variant of a presence reaction. Actually the only one at the moment. Currently only subscriptions of type "dialog" are supported. The phone will start a SIP subscription for every unique dialog subscription it finds within its key configurations.
multiple SIP Registrations#
You can specify which SIP registration to use if you have more than one. Do so by adding the line property (see example below). The line id's are the index of the identity within the identites configuration. The first index has the number 1. If you have multiple SIP registrations but you don't supply the id to use, the subscription is issued using the currently select default outgoing identity that is seen in the phone's idle screen. A change of the default outgoing identity changes will NOT cause any re subscriptions. So you really should define the identity if you use more than one.
dialog notifies#
The PBX will send SIP notifies when a subscription is first established and whenever the dialog state (sip dialogs aka calls) of the monitored party changes. The telephone protects itself of getting overwhelmed with analyzing too many dialog notifies at a time. It only processes a maximum of 10 notifies per second, all the others are queued and processed later. The phone might discard notifies entirely, if it gets bombarded with too many notifies so that the queue raises above 100.
Example of a dialog subscription configuration: