Hey gents,
In relation to my attempts to get transaction logging successful, I'm curious to know when transaction logging triggers.
My current theory is that something I'm doing in my SIPp uac test messages (what's being sent to Kamailio) is preventing the transaction from fully completing and thus preventing logging.
I'm currently setting up an Asterisk box to test this theory, but I'd still like to know more about this and see if I can understand more of what's going on under the hood.
Thanks in advance,
Ryan Brindley
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
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 abalashov@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
but seriously Alex, thank you for the recommendation. It is greatly appreciated :)
Ryan Brindley Software Development Officer Stratics Networks, Inc. 1.866.635.6918 x108
On Mon, Jan 26, 2015 at 6:31 PM, Ryan Brindley ryan@straticsnetworks.com wrote:
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 abalashov@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
Easy to use, obvious? :-) Ahahaha! This is Kamailio, come on.
But seriously, xlog() is the logging feature, and it is easy to use:
route { xlog("L_INFO", "$ci: Message $rm $ru received from $si:$sp\n"); }
onreply_route { xlog("L_INFO", "Reply '$rs $rr' ($rm) from $si:$sp seen\n"); }
The problem is that you were under the misapprehension that the 'acc' module is the logging facility, when in fact it is the accounting module designed to generate CDRs--of a sort.
The fact that this distinction was not obvious is in no way your fault. It's just the trials and tribulations of Kamailio documentation. Hopefully the new book will remedy that.
-- Alex
On 01/26/2015 07:31 PM, Ryan Brindley wrote:
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.
Well, to my credit, i'm not just trying to log anything. I'm actually trying to log billing-related material -- every leg of a call, success or failure.
I just want to log it to a file and i assumed the transaction module had logging and then that acc's transaction logging would be the best/proper approach as I've seen/done in previous kam installs. This one just isn't playing nice.
Ryan Brindley Software Development Officer Stratics Networks, Inc. 1.866.635.6918 x108
On Mon, Jan 26, 2015 at 6:37 PM, Alex Balashov abalashov@evaristesys.com wrote:
Easy to use, obvious? :-) Ahahaha! This is Kamailio, come on.
But seriously, xlog() is the logging feature, and it is easy to use:
route { xlog("L_INFO", "$ci: Message $rm $ru received from $si:$sp\n"); }
onreply_route { xlog("L_INFO", "Reply '$rs $rr' ($rm) from $si:$sp seen\n"); }
The problem is that you were under the misapprehension that the 'acc' module is the logging facility, when in fact it is the accounting module designed to generate CDRs--of a sort.
The fact that this distinction was not obvious is in no way your fault. It's just the trials and tribulations of Kamailio documentation. Hopefully the new book will remedy that.
-- Alex
On 01/26/2015 07:31 PM, Ryan Brindley wrote:
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.
-- 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
-
Alex Balashov -
Ryan Brindley