The reason for storing the last
registation with the subscriber is, as Alexandr says, so it is
permanent. If I have a million accounts I can see how many have
registered within the last month etc, not just how many are online
at one point.
If an event_route can be run when the contact is inserted (i.e. on
a UL_CONTACT_INSERT callback) then we could use sqlops to update
this info in any table, including subscriber. I don't believe
there is one though.
This patch stores the time of successful registrations at the
point that they are inserted, not when they expire, or when they
are successfully un-registered.
Maybe this patch is too specific, and making event routes for the
usrloc callbacks would be more flexible?
Hugh
On 13/03/2014 20:18, Olle E. Johansson wrote:
maybe because after AOR's expire this
information will be deleted ?
And now we have an event_route to insert something in any table
at that point...
I still don't understand how it belongs to the subscriber
table.
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Hugh Waite
Principal Design Engineer
Crocodile RCS Ltd.