You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by jox joe <jo...@gmail.com> on 2021/01/17 17:38:37 UTC
Multimedia server is inaccessible
Hello everybody,
"Multimedia server is inaccessible"
This message sometimes appears.
It would be good to know what it is caused by.
1. By the Openmeetings server?
2. By the Kurento mediaserver?
3. By the browser(s)?
4. By something else?
Debugging a communication module is time consuming
and cooperation is needed to determin what is the problem
in the given environment. The test servers do not help too much
in these cases.
I tried the previous Openmeetings version (4.x/Flash and Red5 server)
and it was very stable.
(I like the WHITEBOARD approach of Openmettings.)
Any opinion?
Thank you.
Re: Multimedia server is inaccessible
Posted by jox joe <jo...@gmail.com>.
Hello kaffeesurrogat,
jawohl (=yes), CoTurn is installed and tested based on your
previous posts. I forgot to mention CoTurn.
I'm going to have more time after 2021. June and will try to run
some tests.
The amended list:
It would be good to know what
"Multimedia server is inaccessible" is caused by.
1. By the Openmeetings server?
2. By the Kurento mediaserver?
3. By the browser(s)?
4. By CoTurn?
5. By something else?
Example for item 5: quality/speed of the internet connection.
COMMAND:
turnutils_uclient -T -W <static-auth-secret> <public-turnserver-ip>
*******************OUTPUT:
0: Total connect time is 0
0: 2 connections are completed
1: start_mclient: msz=2, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~
0, tot_recv_bytes ~ 0
2: start_mclient: msz=2, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~
0, tot_recv_bytes ~ 0
3: start_mclient: msz=2, tot_send_msgs=0, tot_recv_msgs=0, tot_send_bytes ~
0, tot_recv_bytes ~ 0
4: start_mclient: msz=2, tot_send_msgs=5, tot_recv_msgs=5, tot_send_bytes ~
500, tot_recv_bytes ~ 500
5: start_mclient: msz=2, tot_send_msgs=5, tot_recv_msgs=5, tot_send_bytes ~
500, tot_recv_bytes ~ 500
6: start_mclient: msz=2, tot_send_msgs=5, tot_recv_msgs=5, tot_send_bytes ~
500, tot_recv_bytes ~ 500
6: start_mclient: tot_send_msgs=10, tot_recv_msgs=10
6: start_mclient: tot_send_bytes ~ 1000, tot_recv_bytes ~ 1000
6: Total transmit time is 6
6: Total lost packets 0 (0.000000%), total send dropped 0 (0.000000%)
6: Average round trip delay 4.700000 ms; min = 0 ms, max = 23 ms
6: Average jitter 8.900000 ms; min = 0 ms, max = 24 ms
*******************
In the coturn log I can see this sometimes:
31: session 00302: realm <kurento.org> user <>: incoming packet message
processed, error 401: Unauthorized
As far as I know it is a legitimate message.
Thank you.
kaffeesurrogat <ka...@posteo.de> ezt írta (időpont: 2021. jan.
17., V, 19:29):
> did you install coturn ?
>
> On 17/01/2021 18:38, jox joe wrote:
> > Hello everybody,
> >
> > "Multimedia server is inaccessible"
> > This message sometimes appears.
> > It would be good to know what it is caused by.
> > 1. By the Openmeetings server?
> > 2. By the Kurento mediaserver?
> > 3. By the browser(s)?
> > 4. By something else?
> >
> > Debugging a communication module is time consuming
> > and cooperation is needed to determin what is the problem
> > in the given environment. The test servers do not help too much
> > in these cases.
> >
> > I tried the previous Openmeetings version (4.x/Flash and Red5 server)
> > and it was very stable.
> >
> > (I like the WHITEBOARD approach of Openmettings.)
> >
> > Any opinion?
> > Thank you.
> >
> >
> >
> >
>
>
Re: Multimedia server is inaccessible
Posted by kaffeesurrogat <ka...@posteo.de>.
did you install coturn ?
On 17/01/2021 18:38, jox joe wrote:
> Hello everybody,
>
> "Multimedia server is inaccessible"
> This message sometimes appears.
> It would be good to know what it is caused by.
> 1. By the Openmeetings server?
> 2. By the Kurento mediaserver?
> 3. By the browser(s)?
> 4. By something else?
>
> Debugging a communication module is time consuming
> and cooperation is needed to determin what is the problem
> in the given environment. The test servers do not help too much
> in these cases.
>
> I tried the previous Openmeetings version (4.x/Flash and Red5 server)
> and it was very stable.
>
> (I like the WHITEBOARD approach of Openmettings.)
>
> Any opinion?
> Thank you.
>
>
>
>
Re: Multimedia server is inaccessible
Posted by jox joe <jo...@gmail.com>.
>I guess OM, KMS and system logs need to be examined to understand what is
wrong
Yes, debugging can answer this question.
Maxim Solodovnik <so...@gmail.com> ezt írta (időpont: 2021. jan. 19.,
K, 15:32):
>
>
> On Tue, 19 Jan 2021 at 21:15, jox joe <jo...@gmail.com> wrote:
>
>> Thank you Maxim,
>>
>> >>connection between OM and KMS is broken
>>
>> then this is the actual question:
>> Why are OM and KMS disconnected?
>>
>
> I have no idea
> KMS at demo works without disconnections for weeks
>
> The system is Ubuntu 18.04
> KMS 6.15
> OpenJava 11
>
> I guess OM, KMS and system logs need to be examined to understand what is
> wrong
>
>
>> I can use another, similar platform (video+audio communication) in the
>> "same"
>> environment for hours without disconnection.
>>
>
> similar platform? maybe it has fewer bugs? :)))
> Or maybe environment isn't the same
>
>
>>
>> Jox
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Maxim Solodovnik <so...@gmail.com> ezt írta (időpont: 2021. jan.
>> 19., K, 11:13):
>>
>>>
>>>
>>> On Mon, 18 Jan 2021 at 00:38, jox joe <jo...@gmail.com> wrote:
>>>
>>>> Hello everybody,
>>>>
>>>> "Multimedia server is inaccessible"
>>>> This message sometimes appears.
>>>> It would be good to know what it is caused by.
>>>> 1. By the Openmeetings server?
>>>> 2. By the Kurento mediaserver?
>>>> 3. By the browser(s)?
>>>> 4. By something else?
>>>>
>>>
>>> The message caused by the fact connection between OM and KMS is broken
>>> (initially broken or lost after some time)
>>> OM tries to auto-reconnect, so if KMS was re-started network issues are
>>> fixed the connection will be re-created
>>>
>>>
>>>> Debugging a communication module is time consuming
>>>> and cooperation is needed to determin what is the problem
>>>> in the given environment. The test servers do not help too much
>>>> in these cases.
>>>>
>>>> I tried the previous Openmeetings version (4.x/Flash and Red5 server)
>>>> and it was very stable.
>>>>
>>>> (I like the WHITEBOARD approach of Openmettings.)
>>>>
>>>> Any opinion?
>>>> Thank you.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> Best regards,
>>> Maxim
>>>
>>
>
> --
> Best regards,
> Maxim
>
Re: Multimedia server is inaccessible
Posted by Maxim Solodovnik <so...@gmail.com>.
On Tue, 19 Jan 2021 at 21:15, jox joe <jo...@gmail.com> wrote:
> Thank you Maxim,
>
> >>connection between OM and KMS is broken
>
> then this is the actual question:
> Why are OM and KMS disconnected?
>
I have no idea
KMS at demo works without disconnections for weeks
The system is Ubuntu 18.04
KMS 6.15
OpenJava 11
I guess OM, KMS and system logs need to be examined to understand what is
wrong
> I can use another, similar platform (video+audio communication) in the
> "same"
> environment for hours without disconnection.
>
similar platform? maybe it has fewer bugs? :)))
Or maybe environment isn't the same
>
> Jox
>
>
>
>
>
>
>
>
>
>
> Maxim Solodovnik <so...@gmail.com> ezt írta (időpont: 2021. jan.
> 19., K, 11:13):
>
>>
>>
>> On Mon, 18 Jan 2021 at 00:38, jox joe <jo...@gmail.com> wrote:
>>
>>> Hello everybody,
>>>
>>> "Multimedia server is inaccessible"
>>> This message sometimes appears.
>>> It would be good to know what it is caused by.
>>> 1. By the Openmeetings server?
>>> 2. By the Kurento mediaserver?
>>> 3. By the browser(s)?
>>> 4. By something else?
>>>
>>
>> The message caused by the fact connection between OM and KMS is broken
>> (initially broken or lost after some time)
>> OM tries to auto-reconnect, so if KMS was re-started network issues are
>> fixed the connection will be re-created
>>
>>
>>> Debugging a communication module is time consuming
>>> and cooperation is needed to determin what is the problem
>>> in the given environment. The test servers do not help too much
>>> in these cases.
>>>
>>> I tried the previous Openmeetings version (4.x/Flash and Red5 server)
>>> and it was very stable.
>>>
>>> (I like the WHITEBOARD approach of Openmettings.)
>>>
>>> Any opinion?
>>> Thank you.
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> Best regards,
>> Maxim
>>
>
--
Best regards,
Maxim
Re: Multimedia server is inaccessible
Posted by jox joe <jo...@gmail.com>.
Thank you Maxim,
>>connection between OM and KMS is broken
then this is the actual question:
Why are OM and KMS disconnected?
I can use another, similar platform (video+audio communication) in the
"same"
environment for hours without disconnection.
Jox
Maxim Solodovnik <so...@gmail.com> ezt írta (időpont: 2021. jan. 19.,
K, 11:13):
>
>
> On Mon, 18 Jan 2021 at 00:38, jox joe <jo...@gmail.com> wrote:
>
>> Hello everybody,
>>
>> "Multimedia server is inaccessible"
>> This message sometimes appears.
>> It would be good to know what it is caused by.
>> 1. By the Openmeetings server?
>> 2. By the Kurento mediaserver?
>> 3. By the browser(s)?
>> 4. By something else?
>>
>
> The message caused by the fact connection between OM and KMS is broken
> (initially broken or lost after some time)
> OM tries to auto-reconnect, so if KMS was re-started network issues are
> fixed the connection will be re-created
>
>
>> Debugging a communication module is time consuming
>> and cooperation is needed to determin what is the problem
>> in the given environment. The test servers do not help too much
>> in these cases.
>>
>> I tried the previous Openmeetings version (4.x/Flash and Red5 server)
>> and it was very stable.
>>
>> (I like the WHITEBOARD approach of Openmettings.)
>>
>> Any opinion?
>> Thank you.
>>
>>
>>
>>
>>
>
> --
> Best regards,
> Maxim
>
Re: Multimedia server is inaccessible
Posted by Maxim Solodovnik <so...@gmail.com>.
On Mon, 18 Jan 2021 at 00:38, jox joe <jo...@gmail.com> wrote:
> Hello everybody,
>
> "Multimedia server is inaccessible"
> This message sometimes appears.
> It would be good to know what it is caused by.
> 1. By the Openmeetings server?
> 2. By the Kurento mediaserver?
> 3. By the browser(s)?
> 4. By something else?
>
The message caused by the fact connection between OM and KMS is broken
(initially broken or lost after some time)
OM tries to auto-reconnect, so if KMS was re-started network issues are
fixed the connection will be re-created
> Debugging a communication module is time consuming
> and cooperation is needed to determin what is the problem
> in the given environment. The test servers do not help too much
> in these cases.
>
> I tried the previous Openmeetings version (4.x/Flash and Red5 server)
> and it was very stable.
>
> (I like the WHITEBOARD approach of Openmettings.)
>
> Any opinion?
> Thank you.
>
>
>
>
>
--
Best regards,
Maxim