CounterPath Bria 3.1 Configuration Guide - Retail Deployments - Manual (Page 21)

Bria 3 Configuration Guide – Retail Deployments
17
2.16 Network – XMPP
XMPP is not supported in Bria for Linux.
This group covers settings relating to XMPP traffic. Make sure you set them for the XMPP account, if you
support this.
2.17 Presence
Presence is not supported in Bria for Linux.
This group of settings lets you configure how presence is supported when presence is handled using SIMPLE
on SIP accounts. For presence on XMPP accounts, no special configuration is required: presence subscriptions
are always created for XMPP buddies.
If you are not supporting presence through SIP, make sure you disable presence on every SIP account.
If you are supporting presence through SIP and your users have several SIP accounts, you will typically enable
presence on only one SIP account. Make sure you disable presence on the other SIP accounts.
If you support presence, you should also read “Resources” on page 18 for information on how Bria stores the
presence information (buddy list) and privacy rules.
How Presence Subscriptions are Handled
Bria supports IETF standard SIMPLE presence using a SIP subscription to the presence event package. Bria
supports the SIMPLE rich presence extensions (RPID - RFC 4480), which allows detailed presence information
to be conveyed in a standards-compliant manner.
Peer-to-Peer Presence Mode
In peer-to-peer presence modes, the clients in the network send SIP SUBSCRIBE and NOTIFY messages
directly to one another. The Bria that receives the request consults the local copy of the privacy rules to
determine whether a rule already exists. If no rule exists for the other party, then the request is deferred to the
user through a popup; the user’s action typically results in a privacy rule being created. The amount of SIP
message traffic on the network can be substantially larger than in presence agent mode.
Presence Agent Mode
In presence agent mode, when Bria is first started, it sends presence information to the network using the SIP
PUBLISH mechanism (RFC 3903). Bria still sends a SUBSCRIBE message per contact found in the contact list
when it is first started, but the presence agent will simply return a NOTIFY message with the current presence
document on behalf of the contact that was subscribed to. As well, Bria subscribes to the presence info (winfo -
RFC 3857, 3858) event package which will inform the user when they have to make a presence authorization
decision.