Abstract: Implementations for combining at least two video streams received from devices of a plurality of participants of a video conference into a composite video stream are described. A video conference including the video streams received from the devices of the plurality of participants is established. A capability associated with consuming at least two of the video streams is received from at least one of the devices. The at least two video streams are then combined into a composite video stream based on the capability associated with consuming the at least two video streams. The composite video stream is transmitted to the at least one of the devices.

Abstract: A join service joins first and second computerized meetings. The join service receives information about the first and second computerized meetings from respective first and second meeting services. In response to a request from one of the first and second services to join the meetings, the join service translates audio, video, and data signaling between the first computerized meeting service and the second computerized meeting to join participants in the first computerized meeting and participants in the second meeting in a combined computerized meeting. An alternative join service obtains a uniform resource indicator (URI) for an agent of the first meeting. In response to a request from a participant in the second meeting to access the first meeting, the join service provides the URI to the second meeting service to allow the second meeting service to join the second meeting to the first meeting.

Abstract: A first meeting of a first network service is connected to a second meeting of a second network service by sending data identifying the first network service to the second network service and receiving, from the second network service, a key that is associated with the first network service. The first network service then sends information identifying the second meeting and a link to the first meeting to the second network service using an address for second network service that includes the key. The first network service then receives a second meeting link to the second meeting from the second network service and providing devices participating in the first meeting with the second meeting link. These devices activate the second meeting link to access resources of the second meeting.

Abstract: A first meeting of a first network service is connected to a second meeting of a second network service by sending data identifying the first network service to the second network service and receiving, from the second network service, a key that is associated with the first network service. The first network service then sends information identifying the second meeting and a link to the first meeting to the second network service using an address for second network service that includes the key. The first network service then receives a second meeting link to the second meeting from the second network service and providing devices participating in the first meeting with the second meeting link. These devices activate the second meeting link to access resources of the second meeting.

Abstract: Binding of separate communication platform meetings is provided. Video conference service interconnection with online meeting service may be achieved by allowing the online meeting service to provide a tenant identifier to the video conference service, which may be associated with the tenant and used in a key that is used by the video conference service to schedule and initiate meetings. The online meeting service may also include the key in metadata used by its scheduling service. The tenant identifier and/or the key may be used by the components involved in initiating and, facilitating various meetings by users of the online meetings (and by users of the video conference service).

Abstract: Binding of separate communication platform meetings is provided. Video conference service interconnection with online meeting service may be achieved by allowing the online meeting service to provide a tenant identifier to the video conference service, which may be associated with the tenant and used in a key that is used by the video conference service to schedule and initiate meetings. The online meeting service may also include the key in metadata used by its scheduling service. The tenant identifier and/or the key may be used by the components involved in initiating and, facilitating various meetings by users of the online meetings (and by users of the video conference service).

Abstract: One or more techniques and/or systems are disclosed for joining a device to a meeting. A device can send a request to join the meeting, such as by selecting a meeting request link in an invitation received at the device. A join meeting service may receive the request, authenticate the request, and return a code package and meeting related document. The code package can be used at the device, and/or at the join meeting service, to identify one or more meeting clients (e.g., applications) on the device. A supported meeting client that may be used to join the device to the meeting can be selected from the one or more meeting identified clients, if at least one meeting client is identified, and launched to join the device to the online meeting.

Abstract: Embodiments are configured to provide reminders associated with communications and other events. In an embodiment, components of a communication system can operate to generate, maintain, and implement reminders associated with communications and other events. A reminder can be automatically generated and scheduled for one or more users of the communication system when a user is unavailable or unable to take a call. Reminders can be generated to include information which can be used to establish a communication event for a subsequent communication associated with each reminder.

Abstract: Embodiments are configured to provide information associated with a communication event to a communication party. In an embodiment, components of a communication system operate to provide a recorded call subject to a receiving party as part of a communication event. In one embodiment, a communication device can be used to record, package, and transmit subject matter as part of a communication event, wherein the recorded subject matter can be used to inform a receiving party of a communication subject.

Abstract: Embodiments are configured to provide reminders associated with communications and other events. In an embodiment, components of a communication system can operate to generate, maintain, and implement reminders associated with communications and other events. A reminder can be automatically generated and scheduled for one or more users of the communication system when a user is unavailable or unable to take a call. Reminders can be generated to include information which can be used to establish a communication event for a subsequent communication associated with each reminder.

Abstract: Embodiments are configured to provide reminders associated with communications and other events. In an embodiment, components of a communication system can operate to generate, maintain, and implement reminders associated with communications and other events. A reminder can be automatically generated and scheduled for one or more users of the communication system when a user is unavailable or unable to take a call. Reminders can be generated to include information which can be used to establish a communication event for a subsequent communication associated with each reminder.

Abstract: One or more techniques and/or systems are disclosed for joining a device to a meeting. A device can send a request to join the meeting, such as by selecting a meeting request link in an invitation received at the device. A join meeting service may receive the request, authenticate the request, and return a code package and meeting related document. The code package can be used at the device, and/or at the join meeting service, to identify one or more meeting clients (e.g., applications) on the device. A supported meeting client that may be used to join the device to the meeting can be selected from the one or more meeting identified clients, if at least one meeting client is identified, and launched to join the device to the online meeting.

Abstract: Modality selection in establishing multimodal conversations is performed automatically based on contextual information in enhanced communication platforms. Automata in client machines determine how a client machine chooses one or more modalities of a conversation invite based on contextual information such as computing device environment, network environment, user presence state, and comparable factors. Executed automata automatically join the user to a selected modality of a conversation or reject one.