From that I’m assuming you’re using IFrame API to load Jitsi? If so, you could try listening to readyToClose event then redirecting when that event is triggered. That way you’d be redirecting on the parent page rather than in the IFrame itself.
If users are not using IFrame and instead accessing site directly, then you can enable enableClosePage in config.js – this will redirect users to close2.html on leaving the conference. You can update close2.html with any content you want, including a redirect to other sites.
I suppose you could also use the enableClosePage approach and redirect using window.top.location.href = ...; that way it works for both IFrame and direct access.
Hmmm… Strange. Worked when I tried it a few days ago.
You’ll need to pinpoint what’s not working here. Either the event is not triggering or something is blocking your redirect.
Try listening to a few more events, e.g. “raiseHandUpdated”. Then console.log in all callback funcs including readyToClose. Check console to make sure logs happen as expected and if there are errors.
For the record, if you use meet.jit.si as the server, then “readyToClose” will likely be triggered not when user clicks hangout but after the promo content is closed (with the X at the top right). This is in line with the terms of use for the free service where branding and promo should not be hidden from users.