Abstract: In one embodiment, a user may transfer a multimodal conversation. A multimodal conversation may have a first mode communication session and a second mode communication session. A first user point of presence may execute a first transfer of the first mode communication session with a first partner point of presence from the first user point of presence to a first target point of presence. A second user point of presence may execute a second transfer of the second mode communication session with a second partner point of presence from the second user point of presence to a second target point of presence.

Abstract: A client-side signaling mechanism that allows a client to control how a telephone call is handled on a call server. The client user can create call routing rules on the client device using a client control component that manages session protocol messages. Once created, the call routing rule(s) created on the client are transmitted to the call server where a call routing component of the call server processes the rule(s) for a call related to the client. When the server receives the rule(s) and determines that the rule(s) are related to an existing call (incoming or currently in-process), the server halts current normal server rules processing for that call and executes the client-created rule(s). In one example, SIP session messages are employed for client control of server-side call forwarding.

Abstract: Context-based call routing is provided in a unified communication system by enabling subscribers to define a routing document, which is published by the communication system to callers who subscribe to a presence of the called party. Through publication of the context-based routing information, callers are enabled to make selections between call destination options as defined by the caller and provide a subject for the requested call. The call is then routed by the system according to the caller selection allowing efficient facilitation of the communication between the caller and the called party or their designees.

Abstract: A presence aggregation system provides a presence server that allows users to publish information regarding their availability with the presence server. The presence server maintains a record of each user's published information. When an endpoint publishes information regarding a user's availability at that endpoint with the presence server, the presence server provides all of the user's published information, including the information just published, to each of the user's endpoints, including the endpoint which published the information. This allows each of the user's endpoints to generate an aggregated availability of the user. The presence server may also provide all of the user's published information, including the information just published, to each of the subscribing users' endpoints. This allows the subscribing users to also generate a view of the user's aggregated availability.

Abstract: Providing non-voice capabilities relating to a phone call at a computing device includes receiving a request to begin a telephone call from a first telephone to a second telephone, wherein the requesting is performed using messaging between computing devices connected via a computer network, and wherein the messaging is part of a signaling phase dialog. The signaling phase dialog may be used in providing information associated with the identity of parties of the telephone call. Commencing a call phase dialog between the computing devices may be performed after the telephone call is established over the public switched telephone network. The call phase dialog may allow messages relating to the telephone call to be passed between the computing devices, at least while the telephone call is in progress. The dialogs and messaging may be performed using session initiation protocol (SIP) or another computer communication protocol.

Abstract: Contacts lists are dynamically managed in association with communication and collaboration applications and devices. Automated and user defined factors are determined based on information from various resources such as user profile, contact information, past communication information, application/device types, and comparable ones. Factors may be weighted and employed to prioritize contacts lists under different circumstances. Prioritized contacts lists may be provided to a user, stored, updated, or otherwise processed.

Abstract: A facility for integrating data in conversations is provided. In various embodiments, the facility sends a first message to a responding computing device to begin a conversation, receives a second message associated with the conversation from the responding computing device, determines whether the received message contains an indication of data that is to be associated with the conversation and, when the received message contains an indication of data that is to be associated with the conversation, renders the data. The facility can comprise an application server that receives from an initiator a first message associated with a conversation and responds to received messages, a conversation component that handles messages associated with the conversation, and an integration component that determines whether there is data that is to be associated with the conversation and, if so, adds an indication of the data to a second message that it sends to the initiator.

Abstract: Techniques for transfer error recovery are described. A system may comprise a context generator module operative to record context information for a first call session between a first call terminal and a call system resource, and store the context information with a context identifier in a context table. The system may include a transfer error context module to couple to the context generator module, the transfer error context module operative to generate transfer error context information having the context identifier. The system may include a call transfer module to couple to the transfer error context module, the call transfer module operative to send the transfer error context information to the first call terminal for use in case of a transfer failure event. Other embodiments are described and claimed.

Abstract: The claimed subject matter provides a system and/or a method that facilitates authenticating a data communication. An interface component can receive data related to a real time data communication between two or more clients. A verification component can employ a human interaction proof (HIP) to a client participating within the real time data communication, wherein a human identity of the client is authenticated as a function of a response to the HIP.

Abstract: A call forwarding system forwards telephone calls based on presence information of a user as reported by computing devices associated with a telephone number. When a telephone system receives an incoming call directed to one of the telephone numbers of the user's computing devices, it sends an incoming call event to each computing device. Upon receiving the incoming call event from a telephone system, each computing device determines whether the user is most likely present at that computing device based on the presence information. When a computing device determines that the user is most likely present at that computing device, it sends a notification to the telephone system to forward the incoming call to the telephone number associated with that computing device to effect the automatic forwarding of a call based on presence information.

Abstract: Multiple instances of an incoming call in an integrated system capable of communicating through multiple networks are associated such that the called party is provided a single (merged) notification along with options to select among available call types. The call is established using a selected network and end device registered to the called user. Association of the instances is accomplished by comparing caller identity derived from a variety of information associated with the calling party. Conversation or correlation IDs are used to associate the instances as being for the same call and with other related communications such as a related instant messaging session.

Abstract: Techniques for transfer error recovery are described. A system may comprise a context generator module operative to record context information for a first call session between a first call terminal and a call system resource, and store the context information with a context identifier in a context table. The system may include a transfer error context module to couple to the context generator module, the transfer error context module operative to generate transfer error context information having the context identifier. The system may include a call transfer module to couple to the transfer error context module, the call transfer module operative to send the transfer error context information to the first call terminal for use in case of a transfer failure event. Other embodiments are described and claimed.

Abstract: A method and system for providing context of a caller to a callee when a call is initiated is provided. The context system executing on the calling device collects context for the call. The calling device initiates the call and sends a message to the callee that includes the context. Upon receiving the message, the callee device notifies the caller that a call has been initiated and displays the received context. The callee can decide based on the received context whether to answer the call or not answer the call.

Abstract: Techniques for transfer error recovery are described. A system may comprise a context generator module operative to record context information for a first call session between a first call terminal and a call system resource, and store the context information with a context identifier in a context table. The system may include a transfer error context module to couple to the context generator module, the transfer error context module operative to generate transfer error context information having the context identifier. The system may include a call transfer module to couple to the transfer error context module, the call transfer module operative to send the transfer error context information to the first call terminal for use in case of a transfer failure event. Other embodiments are described and claimed.

Abstract: Providing non-voice capabilities relating to a phone call at a computing device includes receiving a request to begin a telephone call from a first telephone to a second telephone, wherein the requesting is performed using messaging between computing devices connected via a computer network, and wherein the messaging is part of a signaling phase dialog. The signaling phase dialog may be used in providing information associated with the identity of parties of the telephone call. Commencing a call phase dialog between the computing devices may be performed after the telephone call is established over the public switched telephone network. The call phase dialog may allow messages relating to the telephone call to be passed between the computing devices, at least while the telephone call is in progress. The dialogs and messaging may be performed using session initiation protocol (SIP) or another computer communication protocol.

Abstract: Providing non-voice capabilities relating to a phone call at a computing device includes receiving a request to begin a telephone call from a first telephone to a second telephone, wherein the requesting is performed using messaging between computing devices connected via a computer network, and wherein the messaging is part of a signaling phase dialog. The signaling phase dialog may be used in providing information associated with the identity of parties of the telephone call. Commencing a call phase dialog between the computing devices may be performed after the telephone call is established over the public switched telephone network. The call phase dialog may allow messages relating to the telephone call to be passed between the computing devices, at least while the telephone call is in progress. The dialogs and messaging may be performed using session initiation protocol (SIP) or another computer communication protocol.

Abstract: Contacts lists are dynamically managed in association with communication and collaboration applications and devices. Automated and user defined factors are determined based on information from various resources such as user profile, contact information, past communication information, application/device types, and comparable ones. Factors may be weighted and employed to prioritize contacts lists under different circumstances. Prioritized contacts lists may be provided to a user, stored, updated, or otherwise processed.

Abstract: A presence aggregation system provides a presence server that allows users to publish information regarding their availability with the presence server. The presence server maintains a record of each user's published information. When an endpoint publishes information regarding a user's availability at that endpoint with the presence server, the presence server provides all of the user's published information, including the information just published, to each of the user's endpoints, including the endpoint which published the information. This allows each of the user's endpoints to generate an aggregated availability of the user. The presence server may also provide all of the user's published information, including the information just published, to each of the subscribing users' endpoints. This allows the subscribing users to also generate a view of the user's aggregated availability.

Abstract: A presence aggregation system provides a presence server that allows users to publish information regarding their availability with the presence server. The presence server maintains a record of each user's published information. When an endpoint publishes information regarding a user's availability at that endpoint with the presence server, the presence server provides all of the user's published information, including the information just published, to each of the user's endpoints, including the endpoint which published the information. This allows each of the user's endpoints to generate an aggregated availability of the user. The presence server may also provide all of the user's published information, including the information just published, to each of the subscribing users' endpoints. This allows the subscribing users to also generate a view of the user's aggregated availability.

Abstract: The present invention comprises a system and methods for facilitating third-party call control using a peer-to-peer configuration with SIP.