THB - This is just the Overview for each scenario, see complete post for details!
Office Communications Server (OCS) 2007 offers multiple voice scenarios that are not necessarily easily understandable just by their names. However, it is essential to understand the different “flavors” of OCS voice in order to determine the best voice integration option for the specific customer environment. For this reason, I have explained and summarized the different voice integration options as follows:
PC-PC communication
Overview
This voice scenario was already available in OCS 2007 predecessor Live Communications Server 2005 SP1. OC acts as a soft client (software telephone), does not have a phone number (extension) assigned (only it’s SIP URI like someone@somewhere.com) and needs an audio or audio/video device connected to the PC in order to make and receive audio conversations by using your PC. Tricky: This is a VoIP scenario, but does not use any of the voice functionality, that has been added for OCS 2007! It’s peer-to-peer voice only between OC clients by using the SIP URI, no phone numbers.
Remote Call Control (RCC)
Overview
Also this voice scenario was already available in OCS 2007 predecessor Live Communications Server 2005 SP1. The users OC client does not act as a soft phone, does not need an audio or audio/video device connected to the PC and the user is not able to make or receive phone calls by using her/his PC. This is not a VoIP scenario!
Enterprise Voice
Overview
This scenario is new with OCS 2007. OC acts as a soft client (software telephone), has a phone number (extension) and needs an audio or audio/video device connected to the PC in order to make and receive phone calls by using your PC. This is a VoIP scenario!
Enterprise Voice with PBX integration – blank SIP Server URI (aka Dual Forking)
Overview
This scenario is new with OCS 2007. OC acts as a soft client (software telephone), has a phone number (extension) and needs an audio or audio/video device connected to the PC in order to make and receive phone calls. This is a VoIP scenario! In addition to that the user has a PBX/IP PBX phone standing next to her/his PC with OC on his desk that has the same phone number (extension) as OC! OC and the PBX/IP PBX phone will ring both on an incoming call to your extension.
No CSTA GW is deployed, but only a Media GW!
Enterprise Voice with PBX integration (aka Dual Forking with RCC)
Overview
This scenario is new with OCS 2007. OC acts as a soft client (software telephone), has a phone number (extension) and needs an audio or audio/video device connected to the PC in order to make and receive phone calls. This is a VoIP scenario! In addition to that the user has a PBX/IP PBX phone standing next to her/his PC with OC on his desk that has the same phone number (extension) as OC! OC and the PBX/IP PBX phone will ring both on an incoming call to your extension.
At least one CSTA and one Media GW need to be deployed!
.jpg)
No comments:
Post a Comment