presentity

A presentity is a network entity, typically a user or device, that publishes its real-time availability and willingness to communicate. In telecommunications systems, the presentity is the source of presence information: it tells the network "I am here, online, and available" or "I am away" or "do not disturb." The presence data flows from the presentity through a presence server to watchers, who subscribe to know that status. Without a presentity generating the signal, there is nothing for the presence infrastructure to distribute.

The term comes from Session Initiation Protocol (SIP) presence extensions, standardized in RFC 3856 and related specifications. In a SIP-based system, a presentity publishes its state by sending PUBLISH requests to a presence agent. That agent then notifies any subscriber (called a watcher) who has asked to be told when that presentity's status changes. A single human user might act as one presentity, but a person with multiple devices (desk phone, mobile, softphone, instant messaging client) can be represented by multiple presentities, each reporting its own availability.

Presence information includes more than just "online" or "offline." A presentity can report its current activity, location, or communication preference: available, away, busy, in a meeting, on the phone, or do-not-disturb. Some systems integrate calendar data, location services, or device state; a presentity might automatically set itself to "in a meeting" based on calendar entries, or to "busy" when the device detects an active call. This contextual data helps watchers (colleagues, managers, automated systems) decide whether and how to initiate contact.

Practical Implementation and Constraints

In practice, a presentity is implemented as a user agent or a process running on behalf of the user. A SIP desk phone is a presentity. A mobile app that reports its network connectivity and user activity is a presentity. Even a voicemail system or an auto-responder can act as a presentity, publishing that the user is unavailable and suggesting an alternative contact method. The presence server holds the presentity's data and refreshes it; if a presentity stops sending updates (no PUBLISH message within the subscription lifetime, typically 3600 seconds), its status expires and is removed.

The distinction between presentity and watcher is strict: a presentity publishes, a watcher subscribes. However, a single user agent often plays both roles simultaneously. Your desk phone publishes your availability to the system and also subscribes to the availability of your colleagues, so you can see who is online. This dual role does not change the terminology; the phone is a presentity for its own status and a watcher for others' status.

Reliability of presence data depends on the presentity's willingness and ability to update. A user who manually sets their status as away but remains at their desk creates stale presence information. Presence systems often include activity detection (keyboard, mouse, touch input) or network monitoring to refresh the presentity's state automatically. Enterprise systems may enforce expiration policies, automatically moving a presentity to offline status if no update is received, reducing the chance that presence data misleads a caller into attempting to reach someone who is no longer available.