1608 Sets losing Personal Directory 2

[SupportDude]

IP Office 500v2 running 8.0.44.
User configures Personal Directory entries via telephone interface.
Entries are visable via telephone interface and in IP Office Manager at User>Personal Directory.
If the IP Office is rebooted, all of the Personal Directory entries disappear.

Known issue?

Is there a fix?


-SD-

http://www.mysupportguy.net

 

[intrigrant]

This is not a phone problem but a IP Office core software problem/issue.
IP Office makes a internal backup every 24 hours after initial startup, so if the IP Office was initially started a 08:00 AM then every day at 08:00AM it makes a backup of the config on the SD card.
If a customer starts programming personal numbers at 10:00 AM and he/she adds 100 numbers all is ok unless the IP Office is rebooted before 08:00AM the next morning, if that happens all programming is lost.

A simple mind delivers great solutions

 

[SupportDude]

Thanks for the response intrigrant!

So, if I understand you correctly, the Personal Directory information configured via the telephone set is written to the SD card, but not saved.
Very interesting. I was not aware of this.
Now off to the lab for some testing.

Thanks again!

-SD-

http://www.mysupportguy.net

 

[amriddle01]

It's written to the VRAM during the day, and at the time indicated by Intrigrant it's then written to the NVRAM (which the system reads upon boot) so it's then safe

 

[SupportDude]

Thanks amriddle01.
That makes complete sense!

Could also force the write from VRAM to NVRAM by making a change using IPO Manager and then saving/merging the save back to the IP Office?

-SD-

http://www.mysupportguy.net

 

[amriddle01]

Should do, this nice diagram sums it up

 

[amriddle01]

Here is the technical description of the process:

· 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 IP Office 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. For IP Office Release 6.1 and higher: 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 Command.

· 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 IP Office Manager

When using IP Office Manager to edit the configuration settings, the following need to be remembered:

· IP Office 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, IP Office 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, see the Mergeable Settings list.



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 IP Office Manager may be lost when the configuration is sent back from IP Office 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.

 

[SupportDude]

Great Info!!

Thank-you very much!!!

-SD-

http://www.mysupportguy.net