IP500 V2 Configuration Operation

Last Updated : May 04, 2022 |
Before editing the system's configuration settings, it is important to understand how those settings are stored and used by the system.
The control unit holds copies of its configuration in both its internal non-volatile and RAM memory. A copy is also held on the System SD card (IP500 V2).
The copies in non-volatile memory and System SD card, are retained even if power to the control unit is removed. During power up, the system loads the configuration file stored on the System SD card into its RAM memory. Other systems load the configuration stored in non-volatile memory into RAM memory. The copy in RAM memory is then used to control the system's operation.
If the system encounters a problem using the configuration file in its System SD card's /primary folder, it attempt to use the copy in its non-volatile memory. For fully details of the IP500 V2 boot process and SD card usage refer to the IP Office Installation Manual.
Users actions such as changing their forward destinations or mailbox passcode are written to the configuration in RAM memory.
Changes made using Manager are written to the configuration in non-volatile memory and then copied into the RAM memory and System SD.
Between 00:00 and 00:30, a daily backup occurs which copies the configuration in the system's operation RAM memory back into its non-volatile memory and, on IP500 V2 system's, the System SD card.On IP500 V2 system, the contents of the system memory cards /primary folder can then also be automatically copied to the /backup folder by enabling System | System | Automatic Backup.
When the system is shutdown using the correct shutdown method, the configuration in RAM memory is copied to the non-volatile memory and System SD card.
Using Manager
When using Manager to edit the configuration settings, the following need to be remembered:
  • Manager receives the current configuration settings from RAM memory. Therefore the configuration it receives includes any changes made by users up to that time. However it will not contain any subsequent changes made by users.
  • When sending the configuration settings back to the system, Manager allows two choices, reboot or merge.
  • Reboot sends the configuration to the system's non-volatile memory along with an instruction to reboot. Following the reboot, the new configuration in non-volatile memory is copied to the RAM memory and used.
  • Merge sends the configuration to the system's non-volatile memory without rebooting. The system then copies those changes that are mergeable into the RAM memory. A key point here is that not all configuration settings are mergeable.
As a result of the above, it is important to bear the follow scenarios in mind:
  • Changes made by users after a configuration is received by Manager may be lost when the configuration is sent back from Manager. Therefore it is preferable to always edit a recently received copy of the configuration rather than one that has been open for a period of time.
  • If a merge is attempted with non-mergeable changes, those items will be written to the non-volatile memory but will not be copied to RAM memory. If a daily backup occurs, they will then be overwritten by the RAM. If a power loss reboot occurs, they will be written to RAM memory.
Related links
Editing Configuration Settings