If yare familiar with Lync Server 2010 then understanding Persistent Chat is no big deal. Since, Persistent Chat is the new and revised form of Group Chat, in Microsoft Lync Server 2013. The new title is more in sync with the functions it provides i.e. even if a user leaves after leaving a message in a chat room, it would remain in the session for others to read and comment, user ending the session does not remove the IM(s), which is the main reason it is renamed as Persistent Chat.
In general, for newbies, Persistent Chat allows multiple users to take part in conversations in which they can post and access content about particular topics. This content, which may include text, pictures, links, attached files, documents etc continues to exist even if the session is ended by users. The chat rooms are controllable meaning only users who have subscribed or are allowed can see the posts and comment. Unlike emails, new members added into the group can view all the previous discussion and content happened in that particular chat room.
Persistent Chat Features
Let’s go through some of the notable features provided by Persistent Chat :
- Assist communication with user irrespective of their geographic position.
- Provide a controlled environment for chats ad group discussions with teams.
- Makes it easy for the dispersed parts/teams of the organization to correspond with each other despite of the language and time zone difference.
- Decrease information overload and increase information awareness.
- Allows a simple and easy upgrade from Group Chat.
- Requires a single client for end user unlike the Group Chat which required two clients for working and managing.
- Similar to any other server role, Persistent Chat is also made as specific server role, which is why it has been added into the Lync 2013 via Topology builder.
- Persistent Chat provides high availability and resultantly lower redundancy.
Persistent Chat Working
A key point to be noted Persistent Chat services run over a devoted pool. This pool entirely depends on the pool of Lync Server in order to direct messages to Lync who have participated in a discussion. Communication between Lync clients and the Persistent Chat services is done via XCOOS – Extensible Chat Communication Over SIP.
Below is the highlight of the process when a client signs into Persistent Chat:
Lync client takes necessary authorization, using in-band provisioning, from Lync Server’13 – which in return let the client know by a response, whether the client is allowed to sign in or not into the persistent chat pool.
Once allowed, Lync client makes a contact with the Persistent Chat server to get a list of chat rooms that user is allowed to enter in. If Lync client wishes to take part in a particular chat room, client can send a message asking for permission to join in. Simple as that.