> Raymond Dans wrote: > > >> Let's say you analyze the CSEs from a week ago. You read > CSE request, > >> then your code kicks in and you declare the call to be over a week > >> long. > >> You flush CDR before you had a chance to read BYE CSE. > > > > Under what conditions would you be analysing CSEs from a week ago? > > The CSEs are analyzed usually within 10 seconds of them being > > generated and never looked at again. > > > > 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 > > Kevin >
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). At any rate, when the resolver starts up, it would start processing all of the CSEs from the last week and would have 5 minutes to complete the processing (more than enough time I believe) before the failed calls or long duration calls queues are checked. Anything in those 2 queues after the 5 minutes would definitely qualify as failed or long duration and then be closed and flushed to the database. Raymond > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
