Office Communications Server 2007 R2 enables users to invite other people, including anonymous users, to participate in instant messaging (IM) conferences, audio conferences, and desktop sharing sessions. To enable people to schedule and to join these conferences, Communicator Web Access (2007 R2 release) hosts a pair of Web pages (that is, dialin and join). Before you can use these pages for scheduling and joining conferences, the URLs must be published to Active Directory. You can do this either when you create a virtual server or later by using Communicator Web Access snap-in.

When you publish URLs you are given four publishing options:

The dial-in conference information suffix is the name of the page where users can configure dial-in conference information. By default, the dial-in conference information suffix (that is, page name) is dialin. For example, if your primary Communicator Web Access URL is, your dial-in conferencing page would be The conference join suffix is the page where users are sent to join a conference. By default, the conference join suffix is join. You cannot change either of these values.

The external and internal virtual server URLs represent the primary Communicator Web Access URL. When you invite someone to join a conference by using Communicator Web Access, you use this address when you create the conference invitation. If you support both internal and external URLs, it is recommended that you set both of these values to the URL of the external virtual server. This is recommended, in part, because the Conferencing Add-in for Microsoft Outlook, the tool that is typically used for conference scheduling, only displays the external URL. The internal URL is not available in the tool. If you set the two URLs to the same value, it will not cause problems for internal or external users who try to join a conference.

If you support only internal users, set both of these values to the URL of your internal virtual server.

URLs typically need to be published just once. You only need to republish URLs if you change your primary Communicator Web Access URL (for example, changing to

If you need to know which URLs and suffixes have been published to Active Directory, you can retrieve this information by using WMI.

To publish Communicator Web Access URLs using the Communicator Web Access snap-in

  1. Log on to the computer where the Communicator Web Access snap-in is installed. To publish URLs, you must be a member of the local Administrators group and a member of the RTCUniversalServerAdmins group.

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

  3. In the console tree, right-click Microsoft Office Communications Server 2007 R2, Communicator Web Accessand then click Publish Web Addresses.

  4. On the Publish Web Addresspage, in both the External web address (URL)and Internal web address (URL)boxes, type the URL that users outside the organization’s firewall use to sign in to the Communicator Web Access client (for example,

  5. Click Publish.

To verify published URLs

  1. On a computer where Communicator Web Access is installed, click Startand then click Run.

  2. In the Rundialog box, type wbemtestand then click OK.

  3. In the Windows Management Instrumentation Tester, click Connect.

  4. In the Namespace box, if necessary, type root\cimv2and then click Connect.

  5. In the Windows Management Instrumentation Tester, click Open Class.

  6. In the Get Class Namedialog box, in the Enter Target Class Namebox, type MSFT_SIPGlobalCWAServerConfigSettingand then click OK.

  7. In the Object editor for MSFT_SIPGlobalCWAServerConfigSettingdialog box, click Hide System Propertiesand then click Instances.

  8. In the Query Resultdialog box, double-click the lone instance of the MSFT_SIPGlobalCWAServerConfigSettingclass.