[jitsi-users] Using Jitsi

#1

I wanted to ask about a couple things I've noticed while testing Jitis at
our location.

When users on windows or mac walk away and their computer goes to sleep, it
does not automatically reconnect them to the server when they return. When
they do reconnect, the contact list is usually empty, they have to close
Jitsi and open it back up to get to full working order.

Users don't go auto away when idle for a set amount of time. I have checked
the box for "Change status while away" and set the time down to 5 (I assume
that's minutes). It doesn't change users status when they leave for more
than 5 minutes.

If these are known bugs or if I'm not configuring something correctly, I
would appreciate knowing. Otherwise the app is great. We've been testing
the video chat and screen sharing and have had mostly good experiences.
Great work so far.

···

--
Caleb O'Connell

#2

Hey Caleb,

That generally works for most users but it is indeed possible that
there are sometimes issues. We did fix a couple of things there
recently so could you please try the latest nightly and send us the
logs if the issue persists?

https://jitsi.org/faq/logs

Thanks,
Emil

···

On Thu, Feb 6, 2014 at 6:02 PM, Caleb O'Connell <caleb@privacyassociation.org> wrote:

I wanted to ask about a couple things I've noticed while testing Jitis at
our location.

When users on windows or mac walk away and their computer goes to sleep, it
does not automatically reconnect them to the server when they return. When
they do reconnect, the contact list is usually empty, they have to close
Jitsi and open it back up to get to full working order.

Users don't go auto away when idle for a set amount of time. I have checked
the box for "Change status while away" and set the time down to 5 (I assume
that's minutes). It doesn't change users status when they leave for more
than 5 minutes.

If these are known bugs or if I'm not configuring something correctly, I
would appreciate knowing. Otherwise the app is great. We've been testing
the video chat and screen sharing and have had mostly good experiences.
Great work so far.

--
Caleb O'Connell

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

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
https://jitsi.org FAX: +33.1.77.62.47.31

#3

Emil,
So, I did some investigation and the auto away does work, I just had to set
the time lower than 15. Thanks.

The disconnect is not what I was thinking. When a user walks away and the
computer goes to sleep (or I just restart the ejabberd server) when they
reconnect, their roster list doesn't re-populate. Users who are on Spark,
it reconnects and the roster is rebuilt. Jitsi, only a few users show up,
maybe after some time some more do, but not all and not immediately. There
is a cache setting in ejabberd "ldap_user_cache_validity" that I've played
around with, but no luck.

I can send the logs from the users computer, where should I send those to?

Thanks again

Caleb

Emil Ivov wrote:

···

Hey Caleb,

That generally works for most users but it is indeed possible that
there are sometimes issues. We did fix a couple of things there
recently so could you please try the latest nightly and send us the
logs if the issue persists?

https://jitsi.org/faq/logs

Thanks,
Emil

On Thu, Feb 6, 2014 at 6:02 PM, Caleb O'Connell > <caleb@privacyassociation.org> wrote:

I wanted to ask about a couple things I've noticed while testing Jitis at
our location.

When users on windows or mac walk away and their computer goes to sleep,
it
does not automatically reconnect them to the server when they return.
When they do reconnect, the contact list is usually empty, they have to
close Jitsi and open it back up to get to full working order.

Users don't go auto away when idle for a set amount of time. I have
checked the box for "Change status while away" and set the time down to 5
(I assume
that's minutes). It doesn't change users status when they leave for more
than 5 minutes.

If these are known bugs or if I'm not configuring something correctly, I
would appreciate knowing. Otherwise the app is great. We've been
testing the video chat and screen sharing and have had mostly good
experiences. Great work so far.

--
Caleb O'Connell

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

#4

Hi,

We've seen the same behaviour here. Although it will indeed reconnect to
the XMPP server after having lost network connectivity (or in your case the
computer goes to sleep), Jitsi will not seem to retrieve its roster from
the server; thus all contacts will appear offline until we receive a
presence packet following a status changes -- then, contacts will start to
appear as available, or whatever their status is that triggered the
presence update.

The same issue arises when manually toggling between "Online" and
"Offline". Jitsi will reconnect, but will not seem to retrieve its
contacts, and their current statuses.

Jitsi appears to only fully retrieve its roster/contact presence upon first
connection, after launch. Closing/re-opening the software will indeed have
it retrieve its full contact list and its contacts' respective statuses.

We are also using ejabberd. Could it be related to how Jitsi establishes
its XMPP session when first launching vs. after a loss of network
connectivity? I know ejabberd pushes a user's roster along with every
contacts' statuses upon connection, but that doesn't seem to happen when
Jitsi "reconnects", although it is triggered when it connects initially.

Thanks.

···

On Tue, Feb 11, 2014 at 11:55 AM, Caleb O'Connell < caleb@privacyassociation.org> wrote:

Emil,
So, I did some investigation and the auto away does work, I just had to set
the time lower than 15. Thanks.

The disconnect is not what I was thinking. When a user walks away and the
computer goes to sleep (or I just restart the ejabberd server) when they
reconnect, their roster list doesn't re-populate. Users who are on Spark,
it reconnects and the roster is rebuilt. Jitsi, only a few users show up,
maybe after some time some more do, but not all and not immediately. There
is a cache setting in ejabberd "ldap_user_cache_validity" that I've played
around with, but no luck.

I can send the logs from the users computer, where should I send those to?

Thanks again

Caleb

Emil Ivov wrote:

> Hey Caleb,
>
> That generally works for most users but it is indeed possible that
> there are sometimes issues. We did fix a couple of things there
> recently so could you please try the latest nightly and send us the
> logs if the issue persists?
>
> https://jitsi.org/faq/logs
>
> Thanks,
> Emil
>
> On Thu, Feb 6, 2014 at 6:02 PM, Caleb O'Connell > > <caleb@privacyassociation.org> wrote:
>> I wanted to ask about a couple things I've noticed while testing Jitis
at
>> our location.
>>
>> When users on windows or mac walk away and their computer goes to sleep,
>> it
>> does not automatically reconnect them to the server when they return.
>> When they do reconnect, the contact list is usually empty, they have to
>> close Jitsi and open it back up to get to full working order.
>>
>> Users don't go auto away when idle for a set amount of time. I have
>> checked the box for "Change status while away" and set the time down to
5
>> (I assume
>> that's minutes). It doesn't change users status when they leave for
more
>> than 5 minutes.
>>
>> If these are known bugs or if I'm not configuring something correctly, I
>> would appreciate knowing. Otherwise the app is great. We've been
>> testing the video chat and screen sharing and have had mostly good
>> experiences. Great work so far.
>>
>> --
>> Caleb O'Connell
>>
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>

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

--

*Sébastien Couture Vice-président et chef des technologies / VP & CTO
scouture@ubity.com <scouture@ubity.com>*

Tel.: 514.907.3400 x105
Fax: 514.907.3401
*Ubity -* www.ubity.com
Technologie d'affaires IP unifiée
Unified Business IP Technology

#5

Hi Caleb and Sébastien,

there is no difference when xmpp protocol provider is initially
registered or reconnected, we are using plugin to reconnect all
protocol providers which is working the same way the GUI will connect
the provider on startup.
What we do in xmpp, is when we detect the initial roster packet we
start initing the contacts inside jitsi.
Me, personally, have never seen this behaviour with openfire. It will
be helpful to check the logs(those including pcap) when this happens.
Also when this happens are the contacts there(just offline and
hidden), and just they are missing their available statuses?

Regards
damencho

···

On Tue, Feb 11, 2014 at 11:14 PM, Sébastien Couture <scouture@ubity.com> wrote:

Hi,

We've seen the same behaviour here. Although it will indeed reconnect to the
XMPP server after having lost network connectivity (or in your case the
computer goes to sleep), Jitsi will not seem to retrieve its roster from the
server; thus all contacts will appear offline until we receive a presence
packet following a status changes -- then, contacts will start to appear as
available, or whatever their status is that triggered the presence update.

The same issue arises when manually toggling between "Online" and "Offline".
Jitsi will reconnect, but will not seem to retrieve its contacts, and their
current statuses.

Jitsi appears to only fully retrieve its roster/contact presence upon first
connection, after launch. Closing/re-opening the software will indeed have
it retrieve its full contact list and its contacts' respective statuses.

We are also using ejabberd. Could it be related to how Jitsi establishes its
XMPP session when first launching vs. after a loss of network connectivity?
I know ejabberd pushes a user's roster along with every contacts' statuses
upon connection, but that doesn't seem to happen when Jitsi "reconnects",
although it is triggered when it connects initially.

Thanks.

On Tue, Feb 11, 2014 at 11:55 AM, Caleb O'Connell > <caleb@privacyassociation.org> wrote:

Emil,
So, I did some investigation and the auto away does work, I just had to
set
the time lower than 15. Thanks.

The disconnect is not what I was thinking. When a user walks away and the
computer goes to sleep (or I just restart the ejabberd server) when they
reconnect, their roster list doesn't re-populate. Users who are on Spark,
it reconnects and the roster is rebuilt. Jitsi, only a few users show up,
maybe after some time some more do, but not all and not immediately.
There
is a cache setting in ejabberd "ldap_user_cache_validity" that I've played
around with, but no luck.

I can send the logs from the users computer, where should I send those to?

Thanks again

Caleb

Emil Ivov wrote:

> Hey Caleb,
>
> That generally works for most users but it is indeed possible that
> there are sometimes issues. We did fix a couple of things there
> recently so could you please try the latest nightly and send us the
> logs if the issue persists?
>
> https://jitsi.org/faq/logs
>
> Thanks,
> Emil
>
> On Thu, Feb 6, 2014 at 6:02 PM, Caleb O'Connell >> > <caleb@privacyassociation.org> wrote:
>> I wanted to ask about a couple things I've noticed while testing Jitis
>> at
>> our location.
>>
>> When users on windows or mac walk away and their computer goes to
>> sleep,
>> it
>> does not automatically reconnect them to the server when they return.
>> When they do reconnect, the contact list is usually empty, they have to
>> close Jitsi and open it back up to get to full working order.
>>
>> Users don't go auto away when idle for a set amount of time. I have
>> checked the box for "Change status while away" and set the time down to
>> 5
>> (I assume
>> that's minutes). It doesn't change users status when they leave for
>> more
>> than 5 minutes.
>>
>> If these are known bugs or if I'm not configuring something correctly,
>> I
>> would appreciate knowing. Otherwise the app is great. We've been
>> testing the video chat and screen sharing and have had mostly good
>> experiences. Great work so far.
>>
>> --
>> Caleb O'Connell
>>
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>

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

--
Sébastien Couture
Vice-président et chef des technologies / VP & CTO
scouture@ubity.com

Tel.: 514.907.3400 x105
Fax: 514.907.3401

Ubity - www.ubity.com
Technologie d'affaires IP unifiée
Unified Business IP Technology

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

#6

I can confirm what Sébastien said in his post. A user does reconnect, and
thus is viewable from other rosters but until a user updates their status
they don't show up on the reconnected users roster. Either upon waking up
from sleep mode or manually going offline then back online, the symptom is
the same. Jitsi seems to rely on the server broadcasting back the full
roster every time the status changes. We used spark before this and it
would repopulate, which makes me think Spark requests the users roster on
every reconnect. Openfire, I suspect, sends back the entire roster on every
status change.

It seems less of a bug and more of a difference of expected actions by the
client to the server. Either Jitsi should request the full roster on every
status change? Maybe just when it sees that it has network connection again?
I'm curious if there is a setting in ejabberd to send the full roster on
every status change, which would probably solve this as well.

Caleb

Damian Minkov wrote:

···

Hi Caleb and Sébastien,

there is no difference when xmpp protocol provider is initially
registered or reconnected, we are using plugin to reconnect all
protocol providers which is working the same way the GUI will connect
the provider on startup.
What we do in xmpp, is when we detect the initial roster packet we
start initing the contacts inside jitsi.
Me, personally, have never seen this behaviour with openfire. It will
be helpful to check the logs(those including pcap) when this happens.
Also when this happens are the contacts there(just offline and
hidden), and just they are missing their available statuses?

Regards
damencho

On Tue, Feb 11, 2014 at 11:14 PM, Sébastien Couture > <scouture@ubity.com> wrote:

Hi,

We've seen the same behaviour here. Although it will indeed reconnect to
the XMPP server after having lost network connectivity (or in your case
the computer goes to sleep), Jitsi will not seem to retrieve its roster
from the server; thus all contacts will appear offline until we receive a
presence packet following a status changes -- then, contacts will start
to appear as available, or whatever their status is that triggered the
presence update.

The same issue arises when manually toggling between "Online" and
"Offline". Jitsi will reconnect, but will not seem to retrieve its
contacts, and their current statuses.

Jitsi appears to only fully retrieve its roster/contact presence upon
first connection, after launch. Closing/re-opening the software will
indeed have it retrieve its full contact list and its contacts'
respective statuses.

We are also using ejabberd. Could it be related to how Jitsi establishes
its XMPP session when first launching vs. after a loss of network
connectivity? I know ejabberd pushes a user's roster along with every
contacts' statuses upon connection, but that doesn't seem to happen when
Jitsi "reconnects", although it is triggered when it connects initially.

Thanks.

On Tue, Feb 11, 2014 at 11:55 AM, Caleb O'Connell >> <caleb@privacyassociation.org> wrote:

Emil,
So, I did some investigation and the auto away does work, I just had to
set
the time lower than 15. Thanks.

The disconnect is not what I was thinking. When a user walks away and
the computer goes to sleep (or I just restart the ejabberd server) when
they
reconnect, their roster list doesn't re-populate. Users who are on
Spark,
it reconnects and the roster is rebuilt. Jitsi, only a few users show
up, maybe after some time some more do, but not all and not immediately.
There
is a cache setting in ejabberd "ldap_user_cache_validity" that I've
played around with, but no luck.

I can send the logs from the users computer, where should I send those
to?

Thanks again

Caleb

Emil Ivov wrote:

> Hey Caleb,
>
> That generally works for most users but it is indeed possible that
> there are sometimes issues. We did fix a couple of things there
> recently so could you please try the latest nightly and send us the
> logs if the issue persists?
>
> https://jitsi.org/faq/logs
>
> Thanks,
> Emil
>
> On Thu, Feb 6, 2014 at 6:02 PM, Caleb O'Connell >>> > <caleb@privacyassociation.org> wrote:
>> I wanted to ask about a couple things I've noticed while testing
>> Jitis at
>> our location.
>>
>> When users on windows or mac walk away and their computer goes to
>> sleep,
>> it
>> does not automatically reconnect them to the server when they return.
>> When they do reconnect, the contact list is usually empty, they have
>> to close Jitsi and open it back up to get to full working order.
>>
>> Users don't go auto away when idle for a set amount of time. I have
>> checked the box for "Change status while away" and set the time down
>> to 5
>> (I assume
>> that's minutes). It doesn't change users status when they leave for
>> more
>> than 5 minutes.
>>
>> If these are known bugs or if I'm not configuring something
>> correctly, I
>> would appreciate knowing. Otherwise the app is great. We've been
>> testing the video chat and screen sharing and have had mostly good
>> experiences. Great work so far.
>>
>> --
>> Caleb O'Connell
>>
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>

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

--
Sébastien Couture
Vice-président et chef des technologies / VP & CTO
scouture@ubity.com

Tel.: 514.907.3400 x105
Fax: 514.907.3401

Ubity - www.ubity.com
Technologie d'affaires IP unifiée
Unified Business IP Technology

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

--
Caleb O'Connell CIPP/US, CIPP/IT | Systems Administrator
IAPP | International Association of Privacy Professionals
Pease International Tradeport
75 Rochester Ave., Suite 4 | Portsmouth, NH 03801 USA
+1.603.427.9200 | Fax: +1.603.427.9249
caleb@privacyassociation.org | www.privacyassociation.org

#7

I can confirm what Sébastien said in his post. A user does reconnect, and
thus is viewable from other rosters but until a user updates their status
they don't show up on the reconnected users roster. Either upon waking up
from sleep mode or manually going offline then back online, the symptom is
the same. Jitsi seems to rely on the server broadcasting back the full
roster every time the status changes.

Eeer ... no. Jitsi does not rely on anything like this. It does however
rely on the server doing this upon every reconnect.

We used spark before this and it
would repopulate, which makes me think Spark requests the users roster on
every reconnect. Openfire, I suspect, sends back the entire roster on

every

status change.

The roster is indeed sent on every reconnect. That's standard XMPP
behaviour.

It seems less of a bug and more of a difference of expected actions by the
client to the server. Either Jitsi should request the full roster on every
status change? Maybe just when it sees that it has network connection

again?

I'm curious if there is a setting in ejabberd to send the full roster on
every status change, which would probably solve this as well.

It would be good to first confirm that this is actually the problem.

Emil

Caleb

Damian Minkov wrote:

Hi Caleb and Sébastien,

there is no difference when xmpp protocol provider is initially
registered or reconnected, we are using plugin to reconnect all
protocol providers which is working the same way the GUI will connect
the provider on startup.
What we do in xmpp, is when we detect the initial roster packet we
start initing the contacts inside jitsi.
Me, personally, have never seen this behaviour with openfire. It will
be helpful to check the logs(those including pcap) when this happens.
Also when this happens are the contacts there(just offline and
hidden), and just they are missing their available statuses?

Regards
damencho

Hi,

We've seen the same behaviour here. Although it will indeed reconnect to
the XMPP server after having lost network connectivity (or in your case
the computer goes to sleep), Jitsi will not seem to retrieve its roster
from the server; thus all contacts will appear offline until we receive

a

presence packet following a status changes -- then, contacts will start
to appear as available, or whatever their status is that triggered the
presence update.

The same issue arises when manually toggling between "Online" and
"Offline". Jitsi will reconnect, but will not seem to retrieve its
contacts, and their current statuses.

Jitsi appears to only fully retrieve its roster/contact presence upon
first connection, after launch. Closing/re-opening the software will
indeed have it retrieve its full contact list and its contacts'
respective statuses.

We are also using ejabberd. Could it be related to how Jitsi establishes
its XMPP session when first launching vs. after a loss of network
connectivity? I know ejabberd pushes a user's roster along with every
contacts' statuses upon connection, but that doesn't seem to happen when
Jitsi "reconnects", although it is triggered when it connects initially.

Thanks.

Emil,
So, I did some investigation and the auto away does work, I just had to
set
the time lower than 15. Thanks.

The disconnect is not what I was thinking. When a user walks away and
the computer goes to sleep (or I just restart the ejabberd server) when
they
reconnect, their roster list doesn't re-populate. Users who are on
Spark,
it reconnects and the roster is rebuilt. Jitsi, only a few users show
up, maybe after some time some more do, but not all and not

immediately.

There
is a cache setting in ejabberd "ldap_user_cache_validity" that I've
played around with, but no luck.

I can send the logs from the users computer, where should I send those
to?

Thanks again

Caleb

Emil Ivov wrote:

> Hey Caleb,
>
> That generally works for most users but it is indeed possible that
> there are sometimes issues. We did fix a couple of things there
> recently so could you please try the latest nightly and send us the
> logs if the issue persists?
>
> https://jitsi.org/faq/logs
>
> Thanks,
> Emil
>
>> I wanted to ask about a couple things I've noticed while testing
>> Jitis at
>> our location.
>>
>> When users on windows or mac walk away and their computer goes to
>> sleep,
>> it
>> does not automatically reconnect them to the server when they

return.

···

On Thu, Feb 13, 2014 at 6:02 PM, Caleb O'Connell < caleb@privacyassociation.org> wrote:

On Tue, Feb 11, 2014 at 11:14 PM, Sébastien Couture >> <scouture@ubity.com> wrote:

On Tue, Feb 11, 2014 at 11:55 AM, Caleb O'Connell >>> <caleb@privacyassociation.org> wrote:

> On Thu, Feb 6, 2014 at 6:02 PM, Caleb O'Connell >>>> > <caleb@privacyassociation.org> wrote:
>> When they do reconnect, the contact list is usually empty, they have
>> to close Jitsi and open it back up to get to full working order.
>>
>> Users don't go auto away when idle for a set amount of time. I have
>> checked the box for "Change status while away" and set the time down
>> to 5
>> (I assume
>> that's minutes). It doesn't change users status when they leave for
>> more
>> than 5 minutes.
>>
>> If these are known bugs or if I'm not configuring something
>> correctly, I
>> would appreciate knowing. Otherwise the app is great. We've been
>> testing the video chat and screen sharing and have had mostly good
>> experiences. Great work so far.
>>
>> --
>> Caleb O'Connell
>>
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>

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

--
Sébastien Couture
Vice-président et chef des technologies / VP & CTO
scouture@ubity.com

Tel.: 514.907.3400 x105
Fax: 514.907.3401

Ubity - www.ubity.com
Technologie d'affaires IP unifiée
Unified Business IP Technology

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

--
Caleb O'Connell CIPP/US, CIPP/IT | Systems Administrator
IAPP | International Association of Privacy Professionals
Pease International Tradeport
75 Rochester Ave., Suite 4 | Portsmouth, NH 03801 USA
+1.603.427.9200 | Fax: +1.603.427.9249
caleb@privacyassociation.org | www.privacyassociation.org

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

--
https://jitsi.o

#8

Emil,

I do see a <query xmlns='jabber:iq:roster'/> IQ from Jitsi (asking for its
roster) in both situations; either upon first connection after launch, or
after a network connectivity loss / offline-online toggle. In both cases,
the XMPP server (here, ejabberd) sends back the full roster, along with the
presence of contacts that are available at that moment.

The issue is that Jitsi will somehow only display these contacts as
available on the first connection, and not after a reconnect. When
reconnecting, Jitsi will show these contacts as offline at first, and then
display them as online only when it receives a presence update.

···

On Thu, Feb 13, 2014 at 12:59 PM, Emil Ivov <emcho@jitsi.org> wrote:

On Thu, Feb 13, 2014 at 6:02 PM, Caleb O'Connell < > caleb@privacyassociation.org> wrote:
> I can confirm what Sébastien said in his post. A user does reconnect, and
> thus is viewable from other rosters but until a user updates their status
> they don't show up on the reconnected users roster. Either upon waking up
> from sleep mode or manually going offline then back online, the symptom
is
> the same. Jitsi seems to rely on the server broadcasting back the full
> roster every time the status changes.

Eeer ... no. Jitsi does not rely on anything like this. It does however
rely on the server doing this upon every reconnect.

> We used spark before this and it
> would repopulate, which makes me think Spark requests the users roster on
> every reconnect. Openfire, I suspect, sends back the entire roster on
every
> status change.

The roster is indeed sent on every reconnect. That's standard XMPP
behaviour.

> It seems less of a bug and more of a difference of expected actions by
the
> client to the server. Either Jitsi should request the full roster on
every
> status change? Maybe just when it sees that it has network connection
again?
> I'm curious if there is a setting in ejabberd to send the full roster on
> every status change, which would probably solve this as well.

It would be good to first confirm that this is actually the problem.

Emil

>
> Caleb
>
> Damian Minkov wrote:
>
>> Hi Caleb and Sébastien,
>>
>> there is no difference when xmpp protocol provider is initially
>> registered or reconnected, we are using plugin to reconnect all
>> protocol providers which is working the same way the GUI will connect
>> the provider on startup.
>> What we do in xmpp, is when we detect the initial roster packet we
>> start initing the contacts inside jitsi.
>> Me, personally, have never seen this behaviour with openfire. It will
>> be helpful to check the logs(those including pcap) when this happens.
>> Also when this happens are the contacts there(just offline and
>> hidden), and just they are missing their available statuses?
>>
>> Regards
>> damencho
>>
>>
>> On Tue, Feb 11, 2014 at 11:14 PM, Sébastien Couture > >> <scouture@ubity.com> wrote:
>>> Hi,
>>>
>>> We've seen the same behaviour here. Although it will indeed reconnect
to
>>> the XMPP server after having lost network connectivity (or in your case
>>> the computer goes to sleep), Jitsi will not seem to retrieve its roster
>>> from the server; thus all contacts will appear offline until we
receive a
>>> presence packet following a status changes -- then, contacts will start
>>> to appear as available, or whatever their status is that triggered the
>>> presence update.
>>>
>>> The same issue arises when manually toggling between "Online" and
>>> "Offline". Jitsi will reconnect, but will not seem to retrieve its
>>> contacts, and their current statuses.
>>>
>>> Jitsi appears to only fully retrieve its roster/contact presence upon
>>> first connection, after launch. Closing/re-opening the software will
>>> indeed have it retrieve its full contact list and its contacts'
>>> respective statuses.
>>>
>>> We are also using ejabberd. Could it be related to how Jitsi
establishes
>>> its XMPP session when first launching vs. after a loss of network
>>> connectivity? I know ejabberd pushes a user's roster along with every
>>> contacts' statuses upon connection, but that doesn't seem to happen
when
>>> Jitsi "reconnects", although it is triggered when it connects
initially.
>>>
>>> Thanks.
>>>
>>>
>>>
>>> On Tue, Feb 11, 2014 at 11:55 AM, Caleb O'Connell > >>> <caleb@privacyassociation.org> wrote:
>>>>
>>>> Emil,
>>>> So, I did some investigation and the auto away does work, I just had
to
>>>> set
>>>> the time lower than 15. Thanks.
>>>>
>>>> The disconnect is not what I was thinking. When a user walks away and
>>>> the computer goes to sleep (or I just restart the ejabberd server)
when
>>>> they
>>>> reconnect, their roster list doesn't re-populate. Users who are on
>>>> Spark,
>>>> it reconnects and the roster is rebuilt. Jitsi, only a few users show
>>>> up, maybe after some time some more do, but not all and not
immediately.
>>>> There
>>>> is a cache setting in ejabberd "ldap_user_cache_validity" that I've
>>>> played around with, but no luck.
>>>>
>>>> I can send the logs from the users computer, where should I send those
>>>> to?
>>>>
>>>> Thanks again
>>>>
>>>> Caleb
>>>>
>>>> Emil Ivov wrote:
>>>>
>>>> > Hey Caleb,
>>>> >
>>>> > That generally works for most users but it is indeed possible that
>>>> > there are sometimes issues. We did fix a couple of things there
>>>> > recently so could you please try the latest nightly and send us the
>>>> > logs if the issue persists?
>>>> >
>>>> > https://jitsi.org/faq/logs
>>>> >
>>>> > Thanks,
>>>> > Emil
>>>> >
>>>> > On Thu, Feb 6, 2014 at 6:02 PM, Caleb O'Connell > >>>> > <caleb@privacyassociation.org> wrote:
>>>> >> I wanted to ask about a couple things I've noticed while testing
>>>> >> Jitis at
>>>> >> our location.
>>>> >>
>>>> >> When users on windows or mac walk away and their computer goes to
>>>> >> sleep,
>>>> >> it
>>>> >> does not automatically reconnect them to the server when they
return.
>>>> >> When they do reconnect, the contact list is usually empty, they
have
>>>> >> to close Jitsi and open it back up to get to full working order.
>>>> >>
>>>> >> Users don't go auto away when idle for a set amount of time. I have
>>>> >> checked the box for "Change status while away" and set the time
down
>>>> >> to 5
>>>> >> (I assume
>>>> >> that's minutes). It doesn't change users status when they leave for
>>>> >> more
>>>> >> than 5 minutes.
>>>> >>
>>>> >> If these are known bugs or if I'm not configuring something
>>>> >> correctly, I
>>>> >> would appreciate knowing. Otherwise the app is great. We've been
>>>> >> testing the video chat and screen sharing and have had mostly good
>>>> >> experiences. Great work so far.
>>>> >>
>>>> >> --
>>>> >> Caleb O'Connell
>>>> >>
>>>> >>
>>>> >> _______________________________________________
>>>> >> users mailing list
>>>> >> users@jitsi.org
>>>> >> Unsubscribe instructions and other list options:
>>>> >> http://lists.jitsi.org/mailman/listinfo/users
>>>> >
>>>> >
>>>> >
>>>>
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/users
>>>
>>>
>>>
>>>
>>> --
>>> Sébastien Couture
>>> Vice-président et chef des technologies / VP & CTO
>>> scouture@ubity.com
>>>
>>> Tel.: 514.907.3400 x105
>>> Fax: 514.907.3401
>>>
>>> Ubity - www.ubity.com
>>> Technologie d'affaires IP unifiée
>>> Unified Business IP Technology
>>>
>>> _______________________________________________
>>> users mailing list
>>> users@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/users
> --
> Caleb O'Connell CIPP/US, CIPP/IT | Systems Administrator
> IAPP | International Association of Privacy Professionals
> Pease International Tradeport
> 75 Rochester Ave., Suite 4 | Portsmouth, NH 03801 USA
> +1.603.427.9200 | Fax: +1.603.427.9249
> caleb@privacyassociation.org | www.privacyassociation.org
>
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

--
https://jitsi.o

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

--

*Sébastien Couture Vice-président et chef des technologies / VP & CTO
scouture@ubity.com <scouture@ubity.com>*

Tel.: 514.907.3400 x105
Fax: 514.907.3401
*Ubity -* www.ubity.com
Technologie d'affaires IP unifiée
Unified Business IP Technology

#9

That's very useful. Thanks Sébastien !

Could you please open a ticket? Not sure when we will be able to have a
look but I want to make sure we don't forget.

Cheers,
Emil

--sent from my mobile

···

On 13 Feb 2014 7:59 PM, "Sébastien Couture" <scouture@ubity.com> wrote:

Emil,

I do see a <query xmlns='jabber:iq:roster'/> IQ from Jitsi (asking for its
roster) in both situations; either upon first connection after launch, or
after a network connectivity loss / offline-online toggle. In both cases,
the XMPP server (here, ejabberd) sends back the full roster, along with the
presence of contacts that are available at that moment.

The issue is that Jitsi will somehow only display these contacts as
available on the first connection, and not after a reconnect. When
reconnecting, Jitsi will show these contacts as offline at first, and then
display them as online only when it receives a presence update.

On Thu, Feb 13, 2014 at 12:59 PM, Emil Ivov <emcho@jitsi.org> wrote:

On Thu, Feb 13, 2014 at 6:02 PM, Caleb O'Connell < >> caleb@privacyassociation.org> wrote:
> I can confirm what Sébastien said in his post. A user does reconnect,
and
> thus is viewable from other rosters but until a user updates their
status
> they don't show up on the reconnected users roster. Either upon waking
up
> from sleep mode or manually going offline then back online, the symptom
is
> the same. Jitsi seems to rely on the server broadcasting back the full
> roster every time the status changes.

Eeer ... no. Jitsi does not rely on anything like this. It does however
rely on the server doing this upon every reconnect.

> We used spark before this and it
> would repopulate, which makes me think Spark requests the users roster
on
> every reconnect. Openfire, I suspect, sends back the entire roster on
every
> status change.

The roster is indeed sent on every reconnect. That's standard XMPP
behaviour.

> It seems less of a bug and more of a difference of expected actions by
the
> client to the server. Either Jitsi should request the full roster on
every
> status change? Maybe just when it sees that it has network connection
again?
> I'm curious if there is a setting in ejabberd to send the full roster on
> every status change, which would probably solve this as well.

It would be good to first confirm that this is actually the problem.

Emil

>
> Caleb
>
> Damian Minkov wrote:
>
>> Hi Caleb and Sébastien,
>>
>> there is no difference when xmpp protocol provider is initially
>> registered or reconnected, we are using plugin to reconnect all
>> protocol providers which is working the same way the GUI will connect
>> the provider on startup.
>> What we do in xmpp, is when we detect the initial roster packet we
>> start initing the contacts inside jitsi.
>> Me, personally, have never seen this behaviour with openfire. It will
>> be helpful to check the logs(those including pcap) when this happens.
>> Also when this happens are the contacts there(just offline and
>> hidden), and just they are missing their available statuses?
>>
>> Regards
>> damencho
>>
>>
>> On Tue, Feb 11, 2014 at 11:14 PM, Sébastien Couture >> >> <scouture@ubity.com> wrote:
>>> Hi,
>>>
>>> We've seen the same behaviour here. Although it will indeed reconnect
to
>>> the XMPP server after having lost network connectivity (or in your
case
>>> the computer goes to sleep), Jitsi will not seem to retrieve its
roster
>>> from the server; thus all contacts will appear offline until we
receive a
>>> presence packet following a status changes -- then, contacts will
start
>>> to appear as available, or whatever their status is that triggered the
>>> presence update.
>>>
>>> The same issue arises when manually toggling between "Online" and
>>> "Offline". Jitsi will reconnect, but will not seem to retrieve its
>>> contacts, and their current statuses.
>>>
>>> Jitsi appears to only fully retrieve its roster/contact presence upon
>>> first connection, after launch. Closing/re-opening the software will
>>> indeed have it retrieve its full contact list and its contacts'
>>> respective statuses.
>>>
>>> We are also using ejabberd. Could it be related to how Jitsi
establishes
>>> its XMPP session when first launching vs. after a loss of network
>>> connectivity? I know ejabberd pushes a user's roster along with every
>>> contacts' statuses upon connection, but that doesn't seem to happen
when
>>> Jitsi "reconnects", although it is triggered when it connects
initially.
>>>
>>> Thanks.
>>>
>>>
>>>
>>> On Tue, Feb 11, 2014 at 11:55 AM, Caleb O'Connell >> >>> <caleb@privacyassociation.org> wrote:
>>>>
>>>> Emil,
>>>> So, I did some investigation and the auto away does work, I just had
to
>>>> set
>>>> the time lower than 15. Thanks.
>>>>
>>>> The disconnect is not what I was thinking. When a user walks away and
>>>> the computer goes to sleep (or I just restart the ejabberd server)
when
>>>> they
>>>> reconnect, their roster list doesn't re-populate. Users who are on
>>>> Spark,
>>>> it reconnects and the roster is rebuilt. Jitsi, only a few users show
>>>> up, maybe after some time some more do, but not all and not
immediately.
>>>> There
>>>> is a cache setting in ejabberd "ldap_user_cache_validity" that I've
>>>> played around with, but no luck.
>>>>
>>>> I can send the logs from the users computer, where should I send
those
>>>> to?
>>>>
>>>> Thanks again
>>>>
>>>> Caleb
>>>>
>>>> Emil Ivov wrote:
>>>>
>>>> > Hey Caleb,
>>>> >
>>>> > That generally works for most users but it is indeed possible that
>>>> > there are sometimes issues. We did fix a couple of things there
>>>> > recently so could you please try the latest nightly and send us the
>>>> > logs if the issue persists?
>>>> >
>>>> > https://jitsi.org/faq/logs
>>>> >
>>>> > Thanks,
>>>> > Emil
>>>> >
>>>> > On Thu, Feb 6, 2014 at 6:02 PM, Caleb O'Connell >> >>>> > <caleb@privacyassociation.org> wrote:
>>>> >> I wanted to ask about a couple things I've noticed while testing
>>>> >> Jitis at
>>>> >> our location.
>>>> >>
>>>> >> When users on windows or mac walk away and their computer goes to
>>>> >> sleep,
>>>> >> it
>>>> >> does not automatically reconnect them to the server when they
return.
>>>> >> When they do reconnect, the contact list is usually empty, they
have
>>>> >> to close Jitsi and open it back up to get to full working order.
>>>> >>
>>>> >> Users don't go auto away when idle for a set amount of time. I
have
>>>> >> checked the box for "Change status while away" and set the time
down
>>>> >> to 5
>>>> >> (I assume
>>>> >> that's minutes). It doesn't change users status when they leave
for
>>>> >> more
>>>> >> than 5 minutes.
>>>> >>
>>>> >> If these are known bugs or if I'm not configuring something
>>>> >> correctly, I
>>>> >> would appreciate knowing. Otherwise the app is great. We've been
>>>> >> testing the video chat and screen sharing and have had mostly good
>>>> >> experiences. Great work so far.
>>>> >>
>>>> >> --
>>>> >> Caleb O'Connell
>>>> >>
>>>> >>
>>>> >> _______________________________________________
>>>> >> users mailing list
>>>> >> users@jitsi.org
>>>> >> Unsubscribe instructions and other list options:
>>>> >> http://lists.jitsi.org/mailman/listinfo/users
>>>> >
>>>> >
>>>> >
>>>>
>>>>
>>>> _______________________________________________
>>>> users mailing list
>>>> users@jitsi.org
>>>> Unsubscribe instructions and other list options:
>>>> http://lists.jitsi.org/mailman/listinfo/users
>>>
>>>
>>>
>>>
>>> --
>>> Sébastien Couture
>>> Vice-président et chef des technologies / VP & CTO
>>> scouture@ubity.com
>>>
>>> Tel.: 514.907.3400 x105
>>> Fax: 514.907.3401
>>>
>>> Ubity - www.ubity.com
>>> Technologie d'affaires IP unifiée
>>> Unified Business IP Technology
>>>
>>> _______________________________________________
>>> users mailing list
>>> users@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/users
> --
> Caleb O'Connell CIPP/US, CIPP/IT | Systems Administrator
> IAPP | International Association of Privacy Professionals
> Pease International Tradeport
> 75 Rochester Ave., Suite 4 | Portsmouth, NH 03801 USA
> +1.603.427.9200 | Fax: +1.603.427.9249
> caleb@privacyassociation.org | www.privacyassociation.org
>
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

--
https://jitsi.o

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

--

*Sébastien Couture Vice-président et chef des technologies / VP & CTO
scouture@ubity.com <scouture@ubity.com>*

Tel.: 514.907.3400 x105
Fax: 514.907.3401
*Ubity -* www.ubity.com
Technologie d'affaires IP unifiée
Unified Business IP Technology

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

#10

Sure, I'll do that.

Thanks.

···

On Monday, February 17, 2014, Emil Ivov <emcho@jitsi.org> wrote:

That's very useful. Thanks Sébastien !

Could you please open a ticket? Not sure when we will be able to have a
look but I want to make sure we don't forget.

Cheers,
Emil

--sent from my mobile
On 13 Feb 2014 7:59 PM, "Sébastien Couture" <scouture@ubity.com> wrote:

Emil,

I do see a <query xmlns='jabber:iq:roster'/> IQ from Jitsi (asking for its
roster) in both situations; either upon first connection after launch, or
after a network connectivity loss / offline-online toggle. In both cases,
the XMPP server (here, ejabberd) sends back the full roster, along with the
presence of contacts that are available at that moment.

The issue is that Jitsi will somehow only display these contacts as
available on the first connection, and not after a reconnect. When
reconnecting, Jitsi will show these contacts as offline at first, and then
display them as online only when it receives a presence update.

On Thu, Feb 13, 2014 at 12:59 PM, Emil Ivov <emcho@jitsi.org> wrote:

On Thu, Feb 13, 2014 at 6:02 PM, Caleb O'Connell < > caleb@privacyassociation.org> wrote:
> I can confirm what Sébastien said in his post. A user does reconnect, and
> thus is viewable from other rosters but until a user updates their status
> they don't show up on the reconnected users roster. Either upon waking up
> from sleep mode or manually going offline then back online, the symptom
is
> the same. Jitsi seems to rely on the server broadcasting back the full
> roster every time the status changes.

Eeer ... no. Jitsi does not rely on anything like this. It does however
rely on the server doing this upon every reconnect.

> We used spark before this and it
> would repopulate, which makes me think Spark requests the users roster on
> every reconnect. Openfire, I suspect, sends back the entire roster on
every
> status change.

The roster is indeed sent on every reconnect. That's standard XMPP
behaviour.

> It seems less of a bug and more of a difference of expected actions by
the
> client to the server. Either Jitsi should request the full roster on
every
> status change? Maybe just when it sees that it has network connection
again?
> I'm curious if there is a setting in ejabberd to send the full roster on
> every status change, which would probably solve this as well.

It would be good to first confirm that this is actually the problem.

Emil

>
> Caleb
>
> Damian Minkov wrote:
>
>> Hi Caleb and Sébastien,
>>
>> there is no difference when xmpp protocol provider is initially
>> registered or reconnected, we are using plugin to reconnect all
>> protocol providers which is working the same way the GUI will connect
>> the provider on startup.
>> What we do in xmpp, is when we detect the initial roster packet we
>> start initing the contacts inside jitsi.
>> Me, personally, have never seen this behaviour with openfire. It will
>> be helpful to check the logs(those including pcap) when this happens.
>> Also when this happens are the contacts there(just offline and
>> hidden), and just they are missing their available statuses?
>>
>> Regards
>> damencho
>>
>>
>> On Tue, Feb 11, 2014 at 11:14 PM, Sébastien Couture > >> <scouture@ubity.com> wrote:
>>> Hi,
>>>
>>> We've seen the same behaviour here. Although it will indeed reconnect
to
>>> the XMPP server after having lost network connectivity (or in your case
>>> the computer goes to sleep), Jitsi will not seem to retrieve its roster
>>> from the server; thus all contacts will appear offline until we
receive a
>>> presence packet following a status changes -- then, contacts will start
>>> to appear as available, or whatever their status is that triggered the
>>> presence update.
>>>
>>> The same issue arises when manually toggling between "Online" and
>>> "Offline". Jitsi will reconnect, but will not seem to retr

--

*Sébastien Couture Vice-président et chef des technologies / VP & CTO
scouture@ubity.com <scouture@ubity.com>*

Tel.: 514.907.3400 x105
Fax: 514.907.3401
*Ubity -* www.ubity.com
Technologie d'affaires IP unifiée
Unified Business IP Technology

#11

Hello,

Today I tried to reproduce the issue with the presence statuses of the contacts but everything seems to work fine. Could you please send a pcap logs to support@jitsi.org?

Thanks,
Hristo.

···

On Feb 17, 2014, at 2:36 PM, Sébastien Couture <scouture@ubity.com> wrote:

Sure, I'll do that.

Thanks.

On Monday, February 17, 2014, Emil Ivov <emcho@jitsi.org> wrote:
That's very useful. Thanks Sébastien !

Could you please open a ticket? Not sure when we will be able to have a look but I want to make sure we don't forget.

Cheers,
Emil

--sent from my mobile

On 13 Feb 2014 7:59 PM, "Sébastien Couture" <scouture@ubity.com> wrote:
Emil,

I do see a <query xmlns='jabber:iq:roster'/> IQ from Jitsi (asking for its roster) in both situations; either upon first connection after launch, or after a network connectivity loss / offline-online toggle. In both cases, the XMPP server (here, ejabberd) sends back the full roster, along with the presence of contacts that are available at that moment.

The issue is that Jitsi will somehow only display these contacts as available on the first connection, and not after a reconnect. When reconnecting, Jitsi will show these contacts as offline at first, and then display them as online only when it receives a presence update.

On Thu, Feb 13, 2014 at 12:59 PM, Emil Ivov <emcho@jitsi.org> wrote:

On Thu, Feb 13, 2014 at 6:02 PM, Caleb O'Connell <caleb@privacyassociation.org> wrote:
> I can confirm what Sébastien said in his post. A user does reconnect, and
> thus is viewable from other rosters but until a user updates their status
> they don't show up on the reconnected users roster. Either upon waking up
> from sleep mode or manually going offline then back online, the symptom is
> the same. Jitsi seems to rely on the server broadcasting back the full
> roster every time the status changes.

Eeer ... no. Jitsi does not rely on anything like this. It does however rely on the server doing this upon every reconnect.

> We used spark before this and it
> would repopulate, which makes me think Spark requests the users roster on
> every reconnect. Openfire, I suspect, sends back the entire roster on every
> status change.

The roster is indeed sent on every reconnect. That's standard XMPP behaviour.

> It seems less of a bug and more of a difference of expected actions by the
> client to the server. Either Jitsi should request the full roster on every
> status change? Maybe just when it sees that it has network connection again?
> I'm curious if there is a setting in ejabberd to send the full roster on
> every status change, which would probably solve this as well.

It would be good to first confirm that this is actually the problem.

Emil

>
> Caleb
>
> Damian Minkov wrote:
>
>> Hi Caleb and Sébastien,
>>
>> there is no difference when xmpp protocol provider is initially
>> registered or reconnected, we are using plugin to reconnect all
>> protocol providers which is working the same way the GUI will connect
>> the provider on startup.
>> What we do in xmpp, is when we detect the initial roster packet we
>> start initing the contacts inside jitsi.
>> Me, personally, have never seen this behaviour with openfire. It will
>> be helpful to check the logs(those including pcap) when this happens.
>> Also when this happens are the contacts there(just offline and
>> hidden), and just they are missing their available statuses?
>>
>> Regards
>> damencho
>>
>>
>> On Tue, Feb 11, 2014 at 11:14 PM, Sébastien Couture > >> <scouture@ubity.com> wrote:
>>> Hi,
>>>
>>> We've seen the same behaviour here. Although it will indeed reconnect to
>>> the XMPP server after having lost network connectivity (or in your case
>>> the computer goes to sleep), Jitsi will not seem to retrieve its roster
>>> from the server; thus all contacts will appear offline until we receive a
>>> presence packet following a status changes -- then, contacts will start
>>> to appear as available, or whatever their status is that triggered the
>>> presence update.
>>>
>>> The same issue arises when manually toggling between "Online" and
>>> "Offline". Jitsi will reconnect, but will not seem to retr

--
Sébastien Couture
Vice-président et chef des technologies / VP & CTO
scouture@ubity.com
Tel.: 514.907.3400 x105
Fax: 514.907.3401

Ubity - www.ubity.com
Technologie d'affaires IP unifiée
Unified Business IP Technology

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