Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Office Communicator OCS on Maemo Conversations

    Reply
    Page 1 of 2 | 1   2   | Next
    otto | # 1 | 2010-12-29, 12:05 | Report

    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!

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by otto; 2010-12-30 at 07:50.
    The Following 7 Users Say Thank You to otto For This Useful Post:
    esiravegna, explit, generationally, jackburton, Manatus, rajeshgklm, ranbaxy

     
    jpalko | # 2 | 2010-12-29, 12:34 | Report

    If you have maemo-extras enabled, you are able to install them directly. In application manager they are:
    • Pidgin protocol plugin for Office Communicator
    • Pidgin protocols plugin for Conversations and Contacts
    You don't need to separately install telepathy-haze as it's a dependency of the account-plugin-haze.

    You shouldn't need to copy any files from ~/.purple/certificates/x509/tls_peers/ as those are the server certificates and not the certificate authority (CA) certificates. It's also not a recommendable solution. The best way is to use pidgin debug to find out what certificates are necessary
    Code:
    $ pidgin --debug >pidgin_output.txt 2>&1
    and from there you can see in the output
    Code:
    certificate/x509/tls_cached: Certificate Authority with DN='certificate dn here' not found. I'll prompt the user, I guess.
    when pidgin client will ask you for accepting the server's certificate. And these are the certificates you should seek to be available under /usr/share/purple/ca-certs.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 4 Users Say Thank You to jpalko For This Useful Post:
    generationally, jackburton, otto, ranbaxy

     
    stefanb | # 3 | 2011-01-17, 11:31 | Report

    FYI: I've packaged the profile and the icon into the new package "Office Communicator plugin for Conversations and Contacts". The package depends on account-plugin-haze and pidgin-sipe to drag in all necessary packages. You can find it in fremantle extras-testing.

    This of course doesn't address the SSL server certificate issue. You still need to run Pidgin at least once to create a SSL connection to your OCS server.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 3 Users Say Thank You to stefanb For This Useful Post:
    Manatus, otto, ranbaxy

     
    Krachlik | # 4 | 2011-01-17, 14:41 | Report

    I managed to connect to my OCS via pidgin messenger (accepted the certificate from the server). I used the same settings for the conversations account but I'm still unable to connect. Is there something I'm doing wrong? I don't see the certificate in /usr/share/purple/ca-certs/ directory

    Edit | Forward | Quote | Quick Reply | Thanks

     
    otto | # 5 | 2011-01-19, 07:35 | Report

    As jpalko mentioned, it is not recommended to use server certificates on /usr/share/purple/ca-certs/ directory. Instead of, remove your company certificate (sip.company.com) from ~/.purple/certificates/x509/tls_peers/ and run pidgin
    Code:
    $ pidgin --debug >pidgin_output.txt 2>&1
    Fill in your company settings and connect. When pidgin prompts for server certificate, discard it.

    In my understanding, you don't need the server certificate if you have proper ca certs (your servers certificates are created using ca certs [someone correct me if I'm wrong]). Discarding server certificate will cause pidgin to print missing ca certs debug info to output log.

    Grep from pidgin output log for missing ca certs
    Code:
    cat pidgin_output.txt |grep "not found"
    for example.

    Now you should see what ca cert(s) you are missing and you can download missing certificate from https://www.digicert.com and save them to /usr/share/purple/ca-certs/ directory.

    In my case I did:
    Code:
    cd /usr/share/purple/ca-certs/
    
    wget https://www.digicert.com/testroot/DigiCertHighAssuranceEVRootCA.crt

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to otto For This Useful Post:
    generationally, ranbaxy

     
    otto | # 6 | 2011-11-08, 13:01 | Report

    stefanb, are you going to add sipe/ocs support to meego?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    jackburton | # 7 | 2012-07-16, 19:55 | Report

    Anybody know if this works on N9? I plan on getting one at some point and would like to know.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Manatus | # 8 | 2012-07-16, 21:28 | Report

    I did put some hours to this to get it working without much success on N9, but my colleague was able to get it running without integration to messages and contacts. So basically it should be possible but currently there is no easy way of doing it.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    topet2k12001 | # 9 | 2012-07-16, 22:25 | Report

    Originally Posted by Manatus View Post
    I did put some hours to this to get it working without much success on N9, but my colleague was able to get it running without integration to messages and contacts. So basically it should be possible but currently there is no easy way of doing it.
    That's enlightening to hear. Do you have the step-by-steps instructions so we can try it as well?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    varunshaji | # 10 | 2012-09-19, 04:07 | Report

    Hi,

    In my case the pidgin itself craches when
    pidgin -> add -> protocol:Officecommunicator

    when i select OfficeCommunicator in protocol list it crashes.
    I am able to select other protocols.

    Meantime i was able to configure OCS in the pidgin installed in my PC. And then copy the certificates to the folder.
    But it doesnt work.
    Can anyone help me out.

    Will my second approach work. I am not able to see the log of maemo conversation and accounts. where can i get it how to enable it?

    Does pidgin fail like mine for anyone else..

    I am loving my N900..And i dont want to migrate for my office have moed to lync..

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following 2 Users Say Thank You to varunshaji For This Useful Post:
    explit, ranbaxy

     
    Page 1 of 2 | 1   2   | Next
vBulletin® Version 3.8.8
Normal Logout