Hello!

Julian Weiß <jul...@ch-weiss.de> schrieb am 26.04.20 um 20:22:27 Uhr:

> Hey there thanks for your reply. Tried it but no results Audio and video is 
> still missing.
> The turnserver is working but only under sudo rights --- is that OK?

netstat -pantu |grep turn

What kind of firewall are you using and how does your network-structure look 
like?

> And I found the log..
> WARNING: cannot find certificate file: turn_server_cert.pem (1)
> 0: WARNING: cannot start TLS and DTLS listeners because certificate file is 
> not set properly
> 0: WARNING: cannot find private key file: turn_server_pkey.pem (1)
> 0: WARNING: cannot start TLS and DTLS listeners because private key file is 
> not set properly
> Might it be possible, that this is the reason I can't get any audio or video.

No, as far as I understand openmeetings uses a selfsigned certificate if you 
didn't configure
it to use yours. Is openmeetings reachable with https?

> I've tried letsencrypt but there themes to be a broken package so that I 
> can't create a ssl certificate  any other ideas how to create certs?
> Thanks a lot for all your great help you all doing such a great job
> 
> Am 26.04.20, 21:25 schrieb "ratatouille" <ratatoui...@bitclusive.de>:
> 
>     Hello!
> 
>     Partha Datta <datta.pa...@gmail.com> schrieb am 24.04.20 um 00:34:14 Uhr:
> 
>     > I have installed OpenMeetings 5.0.0-M3. It is working in LAN both audio 
> &
>     > video.
>     > I have Openmeeting server  behind a Linux firewall with NAT and opened 
> up
>     > 5443 & 8888 ports. I can not see or hear the meeting participants nor he
>     > can see me or hear.  
> 
>     Is this firewall running on the same host like openmeetings? Is this 
> firewalld?
>     What does iptables -nL say on the firewall host?
> 
>     > The setup test, I can see my own voice and video.
>     > Here is my nat table
>     > rule family="ipv4" destination address="112.73.210.134" forward-port
>     > port="5443" protocol="tcp" to-port="5443" to-addr="192.168.110.16"
>     > rule family="ipv4" destination address="112.73.210.134" forward-port
>     > port="8888" protocol="tcp" to-port="8888" to-addr="192.168.110.16"
>     > 
>     > public
>     >   target: default
>     >   icmp-block-inversion: no
>     >   interfaces:
>     >   sources:
>     >   services: mdns dhcpv6-client
>     >   ports: 53/udp 5080/tcp 1935/tcp 5443/tcp
>     >   protocols:
>     >   masquerade: no
>     >   forward-ports:
>     >   source-ports:
>     >   icmp-blocks:
>     >   rich rules:  
> 
>       Andreas

Reply via email to