
Configure the scheduler to use the certificate.
hq-cms> scheduler c2w certs cmscert.key CMS-Chain.cer
It is necessary for the scheduler to be able to trust each Web Bridge it connects to. Upload a trust bundle which contains each Web Bridge certificate, via SFTP.
Configure the scheduler using the command.
hq-cms> scheduler c2w trust CMS-Chain.cer
The scheduler has its own HTTPS interface which if enabled, can be used to configure scheduler meetings using the scheduler APIs.
Configure the HTTPS server listen interface using the command.
hq-cms> scheduler https listen a 9445
Configure a certificate key pair for the server using the command:
hq-cms> scheduler https certs cmscert.key CMS-Chain.cer

To enable the Scheduler to send email notifications via the SMTP with Auth Login, configure the email server to listen on a specified port for the SMTP protocol, enable the SMTP server to support Auth Login, and configure a user account for authentication. This account configured on the MMP must have appropriate permissions to be able to send emails on behalf of web app users.
Configure the email server and port, and et the email protocol to SMTP.
hq-cms> scheduler email server smtp.gmail.com 25
hq-cms> scheduler email protocol smtp
From version 3.4 meeting invites can be sent to all the participants from a common email
address. The MMP command scheduler email common-address <address@mail.domain> “<Display name>” configures the common email address and a display name on the Meeting Server. The Scheduler sends the meeting invites from the common email address to the participants.
If the common email address is left blank, the Scheduler sends the email invites from the organizer’s email address.
To enable the Scheduler to send email notifications via the SMTP, configure the email server to listen on a specified port for the SMTP protocol.
hq-cms> scheduler email common-address rmeddane@gmail.com ipdemystify

Set the username to be used for authentication.
hq-cms> scheduler email username rmeddane
Please enter password:
Please enter password again:
hq-cms>

Enable the Scheduler.
hq-cms> scheduler enable
SUCCESS: HTTPS Key and certificate pair match
SUCCESS: HTTPS full chain of certificates verifies correctly
SUCCESS: C2W Key and certificate pair match
SUCCESS: C2W full chain of certificates verifies correctly
WARNING: Email trust store not configured
SUCCESS: scheduler enabled
hq-cms>

Check the configuration and status of the scheduler service using the following command.

From web browser, connect to a space using an AD user, now the option “Schedule Meeting” is displayed. Now you can use this option to schedule a meeting and invite either AD users or by sending email invitations to non-AD users.



very nice post
LikeLiked by 1 person
Sir,
you mentioned that if the email common-address is left blank,the meeting invitation will be sent out from the organizer’s email address(this is what i want)
do we still need to configure scheduler email username and password since the common-address will be left blank?
LikeLike