CS_DIRTY means that the contact in the memory cache has been modified and the modified structure should be written into the database next time the cleanup timer hits.
That's nothing you should worry about, the shorter the registration interval is the more often you are going to see contacts in CS_DIRTY state.
When the usrloc timer hits, the contact will transit into CS_SYNC state. When next registration comes, it will transit into CS_DIRTY again.
Jan.
On 12-01 21:52, Franz Edler wrote:
Hello,
looking at the usrloc contact state in output of "serctl ul show" I wonder that I have a User Agent which re-registers regulary (e.g every 30 sec) but always shows a state "CS_DIRTY". I would expect a stable state of CS_SYNC. Should not I be concerned about it?
What might be the cause of this "dirty" state? Does anybody have a suggestion?
Thanks Franz
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers