> > Kevin wrote:

> > The call resolver reads the CSEs from a database, meaning we 
> > are able to run the call resolver on calls that took place in 
> > the past and are in the db.  For instance, the call resolver 
> > may be disabled and then when we start it, it reads in all 
> > the entries in the db that occurred while it was disabled

 Raymond Dans wrote:

> I understand what you're saying but I can't really see why someone would
> do this (have the resolver shut off for a week and then turn it on).

Users do all sorts of odd and mysterious things; it is good principle to
design the software so that it isn't sensitive to conditions that it
doesn't have to be.  It's not hard to make the call resolver insensitive
to the time at which it is run.

-- 
Scott Lawrence  tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED]
  sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs
  CTO, Voice Solutions   - Bluesocket Inc. http://www.bluesocket.com/ 
                                           http://www.pingtel.com/

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to