Because that solution, which now sounds easy and great, was not openly obvious to me when searching through the docs and trying to determine the best way to log all transactions.
I naturally assume that the logging features in a product are relatively easy to use and configure. xlog it is. ty. Ryan Brindley Software Development Officer Stratics Networks, Inc. 1.866.635.6918 x108 On Mon, Jan 26, 2015 at 6:26 PM, Alex Balashov <abalas...@evaristesys.com> wrote: > Ryan, > > Why are you working so hard? Why don't you just use xlog() or sqlops[1] to > log whatever SIP messages you want to log, whenever you want to log them, > wherever you want to log them, into a schema of your choosing, on your > terms, and without any regard for the innards of the ACC module or worrying > about relationships between logging and transaction state? > > -- Alex > > [1] http://kamailio.org/docs/modules/4.2.x/modules/sqlops.html > > -- > Alex Balashov - Principal > Evariste Systems LLC > 235 E Ponce de Leon Ave > Suite 106 > Decatur, GA 30030 > United States > > Tel: +1-678-954-0670 > Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
