Cisco Unified MeetingPlace

Field Notice: Cisco MeetingPlace Servers Cannot Schedule Meetings That Falls Between 3 to 4 PM PST on December 31

May 20, 2004

Products Affected



Cisco MeetingPlace Servers

5.0.0af, 4.3.0t and below

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.

A meeting can not be scheduled where any part of the meeting, including the start and end guard times, falls within 3 to 4 PM PST or 23 to 0:00 GMT. It will give you a message similar to the following:

Msg:[13074] The number of ports available at the specified time: 0.
Msg:[5179] Not enough ports available for operation.

Problem Symptoms

Cannot schedule a meeting that crosses the yearly boundary in GMT time.



The workaround for a 4.3.0x and 5.0.0af system is to schedule a meeting with zero port. Make sure there are floater ports configured.

For customers with an older version where zero port meeting is not supported, you may schedule a meeting between that time period and let it extend into that time. For example, if the end guard time is 15 minutes, schedule a meeting at 2:30 for 15 minutes, attend the meeting ahead of time with 2 phones, and let the meeting extend into that time period.


For the Cisco MeetingPlace Server 8112 (M3), upgrade to 5.0.2q.

For the Cisco MeetingPlace Server (PCI), there is a hot fix available for 4.3.0t. Please contact Cisco MeetingPlace Support (TAC) to download the hot fix.

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.