Aura users: Presence and IM services are provided by Presence Services.
Federated users: Presence and IM services are provided by a third-party server, which is federated with Presence Services.
When two users user A and user B have a presence relationship, the users assume one of three roles:
Watcher: When user A adds user B to the contact or buddy list by subscribing to presence of user B , user A is a Watcher of user B.
Presentity: When user A adds user B to the contact or buddy list by subscribing to presence of user B, user B is a Presentity of user A.
Two-way: When user A adds user B to the contact or buddy list by subscribing to presence of user B, and user B adds user A to the contact or buddy list by subscribing to presence of user A, user A is both a Watcher of user B and a Presentity of user B.
Roster is the list of presence relationships of a user. On Presence Services, the size of roster of a user can be administered. By default, an Aura user can have:
A maximum of 100 presentities (contacts), that is, 100 relationships where the user role is Watcher or Two-way.
A maximum of 100 federated watchers, that is, 100 relationships where the user role is Presentity or Two-way, and the watcher is a federated user
In the case where an Aura user has a Two-way relationship with a federated watcher, the relationship is subject to both limits. For instance, if an Aura user has a Two-way relationship with 100 federated users, then both default limits have been reached.
For an Aura H.323 watcher, once an Aura user’s maximum number of presentities or contacts has been reached, when the watcher attempts to add another presentity:
Presence Services rejects the subscription and returns an XMPP error.
The watching user will not see presence of the presentity.
The device of watching user may display an error to the user. For more information, consult Avaya endpoint documentation.
For an Aura SIP watcher, once an Aura user’s maximum number of presentities or contacts has been reached, when the watcher attempts to add another presentity:
Presence Services rejects the subscription and returns a SIP error.
The watching user will not see presence of the presentity.
The Presence Buddy flag of the contact will be set to No. On System Manager, this is available at UsersUser ManagementManage UsersContactsAssociated Contacts.
The device of watching user may display an error to the user. For more information, consult Avaya endpoint documentation.
For a federated SIP or XMPP watcher, once an Aura user’s maximum number of federated watchers has been reached, when another federated watcher attempts to subscribe to the Aura user’s presence:
Presence Services rejects the subscription and returns a SIP or XMPP error.
Presence Services will not send the Aura user’s presence information to the federated server.
Refer to the third-party server documentation to determine how the third-party server behaves in this scenario.
