-
- Using VMware vSphere With Your System
- Networking Checklist For Your System
- Installing Your System Using Automatic Deployment
- Installing Your System Using Manual Deployment
- Configuring Your Mail Server, Time Zone, and Locale
- Altering the System After Installation
- Adding a High Availability System
- Expanding Your System to a Larger System Size
- Updating the System
- Upgrading the System
Configuring Your System
This module describes how to use the administrator pages to configure your system.
- Configuring System Properties
- Upgrading Your System
- Configuring General Settings
- Configuring Servers
- Configuring Your SNMP Settings
- Managing Licenses
Configuring System Properties
Configure your system properties by selecting System and View More in the System section.
- Changing Your Virtual Machine Settings
- Configuring a High Availability System
- Changing Your Virtual IP Address
- Configuring Public Access
- Expanding System Size
Changing Your Virtual Machine Settings
Use this feature to change your virtual machine settings.
![]() Note |
Do not use VMware vCenter to edit your virtual machine settings. |
What to Do Next
If you make changes to any of your virtual machines, you must obtain new certificates for each virtual machine on your system unless you are using wildcard certificates for systems in the same domain. For more information, see Managing Certificates.
Configuring a High Availability System
A high availability system is a redundant system that provides backup in the event of a primary system failure.
Adding a High Availability System
![]() Note |
Most of the features on your high-availability system are prohibited. For example you do not have access to upgrade, SNMP configuration, storage access, or email servers on your high-availability system. You can view system properties, but modification is prohibited. |
![]() Note |
Complete the following procedure on the primary system. |
-
Install Cisco WebEx on a second virtual machine from the OVA file to be used as your high availability system.
Note
Your high-availability system must be the same size as your primary system.
- Your high-availability system must be configured with the same OVA and patch as your primary system. If your primary and high-availability systems' versions do not match, you will be instructed to upgrade to the higher version.
- Copy the high-availability virtual machine fully qualified domain name (FQDN). You must know the FQDN to add your high-availability system.
- Verify that all virtual machines are functioning normally. Determine virtual machine status by viewing the System Monitor as described in About Your Dashboard.
Step 1 | Sign in to the Administration site. |
Step 2 | On the primary system, in the System section, select the View More link. |
Step 3 | Select Add High Availability System. |
Step 4 |
Follow the instructions on the System Properties page to add this HA system. Example: |
Step 5 |
Enter the FQDN of the Administration site virtual machine of the high-availability system and select Continue. We will validate the readiness of both the primary system and the HA system for this add HA procedure. |
Step 6 |
Select Turn On Maintenance Mode, then select Add. Your high-availability system is added and automatically configured to serve as a backup in the event of a primary system failure. |
Step 7 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Removing a High Availability System
You must have a secondary system currently configured as your high-availability system.
Step 1 | Sign in to the Administration site. | ||
Step 2 | In the System section, select the View More link. | ||
Step 3 |
Select Remove High Availability System. The Remove High Availability System page appears displaying the fully qualified domain name (FQDN) of your high-availability system. |
||
Step 4 |
Select Continue.
Your high-availability system is removed. |
||
Step 5 | Open VMware vCenter and remove the high-availability system using the Delete from Disk command. |
Changing Your Virtual IP Address
Step 1 | Sign in to the Administration site. |
Step 2 | Select System and select View More in the System section. |
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. |
Step 4 |
In the Virtual IP Address section, select a link in the Type column. Example:Select Private for the private virtual IP address. |
Step 5 | Enter your new virtual IP address in the VIP IPv4 Address dialogue box. |
Step 6 | Select Save. |
Step 7 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Configuring Public Access
Public access enables people external to your network to host or attend online meetings through the Internet or mobile devices. Removing public access will remove public virtual IP address settings for your WebEx site URLs and terminate external access to your site.
Adding Public Access to Your System
To enable public access you must first configure an Internet reverse proxy virtual machine to serve as your public access system.
Launch VMware vCenter and perform the following:
- Back up your virtual machines using VMware Data Recovery. This enables you to revert the changes if necessary. See Creating a Backup Using VMware vCenter for more information.
-
Deploy an Internet reverse proxy virtual machine using the same OVA file that you used to deploy your administrator virtual machine. Your Internet reverse proxy virtual machine must be on the same subnet as the Public virtual IP address. See Adding Public Access for more information.
Note
If you have a high-availability system, you must also deploy an Internet reverse proxy virtual machine for your high-availability system.
Step 1 | Sign in to the Administration site. | ||
Step 2 | Select System and then select the View More link in the System section. | ||
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. | ||
Step 4 | Select Add Public Access. | ||
Step 5 |
Enter your Internet reverse proxy virtual machine in the FQDN field.
|
||
Step 6 |
Select Detect virtual machines.
If your system has any updates that are incompatible with the OVA version you used to create the Internet reverse proxy virtual machine you receive an error message and cannot proceed until after you redeploy the Internet reverse proxy virtual machine using an appropriate OVA file compatible with updates on your primary system. |
||
Step 7 | Select Continue. | ||
Step 8 |
Enter the IP address from the same subnet that you used to configure your Internet reverse proxy virtual machine in the Public (VIP) Virtual IPv4 Address field and select Save. Your system is updated and public access is configured. Make sure you keep your browser window open for the entire process. If your primary system requires minor updates compatible with the OVA version you used for creating the Internet reverse proxy virtual machine, they are automatically applied to your Internet reverse proxy virtual machine. |
||
Step 9 |
If your system requires minor updates, you are prompted to select Restart after the updates are complete. If no updates are required, proceed to the following step. After your system restarts, you receive a confirmation message indicating that you have added public access. |
||
Step 10 | Verify your configuration. If you are satisfied, you can delete the virtual machine backup that you configured before performing this procedure. | ||
Step 11 | Select Done. | ||
Step 12 | Verify that your security certificates are still valid. Because this procedure changes your virtual machines, it might affect your certificates. If necessary, your system provides a self-signed certificate to keep your system functioning until you can reconfigure your certificates. See Managing Certificates for more information. | ||
Step 13 | Make any necessary changes to your DNS servers. | ||
Step 14 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Removing Public Access
Back up your virtual machines using VMware Data Recovery. This enables you to revert your changes if necessary. See Creating a Backup Using VMware vCenter for more information. Make sure you power on your virtual machines after your backup is complete.
Step 1 | Sign in to the Administration site. | ||
Step 2 | Select System and then select the View More link in the System section. | ||
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. | ||
Step 4 |
Select the desired site, select Remove Public Access, and select Continue. Public access is removed from the site.
|
||
Step 5 | Select Done. | ||
Step 6 | Open VMware vCenter, power off, and delete the Internet Reverse Proxy machine (and high-availability Internet reverse proxy machine, if deployed) from your system. | ||
Step 7 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Expanding System Size
Before you perform a system expansion, see Expanding Your System to a Larger System Size, which describes all the pre-requisite steps you should take before using this feature and how to expand your system using automatic or manual deployment.
Step 1 | Sign in to the Administration site. |
Step 2 | Select System and select the View More link in the System section. |
Step 3 | Select Expand System Size. |
Step 4 | Select Turn On Maintenance Mode and Continue to confirm. |
Step 5 |
Select Continue. Your system checks connectivity to the virtual machines. If there are connectivity problems with one or more virtual machines, you must fix the problems before you can continue. If there are no connectivity problems, your system performs an automatic backup. After the backup is complete, you are notified that you can proceed with your expansion. |
Step 6 |
Deploy the OVA file using one of the following methods:
Your system notifies you once the expansion is complete. |
Step 7 | Select Restart. |
Step 8 | Sign in to the Administration site. |
Step 9 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Upgrading Your System
The Upgrade page gives you the option to update, upgrade, or expand your system.
Step 1 | Sign in to the Administration site. |
Step 2 | Select System > Upgrade. |
Step 3 |
Select the type of upgrade you want to perform and select Continue:
Your proceed to the update, upgrade, or expand page. |
Step 4 | Select Turn On Maintenance Mode and Continue to confirm. |
Step 5 | Perform your update, upgrade, or expansion as described in the associated section. |
Step 6 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Configuring General Settings
To access your general settings, select System and the View More link under Configuration > General settings. General settings include the following features:
- Site Settings—Use this feature to configure or change your site URL. This feature also displays your site private virtual IP address and site public virtual IP address.
- Administration Settings—Use this feature to configure or change your administration site URL. This feature also displays your administration site private virtual IP address.
Changing Your Site Settings
You configure your original site URL setting during deployment. For more information about site URL configuration and naming conventions, see WebEx Site and WebEx Administration URLs.
Make sure you retain your original site URL on the DNS server. Redirect your original site URL to the updated site URL. If users attempt to use the original URL and you have not redirected it to the new URL, they will not be able to host or join meetings or log in from web pages, productivity tools, and mobile apps.
Step 1 | Sign in to the Administration site. |
Step 2 | Select System > Configuration > General settings > View More. |
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. |
Step 4 | In the Site Settings section, select Edit. |
Step 5 | Enter your new site URL in the dialog box and select Save. |
Step 6 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
What to Do Next
Update your site certificate to ensure secure access. See Managing Certificates for more information.
Changing Your Administration Settings
You configure your original administration site URL setting during deployment. For more information about administration site configuration and naming conventions, see WebEx Site and WebEx Administration URLs.
Make sure you retain your original administration site URL on the DNS server. Redirect your original administration site URL to the updated administration site URL. If users attempt to use the original URL and you have not redirected it to the new URL, they will not be able to host or join meetings or log in from web pages, productivity tools, and mobile apps.
Step 1 | Sign in to the Administration site. |
Step 2 |
Select System > Configuration > General settings > View More. The General settings page appears. |
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. |
Step 4 | In the Administration Settings section, select Edit. |
Step 5 | Enter your new administration site URL in the dialog box and select Save. |
Step 6 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
What to Do Next
Update your site certificate to ensure secure access. See Managing Certificates for more information.
Configuring Servers
Use these features to configure your servers:
- Configuring a Mail Server
- Configuring an SMTP Server
- Configuring a Storage Server
- Using the Disaster Recovery Feature
Configuring a Mail Server
Configure a mail server to enable your system to send meeting invitations and other communications to users.
![]() Note |
It is very important that your mail server is always operational. Email is the primary method of communication with your users including recording notifications, meeting information changes, account status, and many other important announcements. |
Step 1 | Sign in to the Administration site. |
Step 2 | Select System and select View More in the Servers section. |
Step 3 | Select Edit in the Mail Server section. |
Step 4 | Select Turn On Maintenance Mode and Continue to confirm. |
Step 5 | Enter your mail server hostname and optionally select the TLS Enabled check box. |
Step 6 | Enter your mail server port number and optionally select the Server Authentication Enabled check box. |
Step 7 | Select Continue. |
Step 8 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Configuring an SMTP Server
Step 1 | Sign in to the Administration site. |
Step 2 | Select System. |
Step 3 | Under Servers, select the View More link. |
Step 4 | Select Turn On Maintenance Mode and Continue to confirm. |
Step 5 | Under SMTP Server, select the Edit link. |
Step 6 | Complete the SMTP server fields: |
Step 7 | Optionally select the TLS Enabled and Server Authentication Enabled check boxes. |
Step 8 | Select Save. |
Step 9 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Configuring a Storage Server
Your storage server backs up your database and recorded meetings on a daily basis.
Make sure to configure your Unix access privileges so that your system can store user-generated content and system backups.
Step 1 | Sign in to the Administration site. |
Step 2 | Select System. |
Step 3 |
In the Servers section, select View More. If a storage server is present on your system, it is displayed on this page. If there is no storage server present on your system, you are given the option to configure one. |
Step 4 | Select Turn On Maintenance Mode and Continue to confirm. |
Step 5 | In the Storage Server section, select Add a Storage Server now. |
Step 6 |
Enter the NFS mount point and select Continue. The system confirms your NFS mount point. |
Step 7 |
Select Continue. You receive a confirmation message that your storage server has been added. |
Step 8 | Select Done. |
Step 9 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
What to Do Next
Configure your system to use the storage server for the following:
- Meeting recordings.
- Disaster recovery. See Using the Disaster Recovery Feature for more information.
Using the Disaster Recovery Feature
Use the disaster recovery features to recover your deployment after any type of system failure or other disaster. A disaster could be a network crash, server failure, data center outage, or other event that makes your system unusable. There are two types of disaster recovery:
- One data center disaster recovery—If you have a single data center and your system becomes unavailable, you can reinstall your system in the same data center and restore it to the same state.
- Two data center disaster recovery—If you have two data centers and your system becomes unavailable on the first data center, you can access the system on your second data center and restore it to the same state.
After you have configured a storage server, your system is backed up on a daily basis. A system backup notice appears on your dashboard that displays information about the latest backup. If you perform a disaster recovery the latest backup is used. Note that disaster recovery
- Takes more than 30 minutes.
- Overwrites your settings with the settings on the latest backup.
- Requires you to perform additional steps to restore service to your users (detailed in "What To Do Next," below).
Perform the procedure below after a disaster has occurred and you have lost the ability to use your system.
- To perform disaster recovery procedures, you must have a storage server configured. See Configuring a Storage Server for more information. If you do not have a storage server configured, the Disaster Recovery option is not available.
- You must have access to a system on which you can restore your deployment. See the information on one data center and two data center disaster recovery, below.
- Your recovery system must be the same deployment size and software version as your original system. Disaster recovery can be performed on systems with or without high availability. However, you cannot configure disaster recovery on a high-availability system. You must configure disaster recovery first and then you can configure high availability on that system. If you have a high-availability system that requires disaster recovery, your must restore your system and then reconfigure high availability on your restored system. For more information on high availability, see Adding a High Availability System.
Step 1 | Sign in to the Administration site on a system where you can restore your deployment. |
Step 2 | Select System > Servers > Add Storage Server. |
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. |
Step 4 |
Enter the name of your storage server in the NFS Mount Point field and select Continue. Example:Enter ip://xyz/yu. |
Step 5 |
Select Continue to proceed with disaster recovery. If the recovery system deployment size and software version matches your original system, you can proceed with disaster recovery. If the system has a different deployment size or software version, you cannot proceed. If this happens, you must redeploy the application on your recovery system so that the deployment size and software version match the original deployment. |
Step 6 |
Select one of the following to continue:
The disaster recovery process begins. If you close your browser, you cannot sign back into the system until the process is completed. |
Step 7 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
What to Do Next
You must perform the following procedures to restore service to your users:
- Reconfigure your teleconferencing settings. Refer to Configuring CUCM in the Planning Guide for more information.
- Reconfigure your SSO settings. See Configuring Federated Single Sign-On (SSO) Settings for more information.
- Reconfigure your SNMP settings. See Configuring Your SNMP Settings for more information.
- Reconfigure your certificates. See Managing Certificates for more information. You might have to reload your SSL certificates if they do not match the SSL certificates that are configured on the recovery system.
- Your recovery system is initially configured for License Free Mode which expires in 180 days. Re-host your previous system's licenses on the recovery system. See About Licenses for more information.
- Configure your DNS settings so that your site URL points to the current VIP. Your VIP on the restored system might be different from what you had on your original system. You must complete your DNS configuration for end users to use their original links to sign into or join meetings on the restored system. See Changing Your Virtual IP Address for more information.
Configuring Your SNMP Settings
You can configure the following SNMP settings:
- Community strings—SNMP community strings authenticate access to MIB objects and function as an embedded password. The default community string is CWS-Public. Select CWS-Public to edit it or add additional community strings.
- USM users—Configure user-based security (USM) to provide additional message-level security. Select an existing USM configuration to edit it or add additional USM configurations.
- Notification destinations—Use this feature to configure the trap/inform receiver.
- Configuring Community Strings
- Configuring USM Users
- Configuring Notification Destinations
- Editing a Notification Destination
Configuring Community Strings
You can add and edit community strings and community string access privileges.
Adding Community Strings
Step 1 | Sign in to the Administration site. | ||||||||
Step 2 | Select System and select the View More link in the SNMP section. | ||||||||
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. | ||||||||
Step 4 | Select Add in the Community Strings section. | ||||||||
Step 5 |
Complete the fields on the Add Community String page.
Select Add. The community string is added to your system. |
||||||||
Step 6 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Editing Community Strings
Step 1 | Sign in to the Administration site. | ||||||||
Step 2 | Select System and select the View More link in the SNMP section. | ||||||||
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. | ||||||||
Step 4 | Select a community string name link in the Community Strings section. | ||||||||
Step 5 |
Change the desired fields on the Edit Community String page.
Select Edit. Your community string information is changed. |
||||||||
Step 6 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Configuring USM Users
You can add and edit your USM users.
Adding USM Users
Step 1 | Sign in to the Administration site. | ||||||||||||||||||||||
Step 2 | Select System and then select View More in the SNMP section. | ||||||||||||||||||||||
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. | ||||||||||||||||||||||
Step 4 | Select Add in the USM Users section. | ||||||||||||||||||||||
Step 5 |
Complete the fields on the Add USM User page.
|
||||||||||||||||||||||
Step 6 |
Select Add. The USM user is added to your system. |
||||||||||||||||||||||
Step 7 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Editing USM Users
![]() Note |
The default USM user, serveradmin, is used internally and the user can only change the password but not security level, auth, and privacy algorithm. |
Step 1 | Sign in to the Administration site. | ||||||||||||||||||||||
Step 2 | Select System and then select View More in the SNMP section. | ||||||||||||||||||||||
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. | ||||||||||||||||||||||
Step 4 | Select a USM user in the USM Users section. | ||||||||||||||||||||||
Step 5 |
Change the desired fields on the Edit USM User page.
|
||||||||||||||||||||||
Step 6 |
Select Edit. The USM user information is changed. |
||||||||||||||||||||||
Step 7 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Configuring Notification Destinations
You can configure virtual machines on your system to generate SNMP notifications or traps for the following:
Step 1 | Sign in to the Administration site. | ||||||||||||||||||
Step 2 | Select System and select the View More link in the SNMP section. | ||||||||||||||||||
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. | ||||||||||||||||||
Step 4 | Select Add new Notification Destination under Notification Destinations. | ||||||||||||||||||
Step 5 |
Configure the following fields for your notification destination:
|
||||||||||||||||||
Step 6 |
Select Add. Your notification destination is added. |
||||||||||||||||||
Step 7 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Editing a Notification Destination
Configuring Notification Destinations
Step 1 | Sign in to the Administration site. | ||||||||||||||||||
Step 2 | Select System and select the View More link in the SNMP section. | ||||||||||||||||||
Step 3 | Select Turn On Maintenance Mode and Continue to confirm. | ||||||||||||||||||
Step 4 | Select a notification destination link from the Notification Destinations list. | ||||||||||||||||||
Step 5 |
You can edit the following fields for your notification destination:
|
||||||||||||||||||
Step 6 |
Select Save. Your notification destination changes are saved. |
||||||||||||||||||
Step 7 |
Select Turn Off Maintenance Mode and Continue to confirm. Your system restarts after you turn off maintenance mode. You can sign back into the Administration site after restart is complete. |
Managing Licenses
When you purchase this product, you are given a 180-day free trial period. After your free trial period expires, you are required to purchase licenses for your users. To obtain licenses, you use an embedded version of Cisco Enterprise License Manager. Refer to the Cisco WebEx Meetings Server Planning Guide for more information.
Contact your Cisco sales representative to order licenses for your system. Your sales representative will send you an email that contains your Product Authorization Key (PAK).
Step 1 | Sign in to the Administration site. | ||
Step 2 | Select System and then select the View More link in the Licenses section. | ||
Step 3 |
Select Manage Licenses
|
||
Step 4 | Select License Management > Licenses. | ||
Step 5 |
Select Generate License Request. The License Request and Next Steps dialog box appears. |
||
Step 6 | Copy the selected text in the field and select Cisco License Registration. | ||
Step 7 |
Log in to your Cisco account. The Product License Registration page appears. |
||
Step 8 |
Enter the PAK that you received from your Cisco sales representative in the Product Authorization Key field and select Next. The Fulfill PAK page appears. |
||
Step 9 | Paste the contents of the License Request that you copied above into the field, enter the quantity of licenses you are purchasing, and select Next. | ||
Step 10 | Review the page and select I agree to the Terms of the license. | ||
Step 11 | Make sure the contact email address is correct. Optionally change the contact email address in the Send to field. | ||
Step 12 |
Select Get License The License Request Status dialog box appears. |
||
Step 13 | Obtain your license file in one of the following ways: | ||
Step 14 | Return to the Administration site and select System and then select the View More link in the Licenses section. | ||
Step 15 |
Select Manage Licenses. Your browser opens a new tab or window containing Cisco Enterprise License Manager (ELM). |
||
Step 16 | Select Install License File. | ||
Step 17 | Select Browse and select the license file (.bin) that you downloaded or extracted from the ZIP file in your email. | ||
Step 18 |
Select Install. Your license file is installed. Check the license information that is displayed to ensure that it is correct. |
||
Step 19 |
Select System and select View More in the License section. The User Licenses page appears. Ensure that the information displayed is correct. |
Adding Licenses
Obtain your registration ID number. You can find your registration ID number by opening your Enterprise License Management tool and selecting About.
Step 1 | Sign in to the Administration site. |
Step 2 | Select Support and call the TAC at the listed number. |
Step 3 |
File a case, requesting the number of additional licenses you want. Cisco processes your request and enables the additional licenses on your system. |
Step 4 | Select System. |
Step 5 | Check the License section to confirm that your additional licenses have been added. |
About Licenses
This product has User-Based Licensing which requires that you purchase a license for each user that intends to host meetings. We count licenses as follows:
- If a user hosts at least one meeting per 30-day window, then that user consumes one license. If this user hosts additional meetings in this same 30-day window, the user still only consumes one license, unless this user hosts simultaneous meetings.
- If a user hosts simultaneous meetings (at the same date and time), then the system counts an additional license for each simultaneous meeting hosted by this user in the 30-day window.
- If a user hosts no meetings in the 30-day window, then this user consumes no licenses.
![]() Note |
There is currently a known issue that causes no licenses to be consumed if a user attends only the teleconference portion of a meeting (and not the web portion). In future versions of this product, attending either the teleconference or web portion of a meeting (or both) will result in a license use. |
![]() Note |
The system counts license use for each user every 30 days, as shown in the following table. |
Scenario | Meeting Date | Meeting Start Time | Simultaneous Meetings | Licenses Consumed in 30 Days |
---|---|---|---|---|
User A schedules a meeting but does not host it. | January 1 | 9:00 a.m. | No | 0 |
User B hosts one meeting. | January 2 | 9:00 a.m. | No | 1 |
User C hosts two meetings on different dates and times. | January 3 January 4 |
9:00 a.m. 10:00 a.m. |
No | 1 |
User D hosts two meetings on the same date and time. | January 6 January 6 |
9:00 a.m. 9:00 a.m. |
Yes (2) | 2 |
User E hosts two meetings on the same date and time, and another two simultaneous meetings on a different date and time within the month. | January 6 January 6 January 10 January 10 |
9:00 a.m. 9:00 a.m. 4 p.m. 4 p.m. |
Yes (2) | 2 |
User F hosts two meetings on the same date and time neither of which he attends, although the meetings occur. | January 7 January 7 |
9:00 a.m. 9:00 a.m. |
Yes (2) | 2 |
User G hosts a meeting and passes host rights to another participant during the meeting. The user then hosts a 2nd meeting that runs simultaneously with the 1st meeting. | January 8 January 8 |
9:00 a.m. 9:00 a.m. |
Yes (2) | 2 |
User H hosts a meeting but all of the meeting participants join the teleconference only (not the web portion) with the Join Before Host option selected. | January 9 | 9:00 a.m. | No | 0 |
User J hosts two meetings on the same date and time but all of the meeting participants join the teleconference only (not the web portion) with the Join Before Host option selected. | January 10 January 10 |
9:00 a.m. 9:00 a.m. |
No | 0 |
User K hosts a meeting and passes host rights to another participant during the meeting. The user then hosts a 2nd meeting that runs simultaneously with the 1st meeting but all of the 2nd meeting participants join the teleconference only (not the web portion) with the Join Before Host option selected. | January 11 January 11 |
10:00 a.m. 10:00 a.m. |
No | 1 |
![]() Caution |
As a convenience, the system permits license consumption to exceed the number of licenses actually installed on the system. In these situations, you and the other administrators will receive ‘Licenses are in Overage’ emails. In addition, the Dashboard displays messages indicating you have up to 180 days to purchase additional licenses to cover the gap. During this 180-day period, the system will continue to function normally for end users. However, once the 180 days elapse, then the system will shut down for all end users until an administrator installs additional licenses.
|