The MCU/bridge servers (Cisco Meeting Server, Pexip, etc.) that host meetings.
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 |
|---|---|
| Enabled | Whether this record is currently enabled. |
| Description | A free-text description for your own reference. |
| IP address | The IP address of the server or system. |
| Opt. separate IP/host for API calls | Eg. 192.168.1.1:444 |
| Verify SSL certificates | Use full domain name that matches server certificates |
| Username | The account username used to authenticate. |
| Password | Use hyphen (-) to reset the value to zero |
| DNS Name | The fully-qualified DNS hostname of the server. |
| Subtype | Controls the “Subtype” setting for this record. |
| Connected domains | Comma separated |
| Cluster | The video cluster this record applies to. |
| Max load | 125 000 for X2, 250 000 for X3 |
| Use local database for searches | Use local database if possible to browse e.g. meeting rooms and users for better performance and reduced API calls. Should always be used in Pexip multitenant environments |
| Use CDR / Eventsink data for active calls | Use local call data to view active calls for better performance. Requires CDR / Eventsink to be connected to Core. Should always be used in Pexip multitenant environments |