turnUrl is set in applicationContext and then passed to JS it never works for me if set in KMS config, and i have no time for further investigation
Hopefully will get back to this topic after 5.0.0 will be final On Sun, 29 Mar 2020 at 23:54, YUP <[email protected]> wrote: > BTW, just wondering, why in the full version of OM in docker the > kurento server doesn't have turn-environments, but have it for OM? It > should be in the line in the file > /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini > with > turnURL=<User>:<Pass>@<IpAddress>:<Port>[?transport=<Transport>] > > If kurento server runs in docker, it is very easy via KMS_TURN_URL. > > If I understand correctly, OM connects to kurento media server which > next connects to turn server, turn-server is something like a meeting > point for different streams from different clients. Please correct me. > I'm trying to figure out how to correctly setup OM in my environment. > > Regards, > Yarema > > > > On Sun, Mar 29, 2020 at 9:37 AM YUP <[email protected]> wrote: > > > > It's ok, at least now I know what the problem is. > > Best, > > Yarema > > > > On Sun, Mar 29, 2020 at 5:25 AM Maxim Solodovnik <[email protected]> > wrote: > > > > > > I'm installing KMS inside docker to avoid this > > > Not sure if I can help with your advanced config :( > > > > > > On Sun, Mar 29, 2020, 08:57 YUP <[email protected]> wrote: > > >> > > >> Hi Maxim, > > >> Probably I found what caused that issue with *.webm files. I run > > >> openmeetings in a docker container which load dependent kurento > > >> container (see my docker-compose.yml file in my first email). > > >> Something is wrong with communication between them, maybe permission > > >> issue, different users, don't know now. > > >> > > >> > it would be more reasonable to have > > >> > listening-port=80 > > >> > in this case (due to it insecure) > > >> > > >> Good advice, I forgot that firewall allows connection to 80 port too > :) > > >> > > >> Regards, > > >> Yarema > -- WBR Maxim aka solomax
