Receive new two-party audio only call (call deflection):If Office Communicator 2007 R2 calls a Communicator Web Access (2007 R2 release) user, the Communicator Web Access (2007 R2 release) user sees the audio system alert and can select to redirect the call to a phone device. The redirected call is sent to the phone device and has no association with Communicator Web Access (2007 R2 release) after the redirection. The redirection selection list comes from the Office Communications Server 2007 R2 user self-information data. The user may also enter a custom number. In either case, Office Communications Server 2007 R2 must be able to place calls to the redirection number. If the user enters a phone number that is not allowed due to location profile, phone usages, or route settings, the call fails.

Receive request to add audio conversation to an existing IM-only conversation (call deflection):Communicator Web Access (2007 R2 release) is in an existing IM conversation with Office Communicator 2007 R2. Office Communicator 2007 R2 adds audio. Communicator Web Access (2007 R2 release) receives an audio system alert. Communicator Web Access (2007 R2 release) user can choose to redirect the audio call to a phone device. The redirected call is not associated with Communicator Web Access 2007 R2 after deflection. The Communicator Web Access (2007 R2 release) presence does not change to In a Call.

In existing two-party audio conversation and the other user adds IM:Communicator Web Access (2007 R2 release) is in an existing audio conversation where the Communicator Web Access (2007 R2 release) user is on cell phone (that is, with no associated conversation window) with an Office Communicator 2007 R2 user. The Office Communicator 2007 R2 user sees the Communicator Web Access (2007 R2 release) user in his roster and chooses to add IM. Communicator Web Access (2007 R2 release) user sees a system alert and a conversation window opens with the instant message. The audio conversation window and the Communicator Web Access (2007 R2 release) IM conversation are not associated. There is no connection in Communicator Web Access between the original audio conversation and the new IM window.

Communicator Web Access (2007 R2 release) user is in an existing two-party audio conversation and sends IM to the other user:A Communicator Web Access (2007 R2 release) user is in an existing two-party audio conversation with Office Communicator 2007 R2. The Communicator Web Access (2007 R2 release) user now wants to communicate with the same Office Communicator 2007 R2 user by using IM. The Communicator Web Access (2007 R2 release) finds the Office Communicator 2007 R2 user in the contact list and clicks to start IM. The Office Communicator 2007 R2 user sees a new window open for the new IM invitation. The Office Communicator 2007 R2 user has two windows open with the Communicator Web Access (2007 R2 release) user. There is no connection in Communicator Web Access between the original audio conversation and the new IM window.

Initiate three or more party audio-only conference from the contact list (add audio):A Communicator Web Access (2007 R2 release) user can initiate an audio conference from the contact list by multi-selecting two or more contacts in the contact list. After choosing the conference members, the Communicator Web Access (2007 R2 release) user can select the phone icon, and direct Office Communications Server 2007 R2 to call the selected phone number to initiate the audio portion of the conference. After the audio call is placed to the Communicator Web Access (2007 R2 release) user, the other participants are invited to join the audio conference.

Add audio to existing IM-only conference (add audio):A Communicator Web Access (2007 R2 release) user is in a conference with other users where IM is the only modality. The Communicator Web Access (2007 R2 release) user wants to add audio to the conference. The Communicator Web Access (2007 R2 release) user clicks the phone icon to add audio. An audio setup pane appears where the Communicator Web Access (2007 R2 release) user selects the self-information phone number he wants to use. The Office Communicator Server 2007 R2 A/V conferencing server initiates the audio call to the Communicator Web Access user and sends audio invitations to the other participants.

Receive new audio-only conference invitation (call deflection):Communicator Web Access (2007 R2 release) user can receive and join an audio-only conference. The Communicator Web Access (2007 R2 release) user can select which phone number she wants to use for the conference by selecting the number from the conference system alert. A conversation window appears with all of the conference participants in the roster. The Communicator Web Access (2007 R2 release) user’s phone rings and the user can communicate by using audio with all of the conference participants.

Receive request to add audio to existing IM-only conference (call deflection):A Communicator Web Access (2007 R2 release) user is in an existing IM-only conference and a participant in the conference adds audio. The Communicator Web Access (2007 R2 release) user receives an audio system alert. The Communicator Web Access (2007 R2 release) user accepts the call by specifying a self-information phone number to receive the call. There is no connection between the original IM conversation and the new audio call.

Receive new audio and IM conference invitation (call deflection):The Communicator Web Access (2007 R2 release) user receives an invitation to join a conference with IM and audio. The system alert is a conference system alert that enables the Communicator Web Access (2007 R2 release) user to join the conference. In the conference window, under join audio conference, the Communicator Web Access (2007 R2 release) user selects one of the self-information phone numbers from which he wants to redirect the audio call. IM is also enabled.

Receive new audio, IM, and application sharing conference invitation (call deflection):Other than the addition of the desktop sharing feature, this scenario is identical in function to the previous scenario.

In an existing two-party audio conversation and the Office Communicator 2007 R2 user adds another participant:A Communicator Web Access (2007 R2 release) user is in an existing two-party audio conversation with an Office Communicator 2007 R2 user. The Office Communicator 2007 R2 user is using the rich client Voice over Internet Protocol (VoIP) functions and the Communicator Web Access (2007 R2 release) user is on a phone device (that is, there is no Communicator Web Access (2007 R2 release) UI associated with the call). The Office Communicator 2007 R2 user sees the Communicator Web Access (2007 R2 release) user in her roster as joined to the audio conversation. The Office Communicator 2007 R2 user chooses to add another participant to the audio conversation. The other participant is successfully added and joined to the audio conversation. All three participants appear in the Office Communicator 2007 R2 user’s roster and they can all hear each other. In this scenario, the Communicator Web Access (2007 R2 release) user takes no action and the Office Communications Server 2007 R2 A/V conferencing server is controlling the audio bridge that allows the audio conference to reach all participants.

In existing two-party audio conversation and Office Communicator 2007 R2 user adds desktop sharing:The Communicator Web Access (2007 R2 release) user is in existing two-party audio conversation with an Office Communicator 2007 R2 user. The Communicator Web Access (2007 R2 release) user is on a phone device and the Office Communicator 2007 R2 user is terminating audio through Office Communicator 2007 R2. The Office Communicator 2007 R2 user sees the Communicator Web Access (2007 R2 release) user in the roster. The Office Communicator 2007 R2 user chooses to add desktop sharing to the conversation. The Communicator Web Access (2007 R2 release) user sees a system alert for desktop sharing and clicks the system alert to accept the invitation. The Communicator Web Access (2007 R2 release) user sees a browser open with the Office Communicator 2007 R2 user and himself listed in the roster. The audio call is still active and there is no connection between the audio call and the desktop sharing session.

The Office Communicator 2007 R2 user now adds another participant:The Communicator Web Access (2007 R2 release) user is using a phone device for an audio conversation with the Office Communicator 2007 R2 user and has a browser window open for desktop sharing with the same Office Communicator 2007 R2 user. Now a third person is invited to the application sharing session. The third person is joined to the audio conversation and desktop sharing session. All three users can speak with each other. As noted previously, the Communicator Web Access (2007 R2 release) user takes no action and the audio conversation and the desktop sharing session have no connection.

The Communicator Web Access (2007 R2 release) user adds another participant:The Communicator Web Access (2007 R2 release) user adds another participant to the audio conversation and desktop sharing session. The Focus Factory knows that audio and desktop sharing are enabled, so the Focus Factory sends the appropriate invitations to the new participant. The new participant is joined to the audio conversation and desktop sharing session. Communicator Web Access (2007 R2 release) still does not connect the audio conversation and the desktop sharing session.