![]() In this scenario deployment has:Īll Call Bridges talk to all Web Bridges. The scheduler maintains Full mesh connections with all Web Bridges. įor example, webbridge3 c2w trust schedulerbun.cer , where schedulerbun.cer is a bundle of all scheduler certificates and Call Bridge certificates. So, bundle all scheduler certificates and have Web Bridge trust Scheduler Bundle: webbridge3 c2w trust Īll the necessary certificates for both schedulers and Call Bridges can be included in the. It is also necessary for the Web Bridge to be able to trust the scheduler. ![]() So bundle all Web Bridge certificates and have the scheduler trust Web Bridge Bundle.Ĭonfigure the scheduler with the command: scheduler c2w trust webbridge_bundle.cerįor example: scheduler c2w trust wbbundle.cer, where wbbundle.cer is a bundle of trust of all Web Bridge certificates. It is important for the scheduler to be able to trust each Web Bridge it connects to. A full chain certificate is to be offered by the Scheduler service when you establish a secure connection to Web Bridge servers. Where BUN344748.cer is a full chain certificate. To do this, create a certificate and upload it to the Meeting Server via Secure File Transfer Protocol (SFTP) or use the Public Key Infrastructure (PKI) MMP commands to create a certificate. This ensures that the certificate used is already included in the Web Bridge C2W trust. Since the Scheduler is required to run on a server which also has a colocated Call Bridge, it is possible to use the Call Bridge certificate and C2W trust cert for the Scheduler service for ease of deployment. In this release, each scheduler needs to be able to connect to each Web Bridge in a cluster. The scheduler requires the configuration of a client certificate and key to be used for this connection. Similarly, the C2W connections are all automatic but it is necessary to configure a trust bundle between the scheduler and Web Bridges.Ĭ2W is a TLS-based WebSocket connection established from the scheduler to each Web Bridge. ![]() No explicit configuration is required to enable the connection between the scheduler and Call Bridge because this happens automatically over the loopback interface. It is not possible to configure the scheduler to use a remote Call Bridge.Ĭ2W connections are established to each Web Bridge similar to how the Call Bridge also establishes a C2W connection to each Web Bridge. It is therefore a requirement that the scheduler is deployed on a Meeting Server which also hosts a Call Bridge. When the scheduler is enabled, it makes API requests to the Call Bridge over the loopback interface. ![]() Scheduler C2W - Web Bridge Connection Explained New Mainboard Management Processor (MMP) command is set to configure the scheduler highlighted as shown in the image. The scheduler is a beta component of CMS 3.3. The web app is configured without a scheduler as shown i n the image. If the meeting has ended 24 or more hours before the task is run, the temporary space is removed. Note: The scheduler component deletes the temporary spaces that are created when you schedule the meeting through an internal task that runs every 24 hours at 1:15 GMT. It is now supported on Meeting Server 1000, Meeting Server 2000, and Meeting Server on Virtualized deployments. Version 3.5 introduces the support for Scheduler on Meeting Server 2000. Note: In version 3.4, the Scheduler component was released as a fully supported feature on Meeting Server 1000 and Virtualized deployments. Background InformationĬMS Version 3.3 introduces the ability to schedule meetings and see upcoming meetings in the web app. Web app users can schedule meetings, modify the scheduled meetings, and notify participants via email. If your network is live, ensure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. The information in this document is based on these software and hardware versions: Prerequisites RequirementsĬisco recommends that you have knowledge of these topics: This document describes how to configure Cisco Meeting Server (CMS) Scheduler on CMS 3.3 and how to schedule a meeting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |