Bug 110402 - SIP/SIMPLE Support for use with MS Live Communications Server
Summary: SIP/SIMPLE Support for use with MS Live Communications Server
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kopete
Classification: Applications
Component: New plugin wishes (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 156657 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-08-08 18:07 UTC by Bill Lewis
Modified: 2019-12-16 06:15 UTC (History)
30 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bill Lewis 2005-08-08 18:07:12 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages

I am often finding the need to connect to Microsoft Live Communications Server (SIP/SIMPLE).  It would be great if I could use Kopete to connect to these servers.
Comment 1 Matthias Granberry 2005-09-06 20:47:55 UTC
Has anyone actually given any thought to incorporating SIP into
Kopete?  The smallest SIP stack I've seen is about 400k, while the
horribly unfriendly dissipate stack (in kphone/kcall) clocks in at
about 500k.  For flexible and compliant stacks, about 1M is the
smallest code size I've seen.  How much is too much for one protocol?

On 8 Aug 2005 16:07:13 -0000, Bill Lewis <bill@enobis.com> wrote:
[bugs.kde.org quoted mail]
Comment 2 Matthias Granberry 2005-09-06 21:06:02 UTC
This is not MSN.  He's referring to the SIP MESSAGE method, which is the basis for the 3GPP IMS messaging among other things.  There are also standards for most of the familiar IM goodies like presence, etc in the pipeline or standardized.  As a bonus, Google Talk sounds like it will support SIP for voice communication, so it might not be an entirely wasted effort.

RFCs 3261, 3428, and 3856 are particularly relevant.
Comment 3 Ralf Holzer 2006-01-26 23:46:35 UTC
This would be a great feature, there is not a single client for LCS under Linux. In addition to SIP/SIMPLE it would require NTLM and TLS support as well to work with LCS.
Comment 4 Sven Boden 2008-01-25 19:33:25 UTC
*** This bug has been confirmed by popular vote. ***
Comment 5 Matt Rogers 2008-01-26 15:39:36 UTC
*** Bug 156657 has been marked as a duplicate of this bug. ***
Comment 6 Mike 2008-02-09 08:30:52 UTC
This is a much needed protocol and could really help boost Kopete usage since a lot of corporate environments run LCS and the only way to connect to it is with a crappy Windows client or crappier web-based client.  
Comment 7 arnaud 2008-05-05 21:34:01 UTC
As many Linux user with Microsoft IT, I'd like to be connected with my collaborators with outside windows.
Does it planed to fixed it or not?
I'm more Java programer than C/C++ one and don't known KDE, but let me known if can help.
Comment 8 Mike 2008-05-27 00:18:56 UTC
If you are interested in seeing this request move forward, please vote for it. There is also a pidgin plug-in for LCS connectivity (http://developer.pidgin.im/ticket/48) but it is not finished (TLS support is not implemented) so it won't work with many LCS servers (including the one I have to connect to). 

Mike

Comment 9 Olivier LAHAYE 2008-06-03 16:02:06 UTC
This much needed feature would greatly help kopete to gain popularity within corporate environments.
I can test if needed.
Comment 10 Andres Hans 2008-06-05 13:39:38 UTC
This would be a great feature, many linux users have to use a completely crappy, near useless web client
Comment 11 Jeremy Guthrie 2008-07-16 06:56:43 UTC
I have to echo above peoples comments.  It is actually pretty silly that SIP/SIMPLE w/ TLS isn't supported.  If this is meant to supplant other IM clients from an OSS perspective than Kopete really must tackle the bastardized MS implementation of SIP/SIMPLE but w/ TLS support.
Comment 12 Kevin Myers 2008-07-18 15:46:03 UTC
It seems that a majority of LCS servers require TLS.  Most IT shops that are swayed by MS are running LCS, and not being able to connect via Linux IM is just one more reason the big-bosses see a delay in migrating to Linux.

Comment 13 Carsten Schlipf 2008-09-02 13:34:33 UTC
I also would like to see support for MS LCS, but I am very pessimistic about that. Excerpt from http://www.informationweek.com/news/showArticle.jhtml?articleID=53700175:

"How is Microsoft hijacking SIP/SIMPLE? Start at the client-to-server side, the protocol exchange between the Windows Messenger or Microsoft Istanbul clients, and an LCS server. The SIP/SIMPLE protocol currently has some limitations when it comes to IM, particularly when it comes to buddy list management, so Microsoft has gone to great lengths to fill in the functionality gaps by implementing their own protocol payload and exchange sequences. While this may fill in the gap left by the fact that SIP/SIMPLE is still being developed, and while it may improve the available feature set, these extensions are Microsoft's intellectual property. That means they must be licensed by any third-party that wants to have access to them in an official manner."
Comment 14 Jiri Navratil 2008-09-17 13:34:19 UTC
Could http://sipe.sf.net/ help there?
Comment 15 Matt Rogers 2008-09-18 01:59:11 UTC
yes and no. It might be a good base, but when I tried it with pidgin, it didn't work. and now that LCS 2007 is out there as well, we'd still have things to implement.

However, none of that matters unless there's somebody willing to work on it.
Comment 16 Jeremy Guthrie 2008-09-18 18:42:28 UTC
People should still add their points to this issue.  FOSS needs to address business solutions and not just 'fun' things.  In any case, if it is ignored we may have some other escalation we can go down to get attention to it from the larger KDE community.
Comment 17 emacsian 2008-09-25 17:41:37 UTC
The NTLM and SIP LCS specs are now open at
NTLM - http://msdn.microsoft.com/en-us/library/cc207842.aspx and
SIP Extensions - http://msdn.microsoft.com/en-us/library/cc246115.aspx
Comment 18 Mike 2008-11-03 20:32:34 UTC
Hi, everyone. It looks like this issue is finally gaining some traction with Pidgin. You might want to check their bug tracker (http://developer.pidgin.im/ticket/48) to follow the progress and see if there is anything you can to do help if you are interested. 

Mike
Comment 19 Molly 2008-11-18 16:07:49 UTC
Proprietary protocols make raptor Jesus cry.
Comment 20 Mike 2008-12-22 23:02:21 UTC
Terrific news. The there is finally a very usable version of the Pidgin plug-in. Check it out! http://sourceforge.net/projects/sipe 

The forum is quite active with lots of information and people to answer questions if needed. http://sourceforge.net/forum/forum.php?forum_id=688534

Mike
Comment 21 arnaud 2009-01-02 23:29:52 UTC
I test is and it works fine for me with a LCS 2005.
Sorry Kopete, I will Pidgin :-$ what ever it is not KDE flavor
Comment 22 Kanwar Plaha 2009-04-20 08:03:25 UTC
I want to vote for this feature to be added to Kopete.
Comment 23 Jonathan 2009-08-19 23:07:35 UTC
for information, with http://sipe.sourceforge.net and pidgin, i can connect with TLS and Kerberos to our LCS-Server (2007??). Unfortunately i don't like pidgin
Comment 24 Alexandre NEY 2009-10-11 23:17:34 UTC
Hey guys !

I've seen the pidgin plugin in action and it works great !

Kopete just NEEDS this kind of plugin for corporate environments where quick chats are taking over useless amounts of emails.

Thank you for your very much appreciated work !
Comment 25 Marcelo Bossoni 2009-12-18 19:45:06 UTC
Voting for this bug, since I think that Kopete should offer something to be used to corporate users (and I prefer Kopete).
Comment 26 Kanwar Plaha 2010-03-25 03:44:43 UTC
echoing sentiments of earlier posters for this bug, i want to re-iterate that although pidgin does just fine with MS OCS/LCS, a kopete plugin would be preferred ... especially for KDE users since it integrates into the desktop, including Kickoff and Lancelot menus.

Please bump this up.
Comment 27 Mathieu Jobin 2010-03-25 13:12:56 UTC
Microsoft Live Communications Server actually use a different version of SIP.

We kindly call it SIPE ! 
there is a pidgin plugin for it. 
you might want to integrate it into kopete? it would be nice.

I personnaly use pidgin stritly for this protocol and kopete for everything else.

http://sipe.sourceforge.net/
Comment 28 Anibal Avelar 2010-03-29 07:47:37 UTC

I'm the SIPE author plugin.

The SIPE plugin was developed originally for pidgin using purple/glib libraries.

But now we have removed all purple libraries from the core source.

I mean, if you want to implement in another language, I think should more or less easy.

Check the git repository for that:

http://repo.or.cz/w/siplcs.git

I love kopete too, if I developed to pidgin, just was due to was easy and there was a plugin called SIMPLE for that (I based my original work on that).

I don't know, may be I can help you if you want. ;)


Regards.
Comment 29 Matt Rogers 2010-03-29 21:23:47 UTC
even better would be to write a telepathy connection manager instead. :)
Comment 30 Anibal Avelar 2010-03-30 02:48:01 UTC

Indeed, It's almost done. We are working in the telepathy support for our plugin SIPE.

Today works using telepathy-haze, but we want to work natively 

;)

Regards.
Comment 31 Stefan Becker 2010-04-18 02:34:53 UTC
Anibal was a little bit too enthusiastic.

Yes - work is ongoing to separate the Sipe core functionality from the Purple code. We're still in the middle of it and don't know when it will be completed.

No - there is no native telepathy backend yet, just a build option and an empty directory. Once the above is achieved it should be technically possible to implement a native telepathy backend. If you want to connect to M$ OCS with a telepathy-based client *today*, you'll need to use telepathy-haze.

Of course the same thing is true for a native kopete backend. As none of the current Sipe developers knows anything about developing kopete protocol plugins it would be nice if someone from the KDE/kopete community would step up and start contributing code to the project.

To start this off I could add a --enable-kopete option to configure and a kopete directory to the source tree. What kind of libraries/packages would configure need to check for to be able to compile a kopete protocol plugin? [e.g. for telepathy we check for telepathy-glib development headers]
Comment 32 Stefan Becker 2010-04-18 02:48:57 UTC
--enable-kopete build option & empty directory have been added in git commit adc47b8.
Comment 33 Vincent Fortier 2010-10-08 15:20:34 UTC
Sadly farther KDE is from integrating MS protocols, farther will it stay from the desktop market... same goes into supporting MS Exchange in kontact/kmail/korganizer/etc (bug #78629) ....  

Hoping either 1) KDE finally integrates a bit better with MS products OR 2) MS products stops being the default enterprise solution... I'd hope for 2) to be true soon but I think I have more chances in hoping for 1) to become a reality first....
Comment 34 Matt Rogers 2010-10-08 15:29:59 UTC
Somebody has to be willing to put in the work to make the integration happen
though. Until that happens were all in the same boat