Abstract: A videoconferencing system includes a hybrid MCU configured to act as a hybrid mesh participant in a videoconference. The hybrid MCU may include a processing module to mix videoconference media data received by the hybrid MCU in data streams transmitted from mesh and non-mesh endpoints. The hybrid MCU may further include a forking module to fork combined video/audio data streams received by the hybrid MCU to provide separate video and audio data streams to each mesh endpoint. The hybrid MCU may be configured to provide a mixed video/audio data steam to each non-mesh endpoint of the videoconference.

Abstract: According to one example, a system includes one or more memory units configured to store one or more instructions, and one or more processors coupled to the memory units. The processors are configured, upon executing the one or more instructions, to receive, based on one or more Session Initiation Protocol Recording (SIPREC) messages, media associated with a communication session between a caller and a call recipient. The processors are further configured to transmit, in real-time to a third party, the media associated with the communication session between the caller and the call recipient.

Abstract: A videoconferencing system includes a hybrid MCU configured to act as a hybrid mesh participant in a videoconference. The hybrid MCU may include a processing module to mix videoconference media data received by the hybrid MCU in data streams transmitted from mesh and non-mesh endpoints. The hybrid MCU may further include a forking module to fork combined video/audio data streams received by the hybrid MCU to provide separate video and audio data streams to each mesh endpoint. The hybrid MCU may be configured to provide a mixed video/audio data steam to each non-mesh endpoint of the videoconference.

Abstract: A videoconferencing system includes a hybrid MCU configured to act as a hybrid mesh participant in a videoconference. The hybrid MCU may include a processing module to mix videoconference media data received by the hybrid MCU in data streams transmitted from mesh and non-mesh endpoints. The hybrid MCU may further include a forking module to fork combined video/audio data streams received by the hybrid MCU to provide separate video and audio data streams to each mesh endpoint. The hybrid MCU may be configured to provide a mixed video/audio data steam to each non-mesh endpoint of the videoconference.

Abstract: A videoconferencing system includes a hybrid MCU configured to act as a hybrid mesh participant in a videoconference. The hybrid MCU may include a processing module to mix videoconference media data received by the hybrid MCU in data streams transmitted from mesh and non-mesh endpoints. The hybrid MCU may further include a forking module to fork combined video/audio data streams received by the hybrid MCU to provide separate video and audio data streams to each mesh endpoint. The hybrid MCU may be configured to provide a mixed video/audio data steam to each non-mesh endpoint of the videoconference.

Abstract: A method of conferencing participant video data and audio data includes switching from a mesh-based conference to an MCU-based conference upon the occurrence of a trigger event. The mesh-based conference includes transmitting separate video and audio data streams between endpoints, and the MCU-based conference includes transmitting single video/audio data from endpoints to an MCU and combined video/audio data streams from the MCU to the endpoints.

Abstract: A videoconferencing system includes a hybrid MCU configured to act as a hybrid mesh participant in a videoconference. The hybrid MCU may include a processing module to mix videoconference media data received by the hybrid MCU in data streams transmitted from mesh and non-mesh endpoints. The hybrid MCU may further include a forking module to fork combined video/audio data streams received by the hybrid MCU to provide separate video and audio data streams to each mesh endpoint. The hybrid MCU may be configured to provide a mixed video/audio data steam to each non-mesh endpoint of the videoconference.

Abstract: A system for monitoring and analyzing application data to offer assistance is disclosed. In particular, the system may monitor and track a user's usage of a selected software application. Based on the monitoring and tracking, the system may determine if the usage of the application triggers a rule associated with the application. If the usage of the application is determining to trigger the rule, the system may determine that the user of the application needs assistance with the application or otherwise. If the user is determined to need assistance, the system may then modify a portion of the application to enable the user to access the assistance provided by the system. The portion of the application and the assistance may be modified by on the monitored usage and based on information associated with the user.

Abstract: A system for sharing a communications session between multiple devices is disclosed. The system may receive a first request to establish the communications session from a first device associated with a user. The system may establish the communications session for the first device associated with the user in response to the first request. Additionally, the system may receive, from a second device associated with the first user, a second request to join the communications session. Furthermore, the system may join the second device to the communications session if the first request and the second request include a common identifier for the first user. Moreover, the system may transmit instructions for causing communications associated with the first device to be presented on a user interface of the second device during the communications session.

Abstract: A method of conferencing participant video data and audio data includes switching from a mesh-based conference to an MCU-based conference upon the occurrence of a trigger event.