Presence and Instant Messaging for Efficient Collaboration

Author

Reads 12K

Muslim ethnic female in hijab texting message on mobile phone near iron construction on blurred background of building
Credit: pexels.com, Muslim ethnic female in hijab texting message on mobile phone near iron construction on blurred background of building

Having a team's presence and instant messaging in one place can save up to 2.5 hours per week in meetings and email threads.

With instant messaging, teams can reduce meeting times by up to 30%. This allows for more focused work and increased productivity.

Instant messaging can also reduce email volume by up to 40%, making it easier to manage and respond to messages.

Instant Messaging

Instant messaging is a crucial aspect of presence and instant messaging. It allows users to communicate with each other in real-time, sending messages, files, and even participating in voice and video calls.

Instant messaging protocols like XMPP and SIP are being considered for use on the internet, but no work has been done on the PRIM protocol since 2001. This is likely due to the fact that newer protocols have been developed and adopted by industry leaders.

XMPP makes it relatively straightforward to exchange presence information by using presence stanzas, which can be sent from a client to its server and then broadcasted to other entities subscribed to the presence of the sending entity.

If this caught your attention, see: Instant Web Traffic

Credit: youtube.com, Skype for Business Overview Using Presence and Instant Messaging

In addition to core server compliance requirements, an instant messaging and presence server MUST support protocols for presence broadcast, subscriptions, roster storage, and manipulation, as well as privacy lists and IM-specific routing and delivery rules.

The IMP service enables users to observe the presence status of other authenticated users and provides instant access to interaction options like instant messages, mail, and phone conferences. Users can also send mail, view profiles, send instant messages, and initiate phone conferences from the presence icon menu.

Cisco Unified Presence technology has been integrated with Cisco Unified Communications Manager for Release 9.0 and later, providing features and capabilities like presence awareness, instant messaging, and group chat. This integration allows users to facilitate faster decision-making and enhance productivity.

Here are some key features and capabilities of Cisco Unified Presence:

  • Presence awareness to view the availability of colleagues and reduce communications delays
  • Instant messaging with partners and customers in other organizations
  • Support for both SIP/SIMPLE and XMPP on a single software appliance
  • Enhanced enterprise IM capabilities like group chat, persistent chat, and IM logging
  • Compliance with regulatory requirements

Productivity and Collaboration

Cisco Unified Presence is a standards-based enterprise platform that brings people together in and across organizations in the most effective way.

This open and extensible platform facilitates the highly secure exchange of presence and instant messaging (IM) information between Cisco Unified Communications and other applications.

By using presence, you can enhance collaboration and make communication more efficient.

Enhance Productivity and Collaboration

Credit: youtube.com, Maximize Team Productivity with AI Collaboration

Cisco Unified Presence is a standards-based enterprise platform that brings people together in and across organizations in the most effective way.

This platform facilitates the highly secure exchange of presence and instant messaging (IM) information between Cisco Unified Communications and other applications.

Cisco Unified Presence is open and extensible, allowing for seamless integration with various applications and systems.

By using Cisco Unified Presence, you can enhance collaboration and productivity by facilitating the exchange of presence and IM information between team members and departments.

This platform supports and enhances the ways we communicate and collaborate, making it easier to work together and achieve common goals.

Sending a Mail

You can send a mail message to a user associated with a Presence icon.

Click the Presence icon for the user you want to contact, and a menu will appear.

Choose Send Mail from the menu. If you're prompted for a login window, enter your user name and password for your mail application.

If your preferences are set up to deliver your login credentials automatically, you can start composing your message right away.

To compose your message, click Send.

Start Phone Conference from Menu

Credit: youtube.com, ChoiceTel Conferencing Solutions

To start a phone conference from the menu, you can initiate a call with another user by clicking the Presence icon associated with them. This icon can be found in various places, such as the Buddies task flow in the Sidebar, or associated with documents and discussion topics.

The Presence icon is a key part of this process, and it's used to initiate a call to the target user. For example, if you see a Presence icon associated with the user "monty", you can click on it to start the process.

To initiate a phone conference, follow these steps:

  1. Click the Presence icon associated with the user you want to contact.
  2. From the menu, choose Start Phone Conference.

This will place a call to you and then to the target user, using the phone numbers specified in the user profiles. If you encounter an error, make sure that user names are in lowercase, as this can sometimes cause issues.

Archiving IM Content

Archiving IM content is a must-have for organizations with compliance regulations to follow. You can use Archiving to archive the content of IM messages for all users in your organization or for only certain users that you specify.

Credit: youtube.com, Web Archiving Collaboration 1: New Tools and Models

If you have Microsoft Exchange Server 2013 deployed, you can integrate the archiving of Exchange data with the archiving of Skype for Business Server data, and use a single tool to search both types of archived data.

Skype for Business Server provides features to help you manage and search archived content. For more information, see Plan for archiving in Skype for Business Server.

Session Establishment

Session establishment is a crucial aspect of presence and instant messaging. In the Jabber community, the client-to-server authentication protocol assumed every client is an IM client and initiated an IM session upon successful authentication and resource binding.

However, XMPP maintains a stricter separation between core functionality and IM functionality, so an IM session is not created until the client specifically requests one using the protocol defined under Session Establishment. This approach allows for more flexibility and control over session management.

The client must explicitly request an IM session, which is a key difference between the Jabber community's approach and XMPP's. This ensures that the client is aware of and agrees to the session establishment, promoting a more secure and user-friendly experience.

Session Establishment

Credit: youtube.com, RPC Session Establishment - Georgia Tech - Advanced Operating Systems

Session Establishment is a crucial aspect of the Jabber community's client-to-server authentication protocol. This protocol assumes every client is an IM client and initiates an IM session upon successful authentication and resource binding, performed simultaneously.

The Jabber Software Foundation documents this protocol in [JEP‑0078] (Saint-Andre, P., “Non-SASL Authentication,” July 2004). XMPP, on the other hand, maintains a stricter separation between core functionality and IM functionality.

In XMPP, an IM session is not created until the client specifically requests one using the protocol defined under Session Establishment. This means that clients have more control over when they establish a session, unlike the Jabber community's protocol.

5.1.1. Initial

After establishing a session, a client SHOULD send initial presence to the server in order to signal its availability for communications. Initial presence is sent as a stanza with no 'to' address and no 'type' attribute.

The client's server must send presence probes to all contacts to which the user is subscribed, if there are no already available resources for the user. This is done to determine if they are available.

View of Communications Tower Against Cloudy Sky
Credit: pexels.com, View of Communications Tower Against Cloudy Sky

The server must also broadcast initial presence from the full JID of the user to all contacts that are subscribed to the user's presence information.

In addition, the server must broadcast initial presence from the user's new available resource to any of the user's existing available resources.

Here's a summary of the server's actions:

  • Send presence probes to subscribed contacts
  • Broadcast initial presence to subscribed contacts
  • Broadcast initial presence to existing available resources

SRV Protocol Label Registration

The Instant Messaging SRV Protocol Label registry is defined in the Address Resolution for Instant Messaging and Presence document, which was published in August 2004.

This registry is used to register protocols that can provide services conforming to the "_im" SRV Service label, such as XMPP. The IANA registers the "_xmpp" protocol label in this registry.

The Presence SRV Protocol Label registry is also defined in the same document, which is used to register protocols that can provide services conforming to the "_pres" SRV Service label, such as XMPP. The IANA registers the "_xmpp" protocol label in this registry as well.

Broaden your view: Azure Messaging

Roster Management

Credit: youtube.com, Microsoft Lync - Instant Messaging & Presence Management

In XMPP, one's contact list is called a roster, which consists of any number of specific roster items, each identified by a unique JID.

A user's roster is stored by the user's server on the user's behalf, so they can access roster information from any resource.

A user MAY add an item to their roster at any time, and the server MUST update the roster information in persistent storage and push the change out to all available resources that have requested the roster.

The server initiates a "roster push" by sending an IQ stanza of type "set" to the client, which enables all available resources to remain in sync with the server-based roster information.

Each resource that received the roster push MUST reply with an IQ stanza of type "result" (or "error").

When a user updates a roster item, the server MUST update the roster information in persistent storage and initiate a roster push to all available resources that have requested the roster.

Take a look at this: Update Text Messages

Credit: youtube.com, Lync Presence, IM, and Contacts in Lync 2013 Instant messaging Video 3 of 4

A user MAY delete an item from their roster by sending an IQ set to the server and making sure the 'subscription' attribute is set to "remove".

The server MUST update the roster information in persistent storage, initiate a roster push to all available resources that have requested the roster, and send an IQ result to the initiating resource.

Removing a roster item and cancelling all subscriptions involves sending a roster set containing an item for the contact with the 'subscription' attribute set to "remove".

Business Rules and Compliance

A server must ignore any 'to' address on a roster "set" and treat any roster "set" as applying to the sender.

When it comes to receiving roster pushes, clients should check the "from" address to ensure it's from a trusted source. Specifically, the stanza must either have no 'from' attribute or have a 'from' attribute whose value matches the user's bare JID or full JID.

If a roster push doesn't meet these criteria, the client should ignore it.

Business Rules

Close-up of hands typing on a digital tablet with messaging app in bed.
Credit: pexels.com, Close-up of hands typing on a digital tablet with messaging app in bed.

Business rules are essential for ensuring compliance in various contexts. A server MUST ignore any 'to' address on a roster "set".

In some cases, a client SHOULD check the "from" address of a "roster push" to ensure it's from a trusted source. Specifically, the stanza MUST either have no 'from' attribute or have a 'from' attribute whose value matches the user's bare JID.

Ignoring the 'to' address on a roster "set" helps prevent potential issues with roster management. A server MUST treat any roster "set" as applying to the sender.

For added safety, clients SHOULD ignore the "roster push" if the 'from' attribute doesn't match the user's bare or full JID. This helps prevent unauthorized roster changes.

Im Compliance Requirements

IM Compliance Requirements are crucial for instant messaging and presence servers and clients to be considered compliant implementations. They MUST comply with the requirements specified in [XMPP‑CORE] (Saint-Andre, P., “Extensible Messaging and Presence Protocol (XMPP): Core,” October 2004.).

Woman typing on a laptop using a messaging app in a home setting, close-up of hands.
Credit: pexels.com, Woman typing on a laptop using a messaging app in a home setting, close-up of hands.

Additional compliance requirements for instant messaging and presence servers and clients are specified in this section. These requirements supplement the core requirements.

A server or client MAY support only presence or instant messaging, but it is not required to support both if only a presence service or an instant messaging service is desired.

Core Details and Features

The IMP service is a powerful tool for staying connected with colleagues and clients. It enables you to observe the presence status of other authenticated users, including their online, offline, busy, or away status.

You can see an icon depicting the presence state of a user wherever they are mentioned, such as in a document library. Hovering over the icon displays a tooltip with the user's current status message, if available.

The IMP service allows you to send mail, view a user's profile, send an instant message, initiate a phone conference, or change credentials. The options available on the context menu depend on the services available to your WebCenter Spaces application and the presence server.

Credit: youtube.com, Skype for Business Overview Using Presence and Instant Messaging

You can make contact with other users directly from within the context of a discussion topic or other WebCenter task flows. This feature is particularly useful for quickly reaching out to colleagues or clients.

Here are some key features of the IMP service:

  • Sending mail to a user
  • Viewing a user's profile
  • Sending an instant message to a user
  • Initiating a phone conference with a user
  • Changing credentials (available with Microsoft Office Live Communications Server)

Note that the options available on the context menu depend on the services available to your WebCenter Spaces application and the presence server.

User Interface and Experience

A good user interface can make or break the experience of using instant messaging apps.

Presence indicators, like the "Away" and "Busy" statuses, help users understand when their contacts are available to chat.

These indicators are usually displayed in a user's contact list, making it easy to see who's available and who's not.

The design of the contact list is crucial, as it should be easy to navigate and understand at a glance.

For example, the article mentions that the popular messaging app, WhatsApp, uses a simple and intuitive contact list design.

Credit: youtube.com, Presence and Instant Messaging

Instant messaging apps often include features like typing indicators and read receipts to enhance the user experience.

These features provide users with a sense of engagement and help them feel more connected to their contacts.

However, users should be mindful of their own presence status, as it can affect how others perceive them.

A consistent and clear presence status can help build trust and rapport with others.

Technical Requirements and Topologies

To set up instant messaging and presence, you'll need to meet some technical requirements. Instant messaging and presence always run on Enterprise Edition Front End pools and Standard Edition servers. For more information on supported hardware, operating systems, and database software, see Certified Gateways, Requirements for your Skype for Business 2015 environment, and Infrastructure requirements for Skype for Business Server 2019.

The only components required for instant messaging and presence are your organization's Front End servers (known as a pool) or a Standard Edition server. IM and presence capabilities are always enabled on these servers. A load balancer is also required if you have an Enterprise Edition Front End pool.

Here's a summary of the required components:

  • Front End servers (pool) or Standard Edition server
  • Load balancer (if using Enterprise Edition Front End pool)

Requirements

Credit: youtube.com, Network Topology

To be considered a basic instant messaging and presence application, a user must be able to complete several key use cases.

These use cases include exchanging messages with other users, exchanging presence information with other users, managing subscriptions to and from other users, managing items in a contact list, and blocking communications to or from specific other users.

A user must be able to exchange messages with other users, which is a fundamental requirement of any instant messaging and presence application.

Exchanging presence information with other users is also a crucial requirement, allowing users to see the availability of their contacts.

Managing subscriptions to and from other users is another important requirement, enabling users to control who can see their presence information and who can initiate conversations with them.

Managing items in a contact list, also known as a roster, is a key requirement for instant messaging and presence applications, allowing users to organize their contacts and see their presence information.

Credit: youtube.com, Topology

Blocking communications to or from specific other users is also a requirement, giving users control over who can contact them and who they can contact.

The protocol makes it possible to offer separate and distinct services for presence and for instant messaging, so a service must not necessarily offer both.

Here is a summary of the key use cases:

  • Exchange messages with other users
  • Exchange presence information with other users
  • Manage subscriptions to and from other users
  • Manage items in a contact list (roster)
  • Block communications to or from specific other users

Technical Requirements

Instant messaging (IM) and presence always run on Enterprise Edition Front End pools and Standard Edition servers.

For Enterprise Edition Front End pools, Skype for Business 2015 requires a specific setup, but details can be found in Certified Gateways.

Instant messaging (IM) and presence are supported on Standard Edition servers, which is a more straightforward option.

For information on supported hardware, operating systems, and database software, see Certified Gateways, Requirements for your Skype for Business 2015 environment, and Infrastructure requirements for Skype for Business Server 2019.

Topologies and Components

To set up instant messaging (IM) and presence, you'll need a few key components. Your organization's Front End servers, also known as a pool, are required. These servers always have IM and presence capabilities enabled.

Credit: youtube.com, NETWORK TOPOLOGY

For a Standard Edition server, you're good to go with just the Front End pool. However, if you're using an Enterprise Edition Front End pool, you'll also need a load balancer to manage the traffic.

Here are the specific components you'll need:

  • Front End servers (pool)
  • Standard Edition server (no additional components needed)
  • Enterprise Edition Front End pool (requires a load balancer)

Frequently Asked Questions

What are the two types of instant messaging?

There are two main types of instant messaging: application-based and web-based. Application-based software is downloaded and installed on a user's computer, while web-based software is accessed through a web browser.

Viola Morissette

Assigning Editor

Viola Morissette is a seasoned Assigning Editor with a passion for curating high-quality content. With a keen eye for detail and a knack for identifying emerging trends, she has successfully guided numerous articles to publication. Her expertise spans a wide range of topics, including technology and software tutorials, such as her work on "OneDrive Tutorials," where she expertly assigned and edited pieces that have resonated with readers worldwide.

Love What You Read? Stay Updated!

Join our community for insights, tips, and more.