Accessibility Skip to content
Article ID: 000041006
Last Modified Date: 12/09/2021
Access Level: Public

ReadiManager LX100 1.0.1 Release Notes

This document provides complementary or late-breaking information about the ReadiManager LX100 1.0.1 that is not available in the documentation or online Help. Check the Polycom web site ( for the latest information.      


·          Conference on a Port support on the Polycom MGC ·          Meet Me per Conference support on the Polycom MGC ·          New endpoint support for the Polycom PVX, VSX8000 and VSX6000 series products ·          Ability to easily reschedule future conferences when equipment parameters are changed. ·          Automatically add resources invited in Outlook to the  ReadiManager LX100 conference.

Server/Administrative Features/Enhancements

·          LDAP group name made configurable   Device Management
  • Support MGC-25
  • Support provisioning for VSX 5000, VSX 6000, VSX 6000a, VSX 7000a, VSX 7000e, VSX 8000a, QSX 300
  • V-Series SoftUpdate
o         SoftUpdate file upload model has been broken into individual supported VSX models with VSX7 serving as the repository for the enchilada file.  The following softupdate models are available: V500, VSX 3000, VSX 5000, VSX 6000, VSX 7000, VSX 7000A, VSX 8000, VSX 8000A, QSX 300 o         If a file for a particular model requiring softupdate is available, we use that file. If not, we will look to see whether the enchilada file is available (upload to the VSX7 model).  If such a file is available, we will use this file to softupdate the endpoint.
  • The latest released version of FX and VSX softupdate password protected the system.xml file (if the user set the admin password on the endpoint).  This will prevent the endpoint from being discovered during a search or added to Device Manager (whether the correct password is provided or not).  In version 1.0.1, the endpoint can be added if the correct password is provided during the addition.
  Scheduling   1.        All scheduling reports, as well as the conference list in the scheduling wizard, now observe Daylight Saving Time adjustments and display scheduled conference time correctly. 2.        Conference notification mails now display the time of the conference according to the scheduler’s local time zone. 3.        High quality conferences of speed 768KB and higher can now be scheduled. 4.        Using “Bridged Audio” or “Rooms only” templates does not result in error any more. 5.        Chairperson option is now enabled also for bridged audio conferences. 6.         READIMANAGER will not add participants in a higher speed than defined to a Continuous Presence conference on the MGC. 7.        When LDAP is turned off, users can now change their password directly from the users menu. 8.        In case RADVision MCU’s are defined, the host MCU is selected according to the conference type and the location of the gateways involved in the conference. In addition, an alias that matches the selected service is generated by  READIMANAGER. 9.        If a conference includes more participants than a single bridge can host,  READIMANAGER will have the conference cascade between multiple bridges, even if all participants are from the same zone. 10.    IP dial-out guest can now be scheduled as part of a conference when using the scheduling wizard. 11.    When changing the type of an existing equipment item, the equipment parameters are now saved only when “Update” button is hit. 12.    When scheduling recurrent conferences in a row, each recurrent conference is assigned a different recurrent conference ID. 13.    Scheduling People+Content conferences doesn’t require opening the “Advanced Settings” dialog if the selected template is defined to use People+Content. 14.    READIMANAGER can now work with an MGC which is set to numeric ID mode. This resolves an incompatibility between WebOffice and  ReadiManager LX100 when they are both communicating with the same MGC. 15.    The LDAP support now integrates with the enterprise LDAP. This provides 1) user password authentication and management through LDAP (not a separate  READIMANAGER database), 2) direct user authentication using the Window’s token already stored when the user logged into the enterprise network, 3) no necessary management of users in the  READIMANAGER database. New users that log into  READIMANAGER are given administration controlled default access rights which can be adjusted to higher levels by the administrator. 16.    Outlook plug-in and Lotus Notes plug-in users do not have to login first to the web interface in order to schedule. 17.    Resources marked as “Hidden” no longer appear in the scheduling wizard. 18.    Advanced conference parameters, modified when scheduling a new conference, will now reload their original values from the template before scheduling the next conference. 19.    On an MGC the IVR conferences can now use People + Content, if defined in the new Meet Me per Conference settings. 20.    When cascading is enabled, a new conference can be now scheduled even if it requires more resources than are available on a single MCU in the system. 21.    The MCU hosting a new scheduled conference will be selected correctly, also in the case where the conference requires transcoding ports. 22.    A recurring conference scheduled to the X day of every month will now be scheduled correctly in December. 23.    When a conference is set to “auto” audio algorithm,  READIMANAGER will leave the audio algorithm selection to the MGC.  24.    The MGC will use H.323 aliases for dialing whenever possible, if the H.323 service of the MGC is set to use Gatekeeper. 25.    Email messages sent by  READIMANAGER for scheduled events have been improved to prevent some email servers from rejecting the message. 26.    The conference reference field has been extended to 128 characters. 27.    The help link from the scheduling wizard is now working. 28.    Default value for “Audio Mix Depth” is now 3, which is consistent with the MGC default setting. 29.     READIMANAGER can now schedule conferences when more than 200 zones are defined. 30.    Viewing trouble tickets from the scheduler is now working correctly. 31.    When a meeting that is part of a recurring meeting is modified, deleting the recurring meetings as a series now deletes the modified meeting as well. 32.    Resource availability is now calculated correctly relative to certain specific time zones and unique daylight savings time zones. This caused 1) incorrect results in the combined resource calendar, 2) miscalculation in the “find earliest time” feature, and 3) not showing all available resources when “show available resources only” option was used. 33.    Major performance improvements when scheduling a new conference. 34.    Audio participants added to a video conference no longer cause the conference on the bridge to alter the state of transcoding or voice activated switching. 35.    Cancellation emails are now sent upon canceling a conference that was created in the web interface. 36.    The web interface can now schedule off-net resources. 37.    More control over dialing rules to set up custom rules. 38.    After altering elements of a resource used for a future conference, the user will have the option of easily accessing and rescheduling those conferences.   Device Management   1.       DeviceManager service stops when polling MGC 50: Monitoring a MGC 50 device causes the DeviceManager service to terminate, then restart again at the next incoming event. The service repeats this forever.         Client-side upgrade issues:134 There has been a change in the ActiveX components labeling since version 1.0. Therefore users who have used version 7.0.0 may encounter unexpected behavior when logging to the upgraded server unless previous controls are removed. To manually remove previous controls,
  • Close all browsers.
  • Use Windows “Add or Remove Programs” to remove previous  ReadiManager LX100 installed components (Outlook plug-in, Lotus Notes plug-in and  READIMANAGERcontrols)
  • Using Windows Explorer, go to c:\windows\Downloaded Program Files.
  • Delete all files in this folder.
  • From the browser’s internet options, delete all temporary internet files.
  • Now the user can login into again to  ReadiManager LX100 and use the scheduling interfaces and/or download the Outlook and Lotus Notes plug-ins.
    You must have a least Power User privileges to install and uninstall the Outlook or Lotus Notes  ReadiManager LX100 plug-in components on a client PC.     For each user who wants to install the Outlook component, on his/her computer, log onto  ReadiManager LX100, go to Support > Downloads link, and select Outlook Plug-In link.   Run the executable on a PC that has Outlook 2000 SR-1, Outlook 2003, or Outlook XP.  READIMANAGEROutlook.exe will not install if Outlook is not detected on the client machine. Before installing, close Outlook and then follow the on-screen instructions to enter the user account, password, domain, and server information. A local user with Power Users privileges is all that is required to install the component.     For each user who wants to install the Lotus Notes component, on his/her computer, log on to  ReadiManager LX100, go to Support > Downloads link, and select Lotus Notes Plug-In link.   Run the executable on a PC that has Lotus Notes 6.0.3 or higher. The local user privilege must be at least Power User in order to install the plug-in. Refer to the Notes Scheduling Guide.PDF for further instructions on setting up the Lotus Notes plug in.     When working in the  ReadiManager LX100 Web View   ·          If a user remains at one screen for some time without taking any action, the user’s session with  ReadiManager LX100 automatically times out. In this case, it may appear that  ReadiManager LX100 is not working. To continue work, close the browser and log on again.   ·          If any unusual error message appears, the Internet Explorer connection to the server has been compromised. Simply close all open Internet Explorer windows, restart Internet Explorer and login as normal.   ·          Allow the web pages to fully load before clicking on any controls, Back button or Home icon in  ReadiManager LX100.  This will reduce the chances of unexpected browser behavior.   §          When using  ReadiManager LX100, only one session should be opened at one time from a computer.  This includes having:   1.        One browser with the  ReadiManager LX100 opened at one time OR 2.        One Scheduling or Manage conference window opened in Outlook at one time. §          It is highly recommended not to have a Scheduling or Manage Conference window through Outlook and a browser opened with the  ReadiManager LX100 at the same time. §          In some cases it may be necessary to remove  READIMANAGER ActiveX controls and load new ones. Use the steps below to remove these files:
  • Close all browsers
  • Using Windows Explorer, go to c:\windows\Downloaded Program Files
o         Delete all files in this folder NOTE: Any files loaded in this directory will automatically be reloaded if they are called by a web-application even if they are not associated with  ReadiManager LX100.
  • From the browser’s internet options, delete all temporary internet files.
  • When the web scheduling page is accessed, new controls will be loaded automatically.
    1.        When adding the first service to a video codec, the user has to click “Update” on the equipment information page for the new service to become the default service of the codec, even though it looks like the settings have taken affect . 2.        If the end time of a scheduled conference is Midnight, the end time doesn’t show on the email notification. 3.        The scheduling user interface allows a conference to be created at 128K with People+Content although the minimum required speed is 192K. 1163 4.        Using Manage Conference, creating a new connection to an on-going conference doesn’t connect the new participant to the conference. 1045 5.        In a Windows XP client where the regional setting is Bulgaria, scheduling or managing conference results in run-time error. 396 6.        Certain foreign language characters, such as French characters çàè"éù, are not recognized in the Conference Name, Ref ID, or Guest edit field. 980 7.        When the Outlook component is uninstalled from a client system, 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 as a Manage Conference window is opened. 9.        Currently, users who have the “request only” user profile are allowed to schedule conferences that start “Now”, but the conference will remain unapproved and will not start. The application does not warn the user that this is not an allowed action.  10.    The Polycom iPower endpoints cannot be scheduled to use their internal multipoint capabilities. 11.    When using a remote SQL database, the import feature returns an error “Request BinaryRead failed” when the CSV file size is greater than 200 KB. The current work around is to break the large file into smaller files (< 200 KB) and perform the import. 1.0.1