Hi Alvaro,

Thanks for the info

> Am 25.09.2023 um 11:21 schrieb Alvaro <zurca...@gmail.com>:
> 
> 
> 
> You said:
> 
> "But the video is only displayed for each local
> user on their own machine"
> 
> ...That is happen to me when the server is not
> connected to Internet. When is connected to Internet
> any user can see the cam of the other users.
> 
> About the live iso in the tutorial section it can
> be booted from USB memory stick.

How get I the iso onto the stick? I tried balenaEtcher which got me just one 
hidden partition on the stick, not recognized as bootable, and I tried dd, 
which got me the same (id 17 HPFS/NTFS) and a warning about iso9660 signature. 
The partition was marked as bootable but not recognized as bootable by BIOS. I 
can mount the partition and get 4 directories. Unfortunately, I have no idea 
how to make it bootable.


> Attached my turn.log file running some minutes ago
> with succes.

I got the same with some differences regarding the interfaces. But after I 
connected to the server I got
In /var/log/coturn/turnserver.log :

3: (1947): DEBUG: turn server id=3 created
3: (1943): INFO: Total auth threads: 3
3: (1943): INFO: turnserver compiled without prometheus support
1661: (1945): ERROR: check_stun_auth: Cannot find credentials of user 
<1695643791:cbb57dbd-240c-4f61-b801-efe0886c2d7f>
1661: (1944): ERROR: check_stun_auth: Cannot find credentials of user 
<1695643791:cbb57dbd-240c-4f61-b801-efe0886c2d7f>
(repeatedly)

So I must have missed an important part of your guide, but I don’t get it.

I generated the secret using openssl and got 
500647a15be4f9cef63a8a5208042cfbfbc50f6ac28b1c10f901ee1caedf8421

I edited /etc/coturn/turnserver:

>————————————<
...
# Listener interface device (optional, Linux only).
# NOT RECOMMENDED.
#
#listening-device=eth0

# TURN listener port for UDP and TCP (Default: 3478).
# Note: actually, TLS & DTLS sessions can connect to the
# "plain" TCP & UDP port(s), too - if allowed by configuration.
#
#listening-port=3478

#
#use-auth-secret
use-auth-secret
...
# by a separate program, so this is why that mode is considered 'dynamic'.
#
#static-auth-secret=north
static-auth-secret=500647a15be4f9cef63a8a5208042cfbfbc50f6ac28b1c10f901ee1caedf8421

...
#
#realm=mycompany.org
realm=letsmeet.commtalk.org
....
#
#stale-nonce=600
stale-nonce=0
>————————————<

And in /opt/openmeetings/…./kurento.properties
>————————————<
################## Kurento ##################
kurento.ws.url=ws://127.0.0.1:8888/kurento
kurento.turn.url=148.251.152.52:3478 
kurento.turn.user=
kurento.turn.secret=500647a15be4f9cef63a8a5208042cfbfbc50f6ac28b1c10f901ee1caedf8421
 
kurento.turn.mode=rest
>————————————<



What do I miss? 


Thanks
Peter





> -------------
> 
> 
> On Mon, 25 Sep 2023 08:55:45 +0200
> Peter Boy <p...@boy-digital.de> wrote:
> 
>> Hi,
>> 
>> 
>> I installed OpenMeetings on a Fedora F38 Server (new VM) following the 
>> Installation Guide by Alvaro Bustos at
>> 
>> https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20OpenMeetings%207.1.0%20on%20Fedora%2038.pdf?version=1&modificationDate=1683788437000&api=v2
>>  
>> 
>> And the corresponding tomcat34 and certificate guide.
>> 
>> The system starts, I can log in and enter one of the (public) predefined 
>> rooms. 
>> 
>> 
>> 
>> But I get a similar issue as user Thomas Scholzen in March this year:
>> 
>> I see all the user in a room by a placeholder graphics. But the video is 
>> only displayed for each local user on their own machine. All other users are 
>> only reprensented by a placeholder image. The admin can obviously perform 
>> all admin tasks, as far as I could notice.
>> 
>> I get the same message on screen: "Media server connection for user XXX is 
>> failed, will try to re-connect“ as described in the post mentioned above. 
>> 
>> 
>> 
>> In the Kurento container I found:
>> ... 
>> ocketTransport.cpp:203:initWebSocket: WebSocket server (ws://) listening on 
>> address '::', port 8888
>> ocketTransport.cpp:89:WebSocketTransport: Secure WebSocket server (wss://) 
>> not enabled.      <========
>> 259:main: Kurento Media Server started
>> ...
>> STUN server not configured! NAT traversal requires STUN or TURN          
>> <======
>> TURN relay server not configured! NAT traversal requires STUN or TURN.   
>> <======
>> 
>> 
>> In log/cotrun/turnserver.log I found
>> 0: (106922): WARNING: cannot find certificate file: turn_server_cert.pem (1)
>> 0: (106922): WARNING: cannot start TLS and DTLS listeners because 
>> certificate file is not set properly
>> 0: (106922): WARNING: cannot find private key file: turn_server_pkey.pem (1)
>> 0: (106922): WARNING: cannot start TLS and DTLS listeners because private 
>> key file is not set properly
>> 0: (106922): INFO: Certificate file found: //turn_server_cert.pem
>> 0: (106922): INFO: Private key file found: //turn_server_pkey.pem
>> 0: (106922): WARNING: NO EXPLICIT LISTENER ADDRESS(ES) ARE CONFIGURED
>> 
>> The installation guide didn’t mention to configure a certificate in Coturn. 
>> I’m not that familiar with the technical details of webrtc. But as far as I 
>> read the docs a while ago, WebRTC/Video always needs a secure connection? So 
>> I’m wondering.
>> 
>> 
>> My questions are:
>> 
>> a) How can I tackle this issue?
>> 
>> 
>> b) Is there a demo VM available that I can run either from an USB stick or 
>> just install in KVM/Libvirt, and use as a kind of role model? (The iso in 
>> the tutorial section is obviously für CD/DVD only and can’t ).  
>> 
>> 
>> c) is there an Ansible playbook for OpenMeetings Installation anywhere (my 
>> search was unsuccessful)?
>> 
>> 
>> 
>> d) Another more general question is:
>> 
>> The starting point for my exploration of OpenMeeting is a search for a 
>> stable video conferencing system that we can introduce into Fedora Server 
>> as a new "specifically supported service".  If I can manage to get a stable 
>> and reproducible test installation, I would then have to compile 
>> OpenMeetings including Kurento from source and build a corresponding RPM. 
>> Kurento is likely to be particularly elaborate. But there was at least a 
>> CentOS 7 rpm. Then it should actually be possible with Fedora, too. 
>> 
>> Do you consider that a feasible project? Or is the OpenMeetings build system 
>> too complex and highly idiosyncratic? I would certainly have some more 
>> questions than I do have now. Would that be feasible with the mailing list 
>> or does it blow up the resources? 
>> 
>> 
>> 
>> Thanks
>> --
>> Peter Boy
>> https://fedoraproject.org/wiki/User:Pboy
>> p...@fedoraproject.org
>> 
>> Timezone: CET (UTC+1) / CEST /UTC+2)
>> 
>> Fedora Server Edition Working Group member
>> Fedora Docs team contributor and board member
>> Java developer and enthusiast
>> 
>> 
>> 
> 
> 
> 
> <turnserver.log>

--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
p...@fedoraproject.org

Timezone: CET (UTC+1) / CEST /UTC+2)

Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast



Reply via email to