[jitsi-dev] Media mixing and Jigasi limitations


#1

Dear list members,

I have few burning questions, regarding the Jigasi component of the Jitsi universe. During our tests we found some severe limitations and I need to confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method, calling towards Jigasi, there is a limitation of a one-user-per-second. Can’t join faster than that, no matter which room is being dialed.

2. Can’t join more than 30 participants to a single Jigasi server.

3. Only single Jigasi instance is supported by Jitisi.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t believe that those limitations are by design and the community is fine with that, so I assume it’s an issue with our understanding or testing method?

c. Which component does the media mixing, for participants joining through Jigasi, is it videobridge or Jigasi itself?

d. Is there a way of buying commercial support from Atlassian, for Jitsi ?

Thank’s in advance for your time.

Regards,
Dima Gutzeit.


#2

Hi,

Dear list members,

I have few burning questions, regarding the Jigasi component of the Jitsi
universe. During our tests we found some severe limitations and I need to
confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method, calling
towards Jigasi, there is a limitation of a one-user-per-second. Can’t join
faster than that, no matter which room is being dialed.

Not sure where this limitation comes from, do you see any exceptions
or anything in jigasi logs.

2. Can’t join more than 30 participants to a single Jigasi server.

It doesn't have any hardcoded limitations, it may be a bug or overload
issue, logs will reveal more what maybe the problem.

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
believe that those limitations are by design and the community is fine with
that, so I assume it’s an issue with our understanding or testing method?

There are no hardcoded limitations, there can be overload problems see
answer to c. or there can be bugs which needs to be investigated.

c. Which component does the media mixing, for participants joining
through Jigasi, is it videobridge or Jigasi itself?

Currently by default jigasi is doing the mixing, it decodes, mixes and
encodes media, which is a cpu intensive work and the limit for this is
the available resources on the server for that instance.

d. Is there a way of buying commercial support from Atlassian, for
Jitsi ?

This is not currently possible. I can just forward you to Yasen
Pramatarov (https://lindeas.com).

Regards
damencho

···

On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> wrote:

Thank’s in advance for your time.

Regards,

Dima Gutzeit.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

Hi damencho

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

How should I configure to have many Jigasi instances?

In my case, I would see below conflict error log if I try to get more than 1 instance Jigasi.

Thanks,

Sunny Mok

Feb 14, 2017 6:46:43 PM net.java.sip.communicator.util.Logger error
SEVERE: conflict, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: conflict
at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 1:42 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> wrote:

Dear list members,

I have few burning questions, regarding the Jigasi component of the Jitsi
universe. During our tests we found some severe limitations and I need to
confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method, calling
towards Jigasi, there is a limitation of a one-user-per-second. Can’t join
faster than that, no matter which room is being dialed.

Not sure where this limitation comes from, do you see any exceptions
or anything in jigasi logs.

2. Can’t join more than 30 participants to a single Jigasi server.

It doesn't have any hardcoded limitations, it may be a bug or overload
issue, logs will reveal more what maybe the problem.

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
believe that those limitations are by design and the community is fine with
that, so I assume it’s an issue with our understanding or testing method?

There are no hardcoded limitations, there can be overload problems see
answer to c. or there can be bugs which needs to be investigated.

c. Which component does the media mixing, for participants joining
through Jigasi, is it videobridge or Jigasi itself?

Currently by default jigasi is doing the mixing, it decodes, mixes and
encodes media, which is a cpu intensive work and the limit for this is
the available resources on the server for that instance.

d. Is there a way of buying commercial support from Atlassian, for
Jitsi ?

This is not currently possible. I can just forward you to Yasen
Pramatarov (https://lindeas.com).

Regards
damencho

Thank’s in advance for your time.

Regards,

Dima Gutzeit.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Hi,

the component is used only for outgoing calls, from jitsi-meet to the
sip side. For multiple jigasi instances to handle only sip incoming
you need:
JIGASI_OPTS="--nocomponent=true" in /etc/jitsi/jigasi/config
Also in /etc/jitsi/jigasi/sip-communicator.properties
org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN=https://your.server.com/http-bind?room={roomName}

This way you can have multiple jigasi with registered with multiple
sip endpoints where you can use it and balance between them with some
logic from the sip service/server you are using.

Regards
damencho

···

On Tue, Feb 14, 2017 at 12:48 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

How should I configure to have many Jigasi instances?

In my case, I would see below conflict error log if I try to get more than
1 instance Jigasi.

Thanks,

Sunny Mok

Feb 14, 2017 6:46:43 PM net.java.sip.communicator.util.Logger error
SEVERE: conflict, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: conflict
at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 1:42 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> wrote:

Dear list members,

I have few burning questions, regarding the Jigasi component of the Jitsi
universe. During our tests we found some severe limitations and I need to
confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method,
calling
towards Jigasi, there is a limitation of a one-user-per-second. Can’t join
faster than that, no matter which room is being dialed.

Not sure where this limitation comes from, do you see any exceptions
or anything in jigasi logs.

2. Can’t join more than 30 participants to a single Jigasi server.

It doesn't have any hardcoded limitations, it may be a bug or overload
issue, logs will reveal more what maybe the problem.

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
believe that those limitations are by design and the community is fine
with
that, so I assume it’s an issue with our understanding or testing method?

There are no hardcoded limitations, there can be overload problems see
answer to c. or there can be bugs which needs to be investigated.

c. Which component does the media mixing, for participants joining
through Jigasi, is it videobridge or Jigasi itself?

Currently by default jigasi is doing the mixing, it decodes, mixes and
encodes media, which is a cpu intensive work and the limit for this is
the available resources on the server for that instance.

d. Is there a way of buying commercial support from Atlassian, for
Jitsi ?

This is not currently possible. I can just forward you to Yasen
Pramatarov (https://lindeas.com).

Regards
damencho

Thank’s in advance for your time.

Regards,

Dima Gutzeit.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#5

Hi damencho,

Thanks for your help.

I tried, but prosody needed to add a new component config line for the 2nd Jigasi (i.e. callcontrol2.10.32.12.23).

Can the command option "--nocomponent=true" help to avoid that?

Thanks,

Sunny Mok

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 4:30 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

the component is used only for outgoing calls, from jitsi-meet to the
sip side. For multiple jigasi instances to handle only sip incoming
you need:
JIGASI_OPTS="--nocomponent=true" in /etc/jitsi/jigasi/config
Also in /etc/jitsi/jigasi/sip-communicator.properties
org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN=https://your.server.com/http-bind?room={roomName}

This way you can have multiple jigasi with registered with multiple
sip endpoints where you can use it and balance between them with some
logic from the sip service/server you are using.

Regards
damencho

On Tue, Feb 14, 2017 at 12:48 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

How should I configure to have many Jigasi instances?

In my case, I would see below conflict error log if I try to get more than
1 instance Jigasi.

Thanks,

Sunny Mok

Feb 14, 2017 6:46:43 PM net.java.sip.communicator.util.Logger error
SEVERE: conflict, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: conflict
at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 1:42 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> wrote:

Dear list members,

I have few burning questions, regarding the Jigasi component of the Jitsi
universe. During our tests we found some severe limitations and I need to
confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method,
calling
towards Jigasi, there is a limitation of a one-user-per-second. Can’t join
faster than that, no matter which room is being dialed.

Not sure where this limitation comes from, do you see any exceptions
or anything in jigasi logs.

2. Can’t join more than 30 participants to a single Jigasi server.

It doesn't have any hardcoded limitations, it may be a bug or overload
issue, logs will reveal more what maybe the problem.

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
believe that those limitations are by design and the community is fine
with
that, so I assume it’s an issue with our understanding or testing method?

There are no hardcoded limitations, there can be overload problems see
answer to c. or there can be bugs which needs to be investigated.

c. Which component does the media mixing, for participants joining
through Jigasi, is it videobridge or Jigasi itself?

Currently by default jigasi is doing the mixing, it decodes, mixes and
encodes media, which is a cpu intensive work and the limit for this is
the available resources on the server for that instance.

d. Is there a way of buying commercial support from Atlassian, for
Jitsi ?

This is not currently possible. I can just forward you to Yasen
Pramatarov (https://lindeas.com).

Regards
damencho

Thank’s in advance for your time.

Regards,

Dima Gutzeit.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#6

Hi damencho,

At least which version or which commit hash would Jigasi support this feature?

Thanks,

Sunny

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 4:30 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

the component is used only for outgoing calls, from jitsi-meet to the
sip side. For multiple jigasi instances to handle only sip incoming
you need:
JIGASI_OPTS="--nocomponent=true" in /etc/jitsi/jigasi/config
Also in /etc/jitsi/jigasi/sip-communicator.properties
org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN=https://your.server.com/http-bind?room={roomName}

This way you can have multiple jigasi with registered with multiple
sip endpoints where you can use it and balance between them with some
logic from the sip service/server you are using.

Regards
damencho

On Tue, Feb 14, 2017 at 12:48 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

How should I configure to have many Jigasi instances?

In my case, I would see below conflict error log if I try to get more than
1 instance Jigasi.

Thanks,

Sunny Mok

Feb 14, 2017 6:46:43 PM net.java.sip.communicator.util.Logger error
SEVERE: conflict, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: conflict
at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 1:42 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> wrote:

Dear list members,

I have few burning questions, regarding the Jigasi component of the Jitsi
universe. During our tests we found some severe limitations and I need to
confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method,
calling
towards Jigasi, there is a limitation of a one-user-per-second. Can’t join
faster than that, no matter which room is being dialed.

Not sure where this limitation comes from, do you see any exceptions
or anything in jigasi logs.

2. Can’t join more than 30 participants to a single Jigasi server.

It doesn't have any hardcoded limitations, it may be a bug or overload
issue, logs will reveal more what maybe the problem.

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
believe that those limitations are by design and the community is fine
with
that, so I assume it’s an issue with our understanding or testing method?

There are no hardcoded limitations, there can be overload problems see
answer to c. or there can be bugs which needs to be investigated.

c. Which component does the media mixing, for participants joining
through Jigasi, is it videobridge or Jigasi itself?

Currently by default jigasi is doing the mixing, it decodes, mixes and
encodes media, which is a cpu intensive work and the limit for this is
the available resources on the server for that instance.

d. Is there a way of buying commercial support from Atlassian, for
Jitsi ?

This is not currently possible. I can just forward you to Yasen
Pramatarov (https://lindeas.com).

Regards
damencho

Thank’s in advance for your time.

Regards,

Dima Gutzeit.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#7

Yes, this is an option which skips registering jigasi as component.

···

On Wed, Feb 15, 2017 at 10:14 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

Thanks for your help.

I tried, but prosody needed to add a new component config line for the 2nd
Jigasi (i.e. callcontrol2.10.32.12.23).

Can the command option "--nocomponent=true" help to avoid that?

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 4:30 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

the component is used only for outgoing calls, from jitsi-meet to the
sip side. For multiple jigasi instances to handle only sip incoming
you need:
JIGASI_OPTS="--nocomponent=true" in /etc/jitsi/jigasi/config
Also in /etc/jitsi/jigasi/sip-communicator.properties
org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN=https://your.server.com/http-bind?room={roomName}

This way you can have multiple jigasi with registered with multiple
sip endpoints where you can use it and balance between them with some
logic from the sip service/server you are using.

Regards
damencho

On Tue, Feb 14, 2017 at 12:48 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

How should I configure to have many Jigasi instances?

In my case, I would see below conflict error log if I try to get more
than
1 instance Jigasi.

Thanks,

Sunny Mok

Feb 14, 2017 6:46:43 PM net.java.sip.communicator.util.Logger error
SEVERE: conflict, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: conflict
at

org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at

org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at

org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at

java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at

java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 1:42 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> wrote:

Dear list members,

I have few burning questions, regarding the Jigasi component of the Jitsi
universe. During our tests we found some severe limitations and I need to
confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method,
calling
towards Jigasi, there is a limitation of a one-user-per-second. Can’t
join
faster than that, no matter which room is being dialed.

Not sure where this limitation comes from, do you see any exceptions
or anything in jigasi logs.

2. Can’t join more than 30 participants to a single Jigasi server.

It doesn't have any hardcoded limitations, it may be a bug or overload
issue, logs will reveal more what maybe the problem.

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
believe that those limitations are by design and the community is fine
with
that, so I assume it’s an issue with our understanding or testing method?

There are no hardcoded limitations, there can be overload problems see
answer to c. or there can be bugs which needs to be investigated.

c. Which component does the media mixing, for participants joining
through Jigasi, is it videobridge or Jigasi itself?

Currently by default jigasi is doing the mixing, it decodes, mixes and
encodes media, which is a cpu intensive work and the limit for this is
the available resources on the server for that instance.

d. Is there a way of buying commercial support from Atlassian, for
Jitsi ?

This is not currently possible. I can just forward you to Yasen
Pramatarov (https://lindeas.com).

Regards
damencho

Thank’s in advance for your time.

Regards,

Dima Gutzeit.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#8

Hi damencho,

does it need to upgrade jicofo and jvb as well?

Thanks,

Sunny

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok <apollomok@hotmail.com>
Sent: Friday, February 17, 2017 2:05 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi damencho,

At least which version or which commit hash would Jigasi support this feature?

Thanks,

Sunny

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 4:30 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

the component is used only for outgoing calls, from jitsi-meet to the
sip side. For multiple jigasi instances to handle only sip incoming
you need:
JIGASI_OPTS="--nocomponent=true" in /etc/jitsi/jigasi/config
Also in /etc/jitsi/jigasi/sip-communicator.properties
org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN=https://your.server.com/http-bind?room={roomName}

This way you can have multiple jigasi with registered with multiple
sip endpoints where you can use it and balance between them with some
logic from the sip service/server you are using.

Regards
damencho

On Tue, Feb 14, 2017 at 12:48 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

How should I configure to have many Jigasi instances?

In my case, I would see below conflict error log if I try to get more than
1 instance Jigasi.

Thanks,

Sunny Mok

Feb 14, 2017 6:46:43 PM net.java.sip.communicator.util.Logger error
SEVERE: conflict, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: conflict
at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 1:42 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> wrote:

Dear list members,

I have few burning questions, regarding the Jigasi component of the Jitsi
universe. During our tests we found some severe limitations and I need to
confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method,
calling
towards Jigasi, there is a limitation of a one-user-per-second. Can’t join
faster than that, no matter which room is being dialed.

Not sure where this limitation comes from, do you see any exceptions
or anything in jigasi logs.

2. Can’t join more than 30 participants to a single Jigasi server.

It doesn't have any hardcoded limitations, it may be a bug or overload
issue, logs will reveal more what maybe the problem.

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
believe that those limitations are by design and the community is fine
with
that, so I assume it’s an issue with our understanding or testing method?

There are no hardcoded limitations, there can be overload problems see
answer to c. or there can be bugs which needs to be investigated.

c. Which component does the media mixing, for participants joining
through Jigasi, is it videobridge or Jigasi itself?

Currently by default jigasi is doing the mixing, it decodes, mixes and
encodes media, which is a cpu intensive work and the limit for this is
the available resources on the server for that instance.

d. Is there a way of buying commercial support from Atlassian, for
Jitsi ?

This is not currently possible. I can just forward you to Yasen
Pramatarov (https://lindeas.com).

Regards
damencho

Thank’s in advance for your time.

Regards,

Dima Gutzeit.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#9

Hi damencho

Thanks for the prompt reply.

I just tried, but I got this host-unknown error, while actually the host and port (192.168.118.59) is accessible.

Do you have any idea?

SEVERE: host-unknown, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: host-unknown
at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Thanks,

Sunny Mok

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Wednesday, February 15, 2017 12:17 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Yes, this is an option which skips registering jigasi as component.

On Wed, Feb 15, 2017 at 10:14 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

Thanks for your help.

I tried, but prosody needed to add a new component config line for the 2nd
Jigasi (i.e. callcontrol2.10.32.12.23).

Can the command option "--nocomponent=true" help to avoid that?

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 4:30 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

the component is used only for outgoing calls, from jitsi-meet to the
sip side. For multiple jigasi instances to handle only sip incoming
you need:
JIGASI_OPTS="--nocomponent=true" in /etc/jitsi/jigasi/config
Also in /etc/jitsi/jigasi/sip-communicator.properties
org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN=https://your.server.com/http-bind?room={roomName}

This way you can have multiple jigasi with registered with multiple
sip endpoints where you can use it and balance between them with some
logic from the sip service/server you are using.

Regards
damencho

On Tue, Feb 14, 2017 at 12:48 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

How should I configure to have many Jigasi instances?

In my case, I would see below conflict error log if I try to get more
than
1 instance Jigasi.

Thanks,

Sunny Mok

Feb 14, 2017 6:46:43 PM net.java.sip.communicator.util.Logger error
SEVERE: conflict, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: conflict
at

org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at

org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at

org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at

java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at

java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 1:42 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> wrote:

Dear list members,

I have few burning questions, regarding the Jigasi component of the Jitsi
universe. During our tests we found some severe limitations and I need to
confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method,
calling
towards Jigasi, there is a limitation of a one-user-per-second. Can’t
join
faster than that, no matter which room is being dialed.

Not sure where this limitation comes from, do you see any exceptions
or anything in jigasi logs.

2. Can’t join more than 30 participants to a single Jigasi server.

It doesn't have any hardcoded limitations, it may be a bug or overload
issue, logs will reveal more what maybe the problem.

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
believe that those limitations are by design and the community is fine
with
that, so I assume it’s an issue with our understanding or testing method?

There are no hardcoded limitations, there can be overload problems see
answer to c. or there can be bugs which needs to be investigated.

c. Which component does the media mixing, for participants joining
through Jigasi, is it videobridge or Jigasi itself?

Currently by default jigasi is doing the mixing, it decodes, mixes and
encodes media, which is a cpu intensive work and the limit for this is
the available resources on the server for that instance.

d. Is there a way of buying commercial support from Atlassian, for
Jitsi ?

This is not currently possible. I can just forward you to Yasen
Pramatarov (https://lindeas.com).

Regards
damencho

Thank’s in advance for your time.

Regards,

Dima Gutzeit.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#10

Hi,

which version of jigasi are you using? This shows that no-component
option is not working. Where did you put the option?

Regards
damencho

···

On Wed, Feb 15, 2017 at 10:31 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho

Thanks for the prompt reply.

I just tried, but I got this host-unknown error, while actually the host and
port (192.168.118.59) is accessible.

Do you have any idea?

SEVERE: host-unknown, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: host-unknown
at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, February 15, 2017 12:17 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Yes, this is an option which skips registering jigasi as component.

On Wed, Feb 15, 2017 at 10:14 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

Thanks for your help.

I tried, but prosody needed to add a new component config line for the 2nd
Jigasi (i.e. callcontrol2.10.32.12.23).

Can the command option "--nocomponent=true" help to avoid that?

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 4:30 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

the component is used only for outgoing calls, from jitsi-meet to the
sip side. For multiple jigasi instances to handle only sip incoming
you need:
JIGASI_OPTS="--nocomponent=true" in /etc/jitsi/jigasi/config
Also in /etc/jitsi/jigasi/sip-communicator.properties

org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN=https://your.server.com/http-bind?room={roomName}

This way you can have multiple jigasi with registered with multiple
sip endpoints where you can use it and balance between them with some
logic from the sip service/server you are using.

Regards
damencho

On Tue, Feb 14, 2017 at 12:48 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

How should I configure to have many Jigasi instances?

In my case, I would see below conflict error log if I try to get more
than
1 instance Jigasi.

Thanks,

Sunny Mok

Feb 14, 2017 6:46:43 PM net.java.sip.communicator.util.Logger error
SEVERE: conflict, host:192.168.118.59, port:5347
org.xmpp.component.ComponentException: conflict
at

org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
at

org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
at

org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at

java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at

java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Tuesday, February 14, 2017 1:42 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> wrote:

Dear list members,

I have few burning questions, regarding the Jigasi component of the
Jitsi
universe. During our tests we found some severe limitations and I need
to
confirm those findings to make sure we find the correct solutions:

1. When we try to join people to the room, by call-in method,
calling
towards Jigasi, there is a limitation of a one-user-per-second. Can’t
join
faster than that, no matter which room is being dialed.

Not sure where this limitation comes from, do you see any exceptions
or anything in jigasi logs.

2. Can’t join more than 30 participants to a single Jigasi server.

It doesn't have any hardcoded limitations, it may be a bug or overload
issue, logs will reveal more what maybe the problem.

3. Only single Jigasi instance is supported by Jitisi.

For the call in functionality, you can configure multiple jigasis to
use bosh, then they will connect to conferences like regular
jitsi-meet client and you can have as many jigasi instances as you
like and make the balancing on the sip side.

Few questions:

a. Are those findings correct?

b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
believe that those limitations are by design and the community is fine
with
that, so I assume it’s an issue with our understanding or testing
method?

There are no hardcoded limitations, there can be overload problems see
answer to c. or there can be bugs which needs to be investigated.

c. Which component does the media mixing, for participants joining
through Jigasi, is it videobridge or Jigasi itself?

Currently by default jigasi is doing the mixing, it decodes, mixes and
encodes media, which is a cpu intensive work and the limit for this is
the available resources on the server for that instance.

d. Is there a way of buying commercial support from Atlassian, for
Jitsi ?

This is not currently possible. I can just forward you to Yasen
Pramatarov (https://lindeas.com).

Regards
damencho

Thank’s in advance for your time.

Regards,

Dima Gutzeit.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#11

Hi,

No upgrade is necessary,
Bosh support was added with:


But you can update to latest source or build 126.

Regards
damencho

···

On Feb 17, 2017 12:16, "Sunny Mok" <apollomok@hotmail.com> wrote:

Hi damencho,

does it need to upgrade jicofo and jvb as well?

Thanks,

Sunny

Sent from Outlook <http://aka.ms/weboutlook>

------------------------------
*From:* dev <dev-bounces@jitsi.org> on behalf of Sunny Mok <
apollomok@hotmail.com>
*Sent:* Friday, February 17, 2017 2:05 AM
*To:* Jitsi Developers
*Subject:* Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi damencho,

At least which version or which commit hash would Jigasi support this
feature?

Thanks,

Sunny

Sent from Outlook <http://aka.ms/weboutlook>

------------------------------
*From:* dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <
damencho@jitsi.org>
*Sent:* Tuesday, February 14, 2017 4:30 AM
*To:* Jitsi Developers
*Subject:* Re: [jitsi-dev] Media mixing and Jigasi limitations

Hi,

the component is used only for outgoing calls, from jitsi-meet to the
sip side. For multiple jigasi instances to handle only sip incoming
you need:
JIGASI_OPTS="--nocomponent=true" in /etc/jitsi/jigasi/config
Also in /etc/jitsi/jigasi/sip-communicator.properties
org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN=https://your.serv
er.com/http-bind?room={roomName}

This way you can have multiple jigasi with registered with multiple
sip endpoints where you can use it and balance between them with some
logic from the sip service/server you are using.

Regards
damencho

On Tue, Feb 14, 2017 at 12:48 PM, Sunny Mok <apollomok@hotmail.com> wrote:
> Hi damencho
>
>
>>>
>>> 3. Only single Jigasi instance is supported by Jitisi.
>>For the call in functionality, you can configure multiple jigasis to
>>use bosh, then they will connect to conferences like regular
>>jitsi-meet client and you can have as many jigasi instances as you
>>like and make the balancing on the sip side.
>
>
> How should I configure to have many Jigasi instances?
>
> In my case, I would see below conflict error log if I try to get more
than
> 1 instance Jigasi.
>
>
> Thanks,
>
> Sunny Mok
>
>
> Feb 14, 2017 6:46:43 PM net.java.sip.communicator.util.Logger error
> SEVERE: conflict, host:192.168.118.59, port:5347
> org.xmpp.component.ComponentException: conflict
> at
> org.jivesoftware.whack.ExternalComponent.connect(ExternalCom
ponent.java:219)
> at
> org.jivesoftware.whack.ExternalComponentManager.addComponent
(ExternalComponentManager.java:221)
> at
> org.jivesoftware.whack.ExternalComponentManager.addComponent
(ExternalComponentManager.java:201)
> at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
> at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
> at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
> at java.util.concurrent.Executors$RunnableAdapter.call(
Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
tureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFu
tureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
>
> Sent from Outlook
>
>
>
> ________________________________
> From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
> <damencho@jitsi.org>
> Sent: Tuesday, February 14, 2017 1:42 AM
> To: Jitsi Developers
> Subject: Re: [jitsi-dev] Media mixing and Jigasi limitations
>
> Hi,
>
> On Tue, Feb 14, 2017 at 11:29 AM, Dima Gutzeit <gutzeit@maaii.com> > wrote:
>> Dear list members,
>>
>>
>>
>> I have few burning questions, regarding the Jigasi component of the
Jitsi
>> universe. During our tests we found some severe limitations and I need
to
>> confirm those findings to make sure we find the correct solutions:
>>
>>
>>
>> 1. When we try to join people to the room, by call-in method,
>> calling
>> towards Jigasi, there is a limitation of a one-user-per-second. Can’t
join
>> faster than that, no matter which room is being dialed.
>
> Not sure where this limitation comes from, do you see any exceptions
> or anything in jigasi logs.
>
>>
>> 2. Can’t join more than 30 participants to a single Jigasi server.
> It doesn't have any hardcoded limitations, it may be a bug or overload
> issue, logs will reveal more what maybe the problem.
>
>>
>> 3. Only single Jigasi instance is supported by Jitisi.
> For the call in functionality, you can configure multiple jigasis to
> use bosh, then they will connect to conferences like regular
> jitsi-meet client and you can have as many jigasi instances as you
> like and make the balancing on the sip side.
>
>>
>>
>>
>> Few questions:
>>
>>
>>
>> a. Are those findings correct?
>>
>> b. What is the scale-out strategy of Jitisi and Jigasi … I can’t
>> believe that those limitations are by design and the community is fine
>> with
>> that, so I assume it’s an issue with our understanding or testing
method?
> There are no hardcoded limitations, there can be overload problems see
> answer to c. or there can be bugs which needs to be investigated.
>
>>
>> c. Which component does the media mixing, for participants joining
>> through Jigasi, is it videobridge or Jigasi itself?
> Currently by default jigasi is doing the mixing, it decodes, mixes and
> encodes media, which is a cpu intensive work and the limit for this is
> the available resources on the server for that instance.
>
>>
>> d. Is there a way of buying commercial support from Atlassian, for
>> Jitsi ?
> This is not currently possible. I can just forward you to Yasen
> Pramatarov (https://lindeas.com).
>
> Regards
> damencho
>
>>
>>
>>
>> Thank’s in advance for your time.
>>
>>
>>
>> Regards,
>>
>> Dima Gutzeit.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> dev mailing list
>> dev@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev