Thread: Office Communicator OCS on Maemo Conversations
View Single Post
otto is offline otto
2010-12-29 , 12:05
Posts: 8 | Thanked: 10 times | Joined on Aug 2010
#1
I managed to get OCS working on maemo conversations. I tried to search this forum for instructions and I didn't find any so I decided to post my workaround for OCS. The main issues were that OCS was missing from account list and Maemo conversation doesn't prompt for incoming certifications and they have to be added manually. So all you need to do is create a OCS profile determine what certifications you are missing.


-------------------------------------------------------------------------------------

First of all, I started by downloading latest versions of these packages:
http://maemo.org/packages/view/account-plugin-haze/
http://maemo.org/packages/view/telepathy-haze/
http://maemo.org/packages/view/pidgin-sipe/

Saved them to /home/user/MyDocs/ocs/ and run
Code:
dpkg -i /home/user/MyDocs/ocs/*.deb
as root

EDIT: You can also install these from maemo-extras repositroy alternatively:
* Pidgin protocol plugin for Office Communicator
* Pidgin protocols plugin for Conversations and Contacts


Then, with help of Palko Jukka, I created file /usr/share/osso-rtcom/sipe.profile
Code:
[Profile]
Manager = haze
Protocol = sipe
IconName = sipe
DisplayName = Office Communications Server (OCS)
ConfigurationUI = haze-plugin
Capabilities = chat-p2p, chat-room, contact-search, supports-alias, supports-avatars, supports-roster
VCardDefault = 1
VCardField = X-SIPE
SupportedPresences = offline,available,away,hidden,do-not-disturb
After the sipe.profile was created, I was able to see OCS profile at my accounts list. I added OCS account with information:
username: firstname.surname@comapany.com
login: domain\username
password: ********
server: sip.company.com:443
Connection type: auto
User agent: SIPE/1.11.2

Find out your SIPE version:
Code:
 dpkg -l pidgin-sipe | grep sipe
Mine was:
ii pidgin-sipe 1.11.2-1maemo1

(With my companys configuration this User Agent was accepted. Some of ocs servers doesn't accept other that M$ clients, so in that case user agent has to be faked)

At this point I was not able to log in. The reason was that maemo conversations is not able to get certificates from servers, it just checks local certifactes and matches it to certificated required by ocs server (correct me if I'm wrong).

I was missing this certificate:
https://www.digicert.com/testroot/Di...ceEVRootCA.crt

[ Old information: And the companys certificate. I acquired companys certificate by installing pidgin, logging in with pidgin (pidgin can do the certificate handshaking). After succesful login with pidgin I copied companys certificate to a folder where maemo conversation would look it up:]
Code:
cp ~/.purple/certificates/x509/tls_peers/sip.mycompany.com /usr/share/purple/ca-certs/
(In my case this was the folder, but I think it could change according to ocs server)
I also copied the Assurance cert to directory mentioined above.
EDIT: As jpalko commented, recommended way is to debug which certificates you are missing and copy missing certificates to /usr/share/purple/ca-certs/ instead of copying sip.mycomapny.com cert directly to /usr/share/purple/ca-certs/. I debugged mine missing certs and installed them and now I'm able to login with conversations

Afterwards, I was able to connect succefully with maemo conversation!
Last edited by otto; 2010-12-30 at 07:50.
 

The Following 7 Users Say Thank You to otto For This Useful Post: