October 25 2008
Microsoft Office Communications Server 2007 R2
Many enterprises have already deployed OCS 2007. I’ve tested it and it’s a great product, I like the proprietary codec that offers excellent voice quality, the ease of voice/video conferencing and one platform that delivers IM, audio and video.The only thing that was missing from OCS 2007 that was stopping us from deploying it internally was the requirement of a VoIP gateway to connect to the phone company. This is no longer an issue! OCS 2007 R2 supports SIP trunks along with a host of other features:
- Dial-in audio conferencing
- Desktop sharing
- Persistent group chat
- Attendant console and delegation
- Response group
- Mobility and single number reach
OCS 2007 R2, like most Microsoft products, offers ease of access from any device, any where. Clients can be connected via hard phones, software clients on PCs, software clients on handhelds, there is even a web based client software to use without installation.So what is holding back most of the other enterprises that have not deployed OCS? I think it’s the heavy resource requirements that OCS has. Microsoft documentation says a dual core CPU is recommended, this says a lot. In addition to the hardware, OCS requires several other software modules to be in place like IIS, .Net framework, in some cases SQL.Â

