Hello,
Microsoft talks about integration with OCS in three areas:
Direct SIP
Dual Forking
RCC
It is possible (or will be possible) to integrate MX-ONE in all these ways for MD110 it will probably be somewhat limited.
Direct SIP / SIP Trunk
It is possible to setup a SIP trunk toward a Microsoft Mediation server (part of OCS).
MX-ONE can signal with SIP over a SIP trunk via either TCP or UDP.
For the MD110 it is possible to use a Qsig trunk with a converter as described in the posting above.
Aastra Collaboration Link / RCC
ACL will give you call control of your PBX extension from a Microsoft Office Communicator.
This is what Microsoft calls RCC (Remote call control)
Aastra Collaboration Link is an OCS gateway using OAS for call control; hence it will work with both MX-ONE as well as MD110.
In MX-ONE 3.2 the Dual Forking feature will be introduced.
Dual Forking makes it ring on your MX-ONE extension and in Microsoft Office Communicator at the same time.
Dual Forking can be explained as the old parallel ringing feature, but now one of the end points is a Windows communicator device connected to OCS.
A Microsoft OCS user, in a solution where an OCS system is connected to an MX-ONE system that is able to accept an incoming call on either of the systems, i.e. on the MX-ONE phone or on the Office Communicator client on the PC. MX-ONE V.3.2 or OCS forks the call to both the called party’s Office Communicator device(s) and to the MX-ONE extension that is associated with that user and all of the called party endpoints start to “ring”. The called party has the option of picking up the call on either the telephone or any of the UC devices. Once the call has been picked up on one endpoint, the remaining endpoints stop ringing. In the case of a call being picked up via the telephone, the PBX generates a SIP CANCEL to close the SIP INVITE transaction with the Office Communicator devices.