Configuring Audio Conferencing for Communicator Web Access

Communications Server 2007 R2

Topic Last Modified: 2009-06-18

Communicator Web Access (2007 R2 release) enables users to add audio conferencing to any instant messaging (IM) or desktop sharing session. After an instant messaging or desktop sharing session has been established a user can then add audio conferencing (that is, by using any telephone, including cell phones) to the session. This enables user to take part in a conference call along with the instant messaging or desktop sharing session. When audio is added to a session, Communicator Web Access will call the user who initiated the audio conference (that is, at a phone number supplied by that user) and then invite other users to join the audio conference. If a user decides to join, Communicator Web Access will then call that user at the phone number he or she supplies.

Audio conferencing requires you to install and configure Audio/Video Conferencing Server and, if you need to support external users, Audio/Video Conferencing Edge Server. You must also set up Mediation Server, which connects Office Communications Server 2007 R2 to the public switched telephone network (PSTN).

If all of your users are internal users who have been enabled for Enterprise Voice, and if you have configured location profiles for these users then no additional work is needed for you to implement audio conferencing. However, this is not the case if you:

  • Support external users.
  • Have users who have not been enabled for Enterprise Voice.
  • Have not configured location profiles for your users.

If any of these are true then you must create static audio routes for each Communicator Web Access server or server pool. These routes point the server or server pool towards the location (IP address) of the appropriate Mediation Server.

To configure a static route for audio conferencing
  1. Log on to a computer running the Office Communications Server 2007 R2 administrative tools. To create static routes you must be member of both the local Administrators group and the RTCUniversalServerAdmins group.

  2. Click Start, point to Administrative Tools, and then click Office Communications Server 2007 R2.

  3. In the console tree, expand the forest node.

  4. Do one of the following:

    • If you are running Office Communications Server Enterprise Edition, expand Enterprise pools, and then right-click the pool in which Communicator Web Access is installed.
    • If you are running Office Communications Server Standard Edition, expand Standard Edition Servers and right-click the name of the server on which Communicator Web Access is installed.
  5. Point to Properties, and then click Front-End Properties.

  6. In the Front End Properties dialog box, on the Routing tab, click Add.

  7. In the Add Static Route dialog box, under Matching URI, type the Communicator Web Access domain name in the Domain box, and then click Phone URI.

  8. Under Next hop, type the fully qualified domain name (FQDN) of the Mediation server (for example, in the FQDN box. Type the IP address of the Mediation server in the IP address box and the listening port number (typically 5061) in the Port box.

  9. Select TLS from the Transport dropdown and then click OK.

Community Additions