Abstract:
In one embodiment, a user paired controller communication device may pair with a user paired server communication device. The user paired controller communication device may direct the user paired server communication device to execute a first mode communication session of a multimodal conversation, such as a voice session. The user paired controller communication may execute a second mode communication session of the multimodal conversation, such as an instant messaging session.
Abstract:
Communication requests added to a conversation are routed directly to a user without following the pre-configured routing rules for the user during a breakthrough period. The breakthrough period may last for the duration of the conversation or for some other period of time. A conversation may be initiated using any supported type of communication. For example, if a user initially sets up an IM conversation with a remote user, then when a voice call is made to the user from the remote user, the voice call is routed directly to the user without applying the routing rules that are configured for the user. Once the breakthrough period has elapsed, the routing rules become active again and are applied to communications received from the remote user that are directed to the user.
Abstract:
In one embodiment, a user paired controller communication device may pair with a user paired server communication device. The user paired controller communication device may direct the user paired server communication device to execute a first mode communication session of a multimodal conversation, such as a voice session. The user paired controller communication may execute a second mode communication session of the multimodal conversation, such as an instant messaging session.
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:
Multiple instances of an incoming call in a unified communication system capable of communicating through multiple networks are provided to devices and/or applications associated with the called party. Upon acceptance or a global rejection of the incoming call through one of the end devices/applications, the remainder are provided a cancellation notice for the forked call request that includes information associated with which end device took the action, what type of action was taken, whether the action was based on automatic policy implementation.
Abstract:
Multiple instances of an incoming call in a unified communication system capable of communicating through multiple networks are provided to devices and/or applications associated with the called party. Upon acceptance or a global rejection of the incoming call through one of the end devices/applications, the remainder are provided a cancellation notice for the forked call request that includes information associated with which end device took the action, what type of action was taken, whether the action was based on automatic policy implementation.
Abstract:
Architecture for enabling identification of a call party's representative during calls on behalf of the call party. The call representative is delegated to initiate or answer an IP call on behalf of the call party. An IP-telephony component initiates or answers the IP call by the call representative on behalf of the call party. The IP-telephony component can be an IP telephone, or any other suitable IP calling interface. An identification component presents a representation notification identifying the call representative to a connected call party. The representation notification can be displayed on a caller ID display on an IP phone, or can be displayed on a user interface of the personal computing device, for example. The calls can be point-to-point IP calls with a single participant, or can be conference calls with multiple participants, and can be performed with one or more suitable protocols.
Abstract:
Architecture for seamless role switching in application sharing. A multipoint control unit (MCU) can be used for connecting multiple clients over a network. An application sharing component establishes an application sharing session over the MCU, and application content is exchanged from a sharer client to one or more viewer clients. Each client can communicate a media connection preference to the session. Client sharer and viewer roles are defined during creation of the application sharing session. A client can seamlessly switch roles during the session from a viewer to a sharer, and vice-versa, so that different application content can be shared to the session viewers. The session can be restricted to only one sharer so that the viewing clients view one sharer client at a time.
Abstract:
Architecture for enabling identification of a call party's representative during calls on behalf of the call party. The call representative is delegated to initiate or answer an IP call on behalf of the call party. An IP-telephony component initiates or answers the IP call by the call representative on behalf of the call party. The IP-telephony component can be an IP telephone, or any other suitable IP calling interface. An identification component presents a representation notification identifying the call representative to a connected call party. The representation notification can be displayed on a caller ID display on an IP phone, or can be displayed on a user interface of the personal computing device, for example. The calls can be point-to-point IP calls with a single participant, or can be conference calls with multiple participants, and can be performed with one or more suitable protocols.
Abstract:
Multiple instances of an incoming call in a unified communication system capable of communicating through multiple networks are provided to devices and/or applications associated with the called party. Upon acceptance or a global rejection of the incoming call through one of the end devices/applications, the remainder are provided a cancellation notice for the forked call request that includes information associated with which end device took the action, what type of action was taken, whether the action was based on automatic policy implementation.