There are two basic audio scenarios for Communicator Web Access (2007 R2 release). Both of the following scenarios enable Communicator Web Access (2007 R2 release) to control audio calls, although Communicator Web Access (2007 R2 release) clients do not have audio capability:
-
Scenario 1: Enterprise Voice-enabled Communicator Web Access
(2007 R2 release) user has an incoming voice call.Office
Communications Server 2007 R2 forks the call to all registered
endpoints. The Communicator Web Access (2007 R2 release) endpoint
that is maintained in the Communicator Web Access (2007 R2 release)
data logic layer is a valid registered endpoint, but the
Communicator Web Access (2007 R2 release) client cannot perform
audio function. Therefore, when the data logic layer in
Communicator Web Access (2007 R2 release) receives the call
notification, the data logic layer shows the user a system alert
with call deflection options that are obtained from self-data and
the data logic layer enables the user to input a custom number. The
path through the client is proxy layer, user session, component
store, system alert manager, and finally the system alert. The data
logic layer receives the response from the client and passes this
data back to Office Communications Server 2007 R2, which takes the
action dictated by the user. The calling party is placed on hold
for the amount of time that it takes to respond to the system
alert. After the data packet from the client is returned to the
data logic layer, the data logic layer passes the data back to the
Office Communications Server 2007 R2 pool for action.
-
Scenario 2: Communicator Web Access (2007 R2 release) user with
an open instant messaging (IM) conference wants to add
audio.From an existing IM conference, the Communicator Web
Access (2007 R2 release) user adds audio. The user selects a number
from the displayed self-data or the user enters a custom number.
The client sends this information along with the request to add
audio to the Communicator Web Access (2007 R2 release) data logic
layer. The data logic layer signals to the other conference users
that audio is being added and it takes one of the following
actions:
- If the called party is Enterprise Voice, the connection is made
to a valid registered endpoint or to an Office Communicator
instance.
- If the called party is a Communicator Web Access (2007 R2
release) user, the Communicator Web Access (2007 R2 release) server
invokes the call deflection scenario.
- If the called party is Enterprise Voice, the connection is made
to a valid registered endpoint or to an Office Communicator
instance.
Office Communications Server 2007 R2 can call any global or local number that is allowed by the Communicator Web Access (2007 R2 release) user’s location profile. For example, if the Communicator Web Access (2007 R2 release) user inputs a telephone number that is not reachable by Office Communications Server 2007 R2 because of routing restrictions or phone usages, the call fails.
In This Section
This section contains the following topics: