[jitsi-users] meet.jit.si configuration changing


#1

Hey folks,

In an effort to load balance meet.jit.si better we are changing the
configuration a bit.

We would have multiple simultaneous deployments and in order for the
load balancers to properly route you to the right one, we would need
the bosh connection to come with a ?ROOM=<your_room_name_here> GET
parameter.

This would be automatically handled by the Jitsi Meet client ant the
Jitsi Meet Lib but we are putting the word out there for anyone who is
accessing the XMPP server through other means (like the raspberry pi
project).

Does anyone see this as an unsurmountable problem?

Emil

···

--
https://jitsi.org


#2

Dear Jitsi Users, We would like to acknowledge that we have received your request and a ticket has been created. A support representative will be reviewing your request and will send you a personal response.(usually within 24 hours). To view the status of the ticket or add comments, please visit https://networklab.freshdesk.com/helpdesk/tickets/32 Thank you for your patience. Sincerely, NetworkLab Support Team


#3

Dear Jitsi Developers, We would like to acknowledge that we have received your request and a ticket has been created. A support representative will be reviewing your request and will send you a personal response.(usually within 24 hours). To view the status of the ticket or add comments, please visit https://networklab.freshdesk.com/helpdesk/tickets/31 Thank you for your patience. Sincerely, NetworkLab Support Team


#4

Hi Emil,

I don't think it's a problem, but will it be possible to support both the old and the new connection schema at the same time, for some time at least?

thanks

Emil Ivov wrote:

···

Hey folks,

In an effort to load balance meet.jit.si better we are changing the
configuration a bit.

We would have multiple simultaneous deployments and in order for the
load balancers to properly route you to the right one, we would need
the bosh connection to come with a ?ROOM=<your_room_name_here> GET
parameter.

This would be automatically handled by the Jitsi Meet client ant the
Jitsi Meet Lib but we are putting the word out there for anyone who is
accessing the XMPP server through other means (like the raspberry pi
project).

Does anyone see this as an unsurmountable problem?

Emil


#5

I am afraid not. Without the URL param different participants may end up on
different servers

···

On Sunday, 15 November 2015, info@linux-projects.org < info@linux-projects.org> wrote:

Hi Emil,

I don't think it's a problem, but will it be possible to support both the
old and the new connection schema at the same time, for some time at least?

thanks

Emil Ivov wrote:

Hey folks,

In an effort to load balance meet.jit.si better we are changing the
configuration a bit.

We would have multiple simultaneous deployments and in order for the
load balancers to properly route you to the right one, we would need
the bosh connection to come with a ?ROOM=<your_room_name_here> GET
parameter.

This would be automatically handled by the Jitsi Meet client ant the
Jitsi Meet Lib but we are putting the word out there for anyone who is
accessing the XMPP server through other means (like the raspberry pi
project).

Does anyone see this as an unsurmountable problem?

Emil

--
https://jitsi.org


#6

When will this start exactly?

Emil Ivov wrote:

···

I am afraid not. Without the URL param different participants may end up on
different servers

On Sunday, 15 November 2015, info@linux-projects.org < > info@linux-projects.org> wrote:

Hi Emil,

I don't think it's a problem, but will it be possible to support both the
old and the new connection schema at the same time, for some time at least?

thanks

Emil Ivov wrote:

Hey folks,

In an effort to load balance meet.jit.si better we are changing the
configuration a bit.

We would have multiple simultaneous deployments and in order for the
load balancers to properly route you to the right one, we would need
the bosh connection to come with a ?ROOM=<your_room_name_here> GET
parameter.

This would be automatically handled by the Jitsi Meet client ant the
Jitsi Meet Lib but we are putting the word out there for anyone who is
accessing the XMPP server through other means (like the raspberry pi
project).

Does anyone see this as an unsurmountable problem?

Emil


#7

We were thinking of doing it last Friday but then realised it could break
things like this one.

···

On Sunday, 15 November 2015, info@linux-projects.org < info@linux-projects.org> wrote:

When will this start exactly?

Emil Ivov wrote:

I am afraid not. Without the URL param different participants may end up
on
different servers

On Sunday, 15 November 2015, info@linux-projects.org < >> info@linux-projects.org> wrote:

Hi Emil,

I don't think it's a problem, but will it be possible to support both the
old and the new connection schema at the same time, for some time at
least?

thanks

Emil Ivov wrote:

Hey folks,

In an effort to load balance meet.jit.si better we are changing the
configuration a bit.

We would have multiple simultaneous deployments and in order for the
load balancers to properly route you to the right one, we would need
the bosh connection to come with a ?ROOM=<your_room_name_here> GET
parameter.

This would be automatically handled by the Jitsi Meet client ant the
Jitsi Meet Lib but we are putting the word out there for anyone who is
accessing the XMPP server through other means (like the raspberry pi
project).

Does anyone see this as an unsurmountable problem?

Emil

--
https://jitsi.org


#8

Is there any active public jitsi meet service instance where I could test this at the moment?

Emil Ivov wrote:

···

We were thinking of doing it last Friday but then realised it could break
things like this one.

On Sunday, 15 November 2015, info@linux-projects.org < > info@linux-projects.org> wrote:

When will this start exactly?

Emil Ivov wrote:

I am afraid not. Without the URL param different participants may end up
on
different servers

On Sunday, 15 November 2015, info@linux-projects.org < >>> info@linux-projects.org> wrote:

Hi Emil,

I don't think it's a problem, but will it be possible to support both the
old and the new connection schema at the same time, for some time at
least?

thanks

Emil Ivov wrote:

Hey folks,

In an effort to load balance meet.jit.si better we are changing the
configuration a bit.

We would have multiple simultaneous deployments and in order for the
load balancers to properly route you to the right one, we would need
the bosh connection to come with a ?ROOM=<your_room_name_here> GET
parameter.

This would be automatically handled by the Jitsi Meet client ant the
Jitsi Meet Lib but we are putting the word out there for anyone who is
accessing the XMPP server through other means (like the raspberry pi
project).

Does anyone see this as an unsurmountable problem?

Emil


#9

Yes: https://whatever.jitsi.net

···

On Sun, Nov 15, 2015 at 3:54 PM, info@linux-projects.org <info@linux-projects.org> wrote:

Is there any active public jitsi meet service instance where I could test
this at the moment?

Emil Ivov wrote:

We were thinking of doing it last Friday but then realised it could break
things like this one.

On Sunday, 15 November 2015, info@linux-projects.org < >> info@linux-projects.org> wrote:

When will this start exactly?

Emil Ivov wrote:

I am afraid not. Without the URL param different participants may end up
on
different servers

On Sunday, 15 November 2015, info@linux-projects.org < >>>> info@linux-projects.org> wrote:

Hi Emil,

I don't think it's a problem, but will it be possible to support both
the
old and the new connection schema at the same time, for some time at
least?

thanks

Emil Ivov wrote:

Hey folks,

In an effort to load balance meet.jit.si better we are changing the
configuration a bit.

We would have multiple simultaneous deployments and in order for the
load balancers to properly route you to the right one, we would need
the bosh connection to come with a ?ROOM=<your_room_name_here> GET
parameter.

This would be automatically handled by the Jitsi Meet client ant the
Jitsi Meet Lib but we are putting the word out there for anyone who is
accessing the XMPP server through other means (like the raspberry pi
project).

Does anyone see this as an unsurmountable problem?

Emil

--
https://jitsi.org


#10

I confirm it works. Please let me know when you ll have officially switched to the new interface for meet.jit.si . Also, are you sure you want the ROOM parameter uppercase?

thanks

Emil Ivov wrote:

···

Yes: https://whatever.jitsi.net

On Sun, Nov 15, 2015 at 3:54 PM, info@linux-projects.org > <info@linux-projects.org> wrote:

Is there any active public jitsi meet service instance where I could test
this at the moment?

Emil Ivov wrote:

We were thinking of doing it last Friday but then realised it could break
things like this one.

On Sunday, 15 November 2015, info@linux-projects.org < >>> info@linux-projects.org> wrote:

When will this start exactly?

Emil Ivov wrote:

I am afraid not. Without the URL param different participants may end up
on
different servers

On Sunday, 15 November 2015, info@linux-projects.org < >>>>> info@linux-projects.org> wrote:

Hi Emil,

I don't think it's a problem, but will it be possible to support both
the
old and the new connection schema at the same time, for some time at
least?

thanks

Emil Ivov wrote:

Hey folks,

In an effort to load balance meet.jit.si better we are changing the
configuration a bit.

We would have multiple simultaneous deployments and in order for the
load balancers to properly route you to the right one, we would need
the bosh connection to come with a ?ROOM=<your_room_name_here> GET
parameter.

This would be automatically handled by the Jitsi Meet client ant the
Jitsi Meet Lib but we are putting the word out there for anyone who is
accessing the XMPP server through other means (like the raspberry pi
project).

Does anyone see this as an unsurmountable problem?

Emil


#11

I confirm it works. Please let me know when you ll have officially switched
to the new interface for meet.jit.si . Also, are you sure you want the ROOM
parameter uppercase?

No, you are right. Should have been lowercase. We have changed it now.
We are probably going to do the switch within the next few days! You
should start including the key already. It will just be ignored on the
current infra.

Thanks for trying this out!

Emil

···

On Sun, Nov 15, 2015 at 8:28 PM, info@linux-projects.org <info@linux-projects.org> wrote:

thanks

Emil Ivov wrote:

Yes: https://whatever.jitsi.net

On Sun, Nov 15, 2015 at 3:54 PM, info@linux-projects.org >> <info@linux-projects.org> wrote:

Is there any active public jitsi meet service instance where I could test
this at the moment?

Emil Ivov wrote:

We were thinking of doing it last Friday but then realised it could
break
things like this one.

On Sunday, 15 November 2015, info@linux-projects.org < >>>> info@linux-projects.org> wrote:

When will this start exactly?

Emil Ivov wrote:

I am afraid not. Without the URL param different participants may end
up
on
different servers

On Sunday, 15 November 2015, info@linux-projects.org < >>>>>> info@linux-projects.org> wrote:

Hi Emil,

I don't think it's a problem, but will it be possible to support both
the
old and the new connection schema at the same time, for some time at
least?

thanks

Emil Ivov wrote:

Hey folks,

In an effort to load balance meet.jit.si better we are changing the
configuration a bit.

We would have multiple simultaneous deployments and in order for the
load balancers to properly route you to the right one, we would need
the bosh connection to come with a ?ROOM=<your_room_name_here> GET
parameter.

This would be automatically handled by the Jitsi Meet client ant the
Jitsi Meet Lib but we are putting the word out there for anyone who
is
accessing the XMPP server through other means (like the raspberry pi
project).

Does anyone see this as an unsurmountable problem?

Emil

--
https://jitsi.org


#12

Dear Jitsi Users, Your ticket - [jitsi-users] meet.jit.si configuration changing - has been closed. We hope that the ticket was resolved to your satisfaction. If you feel that the ticket should not be closed or if the ticket has not been resolved, please reply to this email. Sincerely, NetworkLab Support Team https://networklab.freshdesk.com/helpdesk/tickets/32


#13

Dear Jitsi Developers, Your ticket - [jitsi-dev] meet.jit.si configuration changing - has been closed. We hope that the ticket was resolved to your satisfaction. If you feel that the ticket should not be closed or if the ticket has not been resolved, please reply to this email. Sincerely, NetworkLab Support Team https://networklab.freshdesk.com/helpdesk/tickets/31