KamoCRM

Prosody follows a Settings › Meet save from the next join and never pins a stale policy (Meet Stage QA)

FixKlusterServices
Shipped
November 17, 2026 at 3:16 AM UTC
Author
Kamo
Commit
002f79c

mod_kamo_meet_policy asks kamomeet's room-policy (MediaService read fresh) instead of the classic sidecar's 60 s cache that kept its last value while SecurityService flapped (a 2-minute Max Duration stayed live for two hours). A join asks again once the answer is over 2 s old and waits for it (max 1.5 s, async stanza thread only), so the NEXT join follows a save; organizations with live rooms are re-asked every 30 s; a lost ask is retried after 10 s; a failed refresh keeps the last answer at most 10 minutes after MediaService gave it (kamomeet's staleSeconds counted), then nothing is enforced. A Max Duration change moves a running meeting's clock: lifted, longer, or shorter but never ending within 5 minutes of the change. Offline harness 17/17 in the prosody image.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing