Re: Issues in iptables configuration

[Rohit Dhamal]

 Dear guys, 
the problem of the port settings has got solved now. you need to keep the 
internal port in the line 5 blank. I tried many things and now after leaving it 
blank, it took the range automatically. thanks for your concern. 
A final problem remains is that OM can now be accessed only by  
https://yourdomain:8080/openmeetings. the proxy script given at stackoverflow, 
unfortunately does not work. It just lead to the signin page and nothing works 
there. I am not able to find out why this occurs. Any tutorial to solve this is 
highly welcome. It would also be better if we could get OM to work just on port 
443 alone. This is a big challenge but many similar solutions work on only a 
single port. 

Thanks and Regards, 
Rohit Dhamal.
On Thursday, 14 May, 2020, 10:04:47 am IST, Maxim Solodovnik 
 wrote:  
 
 I'm not very familiar with iptablesCan someone take a look?
line #5 looks suspicious to meit seems port-range is mapped to single port, 
this doesn't look right

Maybe you can start with no restrictionscheck if it works then add restrictions 
one-by-one, layer-by-layer
On Thu, 14 May 2020 at 04:25, Rohit Dhamal  wrote:

Dear All, 
Greetings, 
Being my first mail I feel both nervous and excited to interact with you guys. 
you guys are really awesome! 

I followed this for openmeetings 
https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools?preview=/27838216/152111934/Installation
 SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on Ubuntu 18.04.pdf 

the last rulesudo iptables -A INPUT -p udp --match multiport --dports 
49152:65535 -j ACCEPTthis was accepted
sudo iptables -A OUT -p udp --match multiport --dports 49152:65535 -j 
ACCEPTthis created a problem and output as below

# sudo iptables -A OUT -p udp --match multiport --dports 49152 -j ACCEPT
iptables: No chain/target/match by that name.
After this in iptables  -L, I cannot see the rules. 
I set the rules manually from the gufw. 
By the way I am using the live iso for OM 5m4. 

Moreover in my router I don't have internal port range support in my router. 
how do I accomplish this? 





This was the last instruction and I cannot wait to take openmeetings online!
Thanks and Regards,
Rohit Dhamal



-- 
Best regards,
Maxim  

Re: [DISCUSSION] next release

[seba.wag...@gmail.com]

Yeah that would be great if we have some users that can provide some
testing feedback with larger audiences.

We had some Universities in the past that could run some tests for us.

Thanks,
Seb

Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/




On Thu, 14 May 2020 at 14:59, Maxim Solodovnik  wrote:

> Hello Sebastian,
>
> On Thu, 14 May 2020 at 06:03, seba.wag...@gmail.com 
> wrote:
>
>> How are we doing in terms of Load Testing ?
>>
>
> Well I see no way to test heavy load at one machine
> Here are some number for KMS: https://testrtc.com/sessions-kurento-server/
>
> I had plans to re-implement external video functionality
> this might allow as to test room load with multiple streams
> but I believe this is not real-world scenario
>
> my laptop can handle ~20-30 simultaneous tabs, not 100 
>
>
>>
>> I don't mind so much feature completeness or 100% replicating what was in
>> 4.x.
>>
>> But I am mindful of the backlash in terms of being production ready if we
>> have issues in scaling up to 100+ concurrent users.
>>
>> Do we have any positive results/feedback/scenarios on that ?
>> Can we do anything to de-risk this and confirm we are ready for
>> production ?
>>
>> Are there any users on this list that can help us and that can run a low
>> risk scenario with 100+ users in a presentation conference room ?
>>
>
> Peter has published numbers for 4.x
> Maybe he can share numbers for 5.0 if it will be stable enough :)
>
>
>>
>> Thanks,
>> Seb
>>
>> Sebastian Wagner
>> Director Arrakeen Solutions
>> http://arrakeen-solutions.co.nz/
>>
>> 
>> 
>>
>>
>> On Thu, 14 May 2020 at 08:55, K. Kamhamea 
>> wrote:
>>
>>> Please can someone explain?
>>> I understand that SIP has something to do with IP telephones, but what
>>> does that mean to OM functionality?
>>> Best K.
>>>
>>> Am Mi., 13. Mai 2020 um 18:15 Uhr schrieb R. Scholz <
>>> rene.sch...@abakus-edv-systems.de>:
>>>
 Hello Maxim,

 at this moment two things are important for me:
 - calling a room directly with room-name
 - SIP-support

 Best regards,

 René


 Am 13.05.2020 um 17:59 schrieb Maxim Solodovnik:


 On Wed, 13 May 2020 at 22:55, Rohrbach, Gerald <
 g.rohrb...@funkegruppe.de> wrote:

> Maxim,
>
>
>
> cool, you are coming forward…
>
>
>
>
>
> SIP Next Release means 6.0.0?
>

 This need to be discussed separately, but I would say 5.1.0 :)


>
>
>
>
> Gerald
>
>
>
> *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com]
> *Gesendet:* Mittwoch, 13. Mai 2020 17:47
> *An:* Openmeetings user-list 
> *Betreff:* [DISCUSSION] next release
>
>
>
> Hello All,
>
>
>
> Today I've noticed we already addressed 41 issue for M5
>
> I would like to perform next release as soon as current `master` will
> be even more stable
>
> And release it as "5.0.0" (NOT 5.0.0-M5)
>
>
>
> I plan to include
>
> https://issues.apache.org/jira/browse/OPENMEETINGS-2297
>
> https://issues.apache.org/jira/browse/OPENMEETINGS-2236
>
> https://issues.apache.org/jira/browse/OPENMEETINGS-2217
>
>
>
> to upcoming release as well
>
>
>
> there is no ETA yet due to
>
> 1) we still have reports regarding stability
>
> 2) we are waiting for Apache Wicket release
>
>
>
> please let me know if you see other blockers :)
>
>
>
> SIP most probably will go to the next release
>
>
>
> --
>
> Best regards,
> Maxim
>


 --
 Best regards,
 Maxim



>
> --
> Best regards,
> Maxim
>

Re: Issues in iptables configuration

[Maxim Solodovnik]

I'm not very familiar with iptables
Can someone take a look?

line #5 looks suspicious to me
it seems port-range is mapped to single port, this doesn't look right


Maybe you can start with no restrictions
check if it works then add restrictions one-by-one, layer-by-layer

On Thu, 14 May 2020 at 04:25, Rohit Dhamal  wrote:

> Dear All,
> Greetings,
> Being my first mail I feel both nervous and excited to interact with you
> guys. you guys are really awesome!
>
> I followed this for openmeetings
>
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools?preview=/27838216/152111934/Installation
> SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on Ubuntu 18.04.pdf
>
> the last rule
> sudo iptables -A INPUT -p udp --match multiport --dports 49152:65535 -j
> ACCEPT
> this was accepted
>
> sudo iptables -A OUT -p udp --match multiport --dports 49152:65535 -j
> ACCEPT
> this created a problem and output as below
>
> # sudo iptables -A OUT -p udp --match multiport --dports 49152 -j ACCEPT
> iptables: No chain/target/match by that name.
>
> After this in iptables  -L, I cannot see the rules.
> I set the rules manually from the gufw.
> By the way I am using the live iso for OM 5m4.
>
> Moreover in my router I don't have internal port range support in my
> router. how do I accomplish this?
>
> [image: Inline image]
>
>
>
> This was the last instruction and I cannot wait to take openmeetings
> online!
>
> Thanks and Regards,
>
> Rohit Dhamal
>


-- 
Best regards,
Maxim

Re: [DISCUSSION] next release

[Maxim Solodovnik]

Hello Sebastian,

On Thu, 14 May 2020 at 06:03, seba.wag...@gmail.com 
wrote:

> How are we doing in terms of Load Testing ?
>

Well I see no way to test heavy load at one machine
Here are some number for KMS: https://testrtc.com/sessions-kurento-server/

I had plans to re-implement external video functionality
this might allow as to test room load with multiple streams
but I believe this is not real-world scenario

my laptop can handle ~20-30 simultaneous tabs, not 100 


>
> I don't mind so much feature completeness or 100% replicating what was in
> 4.x.
>
> But I am mindful of the backlash in terms of being production ready if we
> have issues in scaling up to 100+ concurrent users.
>
> Do we have any positive results/feedback/scenarios on that ?
> Can we do anything to de-risk this and confirm we are ready for production
> ?
>
> Are there any users on this list that can help us and that can run a low
> risk scenario with 100+ users in a presentation conference room ?
>

Peter has published numbers for 4.x
Maybe he can share numbers for 5.0 if it will be stable enough :)


>
> Thanks,
> Seb
>
> Sebastian Wagner
> Director Arrakeen Solutions
> http://arrakeen-solutions.co.nz/
>
> 
> 
>
>
> On Thu, 14 May 2020 at 08:55, K. Kamhamea  wrote:
>
>> Please can someone explain?
>> I understand that SIP has something to do with IP telephones, but what
>> does that mean to OM functionality?
>> Best K.
>>
>> Am Mi., 13. Mai 2020 um 18:15 Uhr schrieb R. Scholz <
>> rene.sch...@abakus-edv-systems.de>:
>>
>>> Hello Maxim,
>>>
>>> at this moment two things are important for me:
>>> - calling a room directly with room-name
>>> - SIP-support
>>>
>>> Best regards,
>>>
>>> René
>>>
>>>
>>> Am 13.05.2020 um 17:59 schrieb Maxim Solodovnik:
>>>
>>>
>>> On Wed, 13 May 2020 at 22:55, Rohrbach, Gerald <
>>> g.rohrb...@funkegruppe.de> wrote:
>>>
 Maxim,



 cool, you are coming forward…





 SIP Next Release means 6.0.0?

>>>
>>> This need to be discussed separately, but I would say 5.1.0 :)
>>>
>>>




 Gerald



 *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com]
 *Gesendet:* Mittwoch, 13. Mai 2020 17:47
 *An:* Openmeetings user-list 
 *Betreff:* [DISCUSSION] next release



 Hello All,



 Today I've noticed we already addressed 41 issue for M5

 I would like to perform next release as soon as current `master` will
 be even more stable

 And release it as "5.0.0" (NOT 5.0.0-M5)



 I plan to include

 https://issues.apache.org/jira/browse/OPENMEETINGS-2297

 https://issues.apache.org/jira/browse/OPENMEETINGS-2236

 https://issues.apache.org/jira/browse/OPENMEETINGS-2217



 to upcoming release as well



 there is no ETA yet due to

 1) we still have reports regarding stability

 2) we are waiting for Apache Wicket release



 please let me know if you see other blockers :)



 SIP most probably will go to the next release



 --

 Best regards,
 Maxim

>>>
>>>
>>> --
>>> Best regards,
>>> Maxim
>>>
>>>
>>>

-- 
Best regards,
Maxim

Re: [DISCUSSION] next release

[Maxim Solodovnik]

Hello,

On Thu, 14 May 2020 at 03:55, K. Kamhamea  wrote:

> Please can someone explain?
> I understand that SIP has something to do with IP telephones, but what
> does that mean to OM functionality?
>

In OM 3.x-4.x there was VoIP bridge
Users were able to call do the room using real phone (of soft phone)


> Best K.
>
> Am Mi., 13. Mai 2020 um 18:15 Uhr schrieb R. Scholz <
> rene.sch...@abakus-edv-systems.de>:
>
>> Hello Maxim,
>>
>> at this moment two things are important for me:
>> - calling a room directly with room-name
>> - SIP-support
>>
>> Best regards,
>>
>> René
>>
>>
>> Am 13.05.2020 um 17:59 schrieb Maxim Solodovnik:
>>
>>
>> On Wed, 13 May 2020 at 22:55, Rohrbach, Gerald 
>> wrote:
>>
>>> Maxim,
>>>
>>>
>>>
>>> cool, you are coming forward…
>>>
>>>
>>>
>>>
>>>
>>> SIP Next Release means 6.0.0?
>>>
>>
>> This need to be discussed separately, but I would say 5.1.0 :)
>>
>>
>>>
>>>
>>>
>>>
>>> Gerald
>>>
>>>
>>>
>>> *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com]
>>> *Gesendet:* Mittwoch, 13. Mai 2020 17:47
>>> *An:* Openmeetings user-list 
>>> *Betreff:* [DISCUSSION] next release
>>>
>>>
>>>
>>> Hello All,
>>>
>>>
>>>
>>> Today I've noticed we already addressed 41 issue for M5
>>>
>>> I would like to perform next release as soon as current `master` will be
>>> even more stable
>>>
>>> And release it as "5.0.0" (NOT 5.0.0-M5)
>>>
>>>
>>>
>>> I plan to include
>>>
>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2297
>>>
>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2236
>>>
>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2217
>>>
>>>
>>>
>>> to upcoming release as well
>>>
>>>
>>>
>>> there is no ETA yet due to
>>>
>>> 1) we still have reports regarding stability
>>>
>>> 2) we are waiting for Apache Wicket release
>>>
>>>
>>>
>>> please let me know if you see other blockers :)
>>>
>>>
>>>
>>> SIP most probably will go to the next release
>>>
>>>
>>>
>>> --
>>>
>>> Best regards,
>>> Maxim
>>>
>>
>>
>> --
>> Best regards,
>> Maxim
>>
>>
>>

-- 
Best regards,
Maxim

Re: [DISCUSSION] next release

[seba.wag...@gmail.com]

How are we doing in terms of Load Testing ?

I don't mind so much feature completeness or 100% replicating what was in
4.x.

But I am mindful of the backlash in terms of being production ready if we
have issues in scaling up to 100+ concurrent users.

Do we have any positive results/feedback/scenarios on that ?
Can we do anything to de-risk this and confirm we are ready for production ?

Are there any users on this list that can help us and that can run a low
risk scenario with 100+ users in a presentation conference room ?

Thanks,
Seb

Sebastian Wagner
Director Arrakeen Solutions
http://arrakeen-solutions.co.nz/




On Thu, 14 May 2020 at 08:55, K. Kamhamea  wrote:

> Please can someone explain?
> I understand that SIP has something to do with IP telephones, but what
> does that mean to OM functionality?
> Best K.
>
> Am Mi., 13. Mai 2020 um 18:15 Uhr schrieb R. Scholz <
> rene.sch...@abakus-edv-systems.de>:
>
>> Hello Maxim,
>>
>> at this moment two things are important for me:
>> - calling a room directly with room-name
>> - SIP-support
>>
>> Best regards,
>>
>> René
>>
>>
>> Am 13.05.2020 um 17:59 schrieb Maxim Solodovnik:
>>
>>
>> On Wed, 13 May 2020 at 22:55, Rohrbach, Gerald 
>> wrote:
>>
>>> Maxim,
>>>
>>>
>>>
>>> cool, you are coming forward…
>>>
>>>
>>>
>>>
>>>
>>> SIP Next Release means 6.0.0?
>>>
>>
>> This need to be discussed separately, but I would say 5.1.0 :)
>>
>>
>>>
>>>
>>>
>>>
>>> Gerald
>>>
>>>
>>>
>>> *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com]
>>> *Gesendet:* Mittwoch, 13. Mai 2020 17:47
>>> *An:* Openmeetings user-list 
>>> *Betreff:* [DISCUSSION] next release
>>>
>>>
>>>
>>> Hello All,
>>>
>>>
>>>
>>> Today I've noticed we already addressed 41 issue for M5
>>>
>>> I would like to perform next release as soon as current `master` will be
>>> even more stable
>>>
>>> And release it as "5.0.0" (NOT 5.0.0-M5)
>>>
>>>
>>>
>>> I plan to include
>>>
>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2297
>>>
>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2236
>>>
>>> https://issues.apache.org/jira/browse/OPENMEETINGS-2217
>>>
>>>
>>>
>>> to upcoming release as well
>>>
>>>
>>>
>>> there is no ETA yet due to
>>>
>>> 1) we still have reports regarding stability
>>>
>>> 2) we are waiting for Apache Wicket release
>>>
>>>
>>>
>>> please let me know if you see other blockers :)
>>>
>>>
>>>
>>> SIP most probably will go to the next release
>>>
>>>
>>>
>>> --
>>>
>>> Best regards,
>>> Maxim
>>>
>>
>>
>> --
>> Best regards,
>> Maxim
>>
>>
>>

Issues in iptables configuration

[Rohit Dhamal]

Dear All, 
Greetings, 
Being my first mail I feel both nervous and excited to interact with you guys. 
you guys are really awesome! 

I followed this for openmeetings 
https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools?preview=/27838216/152111934/Installation
 SSL certificates and Coturn for OpenMeetings 5.0.0-M4 on Ubuntu 18.04.pdf 

the last rulesudo iptables -A INPUT -p udp --match multiport --dports 
49152:65535 -j ACCEPTthis was accepted
sudo iptables -A OUT -p udp --match multiport --dports 49152:65535 -j 
ACCEPTthis created a problem and output as below

# sudo iptables -A OUT -p udp --match multiport --dports 49152 -j ACCEPT
iptables: No chain/target/match by that name.
After this in iptables  -L, I cannot see the rules. 
I set the rules manually from the gufw. 
By the way I am using the live iso for OM 5m4. 

Moreover in my router I don't have internal port range support in my router. 
how do I accomplish this? 





This was the last instruction and I cannot wait to take openmeetings online!
Thanks and Regards,
Rohit Dhamal

Re: [DISCUSSION] next release

[K. Kamhamea]

Please can someone explain?
I understand that SIP has something to do with IP telephones, but what does
that mean to OM functionality?
Best K.

Am Mi., 13. Mai 2020 um 18:15 Uhr schrieb R. Scholz <
rene.sch...@abakus-edv-systems.de>:

> Hello Maxim,
>
> at this moment two things are important for me:
> - calling a room directly with room-name
> - SIP-support
>
> Best regards,
>
> René
>
>
> Am 13.05.2020 um 17:59 schrieb Maxim Solodovnik:
>
>
> On Wed, 13 May 2020 at 22:55, Rohrbach, Gerald 
> wrote:
>
>> Maxim,
>>
>>
>>
>> cool, you are coming forward…
>>
>>
>>
>>
>>
>> SIP Next Release means 6.0.0?
>>
>
> This need to be discussed separately, but I would say 5.1.0 :)
>
>
>>
>>
>>
>>
>> Gerald
>>
>>
>>
>> *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com]
>> *Gesendet:* Mittwoch, 13. Mai 2020 17:47
>> *An:* Openmeetings user-list 
>> *Betreff:* [DISCUSSION] next release
>>
>>
>>
>> Hello All,
>>
>>
>>
>> Today I've noticed we already addressed 41 issue for M5
>>
>> I would like to perform next release as soon as current `master` will be
>> even more stable
>>
>> And release it as "5.0.0" (NOT 5.0.0-M5)
>>
>>
>>
>> I plan to include
>>
>> https://issues.apache.org/jira/browse/OPENMEETINGS-2297
>>
>> https://issues.apache.org/jira/browse/OPENMEETINGS-2236
>>
>> https://issues.apache.org/jira/browse/OPENMEETINGS-2217
>>
>>
>>
>> to upcoming release as well
>>
>>
>>
>> there is no ETA yet due to
>>
>> 1) we still have reports regarding stability
>>
>> 2) we are waiting for Apache Wicket release
>>
>>
>>
>> please let me know if you see other blockers :)
>>
>>
>>
>> SIP most probably will go to the next release
>>
>>
>>
>> --
>>
>> Best regards,
>> Maxim
>>
>
>
> --
> Best regards,
> Maxim
>
>
>

Re: [DISCUSSION] next release

[R. Scholz]

Hello Maxim,

at this moment two things are important for me:
- calling a room directly with room-name
- SIP-support

Best regards,

René


Am 13.05.2020 um 17:59 schrieb Maxim Solodovnik:


On Wed, 13 May 2020 at 22:55, Rohrbach, Gerald 
mailto:g.rohrb...@funkegruppe.de>> wrote:


Maxim,

cool, you are coming forward…

SIP Next Release means 6.0.0?


This need to be discussed separately, but I would say 5.1.0 :)

Gerald

*Von:*Maxim Solodovnik [mailto:solomax...@gmail.com
]
*Gesendet:* Mittwoch, 13. Mai 2020 17:47
*An:* Openmeetings user-list mailto:user@openmeetings.apache.org>>
*Betreff:* [DISCUSSION] next release

Hello All,

Today I've noticed we already addressed 41 issue for M5

I would like to perform next release as soon as current `master`
will be even more stable

And release it as "5.0.0" (NOT 5.0.0-M5)

I plan to include

https://issues.apache.org/jira/browse/OPENMEETINGS-2297

https://issues.apache.org/jira/browse/OPENMEETINGS-2236

https://issues.apache.org/jira/browse/OPENMEETINGS-2217

to upcoming release as well

there is no ETA yet due to

1) we still have reports regarding stability

2) we are waiting for Apache Wicket release

please let me know if you see other blockers :)

SIP most probably will go to the next release

-- 


Best regards,
Maxim



--
Best regards,
Maxim

Re: [DISCUSSION] next release

[Maxim Solodovnik]

On Wed, 13 May 2020 at 22:55, Rohrbach, Gerald 
wrote:

> Maxim,
>
>
>
> cool, you are coming forward…
>
>
>
>
>
> SIP Next Release means 6.0.0?
>

This need to be discussed separately, but I would say 5.1.0 :)


>
>
>
>
> Gerald
>
>
>
> *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com]
> *Gesendet:* Mittwoch, 13. Mai 2020 17:47
> *An:* Openmeetings user-list 
> *Betreff:* [DISCUSSION] next release
>
>
>
> Hello All,
>
>
>
> Today I've noticed we already addressed 41 issue for M5
>
> I would like to perform next release as soon as current `master` will be
> even more stable
>
> And release it as "5.0.0" (NOT 5.0.0-M5)
>
>
>
> I plan to include
>
> https://issues.apache.org/jira/browse/OPENMEETINGS-2297
>
> https://issues.apache.org/jira/browse/OPENMEETINGS-2236
>
> https://issues.apache.org/jira/browse/OPENMEETINGS-2217
>
>
>
> to upcoming release as well
>
>
>
> there is no ETA yet due to
>
> 1) we still have reports regarding stability
>
> 2) we are waiting for Apache Wicket release
>
>
>
> please let me know if you see other blockers :)
>
>
>
> SIP most probably will go to the next release
>
>
>
> --
>
> Best regards,
> Maxim
>


-- 
Best regards,
Maxim

AW: [DISCUSSION] next release

[Rohrbach, Gerald]

Maxim,

cool, you are coming forward…


SIP Next Release means 6.0.0?


Gerald

Von: Maxim Solodovnik [mailto:solomax...@gmail.com]
Gesendet: Mittwoch, 13. Mai 2020 17:47
An: Openmeetings user-list 
Betreff: [DISCUSSION] next release

Hello All,

Today I've noticed we already addressed 41 issue for M5
I would like to perform next release as soon as current `master` will be even 
more stable
And release it as "5.0.0" (NOT 5.0.0-M5)

I plan to include
https://issues.apache.org/jira/browse/OPENMEETINGS-2297
https://issues.apache.org/jira/browse/OPENMEETINGS-2236
https://issues.apache.org/jira/browse/OPENMEETINGS-2217

to upcoming release as well

there is no ETA yet due to
1) we still have reports regarding stability
2) we are waiting for Apache Wicket release

please let me know if you see other blockers :)

SIP most probably will go to the next release

--
Best regards,
Maxim

[DISCUSSION] next release

[Maxim Solodovnik]

Hello All,

Today I've noticed we already addressed 41 issue for M5
I would like to perform next release as soon as current `master` will be
even more stable
And release it as "5.0.0" (NOT 5.0.0-M5)

I plan to include
https://issues.apache.org/jira/browse/OPENMEETINGS-2297
https://issues.apache.org/jira/browse/OPENMEETINGS-2236
https://issues.apache.org/jira/browse/OPENMEETINGS-2217

to upcoming release as well

there is no ETA yet due to
1) we still have reports regarding stability
2) we are waiting for Apache Wicket release

please let me know if you see other blockers :)

SIP most probably will go to the next release

-- 
Best regards,
Maxim

Re: 5.0.0-M4 camera and microphone connection lost

[Maxim Solodovnik]

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  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 003117: realm  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 003118: realm  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 001118: realm  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 003119: realm  user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: session 003117: realm  user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: session 003118: realm  user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: session 001118: realm  user <>: incoming
> packet message processed, error 401: Unauthorized
> 288154: session 003119: realm  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

Re: OM 505 Problem reconnect Stream

[Maxim Solodovnik]

Hello Peter,

On Wed, 13 May 2020 at 20:30, Peter Dähn  wrote:

> Hi,
>
> I still have a problem to get sable connection for participants.
>
> For some of them it never works and for some it work a while... for some
> seems to help tu turn on own cam/mic to hear others!?!?... I am really
> helpless... :-(
>
> catalalina out shows this kind of messages if connection fails.
>
> *DEBUG 05-13 14:31:30.961 o.a.o.c.r.StreamProcessor:91 [io-5082-exec-19] -
> Incoming message from user with ID '14421':
> {"type":"kurento","id":"broadcastStarted","uid":"d6805f4c-8fc6-4a7a-9cf5-dd2bd85d1f65","sdpOffer":"v=0\r\no=mozilla...THIS_IS_SDPARTA-71.0
> 7880734367584313215 0 IN IP4 0.0.0.0\r\ns=-\r\nt=0
> 0\r\na=sendrecv\r\na=fingerprint:sha-256
> 59:FD:77:17:E5:21:C7:B5:09:5D:D1:AB:58:4F:26:CD:9A:04:84:24:03:A8:26:E4:C1:43:3E:5C:7B:72:13:5E\r\na=group:BUNDLE
> 0\r\na=ice-options:trickle\r\na=msid-semantic:WMS *\r\nm=audio 9
> UDP/TLS/RTP/SAVPF 109 9 0 8 101\r\nc=IN IP4
> 0.0.0.0\r\na=sendrecv\r\na=extmap:1
> urn:ietf:params:rtp-hdrext:ssrc-audio-level\r\na=extmap:2/recvonly
> urn:ietf:params:rtp-hdrext:csrc-audio-level\r\na=extmap:3
> urn:ietf:params:rtp-hdrext:sdes:mid\r\na=fmtp:109
> maxplaybackrate=48000;stereo=1;useinbandfec=1\r\na=fmtp:101
> 0-15\r\na=ice-pwd:5447d03e80580f7c2893f37f9605b0c4\r\na=ice-ufrag:90a19ebb\r\na=mid:0\r\na=msid:{5ffed8b7-c193-42ad-823d-1783352f933d}
> {8a5bd209-28fa-43a4-aec7-3823895d2f5a}\r\na=rtcp-mux\r\na=rtpmap:109
> opus/48000/2\r\na=rtpmap:9 G722/8000/1\r\na=rtpmap:0
> PCMU/8000\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:101
> telephone-event/8000\r\na=setup:actpass\r\na=ssrc:3478667262
> cname:{d02f827b-578a-4abe-92d4-25274bde1262}\r\n"}*
> *ERROR 05-13 14:31:31.020 o.a.o.w.c.OmWebSocketPanel:144 [io-5082-exec-19]
> - Error while processing incoming message*
> *java.lang.NullPointerException: null*
>

This Exception is most probably is caused by client re-connection
i.e. client have started to re-connect and did it several times


>
> *at
> org.apache.openmeetings.core.remote.KStream.startBroadcast(KStream.java:88)*
> *at
> org.apache.openmeetings.core.remote.StreamProcessor.startBroadcast(StreamProcessor.java:212)*
> *at
> org.apache.openmeetings.core.remote.StreamProcessor.handleBroadcastStarted(StreamProcessor.java:187)*
> *at
> org.apache.openmeetings.core.remote.StreamProcessor.onMessage(StreamProcessor.java:110)*
> *at
> org.apache.openmeetings.core.remote.KurentoHandler.onMessage(KurentoHandler.java:233)*
> *at
> org.apache.openmeetings.core.remote.Wicket_Proxy_KurentoHandler$$FastClassByCGLIB$$756e116d.invoke()*
> *at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)*
> *at
> org.apache.wicket.proxy.LazyInitProxyFactory$AbstractCGLibInterceptor.intercept(LazyInitProxyFactory.java:364)*
> *at
> org.apache.openmeetings.core.remote.Wicket_Proxy_KurentoHandler$$EnhancerByCGLIB$$98325b15.onMessage()*
> *at
> org.apache.openmeetings.web.common.OmWebSocketPanel$2.onMessage(OmWebSocketPanel.java:125)*
> *at
> org.apache.wicket.protocol.ws.api.WebSocketBehavior.onEvent(WebSocketBehavior.java:64)*
> *at
> org.apache.wicket.settings.FrameworkSettings.dispatchEvent(FrameworkSettings.java:147)*
> *at
> org.apache.wicket.ComponentEventSender.dispatchToComponent(ComponentEventSender.java:292)*
> *at
> org.apache.wicket.ComponentEventSender$ComponentEventVisitor.component(ComponentEventSender.java:329)*
> *at
> org.apache.wicket.ComponentEventSender$ComponentEventVisitor.component(ComponentEventSender.java:306)*
> *at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:144)*
> *at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162)*
> *at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:123)*
> *at org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:192)*
> *at
> org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:988)*
> *at
> org.apache.wicket.ComponentEventSender.breadth(ComponentEventSender.java:160)*
> *at
> org.apache.wicket.ComponentEventSender.send(ComponentEventSender.java:68)*
> *at org.apache.wicket.Component.send(Component.java:4418)*
> *at
> org.apache.wicket.protocol.ws.api.WebSocketMessageBroadcastHandler$1.run(WebSocketMessageBroadcastHandler.java:74)*
> *at
> org.apache.wicket.protocol.ws.WebSocketSettings$SameThreadExecutor.run(WebSocketSettings.java:393)*
> *at
> org.apache.wicket.protocol.ws.api.WebSocketMessageBroadcastHandler.respond(WebSocketMessageBroadcastHandler.java:97)*
> *at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:917)*
> *at
> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:63)*
> *at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)*
> *at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:254)*
> *at
> 

Re: help to run openmeetings on port 443

[Maxim Solodovnik]

Hello Rohit,

please do not write personal emails
subscribe to the user@ list
https://openmeetings.apache.org/mailing-lists.html and ask your questions
:))

Your question was discussed a lot recently can you use search (for ex. here
https://openmeetings.markmail.org/)

On Wed, 13 May 2020 at 17:23, Rohit Dhamal  wrote:

> Hi,
> How are you?
> I hope the corona scare is in control in your area. Be safe.
>
> I am trying to use openmeetings to conduct lectures for my students. I
> have a self hosted apache serveron my desktop. I have ssl certificates for
> my site. Unfortunately I cannot access openmeetings from outside on port
> 443.
> I have router port 80 and 443 forwarded to my respective ports. I am using
> your conf file from stachoverflow from here
>
> https://stackoverflow.com/questions/51721771/apache-openmeetings-4-0-4-csrf-attack-when-using-apache2-as-proxypass/51783235#51783235
>
> I can get it to work without audio and video on port 80 by  #ssl
> directives and certificates.
> Unfortunately with port 443 and ssl installed I cannot get it to work.
> Along with it there's another problem that I cannot get my webpage loaded
> as I could on apache listening to port 80 with a simple configuration.
>
> Also the file conf/jee-container.xml  is nowhere to be found.
>
> Why don't you make a tutorial to help teachers and other people like me to
> setup apache openmeetings properly and continue working from home.
> I appreciate you for the wonderful creation of openmeetings and would
> appreciate even more for a complete tutorial to setup openmeetings.
>
> In the meanwhile can I request you to provide me some settings to make
> openmeetings work on my server? I you want I can make it for you if you are
> busy refining optnmeetings. I would like to present it in your name a a
> token of gratitude.
>
> soak your facemasks in caustic (NaOH sodium Hydroxide) to kill viral
> particals and then gently wash with other clothes in washing machine to
> reuse it.
> Take care and Thanks.
>
> Regards,
> Rohit Dhamal.
> Medical Biotechnologist,
> Faculty Biology.
>
>

-- 
Best regards,
Maxim

Re: OM 4.0.10 h263 vs h264

[Maxim Solodovnik]

h264 - сильнее сжимает, поэтому нагрузка на проц выше, НО насколько я знаю
сервер сжиманием/расжиманием не занимается
так что это больше про клиента

сеть несколько разгрузится нагрузка на клиента вырастет

On Wed, 13 May 2020 at 14:01, Tester Debugger 
wrote:

>
> Здравствуйте,
> Подскажите пожалуйста, насколько целесообразно использование кодека H263
> по сравнению с H264 (опция настройки flash.video.codec) с точки зрения
> снижения нагрузки на процессоры сервера?
> Спасибо!



-- 
Best regards,
Maxim

OM 505 Problem reconnect Stream

[Peter Dähn]

Hi,

I still have a problem to get sable connection for participants.

For some of them it never works and for some it work a while... for some 
seems to help tu turn on own cam/mic to hear others!?!?... I am really 
helpless... :-(


catalalina out shows this kind of messages if connection fails.
/
//DEBUG 05-13 14:31:30.961 o.a.o.c.r.StreamProcessor:91 
[io-5082-exec-19] - Incoming message from user with ID '14421': 
{"type":"kurento","id":"broadcastStarted","uid":"d6805f4c-8fc6-4a7a-9cf5-dd2bd85d1f65","sdpOffer":"v=0\r\no=mozilla...THIS_IS_SDPARTA-71.0 
7880734367584313215 0 IN IP4 0.0.0.0\r\ns=-\r\nt=0 
0\r\na=sendrecv\r\na=fingerprint:sha-256 
59:FD:77:17:E5:21:C7:B5:09:5D:D1:AB:58:4F:26:CD:9A:04:84:24:03:A8:26:E4:C1:43:3E:5C:7B:72:13:5E\r\na=group:BUNDLE 
0\r\na=ice-options:trickle\r\na=msid-semantic:WMS *\r\nm=audio 9 
UDP/TLS/RTP/SAVPF 109 9 0 8 101\r\nc=IN IP4 
0.0.0.0\r\na=sendrecv\r\na=extmap:1 
urn:ietf:params:rtp-hdrext:ssrc-audio-level\r\na=extmap:2/recvonly 
urn:ietf:params:rtp-hdrext:csrc-audio-level\r\na=extmap:3 
urn:ietf:params:rtp-hdrext:sdes:mid\r\na=fmtp:109 
maxplaybackrate=48000;stereo=1;useinbandfec=1\r\na=fmtp:101 
0-15\r\na=ice-pwd:5447d03e80580f7c2893f37f9605b0c4\r\na=ice-ufrag:90a19ebb\r\na=mid:0\r\na=msid:{5ffed8b7-c193-42ad-823d-1783352f933d} 
{8a5bd209-28fa-43a4-aec7-3823895d2f5a}\r\na=rtcp-mux\r\na=rtpmap:109 
opus/48000/2\r\na=rtpmap:9 G722/8000/1\r\na=rtpmap:0 
PCMU/8000\r\na=rtpmap:8 PCMA/8000\r\na=rtpmap:101 
telephone-event/8000\r\na=setup:actpass\r\na=ssrc:3478667262 
cname:{d02f827b-578a-4abe-92d4-25274bde1262}\r\n"}//
//ERROR 05-13 14:31:31.020 o.a.o.w.c.OmWebSocketPanel:144 
[io-5082-exec-19] - Error while processing incoming message//

//java.lang.NullPointerException: null//
//    at 
org.apache.openmeetings.core.remote.KStream.startBroadcast(KStream.java:88)//
//    at 
org.apache.openmeetings.core.remote.StreamProcessor.startBroadcast(StreamProcessor.java:212)//
//    at 
org.apache.openmeetings.core.remote.StreamProcessor.handleBroadcastStarted(StreamProcessor.java:187)//
//    at 
org.apache.openmeetings.core.remote.StreamProcessor.onMessage(StreamProcessor.java:110)//
//    at 
org.apache.openmeetings.core.remote.KurentoHandler.onMessage(KurentoHandler.java:233)//
//    at 
org.apache.openmeetings.core.remote.Wicket_Proxy_KurentoHandler$$FastClassByCGLIB$$756e116d.invoke()//

//    at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)//
//    at 
org.apache.wicket.proxy.LazyInitProxyFactory$AbstractCGLibInterceptor.intercept(LazyInitProxyFactory.java:364)//
//    at 
org.apache.openmeetings.core.remote.Wicket_Proxy_KurentoHandler$$EnhancerByCGLIB$$98325b15.onMessage()//
//    at 
org.apache.openmeetings.web.common.OmWebSocketPanel$2.onMessage(OmWebSocketPanel.java:125)//
//    at 
org.apache.wicket.protocol.ws.api.WebSocketBehavior.onEvent(WebSocketBehavior.java:64)//
//    at 
org.apache.wicket.settings.FrameworkSettings.dispatchEvent(FrameworkSettings.java:147)//
//    at 
org.apache.wicket.ComponentEventSender.dispatchToComponent(ComponentEventSender.java:292)//
//    at 
org.apache.wicket.ComponentEventSender$ComponentEventVisitor.component(ComponentEventSender.java:329)//
//    at 
org.apache.wicket.ComponentEventSender$ComponentEventVisitor.component(ComponentEventSender.java:306)//
//    at 
org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:144)//
//    at 
org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:162)//
//    at 
org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:123)//
//    at 
org.apache.wicket.util.visit.Visits.visitChildren(Visits.java:192)//
//    at 
org.apache.wicket.MarkupContainer.visitChildren(MarkupContainer.java:988)//
//    at 
org.apache.wicket.ComponentEventSender.breadth(ComponentEventSender.java:160)//
//    at 
org.apache.wicket.ComponentEventSender.send(ComponentEventSender.java:68)//

//    at org.apache.wicket.Component.send(Component.java:4418)//
//    at 
org.apache.wicket.protocol.ws.api.WebSocketMessageBroadcastHandler$1.run(WebSocketMessageBroadcastHandler.java:74)//
//    at 
org.apache.wicket.protocol.ws.WebSocketSettings$SameThreadExecutor.run(WebSocketSettings.java:393)//
//    at 
org.apache.wicket.protocol.ws.api.WebSocketMessageBroadcastHandler.respond(WebSocketMessageBroadcastHandler.java:97)//
//    at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:917)//
//    at 
org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:63)//
//    at 
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)//
//    at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:254)//
//    at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:222)//
//    at 
org.apache.wicket.protocol.ws.api.AbstractWebSocketProcessor.broadcastMessage(AbstractWebSocketProcessor.java:272)//
//    at