You can use the Reload Cache panel to force cache reloads, as required. During normal operations, manual (forced) reloads of the data caches of the application server are not required. However, reloading system caches ensures that what is displayed within the application server administration interface is synchronized with the Avaya X Connector (AXC) server.
You may need to use the forced operation in following situations:
Force a manual reload of User List, Global Address List, System Greeting, or Classes of service if there have been network problems that have impaired communications between the AXC and the application server. For example, cache reloads are required if you have made changes to extensions associated with local users or caller applications subsequent to initial creation.
After adding users, you must reload the GAL or wait for the system nightly maintenance to view the users on the Remote Users reports page.
Note Reloading the Global Address List is dependent on the size of the list and the responsiveness of the AXC and message store servers. Other cache reloads vary in time, depending on the size.
Force a reload of the System Greeting audio file if the audio file has been updated on the AXC server.
Force a reload of the Classes of Service definition file if this file has been updated on the AXC server.
Force a synchronization of the Distributed Cache whenever the application server has been offline for a long period of time. The application server synchronizes the data with the AXC server to which the application server is bound.