To date, I’ve been setting up Jitsi components with a generic XMPP domain (e.g.
jitsi.xmppdomain) that is different from the domain name it is hosted on (e.g.
meet.mydomain.com). This allowed me to create server images that are preinstalled and preconfigured, and deployable under different hostnames.
This scheme appears to work fine, until I started dabbling with Jibri.
I tried working around the issue by passing my actual domain name to
jibri.conf, but this failed because Jibri also uses the
xmppDomain for pattern matching when extracting the tenant name from the Room JID
Is there any way around this? Or have my shot myself in the foot my assuming XMPP domain could be decoupled from web domain?