On Mon, 20 Apr 2020 at 22:09, Zenon Panoussis <[email protected]> wrote: > > > > This diagram is being discussed here > > https://openmeetings.markmail.org/thread/5n2qm57gzogwmmor > > Ah, thanks, this diagram answers all my questions. > > > KMS can be firewalled but in this case you need TURN .... > > If the client has to talk directly to kms, kms needs to > be accessible on a public IP (directly or NAT:ed, but > accessible). The background to my question was that if > the client never talked directly with kurento, I could > limit kms to 127.0.0.1 and close 8433 for input on the > public address(es). > > Another question on a similar subject: is it possible > (or will it be in the future) to tell OM to use and > advertise ksm on a different IP-address and/or port? > In other words, to run OM on one machine and ksm on > another?
Just change this line: https://github.com/apache/openmeetings/blob/master/openmeetings-web/src/main/webapp/WEB-INF/classes/applicationContext.xml#L148 :)) > > Cheers, > > Z > > -- Best regards, Maxim
