Just stepped out of a session on integrating OCS 2007 with IP PABX systems. The demo was fairly limited (people build entire careers out of this stuff - how much can you do in 90 minutes?) but was demonstrating linking Cisco Call Manager to an OCS Mediation server.
Nice stuff, and given that OCS 2007 Release 2 supports dial-in conferencing too, deploying OCS could potentially provide all the services Mars conferencing, video conferencing and voicemail too.
One of the suggestions floated was that for companies which already have a heavy investment in a PABX, you can replicate the environment and have a secondary dial plan with a prefix. So, for example:
I have extension 1151. If someone from a "standard desk phone" (or an external caller) were to call that number, it would ring on my desk. If they were to call 1151 from an OCS client, it would ring on OCS.
But... if they rang "91151" from a desk phone, it would bridge to the OCS client. When I go home at night, or travel OCB, I can forward my desk phone to "91151" and have the calls follow me.
Also note that, now Windows Server 2008 R2 supports microphones/inbound audio over a terminal services link, it would be possible to publish OCS as a server based application and have voice capability.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment