Fixed Issues In 7.0
1. PCS 6.0 Outlook plug-in would not detect a modification of the conference time if it was done
directly in Outlook. Similarly, PCS could not detect a deletion of an Outlook scheduled
conference. In PCS 7.0 this is detected automatically and updated in PCS DB. The user doesn’t
have to specifically modify the “Conference Resources” tab.
2. When extending the time of a conference that was created using resources from a distributed
network in PCS 6.0, the new conference end time was correctly shown on the interface but
actually the conference was not extended. This was fixed in PCS 7.0.
3. In PCS 6.0, on the Network Management > Monitor screen, the ViaVideo remained active (green
icon) even though the ViaVideo was turned off or the application was not running. In PCS 7.0 the
status shows correctly
.
4. When PCS 6.0 scheduled
an
MCU conference that allowed participants to dial into an MGC 6.0
using IVR, the conference ID in the email notification sent by Polycom Conference Suite
was
incorrect and participants could not get into the conference. This is fixed in 7.0.
5. Removing a guest from a scheduled conference using PCS 6.0 Outlook plug-in would sometimes
cause errors. This is fixed now.
6. In PCS 6.0 there was no option to define specific MP capabilities of a video codec. In PCS 7.0 the
definition of the MP capability is very flexible and can be defined separately for IP, ISDN and
both.
7. In PCS 6.0 there was no SNMP trap or email sent when failing over to the redundant server. In
PCS 7.0, both types of notifications are sent, stating that the primary service was stopped.
8. Host site designation in PCS 6.0 could not be deselected. In this version, this option is available
when selecting resource from the scheduling screen.
Known Issues and Limitations
1. When a meeting that is part of a recurring meeting is modified, deleting the recurring meetings as
a series does not delete the modified meeting.
2. The scheduling user interface allows a conference to be created at 128K with Content
although the minimum required speed is 192K.
3. Using Manage Conference, creating a new connection to an on-going conference doesn’t
connect the new participant to the conference.
4. When scheduling via Microsoft Outlook or Lotus Notes, user cannot add catering to recurrent
scheduled conference.
5. In XP client where the regional setting is Bulgaria, scheduling or managing conference results in
run-time error.
6. Certain foreign language characters, such as French characters çàè"éù, are not recognized in the
Conference Name, Ref ID, or Guest edit field.
7. When the Outlook component is uninstalled from a machine, the “VideoMeeting” drop down
option still exists in Calendar Properties > General Tab. This option must be changed to display
“Appointments”. If “VideoMeeting” is still selected after uninstalling, errors will occur when
scheduling appointments.
8. Refrain from scheduling meetings and managing conferences concurrently as this will result in
performance issues. An example of this would be having the Appointment window opened at the
same time a Manage Conference window is opened.
9. Currently, users who have the “request only” user profile are allowed to schedule conferences
that start “Now”. The application does not warn the user that this is not an allowed action. The
consequences of users being able to schedule “Now” will result in conferences that remain
unapproved after the scheduled time.
10. Multipoint conference cannot currently be scheduled using Polycom iPower as an MCU.
11. Import returns an error “Request BinaryRead failed” when the CSV file size is greater than 200
KB. This occurs when PCS is using a remote SQL setup. The current work around is to break the
large file into smaller files (< 200 KB) and perform the import.
12. The current maximum speed for a scheduled conference is 768 Kbps regardless of whether the
equipment can support higher dial speed.
Polycom Conference Suite
Page 7
9/15/2004
