Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to specify hosts hash entries in config.js with properties like org.jitsi.videobridge.ofmeet.hosts.{domain|muc|bridge|focus} #78

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nitomartinez
Copy link

… org.jitsi.videobridge.ofmeet.hosts.{domain|muc|bridge|focus}, fixes #77

… org.jitsi.videobridge.ofmeet.hosts.{domain|muc|bridge|focus}, fixes igniterealtime#77
@nitomartinez nitomartinez changed the title Allow to specify hosts hash entries in config.js with properties like… Allow to specify hosts hash entries in config.js with properties like org.jitsi.videobridge.ofmeet.hosts.{domain|muc|bridge|focus} Jul 3, 2018
@deleolajide
Copy link
Member

Thank you for the contribution

There is a system property for the openfire xmpp domain called xmpp.domain. It might be better to use that instead of creating org.jitsi.videobridge.ofmeet.hosts.domain

@guusdk
Copy link
Member

guusdk commented Jul 4, 2018

As a default, we might want to use the domain name of the first available conference service (which we can lookup), instead of using a hard-coded value.

@nitomartinez
Copy link
Author

@deleolajide In our particular case we would like to still use the default xmpp.domain, but have a different value for the org.jitsi.videobridge.ofmeet.hosts.domain (config.js hosts->domain value)

The reasoning behind that is that the XMPP users are: [email protected]

But the URL for jitsi will be https://jitsi.domain.com:7443/ofmeet

Reasoning is that the ips for each domain are different:

  • domain.com points to the ip address of the website www.domain.com
  • jitsi.domain.com points to a different ip (which is also pointed at with the SRV registry _xmpp-client._tcp and _xmpp-server._tcp for domain.com)

Does this make sense, or is there another way to configure this?

@nitomartinez
Copy link
Author

@guusdk how can we lookup the "conference" and other hardcoded value?

@deleolajide
Copy link
Member

Does this make sense

No. You have confused me. This is my understanding

ofmeet url
https://domain.com/ofmeet/myconf

openfire
openfire xmpp server = xmpp.domain.com (SRV registry _xmpp-server._tcp)
openfire web server = https://xmpp.domain.com:7443

reverse proxy
nginx web server = https://domain.com

config.js
"hosts": {
"domain": "domain.com",
"focus": "focus.domain.com",
"muc": "conference.domain.com",
"bridge": "jitsi-videobridge.domain.com"
},

@nitomartinez
Copy link
Author

Our setup

In our setup the IP of Openfire is not the same as the principal domain, which is used for the company website. That is:

  • The IP of domain.com points to IP A.B.C.10
  • The IP of xmpp.domain.com points to IP D.E.F.20

Let me know if I have made myself clearer now, as full example, copying your example above:

ofmeet url

https://jitsi.domain.com/ofmeet/myconf

** Company website**
www.domain.com
domain.com

openfire
openfire xmpp server = xmpp.domain.com (SRV registry _xmpp-server._tcp)
openfire web server = https://xmpp.domain.com:7443

reverse proxy
nginx web server = https://jitsi.domain.com
(In our case not implemented yet, but valid option for the discussion**

config.js
"hosts": {
"domain": "jitsi.domain.com",
"focus": "focus.domain.com",
"muc": "conference.domain.com",
"bridge": "jitsi-videobridge.domain.com"
},

@deleolajide
Copy link
Member

"domain": "jitsi.domain.com",

I am not sure that is correct. From my experience, that should be domain.com. It is used for the XMPP jingle signalling which requires an XMPP domain name and not a web server domain name.

@nitomartinez
Copy link
Author

In my case everything worked fin, until I shared the screen, in that case we got black screens.

Changing the parameter in the config.js seemed to fix it.

But obviously, I have not the view of the full picture, so not sure if this has other effects that I am not foreseeing.

So far everything seems to be working by setting the domain in the config.js (crossing fingers)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow to customize config.js hosts -> domain property
3 participants