On Fri, 17 Jul 2020 at 15:29, Online Use
wrote:
> I also used cert and key files for TLS in COTURN, I used https in turnurl
> in the applicationContext.xml file, but I got and NS_ERROR_UNEXPECTED.
>
> Probably the application itself is not designed to use TLS for Kurento and
> COTURN?
>
Not sure
Hello Denis,
I guess it should be under webapps/openmeetings/data/upload/upload or
something similar
On Sat, 18 Jul 2020 at 06:56, Denis Noctor wrote:
> Hi there Maxim,
>
> I hope this email finds you well. I made a huge mistake of doing a OM
> system backup via the user interface (which includ
Hello Zhirong,
this wasn't my answer, but I guess "If your firewall is redirectin
port 3478 TCP/UPD to your server,"
mean if your TURN server behind firewall you should made it opened for the
public as well as who;e bunch of UDP (or TCP if you set it up) used by TURN
server as well
On Sat, 18 Ju
Can you please share with me the architecture of the OM system, showing
components and interfaces?
I don't understand how https is secure while the KMS socket is not secure? And
what is the role of TURN in securing the connection? What should TURN be used
in case of https protocol?
I think secu
On Sun, 19 Jul 2020 at 00:26, Online Use
wrote:
> Can you please share with me the architecture of the OM system, showing
> components and interfaces?
>
we don't have such diagram ATM
>
> I don't understand how https is secure while the KMS socket is not secure?
> And what is the role of TURN
Thanks Maxim.
Sent from my iPhone
> On Jul 18, 2020, at 11:23 AM, Maxim Solodovnik wrote:
>
> Hello Denis,
>
> I guess it should be under webapps/openmeetings/data/upload/upload or
> something similar
>
>> On Sat, 18 Jul 2020 at 06:56, Denis Noctor wrote:
>> Hi there Maxim,
>>
>> I hope th
I have been able to use TLS port and certificates with TURN in the
applicationContext.xml file without a problem, but the TURN url doesn't include
protocol (https or wss) only the TLS port number. I have actually commented out
the non-secure port setting in coturn conf. file. It's working fine,
Encryption
Encryption is mandatory part of WebRTC and is enforced on all aspects of
establishing and maintaining a connection. It makes it effectively impossible
for someone to gain access to the contents of a communication stream because
all media streams are securely encrypted through stand
Will do top posting
It seems I wasn't clear enough while describing how everything works
Here is the diagram
https://doc-kurento.readthedocs.io/en/stable/user/writing_applications.html#application-architecture
(the
beautiful one)
As you can see OM is only "control server"
All streams goes directly
I used WebRTC Internals (about:webrtc in Firefox) to log WebRTC activity, but
nothing got logged when I opened an audio & video session using OM. Why, if
WebRTC is actually utilized?
بتاريخ الأحد، 19 تموز 2020 3:00:25 ص غرينتش+2، Maxim Solodovnik
كتب:
Will do top posting
It seems I w
On Sun, 19 Jul 2020 at 12:41, Online Use
wrote:
> I used WebRTC Internals (about:webrtc in Firefox) to log WebRTC activity,
> but nothing got logged when I opened an audio & video session using OM.
> Why, if WebRTC is actually utilized?
>
just have checked using latest FF at Ubuntu 20.04
about:w
11 matches
Mail list logo
