Guest

Cisco Unified MeetingPlace

Field Notice: FA00333 - User Unable to Join External Meeting Frozen at 1% Loading


Revised June 07, 2004

May 20, 2004


Products Affected

Product

Comments

MeetingPlace Web

4.2.7.106, 4.3.0.63, 4.3.0.100 (DMZ-B or DMZ-C)

Problem Description

Note: This Field Notice is a legacy Latitude Field Notice that has been converted to the Cisco format so the information would remain available to their customers.

Users are unable to join an external Web Conference. Launching the Meeting Room becomes frozen at 1% loading. Restarting the MeetingPlace Web services does not resolve the issue.

This is only an issue with a DMZ-B ,both internal and external sites are configured on a single machine or a DMZ-C ,two web servers, one internal and one external deployment with Split or Segmented DNS. Split DNS means that only one hostname is used which resolves internally to the internal site, and externally to the external site.

Problem Symptoms

Users cannot open the Meeting Room in a public meeting; therefore, they are unable to participate in a Web Conference.

Workaround/Solution

This issue will not be experienced if you have the following MeetingPlace Web versions (hot fixes) installed:

  • 4.3.0.100.3

  • 4.3.0.63.6

  • 4.2.7.106.21

If version 4.3.0.100 is installed, upgrade to 4.3.0.100.3.

If the most recent hot fix is not installed, follow the procedure below or upgrade to 4.3.0.100.3.

For a DMZ-B deployment,

  1. Go to:\Latitude\MPWeb\Template\External\

  2. Open file wcLaunchWebConference.tpl

  3. Search for "m_DataConfServer" and remove the tag [an error occurred while processing this directive]. Be sure to not remove the quotation marks.

  4. Here is an example of how the tag looks like before and after the change:

    Before:

    var m_DataConfServer = "[an error occurred while processing this directive]";
    

    After:

    After: var m_DataConfServer = "";
    
  5. Save the file, then close.

  6. If the DMZ B configuration is on a server without split DNS, copy the updated wcLaunchWebConference.tpl from the external folder to the internal folder.

  7. Restart all the MeetingPlace Web services.

For Web 4.3.0 and later, restart the MeetingPlace Web Conferencing service.

For a DMZ-C deployment, the change is only required on the external Web server.

Repeat steps 1-5 and 7 from above.

On a DC load balancing system, "m_DataConfServer" should not be modified.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.