Configure and use custom meeting types and access methods

Configuring meeting types and access methods is a powerful way to control access and meeting settings tailored to specific needs. What you can control differs between Cisco Meeting Server and Pexip, depending on their native support.

Cisco Meeting Server

Introduction

Before configuring meeting types and access methods, it is important to understand how Cisco Meeting Server manages meeting settings.

• Values in lower profiles in the image above will override those settings set above.
• If no profile is set at one level, the object inherits values from the profile above.
• A specific setting will be used from the first matching profile that contains that setting, by the priority stated in the image above.
• If a specific setting is left empty, it will be reset, and the next available profile settings will be used instead.

The different profiles and where they can be set(in priority):

• callLegProfile – Settings for a participant
  • callLegs/<id>
  • paticipants/<id>
  • coSpaces/<id>/accessMethods/
  • coSpaces/<id>members/
  • coSpaces/<id>
  • tenants/<id>
  • system/profiles
• callProfile – Settings for a call
  • calls/<id>
  • coSpaces/<id>
  • tenants/<id>
  • system/profiles
• lobbyProfile – Settings on how you can connect
  • coSpaces/<id>/accessMethods/
  • coSpaces/<id>/coSpaceUsers/
  • coSpaces/<id>
  • tenants/<id>
  • system/profiles
• dialInSecurityProfile – Security settings
  • coSpaces/<id>/accessMethods/<id>
  • coSpaces/<id>/coSpaceUsers/<id>
  • coSpaces/<id>
  • tenants/<id>
  • system/profiles
• callBrandingProfile – Branding settings
  • coSpaces/<id> (requires a license)
  • tenants/<id> (requires a license)
  • system/profiles
• ivrBrandingProfile – IVR branding settings
  • tenants/<id> (requires a license)
  • system/profiles

Setting up the Cisco Meeting Server

Before you can configure Mividas, you must first configure the profiles you wish to use in the Cisco Meeting Server. The easiest way to do this is to go to the API page in the web interface of the CMS, e.g. https://cms01.example.com/api_explorer.html. If you have already set up profiles that you wish to use, find and copy the object ID of those profiles, have them ready, and then proceed to Link profiles between Mividas Core and the CMS.

For each profile you wish to use, find them in the tree and click ( ) next to it, then click Create new. Fill in all the settings you wish to use, refer to Cisco’s documentation linked above for detailed information about each setting. When you have filled in all the settings you wish to use, click Create to create the profile. After this, take note of the object ID of the profile you created, which will be needed in the next steps.

Repeat this for all profiles and settings you wish to use.

Link profiles between Mividas Core and the CMS

Log in to Mividas Core with your admin account, and go to admin > backend admin > provider > Cisco Meeting Server profiles and click Add.

Option	Description
Name	Enter a name for the profile, to be used within Mividas.
Is moderator	Choose if the participant using this profile should be considered a moderator. Unknown – The moderator status is not explicitly set and will be determined by the profile’s own settings in the CMS. Yes – The participant using this profile will be considered a moderator. No – The participant using this profile will not be considered a moderator.
Visible	If checked, the profile will be visible to use within Mividas.
Resync	When enabled, the profile data will be synchronized from the CMS during periodic syncs. Disable this to prevent the local profile data from being overwritten.
Profile type	Select what type of profile you are creating. 1. callLegProfile 2. callProfile 3. lobbyProfile 4. dialInSecurityProfile 5. callBrandingProfile
Cluster	Select the CMS cluster to which the profile should be linked.
ID of already created profile in CMS	Enter the object ID of the already created profile in CMS. xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Remote/MCU data	After creation, this will display the relevant data that is set in the profile in the CMS.
System name	After creation, this will display the name of the profile in the CMS, if one has been set.
Is system	Indicates whether the profile was auto-created and is managed internally by the system. ( ) – The profile is system-managed and was auto-created by Mividas Core. ( ) – The profile is a custom, user-created profile.
Active	Indicates whether the profile is active and in use. A profile may become inactive if it can no longer be found in the CMS during synchronization. ( ) – The profile is active and available for use. ( ) – The profile is inactive and will not be used.
Ts last sync	After creation, this will display the date and time of the last synchronization.

When everything is set, click Save to save the profile link. Continue to add all profiles you wish to use.

Create predefined custom meeting types in Mividas Core

Log in to Mividas Core with your admin account, and go to admin > backend admin > meeting_type > Meeting types and click Add.

Option	Description
Cluster	Select the CMS cluster you wish to use
Title	Enter a title for your meeting type.
Description	Enter a description of your meeting type.
Call profile	Select a call profile.
Call leg profile	Select a call leg profile.
Lobby profile	Select a lobby profile.
Call branding profile	Select a call branding profile.
Default number range	Select a default number range.
Allow user settings	When enabled, users can customize meeting room settings when creating rooms from this meeting type. When disabled, the settings defined in the meeting type are locked and cannot be changed by users.
Overrides for values sent via API to MCU	A JSON object with additional or overriding values that will be sent to the provider API when creating or updating meeting rooms. These values are merged into the API call but are not synced back to the provider. Example: {"defaultLayout": "allEqual"}
Overrides for values sent via the Booking API	A JSON object with additional or overriding values used when scheduling meetings through the Booking API. These values apply only to booked meetings, not to static rooms. Example: {"settings": {"lobby": true, "force_encryption": true}}
Enable restriction to customers	Enable this to restrict usage of this meeting type to specific customer(s). This will be automatically activated if any customers are selected in the list below.
Limit to customers	Select any customer who should have access to this meeting type. Hold down “Control”, or “Command” on a Mac, to select more than one. If no customer is selected, all customers will have access.
Show as choice for static VMR in Core	Enable this to make the meeting type available to use when creating static meeting rooms in Mividas Core.
Show as choice for static VMR in Portal	Enable this to make the meeting type available to use when creating static meeting rooms in Mividas Meeting Portal.
Sort index	The sort order of where this meeting type will be shown in the Mividas Meeting Portal. Lowest first.

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 Save 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. Yes – Show this meeting type in Mividas Core for this customer. No – Hide this meeting type in Mividas Core for this customer.
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. Yes – Show this meeting type in the Mividas Meeting Portal for all users in this customer. No – Hide this meeting type in the Mividas Meeting Portal for this customer.
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 Save 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. Guest – This access method is for guest participants joining without moderator privileges. Moderator – This access method is for moderator participants with full meeting control.
Member scope	Defines who can use this access method to join the meeting. None – No specific scope. The access method is not restricted. Public – Anyone can join using this access method. Private – Only specific members or moderators can join. Member – Only organization members can join. Directory – Only users listed in the directory can join.
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 Save to remove that row.
Add another access method	Adds another row to add another access method.

When everything is set, click Save to save the meeting type. To delete the meeting type, click Delete .

Pexip

Create predefined custom meeting types in Mividas Core

Log in to Mividas Core with your admin account, and go to admin > backend admin > meeting_type > Meeting types and click Add.

Option	Description
Cluster	Select the Pexip cluster you wish to use
Title	Enter a title for your meeting type.
Description	Enter a description of your meeting type.
Call profile	Not available for Pexip clusters, leave as is.
Call leg profile	Not available for Pexip clusters, leave as is.
Lobby profile	Not available for Pexip clusters, leave as is.
Call branding profile	Not available for Pexip clusters, leave as is.
Default branding profile	Not available for Pexip clusters, leave as is.
Allow user settings	When enabled, users can customize meeting room settings when creating rooms from this meeting type. When disabled, the settings defined in the meeting type are locked and cannot be changed by users.
Overrides for values sent via API to MCU	A JSON object with additional or overriding values that will be sent to the provider API when creating or updating meeting rooms. These values are merged into the API call but are not synced back to the provider. Example: {"defaultLayout": "allEqual"}
Overrides for values sent via the Booking API	A JSON object with additional or overriding values used when scheduling meetings through the Booking API. These values are only applied to booked meetings, not static rooms. Example: {"settings": {"lobby": true, "force_encryption": true}}
Enable restriction to customers	Enable this to restrict usage of this meeting type to specific customer(s). This will be automatically activated if any customers are selected in the list below.
Limit to customers	Select any customer who should have access to this meeting type. Hold down “Control”, or “Command” on a Mac, to select more than one. If no customer is selected, all customers will have access.
Show as choice for static VMR in Core	Enable this to make the meeting type available to use when creating static meeting rooms in Mividas Core.
Show as choice for static VMR in Portal	Enable this to make the meeting type available to use when creating static meeting rooms in Mividas Meeting Portal.
Sort index	The sort order of where this meeting type will be shown in the Mividas Meeting Portal. Lowest first.

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 Save 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. Yes – Show this meeting type in Mividas Core for this customer. No – Hide this meeting type in Mividas Core for this customer.
For all users	Override whether this meeting type is visible in Mividas Meeting Portal for all users belonging to this customer. Unknown – Use the default setting from the meeting type. Yes – Show this meeting type in the Mividas Meeting Portal for all users in this customer. No – Hide this meeting type in the Mividas Meeting Portal for this customer.
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 Save 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. Guest – This access method is for guest participants joining without moderator privileges. Moderator – This access method is for moderator participants with full meeting control.
Member scope	Defines who can use this access method to join the meeting. None – No specific scope. The access method is not restricted. Public – Anyone can join using this access method. Private – Only specific members or moderators can join. Member – Only organization members can join. Directory – Only users listed in the directory can join.
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 Save to remove that row.
Add another access method	Adds another row to add another access method.

When everything is set, click Save to save the meeting type. To delete the meeting type, click Delete .

Create a custom invitation template for your meeting type

Log in to Mividas Core with your admin account, and go to admin > backend admin > ui_message > Messages and click Add.

Option	Description
Title	Enter a title for the template, to be used within Mividas.
Type key	Enter the meeting type key to match against. E.g. custom_meeting_1 NOTE: This will be the template used for Guest participants. To create a template for the Moderator, add _moderator behind the key, e.g. custom_meeting_1_moderator
Content	If you already have the code for the template that you wish to use, paste it here. If you want to create a template from scratch, just add any text here and then edit it in Mividas Core. This field can’t be left empty, so please enter any placeholder to be able to save the template.
Customer	Select the customer that should use this template.
Active	Check this to activate the template. Uncheck this to disable the template.
Extend other key	Enter the type key of another message template to inherit from. When set, the invitation will use the content from the referenced template instead of its own. This avoids duplicating content when multiple meeting types should share the same invitation text. If the referenced template has been customized for a specific customer, that customer’s version will be used. Leave empty to use this template’s own content.
Template format	Select the format of your template: Auto – Tries Jinja2 first, then falls back to the legacy format if Jinja2 rendering fails. Legacy – Uses simple {placeholder} substitution format. Straightforward but does not support conditional logic. Jinja2 – Uses the Jinja2 template engine with {{ variable }} syntax, supporting conditional logic ({% if %}) and advanced formatting.
Attach user manual/other instructions	Select a document to attach to your invitation, such as a user manual.

When everything is set, click Save to save the template.

Edit the template in Mividas Core

Log in to Mividas Core with your admin account, and go to admin > invite messages. Find the template that you have created, it should be towards the bottom of the list and have the prefix Custom:, e.g. Custom: custom_meeting_1. Click Edit to edit the template.

Option	Description
Enable custom message	Toggle to disable, or enable, the custom message.
	Edit the title of your custom message.
	Edit the content of your custom message.
	This displays information, replacement codes, and conditional variables. Read more about them here.

Click Save to save or click Close to close without saving.

Enable scheduling of your custom meeting type from Mividas Meeting Portal

To be able to schedule meetings using your custom meeting type, you must manually enable it for it to be visible in Mividas Meeting Portal.

Add meeting type

Log in to Mividas Meeting Portal with your admin account, and go to backend admin > MEETING_TYPE > Meeting types and click Add.

This will enable scheduling for this meeting type in the Mividas Meeting Portal and the Mividas Outlook Add-in.

Start by selecting your preferred Language. If only one language is set up, that language will be used for all languages.

Option	Description
Enable	Enable or disable this meeting type in the Mividas Meeting Portal and the Mividas Outlook Add-in.
System name in Core API	The API type name used to match this meeting type against the Mividas Core API. Must match the meeting type key configured in Mividas Core.
Icon	An optional icon shortcode to display on the booking button for this meeting type, e.g. calendar-alt The most common icons to use are: calendar-alt – Calendar icon (default) chalkboard-teacher – Chalkboard/presentation icon (e.g. for webinars) door-closed – Door icon (e.g. for existing rooms) globe – Globe icon (e.g. for cloud/Webex meetings) shield-alt – Shield icon (e.g. for secure meetings) user-circle – User icon (e.g. for external meetings) laptop-medical – Laptop with medical sign (e.g. for medical/patient meetings)
Numerically	The sort order for this meeting type. Lower numbers are displayed first.
Hide booking button on home page	When enabled, the booking button for this meeting type will not be shown on the Mividas Meeting Portal home page. The meeting type can still be accessed from other locations.
Enable invitation step in the scheduling wizard	When enabled, users will see a step in the booking wizard where they can compose and send invitations to participants.
Enable scheduled dialout step in the scheduling wizard	When enabled, users will see a step in the booking wizard where they can configure automatic dial-out to participants at the scheduled meeting time.
Turn on moderator PIN	Controls whether the moderator PIN option is shown. When unchecked (None), the user can choose. When enabled, the moderator PIN option is always shown.
Force guest PIN	When enabled, users are required to set a PIN code for guest participants when scheduling a meeting with this meeting type.
Force moderator PIN	When enabled, users must set a PIN code for the moderators when scheduling a meeting with this meeting type.
Advanced settings	A JSON object for additional advanced configuration options not covered by the standard fields, such as layout settings and custom workflow overrides.
Heading, button	The heading text displayed on the scheduling button for this meeting type.
Help text button	The help/description text shown below the scheduling button heading.
Title in meeting scheduling wizard	The title displayed at the top of the meeting scheduling wizard when booking this meeting type.
Instructions title	The title for the instructions section shown to participants after a meeting is booked.
Moderator instructions title	The translated title for the moderator instructions section shown to moderator participants.

When everything is set, click Save to save. You should now be able to schedule these meetings from Mividas Meeting Portal and Mividas Outlook add-in.