We've been asked by a customer to keep the last registration information, even after expiry.
They want to be able to look at the database and see where and when a phone last registered from, even if it was months ago. Only the last registration is important; they don't care about older ones.
This could be done using various methods such as a trigger in the database to update another table any time location is written to, but this is ugly.
Does any one know of a simple way to do it, preferably in ser.cfg?
Unfortunately this is not possible without usrloc module modifications.
Jan.
Alistair Cunningham wrote:
We've been asked by a customer to keep the last registration information, even after expiry.
They want to be able to look at the database and see where and when a phone last registered from, even if it was months ago. Only the last registration is important; they don't care about older ones.
This could be done using various methods such as a trigger in the database to update another table any time location is written to, but this is ugly.
Does any one know of a simple way to do it, preferably in ser.cfg?
Jan Janak wrote:
Unfortunately this is not possible without usrloc module modifications.
Use a database backend that has triggers. When a new entry is added to the location table write the record somewhere else.
Jan.
Alistair Cunningham wrote:
We've been asked by a customer to keep the last registration information, even after expiry.
They want to be able to look at the database and see where and when a phone last registered from, even if it was months ago. Only the last registration is important; they don't care about older ones.
This could be done using various methods such as a trigger in the database to update another table any time location is written to, but this is ugly.
Does any one know of a simple way to do it, preferably in ser.cfg?
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
What about using avp_db_store into your own table for each save() ? Not good for scalability though... g-) ----- Original Message ----- From: "Jan Janak" jan@iptel.org To: "Alistair Cunningham" acunningham@integrics.com Cc: "serusers" serusers@lists.iptel.org Sent: Wednesday, March 01, 2006 10:35 AM Subject: Re: [Serusers] Saving historical registration information
Unfortunately this is not possible without usrloc module modifications.
Jan.
Alistair Cunningham wrote:
We've been asked by a customer to keep the last registration information, even after expiry.
They want to be able to look at the database and see where and when a phone last registered from, even if it was months ago. Only the last registration is important; they don't care about older ones.
This could be done using various methods such as a trigger in the database to update another table any time location is written to, but this is ugly.
Does any one know of a simple way to do it, preferably in ser.cfg?
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers