Sure, I'll do that.
On Monday, February 17, 2014, Emil Ivov <firstname.lastname@example.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.
--sent from my mobile
On 13 Feb 2014 7:59 PM, "Sébastien Couture" <email@example.com> wrote:
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 <firstname.lastname@example.org> wrote:
On Thu, Feb 13, 2014 at 6:02 PM, Caleb O'Connell <email@example.com> 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.
> 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?
>> On Tue, Feb 11, 2014 at 11:14 PM, Sébastien Couture > >> <firstname.lastname@example.org> wrote:
>>> 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
Vice-président et chef des technologies / VP & CTO
Tel.: 514.907.3400 x105
Ubity - www.ubity.com
Technologie d'affaires IP unifiée
Unified Business IP Technology
users mailing list
Unsubscribe instructions and other list options: