You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by "R. Scholz" <re...@abakus-edv-systems.de> on 2019/07/16 14:22:58 UTC
OM5-Kurento-Coturn
Hello,
the last days I tried many times to bring up the combination OM5 -
Coturn - Kurento.
When i try to connect with the recommended site
"https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/"
all seems OK. In the Coturn-log I find a few entries like this:
/6839: session 000000000000000005: realm <kurento.org> user <resch>:
incoming packet ALLOCATE processed, success//
//6839: session 001000000000000004: realm <kurento.org> user <resch>:
incoming packet REFRESH processed, success//
/
As username I see: <resch>. That's OK, that is the user I created.
When I connect with OM5 I get entries like this:
/7132: check_stun_auth: Cannot find credentials of user <1563290264:resch>/
I see that in front of my username the linux-timestamp was sent and I
hope this is the reason that my stream is not functionally.
Can I switch off this timestamp? Or where I have to configurate Coturn
that it accept this?
With best regards,
René
Re: OM5-Kurento-Coturn
Posted by Juan Antonio Moreno Carmona <ja...@gmail.com>.
I am happy that is was useful for you.
El 17/7/19 a las 12:13, René Scholz escribió:
> Hello Juan,
>
> thank you a lot for your help.
> After a few weeks with hundreds of unsuccessful attempts now its
> running with your configuration.
>
> You are my hero of the day.
>
> With best regards,
>
> René
>
>
>
>
>
> Am 17.07.2019 um 10:51 schrieb Juan Antonio Moreno Carmona:
>> Hi
>>
>> I use Archlinux. May be you must change something else in your Ubuntu
>> but you can try my configuration. After many days and many failed
>> attempts, this is the configuration that works for me.
>>
>> Make a backup of the coturn configuration file.
>>
>> sudo mv /etc/turnserver/turnserver.conf
>> /etc/turnserver/turnserver.conf.orig
>>
>> Create a new configuration file /etc/turnserver/turnserver.conf with
>> these lines:
>>
>> verbose
>>
>> fingerprint
>>
>> use-auth-secret
>>
>> static-auth-secret=XXXXXXXXXXXXXXXX
>>
>> realm=your.domain.name
>>
>> As static-auth-secret I used a string of 20 uppercase and lowercase
>> letters, for example, jfdwXCjViTdvDlgVVysx. Then, in the file
>> /opt/open500/webapps/openmeetings/WEB-INF/classes/applicationContext.xml
>> change following lines:
>>
>> p:turnUrl="IPOfYourCoturnInstallation"
>>
>> p:turnSecret="TheStringYouUsedBeforeInTurnserverconfig"
>>
>>
>> And that's it. Restart coturn, then restart openmeeetings and try it.
>> I hope this is enough. Tell us if it works for you.
>>
>> El 16/7/19 a las 18:02, Maxim Solodovnik escribió:
>>> As I wrote multiple times
>>> I would recommend to use this answer
>>> https://stackoverflow.com/questions/35766382/coturn-how-to-use-turn-rest-api/35767224#35767224
>>>
>>> as guide
>>> You can start coturn using commandline with different parameters
>>> and check the result in real-time
>>>
>>> You need to specify valid parameters in applicationContext.xml file
>>>
>>> disclaimer: I'm not WebRTC/Coturn expert, so my config might be not
>>> the best one :(
>>>
>>> On Tue, 16 Jul 2019 at 21:23, R. Scholz
>>> <re...@abakus-edv-systems.de> wrote:
>>>> Hello,
>>>>
>>>> the last days I tried many times to bring up the combination OM5 -
>>>> Coturn - Kurento.
>>>>
>>>> When i try to connect with the recommended site
>>>> "https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/"
>>>> all seems OK. In the Coturn-log I find a few entries like this:
>>>> 6839: session 000000000000000005: realm <kurento.org> user <resch>:
>>>> incoming packet ALLOCATE processed, success
>>>> 6839: session 001000000000000004: realm <kurento.org> user <resch>:
>>>> incoming packet REFRESH processed, success
>>>>
>>>> As username I see: <resch>. That's OK, that is the user I created.
>>>>
>>>> When I connect with OM5 I get entries like this:
>>>> 7132: check_stun_auth: Cannot find credentials of user
>>>> <1563290264:resch>
>>>>
>>>> I see that in front of my username the linux-timestamp was sent and
>>>> I hope this is the reason that my stream is not functionally.
>>>>
>>>> Can I switch off this timestamp? Or where I have to configurate
>>>> Coturn that it accept this?
>>>>
>>>> With best regards,
>>>>
>>>> René
>>>>
>>>>
>>>
>>
>
Re: OM5-Kurento-Coturn
Posted by René Scholz <re...@abakus-edv-systems.de>.
Hello Juan,
thank you a lot for your help.
After a few weeks with hundreds of unsuccessful attempts now its running
with your configuration.
You are my hero of the day.
With best regards,
René
Am 17.07.2019 um 10:51 schrieb Juan Antonio Moreno Carmona:
> Hi
>
> I use Archlinux. May be you must change something else in your Ubuntu
> but you can try my configuration. After many days and many failed
> attempts, this is the configuration that works for me.
>
> Make a backup of the coturn configuration file.
>
> sudo mv /etc/turnserver/turnserver.conf
> /etc/turnserver/turnserver.conf.orig
>
> Create a new configuration file /etc/turnserver/turnserver.conf with
> these lines:
>
> verbose
>
> fingerprint
>
> use-auth-secret
>
> static-auth-secret=XXXXXXXXXXXXXXXX
>
> realm=your.domain.name
>
> As static-auth-secret I used a string of 20 uppercase and lowercase
> letters, for example, jfdwXCjViTdvDlgVVysx. Then, in the file
> /opt/open500/webapps/openmeetings/WEB-INF/classes/applicationContext.xml
> change following lines:
>
> p:turnUrl="IPOfYourCoturnInstallation"
>
> p:turnSecret="TheStringYouUsedBeforeInTurnserverconfig"
>
>
> And that's it. Restart coturn, then restart openmeeetings and try it.
> I hope this is enough. Tell us if it works for you.
>
> El 16/7/19 a las 18:02, Maxim Solodovnik escribió:
>> As I wrote multiple times
>> I would recommend to use this answer
>> https://stackoverflow.com/questions/35766382/coturn-how-to-use-turn-rest-api/35767224#35767224
>>
>> as guide
>> You can start coturn using commandline with different parameters
>> and check the result in real-time
>>
>> You need to specify valid parameters in applicationContext.xml file
>>
>> disclaimer: I'm not WebRTC/Coturn expert, so my config might be not
>> the best one :(
>>
>> On Tue, 16 Jul 2019 at 21:23, R. Scholz
>> <re...@abakus-edv-systems.de> wrote:
>>> Hello,
>>>
>>> the last days I tried many times to bring up the combination OM5 -
>>> Coturn - Kurento.
>>>
>>> When i try to connect with the recommended site
>>> "https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/"
>>> all seems OK. In the Coturn-log I find a few entries like this:
>>> 6839: session 000000000000000005: realm <kurento.org> user <resch>:
>>> incoming packet ALLOCATE processed, success
>>> 6839: session 001000000000000004: realm <kurento.org> user <resch>:
>>> incoming packet REFRESH processed, success
>>>
>>> As username I see: <resch>. That's OK, that is the user I created.
>>>
>>> When I connect with OM5 I get entries like this:
>>> 7132: check_stun_auth: Cannot find credentials of user
>>> <1563290264:resch>
>>>
>>> I see that in front of my username the linux-timestamp was sent and
>>> I hope this is the reason that my stream is not functionally.
>>>
>>> Can I switch off this timestamp? Or where I have to configurate
>>> Coturn that it accept this?
>>>
>>> With best regards,
>>>
>>> René
>>>
>>>
>>
>
Re: OM5-Kurento-Coturn
Posted by Juan Antonio Moreno Carmona <ja...@gmail.com>.
This is a great idea. I use KeePassXC to generate random passwords but I
had not thought about changing them regularly. Thanks.
El 17/7/19 a las 11:25, Maxim Solodovnik escribió:
> Thanks for sharing your config :)
>
> I'm additionally using `apg` tool to generate random passwords of
> desired length and quality and change them automatically :)
>
> On Wed, 17 Jul 2019 at 15:52, Juan Antonio Moreno Carmona
> <ja...@gmail.com> wrote:
>> Hi
>>
>> I use Archlinux. May be you must change something else in your Ubuntu
>> but you can try my configuration. After many days and many failed
>> attempts, this is the configuration that works for me.
>>
>> Make a backup of the coturn configuration file.
>>
>> sudo mv /etc/turnserver/turnserver.conf /etc/turnserver/turnserver.conf.orig
>>
>> Create a new configuration file /etc/turnserver/turnserver.conf with
>> these lines:
>>
>> verbose
>>
>> fingerprint
>>
>> use-auth-secret
>>
>> static-auth-secret=XXXXXXXXXXXXXXXX
>>
>> realm=your.domain.name
>>
>> As static-auth-secret I used a string of 20 uppercase and lowercase
>> letters, for example, jfdwXCjViTdvDlgVVysx. Then, in the file
>> /opt/open500/webapps/openmeetings/WEB-INF/classes/applicationContext.xml
>> change following lines:
>>
>> p:turnUrl="IPOfYourCoturnInstallation"
>>
>> p:turnSecret="TheStringYouUsedBeforeInTurnserverconfig"
>>
>>
>> And that's it. Restart coturn, then restart openmeeetings and try it. I
>> hope this is enough. Tell us if it works for you.
>>
>> El 16/7/19 a las 18:02, Maxim Solodovnik escribió:
>>> As I wrote multiple times
>>> I would recommend to use this answer
>>> https://stackoverflow.com/questions/35766382/coturn-how-to-use-turn-rest-api/35767224#35767224
>>> as guide
>>> You can start coturn using commandline with different parameters
>>> and check the result in real-time
>>>
>>> You need to specify valid parameters in applicationContext.xml file
>>>
>>> disclaimer: I'm not WebRTC/Coturn expert, so my config might be not
>>> the best one :(
>>>
>>> On Tue, 16 Jul 2019 at 21:23, R. Scholz
>>> <re...@abakus-edv-systems.de> wrote:
>>>> Hello,
>>>>
>>>> the last days I tried many times to bring up the combination OM5 - Coturn - Kurento.
>>>>
>>>> When i try to connect with the recommended site "https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/"
>>>> all seems OK. In the Coturn-log I find a few entries like this:
>>>> 6839: session 000000000000000005: realm <kurento.org> user <resch>: incoming packet ALLOCATE processed, success
>>>> 6839: session 001000000000000004: realm <kurento.org> user <resch>: incoming packet REFRESH processed, success
>>>>
>>>> As username I see: <resch>. That's OK, that is the user I created.
>>>>
>>>> When I connect with OM5 I get entries like this:
>>>> 7132: check_stun_auth: Cannot find credentials of user <1563290264:resch>
>>>>
>>>> I see that in front of my username the linux-timestamp was sent and I hope this is the reason that my stream is not functionally.
>>>>
>>>> Can I switch off this timestamp? Or where I have to configurate Coturn that it accept this?
>>>>
>>>> With best regards,
>>>>
>>>> René
>>>>
>>>>
>
>
Re: OM5-Kurento-Coturn
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks for sharing your config :)
I'm additionally using `apg` tool to generate random passwords of
desired length and quality and change them automatically :)
On Wed, 17 Jul 2019 at 15:52, Juan Antonio Moreno Carmona
<ja...@gmail.com> wrote:
>
> Hi
>
> I use Archlinux. May be you must change something else in your Ubuntu
> but you can try my configuration. After many days and many failed
> attempts, this is the configuration that works for me.
>
> Make a backup of the coturn configuration file.
>
> sudo mv /etc/turnserver/turnserver.conf /etc/turnserver/turnserver.conf.orig
>
> Create a new configuration file /etc/turnserver/turnserver.conf with
> these lines:
>
> verbose
>
> fingerprint
>
> use-auth-secret
>
> static-auth-secret=XXXXXXXXXXXXXXXX
>
> realm=your.domain.name
>
> As static-auth-secret I used a string of 20 uppercase and lowercase
> letters, for example, jfdwXCjViTdvDlgVVysx. Then, in the file
> /opt/open500/webapps/openmeetings/WEB-INF/classes/applicationContext.xml
> change following lines:
>
> p:turnUrl="IPOfYourCoturnInstallation"
>
> p:turnSecret="TheStringYouUsedBeforeInTurnserverconfig"
>
>
> And that's it. Restart coturn, then restart openmeeetings and try it. I
> hope this is enough. Tell us if it works for you.
>
> El 16/7/19 a las 18:02, Maxim Solodovnik escribió:
> > As I wrote multiple times
> > I would recommend to use this answer
> > https://stackoverflow.com/questions/35766382/coturn-how-to-use-turn-rest-api/35767224#35767224
> > as guide
> > You can start coturn using commandline with different parameters
> > and check the result in real-time
> >
> > You need to specify valid parameters in applicationContext.xml file
> >
> > disclaimer: I'm not WebRTC/Coturn expert, so my config might be not
> > the best one :(
> >
> > On Tue, 16 Jul 2019 at 21:23, R. Scholz
> > <re...@abakus-edv-systems.de> wrote:
> >> Hello,
> >>
> >> the last days I tried many times to bring up the combination OM5 - Coturn - Kurento.
> >>
> >> When i try to connect with the recommended site "https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/"
> >> all seems OK. In the Coturn-log I find a few entries like this:
> >> 6839: session 000000000000000005: realm <kurento.org> user <resch>: incoming packet ALLOCATE processed, success
> >> 6839: session 001000000000000004: realm <kurento.org> user <resch>: incoming packet REFRESH processed, success
> >>
> >> As username I see: <resch>. That's OK, that is the user I created.
> >>
> >> When I connect with OM5 I get entries like this:
> >> 7132: check_stun_auth: Cannot find credentials of user <1563290264:resch>
> >>
> >> I see that in front of my username the linux-timestamp was sent and I hope this is the reason that my stream is not functionally.
> >>
> >> Can I switch off this timestamp? Or where I have to configurate Coturn that it accept this?
> >>
> >> With best regards,
> >>
> >> René
> >>
> >>
> >
--
WBR
Maxim aka solomax
Re: OM5-Kurento-Coturn
Posted by Juan Antonio Moreno Carmona <ja...@gmail.com>.
Hi
I use Archlinux. May be you must change something else in your Ubuntu
but you can try my configuration. After many days and many failed
attempts, this is the configuration that works for me.
Make a backup of the coturn configuration file.
sudo mv /etc/turnserver/turnserver.conf /etc/turnserver/turnserver.conf.orig
Create a new configuration file /etc/turnserver/turnserver.conf with
these lines:
verbose
fingerprint
use-auth-secret
static-auth-secret=XXXXXXXXXXXXXXXX
realm=your.domain.name
As static-auth-secret I used a string of 20 uppercase and lowercase
letters, for example, jfdwXCjViTdvDlgVVysx. Then, in the file
/opt/open500/webapps/openmeetings/WEB-INF/classes/applicationContext.xml
change following lines:
p:turnUrl="IPOfYourCoturnInstallation"
p:turnSecret="TheStringYouUsedBeforeInTurnserverconfig"
And that's it. Restart coturn, then restart openmeeetings and try it. I
hope this is enough. Tell us if it works for you.
El 16/7/19 a las 18:02, Maxim Solodovnik escribió:
> As I wrote multiple times
> I would recommend to use this answer
> https://stackoverflow.com/questions/35766382/coturn-how-to-use-turn-rest-api/35767224#35767224
> as guide
> You can start coturn using commandline with different parameters
> and check the result in real-time
>
> You need to specify valid parameters in applicationContext.xml file
>
> disclaimer: I'm not WebRTC/Coturn expert, so my config might be not
> the best one :(
>
> On Tue, 16 Jul 2019 at 21:23, R. Scholz
> <re...@abakus-edv-systems.de> wrote:
>> Hello,
>>
>> the last days I tried many times to bring up the combination OM5 - Coturn - Kurento.
>>
>> When i try to connect with the recommended site "https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/"
>> all seems OK. In the Coturn-log I find a few entries like this:
>> 6839: session 000000000000000005: realm <kurento.org> user <resch>: incoming packet ALLOCATE processed, success
>> 6839: session 001000000000000004: realm <kurento.org> user <resch>: incoming packet REFRESH processed, success
>>
>> As username I see: <resch>. That's OK, that is the user I created.
>>
>> When I connect with OM5 I get entries like this:
>> 7132: check_stun_auth: Cannot find credentials of user <1563290264:resch>
>>
>> I see that in front of my username the linux-timestamp was sent and I hope this is the reason that my stream is not functionally.
>>
>> Can I switch off this timestamp? Or where I have to configurate Coturn that it accept this?
>>
>> With best regards,
>>
>> René
>>
>>
>
Re: OM5-Kurento-Coturn
Posted by Maxim Solodovnik <so...@gmail.com>.
As I wrote multiple times
I would recommend to use this answer
https://stackoverflow.com/questions/35766382/coturn-how-to-use-turn-rest-api/35767224#35767224
as guide
You can start coturn using commandline with different parameters
and check the result in real-time
You need to specify valid parameters in applicationContext.xml file
disclaimer: I'm not WebRTC/Coturn expert, so my config might be not
the best one :(
On Tue, 16 Jul 2019 at 21:23, R. Scholz
<re...@abakus-edv-systems.de> wrote:
>
> Hello,
>
> the last days I tried many times to bring up the combination OM5 - Coturn - Kurento.
>
> When i try to connect with the recommended site "https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/"
> all seems OK. In the Coturn-log I find a few entries like this:
> 6839: session 000000000000000005: realm <kurento.org> user <resch>: incoming packet ALLOCATE processed, success
> 6839: session 001000000000000004: realm <kurento.org> user <resch>: incoming packet REFRESH processed, success
>
> As username I see: <resch>. That's OK, that is the user I created.
>
> When I connect with OM5 I get entries like this:
> 7132: check_stun_auth: Cannot find credentials of user <1563290264:resch>
>
> I see that in front of my username the linux-timestamp was sent and I hope this is the reason that my stream is not functionally.
>
> Can I switch off this timestamp? Or where I have to configurate Coturn that it accept this?
>
> With best regards,
>
> René
>
>
--
WBR
Maxim aka solomax