Search

Languages

Other languages on request.

About Me

I am the "Lotus Technology & Productivity Advisor" for IBM Asia Pacific. I'm based in Singapore.

Ads by Google

Visitors

« Explaining the human condition to an eight year old | Main| Spreading the love »

Connecting Sametime to MSN

Disclaimer: The following considerations are hypothetical and are nothing IBM does recommend, support or implement. This are purely my little musings how something eventually could be done if someone would really want to. It also is a technical musing only and anybody acting on this musing better should study MSN's usage agreement and have a word with their lawyers.

So let us begin....
The Sametime gateway that connects a Sametime server to AIM, Yahoo or Google does currently not connect to MSN. This is not a technology shortcoming but the lack of a federation agreement between IBM and Microsoft. This post is no place to speculate who's fault that is. At the core of the problem is federation. When you use Sametime you have one identity, that makes you visible in all networks. Using a client side solution like Pidgin, Digsby, Adium, Trillian or others requires an account with each chat provider. Also it requires your firewall to be open for all these protocols for all workstations. Furthermore you won't be able to have a central logging facility which is a compliance and audit requirement in a lot of industries.
The solution approach: If Sametime traffic could run through something that handles the transition between federation and individual accounts it might do the trick (Important: this is a technical, not a legal statement!). Enter XMPP. The Sametime 7.5.1 gateway could connect to GTalk which is XMPP based. The Sametime 8.0 gateway can connect to any XMPP based server (however there is no ibm-supports-the-following-smpp-servers list). If that XMPP server connects to MSN using MSN IDs a Sametime user can talk to an MSN user. For the MSN user it will look like an MSN account (I once registered my passport account using a regular email address, so it doesn't need to be joe@msn.com or paul@hotmail.com, it can be peter.pan@disney.com). It would work somehow like that:
TiagaseMSN.png
I spoke to Artur Hefczyc from the Tigase project. He confirmed that Tigase has a working MSN transport and that he would work with anybody to get that working. Since Tigase is an open source project, he needs to be paid for that work.

Update: Fixed the X vs. S typo.

Comments

Gravatar Image1 - I believe you meant XMPP, not SMPP.

SMPP is a standard for telcos to do SMS delivery between service centres. Emoticon

Sorry to make you need to change your otherwise beautiful and insightful architecture diagram. Emoticon

Gravatar Image2 - Thanks, Stephan, this is important. It's inevitable that customers who use the ST Gateway will need to include MSN clients.

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::rolleyes:;-)

Disclaimer

This site is in no way affiliated, endorsed, sanctioned, supported, nor enlightened by Lotus Software nor IBM Corporation. I may be an employee, but the opinions, theories, facts, etc. presented here are my own and are in now way given in any official capacity. In short, these are my words and this is my site, not IBM's - and don't even begin to think otherwise. (Disclaimer shamelessly plugged from Rocky Oliver)

© 2003 - 2009 Stephan H. Wissel - all rights reserved as listed here: Creative Commons License
Unless otherwise labeled by its originating author, the content found on this site is made available under the terms of an Attribution/NonCommercial/ShareAlike Creative Commons License, with the exception that no rights are granted -- since they are not mine to grant -- in any logo, graphic design, trademarks or trade names of any type.

Get Firefox Use OpenDNS