« Fahrenheit 9/11 | Main| Rumour central »

IM gateways, client integration...

Category

There's been a lot of discussion lately in the press, blogs and partner forums about the Microsoft announcement concerning IM interoperability.  I see this announcement as a good thing for all companies inolved with or using Instant Messaging.  From what I can tell the Microsoft solution will be a gateway interface, based around SIP but probably based around Microsoft's 'enhanced' SIP standard.  Yes they have already started to 'enhance and embrace' the SIP/SIMPLE protocol.

The gateway approach is the correct approach to take.  Client integration is fine, but typically requires users having a personal login to the other system, and corporations never really liked the idea of their employees using names like bigboy27 to chat with customers.  There are ways you can control this obviously, with products like IMtegrity which does Sametime and AOL chat logging/archiving and allows you to control who in your organisation can use AOL, so you can make sure they are only using an approved name.  If the IM gateways are done correctly, users will have a single logon to one system and gain access to the other systems without requiring logins for each individual user, another benefit of the gateway approach for an organisation is that they can lock down their firewall much more.

IBM has offered their SIP gateway for Sametime since 2.5, but the first couple of versions were very buggy and no one deployed them, in fact today many companies still haven't done much more than install it to see what it does.  The funniest thing that I come across with companies, is that they want to chat with IBM using SIP, but IBM hasn't implemented the SIP gateway, so most people that chat with IBMers over IM are using AOL.  If IBM implemented a SIP gateway for their Sametime infrastructure, I am sure you would see most IBM partners and customers setting up their own SIP gateways.

One thing that does become clear with all these systems finally starting to talk to each other, you unique ID, typically your email address is going to start getting used for much more than just email.  You email address will become your IM ID, your VoIP ID, your signon name, etc.

Comments

Gravatar Image1 - I fully agree with your assessment of connecting to IBM via IM. AIM is it today as 1) an IBM SIP server isn't available and 2) AIM is an aggregating point of IM services across companies.
.
Has anyone given thought to how the SIP gateway approach will 'scale' as companies want to connect to many vendors/clients?

Gravatar Image2 - I must agree with the point that this is a good thing. M$ announcing the SIP/SIMPLE based integration (even if they had to go and alter the standard ) will assist in the spread of corporate gateways for IM. I hope more companies start to look at this as a business solution. I must say I have been a fan of the SIP solution for a long time now. I even supplied an open sip gateway (http://sip.pmooney.net) for anyone to test off. Not many takers. Only one customer site of mine connects via SIP to my company and its been an excellent service for all. Your email address is your corporate identity, all chats are logged and secure and there is no chance of SPIM or the IM viruses.

Give me a few drinks and I start on IPv6 and how everyone has their IP address which is tied to their email / phone / Social security number etc etc.


Post A Comment

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