To update: the configuration of prosody that is v0, v1 and so on can be seen here: https://github.com/jitsi/jitsi-meet/blob/master/resources/extra-large-conference/prosody.cfg.lua.visitor.template
And the configuration of the main prosody is mentioned here: https://github.com/jitsi/jitsi-meet/blob/master/resources/extra-large-conference/README.md The modules about s2s that are enabled are: "s2s_bidi"; "certs_s2soutinjection"; "s2soutinjection"; "s2s_whitelist"; Thanks On Tuesday, May 23, 2023 at 5:37:53 PM UTC-5 Damian Minkov wrote: > Hey all, > > How does s2s works, isn't it supposed to have one connection per host pair? > > # prosodyctl shell "s2s:show()" | wc -l > 461 > > # prosodyctl shell "s2s:show()" > Session ID | Host | Dir | Remote > | IPv | Security | SASL | Dialback > s2sin5558e296def0 | meet.jit.si | <-> | > conference.v0.meet.ji… | IPv4 | TLSv1.3 | Succeeded | Not used > s2sin5558e3a52aa0 | meet.jit.si | <-> | > conference.v0.meet.ji… | IPv4 | TLSv1.3 | Succeeded | Not used > s2sin5558e2bce550 | meet.jit.si | <-> | > conference.v0.meet.ji… | IPv4 | TLSv1.3 | Succeeded | Not used > > And so on, almost the whole list is like that. Is this leaking the > connections? Any idea what can be the reason for that? > > Thank you > > -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prosody-dev/f10171f6-3561-4d96-ba9b-695e7772cfd6n%40googlegroups.com.
