Several readers of my blog have asked about the availability of an OCS client for the iPhone. I recently tried iDialog from Modality Systems (http://www.modalitysystems.com/idialog/) and wanted to share my experience. iDialog is an iPhone (and iTouch) application providing OCS contact list presence information and 2-party instant messaging (see here for the full list of features including the ability to search the corporate GAL).
In general, it worked as advertised, and I love getting OCS presence on my iPhone! I didn’t use the instant messaging functionality often – mostly because of my preference for not typing on a mobile device. It was also useful to see current free-busy information for several of my contacts (e.g. “Free for the next 2 hours”) and having access to GAL details.
There were some minor nuisances such as initially having to manually expand the “All Contacts” group to see my contacts, and a periodic small delay when typing in an IM session.
Here are some other key notes:
- There is no ability to do VoIP audio calls (aka Communicator calls). I didn’t really miss this though because I am on a mobile device and can call through the cellular network. I could see some users wanting to take advantage of a WiFi connection and do a VoIP call though.
- It works for OCS 2007 and OCS 2007 R2 (corporate and hosted) via the OCS Communicator Web Access server, so an external facing OCS 2007 CWA must be available for it to work.
- Given that presence can be a chatty protocol, one of the first questions I had was “How much data does it use?”. Modality Systems told me that approximately 1.2 kpbs is used over a 5 minute interval of “normal” usage. This is not broken down into presence and IM, but it gives a ballpark approximation.
iDialog can be purchased via the Apple iTunes Application Store. I purchased mine for $9.99 Cdn (from the Canadian App Store). I have been told that an update is coming shortly which address some outstanding issues (including the IM typing delay).
All-in-all it was an iPhone application worth purchasing.
You can read more about OCS mobility options in my “Mobile Options for OCS” blog post.


The client requires an OCS Communication Web Access Server (CWA). After that is installed and configured, the user just needs to enter their SIP address and password. You’ll need the web address (URL) of the CWA server from your IT department.
Hi,
Did you require any server side setup to access this, or just your username (email address?) and password?
What information may I need from my IT department in order to set it up?
Thanks
Ian
Hi,
No – iDialog does not reflect your availability in the same way. It has no ‘OCS-related’ call functionality, so any call you make is a regular iPhone call and iDialog just exists when the call is initiated (which apparently is Apple’s ‘rules’ and not iDialog’s).
Curtis
Hi Curtis, there isn’t actually any VoIP capability in the MMOC client either. I’ve always considered this a shortcoming however MSPs are renowned for blocking activity that erodes their own revenue streams. When you initiate a call in WinMo MMOC the OCS server makes a call to your handset over the cellular network and a makes a second call leg to the called party.
The advantage is that MMOC R2 now reflects that you are busy in a cellular call (whether MMOC or manually initiated) so other MOC users can see your presence.
does the idialog client reflect your availability in the same way?