Configuring a Next Hop Server for Anonymous Users
[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]
In this release, Communicator Web Access supports anonymous users as participants in audio conferences or desktop sharing sessions. When an authenticated user joins a Communicator Web Access conference, Communicator Web Access proxies messages to the user's home server. By their very nature, anonymous users do not have an Active Directory identity and therefore no home server. As a result, Communicator Web Access requires a default next hop Office Communications Server 2007 R2 server to which it can proxy messages when an anonymous user joins a conference. You are required to configure this next hop server when you create a Communicator Web Access virtual server, but you can use the procedures in this topic to modify the setting.
To configure a next hop server
Log on to the computer that is running Communicator Web Access Snap-in as a member of the Administrators group and the RTCUniversalServerAdmins group or as a member of the Administrators group and a member of a trustee group to which Office Communications Server 2007 R2 server administration permissions have been delegated.
Click Start, point to Administrative Tools, and then click Microsoft Office Communications Server 2007 R2, Communicator Web Access Snap-in.
In the console tree, expand the FQDN of the computer that is hosting the virtual server that you want to configure with a next hop server, right-click the name of the virtual server, and then click Properties.
On the Properties page, click the Next Hop tab. Click Next hop pool, and then click the FQDN of the Office Communications Server 2007 R2 server to which you want the virtual server to proxy messages when an anonymous user joins a Communicator Web Access conference.
Click Port, and then type the port on the next hop server that is configured to accept messages from Communicator Web Access.
When you are finished, click OK.