Re: Problem: OM5 - Coturn - NAT: my Solution

[Maxim Solodovnik]

yes,

this config is almost identical to what i'm using ...

On Wed, 25 Mar 2020 at 23:40, Daniel Baker 
wrote:

> Maxim  you mean  this  set up  for  TURN  :
>
>
>  Forwarded Message 
> Subject: Problem: OM5 - Coturn - NAT: my Solution
> Date: Tue, 3 Sep 2019 14:46:43 +0200
> From: René Scholz 
> 
> Reply-To: user@openmeetings.apache.org
> To: user@openmeetings.apache.org
>
> Hello,
>
> since yesterday my "Server with NAT" working.
>
> Many thanks at Juan and Maxim helping me a lot.
>
> If anybody have the same problems like me - here are my further steps
> after installation from Alavaros fantastic manual.
> It's possible that I forget something I modified - I tried a lot of ways.
> Feel free to correct me.
>
> 1.) It's important for me to use https.
> I use LetsEncrypt for this so I got LetsEncrypt certificates for my
> subdomain (named: "subdomain.domain.xxx") and configurate the IP of this
> subdomain in the DNS of my provider to the external IP-address.
>
> 2a.) Install coturn:
> apt-get install coturn
>
> 2b.) edit /etc/turnserver.conf
> my config:
>
> verbose
> fingerprint
> use-auth-secret
> static-auth-secret=SECRETSECRET
> realm=subdomain.domain.xxx
> simple-log
> log-file=/var/log/turn.log
> min-port=49152
> max-port=55000
>
> 3.) Config firewall
> Open and forward ports to IP of your OM-server
> 5443
> 3478
> 49152-55000
> (When you put your OM-Server in a DMZ (like me) don't forget to forward to
> port 22 for SSH-access.)
>
> 4.) Edit section " "/opt/openmeetings/conf/server.xml"
>
> ...
>  SSLEnabled="true">
>   
> *  certificateFile="/etc/letsencrypt/live/subdomain.domain.xxx/cert.pem"*
> *
> certificateKeyFile="/etc/letsencrypt/live/subdomain.domain.xxx/privkey.pem"*
> *
> certificateChainFile="/etc/letsencrypt/live/subdomain.domain.xxx/fullchain.pem"
> />*
>   
> 
> ...
>
> 5.) Edit
> "/opt/openmeetings/webapps/openmeetings/WEB-INF/classes/applicationContext.xml"
> In my Example: "123.456.789.123:3478", replace it with your own external IP
>
> at the end of this file edit the last section:
> ...
>  class="org.apache.openmeetings.core.remote.KurentoHandler"
> init-method="init" destroy-method="destroy"
> p:kurentoWsUrl="ws://127.0.0.1:/kurento"
> p:checkTimeout="1"
> p:watchThreadCount="10"
> *p:turnUrl="123.456.789.123:3478"*
> p:turnUser=""
> *p:turnSecret="SECRETSECRET"*
> p:turnMode="rest"
> p:turnTtl="60"
> p:objCheckTimeout="200"
> />
>
> With best regards,
>
> René
>
>

-- 
WBR
Maxim aka solomax

Fwd: Problem: OM5 - Coturn - NAT: my Solution

[Daniel Baker]

Maxim  you mean  this  set up  for  TURN  :



 Forwarded Message 
Subject:Problem: OM5 - Coturn - NAT: my Solution
Date:   Tue, 3 Sep 2019 14:46:43 +0200
From:   René Scholz 
Reply-To:   user@openmeetings.apache.org
To: user@openmeetings.apache.org



Hello,

since yesterday my "Server with NAT" working.

Many thanks at Juan and Maxim helping me a lot.

If anybody have the same problems like me - here are my further steps 
after installation from Alavaros fantastic manual.
It's possible that I forget something I modified - I tried a lot of 
ways. Feel free to correct me.


1.) It's important for me to use https.
I use LetsEncrypt for this so I got LetsEncrypt certificates for my 
subdomain (named: "subdomain.domain.xxx") and configurate the IP of this 
subdomain in the DNS of my provider to the external IP-address.


2a.) Install coturn:
apt-get install coturn

2b.) edit /etc/turnserver.conf
my config:

verbose
fingerprint
use-auth-secret
static-auth-secret=SECRETSECRET
realm=subdomain.domain.xxx
simple-log
log-file=/var/log/turn.log
min-port=49152
max-port=55000

3.) Config firewall
Open and forward ports to IP of your OM-server
5443
3478
49152-55000
(When you put your OM-Server in a DMZ (like me) don't forget to forward 
to port 22 for SSH-access.)


4.) Edit section ""/opt/openmeetings/conf/server.xml"


...

  
/    certificateFile="/etc/letsencrypt/live/subdomain.domain.xxx/cert.pem"//

//certificateKeyFile="/etc/letsencrypt/live/subdomain.domain.xxx/privkey.pem"//
//certificateChainFile="/etc/letsencrypt/live/subdomain.domain.xxx/fullchain.pem" 
/>//

///  

...

5.) Edit 
"/opt/openmeetings/webapps/openmeetings/WEB-INF/classes/applicationContext.xml"

In my Example: "123.456.789.123:3478", replace it with your own external IP

at the end of this file edit the last section:
...
class="org.apache.openmeetings.core.remote.KurentoHandler" 
init-method="init" destroy-method="destroy"

p:kurentoWsUrl="ws://127.0.0.1:/kurento"
p:checkTimeout="1"
p:watchThreadCount="10"
/p:turnUrl="123.456.789.123:3478"/
p:turnUser=""
/p:turnSecret="SECRETSECRET"/
p:turnMode="rest"
p:turnTtl="60"
p:objCheckTimeout="200"
/>

With best regards,

René

Re: Problem: OM5 - Coturn - NAT: my Solution

[Juan Antonio Moreno Carmona]

Hi all.

That is almost exactly my configuration except that I use port 443 for 
https. That way, I don't need to put the port number explicitly in the url.

To achieve this I change line 57 to
redirectPort = "443" />
and line 84 to

Hello,

since yesterday my "Server with NAT" working.

Many thanks at Juan and Maxim helping me a lot.

If anybody have the same problems like me - here are my further steps 
after installation from Alavaros fantastic manual.
It's possible that I forget something I modified - I tried a lot of 
ways. Feel free to correct me.


1.) It's important for me to use https.
I use LetsEncrypt for this so I got LetsEncrypt certificates for my 
subdomain (named: "subdomain.domain.xxx") and configurate the IP of 
this subdomain in the DNS of my provider to the external IP-address.


2a.) Install coturn:
apt-get install coturn

2b.) edit /etc/turnserver.conf
my config:

verbose
fingerprint
use-auth-secret
static-auth-secret=SECRETSECRET
realm=subdomain.domain.xxx
simple-log
log-file=/var/log/turn.log
min-port=49152
max-port=55000

3.) Config firewall
Open and forward ports to IP of your OM-server
5443
3478
49152-55000
(When you put your OM-Server in a DMZ (like me) don't forget to 
forward to port 22 for SSH-access.)


4.) Edit section ""/opt/openmeetings/conf/server.xml"


...

  
/    certificateFile="/etc/letsencrypt/live/subdomain.domain.xxx/cert.pem"//

//certificateKeyFile="/etc/letsencrypt/live/subdomain.domain.xxx/privkey.pem"//
//certificateChainFile="/etc/letsencrypt/live/subdomain.domain.xxx/fullchain.pem" 
/>//

///  

...

5.) Edit 
"/opt/openmeetings/webapps/openmeetings/WEB-INF/classes/applicationContext.xml"
In my Example: "123.456.789.123:3478", replace it with your own 
external IP


at the end of this file edit the last section:
...
class="org.apache.openmeetings.core.remote.KurentoHandler" 
init-method="init" destroy-method="destroy"

p:kurentoWsUrl="ws://127.0.0.1:/kurento"
p:checkTimeout="1"
p:watchThreadCount="10"
/p:turnUrl="123.456.789.123:3478"/
p:turnUser=""
/p:turnSecret="SECRETSECRET"/
p:turnMode="rest"
p:turnTtl="60"
p:objCheckTimeout="200"
/>

With best regards,

René

Re: Problem: OM5 - Coturn - NAT: my Solution

[Maxim Solodovnik]

Thanks for sharing :)))

On Tue, 3 Sep 2019 at 19:46, René Scholz 
wrote:

> Hello,
>
> since yesterday my "Server with NAT" working.
>
> Many thanks at Juan and Maxim helping me a lot.
>
> If anybody have the same problems like me - here are my further steps
> after installation from Alavaros fantastic manual.
> It's possible that I forget something I modified - I tried a lot of ways.
> Feel free to correct me.
>
> 1.) It's important for me to use https.
> I use LetsEncrypt for this so I got LetsEncrypt certificates for my
> subdomain (named: "subdomain.domain.xxx") and configurate the IP of this
> subdomain in the DNS of my provider to the external IP-address.
>
> 2a.) Install coturn:
> apt-get install coturn
>
> 2b.) edit /etc/turnserver.conf
> my config:
>
> verbose
> fingerprint
> use-auth-secret
> static-auth-secret=SECRETSECRET
> realm=subdomain.domain.xxx
> simple-log
> log-file=/var/log/turn.log
> min-port=49152
> max-port=55000
>
> 3.) Config firewall
> Open and forward ports to IP of your OM-server
> 5443
> 3478
> 49152-55000
> (When you put your OM-Server in a DMZ (like me) don't forget to forward to
> port 22 for SSH-access.)
>
> 4.) Edit section " "/opt/openmeetings/conf/server.xml"
>
> ...
>  SSLEnabled="true">
>   
> *  certificateFile="/etc/letsencrypt/live/subdomain.domain.xxx/cert.pem"*
> *
> certificateKeyFile="/etc/letsencrypt/live/subdomain.domain.xxx/privkey.pem"*
> *
> certificateChainFile="/etc/letsencrypt/live/subdomain.domain.xxx/fullchain.pem"
> />*
>   
> 
> ...
>
> 5.) Edit
> "/opt/openmeetings/webapps/openmeetings/WEB-INF/classes/applicationContext.xml"
> In my Example: "123.456.789.123:3478", replace it with your own external IP
>
> at the end of this file edit the last section:
> ...
>  class="org.apache.openmeetings.core.remote.KurentoHandler"
> init-method="init" destroy-method="destroy"
> p:kurentoWsUrl="ws://127.0.0.1:/kurento"
> p:checkTimeout="1"
> p:watchThreadCount="10"
> *p:turnUrl="123.456.789.123:3478"*
> p:turnUser=""
> *p:turnSecret="SECRETSECRET"*
> p:turnMode="rest"
> p:turnTtl="60"
> p:objCheckTimeout="200"
> />
>
> With best regards,
>
> René
>
>

-- 
WBR
Maxim aka solomax

Problem: OM5 - Coturn - NAT: my Solution

[René Scholz]

Hello,

since yesterday my "Server with NAT" working.

Many thanks at Juan and Maxim helping me a lot.

If anybody have the same problems like me - here are my further steps 
after installation from Alavaros fantastic manual.
It's possible that I forget something I modified - I tried a lot of 
ways. Feel free to correct me.


1.) It's important for me to use https.
I use LetsEncrypt for this so I got LetsEncrypt certificates for my 
subdomain (named: "subdomain.domain.xxx") and configurate the IP of this 
subdomain in the DNS of my provider to the external IP-address.


2a.) Install coturn:
apt-get install coturn

2b.) edit /etc/turnserver.conf
my config:

verbose
fingerprint
use-auth-secret
static-auth-secret=SECRETSECRET
realm=subdomain.domain.xxx
simple-log
log-file=/var/log/turn.log
min-port=49152
max-port=55000

3.) Config firewall
Open and forward ports to IP of your OM-server
5443
3478
49152-55000
(When you put your OM-Server in a DMZ (like me) don't forget to forward 
to port 22 for SSH-access.)


4.) Edit section ""/opt/openmeetings/conf/server.xml"


...

  
/    certificateFile="/etc/letsencrypt/live/subdomain.domain.xxx/cert.pem"//

//certificateKeyFile="/etc/letsencrypt/live/subdomain.domain.xxx/privkey.pem"//
//certificateChainFile="/etc/letsencrypt/live/subdomain.domain.xxx/fullchain.pem" 
/>//

///  

...

5.) Edit 
"/opt/openmeetings/webapps/openmeetings/WEB-INF/classes/applicationContext.xml"

In my Example: "123.456.789.123:3478", replace it with your own external IP

at the end of this file edit the last section:
...
class="org.apache.openmeetings.core.remote.KurentoHandler" 
init-method="init" destroy-method="destroy"

p:kurentoWsUrl="ws://127.0.0.1:/kurento"
p:checkTimeout="1"
p:watchThreadCount="10"
/p:turnUrl="123.456.789.123:3478"/
p:turnUser=""
/p:turnSecret="SECRETSECRET"/
p:turnMode="rest"
p:turnTtl="60"
p:objCheckTimeout="200"
/>

With best regards,

René

Re: Problem: OM5 - Coturn - NAT

[René Scholz]

Hm, Aha.
And where is a approach to solve the problem?

In my opinion it is strange that separately mic and cam is functionally, 
but combined not.


Best regards,

René


Am 26.08.2019 um 11:07 schrieb Maxim Solodovnik:

Hello Rene,

Kurento port is not allowed in FW on the demo-next server
So I believe all communications are being made via STUN/TURN

On Mon, 26 Aug 2019 at 15:49, René Scholz 
> wrote:


Hello Maxim,

I made a test with "https://om.alteametasoft.com:8443/next;
.
All is functionally wonderful.

Is there a coturn in the background? Is this a server behind a NAT?

Best regards,

René




Am 26.08.2019 um 09:26 schrieb Maxim Solodovnik:

Is it also doesn't work for on demo-next? (Chrome latest)

On Mon, 26 Aug 2019 at 13:39, René Scholz
mailto:rene.sch...@abakus-edv-systems.de>> wrote:

Hello Maxim,

today I try it out with a Ubuntu-18.04.
It is the same result as with Windows.

- only camera: OK
- only microphone: OK
- together camera and microphone: No

Best regards,

René


Am 22.08.2019 um 04:43 schrieb Maxim Solodovnik:

Hello Rene,

I believe I was able to fix the issue
Could you please double-check?

On Tue, 20 Aug 2019 at 18:53, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

Hello Rene,

i was able to reproduce this problem
It seems to Windows specific (was reproduced at 2 Win10
machines)

https://issues.apache.org/jira/browse/OPENMEETINGS-2101

On Mon, 19 Aug 2019 at 13:05, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

Hello Rene,

Is this issue reproducible if you are using demo-next?

On Fri, 16 Aug 2019 at 14:37, René Scholz
mailto:rene.sch...@abakus-edv-systems.de>> wrote:

Hello,

today I made some further tests with my problem
"camera + microphone not working together".

System server: Ubuntu 18.04, OM5-M3 (yesterday
updated)

Result: When my OM5-server is in the same
intranet with my client who use the camera &
microphone ("cam_mic_client") all is working great.
When this "cam_mic_client" is in another
Intranet (or far away over the internet) only
cam _or_ microphone is working - but not together.

I have checked the open ports on my OM5-server
(with netstat) but there is no connection to my
client-IP-address.

Have anybody an idea what I can try?

Best regards,

René



-- 
WBR

Maxim aka solomax



-- 
WBR

Maxim aka solomax



-- 
WBR

Maxim aka solomax




-- 
WBR

Maxim aka solomax




--
WBR
Maxim aka solomax

Re: Problem: OM5 - Coturn - NAT

[Maxim Solodovnik]

Hello Rene,

Kurento port is not allowed in FW on the demo-next server
So I believe all communications are being made via STUN/TURN

On Mon, 26 Aug 2019 at 15:49, René Scholz 
wrote:

> Hello Maxim,
>
> I made a test with  "https://om.alteametasoft.com:8443/next;
> .
> All is functionally wonderful.
>
> Is there a coturn in the background? Is this a server behind a NAT?
>
> Best regards,
>
> René
>
>
>
>
> Am 26.08.2019 um 09:26 schrieb Maxim Solodovnik:
>
> Is it also doesn't work for on demo-next? (Chrome latest)
>
> On Mon, 26 Aug 2019 at 13:39, René Scholz <
> rene.sch...@abakus-edv-systems.de> wrote:
>
>> Hello Maxim,
>>
>> today I try it out with a Ubuntu-18.04.
>> It is the same result as with Windows.
>>
>> - only camera: OK
>> - only microphone: OK
>> - together camera and microphone: No
>>
>> Best regards,
>>
>> René
>>
>>
>> Am 22.08.2019 um 04:43 schrieb Maxim Solodovnik:
>>
>> Hello Rene,
>>
>> I believe I was able to fix the issue
>> Could you please double-check?
>>
>> On Tue, 20 Aug 2019 at 18:53, Maxim Solodovnik 
>> wrote:
>>
>>> Hello Rene,
>>>
>>> i was able to reproduce this problem
>>> It seems to Windows specific (was reproduced at 2 Win10 machines)
>>>
>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2101
>>>
>>> On Mon, 19 Aug 2019 at 13:05, Maxim Solodovnik 
>>> wrote:
>>>
 Hello Rene,

 Is this issue reproducible if you are using demo-next?

 On Fri, 16 Aug 2019 at 14:37, René Scholz <
 rene.sch...@abakus-edv-systems.de> wrote:

> Hello,
>
> today I made some further tests with my problem "camera + microphone
> not working together".
>
> System server: Ubuntu 18.04, OM5-M3 (yesterday updated)
>
> Result: When my OM5-server is in the same intranet with my client who
> use the camera & microphone ("cam_mic_client") all is working great.
> When this "cam_mic_client" is in another Intranet (or far away over
> the internet) only cam *or* microphone is working - but not together.
>
> I have checked the open ports on my OM5-server (with netstat) but
> there is no connection to my client-IP-address.
>
> Have anybody an idea what I can try?
>
> Best regards,
>
> René
>


 --
 WBR
 Maxim aka solomax

>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>>
>
> --
> WBR
> Maxim aka solomax
>
>
>

-- 
WBR
Maxim aka solomax

Re: Problem: OM5 - Coturn - NAT

[René Scholz]

Hello Maxim,

I made a test with  "https://om.alteametasoft.com:8443/next;.
All is functionally wonderful.

Is there a coturn in the background? Is this a server behind a NAT?

Best regards,

René




Am 26.08.2019 um 09:26 schrieb Maxim Solodovnik:

Is it also doesn't work for on demo-next? (Chrome latest)

On Mon, 26 Aug 2019 at 13:39, René Scholz 
> wrote:


Hello Maxim,

today I try it out with a Ubuntu-18.04.
It is the same result as with Windows.

- only camera: OK
- only microphone: OK
- together camera and microphone: No

Best regards,

René


Am 22.08.2019 um 04:43 schrieb Maxim Solodovnik:

Hello Rene,

I believe I was able to fix the issue
Could you please double-check?

On Tue, 20 Aug 2019 at 18:53, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

Hello Rene,

i was able to reproduce this problem
It seems to Windows specific (was reproduced at 2 Win10 machines)

https://issues.apache.org/jira/browse/OPENMEETINGS-2101

On Mon, 19 Aug 2019 at 13:05, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

Hello Rene,

Is this issue reproducible if you are using demo-next?

On Fri, 16 Aug 2019 at 14:37, René Scholz
mailto:rene.sch...@abakus-edv-systems.de>> wrote:

Hello,

today I made some further tests with my problem
"camera + microphone not working together".

System server: Ubuntu 18.04, OM5-M3 (yesterday updated)

Result: When my OM5-server is in the same intranet
with my client who use the camera & microphone
("cam_mic_client") all is working great.
When this "cam_mic_client" is in another Intranet (or
far away over the internet) only cam _or_ microphone
is working - but not together.

I have checked the open ports on my OM5-server (with
netstat) but there is no connection to my
client-IP-address.

Have anybody an idea what I can try?

Best regards,

René



-- 
WBR

Maxim aka solomax



-- 
WBR

Maxim aka solomax



-- 
WBR

Maxim aka solomax




--
WBR
Maxim aka solomax

Re: Problem: OM5 - Coturn - NAT

[Maxim Solodovnik]

Is it also doesn't work for on demo-next? (Chrome latest)

On Mon, 26 Aug 2019 at 13:39, René Scholz 
wrote:

> Hello Maxim,
>
> today I try it out with a Ubuntu-18.04.
> It is the same result as with Windows.
>
> - only camera: OK
> - only microphone: OK
> - together camera and microphone: No
>
> Best regards,
>
> René
>
>
> Am 22.08.2019 um 04:43 schrieb Maxim Solodovnik:
>
> Hello Rene,
>
> I believe I was able to fix the issue
> Could you please double-check?
>
> On Tue, 20 Aug 2019 at 18:53, Maxim Solodovnik 
> wrote:
>
>> Hello Rene,
>>
>> i was able to reproduce this problem
>> It seems to Windows specific (was reproduced at 2 Win10 machines)
>>
>> https://issues.apache.org/jira/browse/OPENMEETINGS-2101
>>
>> On Mon, 19 Aug 2019 at 13:05, Maxim Solodovnik 
>> wrote:
>>
>>> Hello Rene,
>>>
>>> Is this issue reproducible if you are using demo-next?
>>>
>>> On Fri, 16 Aug 2019 at 14:37, René Scholz <
>>> rene.sch...@abakus-edv-systems.de> wrote:
>>>
 Hello,

 today I made some further tests with my problem "camera + microphone
 not working together".

 System server: Ubuntu 18.04, OM5-M3 (yesterday updated)

 Result: When my OM5-server is in the same intranet with my client who
 use the camera & microphone ("cam_mic_client") all is working great.
 When this "cam_mic_client" is in another Intranet (or far away over the
 internet) only cam *or* microphone is working - but not together.

 I have checked the open ports on my OM5-server (with netstat) but there
 is no connection to my client-IP-address.

 Have anybody an idea what I can try?

 Best regards,

 René

>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>

-- 
WBR
Maxim aka solomax

Re: Problem: OM5 - Coturn - NAT

[René Scholz]

Hello Maxim,

today I try it out with a Ubuntu-18.04.
It is the same result as with Windows.

- only camera: OK
- only microphone: OK
- together camera and microphone: No

Best regards,

René


Am 22.08.2019 um 04:43 schrieb Maxim Solodovnik:

Hello Rene,

I believe I was able to fix the issue
Could you please double-check?

On Tue, 20 Aug 2019 at 18:53, Maxim Solodovnik > wrote:


Hello Rene,

i was able to reproduce this problem
It seems to Windows specific (was reproduced at 2 Win10 machines)

https://issues.apache.org/jira/browse/OPENMEETINGS-2101

On Mon, 19 Aug 2019 at 13:05, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

Hello Rene,

Is this issue reproducible if you are using demo-next?

On Fri, 16 Aug 2019 at 14:37, René Scholz
mailto:rene.sch...@abakus-edv-systems.de>> wrote:

Hello,

today I made some further tests with my problem "camera +
microphone not working together".

System server: Ubuntu 18.04, OM5-M3 (yesterday updated)

Result: When my OM5-server is in the same intranet with my
client who use the camera & microphone ("cam_mic_client")
all is working great.
When this "cam_mic_client" is in another Intranet (or far
away over the internet) only cam _or_ microphone is
working - but not together.

I have checked the open ports on my OM5-server (with
netstat) but there is no connection to my client-IP-address.

Have anybody an idea what I can try?

Best regards,

René



-- 
WBR

Maxim aka solomax



-- 
WBR

Maxim aka solomax



--
WBR
Maxim aka solomax

Re: Problem: OM5 - Coturn - NAT

[Maxim Solodovnik]

Hello Rene,

I believe I was able to fix the issue
Could you please double-check?

On Tue, 20 Aug 2019 at 18:53, Maxim Solodovnik  wrote:

> Hello Rene,
>
> i was able to reproduce this problem
> It seems to Windows specific (was reproduced at 2 Win10 machines)
>
> https://issues.apache.org/jira/browse/OPENMEETINGS-2101
>
> On Mon, 19 Aug 2019 at 13:05, Maxim Solodovnik 
> wrote:
>
>> Hello Rene,
>>
>> Is this issue reproducible if you are using demo-next?
>>
>> On Fri, 16 Aug 2019 at 14:37, René Scholz <
>> rene.sch...@abakus-edv-systems.de> wrote:
>>
>>> Hello,
>>>
>>> today I made some further tests with my problem "camera + microphone not
>>> working together".
>>>
>>> System server: Ubuntu 18.04, OM5-M3 (yesterday updated)
>>>
>>> Result: When my OM5-server is in the same intranet with my client who
>>> use the camera & microphone ("cam_mic_client") all is working great.
>>> When this "cam_mic_client" is in another Intranet (or far away over the
>>> internet) only cam *or* microphone is working - but not together.
>>>
>>> I have checked the open ports on my OM5-server (with netstat) but there
>>> is no connection to my client-IP-address.
>>>
>>> Have anybody an idea what I can try?
>>>
>>> Best regards,
>>>
>>> René
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

Re: Problem: OM5 - Coturn - NAT

[R. Scholz]

Hello Maxim,

nice that you can reproduce it. I hope you can solve it soon.

You mean that under Linux the problem not appears? If you want I try it out.
In my normal work I not use Linux myself, but its no problem to make a 
system.


Best regards

René


Am 20.08.2019 um 13:53 schrieb Maxim Solodovnik:

Hello Rene,

i was able to reproduce this problem
It seems to Windows specific (was reproduced at 2 Win10 machines)

https://issues.apache.org/jira/browse/OPENMEETINGS-2101

On Mon, 19 Aug 2019 at 13:05, Maxim Solodovnik > wrote:


Hello Rene,

Is this issue reproducible if you are using demo-next?

On Fri, 16 Aug 2019 at 14:37, René Scholz
mailto:rene.sch...@abakus-edv-systems.de>> wrote:

Hello,

today I made some further tests with my problem "camera +
microphone not working together".

System server: Ubuntu 18.04, OM5-M3 (yesterday updated)

Result: When my OM5-server is in the same intranet with my
client who use the camera & microphone ("cam_mic_client") all
is working great.
When this "cam_mic_client" is in another Intranet (or far away
over the internet) only cam _or_ microphone is working - but
not together.

I have checked the open ports on my OM5-server (with netstat)
but there is no connection to my client-IP-address.

Have anybody an idea what I can try?

Best regards,

René



-- 
WBR

Maxim aka solomax



--
WBR
Maxim aka solomax

Re: Problem: OM5 - Coturn - NAT

[Maxim Solodovnik]

Hello Rene,

i was able to reproduce this problem
It seems to Windows specific (was reproduced at 2 Win10 machines)

https://issues.apache.org/jira/browse/OPENMEETINGS-2101

On Mon, 19 Aug 2019 at 13:05, Maxim Solodovnik  wrote:

> Hello Rene,
>
> Is this issue reproducible if you are using demo-next?
>
> On Fri, 16 Aug 2019 at 14:37, René Scholz <
> rene.sch...@abakus-edv-systems.de> wrote:
>
>> Hello,
>>
>> today I made some further tests with my problem "camera + microphone not
>> working together".
>>
>> System server: Ubuntu 18.04, OM5-M3 (yesterday updated)
>>
>> Result: When my OM5-server is in the same intranet with my client who use
>> the camera & microphone ("cam_mic_client") all is working great.
>> When this "cam_mic_client" is in another Intranet (or far away over the
>> internet) only cam *or* microphone is working - but not together.
>>
>> I have checked the open ports on my OM5-server (with netstat) but there
>> is no connection to my client-IP-address.
>>
>> Have anybody an idea what I can try?
>>
>> Best regards,
>>
>> René
>>
>
>
> --
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

Problem: OM5 - Coturn - NAT

[René Scholz]

Hello,

today I made some further tests with my problem "camera + microphone not 
working together".


System server: Ubuntu 18.04, OM5-M3 (yesterday updated)

Result: When my OM5-server is in the same intranet with my client who 
use the camera & microphone ("cam_mic_client") all is working great.
When this "cam_mic_client" is in another Intranet (or far away over the 
internet) only cam _or_ microphone is working - but not together.


I have checked the open ports on my OM5-server (with netstat) but there 
is no connection to my client-IP-address.


Have anybody an idea what I can try?

Best regards,

René