On Mon, 2009-06-08 at 09:54 -0400, Damian Krzeminski wrote: > Scott Lawrence wrote: > > On Sun, 2009-06-07 at 22:41 +0200, Alberto wrote: > >> Hi, > >> i was reading an old post where Dale was explaining how to extract a > >> single call from logs: > >> > >> /usr/bin/merge-logs --containing=<call-id> /var/log/sipxpbx/sip*.log > >> > >> where <call-id> is identifying a single call. > >> > >> Don't know if current CDR is actually storing call-id but the idea might > >> be quite simple. Why don't just add a link/button for every cdr record > >> to download the sipxviewer xml file of a single call? It's just a matter > >> of storing the call-id in the db. > >> > >> I would be simply ... lovely! Any thoughts? > > > > Vote for it: > > http://track.sipfoundry.org/browse/XX-5491 > > > > > > call-id is already in DB - it's just a question of calling merge-logs > script from sipXconfig. > > I think it's trivial in a single server setup. Does anybody know how it can > be made to work in HA?
Sure - sipXconfig just needs to invoke a command on each distributed server that scans the logs on that server, extracting all relevant messages, and then combine them with those from the local server. While the mechanics might be somewhat different, the basic logic needed is all in the sipx-trace script (sipx-trace uses ssh to do the remote command execution - a solution integrated into sipXconfig would probably use some query executed through sipXsupervisor). _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
