Problem with movim client

Hi guys! I have a problem with the movim client working with openfire 4.7.5! In general, the chats themselves work, the history is synchronized, but when I try to enter a group room in the xmpp logs on the movim side I see the following:

<iq xmlns="jabber:client" from="andrei.muzalev@rlspb-dc/movimQ8DGEN" type="set" id="Qro7WI"><pubsub xmlns="http://jabber.org/protocol/pubsub"><publish node="urn:xmpp:bookmarks:1"><item id="itteam@conference.rlspb-dc"><conference xmlns="urn:xmpp:bookmarks:1" name="itteam" autojoin="true"><nick>andrei.muzalev</nick><extensions><notifications xmlns="xmpp:movim.eu/notifications:0" notify="quoted"/><pinned xmlns="urn:xmpp:bookmarks-pinning:0"/></extensions></conference></item></publish><publish-options><x xmlns="jabber:x:data" type="submit"><field type="hidden" var="FORM_TYPE"><value>http://jabber.org/protocol/pubsub#publish-options</value></field><field var="pubsub#persist_items"><value>true</value></field><field var="pubsub#access_model"><value>whitelist</value></field><field var="pubsub#send_last_published_item"><value>never</value></field><field var="pubsub#max_items"><value>max</value></field><field var="pubsub#notify_retract"><value>true</value></field></x></publish-options></pubsub></iq> sent to XMPP
ноя 08 13:20:20 rlspb-movim movim[12320]: NrcvdqGAbOjKzJPGDBSRuED3cHC8yMuR : <presence xmlns="jabber:client" from="andrei.muzalev@rlspb-dc/movimQ8DGEN" id="X1SM3w" to="itteam@conference.rlspb-dc/andrei.muzalev" type="unavailable"><c xmlns="http://jabber.org/protocol/caps" hash="sha-1" node="https://movim.eu/" ver="mmXSnlVhLNtV3HzO4hBramTOlFU="/></presence> sent to XMPP

the room was previously created. as far as I understand, he tries to add it to the pubsub bookmarks, and then immediately leaves the room, as a result of which it is not displayed in the list.
What is strange is that the request does not contain the pubsub service address, it should be like this - pubsub.rlspb-dc
Also, if you go to the movim settings, the following will be written:
Your server doesn’t support XMPP Pubsub persistence or the social features (communities, news feed and profile) are disabled by the administrator.
I did not find many messages on the Internet that the Openfire server does not support working with movim.

Openfire version 4.7.5.
xmpp domain - rlspb-dc.
All DNS records are correct, the SRV record has also been created.

I remember fixing some Movim-specific issues in Openfire in the last months. Openfire 4.7.5 is pretty old. Can you please test with the latest release, to see if things are better with that version?

I tried it, but overall nothing changed. When I try to enter a group room, the logs are the same. I’ll also note that no user avatars are displayed (I don’t have user avatars, but as far as I understand, movim should generate some default images, for example, based on the user’s initials, and store this in pubsub, but this does not happen.

Version 4.9.2

@casdanic: About Avatar (and vCard), it is about missing XEP supports in Openfire:

@guus: XEP-0084: User Avatar is not in Openfire .doap file, it is supported?

XEP-0153: vCard-Based Avatars is supported? It is in .doap file but not sure:

XEP-0292: vCard4 Over XMPP is not supported

Not clear for: XEP-0398: User Avatar to vCard-Based Avatars Conversion, it is in .doap file (no XEP version) and docs but it is really supported, if yes what version?

XEP-0486: MUC Avatars is not supported:

@guus: Can you create a new ticket in bug tracker for “XEP-0292: vCard4 Over XMPP” and another one for “XEP-0486: MUC Avatars”?

Can you verify for XEP-0084, XEP-0153, XEP-0398 and latest version?

Gajim/Movim/Prosody/Psi/Psi+ have XEP-0292 support.
Dino/Monal IM/Psi/Psi+ have XEP-0486 support.

Thanks in advance.

Not that this is relevant to the author of the this issue question(i dont think it is related). But no Openfire doesn’t support yet XEP-0398, i think it does support XEP-0153(not sure which version), and it does support XEP-0084(again not sure to what version). That being said, Some issues with the avatar were already documented Openfire - Issues - Ignite Realtime Jira.