i dont know why the gojara / spectrum2 guide is currently not visible, i can press publish but it doesnt change anything. I will attach it as PDF here as long as its not visible. DOC-2601.pdf (380044 Bytes)
In case I want to provide gateways for multiple IM services like MSN, ICQ, AIM, then, shall I need to run multiple instances of Spectrum2 with configuration files for respective IM services?
e.g.
spectrum -n msn.cfg
spectrum2 -n icq.cfg
spectrum2 -n aim.cfg
Or only a single instance of spectrum2 will suffice with configuration information in a single configuration file for all the different IM services?
You create multiple configurations for multiple transports and use spectrum2_manager to control them.
“spectrum2_manager start” starts all available configuration files, “spectrum2_manager jid.yourdomain.tld start” starts only a single configuration defining its JID as jid.yourdomain.tld.
When registering with MSN transport, does the registration show up in the gojara transport overview? ( be sure to delete it if it exist before trying it out again)
Then try unregistering your credentials via your MESSENGER, not gojara admin console. After unregistering, is the registration still in the gojara overview?
Would also help me greatly if you could show me how gajim sends the unregister packet to OF, so just log the unregister process in the client.
Your problem is currently that after entering your credentials for msn, it just stays offline and does nothing until you manually set your presence to online, did i get this right?
Your registration should now get tracked properly, so register & unregister from gajim should be shown in transport overview. I dont think this affects the presence thing, but please try it out.
Concerning the presence i could probably do an extra presence push when Gojara see’s you connect via gajim packet forms, i just need to be sure it doesnt affect already working features so please try this out before we work on that
registration/unregistration works now, though it still is only reflected in the transport overview after I change my individual presence to online for the transport.
What about the presence push - how did Kraken do this? I can connect to ejabberd and openfire kraken transports without any of the problems I have with Gojara/Spectrum2.
Try the jar in this post. Also wrote you a pm Ill upload it here because i will have to go offline now. Will be back on monday / tuesday. Hope this works for you, if it still doesnt work its probably a bit more work anyways, i’ll have to think about how to include the option so its done nicely and doesnt interfere with anything else
A lot of openfire users complain about spectrum2 setup with openfire and can’t getting it work.
I have try to setup openfire and spectrum and found the problem: openfire does not push transport jid to user roster. It must be there and subscription must be approved in “both” ways, then spectrum will able to detect user connect/disconnect and sends proper presences from contacts. The only way to make spectrum work - is add spectrum jid manually.
At first, the problem is in openfire core: when user have registered on transport - transport check remote roster support by sending jabber:iq:roster request to server jid from transport jid. If server reply with error - then spectrum considers remote roster is not supported and sends subscription request to user and when user approve it - it pushed to user roster and transport will work normal. But Openfire replies with empty result, which is a **bug **- it should send an error response, because we cannot access to user roster.(See http://xmpp.org/rfcs/rfc6121.html#roster for details). Transport receive empty result, consider server is supporting remote roster and trying to push contacts directly, which doesn't work, because server reject pushes from unapproved jid. So the whole registration flow is broken: user must add transport jid to roster manually to work properly, receive tons of subscription requests from his contacts and only after that it will work more or less normal.
The second problem is gojara - it does not resolve the first problem properly
It approve somehow transport jid for roster pushes, but it should push transport jid first when user just registered. If it will do it, then “gajim workaround” will not need Anyway, this workaround works only first time, if I check “persistent roster” option, which should be default, as I think
If you have any questions - please, contact me in spectrum room.
Is this in the latest Openfire/GoJara? I never had this issue with my Openfire installation. Haven’t updated either for a while… rolled back a bit to get Twitter working again.