Configuration
Delivery Method
Choose whether you want to use multicast (thick client), caching/relay servers (HLS), or both.
Platforms
When no rule matches, the viewer goes to the platform named in the request URL
(/<route>/<id>). Only the fallback URL is editable — change the domain
or any path part. /j/ is an alias for /zoom/. Webcast uses the
unicast source below. URLs support ${webinar_id}.
| Platform | Route | Fallback URL |
|---|---|---|
| Zoom | /zoom/ | |
| Webex | /webex/ | |
| MS Teams | /microsoft/ | |
| Google Meet | /google/ | |
| Webcast | /webcast/ | Uses the Webcast unicast fallback source ↓ |
Webcast unicast fallback
Source used for /webcast/ when no rule matches. If unset, those requests
return an error asking the viewer to contact their administrator.
User-agent exclusions
Clients whose user-agent matches are excluded from multicast and sent to
the URL fallback — e.g. Macintosh when the app's multicast is unreliable.
| Pattern | Note | |
|---|---|---|
| No exclusions. | ||
Not-found (404) page
HTML returned for requests with no platform, e.g. https://VWM/<id>.
Requests like /zoom/<id> never 404 — the id is passed through and the
platform handles unknown meetings.
Multicast launch page
HTML served on a Multicast-type rule match. Placeholders: ${vivoh_url} (the resolved vivoh:// launch URL), ${webinar_id}, ${logo}, ${header_color}.