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 wrote:
> BTW, just wondering, why in the full ver
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=:@:[?transport=]
If kurento server runs in docker, it is very e
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 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 wrote:
>>
>> Hi Maxim,
>> Probably I
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 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 (
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
Hello Yarema,
sorry had no time and HW so far to experiment
it would be more reasonable to have
listening-port=80
in this case (due to it insecure)
>> The only problem remain, that session recording files are
>> wav file, not avi. Do you have a clue what is the reason is? Coul it
>> be a ffmpeg
Maxim,
Finally I managed to launch openmeetings with kurento and coturn. The
problem was in coturn server which didn't work as expected. I
installed coturn server on my private laptop (no firewall and NAT)
which listens on port 443, with the following configuration:
listening-port=443
tls-listenin
Maxim,
I made a mistake, in nginx configuration section for openmetings port
should be 5443 instead of 5080, sorry for that.
I also forgot to mention that only tcp requests are allowed in our
firewall, udp if prohibited, as far as know.
Can you examine my configs and say what is wrong?
Regards,
Ya
Please take your time.
I gonna describe my set up briefly .
Initial data:
External nat has address external_nat_ip
All external ports are closed except 443
>From inside allowed only http connections to ports 80, 8080, 443 and 22
Openmeetings runs in docker, I use docker-compose with the following
Hello Yarema,
sorry for keeping silence
I'll try to investigate this config later this week
To much day time job right now :(
Please share your further findings here if any :)
On Mon, 16 Mar 2020 at 09:04, YUP wrote:
>
> Maxim,
> I was also managed to install coturn on external server which lis
Maxim,
I was also managed to install coturn on external server which listen
on port 443. Kurento connects to this port (via TURN_URL,
TURN_USER,TURN_PASS), I can see it in logs. I see in logs that
openmeetings connects to kurento. But I don't understand why all my
construction not working as needed
I was able to connect to kurento websocket which is proxified by
nginx, the solution was very simple, put wss instead of https,
probably for some reasons openmeetings needs to have ws or wss in the
input url:
- OM_KURENTO_WS_URL=wss://external_server_ip_address/kurento
But it is not solved the issu
No, it is not a reason, checked.
On Sun, Mar 15, 2020 at 10:10 AM YUP wrote:
>
> Server has self-signed certificate, can it be a reason?
>
> On Sun, Mar 15, 2020 at 9:38 AM YUP wrote:
> >
> > Just to inform you, I made proxified kurento websocket in nginx and I
> > can connect to it:
> > $ wscat
Server has self-signed certificate, can it be a reason?
On Sun, Mar 15, 2020 at 9:38 AM YUP wrote:
>
> Just to inform you, I made proxified kurento websocket in nginx and I
> can connect to it:
> $ wscat -n --connect https://external_server_ip_address/kurento
> (node:24082) [DEP0123] Deprecation
Just to inform you, I made proxified kurento websocket in nginx and I
can connect to it:
$ wscat -n --connect https://external_server_ip_address/kurento
(node:24082) [DEP0123] DeprecationWarning: Setting the TLS ServerName
to an IP address is not permitted by RFC 6066. This will be ignored in
a fu
Can we just proxify kurento websocket? Something like this
https://gist.github.com/steve-ng/ed6de1fa702ef70bd6ce ?
On Sun, Mar 15, 2020 at 8:41 AM Maxim Solodovnik wrote:
>
> It seems I misread your previous email "all ports except 443, 80, 8080 and
> 22."
> I'm afraid you need more open ports .
It seems I misread your previous email "all ports except 443, 80, 8080 and 22."
I'm afraid you need more open ports ...
I'm not sure but I would investigate if KMS/TURN URLs can be set up
for context i.e.
yourserver:4278/turn, yourserver:/kms in this case you can proxy them
On Sun, 15 Ma
It nothing changes, only 443 is open to the world.
On Sun, Mar 15, 2020 at 8:24 AM Maxim Solodovnik wrote:
>
> Maybe you can set up KMS to use 8080?
> TURN requires more open port to handle "totally closed" networks ...
>
> On Sun, 15 Mar 2020 at 14:18, YUP wrote:
> >
> > It seems to me that I f
Maybe you can set up KMS to use 8080?
TURN requires more open port to handle "totally closed" networks ...
On Sun, 15 Mar 2020 at 14:18, YUP wrote:
>
> It seems to me that I found what is happening. Firewall blocks all non
> http requests out to all ports except 443, 80, 8080 and 22. That is
> wh
It seems to me that I found what is happening. Firewall blocks all non
http requests out to all ports except 443, 80, 8080 and 22. That is
why I don't have connection to outside turn ans stun servers. Is it
possible to connect to those server in such conditions? Tunnels?
On Fri, Mar 13, 2020 at 1:
Hello Yarema,
I'm afraid you need to set-up turn server "visible to KMS"
Which means
1) your KMS port should be opened
OR
2) TURN server should be on the same server as KMS and TURN ports
should be opened
3*) (I'm not nginx expert) maybe you can proxy TURN
requests/responses, I'm not aware on such
Hello all,
Could someone help me with configuration of my OM setup? Any help will
be greatly appreciated.
I have a server which is for several reasons behind NAT, only 443 port
is open. There is sslh balancer, which redirect external traffic to
different targets: nginx, openvpn, etc. Openmeetings
22 matches
Mail list logo
