Ok, I've been trying to work out how to test, validate, configure the xmpp messenging support with Continua and failing badly.
I had a good look at http://en.wikipedia.org/wiki/Compar...ng_clients (I even edited that page to include more up-to-date information on Microsoft Live Messenger), but it hasn't got me closer to a practical implementation.
I have the following messaging options all with very different credentials.
Google talk (Google apps run our domain communication).
Skype
Live Messenger
Microsoft Lync (corporate, for linking into some customers)
However, I'm kind of getting frustrated at running all these messaging clients at the same time. Any help would be appreciated. I'm assuming that Continua publishes messages via XMPP and still needs to connect to the appropriate messaging service servers. Is that correct.
I know each of these providers have different standard ports for communication, compared to port 5222 that's configured. Now I look at this there are multiple firewalls between continua and the internet, which might be the problem! DOH.
Could we have a validate button where XMPP ID's are getting set, so we can confirm they are working? Cheers.
When configuring XMPP, should we be creating a "CI server" account for publishing, or should it come back to a know person managing Continua?
Continua CI 's XMPP support connects directly to the XMPPServer, it doesn’t need a client installed. Vinnie has started working on a validation button for that page… might take a few days though as the whole messaging architecture is queue based so it’s not a simple change.
I would recommend creating an account for the CI Server. We are using OpenFire here internally and it’s been very reliable - http://www.igniterealtime.org/projects/openfire/ I’m not sure what other XMPP servers were tested with, I suspect we may still have some work to do with other XMPP servers as the XMPP spec seems a bit loosy goosy and not all servers are implemented equally.
Looks like we will have to do some more work to support messenger. We only have support for user/password authentication at this time. I’ll add a task for us to look at supporting messenger but it won’t happen until after v1 is done. I had a quick look and the xmpp client library we are using (jabber-net) doesn’t support messenger and the project seems dead, so this will involve us rewriting our xmpp support with another library. From memory there’s not a lot out there, and only decent one I found is ridiculously expensive (EUR1200 per developer), not a cost I’m willing to absorb at this time.
XMPP validation button is available now (thanks Build 889). I’m struggling to find my Microsoft live messenger jabber ID, with the API’s that have been created for those new XMPP services. Looks like that’s going to be part of the Windows phone/tablet/desktop/everywhere strategy to communication between all the devices. I’ve ask the question on the support forum, so hopefully a smarter man than me who can supply the information without me resorting to programming. http://social.msdn.microsoft.com/Forums/en-US/messengerconnect/thread/e091da34-17b4-4d16-a880-41f9482a7cfe
The validation message I get includes “time-out after 10 seconds” with my XMPPID. I’m going to assume that there are some firewall ports that will need to be opened to help allow the validation process to complete correctly. Is it just a case of opening port 5222 through server and router?
It should just need the xmpp server port opened. Which xmpp server are you using? As I mentioned before, we need to do a lot more work before live messenger can be supported. I would also try using another xmpp client like pidgeon and see if that can connect to the server.
