Ah, I see. Well, in that case your use of ACC makes more sense, though I still think depending on its innards incurs more work than just rolling one's own logging for such cases. That may be a controversial viewpo
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
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 se
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
wrote:
> Because that solution, which now sounds easy and great, was not openl
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.
R
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
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 th
