Abstract:
A server is configured to provide a service that manages access to communication sessions supported by at least one communication service and to which user devices connect. The service assigns to users registered with the service respective communication identifiers that the users, and unregistered users of the service, use to access the communication sessions via user devices. The service maps each communication identifier to a list of communication sessions, if any, in which the respective user is currently participating and/or is scheduled to participate. The service receives from a user device a join request from a requester. The join request indicates a particular communication identifier of a particular user registered with the service and a requester identifier. The service connects the user device to a communication session, if any, based on the particular communication identifier and the requester identifier.
Abstract:
A server or other computing device manages meetings in a virtual meeting room on behalf of a virtual meeting room owner. A request is received from an attendee to join a meeting in the virtual meeting room. A determination is made, based on configurations set by the virtual meeting room owner, whether to connect the attendee to a virtual waiting room. The attendee is connected to the virtual waiting room in accordance with the configurations set by the virtual meeting room owner.
Abstract:
A meeting application can gather calendar information from a calendaring service, even if that calendaring service is independent from (e.g., a “third party to”) the meeting service. The meeting application can incorporate the calendar information into an in-meeting graphical user interface so that the calendar information can be displayed with the meeting. In some embodiments, this includes listing all invitees and participants alongside their associated acceptance status (e.g., are they present, did they accept, did they decline, etc.). In some embodiments, the calendar information can inform a meeting timer that can indicate the remaining time for the meeting. In some embodiments, the calendar information can inform individual timers that indicate how much time individual participants have before their next appointment.
Abstract:
A server is configured to host a web-based collaboration room through which user devices of member users are able to communicate. Each of the member users is assigned a distinct communication identifier. The server generates for display at each of the user devices a selectable start option associated with the communication identifier assigned to the user of the user device. The server receives from a first user device among the user devices a selection of the start option and that includes the communication identifier of a first user among the users. In response, the server initiates a communication session, connects the first user device to the communication session, links the received communication identifier to the communication session, and generates for display at each of the user devices a respective selectable join option associated with the linked communication identifier and by which the communication session is accessible.
Abstract:
A meeting server receives from a client device a join request for a user to join a scheduled meeting. An identifier is obtained for the user based on the join request. Information for the meeting is accessed based on the join request, the information including a list of invitees for the meeting. The identifier for the user is compared with the list of invitees for the meeting. It is determined whether to connect the client device to the meeting based on the comparing.
Abstract:
A stack fusion method is implemented at an originator cluster of software services in a distributed Software-as-a-Service (SaaS) system. The method includes receiving a request for a communication service from an originator registered to the originator cluster. The method further includes, responsive to the request, creating a communication protocol object in the originator cluster, discovering a participant cluster on which the participant is registered, notifying the participant via the participant cluster that the communication protocol object exists, and updating an index protocol object in the participant cluster that tracks communication sessions in which the participant is engaged with a reference that points to the communication protocol object in the originator cluster.
Abstract:
A stack fusion architecture enables a cloud provider to provide Software-as-a-Service (SaaS) offerings to multiple organizations. Each organization operates a Infrastructure-as-a-Service (IaaS) platform and is associated with an organization domain. A cluster of software/communication services is deployed to each platform. Users registered to an organization domain have access limited to the cluster uniquely associated with that domain. The architecture includes a globally accessible domain-to-cluster map used to map each cluster to the associated domain. A locally accessible user-to-cluster map is stored in each cluster to map that cluster to each user registered to the domain uniquely associated with that cluster. The architecture enables communication between users provisioned on different clusters and registered to different domains without exposing private information to the cloud provider.