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
ADD Click to add a new tenant/customer.
Actions 1. Page refresh ( ) allows you to manually refresh the monitoring view
2. Access relevant documentation ( )
OptionDescription
Search for a customer.
Reload the data to apply any changed filters.
CLUSTER Choose one or more clusters to filter by.

Click APPLY to save, or CLOSE to cancel.
FILTER 1. All types – Filter by all types.
2. Pexip – Filter by Pexip only.
3. Cisco Meeting Server – Filter by CMS only.

Click APPLY to save, or CLOSE 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 > Systems for 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 clients for that customer/tenant.
  • Address books – Shows the total number of address books in use. Clicking its number will take you to Mividas Rooms > Address books for that customer/tenant.
  • Meetings – Shows the total number of meetings they have had. Clicking its number will take you to Mividas Core > Scheduled meetings for 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 > Users with filters applied to show only admin users for that customer/tenant.
OptionDescription
EDIT Takes you to Mividas Core > Admin > Backend admin > Provider > Customer > [Customer-name] where you can edit the customer.

Add customer

When clicking ADD , you will first have to choose which cluster to attach that customer to.

Cisco Meeting Server

OptionDescription
NameEnter the customer/tenant name.
Callbranding URLEnter a callbranding URL.
Invite text URLEnter an IVR branding URL.
IVR branding URLEnter a IVR branding URL.
Create Core customerChoose if it should create the customer in Mividas Core.
Customer API keysEnter Customer API key.
Create LDAP SourceChoose if it should create a LDAP source.
LDAP serverChoose a LDAP server.
LDAP mappingChoose a LDAP mapping.
LDAP base dnSpecify where in the tree the initial search for results should begin. Eaxmple: dc=example,dc=com
LDAP filterHere you choose how users are filtered out and displayed. Example: (&(objectClass=person)(cn=*)(!(ou=ou=Demo)))
Enable StreamingChoose to enable streaming.
Enable RecordingChoose to enable recording.
Click Add 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 API will take you to that place in the API client.

OptionDescription
Manage name conflict with existing customersManage 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.
Sync existing tenants Synchronize existing tenants.

Pexip Infinity

Customer info

OptionDescription
TitleEnter the name fo the Customer/tenant.
Video ProviderSelect which provider the customer should be under. Usually filled in by the choice you made before you got here.
Add x seconds before a meetingAdds 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 meetingAdds 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 IDEnter the CMS tenant ID, must be available within the CMS.
Pexip tenant IDAutomatically generated if this customer is not set as the default customer for the cluster.
Possible SEEVIA API KeyDeprecated
Enable access to CoreChoose if the customer should have access to Mividas Core.
Enable access to RoomsChoose if the customer should have access to Mividas Rooms.
Logo URLEnter a URL to a customer logo. Is used for invitations.

Customer key

OptionDescription
Add another Customer keyAdds a row to add a shared key.
Shared keyEnter the customer shared key.
ActiveActivate or disable the shared key.
DeleteDelete the shared key.

Cluster settings

OptionDescription
ClusterChoose which cluster to add settings to.
Default SIP domainEnter the primary SIP domain that will be used in the video cluster. E.g. video.example.com
Separate domain WebRTC accessEnter the Hostname/FQDN that will be used for WebRTC in your video cluster. E.g. webrtc.example.com
IVR phone numberEnter the phone number that sends you to your video cluster IVR.
Alternative SIP domainsIf the customer uses more than one domain, you can add them here, comma-separated.
Scheduled room number rangeEnter the start and end of the range that should be used to create your booked meeting rooms, e.g. 160000-169999.
Static room number rangeEnter the start and end of the range that should be used to create your static meeting rooms, e.g. 150000-159999.
Provision meetings1. 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 meetingThe amount of minutes before the meeting when the meeting room should be created.
Delete meeting room x min after scheduled meetingThe amount of minutes after the meeting when the meeting room should be deleted.
Disconnect all participants x min after booked meetingThe amount of minutes after the meeting when all participants should be disconnected.
Show message x min before the end time of the meeting timeThe amount of minutes before the end of the meeting when a message about the meeting ending should be shown.
Skype domainCustomers Skype domain.
Rewrite for Skype SIP domainLets you rewrite the Skype SIP domain. Use {conf} to replace with conference ID, {url} for URL (without protocol).
Add another Cluster settingsAdds another cluster configuration for the customer. Fields will be the same as above.

Number matching rules

OptionDescription
ClusterChoose which cluster this rule should apply to.
SIP-URI / alias starts withAdd a prefix to match with. E.g. 123 will match with [email protected].
SIP-URI / alias ends withAdd a suffix to match with, this is usually a domain. E.g. example.com will match with [email protected].
Type of matchingChoose how the rules should match: Both prefix and suffix match, Either prefix or suffix match, Use the Regexp field.
RegexpAllows you to use regular expressions to match rules.
Require external authentication before participants are admittedAllows 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.
PrioritySet a priority for the rules. 1 has priority over 2.
DeleteAllows you to delete a rule.
Add another Number matching ruleAdds another row for a new rule.

Customer policies

OptionDescription
Add another Customer policyAdds a new row for a customer policy.
Participant normal limitSets the total number of allowed calls before the normal limit is reached.
Participant gateway limitSet the total number of allowed gateway calls.
Participant hard limitSets the total number of allowed calls before the hard limit is reached.
Valid fromSet the date from when this policy should be active.
Soft limit actionChoose what should happen if the soft limit is reached: Default value, Ignore, Log, Reject.
Hard limit actionChoose what should happen if the hard limit is reached: Default value, Ignore, Log, Reject.
DeleteAllows you to delete a policy.

Click SAVE to save.

Expressway/VCS

Customer info

OptionDescription
TitleEnter the name fo the Customer/tenant.
Video ProviderSelect which provider the customer should be under. Usually filled in by the choice you made before you got here.
Add x seconds before a meetingAdds 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 meetingAdds 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 IDEnter the CMS tenant ID, must be available within the CMS.
Pexip tenant IDAutomatically generated if this customer is not set as the default customer for the cluster.
Possible SEEVIA API KeyDeprecated
Enable access to CoreChoose if the customer should have access to Mividas Core.
Enable access to RoomsChoose if the customer should have access to Mividas Rooms.
Logo URLEnter a URL to a customer logo. Is used for invitations.

Customer keys

OptionDescription
Add another Customer keyAdds a row to add a shared key.
Shared keyEnter the customer shared key.
ActiveActivate or disable the shared key.
DeleteDelete the shared key.

Cluster settings

OptionDescription
ClusterChoose which cluster to add settings to.
Default SIP domainEnter the primary SIP domain that will be used in the video cluster. E.g. video.example.com
Separate domain WebRTC accessEnter the Hostname/FQDN that will be used for WebRTC in your video cluster. E.g. webrtc.example.com
IVR phone numberEnter the phone number that sends you to your video cluster IVR.
Alternative SIP domainsIf the customer uses more than one domain, you can add them here, comma-separated.
Scheduled room number rangeEnter the start and end of the range that should be used to create your booked meeting rooms, e.g. 160000-169999.
Static room number rangeEnter the start and end of the range that should be used to create your static meeting rooms, e.g. 150000-159999.
Provision meetings1. 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 meetingThe amount of minutes before the meeting when the meeting room should be created.
Delete meeting room x min after scheduled meetingThe amount of minutes after the meeting when the meeting room should be deleted.
Disconnect all participants x min after booked meetingThe amount of minutes after the meeting when all participants should be disconnected.
Show message x min before the end time of the meeting timeThe amount of minutes before the end of the meeting when a message about the meeting ending should be shown.
Skype domainCustomers Skype domain.
Rewrite for Skype SIP domainLets you rewrite the Skype SIP domain. Use {conf} to replace with conference ID, {url} for URL (without protocol).
Add another Cluster settingsAdds another cluster configuration for the customer. Fields will be the same as above.

Number matching rules

OptionDescription
ClusterChoose which cluster this rule should apply to.
SIP-URI / alias starts withAdd a prefix to match with. E.g. 123 will match with [email protected].
SIP-URI / alias ends withAdd a suffix to match with, this is usually a domain. E.g. example.com will match with [email protected].
Type of matchingChoose how the rules should match: Both prefix and suffix match, Either prefix or suffix match, Use the Regexp field.
RegexpAllows you to use regular expressions to match rules.
Require external authentication before participants are admittedAllows 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.
PrioritySet a priority for the rules. 1 has priority over 2.
DeleteAllows you to delete a rule.
Add another Number matching ruleAdds another row for a new rule.

Customer policies

OptionDescription
Add another Customer policyAdds a new row for a customer policy.
Participant normal limitSets the total number of allowed calls before the normal limit is reached.
Participant gateway limitSet the total number of allowed gateway calls.
Participant hard limitSets the total number of allowed calls before the hard limit is reached.
Valid fromSet the date from when this policy should be active.
Soft limit actionChoose what should happen if the soft limit is reached: Default value, Ignore, Log, Reject.
Hard limit actionChoose what should happen if the hard limit is reached: Default value, Ignore, Log, Reject.
DeleteAllows you to delete a policy.

Click SAVE to save.

On This Page
    © Mividas Video Solutions AB 2025