I'm having trouble with the DND and CFWD status not syncing to the phone's LEDs, and the problem can be traced to data loss in the context files in /var/cache/aastra. This never happened (that I noticed) during our testing phase, with a handful of phones (57i CT) polling the synch.php script every five minutes.
Three things changed at roughly the same time:
- The XML Scripts package was updated to 2.1.1.
- I changed the "action uri poll interval" to 60 seconds.
- We provisioned and deployed 110 phones.
Since that time, here's what happens:
1) A phone for (for example) 3333 is newly provisioned. It has both CFWD and DND keys defined in /var/cache/aastra/3333.context, and the LEDs work just fine when the DND or CFWD modes are activated.
2) Within a few minutes or hours, the 3333.context file "decays" and some of the features no longer sync. There's no random file corruption; the file format is still valid and readable -- but some of the parameters are just gone. Usually the "key" parameter in the [cfwd] section goes first, then later the "key" for the [dnd] section. Sometimes the whole [cfwd] section disappears. The other sections of the file (e.g. [daynight], [speed]) seem to persist with no problems.
Due to the precise nature of the parameter deletion, I believe that some sort of race condition in the reading and writing of the context files is causing partial files to be written out every so often. I don't think it's caused by my having the phones update every minute, but that's probably making it happen much sooner.
Has anyone else seen this issue? Can anyone suggest a clean fix for it?
Member Since:
2008-07-17