Re: Multimedia server (Kurento?)

2019-08-06 Thread Maxim Solodovnik
M1 == milestone 1 == first step to production ready version

To get rid of warnings you need latest version (M2 ATM)

To be able to broadcast audio/video to the room you have to install and
configure Kurento-media-server and (most probably) stun/turn server

On Tue, Aug 6, 2019, 19:26 Xavier M  wrote:

> Hello all,
>
> Yesterday, I secured the access to OpenMeetings (sorry again for the many
> mails). I do not know whether it is bound with the problem exposed here.
>
> I'm still using OM 5.0.0-M1 (even if I do not know what -M1 refers to).
> I got following errors when I connect through the proxy (
> https://openmeetings.domain.eu/openmeetings) and when I connect
> "directly" (https://:5443/openmeetings).
>
>  * When I'm doing "auto-test", Firefox console indicates on
> webcam-activation:
> 
> *onaddstream is deprecated! Use peerConnection.ontrack instead.*
> *constraints: {"offerToReceiveAudio":false,"offerToReceiveVideo":false}*
> 
>
>  * When I'm doing "auto-test", Firefox console indicates on
> microphone-activation (terms in french mean the same as for previous
> points):
> 
> *RTCPeerConnection.getLocalStreams/getRemoteStreams sont obsolètes.
> Veuillez utiliser RTCPeerConnection.getSenders/getReceivers à la place.*
> *Created SDP offer*
>
> *Local description set v=0 *
>
> *o=mozilla...THIS_IS_SDPARTA-68.0.1 5085935884128962176 0 IN IP4 0.0.0.0 *
> *(... many other lines ...)*
>
> *a=rtcp-fb:97 goog-remb *
>
> *a=rtcp-mux *
>
> *a=rtpmap:120 VP8/9 *
>
> *a=rtpmap:121 VP9/9 *
>
> *a=rtpmap:126 H264/9 *
>
> *a=rtpmap:97 H264/9 *
>
> *a=setup:actpass *
> *a=ssrc:24694 cname:{2f3bd7a1-c675-2e4f-86bf-940dc274dc1e}*
> 
>  * When I enter the public conference room and allow webcam and microphone
> to be activated, it works (I can see me and I see the green bar varying
> with the surrounding noise) but I've got many times the same messages on
> the right and in Firefox console:
> *Multimedia server is inaccessible*
>
> In the Firefox console, I can read similar lines as previously such as
>
>
> * _error https:// address>:5443/openmeetings/wicket/resource/org.apache.openmeetings.web.common.MainPanel/main-ver-23616A388817B675DD5E7E8072938083.js:62
> h https:// address>:5443/openmeetings/wicket/resource/org.apache.openmeetings.web.room.RoomPanel/room-ver-3C0177766D564BA883115AC2C4BC0735.js:38
> g https:// address>:5443/openmeetings/wicket/resource/org.apache.openmeetings.web.room.RoomPanel/room-ver-3C0177766D564BA883115AC2C4BC0735.js:38
> *
>  * When I enter the public interview room and try to activate webcam or
> microphone, I have the same message on the right. Firefow console indicates
> moreover (for french terms, please sea meaning above, at the very
> beginning):
> *RTCPeerConnection.getLocalStreams/getRemoteStreams sont obsolètes.
> Veuillez utiliser RTCPeerConnection.getSenders/getReceivers à la place.*
>
>  * When someone else enters the public conference room, the name appears
> on the left, we can interact on the whiteboard, but we can not see/hear
> each other.
>
> --> To make it short, the transfer of video/audio do not work in the cases
> with the webcam images.
> I really do not know if it still worked yesterday before I did the
> modifications that Maxim indicated me to secure tomcat.
>
> I found something interesting on the web basing upon the lines I wrote
> with bold policy, but do not know what I can do with it: has someone an
> idea? In the best case, I just have to update "something"...
> https://github.com/mattermost/mattermost-server/issues/7908
>
> Thank you all,
> Xavier
>


Multimedia server (Kurento?)

2019-08-06 Thread Xavier M
Hello all,

Yesterday, I secured the access to OpenMeetings (sorry again for the many 
mails). I do not know whether it is bound with the problem exposed here.

I'm still using OM 5.0.0-M1 (even if I do not know what -M1 refers to).
I got following errors when I connect through the proxy 
(https://openmeetings.domain.eu/openmeetings) and when I connect "directly" 
(https://:5443/openmeetings).

 * When I'm doing "auto-test", Firefox console indicates on webcam-activation:

onaddstream is deprecated! Use peerConnection.ontrack instead.
constraints: {"offerToReceiveAudio":false,"offerToReceiveVideo":false}


 * When I'm doing "auto-test", Firefox console indicates on 
microphone-activation (terms in french mean the same as for previous points):

RTCPeerConnection.getLocalStreams/getRemoteStreams sont obsolètes. Veuillez 
utiliser RTCPeerConnection.getSenders/getReceivers à la place.
Created SDP offer
Local description set v=0
o=mozilla...THIS_IS_SDPARTA-68.0.1 5085935884128962176 0 IN IP4 0.0.0.0
(... many other lines ...)
a=rtcp-fb:97 goog-remb
a=rtcp-mux
a=rtpmap:120 VP8/9
a=rtpmap:121 VP9/9
a=rtpmap:126 H264/9
a=rtpmap:97 H264/9
a=setup:actpass
a=ssrc:24694 cname:{2f3bd7a1-c675-2e4f-86bf-940dc274dc1e}

 * When I enter the public conference room and allow webcam and microphone to 
be activated, it works (I can see me and I see the green bar varying with the 
surrounding noise) but I've got many times the same messages on the right and 
in Firefox console:
Multimedia server is inaccessible

In the Firefox console, I can read similar lines as previously such as
_error https://:5443/openmeetings/wicket/resource/org.apache.openmeetings.web.common.MainPanel/main-ver-23616A388817B675DD5E7E8072938083.js:62
h https://:5443/openmeetings/wicket/resource/org.apache.openmeetings.web.room.RoomPanel/room-ver-3C0177766D564BA883115AC2C4BC0735.js:38
g https://:5443/openmeetings/wicket/resource/org.apache.openmeetings.web.room.RoomPanel/room-ver-3C0177766D564BA883115AC2C4BC0735.js:38

 * When I enter the public interview room and try to activate webcam or 
microphone, I have the same message on the right. Firefow console indicates 
moreover (for french terms, please sea meaning above, at the very beginning):
RTCPeerConnection.getLocalStreams/getRemoteStreams sont obsolètes. Veuillez 
utiliser RTCPeerConnection.getSenders/getReceivers à la place.

 * When someone else enters the public conference room, the name appears on the 
left, we can interact on the whiteboard, but we can not see/hear each other.

--> To make it short, the transfer of video/audio do not work in the cases with 
the webcam images.
I really do not know if it still worked yesterday before I did the 
modifications that Maxim indicated me to secure tomcat.

I found something interesting on the web basing upon the lines I wrote with 
bold policy, but do not know what I can do with it: has someone an idea? In the 
best case, I just have to update "something"...
https://github.com/mattermost/mattermost-server/issues/7908

Thank you all,
Xavier