Avaya and Office Communication Server 2007
A couple of customers have asked me recently about OCS interoperability with Avaya.
Avaya can provide interoperability today with two different methods for providing Remote Call Control (RCC) to Office Communication Server/LCS. The first is to utilize the AES (Application Enablement Services) which runs on a stand-alone server platform. This provides direct API support to link external systems into the Avaya telephony network using CSTA (TR/87) on the AES server for functionality extensions to Microsoft Office Communicator (MOC) and interoperability. Utilizing this service allows the Avaya customer/user to keep their existing handsets (analog, digital, or IP), and receive advanced presence updates in the Office Communicator enabled applications. These integrated presence updates include, “Available”, “Busy”, “On Phone”, and “Away from Desk”.
The second method is to utilize the Avaya soft client on the desktop, which provides a shim into MOC. This also provides TR/87 integration to forward all call information from Office Communicator to the Avaya client for call management. The Office Communicator is then provided with a tab for the soft client. This tab can be hidden if desired, or utilized to provide the end user with the option of using full Avaya CM functionality via MOC, such as accessing the pre-programmed function keys that they may have already established on their phone.
