On Sun, 2009-11-01 at 15:55 -0500, Dale Worley wrote: > Currently, we generate 'reg' events with a very crude strategy. Among > other problems, we don't generate prompt events when a registration > times out. > > What are the minimum requirements for useful 'reg' events, and how can > we provide them with reasonable efficiency?
We could always add a low-priority thread to the registrar to handle expiration and sending those events (removing the expiration code from where it now - essentially a side effect of other registration processing). Alternatively, we could actually keep track of the time to the next expiration, but that actually seems like more complexity than it's worth. The check for expired registrations is just one query against the registration database. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
