Microsoft release OCS client for Java handsets
Microsoft have released a version of the Office Communicator Mobile client software for Java-based handsets.
The client can be downloaded from here:
http://www.microsoft.com/downloads/details.aspx?familyid=1FEEAB9B-02FC-4...
(for Nokia S60 240X320 resolution)
or from:
http://www.microsoft.com/downloads/details.aspx?familyid=DCB3AE06-ED5F-4...
(for Nokia S60 320x240 resolution)
Or alternatively by browsing to http://www.getcomo.com in the device browser.
The client is downloaded as a ZIP file containing 2 files:
- communicator_NOKIAS60R2_JVP_EN_US.jad
- communicator_NOKIAS60R2_JVP_EN_US.jar
Unzip the files and copy them to your Nokia handset. Then simply browse to where you saved them using the built-in File Manager and click on the Jar file to install it.
Once installed, the client will appear in the Installations folder:
Launching the client for the first time will display the license agreement which you will need to read and accept to continue:
You will then be prompted to enter in your username details (in the form 'DOMAIN\Username'), your password (your Active Directory password, ie the same password you use to log into your PC or access your email via OWA) and the address of the Office Communicator Server (OCS) box:
You will then be prompted to enter a PIN number, of your choosing and known only to you, that you will be prompted to enter each time you launch the client to prevent unauthorised access to the software should someone inadvertently (or purposefully) get their hands on your phone:
Now you're all set. When logging in you will be prompted to allow the software to use your network connection and specify the access point to use:
After a few moments you will hopefully be logged in.
It is important to note that this version of the client only supports the IM functionality rather than full-blown video-conferencing, and should you wish to connect to your company's OCS server then it will either need to be publicly available (ie, Internet-facing), or you will need to have established a VPN connection to the LAN by some other means before being able to contact the internal address of the server.