Pidgin protocol plugin for Office Communicator 1.9.0-1maemo1

Adds support to connect to Microsoft Office Communicator A third-party plugin for the Pidgin multi-protocol instant messenger. It implements the extended version of SIP/SIMPLE used by various products: * Microsoft Office Communications Server (OCS 2007/2007 R2 and newer) * Microsoft Live Communications Server (LCS 2003/2005) * Reuters Messaging With this plugin you should be able to replace your Microsoft Office Communicator client with Pidgin.
Homepage:
http://sipe.sourceforge.net/
Section:
user/network
Repository:
Fremantle Extras-testing free armel
Maintainers:
Stefan Becker
Depends:
libc6 (>= 2.5.0-1), libgcc1 (>= 4.2.1), libglib2.0-0 (>= 2.20.0), libpurple0 (>= 2.6.0)
Size:
175808 bytes
MD5sum:
306fb22f918851a5e1ccb46618a4726a
File:
pidgin-sipe_1.9.0-1maemo1_armel.deb
Source:
pidgin-sipe 1.9.0-1maemo1
Status:
Old version cleaned by repository management
Bugtracker:
Report a bug in this project's bugtracker
QA Quarantine ends:
ENDED 2010-03-20 10:15
Packages depending on this package:
account-plugin-haze-sipe
TesterKarmaTimestamp
Roland Canimo (11)
2010-03-12 13:48 UTC
Stefan Becker (Maintainer) (89)
2010-03-10 11:01 UTC

Package events

Event typeUserTimestamp
Old version cleaned by repository managementSystem2010-04-07 13:09 UTC
Package is in testingSystem2010-03-10 10:15 UTC

Comments:

1 2 3 4 next »
Roland Canimo
Roland Canimo
Karma: 11

I was able to make this work!!!! This is EXCELLENT!!! Thank you!

2010-03-12 13:48 UTC
Stefan Becker
Stefan Becker
Karma: 89

Another problem that can trip you: OCS might be set up to reject non-M$ clients. Pidgin will show an error message if this is the case.

Please check the support forums on the home page for suggested User Agent values to fake a M$ client :-)

2010-03-12 08:05 UTC
Stefan Becker
Stefan Becker
Karma: 89

Unfortunately there are many ways how M$ LCS/OCS can be set up for your company. Most often your account details are:

Username: first.last@company.com (i.e. your email address) Login: Windows-Domain\Window-Account Password: Windows Domain Password

Please check out the support forums on the home page. There are many tips available:

  • One way to discover the correct account details is to look at the log of the M$ OC client
  • Server autodiscovery might not be set up in your company. The M$ OC log should show you which server to connect to. In many cases it has been ocs.company.com or sip.company.com.

  • Stop Pidgin, open an X Terminal and run

    pidgin --debug >pidgin_debug.log 2>&1

The log file will show what actually goes wrong in your case. If you think this is a bug then please report it to the project and provide the log.

2010-03-12 06:50 UTC
Roland Canimo
Roland Canimo
Karma: 11

This would have been really really great... but for some reason, I am not able to connect. :(

2010-03-11 20:20 UTC
1 2 3 4 next »

Comments:

You must be logged in to make comments.