dkliss
commented
1 year ago After looking further in the documentation, found a note: "If subscriber is subscribed to node urn:xmpp:mucsub:nodes:subscribers, message will be sent for every mucsub subscription change. When a user becomes a subscriber:". This is the approach used i.e. if a new room is created (example mucSubRoom) a "subscribe" message is issued by the server (instead of roster push). Therefore, this does seem to be an issue related to the server & hence closing.
Hi,
In the link below on MucSub, if a muc room is subscribed, no roster push is currently received. That means, one has to fetch rooms from server.
https://docs.ejabberd.im/developer/xmpp-clients-bots/extensions/muc-sub/
What I was expecting is a "roster push" stanza like below sent from server, when a new room (example mucSubRoom) is created. If there is any other way to auto update roster without a roster push, please advice.
iq to='testuser@server.com/295389b0-e966-11ed-b798-c91f4f94ebbf' from='testuser@server.com' type='set' id='push2926847785642867526'><query ver='70c88fcd070f62c3b9329cc5595f28cbcf4208d8' xmlns='jabber:iq:roster'><item subscription='none' jid='mucSubRoom@conference.server.com'/></query></iq>Any suggestions are appreciated?
Before creating a ticket, please consider if this should fit the discussion forum better.
Environment
erl +VConfiguration (only if needed): grep -Ev '^$|^\s*#' ejabberd.yml
Errors from error.log/crash.log
No errors
Bug description
Please, give us a precise description (what does not work, what is expected, etc.)