4 pidgin-sipe is a third-party plugin for the Pidgin/Adium/Miranda/Telepathy
5 multi-protocol instant messaging clients/frameworks. It implements the
6 extended version of SIP/SIMPLE used by various products:
9 * Microsoft Business Productivity Online Suite (BPOS)
10 * Microsoft Lync Server
11 * Microsoft Office Communications Server (OCS 2007/2007 R2)
12 * Microsoft Live Communications Server (LCS 2003/2005)
15 With this plugin you should be able to replace your Microsoft Office
16 Communicator client with Pidgin/Adium/Miranda/Telepathy.
22 The plugin has support for
24 * Instant Messaging (IM)
26 * Group (Lync 2010) or Persistent (Lync 2013) chat
28 * Calendar integration with Exchange 2007/2010
29 * Contact details information - company, phones, web site, etc.
30 * Contact search - [MS-PRES] and [MS-DLX] methods supported
31 * Encrypted file transfer
32 * Call initiation through PBX
33 * NTLMv2, Kerberos & TLS-DSK authentication support
34 * TLS encryption support
35 * Translated to many languages
37 The plugin has backends for
39 * Pidgin/Finch (libpurple)
42 * Telepathy (under development)
44 Advantages over Office Communicator products
45 ============================================
47 * Available on broader range of platforms: Linux, *BSD, Maemo, OSX,
48 commercial UNIX, Windows.
49 * Ability to simultaneously connect to several Office Communicator
50 accounts in addition to public IM network accounts like MSN, AOL,
51 Yahoo. For example one account is in vendor company and another is
53 * Keeps history of communications in environments without Outlook. For
54 example in companies where Lotus Notes is deployed as a default
55 groupware client instead of Outlook.
56 * Lotus Notes/Domino calendar integration. Unique to SIPE.
57 * Open development model, open source product. License is GPLv2+
63 The Pidgin project does not support third-party plugins! If you have problems
64 with this plugin then please check out the support forums:
66 http://sourceforge.net/p/sipe/discussion/
68 Bugs should be reported here:
70 https://sourceforge.net/p/sipe/bugs/
76 SIPE has already been localized for several languages. You can help to
77 translate SIPE to your native language at Transifex:
79 https://www.transifex.com/projects/p/pidgin-sipe/r/mob/
81 The service offers a convenient web editor and automatic submission to the
85 Installing from a distribution repository
86 =========================================
88 Many Open Source OS distributions have a ready-made package "pidgin-sipe".
89 Before trying to compile it from the source code yourself, you should try
90 to install this package with the standard installation method provided by
94 Do It Yourself I: compiling against "pidgin" package
95 ====================================================
97 If you already have installed the "pidgin" package from your distribution
98 repository and want compile pidgin-sipe from source code yourself, then you
99 need to install the necessary headers first. Depending on your distribution
100 you'll need to install one of the following packages
105 For the compilation you'll need to install a C compiler and some of the
114 libgmime-2.4-dev (optional)
115 libgmime-2.6-dev (optional)
121 gmime-devel (optional)
123 You have to choose between NSS or OpenSSL for the crypto backend. You'll
124 need one of the following packages
135 If you want to enable Kerberos authentication support then you'll need one
136 of the following packages
141 If you want to enable Voice & Video features then you'll need some of the
144 libnice-dev (>= 0.1.0)
147 libnice-devel (>= 0.1.0)
150 Now you should be able to compile the source code with
152 ./configure --prefix=/usr
155 If you get errors then you are missing some required package. After
156 successful compilation you can install pidgin-sipe with:
160 If you get errors from configure or libtool about version conflicts then
161 you need to regenerate the autoconf files. You'll need these additional
167 Now you should be able to regenerate the files with
169 autoreconf --verbose --install --force
171 After that go back to the configure step above.
174 Do It Yourself II: compiling against self-compiled pidgin
175 =========================================================
177 If you have compiled pidgin from source code yourself then you'll have to
178 specify the correct installation path in configure. Usually pidgin is
179 installed in /usr/local so the following command should work
181 ./configure --prefix=/usr/local
183 The rest of the steps are the same as in the previous section.