Troubleshoot Missing Conferencing Settings Information in the 2007 R2 Release of Communicator Web Access
One day the dial-in conferencing feature for Office Communications Server 2007 R2 is working great, but the next day while trying to reset your PIN, you discover that the PIN information that usually appears in the Assigned Conference Information box is missing, and you get the message, "The server is currently unavailable. If the problem persists, contact your system administrator." What is going on here?
Author: Greg Anthony
Publication date: January 2010
Product version: 2007 R2 release of Communicator Web Access and Office Communications Server 2007 R2
Sometimes the information given in an error message, doesn’t lead you to the actual problem, and I encountered this one day when trying to reset my Personal Identification Number (PIN). I configured the dial-in conferencing feature for Office Communications Server 2007 R2, and it was working well. One day I forgot my PIN, so I opened the Dial-in Conferencing Settings page in the 2007 R2 release of Communicator Web Access and signed in to reset my PIN. The PIN information that usually appears in the Assigned Conference Information box was missing. When I tried to reset my PIN, I got the error message shown in Figure 1.
I decided to go back through the steps to configure dial-in conferencing, and I discovered that the meetings policy that was assigned to the forest or user was not configured to enable dial-in conferencing from a PSTN as shown in Figure 2.
I resolved the issue by enabling PSTN conference dial-in.To enable PSTN conference dial-in
In Office Communications Server 2007 R2 management console, right-click the forest that you want to configure, click Properties, and then click Global Properties (see Figure 3).
Click the Meetings tab (see Figure 4).
If you have a global policy, select the policy on the Global policy drop-down menu, select that named policy under Policy Definition, and then click Edit. If you are using per-user meeting policy settings, you will have to edit the policies for the affected users.
In the Edit Policy box, select Enable PSTN conference dial-in, and then select PSTN conference dial-in requires passcode if you want to require a passcode (see Figure 5).
You may have to wait up to 15 minutes for Active Directory replication or you can restart the front end services for the change to take effect immediately.
Now when I access the Dial-in Conferencing Settings page, I can reset my pin as shown in Figure 6.
Reading the actual error message seemed to indicate that there was a problem with the Communicator Web Access server, when, in reality, the problem was that the option to allow a PSTN dial-in wasn’t enabled. Sometimes, the cause is not easy to figure out based on the error information that you are given.
Visit the Office Communications Server main page at http://go.microsoft.com/fwlink/?LinkId=132607.
View the complete Office Communications Server documentation library at http://go.microsoft.com/fwlink/?LinkId=132106.
Follow tweets from the Office Communications Server team at http://go.microsoft.com/fwlink/?LinkId=167909.
Download all the Office Communications Server content as a Word document at http://go.microsoft.com/fwlink/?LinkId=133609.
Download all the Office Communications Server content as a compiled help file at http://go.microsoft.com/fwlink/?LinkId=160355. (Make sure you scroll down to the Additional Information section to download OCSDocumentation.chm.)