[How to] How do I use the new Lobby Feature?

update my jitsi to latest today, add your guide for secure domain to my lua… but no lobby option on shield icon, only setup password for meeting… is there something i miss??

very probably. Either you skimmed the post to search for requirements, however the prosody version requirement is not listed among them, it’s cited previously in the version details; or you did not update the prosody config file correctly; or you did not restart the whole thing.
If you have the correct Prosody version (0.11), restarted the computer after updating everything, and it still does not work, post your prosody config file.

my prosody is 0.11.2-1, for authentication im using ldap
after editing those thing i already restart the server.
here is my prosody conf, i change my meet server name to “myvc”

VirtualHost “guest.myvc”
authentication = “anonymous”
c2s_require_encryption = false
modules_enabled = {
“muc_lobby_rooms”;
“participant_metadata”;
}

lobby_muc = "lobby.myvc"
main_muc = "conference.myvc"

Component “lobby.myvc” “muc”
storage = “memory”
restrict_room_creation = true
muc_room_locking = false
muc_room_default_public_jids = true

Component “conference.myvc” “muc”
storage = “memory”
–modules_enabled = { “token_verification” }
admins = { “focus@auth.myvc” }

obviously that’s not your whole file, it seems that presence of lobby instructions in authenticated host can mess things.
What you are showing seems correct.
Has your prosody.log a line with

… guest.yourdomain info Lobby component loaded …

Sorry, its work now…
somehow im screwed up when creating symbolic link…

thanks for your guide…

Hi @Corby @damencho! Thank you for your hard work and bringing this new feature and this guide.

I’ve working debian stable jtisti meet installation up to date with /stable jitsi repo with secure domain enabled. I want to test lobby room, I’ve successfully enabled Lobby room feature, but accepting incoming knocking participant doesn’t work. Rejecting works fine. In dev console I’ve this warnings:

  1. when enabling Lobby room:

Logger.js:154 2020-08-11T09:41:07.591Z [JitsiConferenceEventManager.js] <a.>: Ignored XMPPEvents.JSON_MESSAGE_RECEIVED for not existing participant: migo@conference.mydomain.com/e2f6d029
{event: “LOBBY-ENABLED”, value: true, type: “lobby-notify”}
event: “LOBBY-ENABLED”
type: “lobby-notify”
value: true
proto: Object
o @ Logger.js:154
(anonymous) @ JitsiConferenceEventManager.js:379
a.emit @ events.js:152
onMessage @ ChatRoom.js:1057
onMessage @ strophe.emuc.js:155
run @ strophe.umd.js:1875
(anonymous) @ strophe.umd.js:3157
forEachChild @ strophe.umd.js:830
_dataRecv @ strophe.umd.js:3146
_onMessage @ strophe.umd.js:5836\

  1. when I click on Allow button:

Logger.js:154 2020-08-11T09:42:14.308Z [JitsiConferenceEventManager.js] <a.>: Ignored XMPPEvents.JSON_MESSAGE_RECEIVED for not existing participant: migo@conference.mydomain.com/e2f6d029
{event: “LOBBY-ACCESS-GRANTED”, value: “migo@lobby.mydomain.com/8d0fc392”, type: “lobby-notify”}
event: “LOBBY-ACCESS-GRANTED”
type: “lobby-notify”
value: “migo@lobby.mydomain.com/8d0fc392”
proto:
constructor: ƒ Object()
hasOwnProperty: ƒ hasOwnProperty()
isPrototypeOf: ƒ isPrototypeOf()
propertyIsEnumerable: ƒ propertyIsEnumerable()
toLocaleString: ƒ toLocaleString()
toString: ƒ toString()
valueOf: ƒ valueOf()
defineGetter: ƒ defineGetter()
defineSetter: ƒ defineSetter()
lookupGetter: ƒ lookupGetter()
lookupSetter: ƒ lookupSetter()
get proto: ƒ proto()
set proto: ƒ proto()
o @ Logger.js:154
(anonymous) @ JitsiConferenceEventManager.js:379
a.emit @ events.js:152
onMessage @ ChatRoom.js:1057
onMessage @ strophe.emuc.js:155
run @ strophe.umd.js:1875
(anonymous) @ strophe.umd.js:3157
forEachChild @ strophe.umd.js:830
_dataRecv @ strophe.umd.js:3146
_onMessage @ strophe.umd.js:5836

  1. Clicking on Reject button (working):

Logger.js:154 2020-08-11T09:43:06.177Z [JitsiConferenceEventManager.js] <a.>: Ignored XMPPEvents.JSON_MESSAGE_RECEIVED for not existing participant: migo@conference.mydomain.com/e2f6d029
{event: “LOBBY-ACCESS-DENIED”, value: “migo@lobby.mydomain.com/8d0fc392”, type: “lobby-notify”}
event: “LOBBY-ACCESS-DENIED”
type: “lobby-notify”
value: “migo@lobby.mydomain.com/8d0fc392”
proto:
constructor: ƒ Object()
hasOwnProperty: ƒ hasOwnProperty()
isPrototypeOf: ƒ isPrototypeOf()
propertyIsEnumerable: ƒ propertyIsEnumerable()
toLocaleString: ƒ toLocaleString()
toString: ƒ toString()
valueOf: ƒ valueOf()
defineGetter: ƒ defineGetter()
defineSetter: ƒ defineSetter()
lookupGetter: ƒ lookupGetter()
lookupSetter: ƒ lookupSetter()
get proto: ƒ proto()
set proto: ƒ proto()
o @ Logger.js:154
(anonymous) @ JitsiConferenceEventManager.js:379
a.emit @ events.js:152
onMessage @ ChatRoom.js:1057
onMessage @ strophe.emuc.js:155
run @ strophe.umd.js:1875
(anonymous) @ strophe.umd.js:3157
forEachChild @ strophe.umd.js:830
_dataRecv @ strophe.umd.js:3146
_onMessage @ strophe.umd.js:5836

Am I missing some pieces of lobby room puzzle? I’ve followed this guide for lobby room feature enable. I’ve tried to upgrade prosody to 0.11.5 but didn’t help with this problem.

Thank you for your time in advance!

Kind regards,

Milan

EDIT 12.08.2020

I’ve disabled secure domain, but still can’t accept incoming participants knocking. I’m using websockets and Jitsi meet works well besides this. Is some configuration changes needed when upgrading from older build?

Any ideas?

Thank you!

hi friend, hey what benefits does this new jitsi update bring? is that I can not find information about it.

best regards

AFAIK the most noticeable is we get easier access to switch mic and camera access on meeting, lobby support, mobile browser support (finally no apps needed on phone), and encryption support (? haven’t use it yet).

1 Like

For others that may find their way here and have the same question:

1 Like

Hi @damencho, I found reason for problem I’ve reported. When is smacks module enabled in prosody you get this erratic behavior with being not able to accept incoming participants to conference room.

Here is error log from prosody generated by pressing accept button in jitsi:

Aug 12 14:41:53 c2s55dc33a6f290 error Traceback[c2s]: /usr/share/jitsi-meet/prosody-plugins/mod_smacks.lua:442: attempt to call field ‘log’ (a nil value)
stack traceback:
/usr/share/jitsi-meet/prosody-plugins/mod_smacks.lua:442: in function ‘?’
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/modules/mod_mam/mod_mam.lua:307: in function ‘?’
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/core/stanza_router.lua:180: in function </usr/lib/prosody/core/stanza_router.lua:149>
(…tail calls…)
/usr/lib/prosody/modules/muc/muc.lib.lua:1217: in function ‘route_stanza’
/usr/lib/prosody/modules/muc/muc.lib.lua:1116: in function </usr/lib/prosody/modules/muc/muc.lib.lua:1098>
(…tail calls…)
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/core/stanza_router.lua:180: in function ‘core_post_stanza’
/usr/lib/prosody/core/stanza_router.lua:127: in function ‘core_process_stanza’
/usr/lib/prosody/modules/mod_c2s.lua:275: in function ‘func’
/usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>

Is this bug in prosody or jitsi-meet? Or is using smacks module not supported/recomended with jitsi-meet? Or is some additional configuration needed?

With smacks modele disabled lobby room works as expected.

Any ideas on this?

Thank you!

Milan

You are using this version of that module and this is prosody 0.11? https://github.com/jitsi/jitsi-meet/blob/master/resources/prosody-plugins/mod_smacks.lua
We are using them both with no problem.

Hi @damencho, yes I’m using exactly that version, had it checked right now.

-rw-r–r-- 1 root root 27643 Mar 11 15:00 mod_smacks.lua

I’ve tested default debian/stable prosody 0.11.2 and upgraded 0.11.5, result is the same. :frowning:

Any ideas what can cause it?

Thank you for your time,

Milan

Do you use that? Can you disable it and try without it?

1 Like

thks my friend

thks my friend for helpme

Hi @damencho, thank you for investigating on it.

Yes, I confirm that disabling mod_mam resolved this issue for me. mod_smacks can be enabled now with lobby room feature.

Is your prosody config secret/proprietary? Maybe publishing that can save some problem like this.

Thank you very much for your help.

Milan

thx its working
btw how to set it default to enable ?

Well I don’t think it differed a lot from the defaults, we try to keep them in sync.

There is no such option.

Thank you for info that makes sense. Module smacks is disabled in default prosody config so I was curious if you use some special/tested parameters for this module that can help jitsi-meet.

Thank you,

Milan