Abstract: A method is provided for detecting interactions between call-related and web-enabled features. In some embodiments, communication application components are configured to transmit an indication to a feature interaction detector every time a feature is invoked by the user. When the interaction detector receives an indication that a feature is being invoked, it compares the invoked feature against features that have previously been invoked (or executed) and determines whether the invoked feature interacts with any of the features that have been previously executed.

Abstract: Techniques for detecting and resolving feature interactions during calls are disclosed. In particular, a finite-state machine and a corresponding method detect when a feature that is invoked during a call would interact with another previously-activated feature, and ensure that both features are not active simultaneously. Three different techniques for resolution are disclosed: in one technique, activation of the latter feature is always refused; in a second technique, the former feature is always deactivated and the latter feature is then activated; and in a third technique, one of the two features is selected to be the active feature—perhaps based on priorities assigned to the features—and the features are activated and/or deactivated accordingly.

Abstract: A method is disclosed for detecting feature interactions in multi-party calls (i.e., calls involving more than two endpoints), and in calls with bridged appearances. In accordance with the illustrative embodiment, a set of rules is applied to the specifications of two features in order to detect interactions between the features. The rules specify conditions for, or relationships among, the original connections for the features, the resulting connections for the features, the triggering party for the features, and the originating and terminating parties of connections. A rule is considered matched for a multi-party call when any of the original and resulting connections for the call match the conditions of the rule. Similarly, a rule is considered matched for a call with one or more bridged appearances when any of the original and resulting connections for the call, including those of bridged appearances, match the conditions of the rule.

Abstract: Methods are disclosed for detecting feature interactions during a call that has a signaling path comprising two or more legs. In accordance with the illustrative embodiment, feature state information is maintained for each of the legs of the call and is propagated along the signaling path. The illustrative embodiment is capable of detecting interactions between features in different legs of a call, as well as interactions between features in the same leg of a call. Moreover, the illustrative embodiment is capable of accommodating a variety of feature resolution techniques. In one illustrative embodiment specific to Voice over Internet Protocol (VoIP) telephony, a Back-to-Back User Agent (B2BUA) stores and propagates the feature state information, and performs address mapping for two specially-defined headers in addition to the usual Session Initiation Protocol (SIP) headers.

Abstract: Disclosed herein are systems, methods, and non-transitory computer-readable storage media for communicating via a multi-model collaboration space. A system practicing the method first assigns a communication endpoint identifier to a multi-model collaboration space having at least one entity. The endpoint identifier can be a telephone, email address, IP address, or username, for example. The system receives an incoming communication addressed to the communication endpoint identifier, such as a telephone call or email, and transfers the incoming communication to at least one entity in the multi-model collaboration space. In one aspect, the multi-model collaboration space provides a shared persistent container where entities can perform collaboration activities. The entities can have unique identities. The entities can be humans and/or automated, non-human, system-owned entities. Entities can share their context-specific view of the multi-model collaboration space with other entities.

Abstract: A method is provided for detecting interactions between call-related and web-enabled features. In some embodiments, communication application components are configured to transmit an indication to a feature interaction detector every time a feature is invoked by the user. When the interaction detector receives an indication that a feature is being invoked, it compares the invoked feature against features that have previously been invoked (or executed) and determines whether the invoked feature interacts with any of the features that have been previously executed.

Abstract: A method is disclosed for detecting feature interactions in multi-party calls (i.e., calls involving more than two endpoints), and in calls with bridged appearances. In accordance with the illustrative embodiment, a set of rules is applied to the specifications of two features in order to detect interactions between the features. The rules specify conditions for, or relationships among, the original connections for the features, the resulting connections for the features, the triggering party for the features, and the originating and terminating parties of connections. A rule is considered matched for a multi-party call when any of the original and resulting connections for the call match the conditions of the rule. Similarly, a rule is considered matched for a call with one or more bridged appearances when any of the original and resulting connections for the call, including those of bridged appearances, match the conditions of the rule.

Abstract: Techniques for detecting and resolving feature interactions during calls are disclosed. In particular, a finite-state machine and a corresponding method detect when a feature that is invoked during a call would interact with another previously-activated feature, and ensure that both features are not active simultaneously. Three different techniques for resolution are disclosed: in one technique, activation of the latter feature is always refused; in a second technique, the former feature is always deactivated and the latter feature is then activated; and in a third technique, one of the two features is selected to be the active feature—perhaps based on priorities assigned to the features—and the features are activated and/or deactivated accordingly.

Abstract: Methods are disclosed for detecting feature interactions during a call that has a signaling path comprising two or more legs. In accordance with the illustrative embodiment, feature state information is maintained for each of the legs of the call and is propagated along the signaling path. The illustrative embodiment is capable of detecting interactions between features in different legs of a call, as well as interactions between features in the same leg of a call. Moreover, the illustrative embodiment is capable of accommodating a variety of feature resolution techniques. In one illustrative embodiment specific to Voice over Internet Protocol (VoIP) telephony, a Back-to-Back User Agent (B2BUA) stores and propagates the feature state information, and performs address mapping for two specially-defined headers in addition to the usual Session Initiation Protocol (SIP) headers.