You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Maxim Solodovnik <so...@gmail.com> on 2020/05/13 15:20:12 UTC

Re: 5.0.0-M4 camera and microphone connection lost

Hello jox,

your question is for user@ mailing list NOT for dev@
(dev@ is for OM development questions)

On Wed, 13 May 2020 at 21:51, jox joe <jo...@gmail.com> wrote:

> SPECIFICATION OF THE ENVIRONMENT:
>
> Main server:
> It is a VPS. Runs as a guest in a virtual environment.
> Ubuntu 18.04.4 LTS (GNU/Linux 4.19.0-6-amd64 x86_64)
>
> INSTALLED APPLICATIONS under the UBUNTU server:
>
> Installation OpenMeetings 5.0.0-M4 on Ubuntu 18.04 LTS.pdf
> Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on
> Ubuntu 18.04.pdf
> I used these two documents above and installed everything including
> the CoTURN server and the "letsencrypt.org" free SSL certificate.
> The SSL certificate was installed manually, I did nor used
> the automatic installation method.
> No firewall is activated on the Linux server.
>
> INSTALLED APPLICATIONS/CLIENT MACHINES:
> - operating systems: Windows 10
> - Google Chrome is up to date
>   (Version 81.0.4044.138 (Official Build) (64-bit))
> - proxy: no
>
> SPECIFICATION OF THE PERFORMED TESTING:
> Two user are present in the same room.
> One is sitting in Greece the other one in London.
> We used the following functions:
> - video/audio communication
> - screenshare
> Duration of the test: one hour
>
> DESCRIPTION OF THE PROBLEM:
>
> Audio/video connection suddenly stoped
> abou ten times within the one hour.
> The other user cannot hear/see me or the other way.
> Connection can be reestablished with EXIT and
> then entering the room again.
>

M4 contains code (https://issues.apache.org/jira/browse/OPENMEETINGS-2209)
to restore connection
in case it was broken for whatever reason
should be investigated and fixed


>
> If I do same testing using two machines on the same
> local network running the same client, the video/audio
> communication is very stable.
>

Is it also Win10+Chrome clients?


>
> DEBUG INFORMATION:
> CoTURN server log:
> 288154: session 003000000000000117: realm <kurento.org> user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: handle_udp_packet: New UDP endpoint: local addr 89.120.30.78:3478,
> remote addr 189.105.252.44:14294
> 288154: session 003000000000000118: realm <kurento.org> user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: handle_udp_packet: New UDP endpoint: local addr  89.120.30.78:3478
> , remote addr 183.206.174.85:14295
> 288154: session 001000000000000118: realm <kurento.org> user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: handle_udp_packet: New UDP endpoint: local addr 95.140.40.95:3478,
> remote addr  189.105.252.44:14294
> 288154: session 003000000000000119: realm <kurento.org> user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: session 003000000000000117: realm <kurento.org> user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: session 003000000000000118: realm <kurento.org> user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: session 001000000000000118: realm <kurento.org> user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: session 003000000000000119: realm <kurento.org> user <>: incoming
> packet message processed, error 401: Unauthorized
>

I believe you need to check your coturn+OM config
i.e. /etc/turnserver.conf and applicationContext.xml


>
> Full of "error 401: Unauthorized" and video/audio unstable.
> If I use the client machines on the local network, no "error 401:
> Unauthorized" message
> and  video/audio stable.
>
> QUESTIONS:
> 1.
> The turn server log has no date stamp so I cant determine the action in the
> application.
> Should I modify the COTURN server source and recompile it?
>

I usually use `tail -f ` and the list of the logs it can help to see the
correct order
BUT in this case your browser talks to TURN server not OM so I doubt logs
can help


>
> 2.
> Is "error 401: Unauthorized" a legal message?
> Where can I find info about this?
>

As I wrote earlier I would check coturn config and the values used in
$OM/**/applicationContext.xml


>
> 3.
> Has anyone the same problem?
>

Not me :(


>
> 4.
> Should I set anything in the Chrome client
> if I want to use it with the CoTurn server?
>

No


>
> 5.
> I have several hours testing capacaty
> every week.
> Could you give me any hint how to proceed?
> I want want to find out why is this version so
> unstable. It is practically unusable.
>

Hopefully have provide you with some info :)


>
> By the way, I like OM.
>
> Thank you.
> jox
>
> (REF: 2020-05-13-13-43-26)
>
>
>
>
> Search Results
> Web result with site links
>


-- 
Best regards,
Maxim