On Tue, 2010-03-02 at 13:57 -0500, Dale Worley wrote: > If the log files on a system are large, the script analyze_483s can take > many minutes to execute. This is problematic, because in sipx-snapshot, > we run analyze_483s automatically, to check whether the user is having a > message-looping problem. I believe that for the user experience, we > need to remove this slowness. > > One solution is to simply remove analyze_483s from sipx-snapshot. > > Another would be to have a version that runs much faster by restricting > its attention to a suitably small tail section of the logs. > > Another solution would be to do a quick search for the relevant error > codes but not to do any sophisticated analysis of the cause.
I'd suggest removing it from sipx-snapshot, and replace it with a version to be run separately that takes a snapshot as input. Looping requests appear to be a much smaller problem since the fixes to the proxy to detect them were added in 4.0; there are still ways to fool those checks, but they're much harder to do. _______________________________________________ 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/
