When a system first connects to COM, it requests the customization files. Later, using COM or web manager, a customer system can be instructed to reload any customization files available. See Refreshing a Customer’s Customization Files.
The customer system does the following when it requests the customization files:
The first time the system connects it requests the CustomData.xml file (see The "CustomData.xml" File). This is used to set the initial value of various configuration settings. This file is only loaded once. It is not included in subsequent customization file refreshes.
The system requests the CustomPhoneFiles.tar and CustomTemplates.tar files from its provider's customization files folder. It present, it downloads and unpacks the contents of those files.
New files are added to the system.
Files with the same name as any existing files overwrite the existing files.
The system then requests the same files from its reseller's customization files folder. If they exist it repeats the download and unpacking process.
The system then requests the same files from its own server name customization files folder and repeats the download and unpacking process.
Once all the customization files have been unpacked and loaded:
New and updated template files do not affect any existing operation, but are available for use when configuring new items in web manager.
New and updated phone files are used when the phones are next restarted.
