Hi Janine. I think other users have had same problem. Try to delete the last line of the file applicationContext.xml. The line that says p:flowoutTimeout and restart openmeetings.

Regards.

El 23/4/20 a las 15:54, Janine Arendt escribió:

Hi Juan,

I have testet your configuration, now I can‘t access my OM Webgui because the request end in a timeout. Here my config files:

*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="ext-IP:4378"

p:turnUser="kurento:passwd“

p:turnSecret="4c6c34650558fa434ffa8c86xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx“

            p:turnMode="rest"

p:turnTtl="60"

p:objCheckTimeout="200"

p:flowoutTimeout="5"

/>

*In Turnserver.conf only this:*

verbose

use-auth-secret

static-auth-secret=4c6c34650558fa434ffa8c866xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

user=kurento:passwd

realm=sub.domain.toplvl

log-file=/var/log/turnserver/turnsrv.log

The turn logfile seems to be okay (no errors):

IO method (main listener thread): epoll (with changelist)

0: Wait for relay ports initialization...

0:   relay 192.168.23.60 initialization...

0:   relay 192.168.23.60 initialization done

0:   relay ::1 initialization...

0:   relay ::1 initialization done

0: Relay ports initialization done

0: IO method (general relay thread): epoll (with changelist)

0: IO method (general relay thread): epoll (with changelist)

0: turn server id=0 created

0: turn server id=3 created

0: IPv4. SCTP listener opened on : 127.0.0.1:3478

0: IPv4. TCP listener opened on : 127.0.0.1:3478

0: IPv4. TCP listener opened on : 127.0.0.1:3478

0: IPv4. SCTP listener opened on : 127.0.0.1:3479

0: IPv4. TCP listener opened on : 127.0.0.1:3479

0: IPv4. TCP listener opened on : 127.0.0.1:3479

0: IPv4. SCTP listener opened on : 192.168.23.60:3478

0: IPv4. TCP listener opened on : 192.168.23.60:3478

0: IPv4. TCP listener opened on : 192.168.23.60:3478

0: IPv4. SCTP listener opened on : 192.168.23.60:3479

0: IPv4. TCP listener opened on : 192.168.23.60:3479

0: IPv4. TCP listener opened on : 192.168.23.60:3479

0: IPv6. SCTP listener opened on : ::1:3478

0: IPv6. TCP listener opened on : ::1:3478

0: IPv6. TCP listener opened on : ::1:3478

0: IPv6. SCTP listener opened on : ::1:3479

0: IPv6. TCP listener opened on : ::1:3479

0: IPv6. TCP listener opened on : ::1:3479

0: IO method (general relay thread): epoll (with changelist)

0: IO method (general relay thread): epoll (with changelist)

If I change to Martinfs config turn.log shows this:

58: check_stun_auth: Cannot find credentials of user <1587579759:kurento:passwd>

58: handle_udp_packet: New UDP endpoint: local addr 192.168.23.60:3478, remote addr xxxxx:9688

58: session 000000000000000003: realm <fqdn-server> user <1587579759:kurento:passwd>: incoming packet message processed, error $

58: session 001000000000000002: realm <fqdn-server> user <>: incoming packet message processed, error 401: Unauthorized

58: check_stun_auth: Cannot find credentials of user <1587579759:kurento:passwd>

58: session 000000000000000004: realm <fqdn-server> user <1587579759:kurento:passwd>: incoming packet message processed, error $

58: handle_udp_packet: New UDP endpoint: local addr 192.168.23.60:3478, remote addr xxxxx:9700

58: session 001000000000000003: realm <fqdn-server> user <>: incoming packet message processed, error 401: Unauthorized

Anything else to do? Iam really new to STUN configurations..

Thanks for your time!

Best wishes

Janine

*Von:* Juan Antonio Moreno Carmona <[email protected]>
*Gesendet:* Mittwoch, 22. April 2020 19:01
*An:* [email protected]
*Betreff:* Re: No Audio / Video

Hi Janine.

This is exactly my turnserver.conf file. I recommend that you rename the included file and create a new one

verbose
use-auth-secret
static-auth-secret=XXXXXXXXXXXXXXXXXXX
user=kurento:XXXXXXXXXXXXX
realm=om.asignatura.es
log-file=/var/log/turnserver/turn.log
pidfile=/run/turnserver/turnserver.pid

The realm value is absolutely irrelevant. Then in the last lines of the file applicationContext.xml change the values for p:turnUrl, p:turnUser and p:turnSecret

            p:kurentoWsUrl="ws://127.0.0.1:8888/kurento" <ws://127.0.0.1:8888/kurento>
            p:checkTimeout="10000"
            p:watchThreadCount="10"
            p:turnUrl="IP:PORT"
            p:turnUser="kurento:XXXXXXXXXXXXXXXXX"
            p:turnSecret="XXXXXXXXXXXXXXXXXX"
            p:turnMode="rest"
            p:turnTtl="60"
            p:objCheckTimeout="200"
            p:flowoutTimeout="5"

Regards.

El 22/4/20 a las 18:41, Chamberland, Martin escribió:

    
imap://jamc60%40gmail%[email protected]:993/fetch%3EUID%3E/Openmeetings%3E2701?header=quotebody&part=1.3&filename=banner1.jpg

    /etc/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

    *Martin Chamberland **
    *Technicien en informatique

    *La Financière agricole du Québec**

    *1400, boul. Guillaume-Couture
    Lévis (Québec) G6W 8K7
    Téléphone : 418 838-5614, poste 6230
    [email protected] <mailto:[email protected]>
    www.fadq.qc.ca <http://www.fadq.qc.ca>

    
imap://jamc60%40gmail%[email protected]:993/fetch%3EUID%3E/Openmeetings%3E2701?header=quotebody&part=1.2&filename=image001.jpg


    *De :*Janine Arendt [mailto:[email protected]]
    *Envoyé :* 22 avril 2020 12:17
    *À :* [email protected]
    <mailto:[email protected]>
    *Objet :* RE: No Audio / Video

    Thanks for your fast response!

    Unfortunately it didn't work for me to delete the port in
    applicationContext.xml.

    So here we are:

    Port 5443, 8888, 3478 TCP ans 3478 UDP are forewarded. In my
    applicationContext i have the Server, User and public IP nothing
    else changed.

    In the /etc/turnserver.conf I added die user-auth, User and realm.
    Realm is set to kurento.org. is this right?

    Anything else to do?

    Von meinem Samsung Galaxy Smartphone gesendet.

    -------- Ursprüngliche Nachricht --------

    Von: "Chamberland, Martin" <[email protected]
    <mailto:[email protected]>>

    Datum: 22.04.20 16:57 (GMT+01:00)

    An: [email protected]
    <mailto:[email protected]>

    Betreff: RE: No Audio / Video

    
imap://jamc60%40gmail%[email protected]:993/fetch%3EUID%3E/Openmeetings%3E2701?header=quotebody&part=1.3&filename=banner1.jpg

    
http://mail-archives.apache.org/mod_mbox/openmeetings-user/201908.mbox/%[email protected]%3E

    *Martin Chamberland **
    *Technicien en informatique

    *La Financière agricole du Québec**

    *1400, boul. Guillaume-Couture
    Lévis (Québec) G6W 8K7
    Téléphone : 418 838-5614, poste 6230
    [email protected] <mailto:[email protected]>
    www.fadq.qc.ca <http://www.fadq.qc.ca>

    cid:[email protected]

    *De :*Janine Arendt [mailto:[email protected]]
    *Envoyé :* 22 avril 2020 10:52
    *À :* [email protected]
    <mailto:[email protected]>
    *Objet :* No Audio / Video

    Hello guys,

    iam new to OM and have a problem with OM5.0.0-M3.

    In my internal network the server works korrekt i can see and hear
    everybody but outsite the network there is no audio and video
    streaming. It is true that i only have to foreward port 5443 for
    https and 8888 for coturn to the server? I installed the service
    with the guide *Installation of Apache OpenMeetings 5.0.0-M3 on
    Ubuntu 18.04 lts *and then*Creating Let's Encrypt SSL Certificates
    and Installing Coturn on Ubuntu 18.04 for OpenMeetings 5.0.0-M3.
    *Is anything wrong with my installation or STUN?**

    Thanks for your time!

Reply via email to