Abstract: An exemplary embodiment builds on the idea of presence and SIP messaging in conjunction with a profile comprising, for example, a lookup table and a rules module, to assist with one or more of reminders, actions, endpoint maintenance, availability, endpoint capabilities and session management. One exemplary embodiment provides a message-based notification system. SIP allows a user to associate themselves with a number of different User Agents (UAs). This means that a user may have a presence on more than one UA at any given time, e.g., soft phone, PDA, and workstation. One exemplary embodiment utilizes this fact in connection with monitoring and determining if a message is a trigger-type message to provide more timely and relevant notifications to users.

Abstract: Described are embodiments that provide for an intelligent call log. Specifically, in embodiments, a call log module can be provided on a user's phone (or as a sequenced application) that analyzes the actual communications between a calling party and a called party. The call log module is configured, in embodiments, to do analysis of the calling party's interaction with the called party, changes in routing, and/or failure to connect. The call log module is linked to the calling party's schedule information, in some embodiments, for situations with multiple failures to connect and/or multiple short discussions have inadequately dealt with the need to talk, and therefore scheduling a meeting is likely to be more effective.

Abstract: Mechanisms are provided herein which accommodate the sharing of a user device among multiple users. In particular, when multiple users are detected as sharing a user device, the user interface of the user device can be automatically altered to facilitate the sharing of the user device. Data associated with each sharing user may also be presented according to each user's presentation preferences and to accommodate presentation needs of each user.

Abstract: Described are embodiments that provide for an intelligent call log. Specifically, in embodiments, a call log module can be provided on a user's phone (or as a sequenced application) that analyzes the actual communications between a calling party and a called party. The call log module is configured, in embodiments, to do analysis of the calling party's interaction with the called party, changes in routing, and/or failure to connect. The call log module is linked to the calling party's schedule information, in some embodiments, for situations with multiple failures to connect and/or multiple short discussions have inadequately dealt with the need to talk, and therefore scheduling a meeting is likely to be more effective.

Abstract: Mechanisms are provided herein which accommodate the sharing of a user device among multiple users. In particular, when multiple users are detected as sharing a user device, the user interface of the user device can be automatically altered to facilitate the sharing of the user device. Data associated with each sharing user may also be presented according to each user's presentation preferences and to accommodate presentation needs of each user.

Abstract: An exemplary embodiment builds on the idea of presence and SIP messaging in conjunction with a profile comprising, for example, a lookup table and a rules module, to assist with one or more of reminders, actions, endpoint maintenance, availability, endpoint capabilities and session management. One exemplary embodiment provides a message-based notification system. SIP allows a user to associate themselves with a number of different User Agents (UAs). This means that a user may have a presence on more than one UA at any given time, e.g., soft phone, PDA, and workstation. One exemplary embodiment utilizes this fact in connection with monitoring and determining if a message is a trigger-type message to provide more timely and relevant notifications to users.