Key features of Presence Services

Last Updated : Oct 06, 2020 |
Prolog information
Presence Services support:
  • Presence aggregation service that collects the presence information from Avaya and third-party sources and distributes the presence information to the Avaya tools.
  • Aggregation of presence information from a variety of Avaya endpoints, including Avaya Workplace Client clients.
  • Presence model that uses rules in an algorithm to arrive at an aggregated presence for a user.
  • Protocols such as SIP and XMPP. These protocols enable Presence Services to aggregate and federate presence with major IM and messaging solutions and a number of user-productivity tools.
  • Architectural design that improves network traffic management. To reduce traffic on the network, Presence Services uses server-to-server updates to collect and publish presence information.
  • Supports robustness. 9600 Series IP Deskphones Release 6.5 and 7.0, Avaya one-X® Communicator Release 6.2, Avaya Workplace Client for Windows, and Avaya Workplace Client for iPad support this Presence Services feature.
  • Up to 2048 characters for Extensible Messaging and Presence Protocol (XMPP) IM.
  • Presence Services supports the following IM services. IM services allow users to exchange messages in various formats like text, image, voice, and video.
    • Point-to-point IM between users.
    • IM conversation status indication. For example, if the other user is typing a response, chat window displays an indication that the other user is typing a message.
    • Multi-user chat.
    • IM to federated users like XMPP and Microsoft RTC (Skype for Business).
    • A user to log into multiple devices simultaneously. A user can log into multiple devices using the Multi-Device Access (MDA) feature. This is similar to placing all endpoints of the parties in a chat room.
    • Storing of messages when user is offline.
    • Sharing of multimedia message attachments.
    • Message archiving to keep a record of conversations for future reference.
    • Suspending of message and notifications delivery during the Do Not Disturb (DND) state.
    • Multi-tenant communication control.
    • Clustered deployment.
    • Multi-cluster deployments and auto-federation between clusters.