Presence Services supports the following Presence and IM capable Avaya Workplace Client clients:
Avaya Workplace Client 3.3 or later
Avaya Workplace Client Native
Avaya Workplace Client Web
Avaya Workplace Client Attendant
Avaya Workplace Client uses SIP for Presence information and REST protocol for IM.
Avaya Workplace Client use Presence Services to:
Gather real-time presence of users for watchers across the Avaya client portfolio.
Gather real-time presence of users for watchers across vendors such as Cisco, Microsoft, and third-party clients.
Support point-to-point and multiparty messaging, and compose and send multimedia messages, such as text, voice, video, file, and photo, between one or more Avaya Workplace Client users.
Create dynamic team or group conversations.
Hold subject-based conversations.
Support persistent conversations across devices and clients.
Store messages centrally and deliver the messages after the users connect.
Transition from multimedia messaging to voice, video, or multiparty collaborative calls.
Provide Is Typing and Message Read indication.
Provide emoticon pass through.
Note:
Presence Services does not support the Is Typing, Message Read, and emoticon and font pass through features when a user on an Avaya Workplace Client is in conversation with a contact on a federated system such as Microsoft S4B, Openfire, or Cisco Jabber.
Presence Services does not support deployments where both Avaya Workplace Client and Avaya one-X® Communicator clients are used for instant messaging.
Avaya Workplace Client support limitations
Avaya Workplace Client release 3.4.8 and later support Access Control List functionality. Avaya Workplace Client prior to release 3.4.8 does not support Access Control List functionality.
You must specify the Avaya Breeze® platform cluster service FQDN in the Multimedia Messaging Server Address parameter of the Avaya Workplace Client client. This ensures that the Avaya Workplace Client client properly connects to Presence Services.
