Hello Maxim,
And thank you for the hint. I read the whole discussion. I tried the
configuration mentioned there but still I cannot make it work.
I checked turn.log and the only possible error I see is this: realm <realm>
user <>: incoming packet message processed, error 401: Unauthorized
This is the configuration I use in applicationContext.xml
<bean id="kurentoHandler"
class="org.apache.openmeetings.core.remote.KurentoHandler" init-method="init"
destroy-method="destroy"
p:kurentoWsUrl="ws://127.0.0.1:8888/kurento"
p:checkTimeout="10000"
p:watchThreadCount="10"
p:turnUrl="<EXTERNAL-IP>:3478"
p:turnUser=""
p:turnSecret="<SECRET STRING>"
p:turnMode="rest"
p:turnTtl="60"
p:objCheckTimeout="200"
/>
This is the configuration I use in Kurento WebRtcEndpoint.conf.ini
turnURL==<SECRET STRING>@<EXTERNAL-IP>:3478
This is the configuration I use in turnserver.conf
listening-port=3478
external-ip=><EXTERNAL-IP>/>@<INTERNAL-IP>
use-auth-secret
static-auth-secret=<SECRET STRING>
realm=<SERVER FQDN>
log-file=/var/tmp/turn.log
simple-log
FIREWALL exceptions are set for 5443,8888 3478 and the media UDP range.
Probably something in the above configuration is NOT ok. Any ideas?
Thank you for all your help.
Best,
CR
From: Maxim Solodovnik <[email protected]>
Reply to: "[email protected]" <[email protected]>
Date: Thursday, 8 August 2019 at 8:44 AM
To: Openmeetings user-list <[email protected]>
Subject: Re: Openmeetings 5.0.0-M2 and NAT
Hello Christos,
The topic was discussed https://markmail.org/message/khy2pjp65wwpmy42
Please read the above discussion and ask additional questions (if any) here :)
On Thu, 8 Aug 2019 at 01:35, Christos T. Rodosthenous
<mailto:[email protected]> wrote:
Hello Maxim and Rene,
Thank you for responding and helping. So I followed the steps in this tutorial
https://doc-kurento.readthedocs.io/en/6.10.0/user/faq.html and setup coturn and
connected it with kurento. I tested using
https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/ and it
works. Unfortunately, in openmeetings I still have the same problems.
Openmeetings is accessible through 5443 (5080 just redirects). Do I need to add
any configuration to openmeetings as well? If you have any other ideas or
pointers, let me know.
Best,
CR
From: "Scholz, Rene" <mailto:[email protected]>
Reply to: "mailto:[email protected]";
<mailto:[email protected]>
Date: Wednesday, 7 August 2019 at 9:05 PM
To: "mailto:[email protected]"; <mailto:[email protected]>
Subject: Re: Openmeetings 5.0.0-M2 and NAT
Hello Christos,
i Had the same problems a few weeks ago.
This week I am in a holiday-trip. If your problems next week not solve I can
try to help you.
Best regards,
René
Am Mittwoch, den 07.08.2019 um 18:52 schrieb Maxim Solodovnik:
You need to install TURN server (I'm using `coturn` ATM)
BTW I would close port 5080
On Wed, 7 Aug 2019 at 17:34, Christos T. Rodosthenous
<mailto:mailto:[email protected]> wrote:
Hello,
I have installed Openmeetings 5.0.0-M2. The installation works very well (both
video and audio) when used though the local organization network. When an
external user joins from a public network, the video and audio are not working
(user joins the room). Firewall ports are allowed through 5443,5080 and 8888
and since everything else in working perfectly from the local network my guess
is that the webRTC is not working with NAT so well.
Anyone else tried that or have any hints on what to do? I am missing some port
exceptions?
CR
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
