Set the Meet media routing policy (Routing Policy Editor)
Choose Dynamic Hybrid or force one engine, save the override, and read the classification and plan capacity references.
Have questions or need step-by-step guidance on this topic?
Step-by-Step Procedure
Open the editor
From the Meet Console click "Routing Policy Editor", or go to /admin/meet/engines. The page is titled "Hybrid Media Routing & Capacity Policies"; "Back to Meet Console" returns to the dashboard.
Choose the override
In "Manual Routing Override" click one tile: "Dynamic Hybrid" (auto-selection, the default), "Force WebRTC", "Force Jitsi" or "Force LiveKit". The selected tile gets a cyan ring. Nothing is saved yet.
Save
Click "Save Forced-Provider Override" at the top right (it reads "Applying..." while working). The message confirms either "New meetings are now forced onto <provider>." or "Forced-provider override cleared."; a failure shows the server's reason.
Use the reference panels
"Provider Priority & Fallback Order" shows a "Not configurable yet" notice: a custom order is not stored or used, new meetings pick LiveKit, then Jitsi, then WebRTC (whichever is configured and healthy). "Dynamic Headcount Classification Thresholds" lists Micro Meet 2-3, Small Meet 4-10, Team Meet 11-25 and Conference 26+ participants. "Plan Capacity Policy Mesh" lists the real policies in effect: plan, seat range, maximum duration, recording limit and guests.
The chosen override is stored on the server and the dashboard shows or clears the "Emergency Manual Routing Active" panel accordingly.
Troubleshooting & Failure Modes
Was this guide helpful?
Help us refine our platform documentation