Table of contents
-
1.
Mividas Rooms
- 1.1. Installation and upgrades
- 1.2. Onboarding
- 1.3. Dashboard
- 1.4. Systems
- 1.5. Monitoring
- 1.6. Address books
- 1.7. Firmware
- 1.8. Scheduled meetings
- 1.9. Panels and macros
- 1.10. Sensors
- 1.11. Call statistics
-
1.12.
Admin
- 1.12.1. Settings
- 1.12.2. System defaults
- 1.12.3. Organization tree
- 1.12.4. Branding profiles
- 1.12.5. Proxy clients
- 1.12.6. Integrations
- 1.12.7. Calendar service
- 1.12.8. Customer
-
1.12.9.
Backend admin
- 1.12.9.1. Address books
- 1.12.9.2. API keys & OAuth
- 1.12.9.3. Authentication and authorization
- 1.12.9.4. Access monitoring (Axes)
- 1.12.9.5. Calendar connections
- 1.12.9.6. CUCM API authorizations
- 1.12.9.7. Endpoints
- 1.12.9.8. Endpoint auth backends
- 1.12.9.9. Endpoint networks
- 1.12.9.10. Endpoint templates
- 1.12.9.11. Exchange Web Services (EWS) connections
- 1.12.9.12. LDAP syncs
- 1.12.9.13. Housekeeper
- 1.12.9.14. Meeting types
- 1.12.9.15. Monitoring rules
- 1.12.9.16. MS Graph API connections
- 1.12.9.17. Providers & infrastructure
- 1.12.9.18. Statistics
- 1.12.9.19. Active trace logs
- 1.12.9.20. Messages
- 1.12.9.21. Authorizations for Webex API
1. Mividas Rooms

Mividas Rooms provides management of your Cisco room systems. From system monitoring to bulk provisioning of software upgrades, address books, and branding profiles, it provides everything you need to manage your systems from one single management interface, the perfect replacement for Cisco TMS.
Its main features include:
- Usage and diagnostic data: it provides instant visibility into video systems and room usage data, allowing you to diagnose room system health in real-time. Call statistics allows you to generate valuable insights reports showing system usage per hour/day by participant or group.
- Monitoring: get an overview of all systems and their current notifications with support for acknowledging and hiding certain notifications.
- Provisioning of video systems: you can provision configuration and registration settings to a single system or in bulk across your organization. Update firmware for any number of systems either immediately or scheduled for later that night.
- Address books: you can create address books from multiple sources, including importing from Cisco TMS. Entries in large phonebooks are easy to find by using the search and filtering functions.
- Room Controls: you can create and distribute powerful macros for room automation, with variable support for powerfull integration with Mividas Rooms.
- Sensors: real time monitoring of meeting room usage (people count) enables you to create powerful reporting from both online and offline meetings. Also includes sensors overview for temperature, noice, humidity etc.
- Branding profiles: you can provision your branding profiles on all or some of your meeting room displays and touch panels across the organization as often as needed.
- First time installing Mividas Rooms? continue here
- Release notes for Mividas Rooms can be found here
Supported systems
| Cisco Webex Room series (Room, Room Kit) |
| Cisco Webex Desk series (Desk, Desk pro) |
| Cisco C series (C20, C40, C60, C90) |
| Cisco DX series (DX70, DX80) |
| Cisco EX series (EX60, EX90) |
| Cisco MX series (MX200, MX300, MX700, MX800) |
| Cisco SX series VTC systems (SX10, SX20, SX80) |
Supported software versions
| Cisco CE9.x and later |
| RoomOS 10.x and later |
| TC 7.3.x (limited support) |
1.1. Installation and upgrades
The Mividas Rooms installation and deployment process involves three main steps:
- Mividas Virtual Machine (VM): You must first deploy the Mividas Installer virtual machine to your network. Ensure the VM is deployed and running. If not, refer to the VM deployment documentation.
- Mividas Installer Setup: Mividas Installer must be set up correctly and your license key activated. Refer to the Mividas Installer documentation if needed. After entering your license key, the Mividas Installer displays all product modules that are accessible with your license. The installation of Mividas Rooms can proceed as a stand-alone installation or alongside other Mividas products.
- Install the Mividas Rooms module: Follow the instructions below to install and deploy the Mividas Rooms product module from the Mividas Installer.
Configuration
On the Mividas Installer start screen, click under Mividas Rooms to start configuration before deployment. Choose Mividas Rooms, which will open up the configuration fields below.
Main domain name for management web interface
| Option | Description |
|---|---|
| Configure Hostname/FQDN | Enter the hostname/FQDN for your installation. Must be a valid DNS record. |
| Select existing certificate | Choose one of your previously uploaded certificates to be used for the installation. |
| Opens up a window of the installer certificate management, where you can upload certificates and more. |
Locale settings
| Option | Description |
|---|---|
| Default language | Set the preferred language for the system. Mividas Rooms uses the browser’s language setting if available; otherwise, it defaults to the language set here. |
| Timezone | Set the preferred time zone for the system. |
Other settings
| Option | Description |
|---|---|
| Incoming SMTP port | Set your incoming SMTP port. Listens to incoming meeting e-mail invites on this port, e.g. for OBTP. |
| Disable SMTP service | Disables the SMTP service. |
| Incoming Mividas Proxy client port | Set your incoming port for Mividas Proxy. Listens for authorized clients on this port. |
| Disable Proxy service | Disables the Proxy service. |
Outgoing Email Settings (SMTP)
Configure SMTP details for email notifications and invitations. If you configured this during the initial Installer setup, fields will be pre-filled but can be modified as needed.
| Option | Description |
|---|---|
| Display-name of sender | Enter the name to appear as the email sender. |
| Sender email-address | Enter the email address for outgoing messages (typically a no-reply address). |
| SMTP relay server hostname | Specify the SMTP server’s hostname. E.g. smtp-server.example.com. |
| TLS mode | Choose your preferred TLS mode. |
| Port | Specify the SMTP server port. E.g. 25. |
| Username | Enter the SMTP username. |
| Password | Enter the SMTP password. If no password is needed, enter a hyphen. |
Optional Settings
OIDC (OpenID Connect) provider settings
| Option | Description |
|---|---|
| Enable | Enable OIDC provider support. |
| Select existing certificate | Select any already uploaded certificate to use with OIDC. |
| Click to open a new window where you Manage certificates. | |
| Remove optional setting | Check this box and click save to remove the settings. |
LDAP authentication settings
| Option | Description |
|---|---|
| Server | Enter the hostname of the current LDAP or AD server to use by default. Use “fqdn:389” to use a specific port. |
| Service account DN/username | Here you enter the path to the account to be used as a service account. The path is often unique to your particular organization. |
| Password | Enter the password for your LDAP or AD server. The field will get empty after pressing save. |
| Use LDAPS-connection | Connect to the server using SSL-based LDAPS-connection (port 636 by default). Make sure you have added any custom CA-certificates to make verification work. |
| Ignore TLS/SSL verification errors | Ignore TLS CA verification. TLS over regular LDAP port 389 may be used even if LDAPS is not enabled so unless you have added custom CA certificates for verification login may fail. |
| Disable referral chasing | Referrals occur when the queried server doesn’t have the requested information but points the client to another server that might. The client can then “chase” these referrals to retrieve the needed data. |
| Base dn | Specify where in the tree the initial search for results should begin. |
| User filter | Here you choose how users are filtered out and displayed. |
| End user group DN | Specify which group in the tree that will have access to the system and be able to use the product. |
| Admin group DN | Specify which group in the tree will have elevated admin rights in the system, which opens up additional settings and functions for the logged-in user. |
| Superuser group DN | Specify which group in the tree that will give members superuser status (highest). Use this with caution as these users will have full control over the system and should only be assigned to users with high technical knowledge. |
| Customer attribute | For dynamic multi-tenant Mividas Meeting Portal use. User LDAP-object attribute that contains customer shared keys, e.g. "customerAttribute". |
| Enable local accounts | Allow logging in to users added to the local user database. |
Separate domain name for video conference system requests
Use separate domain name for endpoint HTTP communication (events, firmware, passive provisioning etc). Allows for separate access rules in firewall/load balancers.
| Option | Description |
|---|---|
| Hostname / FQDN | Enter the Hostname/FQDN you wish to use. |
| Select existing certificate | Choose one of you previously uploaded certificates to be used. |
| Public SSL-certificate | Choose a Full chain PEM-formatted certificate bundle to upload. |
| Private key | Choose the private key of the above chosen certificate to upload. |
Separate domain name for incoming SMTP invites
You have the option to specify a separate domain to use for conference system email addresses. This is used, among other things, to redirect e-mails through external spam filters.
| Option | Description |
|---|---|
| Hostname / FQDN | Enter the Hostname/FQDN you wish to use. |
| Select existing certificate | Choose one of you previously uploaded certificates to be used. |
| Public SSL-certificate | Choose a Full chain PEM-formatted certificate bundle to upload. |
| Private key | Choose the private key of the above chosen certificate to upload. |
SAML SSO settings
| Option | Description |
|---|---|
| Entity URI to pass to SAML server | This will normally be the address to the product you are setting this up for, e.g. https://core.example.com Ensure this name is exactly the same as configured in idp configuration as “Identifier” for the Relaying Party Trust! |
| URL to autoconfig metadata XML-file | The URL that is used for the product to automatically get the metadata XML-file. Example for ADFS: https://<ADFS server FQDN>/FederationMetadata/2007-06/FederationMetadata.xml Example for Keycloak: https://<Keycloak server FQDN>/auth/realms/<REALM>/protocol/saml/descriptor |
| Offline idP metadata XML | This is only needed if auto configuration is not used. Paste the iDP metadata XML in the text field. |
| Offline SP metadata XML | This is only needed if auto configuration is not used. Paste the SP metadata XML in the text field. |
| Select existing certificate | Choose one of you previously uploaded certificates to be used for encryption and signing of requests. |
| Sign SSL-certificate | If you have not yet uploaded a certificate that can be selected in the previous step, choose a Full chain PEM-formatted certificate bundle to upload. |
| Sign private key | Choose the private key of the above chosen certificate to upload. |
| Username claim | SAML Claim to use for creating the username. For Cisco Meeting Server installations, this should correspond to the username in CMS (jid). Structure: <saml_claim_name>[/<search>/<replace>]. Example: email/example.org/video.example.org |
| Group/role/memberOf SAML claim | SAML Claim where you get the Group/role/memberOf to determine if the login is for a regular user, administrator or Superuser. What to enter here varies a lot depending on what service you use. Example: OU=Groups,DC=example,DC=com |
| Group/role claim value required for regular users | Enter the path for the group/role that is required for regular users. Example: CN=regular-users,OU=Groups,DC=example,DC=com |
| Group/role claim value required for admin-users | Enter the path for the group/role that is required for admin-users. Example: CN=admin-users,OU=Groups,DC=example,DC=com |
| Group/role claim value required for superuser-users | Enter the path for the group/role that is required for superusers-users. Example: CN=superusers-users,OU=Groups,DC=example,DC=com |
| Customer SAML claim | SAML Claim used in multi-tenant installations, to determin if the login is for a specific Customer. |
| Enable single log out (SLO) | Single Logout (SLO) results in all user sessions being terminated simultaneously for the browser that initiated the logout. Closing all user sessions prevents unauthorized users from accessing resources at the Mividas products (SPs). |
| Enable local accounts | Allow logging in using username/password (using backend admin or API) with local accounts. |
| Enable debug-mode | Print more information in logs, good for troubleshooting. |
Save configuration
When you have filled in everything needed for your installation, or just want to save your progress, you need to save theese settings. Do so by clicking in the bottom left corner.
Deployment
Select Version and Deploy
After everything is configured it is time to deploy Mividas Rooms. Choose the Mividas Rooms version from the drop-down list
, then click
. A terminal window will display the installation progress. Once completed, reload the page to verify the correct version.
rooms_epm: Running 15/18
rooms_epm: Running 15/18
rooms_epm: Running 16/18
rooms_epm: Running 18/18
Finished
Reload
Update settings post-deployment
To update settings after deployment, select Mividas Rooms from the start screen and click . Adjust settings as needed, save changes, and redeploy by clicking .
Following these steps, you can complete the Mividas Rooms configuration and deployment while retaining the flexibility to update settings as requirements evolve.
Upgrade
Before upgrading
Before upgrading, we always recommend that you:
- Check your platform health and fix any current alerts affecting your installation.
- Check that you have disk space available.
- Take a snapshot of your installation in your hypervisor.
Upgrading
To upgrade, click
next to Mividas Identify from the start screen. Select the version you wish to upgrade to in the drop-down list
, and then click
.
1.2. Onboarding
Onboarding wizard
When you visit the Mividas Rooms for the first time, you are welcomed by the onboarding wizard.
1. Organization setup

| Option | Description |
|---|---|
| Organization | Enter the name of the default organization that will represent your Mividas Rooms installation, then click . |
2. Choose password

| Option | Description |
|---|---|
| New password | Choose a password for the user “mividas_fallback”. Please document this password. |
| New password confirmation | Type the password again to verify it. |
| Proceed | Click to finish the setup. You can now proceed to manage and configure video conferencing systems within the platform. |
1.3. Dashboard

The Mividas Rooms dashboard provides a summary of the current status of your video systems.
The top of the dashboard provides a summary of the video conferencing systems connected to your Mividas Rooms installation. You can click any panel to see more details.
| Page actions | |
|---|---|
| Help (
) – Opens the configuration wizard. Update ( ) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
Page widgets
1.4. Systems

The Systems section in Mividas Rooms covers everything from adding and managing systems to tracking their status and history. It provides a structured approach to system administration, starting with an overview of connected systems and their details.
The process of adding and approving new systems ensures controlled expansion, while queue history keeps track of past actions. With tools for configuration, monitoring, and task management, this section helps maintain a well-organized and efficient system environment.
1.4.1. Overview

From within Mividas Rooms, select Systems via the main navigation in the left sidebar to get an overview of all of the currently available video conferencing systems. From this page you can also add new systems, approve systems that have been entered with a passive url, and view the actions that have already been, or are queued to be, applied to systems.
| Page actions | |
|---|---|
| Allows you to add a system. | |
| Allows you to add multiple systems, either manually or by importing from an Excel file. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
Systems list

- (
) – Displays the status of the system.
- (
) – The system is online (direct connection). - (
) – The system is online (passive connection). - (
) – The system is online (proxied connection). - (
) – The system is offline (direct connection). - (
) – The system is offline (passive connection). - (
) – The system is offline (proxied connection). - ( ) – Unknown status
- ( ) – The system is in a call.
- ( ) – the system has an active meeting.
- ( ) – The system has a connection or authentication error.
- (
- Name – The name of the system and its type.
- URI – The URI of the system.
- IP – The IP of the system.
- Serial number
– Allows you to choose what to show in this column.
- Serial number – The serial number of the system.
- Model – The model of the system.
- Group – The group of the system.
- Firmware – The firmware installed on the system.
- MAC address – The MAC address of the system.
- E.164 – The E.164 alias of the system.
- H323 – The H.323 alias of the system.
- Location – The location of the system.
- ID in inventory systems – The ID of the system in the inventory.
- ( ) – Displays if there is an active alert on the system.
Bulk actions
Selecting one, multiple or all meeting rooms will show bulk actions:
Grouping filter
The systems list also includes a grouping feature that allows you to display systems based on specific groups, such as Organization, System Type, Model, Location, Status, and/or Connection. The grouping feature is available in the right sidebar on wider screens or by clicking the group button
on smaller screens.
Create report

By selecting one or more systems from the system list, you can choose the bulk action a detailed report by querying their live status, configuration, and custom attributes. For example, it could be used to compare specific settings across multiple systems or to export specific values.
Base system

Choose which of the selected endpoints to use as the “base system.” The available status and configuration keys shown in the tree (right menu) are loaded from this endpoint’s API, since different endpoint models may expose different fields.
Load template

Lists previously saved report templates with their chosen name and the number of settings applied within the template.
| Option | Description |
|---|---|
| Populates the field selection tree (right menu) with the template’s saved choices. | |
| Opens a read-only preview of the template’s included fields grouped by category. | |
| Allows you to click to delete the template. |
Search and add settings

Search for any information you wish to base your report on, and the tree will filter the results based on what you type. Check the boxes to select them. To manually add entries, click .
Add manual entries

Enter the entries you wish to use, one per line.
Example, Status:Audio > Volume
Example, Configuration:Configuration > Audio > Microphones > NoiseRemoval > Mode
Create template and/or report

After at least one setting has been selected, you can choose to create a template or a report.
| Option | Description |
|---|---|
| Cancel the report creation. | |
| Save your currently selected settings to a template so they can be easily reused. | |
| Create a report based on your currently selected settings. |
Report created

| Option | Description |
|---|---|
| View system vertically | Toggle to swap the X and Y axes for the systems. |
| Export your report to Excel. | |
| Close the report. | |
| Go back and create a new report. |
In Mividas Rooms queue view, an overview of all actions provisioned to systems is provided, with the option to rerun them and view more details for each individual action.
| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Action – An ID number is assigned to each action, If an event has multiple tasks, you will see multiple rows with the same Action ID
- ID – Event ID on each action.
- System – Displays the system name.
- Type – Displays what type of action is performed.
- Users – Displays the user responsible for the action.
- Status – Displays the status of the action:
- ( ) – The action is being performed.
- ( ) – The action was successful.
- ( ) – The action failed.
- ( ) – The action was canceled.
- Created – The date and time of when the action started.
In cases where provisioning details have been manually entered for a system, they will need to be approved in Mividas Rooms through this view. There is also an option to specify IP ranges for systems that should be automatically registered via the settings.
| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
| Option | Description |
|---|---|
Takes you to Mividas Rooms > Admin > Settings > General. |
List of systems

- ID – Increasing number of every system
- Name – Displays the name of the system.
- IP – Displays the system’s IP address.
- Created – Displays the date and time of creation
| Option | Description |
|---|---|
| Approve the system and open up a form you can edit before adding it. | |
| Remove the system. |
If a system is missing, check that:
- CA certificates for this server are uploaded to the system or that TlsVerify=Off.
- A system with the same MAC address/serial number is not already installed or IP series automatically accepted.
- The system supports the TLS version that this server is set to use.
- There are no network-related issues along the way – e.g. firewall, routing, load balancer, split DNS.
Approve system form

Note: This option will only set the name for the system in Mividas Rooms, to change the name for the system itself you will need to provision the dialing properties. Note: Proxy requires that the tenant has a Mividas Proxy deployed and configured. Note: If a passive connection is used the MAC address will be received first after the system has been approved. Note: If a passive connection is used the serial number will be received first after the system has been approved.
Option
Description
Name
The system unit name displayed in Mividas Rooms list of endpoints and in the address book.
Type of system
Choose the type of system:
Cisco System, Cisco system using Webex API, Other (list only).
Username 1
Enter the username for the system.
Sign in with default password 1
If this option is checked, Mividas Rooms will try to add the system with one of the passwords specified under
Mividas Rooms > Admin > Settings > Security. To add the password manually instead, uncheck this checkbox.
Enter password manually 1
Enter the password manually. Only shows if the default checkbox is unchecked.
IP address
Enter the IP address of the system.
Port to the Web interface 1
Enter the port that is used for the systems web interface.
Full DNS hostname 1
Enter the FQDN of the system. The FQDN will take precedence over the IP address.
Update IP data automatically when sent from system
Check this option if you want Mividas Rooms to acknowledge and track IP address changes for the selected endpoint.
Type of connection
Choose if the endpoint is accessible directly from Mividas Rooms, through Proxy or passive provisioning.
Validate SSL connection
Check this option if you wish to validate the SSL connection between Mividas Rooms and the system.
MAC address
This will be automatically filled in when the system connection is active. You can also specify the MAC address in advance so that the correct system is connected to Mividas Rooms for passive provisioning.
Serial number
This will be automatically filled in when the system connection is active. You can also specify the serial number in advance so that the correct system is connected to Mividas Rooms for passive provisioning.
Location
Choose a location for the system. This can be used for filtering and analytics.
Organization unit
Choose a organization unit for the system. This can be used for filtering and analytics.
Number of seats in room
Set the number of seats in the physical meeting room. This value will be used for analytics and will show the efficiency of that particular meeting room.
Allow storage of sensor data
Enabling this option allows Mividas Core/Mividas Rooms to store sensor data from the Cisco endpoint. This setting does not disable or impact any functionality of the Cisco system.
Personal system
Check this box if the system is a personal system. This will disable the people count for the system for privacy reasons.
External mailbox
Specify a calendar e-mail address. Preparation for future update to connect systems to hybrid calendar mailboxes to enable OBTP using e-mail instead of directly contacting the system.
Standard type of scheduling from Portal
Choose what the the standard type of scheduling should be.
Dial out from meeting room + OBTP, OBTP, Dial out from system, No booking.
ID in inventory systems
If an organization uses, for example, inventory numbers, this ID can be added as metadata. This can be useful when a conference system is replaced, requiring an update to a new ID, or when a device is decommissioned, necessitating the removal of an ID.
Service reference
Manually added references, such as a service contract with Cisco.
Notes
Enter any notes for the system.
Press
to continue adding the system, or press
to cancel.
1. Not available for Cisco systems using Webex API.
1.4.4. Adding systems

This topic describes how to add your video conferencing systems to be managed by Mividas Rooms, including how to import endpoint details in bulk from Cisco TMS or Excel, and how to approve new systems.
If Cisco TMS and Mividas Rooms co-exist during a trial process or migration, you should disable the Enforce management settings on systems option in the TMS Services section on Cisco TMS. Otherwise, Cisco TMS may overwrite various settings.
From within Mividas Rooms, select Systems via the main navigation in the left sidebar to get an overview of all of the currently available video conferencing systems.
| Page actions | |
|---|---|
| Allows you to manually add a single system. | |
| Allows you to add several systems, either manually or by importing from an Excel file. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
Add a single system
Note: This option will only set the name for the system in Mividas Rooms, to change the name for the system itself you will need to provision the dialing properties. Note: Proxy requires that the tenant has a Mividas Proxy deployed and configured. Note: If a passive connection is used the MAC address will be received first after the system has been approved. Note: If a passive connection is used the serial number will be received first after the system has been approved.
Option
Description
Name
The system unit name displayed in Mividas Rooms list of endpoints and in the address book.
Type of system
Choose the type of system:
Cisco System, Cisco system using Webex API, Other (list only).
Username 1
Enter the username for the system.
Sign in with default password 1
If this option is checked, Mividas Rooms will try to add the system with one of the passwords specified under
Mividas Rooms > Admin > Settings > Security. To add the password manually instead, uncheck this checkbox.
Enter password manually 1
Enter the password manually. Only shows if the default checkbox is unchecked.
IP address
Enter the IP address of the system.
Port to the Web interface 1
Enter the port that is used for the systems web interface.
Full DNS hostname 1
Enter the FQDN of the system. The FQDN will take precedence over the IP address.
Update IP data automatically when sent from system
Check this option if you want Mividas Rooms to acknowledge and track IP address changes for the selected endpoint.
Type of connection
Choose if the endpoint is accessible directly from Mividas Rooms, through Proxy or passive provisioning.
Validate SSL connection
Check this option if you wish to validate the SSL connection between Mividas Rooms and the system.
MAC address
This will be automatically filled in when the system connection is active. You can also specify the MAC address in advance so that the correct system is connected to Mividas Rooms for passive provisioning.
Serial number
This will be automatically filled in when the system connection is active. You can also specify the serial number in advance so that the correct system is connected to Mividas Rooms for passive provisioning.
Location
Choose a location for the system. This can be used for filtering and analytics.
Organization unit
Choose a organization unit for the system. This can be used for filtering and analytics.
Number of seats in room
Set the number of seats in the physical meeting room. This value will be used for analytics and will show the efficiency of that particular meeting room.
Allow storage of sensor data
Enabling this option allows Mividas Core/Mividas Rooms to store sensor data from the Cisco endpoint. This setting does not disable or impact any functionality of the Cisco system.
Personal system
Check this box if the system is a personal system. This will disable the people count for the system for privacy reasons.
External mailbox
Specify a calendar e-mail address. Preparation for future update to connect systems to hybrid calendar mailboxes to enable OBTP using e-mail instead of directly contacting the system.
Standard type of scheduling from Portal
Choose what the the standard type of scheduling should be.
Dial out from meeting room + OBTP, OBTP, Dial out from system, No booking.
ID in inventory systems
If an organization uses, for example, inventory numbers, this ID can be added as metadata. This can be useful when a conference system is replaced, requiring an update to a new ID, or when a device is decommissioned, necessitating the removal of an ID.
Service reference
Manually added references, such as a service contract with Cisco.
Notes
Enter any notes for the system.
Press
to continue adding the system, or press
to cancel.
1. Not available for Cisco systems using Webex API.
Add multiple systems
Manually
| Option | Description |
|---|---|
| Choose some default settings that will apply to all the systems you are about to add. The options are:
Update IP data automatically when sent from the system – Check this option if you want Mividas Rooms to acknowledge and track IP address changes for the selected endpoint. |
- Product family – Choose the type of system:
Cisco System,Cisco system using Webex API,Other (list only).
- Name – The system unit name displayed in Mividas Rooms list of endpoints and in the address book.
Note: This option will only set the name for the system in Mividas Rooms, to change the name for the system itself you will need to provision the dialing properties.
- IP – Enter the IP address of the system.
- Username – Enter the username for the system.
- Password – If this option is checked, Mividas Rooms will try to add the system with one of the passwords specified under
Mividas Rooms > Admin > Settings > Security. To add the password manually instead, uncheck this checkbox. - Seats – Set the number of seats in the physical meeting room. This value will be used for analytics and will show the efficiency of that particular meeting room.
- MAC – This will be automatically filled in when the system connection is active. You can also specify the MAC address in advance so that the correct system is connected to Mividas Rooms for passive provisioning.
Note: If a passive connection is used the MAC address will be received first after the system has been approved.
- Serial number – This will be automatically filled in when the system connection is active. You can also specify the serial number in advance so that the correct system is connected to Mividas Rooms for passive provisioning.
Note: If a passive connection is used the serial number will be received first after the system has been approved.
- Organization inherence – Choose an organization unit for the system. This can be used for filtering and analytics.
- Hostname – Enter the FQDN of the system. The FQDN will take precedence over the IP address.
- Location – Choose a location for the system. This can be used for filtering and analytics.
- SIP – Enter the SIP URI of the system.
- H.323 – Enter the H.323 ID of the system.
- E.164 – Enter the E.164 alias of the system.
- Person’s e-mail address – Connect the system to a user. Will be used to automatically list systems belonging to a user in the scheduling portal (if applicable).
- External mailbox – Specify a calendar e-mail address. Preparation for future update to connect systems to hybrid calendar mailboxes to enable OBTP using e-mail instead of directly contacting the system.
- ID in inventory systems – If an organization uses, for example, inventory numbers, this ID can be added as metadata. This can be useful when a conference system is replaced, requiring an update to a new ID, or when a device is decommissioned, necessitating the removal of an ID.
- Service reference – Add a service contract reference if applicable.
- Service valid until – Manually enter this system’s service contract end date.
- Notes – Enter any notes for the system.
From Excel
Choose an Excel file to import. The file format does not need to match the form precisely; instead, you map each column in the file to the corresponding column.
This section provides a comprehensive view of system performance, health, and configuration. It combines real-time monitoring, status tracking, and remote management tools, ensuring systems run smoothly.
It offers full control over system operations, from overseeing key metrics and configurations to executing commands and managing backups. Task queues and provisioning streamline workflows, keeping everything efficient and responsive. Altogether, these features create a centralized space for maintaining and optimizing system functionality.
1.4.5.1. Overview

Each system has its own dashboard displaying relevant information, sensor values, call control, call history, and much more.
Page actions
| Page actions | |
|---|---|
| Allows you to edit the system. | |
| Debug (
) – Takes you to debug data for the system. Update ( ) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. – Delete the system. |
Control bars
Quick control bar

| Option | Description |
|---|---|
| Enter or search for an address to call. | |
| Click to call the entered address. | |
| Toggle mute.
|
|
| Set the volume on the system. | |
| Restart the system. |
In call control bar
This bar is only displayed when the system is in a call.

| Option | Description |
|---|---|
| Hang up the current call. | |
| Send DTMF signals. |
In meeting control bar
This bar is only displayed when the system is in a meeting within Mividas.

| Option | Description |
|---|---|
| Takes you to the scheduled meeting it is a part of. |
Widgets and lists
Widgets
System information

This list displays various information about the system and varies depending on its settings. The following information can be displayed: Name, Organization, Location, Connection, Dial-in protocol, Standard type of scheduling from portal, System has active macros, HTTP/HTTPS mode.

- Type – Displays the severity of the alert:
- – Indicates a severe failure that requires immediate attention. The system might be unusable or crashing.
- – Signals that the system might not operate fully, immediate action might be required, but the system can still run.
- – Something unexpected happened, or a potential issue was detected. The system is working, but attention is needed.
- – Normal operational messages that indicate system status or changes. No action required, just for tracking purposes.
- – Debug. Debug level will probably never be enabled by the remote systems but the option is left if that would change.
- – Mividas Rooms is unable to determine the severity level of the notification.
- Details – Displays the error message.
| Option | Description |
|---|---|
| Hides and acknowledges the alert for the system until it is triggered again. | |
| Takes you to Monitoring with this system applied as a filter. |

This list displays technical information about the system: Type, Model, MAC address, Serial, Firmware.
Room usage

This graph displays the number of seats in the room and the number of people in that room.
(
) – Shows the total number of seats in the room.
(
) – Shows the total number of people in the room at the time.
Peripherals

This list displays all peripherals connected to the system. Clicking expands that peripheral with details.
Example: Cisco Room Navigator

- Network address – Displays the Cisco Room Navigator’s IP address.
- Serial number – Displays the Cisco Room Navigator’s serial number.
- Firmware – Displays the Cisco Room Navigator’s current firmware version.
- Status – Displays the current status of the Cisco Room Navigator.
Example: Samsung TV

- Monitor role – Displays the monitor’s role;
First,Second. - Screen size – Displays the monitor’s screen size. E.g.
43. - Preferred format – Displays the monitor’s preferred format. E.g.
3840x2160@30Hz. - Serial number – Displays the monitor’s serial number. E.g.
12345678. - Model – Displays the monitor’s model.
- Manufacturer – Displays the monitor’s manufacturer.
Call history
To retrieve call history, click .

When you hover one of the calls, two buttons appear.
| Option | Description |
|---|---|
| Opens details about the call. | |
| Call the address. |
Upcoming meetings

When you hover the upcoming meeting, a button appears.
| Option | Description |
|---|---|
| Takes you to the scheduled meeting. | |
| Takes you to Scheduled meetings with this system applied as a filter. |
The status tab within the system provides a list of all status values for the systems, similar to the one displayed in the systems’ web interface. It is also possible to create reports where selected status values are compared against other systems managed in Mividas Rooms.
| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
1.4.5.3. Configuration

The configuration tab within the system provides a list of configurations for the systems, similar to the one displayed in the systems’ web interface. Just like in the web interface, various configurations can be provisioned directly to the system or saved as templates for future use.
| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
Edit configuration

Search for the configurations you wish to edit, and select them by checking their checkboxes. When a checkbox is checked, you can edit the value of that configuration. You can add as many configurations as you like.

When you have selected all of your configurations, proceed by clicking .

Before you continue, make sure to review your configurations. When you are ready, click .
Create template

Search for the configurations you wish to include in your template and select them by checking their checkboxes. When a checkbox is checked, you can edit the value of that configuration, this will be the default value for that configuration. You can add as many configurations as you like.

When you have selected all of your configurations, proceed by clicking .

Before you continue, make sure to review your configurations. When you are ready, click . Choose a name for your template and then click .
Load template

To load a template on a system, click in the top right corner.

Select a template to add to the system by clicking its corresponding checkbox, then click to proceed or to cancel.
| Option | Description |
|---|---|
| View all the settings within the template. | |
| Delete the template. |


1.4.5.4. Commands

Through the command tab, commands are provisioned to the system. You have the option to either execute the command immediately or add it to a queue, allowing multiple commands to run sequentially in the system. It is also possible to save a list of commands as templates for future execution.
| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
| Option | Description |
|---|---|
| Search fo a command. | |
| Load a template. |
Run a command

- Command – The description of the command.
| Option | Description |
|---|---|
| Run the selected command. | |
| Add the selected command to the queue. | |
| Text | Enter the value needed for the command. In this case it is the message you wish to send, but it varies depending on the command. |
Run queue

| Option | Description |
|---|---|
| Queued commands | See all queued commands. |
| Review your queued commands before running them. | |
| Clear all queued commands. |
Review

- Command – The description of the command.
- Arguments – The value chosen for the command.
| Option | Description |
|---|---|
| Go back to the previous view. | |
| Apply and run all commands in the queue. | |
| Save the all chosen commands and their values as a template. | |
| Clear all queued commands. | |
![]() |
Switch the list between the Review list and the System list. In the review list, you can see all chosen commands; in the system list, you can see and choose which system(s) are selected to run the commands on. |
| Edit chosen command. | |
| Remove the chosen command. |
No commands available

The commands can only be loaded if the system is connected with a direct connection. In other cases, the list of commands needs to be added manually. Mividas Rooms will reuse previously uploaded lists of commands for other systems of the same type. For example, if you have uploaded a list of commands for a Cisco Desk Pro and afterward add another Cisco Desk Pro, it will use the already existing list of commands.
Manually update command specification
- Download file from system:
[System IP]/command.xml. To avoid format changes, use CTRL+S when saving the file. - Download file from system:
[System IP]/valuespace.xml. To avoid format changes, use CTRL+S when saving the file. - Upload command.xml that you saved in the previous step.
- Upload valuespace.xml that you saved in the previous step.
- Click to upload.
1.4.5.5. Variables

Variables are a powerful addition to macros, enabling dynamic content that can be set per system in Mividas Rooms. Through the system’s variables tab, you can specify which dynamic variables should have a different value for that specific system. For more information on how macros and variables work, see the Panels and Macros Variable documentation.
| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- ID – Displays the ID of the variable.
- Name – Displays the name of the variable.
- Type – Displays the type of the variable:
Text,Choices,Integer,Number,True / False,JSON. - Default value – Displays the variable’s default value.
- System value – Displays the system’s current value.
| Option | Description |
|---|---|
| Allows you to delete the namespace and all its variables. | |
| Allows you to activate the selected variable. | |
| Allows you to edit the selected varable. | |
| Allows you to delete the selected variable. | |
| Allows you to add a variable to this namespace. |
Through the backup tab, system settings can be both backed up and restored. Backups can also be downloaded for local storage.
| Page actions | |
|---|---|
| Click to create a backup. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Name – Displays the name of the backup file.
- Created – Displays the date and time of when the backup was created.
- Checksum – Displays the checksum of the backup file.
- Error – Displays any error if available.
| Option | Description |
|---|---|
| Download the backup file. | |
| Restore from the backup file. | |
| Delete the backup file. |
1.4.5.7. Queue

In the system’s queue view, an overview of all actions provisioned to the specific system is provided, with the option to rerun them and view more details for each individual action. Mividas Rooms also has a global queue and history of actions, which can be read more about here: Systems Queue / History.
| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Action – ID of the provisioning request. May contain multiple tasks
- ID – ID of this particular task
- Type – Displays the type of action.
- Users – Displays the user who created the action.
- Status – Displays the status of the action:
- ( ) – The action is being performed.
- ( ) – The action was successful.
- ( ) – The action failed.
- ( ) – The action was canceled.
- Created – Displays the date and time the action was created.
| Option | Description |
|---|---|
| Run the same action again. | |
| Shows detailed information about the selected action. |
1.4.5.8. Statistics

Through the system’s statistics tab, graphs are provided for relevant measurement data, based both on the system’s call history and various sensor values for systems that support this.
| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
Results
Widgets
Graphs
Total hours of system use per day

Number of people in the room per date

Number of people in the room per hour

Number of people in the room per day of the week

Sensors in the room per hours of the day

Sensors in the room per day of the week

Sensors in the room over time

1.4.5.9. Provisioning

In the system’s provisioning tab, there is an option to provision various features available through Mividas Rooms, including updating configurations, executing commands, changing passwords, setting up address books, macros, and much more.
| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
Update configuration
From a template


- Name – Displays the name of the template.
- Model – Displays which model(s) the template is for.
| Option | Description |
|---|---|
| Displays all configurations within the template. | |
| Load the template. |
When you load a template, it takes you to Review. For the changes to be made, you need to scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
From a system


-
– Displays the status of the system.
- (
) – The system is online (direct connection). - (
) – The system is online (passive connection). - (
) – The system is online (proxied connection). - (
) – The system is offline (direct connection). - (
) – The system is offline (passive connection). - (
) – The system is offline (proxied connection). - ( ) – Unknown status
- ( ) – The system is in a call.
- ( ) – the system has an active meeting.
- ( ) – The system has a connection or authentication error.
- (
- Name – Displays the name and type of system.
- URI – Displays the URI of the system.
Select a system and then click to load its settings; this will take you to Review. For the changes to be made, you need to scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Edit manually

| Option | Description |
|---|---|
![]() |
Select one of these categories to view all available configurations under it. |

- Option – The name of the configuration.
- Value right now – The current value of the configuration.
Check a configuration’s checkbox to edit its value. When you are ready, go to Review to ensure everything is as you want it. For the changes to be made, you need to scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Review

| Option | Description |
|---|---|
| Save the selected configuration and current values as a template. | |
| Clear everything from the review tab. | |
| Edit the value of the selected configuration- |
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Run custom command
From a template

- Name – The name of the template
- Model – The model(s) for the template.
| Option | Description |
|---|---|
| See the details of the template. | |
| Load the template. |
When you load a template, it takes you to Review. For the changes to be made, you need to scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Review

- Command – The command.
- Arguments – The arguments int he command.
| Option | Description |
|---|---|
| Clear everything from the review tab. |
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Subscribe to live updates
Check this box to enable the subscription to live updates. This will update Mividas Rooms immediately with new data, for example, when a call starts.
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Change password
Check this to update the password of the user on the system. You can either choose to use the default password or enter it manually.
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Change passive room analysis
| Option | Description |
|---|---|
| People count out of call 1 | Counts the people in the room even when there is no on-going call. |
| Detect presence 1 | Older system without people count may instead support to detect any present person in the room |
1. Not supported by all systems.
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Get previous statistics
Fetch any previous calls stored on the system and add it to call statistics. Note: this may take more than a minute for each system to generate the list and respond to the request.
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Set up passive provisioning
Check this box to enable passive provisioning. The system contacts Mividas Rooms periodically to see if any settings should be changed. Allows to control systems that are behind a firewall or in case of proxy errors.
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Use address book
Select an address book from Mividas Rooms to be used on the system.
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Use branding
Select a branding profile from Mividas Rooms to be used on the system.
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Upgrade firmware
Select a firmware from Mividas Rooms to upgrade or downgrade the system.
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Select Force installation to force the device to accept a software upgrade immediately, without giving users
a chance to acknowledge or postpone the update.
Install CA certificates
Check this box to install CA certificates from Mividas Rooms on to the system.
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Apply macros/panels
| Option | Description |
|---|---|
| Delete all existing macros/panels | Delete all existing macros/panels from the system. |
| Controls | Select one or more existing controls to add to the system. |
| Collection | Select one or more collections to add to the system |
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
Call settings
| Option | Description |
|---|---|
| System Name | See/update the system name. |
| SIP URI | See/update the system’s SIP URI. |
| SIP Display name | See/update the system’s SIP Display name. |
| H.323 ID | See/update the system’s H.323 ID |
| E.164 | See/update the system’s E.164 alias. |
| SIP Proxy | See/update the system’s SIP Proxy. |
| SIP Proxy username | See/update the system’s SIP Proxy username. |
| SIP Proxy password | See/update the system’s SIP Proxy password. |
| H.323 gatekeeper | See/update the system’s H.323 gatekeeper. |
| Register Systems in Webex | Select to register system in Webex. |
Scroll to the bottom right of the page and click to apply your changes directly, or click to schedule the change.
1.5. Monitoring

This section provides visibility into system performance and health. It offers an overview of monitored systems, allowing users to track individual system status and metrics in detail. With these tools, administrators can stay proactive, addressing potential issues before they impact performance.
1.5.1. Overview

| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Type – Displays the severity of the alert:
- – Indicates a severe failure that requires immediate attention. The system might be unusable or crashing.
- – Signals that the system might not operate fully, immediate action might be required, but the system can still run.
- – Something unexpected happened, or a potential issue was detected. The system is working, but attention is needed.
- – Normal operational messages that indicate system status or changes. No action required, just for tracking purposes.
- – For debugging purposes, some notifications may be generated by Mividas Rooms. Currently, there are no active debug notifications.
- – Mividas Rooms is unable to determine the severity level of the notification.
- Details – Displays the error message.
- Systems – Displays the total number of system having this problem:
| Option | Description |
|---|---|
| Ignores and hides this alert for all affected systems. | |
| Opens up the list of systems affected with this alert. |

- System – Displays the name of the system and its type.
- URI – Displays the URI of the system.
| Option | Description |
|---|---|
| Hides and acknowledges the alert for the system until it is triggered again. | |
| If the alert was previously Acknowledged, this activates and shows it again. | |
| Ignore and hide the alert for this system. |
1.5.2. Per system

| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- System – Displays the name and model of the system.
- ( ) – Displays the total number of Critical alerts per system.
- ( ) – Displays the total number of Error alerts per system.
- ( ) – Displays the total number of Warning alerts per system.
- ( ) – Displays the total number of Info alerts per system.
- ( ) – Displays the total number of Debug alerts per system.
- ( ) – Displays the total number of Unknown alerts per system.
- Acknowledged – Displays the total number of Acknowledged alerts per system.
| Option | Description |
|---|---|
| Opens up the system with more information about the alerts. |

- Type – Displays the type of alert.
- Details – Displays details about the alert.
- First seen – Date and time of when the alert was first triggered.
- Latest – Date and time of when the alert was triggered most recently.
| Option | Description |
|---|---|
| Hides and acknowledges the alert for the system until it is triggered again. | |
| If the alert was previously Acknowledged, this activates and shows it again. | |
| Ignore and hide the alert for this system. |
1.5.3. Ignored

| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Type – Displays the severity of the alert:
- – Indicates a severe failure that requires immediate attention. The system might be unusable or crashing.
- – Signals that the system might not operate fully, immediate action might be required, but the system can still run.
- – Something unexpected happened, or a potential issue was detected. The system is working, but attention is needed.
- – Normal operational messages that indicate system status or changes. No action required, just for tracking purposes.
- – For debugging purposes, some notifications may be generated by Mividas Rooms. Currently, there are no active debug notifications.
- – Mividas Rooms is unable to determine the severity level of the notification.
- Details – Displays details of the error message.
- Applies to all – Enable this to apply the ignoring to all systems.
- Systems – Displays the total number of systems the ignore is applied to. Displays if it applies to all systems.
- Created – Displays the date and time for when the
| Option | Description |
|---|---|
| Removes the ignore of the alert.
If the alert has been reactivated manually, it must trigger again for it to be visible. |
|
| Opens up the alert to show more information. |

- System – Displays the name and type of system.
- Created – Displays the date and time when the alert was created.
| Option | Description |
|---|---|
| Hides and acknowledges the alert for the system until it is triggered again. |
1.6. Address books

| Page actions | |
|---|---|
| Allows you to add an address book. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Name – Displays the name of the address book.
- Type – Displays the typ of the address book,
ExternalorManual.
1.6.1. Add address book

To add an address book, click on in the top right corner.
Add a manual address book

- Name – Enter the name of your address book.
Click to add it or to cancel.
Add a external address book

- Name – Enter the name of your address book.
- External Address Book – Check this to make it a external address book.
- Search URL (TMS SOAP) – Enter the URL to the address book.
- External Editing URL – Enter the URL to where you can edit the address book.
Click to add it or to cancel.
1.6.2. Manage address book

The Address Books section in Mividas Rooms focuses on efficiently managing contact directories. It covers both manual and synchronized entries, allowing users to add, edit, and organize contacts as needed. Manual groups provide a way to structure entries, while synchronized sources ensure seamless integration with external directories. Whether maintaining individual contacts or syncing with larger databases, this section streamlines address book management for better accessibility and organization.
1.6.2.1. Content

| Page actions | |
|---|---|
| Displays the URL to this address book. | |
| Download (
) – Download the address book. Update ( ) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Title – Displays the name of the entry.
- Group – Displays which group the entry is in.
- External – If the entry is external, it displays a ( ).
- SIP – Displays the entry’s SIP URI.
- (
) – Allows you to choose what information to show in the column:
- H323 – Displays the H323 ID of the entry.
- E.164 – Displays the E.164 alias of the entry.
- Phone number – Displays the phone number of the entry.
- E-mail address – Dispalys the e-mail address of the entry.
1.6.2.2. Edit manual entries

Page actions
Allows you to manually add a entry.
Allows you to add several entries, either manually or by importing from an Excel file.
Download (
) – Download the address book.
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
Add an entry
| Option | Description |
|---|---|
| Name | Enter a name for the entry. |
| Description | Enter a description for the entry. |
| Group | Choose a group that the entry belongs to. |
| SIP | Enter the SIP URI of the entry. |
| H.323 | Enter the H.323 ID of the entry. |
| E.164 | Enter the E.164 alias of the entry. |
| Phone number | Enter a phone number for the entry, usually someone responsible for the entry. |
| E-mail address | Enter an e-mail address for the entry, usually someone responsible for the entry. |
Click to add it or to cancel.
Add multiple entries
Manually

| Option | Description |
|---|---|
| Choose some default settings that will apply to all the entries you are about to add. The options are: Group – Select or add a group that will apply to all entries added. Overwrite Posts – All manual entries will be removed before the new entries are added. |
- Name – Enter a name for the entry.
- Description – Enter a description for the entry.
- SIP – Enter the SIP URI of the entry.
- H.323 – Enter the H.323 ID of the entry.
- E.164 – Enter the E.164 alias of the entry.
- Phone number – Enter a phone number for the entry, usually someone responsible for the entry.
- Group – Choose a group that the entry belongs to.
- E-mail – Enter an e-mail address for the entry, usually someone responsible for the entry.
From Excel
Choose an Excel file to import. The file format does not need to match the form precisely; instead, you map each column in the file to the corresponding column.
1.6.2.3. Manual groups

| Page actions | |
|---|---|
| Allows you to manually add a group. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
| Search | Description |
|---|---|
| Allows you to search for a group. |

| Option | Description |
|---|---|
| Allows you to add a sub-group (child) to the chosen group. | |
| Allows you to edit or remove the chosen group. |
1.6.2.4. Synchronized sources

Page actions
Allows you to manually add a synchronized source.
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
- Description – Displays the description of the source.
- Subgroup – Displays the subgroup of the source.
- Last synchronized – Displays the date and time of when the last synchronization occured.
- Type of source – Displays the type of source.
| Page actions | |
|---|---|
| Allows you to remove a synchronized source. |
1.6.2.4.1. Add a synchronized source

To add a synchronized source, click the in the top right corner.
Add external source

Managed video conferencing systems
TMS
Copy manual entries from address book
CMS users
CMS VMR
VCS
Click to add it or to cancel.
1.7. Firmware

Page actions
Upload firmware.
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
- Version – Displays the version of the firmware.
- Global 1 – If this shows a it means that the software is available for all tenants.
- Filename – Displays the filename of the firmware.
- Product – Displays what product the firmware belongs to.
- Uploaded – Displays the date and time of when the firmware was uploaded.
1. Only available in multi-tenant installations.
To upload firmware, click the in the top right corner.
IMPORTANT: It is not possible to install .pkg files with API (Cisco limitation), please use the .cop.sgn file format instead.

| Option | Description |
|---|---|
| Select file | Select the firmware file to upload. |
| Models | Select what model this firmware belongs to. You can only select from models already added to your Mividas Rooms installation. The system will automatically fill this out after you select the firmware. |
| Version | The version of the selected firmware. The system will automatically fill this in after you select the firmware. |
| Show for all tenants 1 | Select if this firmware should be available for all tenants in this installation. |
1. Only available for installations with multi-tenants.
Click to upload the firmware or to cancel.
1.8. Scheduled meetings

| Page actions | |
|---|---|
| Press this button to add a scheduled meeting. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Title – Displays a meeting icon; ( ) is a one-time meeting and ( ) is a recurring meeting. It also shows the name of the meeting and who booked it. Clicking on the meeting name takes you to the scheduled meeting details page.
- Systems – Displays any systems added to the meeting.
- Status: Displays the following statuses for the meetings:
- The meeting has been held.
- The meeting has been deprovisioned.
- The meeting has been cancelled.
- The meeting is scheduled and upcoming.
- The meeting has started.
- In call: Indicates if the meeting has active participants.
- ( ) No participant is active.
- ( ) At least one participant is active.
- Start time – The date and time of the meeting start.
- End time – The date and time of the meeting end.
- Type – Displays the type of meeting.
1.8.1. Schedule a meeting

This feature is primarily intended for testing or troubleshooting, as these meetings cannot be edited. To add a scheduled meeting here, click the in the top right corner.
For booking meetings to support users and organizations, it is recommended to use the ‘Schedule on-behalf’ function available in the Mividas Portal. This feature allows support staff to book meetings on behalf of another user.

| Option | Description |
|---|---|
| Title | The name of the meeting. |
| Start time | The date and time when the meeting will start. |
| End time | The date and time when the meeting will end. |
| External SIP-URI | The external SIP URI you wish to dial out to. |
| Owner | The owner of the meeting. |
| Auto dial-out | Automatically dials the SIP URI from these room systems when the meeting starts. |
| Recurring meeting | Recurring meetings can be created using syntax that is compliant with the iCalendar RFC 5545 standard. E.g. RRULE:FREQ=WEEKLY;COUNT=2 |
Click to schedule the meeting or to cancel.
1.9. Panels and macros

The Panels and Macros section in Mividas Rooms focuses on customization and automation, enabling users to create tailored room controls and interactive panels. It provides tools for managing room control settings, organizing macros into collections, and tracking changes through a queue system. Variables offer additional flexibility, allowing dynamic adjustments to settings and behaviors. By combining these elements, administrators can enhance usability, streamline workflows, and optimize meeting room functionality.
1.9.1. Overview

| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Name – Displays the name of the system and its type.
- Room controls and collections – Displays which room controls and/or collections have been added to the system.
| Option | Description |
|---|---|
| Allows you to add a room control or collection to the system. | |
| Allows you to reinstall the selected room controls and collections on the system. |
1.9.2. Room controls

Page actions
Press this button to add a room control.
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
- Name – Displays the name and description of the room control.
- Type – Displays the type of room control, and/or .
- Files – Displays the total number of files within this room control.
- Variables – Displays the total number of variables within this room control.
| Option | Description |
|---|---|
| Edit the selected room control. | |
| Download the room control as a packaged bundle. | |
| Remove selected room control. |
Create collection

To create a collection, select 2 or more room controls, then click create collection in the bottom right corner.
To upload new room controls, click on in the top right corner.

| Option | Description |
|---|---|
| Title | Enter a title for your room control. |
| Description | Enter a description of your room control. |
| Files / ZIP | Files – Select the file(s) you wish to upload for Panel (.xml) and/or Macro (.js). ZIP – Select the ZIP bundle you wish to upload containing the Panel (.xml) and/or Macro (.js) files. |
| Automatically add variables from manifests | If uploading a zip file that contains a manifest.json, any supported variables specified in “userParams” will be automatically imported. |
Click to upload files, or to cancel.
1.9.2.2. Edit room controls

After you have created and uploaded panels and/or macros, you can edit them directly in Minidas Rooms.
Overview

| Option | Description |
|---|---|
![]() |
The number of files used in the configuration. |
![]() |
The number of panels used in the configuration. |
![]() |
The number of macros used in the configuration. |
![]() |
The number of systems that have the configuration enabled. |
| Title | The title of your configuration. |
| Requires version | Enter a valid version number spec list in ==X.Y.Z, >=A.B.C format. |
| Description | A description of your configuration. |
| Update the configuration with your latest changes. |
Files

| Option | Description |
|---|---|
| Select files | Controls whether a macro file is transpiled (ES6+ → ES5) before being uploaded to a Cisco endpoint. Transpilation is needed because older endpoint runtimes can’t execute modern JavaScript.
Auto – Auto-detect based on file content and endpoint runtime. |
| Click to upload selected file. | |
| Create a new file. | |
| Automatically add variables from manifest file | If uploading a zip file that contains a manifest.json, any supported variables specified in “userParams” will be automatically imported. |
| File | Displays the filename. |
| Type | Displays the type of file. |
| Enabled | Toggle to enable/disable the file. |
| Transpile | Controls whether a macro file is transpiled (ES6+ → ES5) before being uploaded to a Cisco endpoint. Transpilation is needed because older endpoint runtimes can’t execute modern JavaScrip.
Auto – Auto-detect based on file content and endpoint runtime. |
| Edit the file. | |
| Allows you to select from options:
(
) – Replace the file. |
Create a new file

| Option | Description |
|---|---|
| File extension | Select what type of file you want to create. |
| Filename | Set the filename. |
| Content | The content of your file. |
| Create the file. | |
| Create the file and choose which systems to install it on directly. | |
| Close without saving your file. |
Edit file

| Option | Description |
|---|---|
| File extension | Display the type of file. |
| Filename | Displays the filename. |
| Content | The content of your file. |
| Save the file. | |
| Save the file and choose which systems to install it on directly. | |
| Close without saving your changes. |
Systems

| Option | Description |
|---|---|
| Add a system to the list. | |
| After selecting one or more systems, click to reinstall the macro/panel on selected systems. | |
| After selecting one or more systems, click to remove system(s) from the list. | |
| Close this window. |
Variables

| Option | Description |
|---|---|
| Variable | The variable name, check the checkbox to enable the variable. |
| Type | Displays the type of variable. Click to see the details of the variable. |
| Required | If the checkbox is checked, the variable is required. |
| Save any changes made. | |
| Close this window. |
1.9.3. Collections

| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Name – Displays the name of the collection.
- Controls – Displays the total number of controls in the collection.
- Files – Displays the total number of files in the collection.
| Option | Description |
|---|---|
| Edit the selected collection. | |
| Download the collection as a packaged bundle. | |
| Remove selected collection. |
1.9.4. Queue

| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Action – ID of the parent action – e.g. provisioning request. May contain multiple tasks
- ID – ID of this particular task
- System – Displays the name of the system.
- Type – Displays the type of action.
- Users – Displays the user who created the action.
- Status – Displays the status of the action:
- ( ) – The action is being performed.
- ( ) – The action was successful.
- ( ) – The action failed.
- ( ) – The action was canceled.
- Created – Displays the date and time the action was created.
| Option | Description |
|---|---|
| Allows you to run the same action again. | |
| Shows detailed information about the selected action. |
1.9.5. Variables

| Page actions | |
|---|---|
| Press this button to add a new namespace and variable. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- ID – Displays the ID of the variable.
- Name – Displays the name of the variable.
- Type – Displays the type of the variable:
Text,Choices,Integer,Number,True / False,JSON. - Default value – Displays the variable’s default value.
| Option | Description |
|---|---|
| Allows you to delete the namespace and all its variables. | |
| Allows you to edit the selected variable. | |
| Allows you to delete the selected variable. | |
| Allows you to add a variable to this namespace. |
1.9.5.1. Add variable

To add a new namespace and variable, click on in the top right corner. To add a variable in to a namespace, click in the namespace list.
Add variable

| Option | Description |
|---|---|
| Namespace | Set the name of the namespace. If you clicked to add a variable to a namespace, this will be filled in with that namespace automatically. |
| ID | Variable name – alphanumeric and underscore. Same as the const/let/var-definition that is used in the macro source code. |
| Type | Choose your type of variable:
Text – A string of characters, such as words, sentences, or any alphanumeric input. E.g. |
| Name/description | Friendly name in Mividas Rooms |
Text
| Option | Description |
|---|---|
| Information | Description/comment about the field |
| Default value | Set the default value for this variable. |
| Minimum length | Set the minimum length for this variable |
| Maximum length | Set the maximum length for this variable. |
Choices
| Option | Description |
|---|---|
| Information | Description/comment about the field |
| Default value | Select the default value from the options below. |
| Add an alternative. This will open a new field where you set the Value and Label for that alternative. |
Integer
| Option | Description |
|---|---|
| Information | Description/comment about the field |
| Default value | Set the default value for this variable. |
| Minimum length | Set the minimum value for this variable |
| Maximum length | Set the maximum value for this variable. |
Number
| Option | Description |
|---|---|
| Information | Description/comment about the field |
| Default value | Set the default value for this variable. |
| Minimum length | Set the minimum value for this variable |
| Maximum length | Set the maximum value for this variable. |
True / False
| Option | Description |
|---|---|
| Information | Description/comment about the field |
| Default value | Default value of field (true/false) |
JSON
A
| Option | Description |
|---|---|
| Information | Description/comment about the field |
| Default value | Enter the default value. |
Click to create your variable or to cancel.
1.10. Sensors

The Sensors section in Mividas Rooms provides detailed metrics on room conditions and occupancy. It includes people counting to track attendance, temperature and humidity monitoring for climate control, and air quality measurements to ensure a comfortable environment. Historical data allows for trend analysis, helping organizations optimize space utilization, improve resource management, and maintain ideal meeting conditions.
1.10.1. Overview

| Page actions | |
|---|---|
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

- Name – Displays the name of the system and its type.
- People – Displays the number of people in the room and the room’s capacity.
- Temperature – Displays the current temperature in the room.
- Air quality – Displays the current air quality in the room.
- Humidity – Displays the current humidity in the room.
- Ambient noise – Displays the current ambient noise in the room.
- Noise – Displays the current noise in the room.
| Option | Description |
|---|---|
| Opens up a diagram with data from the last 7 days. See example below. |

1.10.2. People count

Page actions
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
-
– Changes depending on the status of the room:
- – The room is free.
- – The system in the room is offline.
- – The system in the room has an error.
- – The system is in a call, but no people are in the room.
- – The system is a call, and there are people in the room.
- – There are people in the room, but the system is not in a call.
- Name – Displays the name of the room and the system type.
- Status – Displays the current status of the room:
- Free – The room is free.
- Offline – The system in the room is offline.
- Error – The system in the room has an error.
- Ghost meeting – The system is in a call or has a scheduled meeting, but no people are in the room.
- Meeting – The system is a call, and there are people in the room.
- Occupied – There are people in the room, but the system is not in a call.
- People count – Displays the total number of people in the room and the number of seats.
1.10.3. History

Page actions
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
1.11. Call statistics

Page actions
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
Overview

Graph
Total hours of calls per day

Participants

List

- System – Displays the name of the system.
- URI – Displays the URI of the system.
- Hours – Displays the total amount of hours the system has been in calls.
- Calls – Displays the total number of calls made with the system.
| Option | Description |
|---|---|
| This system is applied as a filter. | |
| Takes you to the configuration page of that system. |
Group

List

- Group – Displays the name of the group.
- Hours – Displays the total amount of hours the group has been in calls.
- Calls – Displays the total number of calls made from this group.
| Option | Description |
|---|---|
| This group is applied as a filter. |
1.12. Admin
The Admin section in Mividas Rooms provides the essential tools for configuring and managing the platform. It covers system-wide settings, organizational structure, and branding customization, ensuring a tailored end-user experience. Integration options, such as Webex and calendar services, allow seamless connectivity with external tools.
Customer management and backend administration further streamline control, giving administrators full oversight of users, services, and system behavior. This section serves as the foundation for maintaining a well-organized and efficiently managed environment.
1.12.1. Settings

| Page actions | |
|---|---|
| Help (
) – Opens the configuration wizard for this page. Update ( ) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
General

| Option | Description |
|---|---|
| Address book for searches in the booking portal | Select one of your address books to be used when your are searching within Mividas Meeting Portal. |
| Address book for searches in Mividas Core | Select one of your address books to be used when searching within Mividas Core. If none is specified, the address book for searching in the booking portal is used. |
| First hour of night | Choose the first hour of nighttime in 24h format. Provisioning work that has been scheduled. |
| Last hour of night | Choose the first hour of nighttime in 24h format. Provisioning work that has been scheduled. |
| Automatically register new systems from these IP series | All systems on selected networks will automatically be approved when Mividas Rooms have been set up for provisioning from system-side. |
| Try to create active connection for automatically added systems | Will automatically try to create an active connection to the system after it has been automatically added. This will use the default password(s) set under the security tab. |
Click to save your settings, or to proceed to the next tab.
System defaults
System defaults is now a separate item in the Rooms admin menu. It defines the default configuration, specifications and provisioning behaviour applied to managed systems. See System defaults for the full documentation.
Security

| Option | Description |
|---|---|
| Default password | Set one or more default passwords that can be used when adding systems. |
| Enable debug reports for users without administrator rights | Allows for every user to use the debug reports without being an administrator. |
| Passive provisioning address key | Set the passive provisioning address key. |
| Proxy client passwords | Set the password for proxy client(s). |
| Load ‘Trusted CA Root Certificates’ from file | Allows you to upload trusted CA root certificates from file. |
| Trusted CA Root Certificates | Allows you to manually edit the trusted CA root certificates. |
Click to save your settings, or to proceed to the next tab.
Scheduled meetings

| Option | Description |
|---|---|
| Minutes in advance to view OBTP meetings | Set the number of minutes before the meeting starts so that the Join button should appear on the systems. |
| Allow email invitations from these domains |
Specify a list of domains to be accepted for email invitations. |
| Enable OBTP for Rooms | Enable or disable OBTP from Mividas Rooms for managed systems. |
| Enable OBTP from Core/Portal | Enable or disable OBTP from Mividas Core/Mividas Portal for managed systems. |
| Standard type of scheduling from Portal | Select your standard type of scheduling from Mividas Meeting Portal: Dial out from meeting room + OBTP, OBTP, Dial out from system, No booking. |
| External provisioning service URL | Resend all provisioning requests to an external server (beta). |
Click to save your settings, or to proceed to the next tab.
Sensor

| Option | Description |
|---|---|
| Temperature | Set the minimum and maximum threshold for temperature. |
| Air quality | Set the minimum and maximum threshold for air quality. |
| Humidity | Set the minimum and maximum threshold for humidity. |
| Ambient noise | Set the minimum and maximum threshold for ambient noise. |
| Noise | Set the minimum and maximum threshold for noise. |
Click to save your settings, or to save and go back to the beginning.
1.12.2. System defaults

The System defaults page defines the default configuration, specifications, and provisioning behavior that Mividas Rooms applies to managed systems. Setting these once means newly added systems inherit sensible defaults without having to configure each one by hand.
| Page actions | |
|---|---|
| Help (
) – Opens the configuration wizard for this page. Update ( ) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
General

| Option | Description |
|---|---|
| Default Address Book | Select one of your address books that should be added to all systems by default. |
| Default branding profile | Select one of your branding profiles that should be added to all systems by default. |
| HTTP Feedback Slot | Determines which HTTP feedback slot to use by default when subscribing to live updates is provisioned to the system. Each slot is unique to one provisioning system. Cisco TMS uses FeedbackSlot 3 by default. |
| Dial-in protocol | Select your default dial-in protocol. |
| Use proxy by default | Specify whether to use a proxy by default; note that this requires that you have at least one proxy connected to Mividas Rooms. Read more in the Proxy clients documentation. |
| Default SIP Proxy | Determines whether a default SIP proxy should be used when dialing properties are provisioned to systems. |
| Default SIP proxy user name | Enter the default SIP proxy user name. |
| Default SIP proxy password | Enter the default SIP proxy password. |
| Standard H323 Gatekeeper | Determines if an H.323 gatekeeper address should be pre-filled when dialing properties are provisioned to systems. |
When done, click to save, or to continue to the next tab.
Default settings

Define the default Specifications and Configuration per system category, applied to systems of that type. Two categories are available:
- Cisco systems – directly managed Cisco endpoints (grouped by model).
- Cisco system using Webex API – Cisco endpoints managed through the Webex API (grouped by model).
Category settings

Apply settings to all system types within this category.
| Option | Description |
|---|---|
| Commands | Upload a command.xml |
| Value specification | Upload a valuspace.xml |
| Configuration templates | Click and select a template. |
| Command templates | Click and select a template. |
Click to save/upload. Click to delete the current settings.
System type specific settings

Apply settings to a specific system type.
| Option | Description |
|---|---|
| Commands | Upload a command.xml |
| Value specification | Upload a valuspace.xml |
| Configuration templates | Click and select a template. |
| Command templates | Click and select a template. |
Click to save/upload. Click to delete the current settings.
Templates

Reusable configuration templates that can be applied to systems during provisioning. Use to narrow the list.
| Option | Description |
|---|---|
| Name | The template name |
| Model | The system model the template applies to. |
| View the template’s saved settings. | |
| Delete the template. |
Provisioning

Set the default provisioning options – the actions that are enabled by default on the systems provisioning tab.
| Alternative | Default value |
|---|---|
| Subscribe to live updates | On, Off or Standard. |
| Change passive room analysis | On, Off or Standard. |
| People count out of call | On, Off or Standard. |
| Detect presence | On, Off or Standard. |
| Install CA certificates | On, Off or Standard. |
| Provision base settings | On, Off or Standard. |
| Change password | On, Off or Standard. |
| Get previous statistics | On, Off or Standard. |
| Set up passive provisioning | On, Off or Standard. |
| Use address book | On, Off or Standard. |
| Use branding | On, Off or Standard. |
| Upgrade firmware | On, Off or Standard. |
| Apply macros/panels | On, Off or Standard. |
| Call settings | On, Off or Standard. |
When done, click to store the default provisioning options.
1.12.3. Organization tree

Page actions
Add a post.
Help (
) – Opens the configuration wizard for this page.
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
1.12.4. Branding profiles

Page actions
Add a branding profile.
Help (
) – Opens the configuration wizard for this page.
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
Add profile

To add a branding profile, click on in the top right corner.

Choose a name for your profile, click to continue or to cancel.

| Option | Description |
|---|---|
| Name | The name of the profile. Filled in from your previous step. |
| Background | The image will be displayed as a background on both the main screen and on the touch panel when the system is awake.
Recommendation: 3840x2160px. PNG or JPEG. |
| Branding | The logo will be displayed in the bottom right corner on both the main screen and the touch panel. For best results, the logo should be all black/dark, without padding, and with a transparent background.
Recommendation: 272x272px. PNG or JPEG. (JPEG do not support transparent background) |
| Halfwake Background | The image will be displayed as a background on both the main screen and on the touch panel when the system is half-awake.
Recommendation: 3840x2160px. PNG or JPEG. |
| Halfwake Branding | The logo will be displayed in the bottom right corner on both the main screen and the touch panel. For best results, the logo should be all white/light, without padding, and with a transparent background.
Recommendation: 272x272px. PNG or JPEG. (JPEG does not support a transparent background) |
| Camera Background1 | The background image for the virtual camera in a webrtc meeting.
Recommendation: 1920x1080px. PNG or JPEG. |
| Scheduler Branding | The logo will be displayed in scheduler mode.
Recommendation: 272x272px. PNG or JPEG. |
| Scheduler Background | The image will be displayed as a background in scheduler mode.
Recommendation: 3840x2160px. PNG or JPEG. |
Click to finish adding your profile, or to cancel.
1.12.5. Proxy clients

Page actions
Update (
) – Allows you to manually update the current page.
Documentation (
) – Takes you to the relevant documentation.
Proxy client list

- (
) – Displays the status of the proxy client.
- ( ) – New proxy client that must be approved before connecting to Mividas Rooms.
- ( ) – The proxy client is online.
- ( ) – The proxy client is offline.
- Name – The name of the proxy client. Click on the name to edit the proxy client.
- IP – The IP of the proxy client.
- Last connection – Shows the time when Mividas Rooms last had contact with the proxy.
- Last checked – Shows the time when Mividas Rooms last checked for proxy connection.
- ( ) – Approve system to connect to Mividas Rooms. Note that for multi-tenants, the proxy client will be added for the customer you are currently managing.
- ( ) – Delete the proxy client.
Edit proxy client

| Option | Description |
|---|---|
| Name | Change the name of the proxy client. |
| Configure proxy connectivity for passive systems from these IP series | Enter the IP series for systems that should use this proxy client in passive mode. Tab-separated. E.g. 10.10.10.0/24. Use 0.0.0.0/0 for all. |
Status changes
The sidebar shows the latest status change for all proxy clients. Each entry shows the date, time, name, IP number, and status. Click on the name to edit the proxy client.
- – The proxy handshake was successful and the tunnel is validated as working.
- – A non-approved proxy made contact with Mividas Rooms.
- – The proxy contacted Mividas Rooms and started the handshake, but the tunnel could not be opened (most commonly due to firewall problems).
- – The proxy went offline.
The Integrations page manages external system integrations for Mividas Rooms. Two integration types are supported: Webex (sync Webex-registered devices) and Cisco Unified Communications Manager (CUCM) (sync devices registered to CUCM). Each integration synchronizes its systems into Mividas Rooms and shows a status indicator and the time of the last synchronization.
| Page actions | |
|---|---|
| Add an integration. Choose the type from the dropdown: Webex or Cisco Unified Communications Manager. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |

-
– Displays the status of the integration:
- – The integration is active.
- – The Integration is not active, last sync error.
- – Dispalys the ID of the integration.
- – Displays if the integration is automatically synchronized.
- – Displays the date and time of the last synchronization.
- – Displays the cuesomter fo this integration.
| Option | Description |
|---|---|
| Edit the integration. | |
| Manually synchronize. | |
| Update login. | |
| Expand the integration list. |

-
– Displays the status of the system.
- ( ) – The system is online (direct connection).
- ( ) – The system is offline (direct connection).
- ( ) – Unknown status
- ( ) – The system is in a call.
- ( ) – the system has an active meeting.
- ( ) – The system has a connection or authentication error.
- Name – Displays the type and name of the system.
- URI – Displays the URI of the system.
- Serial number – Displays the serial number of the system.
1.12.6.1. Add a Webex Integration

To add a new Webex integration, click in the top right corner.
The integration application is linked to your Webex account. It will stop working if it is disabled or if you change your password while the service application is used independently from your user. We strongly advise you to use the service application integration. Read more.
Add an Integration application

- Log in to developer.webex.com. You must use an admin account.
- Go to My Webex Apps -> Create a New App.
- Select Create an Integration. [Link]
- Create a new integration, and enter the value from the field visible in Mividas Rooms as the Redirect URI.

- Select the following Scopes:
- identity:placeonetimepassword_create
- spark-admin:devices_read
- spark-admin:devices_write
- spark-admin:people_read
- spark-admin:workspaces_write
- spark:xapi_commands
- spark:xapi_statuses
- Copy Client ID and Client Secret and paste them into their corresponding fields in Mividas Rooms.
| Option | Description |
|---|---|
| Client ID | Enter the Client ID from the steps described above. |
| Client Secret | Enter the Client Secret using the steps described above. |
| Instant onboarding of the Webex registered systems | All systems accessible via the Webex API will be added as Webex systems unless they are already hosted in Mividas Rooms. |
| Automatic synchronization | Same as above. Continues to run automatically at regular intervals, adding new Webex systems as they appear. |
Click to proceed or click to cancel.
Add an Service application

- Log in to developer.webex.com. You must use an admin account.
- Go to My Webex Apps -> Create a New App.
- Select Create a Service App. [Link]
- Select the following Scopes:
- identity:placeonetimepassword_create
- spark-admin:devices_read
- spark-admin:devices_write
- spark-admin:people_read
- spark-admin:workspaces_write
- spark:xapi_commands
- spark:xapi_statuses
- Copy Client ID and Client Secret and paste them into their corresponding fields in Mividas Rooms.
- Sign in to Webex Admin, and go to Apps > Service Apps to authorize your App. [Link]
- Find your Webex integration here: [Link]
- Select your organization, paste in Secret from the previous steps to generate Access Token and Refresh Token. Add them to the form below.
| Option | Description |
|---|---|
| Client ID | Enter the Client ID from the steps described above. |
| Client Secret | Enter the Client Secret using the steps described above. |
| Refresh token | Enter the Refresh token using the steps described above. |
| Access token | Enter the Access token using the steps described above. |
| Instant onboarding of the Webex registered systems | All systems accessible via the Webex API will be added as Webex systems unless they are already hosted in Mividas Rooms. |
| Automatic synchronization | Same as above. Continues to run automatically at regular intervals, adding new Webex systems as they appear. |
Click to proceed or click to cancel.
1.12.7. Calendar service

| Page actions | |
|---|---|
| Add a calendar service. | |
| Displays Powershell commands for you to change how calendar information is saved. Read more about what each command means here: docs.microsoft.com. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
| Search and filters | Description |
|---|---|
| Search for services. | |
| Reload the list with applied filters. | |
Filter by Customer. |

-
– Displays the status of the last synchronization.
- – The last synchronization was successful.
- – The last synchronization failed.
- Title – Displays the calendar service title.
- Type – Displays the calendar service type.
- Last sync – Displays the date and time of the last synchronization.
- Customer – Displays the customer of the calendar service.
| Option | Description |
|---|---|
| Edit the calendar configuration. | |
| Choose to:
(
) – Manage calendars. |
- This will run an incremental sync, synchronizing meetings only for the upcoming 24 hours.
- Only available for Graph.
1.12.7.1. Add Calendar service

To add a new Calendar service, click in the top right corner.
Add Exchange Web Services
Basic Auth
| Option | Description |
|---|---|
| Username | Enter the username. E.g. [email protected] |
| Password | Enter the password for the username typed above. |
| Service account SMTP address | If different from the username, enter the service account SMTP address. E.g. [email protected] |
| Exchange Server Host Name | Enter the exchange server hostname. Leave blank to find the correct server via auto-discovery. |
| Use autodiscover to retrieve additional settings | Autodiscovery may add delays or cause errors depending on DNS/firewall configuration, but it may help in scenarios where a static Server hostname is not possible. |
| Use impersonation | Use impersonation to get access to each calendar instead of delegation to the service account. Impersonation usually have higher throttling limits and will be a better option for large installations. It will however need additional permissions in Exchange/Office365.
Note: Impersonation requires OAuth login alt. ManagementRoleAssignment with Role:ApplicationImpersonation for the service account. If impersonation is not enabled (Delegation), then Set-ThrottlingPolicy is required. |
Click to save and process, or to cancel.
OAuth

- Log in to Office 365 > Admin. Go to Azure Active Directory
- Select App registrations. [Link]
- Create a new app registration. Leave the single tenant check box, and enter the address from Mividas Rooms as Redirect URI (type Web).

- Fill in the Application (Client) ID and Directory (Tenant) ID below.
- Go to the Certificates and Secrets menu and choose create new. Select ‘never’ as expiry. Copy the key and paste it below, you will not be able to show it again.
| Option | Description |
|---|---|
| Service account username | Enter the service account username. |
| Application (Client) ID | Enter the Application ID. |
| Directory (Tenant) DI | Enter the Directory ID. |
| Client secret | Enter the Client secret. |
Click to save and process, or to cancel.
Add MS Graph connection

- Log in to Office 365 > Admin. Go to Azure Active Directory.
- Select App registrations. [Link]
- Create a new app registration. Leave the single tenant check box, and enter the address from Mividas Rooms as Redirect URI (type Web).

- Fill in the Application (Client) ID and Directory (Tenant) ID below.
- Go to the Certificates and Secrets menu and choose create new. Select ‘never’ as expiry. Copy the key and paste it below, you will not be able to show it again.
| Option | Description |
|---|---|
| Application (Client) ID | Enter the Application ID. |
| Directory (Tenant) ID | Enter the Directory ID. |
| Client secret | Enter the Client secret. |
Click to save and process, or to cancel.
1.12.8. Customer

For service providers and larger organizations, there would be too much data to have a clear overview in one single installation of the Mividas product suite. That is why we have developed the Mividas product suite with multi-tenant support for better handling.
| Page actions | |
|---|---|
| Click to add a new customer. | |
| Update (
) – Allows you to manually update the current page. Documentation ( ) – Takes you to the relevant documentation. |
| Option | Description |
|---|---|
| Search for a customer. | |
| Reload the data to apply any changed filters. | |
| Choose one or more clusters to filter by.
Click to save, or to cancel. |
|
| 1. All types – Filter by all types. 2. Pexip – Filter by Pexip only. 3. Cisco Meeting Server – Filter by CMS only. Click to save, or to cancel. |

- Name – The name of the customer/tenant. Clicking its name takes you to the Mividas Core dashboard of that customer/tenant.
- Cluster – Shows which cluster they are using. If applicable, the customer’s tenant ID is in the CMS.
- Endpoints – Shows the total amount of endpoints that are registered. Clicking its number will take you to
Mividas Rooms > Systemsfor that customer/tenant. - Proxy clients – Shows the total number of proxy clients in use. Clicking its number will take you to
Mividas Rooms > Admin > Proxy clientsfor that customer/tenant. - Address books – Shows the total number of address books in use. Clicking its number will take you to
Mividas Rooms > Address booksfor that customer/tenant. - Meetings – Shows the total number of meetings they have had. Clicking its number will take you to
Mividas Core > Scheduled meetingsfor that customer/tenant. - Matching rules – Shows the total number of matching rules. Clicking its number will take you to
Mividas Core > Admin > Backend admin > Provider > Customer > [Customer-name]. - Admin users – Shows the total number of admin users. Clicking its number will take you to
Mividas Core > Admin > Backend admin > Authentication and authorization > Userswith filters applied to show only admin users for that customer/tenant.
| Option | Description |
|---|---|
Takes you to Mividas Core > Admin > Backend admin > Provider > Customer > [Customer-name] where you can edit the customer. |
Add customer
When clicking , you will first have to choose which cluster to attach that customer to.
Cisco Meeting Server
| Option | Description |
|---|---|
| Name | Enter the customer/tenant name. |
| Callbranding URL | Enter a callbranding URL. |
| Invite text URL | Enter an IVR branding URL. |
| IVR branding URL | Enter a IVR branding URL. |
| Create Core customer | Choose if it should create the customer in Mividas Core. |
| Customer API keys | Enter Customer API key. |
| Create LDAP Source | Choose if it should create a LDAP source. |
| LDAP server | Choose a LDAP server. |
| LDAP mapping | Choose a LDAP mapping. |
| LDAP base dn | Specify where in the tree the initial search for results should begin. Eaxmple: dc=example,dc=com |
| LDAP filter | Here you choose how users are filtered out and displayed. Example: (&(objectClass=person)(cn=*)(!(ou=ou=Demo))) |
| Enable Streaming | Choose to enable streaming. |
| Enable Recording | Choose to enable recording. |
| Click to add the customer. |
Below the form and the Add-button, you will find available options from your chosen CMS to use when you create the customer. You will find available Tenants, Call brandings, IVR brandings, System profiles and LDAP sources. Clicking on will take you to that place in the API client.

| Option | Description |
|---|---|
| Manage name conflict with existing customers | Manage what happens when there is a conflict with existing customers. Click to choose: Skip import, Add suffix, Create duplicate, Link tenant ID to existing customer without changing settings. |
| Synchronize existing tenants. |
Pexip Infinity
Customer info
| Option | Description |
|---|---|
| Title | Enter the name fo the Customer/tenant. |
| Video Provider | Select which provider the customer should be under. Usually filled in by the choice you made before you got here. |
| Add x seconds before a meeting | Adds the amount of seconds you choose to the start time of the meeting. E.g. if you have entered 360 and you book a meeting to start at 14:00, it will start at 13:55. |
| Add x seconds after a meeting | Adds the amount of seconds you choose to the end time of the meeting. E.g. if you have entered 360 and you book a meeting to end at 15:00, it will end at 15:05. |
| CMS tenant ID | Enter the CMS tenant ID, must be available within the CMS. |
| Pexip tenant ID | Automatically generated if this customer is not set as the default customer for the cluster. |
| Possible SEEVIA API Key | Deprecated |
| Enable access to Core | Choose if the customer should have access to Mividas Core. |
| Enable access to Rooms | Choose if the customer should have access to Mividas Rooms. |
| Logo URL | Enter a URL to a customer logo. Is used for invitations. |
Customer key
| Option | Description |
|---|---|
| Add another Customer key | Adds a row to add a shared key. |
| Shared key | Enter the customer shared key. |
| Active | Activate or disable the shared key. |
| Delete | Delete the shared key. |
Cluster settings
| Option | Description |
|---|---|
| Cluster | Choose which cluster to add settings to. |
| Default SIP domain | Enter the primary SIP domain that will be used in the video cluster. E.g. video.example.com |
| Separate domain WebRTC access | Enter the Hostname/FQDN that will be used for WebRTC in your video cluster. E.g. webrtc.example.com |
| IVR phone number | Enter the phone number that sends you to your video cluster IVR. |
| Alternative SIP domains | If the customer uses more than one domain, you can add them here, comma-separated. |
| Scheduled room number range | Enter the start and end of the range that should be used to create your booked meeting rooms, e.g. 160000-169999. |
| Static room number range | Enter the start and end of the range that should be used to create your static meeting rooms, e.g. 150000-159999. |
| Provision meetings | 1. Directly upon booking – Meeting rooms will be created directly upon bookings. 2. Scheduled before and after the meeting (beta) – Meetings will be created before and after the meeting, the time depends on your settings below. |
| Provision meeting rooms x min before scheduled meeting | The amount of minutes before the meeting when the meeting room should be created. |
| Delete meeting room x min after scheduled meeting | The amount of minutes after the meeting when the meeting room should be deleted. |
| Disconnect all participants x min after booked meeting | The amount of minutes after the meeting when all participants should be disconnected. |
| Show message x min before the end time of the meeting time | The amount of minutes before the end of the meeting when a message about the meeting ending should be shown. |
| Skype domain | Customers Skype domain. |
| Rewrite for Skype SIP domain | Lets you rewrite the Skype SIP domain. Use {conf} to replace with conference ID, {url} for URL (without protocol). |
| Add another Cluster settings | Adds another cluster configuration for the customer. Fields will be the same as above. |
Number matching rules
| Option | Description |
|---|---|
| Cluster | Choose which cluster this rule should apply to. |
| SIP-URI / alias starts with | Add a prefix to match with. E.g. 123 will match with [email protected]. |
| SIP-URI / alias ends with | Add a suffix to match with, this is usually a domain. E.g. example.com will match with [email protected]. |
| Type of matching | Choose how the rules should match: Both prefix and suffix match, Either prefix or suffix match, Use the Regexp field. |
| Regexp | Allows you to use regular expressions to match rules. |
| Require external authentication before participants are admitted | Allows you to force participants to be authenticated by a external policy server before getting admitted to a meeting. Requires policy server and cluster rules to be enabled. |
| Priority | Set a priority for the rules. 1 has priority over 2. |
| Delete | Allows you to delete a rule. |
| Add another Number matching rule | Adds another row for a new rule. |
Customer policies
| Option | Description |
|---|---|
| Add another Customer policy | Adds a new row for a customer policy. |
| Participant normal limit | Sets the total number of allowed calls before the normal limit is reached. |
| Participant gateway limit | Set the total number of allowed gateway calls. |
| Participant hard limit | Sets the total number of allowed calls before the hard limit is reached. |
| Valid from | Set the date from when this policy should be active. |
| Soft limit action | Choose what should happen if the soft limit is reached: Default value, Ignore, Log, Reject. |
| Hard limit action | Choose what should happen if the hard limit is reached: Default value, Ignore, Log, Reject. |
| Delete | Allows you to delete a policy. |
Click to save.
Expressway/VCS
Customer info
| Option | Description |
|---|---|
| Title | Enter the name fo the Customer/tenant. |
| Video Provider | Select which provider the customer should be under. Usually filled in by the choice you made before you got here. |
| Add x seconds before a meeting | Adds the amount of seconds you choose to the start time of the meeting. E.g. if you have entered 360 and you book a meeting to start at 14:00, it will start at 13:55. |
| Add x seconds after a meeting | Adds the amount of seconds you choose to the end time of the meeting. E.g. if you have entered 360 and you book a meeting to end at 15:00, it will end at 15:05. |
| CMS tenant ID | Enter the CMS tenant ID, must be available within the CMS. |
| Pexip tenant ID | Automatically generated if this customer is not set as the default customer for the cluster. |
| Possible SEEVIA API Key | Deprecated |
| Enable access to Core | Choose if the customer should have access to Mividas Core. |
| Enable access to Rooms | Choose if the customer should have access to Mividas Rooms. |
| Logo URL | Enter a URL to a customer logo. Is used for invitations. |
Customer keys
| Option | Description |
|---|---|
| Add another Customer key | Adds a row to add a shared key. |
| Shared key | Enter the customer shared key. |
| Active | Activate or disable the shared key. |
| Delete | Delete the shared key. |
Cluster settings
| Option | Description |
|---|---|
| Cluster | Choose which cluster to add settings to. |
| Default SIP domain | Enter the primary SIP domain that will be used in the video cluster. E.g. video.example.com |
| Separate domain WebRTC access | Enter the Hostname/FQDN that will be used for WebRTC in your video cluster. E.g. webrtc.example.com |
| IVR phone number | Enter the phone number that sends you to your video cluster IVR. |
| Alternative SIP domains | If the customer uses more than one domain, you can add them here, comma-separated. |
| Scheduled room number range | Enter the start and end of the range that should be used to create your booked meeting rooms, e.g. 160000-169999. |
| Static room number range | Enter the start and end of the range that should be used to create your static meeting rooms, e.g. 150000-159999. |
| Provision meetings | 1. Directly upon booking – Meeting rooms will be created directly upon bookings. 2. Scheduled before and after the meeting (beta) – Meetings will be created before and after the meeting, the time depends on your settings below. |
| Provision meeting rooms x min before scheduled meeting | The amount of minutes before the meeting when the meeting room should be created. |
| Delete meeting room x min after scheduled meeting | The amount of minutes after the meeting when the meeting room should be deleted. |
| Disconnect all participants x min after booked meeting | The amount of minutes after the meeting when all participants should be disconnected. |
| Show message x min before the end time of the meeting time | The amount of minutes before the end of the meeting when a message about the meeting ending should be shown. |
| Skype domain | Customers Skype domain. |
| Rewrite for Skype SIP domain | Lets you rewrite the Skype SIP domain. Use {conf} to replace with conference ID, {url} for URL (without protocol). |
| Add another Cluster settings | Adds another cluster configuration for the customer. Fields will be the same as above. |
Number matching rules
| Option | Description |
|---|---|
| Cluster | Choose which cluster this rule should apply to. |
| SIP-URI / alias starts with | Add a prefix to match with. E.g. 123 will match with [email protected]. |
| SIP-URI / alias ends with | Add a suffix to match with, this is usually a domain. E.g. example.com will match with [email protected]. |
| Type of matching | Choose how the rules should match: Both prefix and suffix match, Either prefix or suffix match, Use the Regexp field. |
| Regexp | Allows you to use regular expressions to match rules. |
| Require external authentication before participants are admitted | Allows you to force participants to be authenticated by a external policy server before getting admitted to a meeting. Requires policy server and cluster rules to be enabled. |
| Priority | Set a priority for the rules. 1 has priority over 2. |
| Delete | Allows you to delete a rule. |
| Add another Number matching rule | Adds another row for a new rule. |
Customer policies
| Option | Description |
|---|---|
| Add another Customer policy | Adds a new row for a customer policy. |
| Participant normal limit | Sets the total number of allowed calls before the normal limit is reached. |
| Participant gateway limit | Set the total number of allowed gateway calls. |
| Participant hard limit | Sets the total number of allowed calls before the hard limit is reached. |
| Valid from | Set the date from when this policy should be active. |
| Soft limit action | Choose what should happen if the soft limit is reached: Default value, Ignore, Log, Reject. |
| Hard limit action | Choose what should happen if the hard limit is reached: Default value, Ignore, Log, Reject. |
| Delete | Allows you to delete a policy. |
Click to save.
1.12.9. Backend admin

The Backend admin is the superuser-only administration interface, accessed at /admin/. It exposes low-level configuration that may not be surfaced in the standard product interface.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Table of contents
- Address books
- API keys & OAuth
- Authentication and authorization
- Access monitoring (Axes)
- Calendar connections
- CUCM API authorizations
- Endpoints
- Endpoint auth backends
- Endpoint networks
- Endpoint templates
- Exchange Web Services (EWS) connections
- LDAP syncs
- Housekeeper
- Meeting types
- Monitoring rules
- MS Graph API connections
- Number ranges
- Providers & infrastructure
- Statistics
- Active trace logs
- Messages
- Authorizations for Webex API
1.12.9.1. Address books

Manage the address books available in Mividas Rooms. Each address book groups the contacts and systems that users can search for and dial.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard web interface when the same setting is available there.
| Option | Description |
|---|---|
| ADD ADDRESS BOOK + | Add an address book. |

| Option | Description |
|---|---|
| Name | The name of the address book. |
| Customer | The customer that the address book belongs to. Clicking the name allows you to edit the address book. |
| GET SOAP URL | The SOAP URL of the address book. |
| ITEMS | Number of items in the address book. |
| View the address book in Mividas Rooms. | |
| Export the address book to an Excel file. |
Adding or editing an address book

IMPORTANT: We recommend that you do not change any settings here unless instructed by support. Use Mividas Rooms web interface to configure Address Books.
| Field | Description |
|---|---|
| Customer | Select the customer this record applies to; leave blank for a global/shared record. |
| Name | A descriptive name used to identify this record. |
| URL | The URL for this record. |
| Editing URL | The URL used to edit the external source. |
| External type | The type of external source. |
| Group | The group this record belongs to. |
| Type | The type/category of this record. |
| Secret key | A secret key used to authenticate the source. |
1.12.9.2. API keys & OAuth
Manage programmatic access to Mividas API – OAuth applications, external OAuth service connections, and Scheduling-portal API keys.
This section contains the following settings pages:
1.12.9.2.1. Applications

Configure OAuth 2.0 client applications that can authenticate with the Mividas API.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard web interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| User | The user associated with this record. |
| Redirect uris | Allowed URIs list, space separated. |
| Post logout redirect uris | Allowed Post Logout URIs list, space separated. |
| Client type | Choose the OAuth client type:
Confidential – Applications running on protected servers where unauthorized users cannot access the configuration or source code, allowing them to maintain a |
| Authorization grant type | Choose the OAuth authorization grant type:
Authorization code – A secure, redirection-based flow where the application exchanges a temporary authorization code for an access token. This is the industry standard for both web apps and public clients (when paired with PKCE). |
| Hash client secret | Whether to store the client secret hashed. |
| Name | A descriptive name used to identify this record. |
| Skip authorization | Whether to skip the user authorization step. |
| Algorithm | Select the signing algorithm used for tokens: No OIDC support, RSA with SHA-2 256, HMAC with SHA-2 256. |
| Allowed origins | Allowed origins list to enable CORS, space-separated. |
| Enable customer restriction | This will be activated if some customers are selected in the list. |
| Limit to customers | Hold down Control, or Command on a Mac, to select more than one. |
| Limit to IP addresses | A list of approved IP addresses/networks. |
| Client id | The OAuth client ID. |
| Client secret | Hashed on Save. Copy it now if this is a new secret. |
1.12.9.2.2. Open Auth Services (OAuth)

External OAuth service connections that Mividas uses to authenticate to third-party services.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard web interface when the same setting is available there.
| Option | Description |
|---|---|
| Recover deleted Open Auth Services (OAuth) | Allows you to recover previously deleted OAuth services. |
| Add Open Auth service (OAuth) + | Add an OAuth service. |

| Option | Description |
|---|---|
| Application (Client) ID | The Application (Client) ID. |
| Service Account Username | The service account username. |
| Type | Displays the record type. |
| Customer | Displays the customer for the record. |
Add OAuth service

| Field | Description |
|---|---|
| Customer | The customer this record applies to; leave blank for a global/shared record. |
| Type | Select the type for this record: EWS, Microsoft Graph, Microsoft Graph Teams Devices, Webex Device API, Webex Meeting API, Webex Meeting G2G-tenant API. |
| Service account username | All access will be from this account. |
| Application (Client) ID | Enter the Application (Client) ID. |
| Directory (Tenant) ID | Enter the Application (Tenant) ID. |
| Client secret | Enter the Client secret. |
| Use app authorization | Whether to authenticate as the application rather than as a user. |
| Scope | The OAuth scope(s) requested for this credential. |
MS Graph API-Connection

| Option | Description |
|---|---|
| Description | Enter a description of this record. |
| Customer | Select a customer for this record. |
| Username | Enter a username for this record. |
| Turn on sync | Check to enable synchronization. |
| Synchronize room list | Check to enable synchronization of room list to automatically find room resources. |
| Use impersonation | Check to enable impersonation. |
| Type | Select the type of record: EWS / Exchange, Microsoft Graph, Webex API, CUCM. |
| Last sync error | If there was an error on the last sync, the error message will be shown here. |
| Video meeting only | Only synchronize video meetings. |
| Delete | Click to delete this record. |
| Add another MS Graph API-connection | Click to add a record. |
Exchange Web Service link (EWS)

| Option | Description |
|---|---|
| Description | Enter a description of this record. |
| Customer | Select a customer for this record. |
| Username | Enter a username for this record. |
| Turn on sync | Check to enable synchronization. |
| Synchronize room list | Check to enable synchronization of room list to automatically find room resources. |
| Use impersonation | Check to enable impersonation. |
| Type | Select the type of record: EWS / Exchange, Microsoft Graph, Webex API, CUCM. |
| Last sync error | If there was an error on the last sync, the error message will be shown here. |
| Video meeting only | Only synchronize video meetings. |
| Password | Enter a password. Only used when running Basic authentication instead of OAuth. |
| SMTP address for service account | Enter the SMTP address for the service account, if different from the username. |
| Exchange server host name | Enter the host name of the Exchange server. Leave empty to find the correct server via auto-discovery. |
| Use autodiscover to retrieve additional settings | Check to use autodiscover to retrieve additional settings. |
| Limit the number of calendars to sync at a time | Enter the maximum number of calendars to synchronize at a time. Default is 15 to match the default user session count limit; increase or decrease to fit your throttling policy and Managed Store limits. |
| Number of days to sync | Enter the number of days to synchronize. Default is 21; adjust to fit the throttling limit for found and open objects. |
| Delete | Click to delete this record. |
| Add another Exchange Web Services Link (EWS) | Click to add a record. |
Authorization for Webex API

| Option | Description |
|---|---|
| Description | Enter a description of this record. |
| Customer | Select a customer for this record. |
| Username | Enter a username for this record. |
| Turn on sync | Check to enable synchronization. |
| Synchronize room list | Check to enable synchronization of room list to automatically find room resources. |
| Use impersonation | Check to enable impersonation. |
| Type | Select the type of record: EWS / Exchange, Microsoft Graph, Webex API, CUCM. |
| Video meeting only | Only synchronize video meetings. |
| Guest issuer ID | Enter the Webex guest issuer ID. |
| Guest issuer secret | Enter the Webex guest issuer secret. |
| Last sync error | If there was an error on the last sync, the error message will be shown here. |
| Delete | Click to delete this record. |
| Add another Authorization for Webex API | Click to add a record. |
1.12.9.2.3. Scheduling portal API keys

API keys used by Mividas Meeting Portal and other integrations to call the booking API. A system-generated API key is always added on installation.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard web interface when the same setting is available there.
| Option | Description |
|---|---|
| Recover deleted scheduling portal API keys | Allows you to recover previously deleted OAuth services. |
| Add scheduling portal API key + | Add an OAuth service. |
Add scheduling portal API key

| Field | Description |
|---|---|
| Name | A descriptive name used to identify this record. |
| Update key | A new key has been generated. Save it, it will be hidden after saving. |
| Enable customer restriction | Enable this to limit the API key to specific customer(s). This will be activated if some customers are selected in the list below. |
| Limit to customers | Select one or more customers to enable the API key for. |
| Limit to IP addresses | A list of approved IP addresses/networks that can use the API key. |
| Turn on change settings for static meeting rooms | Controls the “Turn on change settings for static meeting rooms” setting for this record. |
| Allow users to create new static meeting rooms | Controls the “Allow users to create new static meeting rooms” setting for this record. |
| Expiration date | When this key expires. |
| Created | When this record was created (read-only). |
| Last used | When this key was last used (read-only). |
| Enabled | Whether this record is currently enabled (read-only). |
| Key value | The generated key value, only parts of the key for identification. (read-only). |
1.12.9.3. Authentication and authorization
Manage user accounts and the permission groups that grant web-interface access and granular API rights.
This section contains the following settings pages:
1.12.9.3.1. Groups

Permission groups that bundle web-interface access and granular API rights, and can be mapped from an external identity provider.
| Option | Description |
|---|---|
| ADD GROUP + | Add a new group. |
Permissions are assigned with the checkbox groups below. A :write right automatically also grants the matching :read right. External identity-provider groups can be mapped to this group via the Group mappings inline section (used with SAML/LDAP).
Permissions
Each permission group below is a set of checkboxes. Tick the rights this group should grant.
Access to view/use the web interface
If no web: permission is granted, the user can only use the API for the selected read/write permissions. Access to each data type/API needs to be assigned separately.
| Permission | Grants |
|---|---|
web:all |
Access to all web interfaces. |
web:core |
Access to Mividas Core web interface. |
web:insight |
Access to Mividas Insight web interface. 1 |
web:rooms |
Access to Mividas Rooms web interface. |
- To view the Mividas Insight web interface, the user must also have admin rights.
Global rights
A :write right automatically gives the corresponding :read right.
| Permission | Grants |
|---|---|
admin:all:read |
Full read-access to all data and admin settings. |
admin:all:write |
Full access to read and change all data and admin settings. |
api:all:read |
Read all data except admin settings. |
api:all:write |
Write all data except admin settings. |
customers:all |
Access to all customers/tenants. |
Administrator rights for individual products
A :write right automatically gives the corresponding :read right.
| Permission | Grants |
|---|---|
admin:core:read |
Read access to all data, both for users and administrators, for Mividas Core only. |
admin:core:write |
Write access to all data, both for users and administrators, for Mividas Core only. |
admin:rooms:read |
Read access to all data, both for users and administrators, for Mividas Rooms only. |
admin:rooms:write |
Write access to all data, both for users and administrators, for Mividas Rooms only. |
Granular API rights – Core
A :write right automatically gives the corresponding :read right.
| Permission | Grants |
|---|---|
calls:read |
Read calls and participants. |
calls:write |
Create/Update/Delete calls and participants. |
cospaces:read |
Read meeting rooms. |
cospaces:write |
Create/Update/Delete meeting rooms. |
meetings:read |
Read scheduled meetings. 1 |
meetings:write |
Create/Update/Delete scheduled meetings. 1 |
messages:read |
Read invitation messages. 2 |
messages:write |
Create/Update/Delete invitation messages. 2 |
monitoring:core:read |
Read core monitoring. |
monitoring:core:write |
Write core monitoring. |
organization:read |
Read Org. unit. 2 |
organization:write |
Create/update Org. unit. 2 |
users:read |
Read users. |
- These permissions require the corresponding permissions in Mividas Rooms, so that will be automatically checked upon saving. When removing the permission, it must be removed in both places.
- Since these permissions also require that you are an administrator, and when you have administrator rights they are automatically shown, this only affects API usage.
Detailed API rights – Rooms
A :write right automatically gives the corresponding :read right.
| Permission | Grants |
|---|---|
addressbooks:read |
Read address books. |
addressbooks:write |
Create/Update/Delete Address Books. |
endpoints:read |
Read endpoints. |
endpoints:write |
Create/Update/Delete endpoints and provisioning settings. |
firmwares:read |
Read firmware. |
firmwares:write |
Create/Update/Delete firmware. |
macros:read |
Read macros and room controls. |
macros:write |
Create/Update/Delete Macros and Room Controls. |
meetings:read |
Read scheduled meetings. 1 |
meetings:write |
Create/Update/Delete scheduled meetings. 1 |
monitoring:rooms:read |
Read room monitoring. |
monitoring:rooms:write |
Write room monitoring. |
organization:read |
Read Org. unit. 2 |
organization:write |
Create/update Org. unit. 2 |
sensors:read |
Read sensor data. |
- These permissions require the corresponding permissions in Mividas Core, so that will be automatically checked upon saving. When removing the permission, it must be removed in both places.
- Since these permissions also require that you are an administrator, and when you have administrator rights they are automatically shown, this only affects API usage.
Detailed API rights – Other
A :write right automatically gives the corresponding :read right.
| Permission | Grants |
|---|---|
statistics:calls:export |
Export call statistics. |
statistics:calls:read |
Reading call statistics. |
statistics:sensors:export |
Export sensor data. |
Using the Booking API
Primarily used by integrations.
| Permission | Grants |
|---|---|
book_api:cospaces_change |
Allow users to change meeting rooms, using the API. |
book_api:cospaces_create |
Allow creation of meeting rooms, using the API. |
book_api:write |
Schedule a meeting via the booking API. |
Group mappings

Here you can map external identity-provider groups (SAML/LDAP) so that a user automatically receives the correct permissions upon logging in.
| Option | Description |
|---|---|
| Mapping type | LDAP or SAML. |
| Value | Add the mapping value, e.g. CN=admin-users,OU=Groups,DC=example,DC=com. |
| Clear missing | When enabled, this group is automatically removed from a user at login if their SAML/LDAP login no longer includes the matching value. Checked by default. |
| Delete | Click to delete the group mapping. |
| Add another Group mapping | Add another group mapping. |
1.12.9.3.2. Users

Manage local users and users created via external identity-providers (LDAP/SAML).
| Option | Description |
|---|---|
| ADD USER + | Add a local user. |
Add a local user

When adding a local user, start by entering a username and password, then click at the bottom of the page (to stay on the page, otherwise choose another save option). After the user is added, more options become available, see edit user.
Edit a user

| Field | Description |
|---|---|
| Username | Required. 150 characters or fewer. Letters, digits and @/./+/-/_ only. |
| Password | Raw passwords are not stored. |
| First name | The user’s first name. |
| Last name | The user’s last name. |
| Email address | The user’s email address. |
| Active | Whether the account is active. Unselect this instead of deleting an account. |
| Staff-status | Displays if, and how, the user has Staff-status (admin). |
| Superuser-status | Displays if, and how, the user has Superuser-status. |
| Groups | Manage which group(s) the user should have access to. This handles the users’ permissions; read more under groups. Group membership may be overwritten by LDAP/SAML mappings configured elsewhere. |
| Last login | When the user last signed in. |
| Date joined | When the account was created. |
Customer permissions

Select what customer(s) the user should have access to.
| Option | Description |
|---|---|
| Customer | Select a customer. |
| Auto granted at | Displays when (if) the user was automatically granted access to a customer. |
| Delete | Check the checkbox and click to remove access to that customer. |
| Add another Customer permission | Add access to another customer. |
1.12.9.4. Access monitoring (Axes)
Read-only login-security logs from the Axes brute-force-protection module.
This section contains the following settings pages:
1.12.9.4.1. Access attempts
A read-only log of login attempts recorded by the Axes brute-force-protection module (username, IP address, user agent, and time). Entries are created automatically and cannot be added here.
1.12.9.4.2. Access failures
A read-only log of failed logins recorded by Axes and used to lock out repeated failures. Entries are created automatically and cannot be added here.
1.12.9.5. Calendar connections

The individual room calendar mailboxes are connected through an Exchange (EWS) or Microsoft Graph integration. Each row is one mailbox being synchronized for OBTP and booking.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
| Option | Description |
|---|---|
| Add calendar connection + | Add a calendar connection. |
Add calendar connection

| Field | Description |
|---|---|
| Credentials | The connection/credential this calendar uses. |
| Username | The account username used to authenticate. |
| Endpoint | The room system (endpoint) to which this record is linked. |
| Cached name | The cached display name of the mailbox. |
| Cached path | The cached calendar path. |
| Folder id | The calendar folder identifier. |
| Is working | Could this calendar be accessed on the last try. |
| Customer | The customer this record applies to. |
1.12.9.6. CUCM API authorizations

Credentials for connecting Mividas to a Cisco Unified Communications Manager (CUCM) server in order to synchronize its registered devices.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Edit authorization for CUCM API

| Field | Description |
|---|---|
| Description | A free-text description for your own reference. |
| Customer | The customer this record applies to; leave blank for a global/shared record. |
| Username | UserPrincipalName/SMTP-adress. |
| Turn on sync | Enable automatic synchronization. |
| Password | Used if you run Basic auth instead of OAuth. |
| FQDN of CUCM server | Enter the FQDN of the CUCM server. |
| Verify SSL certificates | Enable SSL certificate verification upon connection. |
| Is working | If True, then this was working on last_sync. |
| Last modified time | When this record was last modified. |
| Last sync | When this record was last synchronized. |
| Last incremental sync | When this record last performed an incremental sync. |
| Last sync error | The most recent synchronization error, if any. |
1.12.9.7. Endpoints
The full configuration record for each managed room system (endpoint). This backend view exposes every low-level setting for a system – most of which are also editable from Mividas Rooms.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
| Option | Description |
|---|---|
| Recover deleted endpoints | Allows you to recover previously deleted endpoints. |
| Add endpoint + | Add an endpoint. |
Add an endpoint

| Field | Description |
|---|---|
| Customer | The customer this record applies to. |
| Organization unit | The organization unit (OU) the record belongs to, used for filtering and statistics. |
| Name | A descriptive name used to identify this record. |
| IP address | The IP address of the system. |
| Automatically update IP | Enable tracking of IP changes on the system. |
| Full DNS hostname | The system’s full DNS hostname. |
| Validate SSL connection | Whether to validate the system’s SSL certificate. |
| SIP | The SIP address (URI) of the system. |
| H323 | The H.323 ID of the system. |
| H.323 E.164 | The H.323 E.164 alias (number) of the system. |
| Timezone | The time zone used for the system. |
| Username | The account username used to authenticate. |
| Password | The password for the username entered above. Use a hyphen (-) to reset the value. |
| Type of connection | Select the type of connection: Direct, Incoming, Passive, Proxy. |
| Port to Web Interface | The port used to reach the system’s web interface. |
| Http mode | Whether to use HTTP or HTTPS for the system. |
| Proxy | The proxy used to reach this system, if any. |
| Email inbox | The email inbox associated with the system. |
| Location | The physical location of the system. |
| Type of system | Select the category of the system: Cisco_CE, Cisco_Webex, TeamsMTR (not in use), Other. |
| Model | The device model. |
| Serial number | The system’s serial number. |
| MAC address | The system’s MAC address. |
| Has people count | Select whether the system reports people-count data: Yes, No, Unknown. |
| Dial-in protocol | Select the default dial-in protocol for the system: Default setting, SIP, H.323, H.320, Spark. |
| Number of seats in rooms | The number of seats in the room. |
| Default address book | The address book pushed to the system by default. |
| SIP registration | Whether the system is SIP-registered. |
| Personal system | Whether this is a personal system. |
| Person’s e-mail address | The e-mail address of the system’s owner. |
| External mailbox | The external mailbox linked to the system. |
| Allow storage of sensor data | Whether sensor data from the system may be stored. |
| Standard type of scheduling from Portal | Select the default scheduling/dial method used when booking from the portal: Dialout, OBTP, Dial, None. |
| OBTP PIN mode | Select how the PIN is embedded for OBTP dial-out: Off, Embedded in URI. |
| External provisioning service URL | URL of an external provisioning service. |
| Webex registered device ID | The device ID when the system is registered to Webex. |
| Standard Connection | The default connection used for the system. |
| Hide in address books | Whether to hide this system from automatically generated address books. |
| ID in inventory system | The system’s ID in an external inventory system. |
| Service reference | A service reference for the system. |
| Service valid until | When the system’s service contract expires. |
| Notes | Free-text notes for your own reference. |
| Warning text | Displayed as a warning on the system dashboard. |
| Listing only | Blocks call control, commands, configuration changes, and all provisioning (both active and passive). Local data can still be edited, and appointment booking is still allowed. |
| Metadata from external systems | Metadata imported from external systems. |
| Network | The endpoint network used to reach the system. |
| Webex registration | Webex registration details for the system. |
| Pexip registration | Pexip registration details for the system. |
| Event secret key | Secret key used to validate event callbacks from the system. |
1.12.9.8. Endpoint auth backends

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
| Option | Description |
|---|---|
| Add endpoint auth backend + | Add an endpoint auth backend. |
Add an endpoint auth backend

| Field | Description |
|---|---|
| Name | A descriptive name used to identify this record. |
| Active | Whether this record is currently active. |
| Customer | The customer this record applies to. |
| Sort index | Controls the display order – lower values appear first. |
| Client id | The OAuth client ID. |
| Client secret | The client secret. Use a hyphen (-) to reset the value. |
| Scope | The OAuth scope(s) requested for this credential. |
| Authorization grant type | The OAuth authorization grant type. |
| Enable password grant type | Allow the OAuth password grant type. |
| Enable device grant type | Allow the OAuth device grant type. |
| Authorization url | The OAuth authorization endpoint URL. |
| Token url | The OAuth token endpoint URL. |
| Userinfo url | The OpenID userinfo endpoint URL. |
| Device authorization url | The OAuth device-authorization endpoint URL. |
| Device token url | The OAuth device-token endpoint URL. |
| Device verification url search | Search pattern for rewriting the device verification URL. |
| Device verification url replace | Replacement for rewriting the device verification URL. |
| Username field | Which claim/field to use as the username. |
| May be used to connect user to active devices | Allow this backend to link a user to active devices. |
| Keep access token | Whether to store the access token. |
| Display redirect url | Show the redirect URL for configuration. |
1.12.9.9. Endpoint networks
Named network definitions that control how Mividas Rooms reaches systems (directly or via a proxy), including alternate FQDNs for contact and firmware download.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| Name | A descriptive name used to identify this record. |
| Proxy from Rooms to the respective system | Route traffic from Rooms to the system through a proxy. |
| Endpoint proxy | The proxy client used to reach systems on this network. |
| Use different FQDN to contact Rooms | Requires a separate load balancer that forwards traffic to the regular FQDN |
| Use different FQDN to download firmware | Requires a separate load balancer that forwards traffic to the regular FQDN |
1.12.9.10. Endpoint templates

Reusable provisioning templates (settings and commands) that can be applied to room systems.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
| Option | Description |
|---|---|
| Add endpoint template + | Add an endpoint template. |
Add an endpoint template

| Field | Description |
|---|---|
| Customer | The customer this record applies to; leave blank for a global/shared record. |
| Name | A descriptive name used to identify this record. |
| Manufacturer | Select the device manufacturer that the template targets: Cisco_CE, Cisco_Webex, Teams MTR (not in use), Other. |
| Product name | The product/model name the template targets. |
| Settings | JSON array of objects [{“key”: [“Audio”, “Volume”], “value”: “1”}] |
| Commands | JSON array of objects [{“command”: [“HttpFeedback”, “Register”], “arguments”: {“FeedbackSlot”: “1”}, “body”: “”}] |
1.12.9.11. Exchange Web Services (EWS) connections

Exchange Web Services (EWS) connections are used to synchronize room/resource calendars for OBTP and booking.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
| Option | Description |
|---|---|
| Add Exchange Web Services Link (EWS) + | Add an Exchange Web Services Link (EWS). |
Add an Exchange Web Services Link (EWS)

| Option | Description |
|---|---|
| Description | A free-text description for your own reference. |
| Customer | Select the customer to which this record applies. |
| Username | Enter UserPrincipalName/SMTP-adress. |
| Turn on sync | Enable automatic synchronization. |
| Synchronize room lists | Enable synchronization of Exchange room lists to automatically find resource calendars. |
| Use impersonation | Impersonation requires an OAuth login; alternatively, ManagementRoleAssignment with Role:ApplicationImpersonation for a service account. If impersonation is not enabled, then Set-ThrottlingPolicy is required. |
| Video meetings only | Disable to skip all meetings that cannot be matched to a dialing address. |
| Oauth credential | Select the OAuth service connection that is used to authenticate. |
| Password | Used if you run Basic auth instead of OAuth. |
| SMTP address for service account | If other than username. |
| Exchange Server Host Name | Leave blank to find the right server via auto-discovery. |
| Use autodiscover to retrieve additional settings | Use Autodiscover to fetch additional server settings. |
| Limit the number of calendars to sync at a time | The default is 15 to fit the default user session count limit. Increase or decrease this to suit your Throttling policy and Managed Store Limits. |
| Number of days to sync | The default is 21. This needs to be adapted to the Throttling limit for found and open objects. |
| Is working | If True, then this was working on the last sync. |
| Last modified time | When this record was last modified. |
| Last sync | When this record last synchronized. |
| Last incremental sync | When this record last performed an incremental sync. |
| Last sync error | The most recent synchronization error, if any. |
Calendar connection

| Option | Description |
|---|---|
| Username | The username for the calendar connection. |
| Endpoint | Select the system that this calendar connection should be connected to. |
| Is working | Displays if this was working on the last sync. |
| TS last sync | Time stamp of the last performed synchronization. |
| Delete | Click to delete this calendar connection. |
| Add another Calendar connection | Add another calendar connection. |
1.12.9.12. LDAP syncs

Scheduled synchronizations from an LDAP directory into Mividas (users, address books and VMRs).
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
| Option | Description |
|---|---|
| Add LDAP sync + | Add an LDAP sync. |
Add an LDAP sync

| Field | Description |
|---|---|
| Provider | Select the provider this record should be linked to. |
| Customer | Select the customer to which this record applies. |
| Sync to OU | The organization unit synced records should be placed in. |
| Class for object | The LDAP object class to synchronize. |
| Set up items for VMRs | Create items for virtual meeting rooms during sync. |
| Sync Address book | Synchronize the address book. |
| Sync tms | Select a TMS to synchronize TMS data. |
| Ts last sync | Timestamp of the last synchronization. |
| Ts last completed sync | Timestamp of the last completed synchronization. |
| Item count | Number of items processed. |
| Last error | The most recent error message, if any. |
1.12.9.13. Housekeeper
Data-retention and housekeeping settings that control automatic cleanup and redaction of old call data.
Automatic cleanup (housekeeping)
Mividas Core stores a large amount of logs, synchronization and call-statistics data over time. To keep your database from growing without limit, Mividas Housekeeper can automatically delete this data once it reaches a certain age. This page controls whether that happens and how long each type of data is kept.
How the retention interval works:
- For each data category, you enter an interval – the length of time the data is kept. Anything older than the interval is removed the next time cleanup runs; newer data is always kept.
- Enter the interval as
DD HH:MM:SS(days, hours, minutes, seconds). Example:30 00:00:00keeps 30 days of data. - Leave the interval empty to disable cleanup for that category – that data is then never deleted automatically.
- Cleanup only runs when Enable automatic cleanup is switched on.
Important – Enabling automatic cleanup, or changing a schedule from e.g. 30 days to 10 days, will not create free space on the hard drive. The used up space will remain the same, but the space that was used can be re-used. For information on how to free up space from /var/logs, see FAQ below.
Cleanup settings

| Option | Description |
|---|---|
| Enable automatic cleanup | Master on/off switch for all housekeeping. When switched off, no data is ever removed, regardless of the intervals below. When on, Mividas checks roughly every 15 minutes whether any category is due for cleaning. |
| Save meeting room names when redacting call participants | When enabled (default), the meeting room name is kept while personal participant details (names and addresses) are removed. When disabled, the meeting room name is also removed. |
| Ts last run | Shows the date and time the automatic cleanup last ran. |
Cleanup schedules
| Interval | Type key | Description |
|---|---|---|
| acano_cdr Default: 30 00:00:00 | CMS CDR log. | Call Detail Records received from Cisco Meeting Server. |
| acano_cdr_spam Default: 10 00:00:00 | CMS CDR spambox log | Unmatched or discarded CMS CDR events (the “spam box”). |
| audit_log Default: empty | Audit log | Audit trail and policy log entries. |
| changed_meeting Default: 60 00:00:00 | Meeting changes | Superseded versions of meetings that were later changed. |
| email_log Default: 30 00:00:00 | Email log | Record of emails sent by the system. |
| endpoint_cisco_event Default: 30 00:00:00 | Cisco HTTP events | HTTP feedback events received from Cisco endpoints. |
| endpoint_cisco_provision Default: 30 00:00:00 | Cisco provisioning log | Log of provisioning actions sent to Cisco endpoints. |
| endpoint_data_file Default: 30 00:00:00 | Historical system information | Older snapshots of endpoint configuration and status changes. |
| endpoint_tasks Default: empty | Provisioning actions | History of completed or canceled endpoint provisioning tasks. |
| error_log Default: 30 00:00:00 | Error log | Recorded system error messages. |
| meeting Default: empty | Ended meetings | Information about meetings that have already finished. |
| pexip_eventsink Default: 30 00:00:00 | Pexip Event Sink | Event data pushed from Pexip via the event sink. |
| pexip_history Default: 30 00:00:00 | Pexip History API | Call history retrieved from the Pexip History API. |
| pexip_policy_log Default: 30 00:00:00 | Pexip Policy | Pexip external policy request log. |
| policy_auth_log Default: empty | Policy authentication log | Expired policy authorization records. |
| policy_auth_log_redaction Default: empty | Policy authentication log cleaning of overrides | Removes stored setting overrides from policy authentication records (anonymization, not deletion). |
| sensor_data 1 Default: empty | Sensor data | Room sensor readings such as people count, temperature and air quality. |
| statistics_full_delete 1 Default: empty | Full deletion of call statistics | Permanently deletes all call statistics data older than the interval. Use with care. |
| statistics_invalid_calls 1 Default: 60 00:00:00 | Invalid calls | Calls that have no valid participants. |
| statistics_invalid_legs 1 Default: 60 00:00:00 | Invalid call participants | Participant records that do not count towards statistics (for example, calls under 60 seconds, or chat/presentation/distribution legs). |
| statistics_redaction 1 Default: empty | Redaction of participant information | Anonymizes participant records by removing names and addresses. The data is retained for statistical purposes, but personal details are anonymized. |
| synced_mcu_data Default: 60 00:00:00 | Previously synced MCU information | Cached provider objects (for example, meeting rooms, URIs, and users) that are no longer active on the provider. |
| trace_log Default: 1 00:00:00 | Trace log | Detailed diagnostic trace data (verbose; kept only briefly). |
| vcs_calls Default: 30 00:00:00 | VCS/Expressway call history | Call history collected from Cisco VCS/Expressway. |
- Enabling/changing these will affect data presented in the product, e.g., sensor data or call statistics.
FAQ
Here are some frequently asked questions (FAQs) to help you find the answers you’re looking for.
To clean up the /var/log directory when it’s full, you can follow these steps using SSH or the Mividas Installer console:
Check and Identify Large Files
Identify the largest folders in /var/log:
sudo du -xh /var/log | sort -h | tail -n40
List files by size within the /var/log and /var/log/docker/ directories to locate the largest log files:
ls -shSr /var/log/
ls -shSr /var/log/docker/
Delete Unnecessary Log Files
Delete specific old log files one at a time:
sudo rm /var/log/<file_name>
Bulk delete compressed log files:
sudo rm -f /var/log/*.log.[1-4].gz
Run Hard Drive Cleanup from the Mividas Installer Console
Access Hard drive cleanup options in the Mividas Installer console:
- Debug logs/raw call data: Remove old debug logs and raw call data.
- Old versions: Remove old versions of components or software.
Clean Up Docker Resources
Remove unused Docker images if they’re no longer needed:
sudo docker image prune -f
Note: Only perform Docker cleanup when all Mividas components are active and running. If components are missing or inactive, this can lead to further cleanup or redeployment needs, particularly for offline systems.
Remove all unused Docker resources (images, containers, networks):
sudo docker system prune -f
Clean up any Docker resources that are not currently in use:
sudo docker system prune -af
By following these steps, you can manage storage in /var/log effectively without compromising system stability.
1.12.9.14. Meeting types

Define the meeting types (templates) that users can choose when scheduling meetings or creating static meeting rooms.
NOTE: For a more complete guide on how to properly set up custom meeting types and access methods, see Configure and use custom meeting types and access methods
| Option | Description |
|---|---|
| Recover deleted meeting types | Allows you to recover previously deleted meeting types. |
| Add meeting type + | Add a meeting type. |
Add a meeting type

Start by entering a Title and selecting a Cluster for the meeting type, then click to reveal the remaining options.

| Option | Description |
|---|---|
| Key | Enter a key to use to match this meeting type from Mividas Meeting Portal and invite templates. E.g. custom_meeting_1 |
| Delete | If not yet saved: Click (
) to remove that row.
If already saved: Check the box and click to remove that row. |
| Add another Meeting type match key | Adds another row to add another meeting type match key. |

| Option | Description |
|---|---|
| Customer | Select the customer this override applies to. Each customer can only have one override per meeting type. |
| Show in Core | Override whether this meeting type is visible when creating static meeting rooms in Mividas Core for this specific customer.
Unknown – Use the default setting from the meeting type. |
| For all users | Override whether this meeting type is visible in the Mividas Meeting Portal for all users of this customer.
Unknown – Use the default setting from the meeting type. |
| Meeting type key | A customer-specific key that can be used to look up this meeting type instead of the default match keys. This allows different customers to reference the same meeting type using different keys. |
| Delete | If not yet saved: Click (
) to remove that row.
If already saved: Check the box and click to remove that row. |
| Add another override for customer | Adds another row to add another override. |

| Option | Description |
|---|---|
| Enabled | Check to enable this access method. |
| Title | Enter a title for this access method. |
| Call leg profile | Select which call leg profile to use for this access method. |
| Lobby profile | Select which lobby profile to use for this access method. |
| Always create | When enabled, this access method will always be created for rooms using this meeting type, regardless of other conditions. When disabled, the access method is only created when matching conditions are met, such as a moderator PIN being set. |
| Fallback setting | When enabled, this access method is used as the fallback for all additional addresses matching the same member scope. When disabled, the access method is only used when explicitly matched. |
| Is the default address for room | When enabled, this access method will be used as the primary address for the meeting room. Only one access method per meeting type can be set as the default. Enabling this will automatically unset the default flag on other access methods in the same meeting type. |
| System ID | Defines the role of this access method. Only one guest and one moderator access method can exist per meeting type; any additional access methods must be set to None.
None – No specific role assigned. Used for additional access methods such as member or directory entries. |
| Member scope | Defines who can use this access method to join the meeting.
None – No specific scope. The access method is not restricted. |
| Overrides for values sent via API to MCU | A JSON object with additional or overriding values that will be sent to the provider API for this specific access method. These values are not synced to the provider template. |
| Delete | If not yet saved: Click (
) to remove that row.
If already saved: Check the box and click to remove that row. |
| Add another access method | Adds another row to add another access method. |
1.12.9.15. Monitoring rules
Rules that drive Mividas monitoring alerts – automatic actions and custom per-value thresholds.
This section contains the following settings pages:
1.12.9.15.1. Alert action rules

Alert Action Rule is a suppression (mute) rule. The only action it can perform is Ignore – i.e., “when an alert with this title/code would be raised, don’t raise it”. Rules that have been ignored in the web interface will show up here. This page should be considered read-only.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
1.12.9.15.2. User alert rules

Here you can configure your own alert rules for systems, based on xStatus, xConfiguration, or Mividas Rooms metadata.
| Option | Description |
|---|---|
| Add user alert rule + | Add a user alert rule. |
Add a user alert rule

| Field | Description |
|---|---|
| Customer | Select the customer this record applies to; leave blank for a global record. |
| Endpoint | Select the room system this record is linked to; leave blank for all systems. |
| Value type | Select the type of value being evaluated: Status, Configuration, Rooms metadata. |
| Key | Input the key identifier:
For Status type, enter the full path, separated by a dot (.) or slash (/), e.g. For Configuration type, enter the full path, separated by a dot (.) or slash (/), e.g. For Rooms metadata type, enter the parameter, e.g., |
| Operator | Select the comparison operator used to evaluate the value: Equal, Not equal, Less than, Less than or equal, More than, More than or equal, New value, Removed value. |
| Limit | Enter the threshold value the rule compares against. |
| Ignore unset | Ignore systems where the value is not set. |
| Persistent | Whether the alert persists until it is resolved. |
| Message | The message shown when the rule triggers. |
| Severity | The severity level applied when this rule matches. |
Example alerts
Value type: Status (xStatus values)
| Key | Operator | Limit | Severity | Message |
|---|---|---|---|---|
| SystemUnit/Hardware/Temperature | More than or equal | 80 | ERROR | System overheating, chassis nearing the 85 °C threshold. |
| Cameras/Camera[1]/Connected | Equal | False | WARNING | Camera 1 disconnected. |
Value type: Configuration (xConfiguration settings)
| Key | Operator | Limit | Severity | Message |
|---|---|---|---|---|
| Conference/Encryption/Mode | Equal | Off | ERROR | Encryption has been disabled. |
| Conference/AutoAnswer/Mode | Equal | On | WARNING | Auto-answer enabled, privacy risk. |
Value type: Rooms metadata (Mividas Rooms metadata)
The Mividas Rooms metadata keys are based on you locale settings, that means that e.g. People wont work as a key in a Swedish installation, there it would be Personer.
| Key | Operator | Limit | Severity | Message |
|---|---|---|---|---|
| People | More than | 8 | WARNING | Room over capacity, more people than seats. |
| Temperature | More than or equal | 25 | WARNING | The room is too warm; check the AC. |
1.12.9.16. MS Graph API connections

Microsoft Graph API connections are used to synchronize room/resource calendars for OBTP and booking.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
| Option | Description |
|---|---|
| Add MS Graph API-connection + | Add MS Graph API connection. |
Add MS Graph API connection

| Option | Description |
|---|---|
| Description | A free-text description for your own reference. |
| Customer | Select the customer to which this record applies. |
| Turn on sync | Enable automatic synchronization. |
| Synchronize room lists | Enable synchronization of Exchange room lists to automatically find resource calendars. |
| Use impersonation | Impersonation requires an OAuth login; alternatively, ManagementRoleAssignment with Role:ApplicationImpersonation for a service account. If impersonation is not enabled, then Set-ThrottlingPolicy is required. |
| Video meetings only | Disable to skip all meetings that cannot be matched to a dialing address. |
| Oauth credential | Select the OAuth service connection that is used to authenticate. |
| Is working | If True, then this was working on the last sync. |
| Username | Displays the username used for the integration. |
| Last modified time | When this record was last modified. |
| Last sync | When this record last synchronized. |
| Last incremental sync | When this record last performed an incremental sync. |
| Last sync error | The most recent synchronization error, if any. |
Calendar connection

| Option | Description |
|---|---|
| Username | The username for the calendar connection. |
| Endpoint | Select the system that this calendar connection should be connected to. |
| Is working | Displays if this was working on the last sync. |
| TS last sync | Time stamp of the last performed synchronization. |
| Delete | Click to delete this calendar connection. |
| Add another Calendar connection | Add another calendar connection. |
1.12.9.17. Providers & infrastructure
Low-level video infrastructure: clusters, meeting platforms (CMS/Pexip), customers/tenants, and related servers.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
This section contains the following settings pages:
- Cisco Meeting Server profiles
- Cisco/Tandberg TMS
- Clusters
- Customers
- Expressway/VCS
- LDAP Servers
- Meeting platforms
1.12.9.17.1. Cisco/Tandberg TMS
Connection to a Cisco/Tandberg TMS server for phone-book and system data.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| DNS Name | The fully-qualified DNS hostname of the server. |
| Verify SSL certificates | Use full domain name that matches server certificates |
| Phone book URL | The TMS phone-book URL. |
| MAC address for verification | A MAC address used to verify the connection. |
| Default domain for URI with no domain | Domain appended to URIs that have no domain. |
1.12.9.17.2. Expressway/VCS
Connection to a Cisco Expressway/VCS server.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| Description | A free-text description for your own reference. |
| DNS Name | The fully-qualified DNS hostname of the server. |
| IP | The IP address of the server or system. |
| Opt. separate api-ip/host | Controls the “Opt. separate api-ip/host” setting for this record. |
| Verify SSL certificates | Use full domain name that matches server certificates |
| Customer | The customer (tenant) this record applies to; leave blank for a global/shared record. |
| Default video address domain | Default domain for video addresses. |
| Username | The account username used to authenticate. |
| Password | Use hyphen (-) to reset the value to zero |
| Cluster | The video cluster this record applies to. |
| Cdr active | Maintenance > Logging > Call Data Records = “Service only” |
1.12.9.17.3. Customers
Customer/tenant records and their per-cluster dialing, provisioning and PIN settings.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| Title | A descriptive title shown in lists and pickers. |
| Video Provider | The primary video provider (bridge) for the customer. |
| Cloud provider | The cloud provider used for hybrid/cloud meetings. |
| Add x seconds before a meeting | Extra seconds added before each meeting. |
| Add x seconds after a meeting | Extra seconds added after each meeting. |
| CMS tenant ID | Must be in CMS |
| Pexip tenant ID | Automatically generated if this customer is not set as the default customer for the cluster |
| Possible SEEVIA API Key | Optional SEEVIA API key. |
| Activate | Activate this customer. |
| Enable access to Core | Allow this customer to use Mividas Core. |
| Enable access to Rooms | Allow this customer to use Mividas Rooms. |
| Logo url | For invitation messages |
| Cluster | The video cluster this record applies to. |
| Default SIP domain | The default SIP domain for the cluster/customer. |
| Separate domain WebRTC/Web access | A separate domain for WebRTC/web access. |
| IVR phone number | The IVR phone number shown to participants. |
| Alternative SIP domains | Allow use of additional domains. Comma-separated |
| Scheduled room number range | Number range used for scheduled meeting rooms. |
| Static room number range | Number range used for static meeting rooms. |
| Provision meetings | Provision meetings to the bridge. |
| Provision meeting rooms x min before scheduled meeting | For scheduled provisioning |
| Delete meeting room x min after scheduled meeting | Minutes after a meeting ends before its room is deleted. |
| Disconnect all participants x min after booked meeting | Minutes after the booked end time before participants are disconnected. |
| Show message x min before the end time of the meeting | Minutes before the end time to show an ending-soon message. |
| Number of PIN digits | The number of digits generated PINs use. |
| Require PIN for guests | Require a PIN for guest participants. |
| Require PIN for moderators | Require a PIN for moderators. |
| Skype domain | The Skype/Teams domain used for gateway calls. |
| Rewrite for Skype SIP domain | Use {conf} to replace with conference ID, {url} for URL (without protocol) |
1.12.9.17.4. LDAP Servers
LDAP directory servers used for user and address-book synchronization.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| Description | A free-text description for your own reference. |
| Customer | The customer (tenant) this record applies to; leave blank for a global/shared record. |
| Type | The type/category of this record. |
| IP address | The IP address of the server or system. |
| Public DNS name | Possibly with a gate, ldap.example.org:389 |
| Internal DNS name for update | Possibly with a gate, ldap.example.org:389 |
| Base DN | The LDAP base DN to search from. |
| Username | Bind DN |
| Password | Use hyphen (-) to reset the value to zero |
| Verify certificates | Whether to verify TLS certificates. |
| Last error | The most recent error message, if any (read-only). |
1.12.9.18. Statistics
Configuration for call statistics / Insight – data sources and domain mapping.
This section contains the following settings pages:
1.12.9.18.1. Domain transforms
Map dialing domains to organization units so call statistics can be grouped by OU.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| Domain | The domain to match. |
| OU Group in AD | The Active Directory OU/group mapped to the organization unit. |
| Organization unit | The organization unit (OU) the record belongs to, used for filtering and statistics. |
1.12.9.18.2. Servers
The data sources (servers) that feed call statistics / Insight.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| Name | A descriptive name used to identify this record. |
| Default domain | The default domain used for this server. |
| Customer | This should only be used for servers of type Endpoint, or VCS when having dedicated clusters for a single customer in multi-tenant installations |
| Typ | The type/category of this record. |
| Cluster | The video cluster this record applies to. |
| Combine servers | Use this to add a tab under Insights to merge call statistics from multiple sources. Only applicable if Type is Combined server. |
| Include external participants | E.g. other team members in Pexip gateway calls that should normally be filtered out |
| Csv export | Enable CSV export for this server. |
| Get cdr url | The URL used to fetch call-detail records (read-only). |
| Ts last event | Timestamp of the last received event (read-only). |
1.12.9.19. Active trace logs
Time-boxed trace-logging sessions that capture detailed diagnostics for a cluster, provider, customer or endpoint.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| Cluster | The video cluster this record applies to. |
| Provider | The meeting platform / provider this record is linked to. |
| Customer | The customer (tenant) this record applies to; leave blank for a global/shared record. |
| Endpoint | The room system (endpoint) this record is linked to. |
| Everything | Trace everything rather than a single target. |
| Ts start | Start timestamp (read-only). |
| Ts stop | Stop timestamp (read-only). |
| User | The user associated with this record. |
| Ts created | When this record was created (read-only). |
1.12.9.20. Messages
Customizable UI messages, help texts and templates shown throughout the products, configurable per customer.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| Title | A descriptive title shown in lists and pickers. |
| Type | The category of message (controls where it is shown). |
| Type key | The internal key identifying where the message is shown. |
| Content | The body content. |
| Customer | The customer (tenant) this record applies to; leave blank for a global/shared record. |
| Active | Whether this record is currently active. |
| Extend other key | Inherit content from another message key. |
| Template format | The format used to render the message template. |
| Attach user manual/other instructions | Max 5 MB, filformat %s |
When editing an existing message the Type and Extend-other fields are also shown.
1.12.9.21. Authorizations for Webex API
Credentials/authorizations that connect Mividas to the Webex API for device synchronization.
Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Core/Rooms interface when the same setting is available there.
Form fields
When adding or editing a record, the following fields are available:
| Field | Description |
|---|---|
| Description | A free-text description for your own reference. |
| Customer | The customer (tenant) this record applies to; leave blank for a global/shared record. |
| Turn on sync | Enable automatic synchronization. |
| Oauth credential | The OAuth service connection used to authenticate. |
| Username | UserPrincipalName/SMTP-adress ([email protected]) |
| Guest issuer id | Deprecated guest issuer id. Note: Separate G2G tenant (new API) should be added instead using backend admin |
| Guest issuer secret | The Webex guest issuer secret. |



























































































