[jitsi-dev] [solved] Re: Slow conference start/establishement with ejabberd and prosody (5 sec delay)


#1

Hi

:

Hi,

2016-02-01 17:39 GMT+01:00 Etienne Champetier <
champetier.etienne@gmail.com>:

Hi,

2016-01-29 18:36 GMT+01:00 Etienne Champetier <
champetier.etienne@gmail.com>:

Hi,

I'm trying to use ejabberd (16.01) instead of openfire, but I have a
weird 5 sec delay before each ChatRoomMemberPresenceChangeEvent, which is
killing the user experience.

Is there anyone out there using ejabberd with jitsi meet?
Does the 5 sec delay ring a bell to someone (fallback to pooling?)?

I'm currently using Openfire and this part is working well

*exemple 1:*
janv. 29, 2016 6:20:49 PM net.java.sip.communicator.util.Logger info
INFOS: Auto owner feature enabled
janv. 29, 2016 6:20:49 PM net.java.sip.communicator.util.Logger info
INFOS: Focus role: OWNER init: true
janv. 29, 2016 6:20:49 PM net.java.sip.communicator.util.Logger info
INFOS: Focus role: OWNER init: false
janv. 29, 2016 6:20:54 PM net.java.sip.communicator.util.Logger info
INFOS: Chat room event
ChatRoomMemberPresenceChangeEvent[type=MemberJoined
sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@3dbb863b
member=org.jitsi.impl.protocol.xmpp.ChatMemberImpl@6d636d56]

*exemple 2:*
janv. 29, 2016 6:30:03 PM net.java.sip.communicator.util.Logger info
INFOS: Focus request for room: fff@muc.jitsi.aaa.net
janv. 29, 2016 6:30:08 PM net.java.sip.communicator.util.Logger info
INFOS: Chat room event
ChatRoomMemberPresenceChangeEvent[type=MemberJoined
sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@3dbb863b
member=org.jitsi.impl.protocol.xmpp.ChatMemberImpl@71591d24]

Regards
Etienne

I have the same 5sec delay with prosody (0.9.9)

févr. 01, 2016 5:29:08 PM net.java.sip.communicator.util.Logger warn
AVERTISSEMENT: Presence for not existing member: <presence to="
focus@jitsi.exemple.com/focus635524651187219" from="
sss@muc.jitsi.exemple.com/8e711d0b"><c xmlns='
http://jabber.org/protocol/caps' hash='sha-1' node='fiducom'
ver='cvjWXufsg4xT62Ec2mlATkFZ9lk='/><user-agent xmlns="
http://jitsi.org/jitmeet/user-agent"></user-agent><userId
xmlns="jabber:client"></userId><nick xmlns="
http://jabber.org/protocol/nick">linux chrome</nick><devices
xmlns="jabber:client"><audio>true</audio><video>true</video></devices><videoType
xmlns="http://jitsi.org/jitmeet/video"></videoType><x xmlns="
http://jabber.org/protocol/muc#user"><item affiliation="none" jid="
8e711d0b-6d4b-4ca5-a6ef-9b91dd289d01@anon.exemple.com/0e4d13d9-ca8d-48f9-9289-7eb6d5d66414"
role="participant"><reason></reason><actor jid=""/></item></x></presence>
févr. 01, 2016 5:29:13 PM net.java.sip.communicator.util.Logger info
INFOS: Chat room event
ChatRoomMemberPresenceChangeEvent[type=MemberJoined
sourceRoom=org.jitsi.impl.protocol.xmpp.ChatRoomImpl@3380303a
member=org.jitsi.impl.protocol.xmpp.ChatMemberImpl@8c9a32d]

Am I the only one affected ?
Do i need some special prosody patch/conf?

Regards
Etienne

I'm still fighting this bug
meet.jit.si is working for me, and it's also working with openfire ...

can someone share meet.jit.si prosody config (and version)

Thanks
Etienne

Just found out :slight_smile:
I'm using strip down config and i've just removed too much modules: you
need "roster" module (at least in prosody) and no more 5 sec delay

Hope this helps someone
Regards
Etienne

···

2016-02-02 13:36 GMT+01:00 Etienne Champetier <champetier.etienne@gmail.com>