<HTML>
<HEAD>
<TITLE>Re: [SR-Users] new functionality: CDR-based accounting</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi Timo,<BR>
<BR>
I would be interested in the 1.5 backported module. Is that available for the masses?<BR>
<BR>
Thanks!<BR>
<BR>
-graham<BR>
<BR>
<BR>
On 8/4/11 1:08 AM, "Timo Reimann" <<a href="timo.reimann@1und1.de">timo.reimann@1und1.de</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
<BR>
Hi all,<BR>
<BR>
as announced quite a while ago, I finally checked in code that allows to<BR>
produce CDRs (Call Data Records) directly from SIP-Router and generate<BR>
logs accordingly.<BR>
<BR>
The main code portion resides in modules_k/acc and provides a switch to<BR>
enable basic CDR generation including start time, end time, and<BR>
duration. Analogous to the existing logging approach, you may define an<BR>
extra parameter covering to-be-included dialog pseudo-variables that<BR>
must be assigned in the configuration script. The new code will take<BR>
care of transforming the basic and custom CDR fields into CDR logs at<BR>
the end of a dialog.<BR>
<BR>
Speaking of dialogs: The implementation relies heavily on the dialog<BR>
module. It takes advantage of dialog variables introduces by Carsten<BR>
Bock and adds a few more features. Most notably, we had to change the<BR>
dialog callback signature to provide both request and response messages.<BR>
Having only one of them proved to be insufficient in certain cases; for<BR>
instance, a locally generated 408 returned a FAKED_REPLY, thus rendering<BR>
it impossible to access dialog variables through the PV framework. Other<BR>
modules using dialog callbacks have been updated along the commit,<BR>
third-party modules outside the repository will need to do so too (and<BR>
think about whether using the request or response is the Right Thing to do).<BR>
<BR>
Due to the changes brought to the dialog module, I pushed the new acc<BR>
and dialog code into a separate branch called treimann/acc-cdr. Feel<BR>
free to give it a try by consulting the updated documentation and<BR>
suggesting (or, if it's good enough, implementing :) ) improvements. A<BR>
Kamailio 1.5 backport of the code has been in usage for quite some time<BR>
with us, so generally there shouldn't be any major logical flaws.<BR>
SIP-Router certainly needs more testing, however, so I'd be glad for any<BR>
feedback. My plan is to merge the code into master branch prior to the<BR>
3.2 feature freeze, unless significant objections arise.<BR>
<BR>
Finally, big-time credits go to my co-worker Sven Knoblich who is the<BR>
main contributor of the code. He's been working on this stuff for the<BR>
past few months and dreams in CDRs by now.<BR>
<BR>
<BR>
Cheers,<BR>
<BR>
--Timo<BR>
<BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"></SPAN></FONT><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>_______________________________________________<BR>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<BR>
<a href="sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><BR>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>