[sr-dev] Suggestion: Common Log file for Sip-Router / Kamailio

[Victor Pascual Avila]

To my best knowledge this work is still in its infancy. Please check
the following link:
http://www.ietf.org/mail-archive/web/sipping/current/msg17190.html

-Victor

On Tue, Feb 2, 2010 at 5:11 PM, Iñaki Baz Castillo <ibc at aliax.net> wrote:
> Hi, in most of my deployments I see myself adding xlog lines to imitate
> an "access" log (like Apache/Nginx/Squid do).
>
> Note that this is not the same as a CDR. Also, using xlog for this purpose
> is not very cool as the logs are mixed with other logs generated by SR/Kamailio
> itself (or its modules) as warnings, errors, other custom xlog's...
>
> I'm reading a draft called "The Common Log File (CLF) format for SIP":
>
>  http://tools.ietf.org/html/draft-gurbani-sipping-clf
>
> It seems really interesting for me and I'd love to have something similar in
> SR/Kamailio.
> The only "similar" approach would be using the siptrace module storing all
> the SIP flows into database, however it's not recommended for scenarios with
> high traffic.
>
> An example of this kind of log would be the following (extracted from the
> draft):
>
>
> - Alice calls Bob.
> - The proxy does parallel forking to two locations.
> - Bob-1 replies 500.
> - Bob-2 replies 200.
> - Alice sends the ACK for the 200.
>
>
> The common log generated by the proxy would look as follows:
>
> ------------------------------------------------------------------------
> ### Received request (server transaction):
> 1230756560 192.168.1.10 - INVITE sip:bob at example.net sip:alice at example.com;tag=hy7 sip:bob at example.net 7yhgt1 at example.com - uyt67h FORK/-
>
> ### 100 replied upstream:
> 1230756560 uyt67h - 100 INVITE + -
>
> # First INVITE generated by the proxy (client transaction):
> 1230756563 - - INVITE sip:bob at home.example.net sip:alice at example.com;tag=hy7 sip:bob at example.net 7yhgt1 at example.com - uyt67h CLIENT/hb76
>
> ### Second INVITE generated by the proxy (client transaction):
> 1230756564 - - INVITE sip:bob at carphone.example.net sip:alice at example.com;tag=hy7 sip:bob at example.net 7yhgt1 at example.com - uyt67h CLIENT/hb77
>
> ### Replies received from Bob-1 and Bob-2:
> 1230756565 uyt67h hb76 100 INVITE sip:bob at example.net;tag=876v -
> 1230756565 uyt67h hb77 100 INVITE sip:bob at example.net;tag=561t -
> 1230756565 uyt67h hb76 180 INVITE sip:bob at example.net;tag=876v -
> 1230756565 uyt67h hb77 180 INVITE sip:bob at example.net;tag=561t -
> 1230756567 uyt67h hb77 182 INVITE sip:bob at example.net;tag=561t -
> 1230756568 uyt67h hb76 500 INVITE sip:bob at example.net;tag=876v -
> 1230756568 uyt67h hb77 200 INVITE sip:bob at example.net;tag=561t "sip:bob at home.example.net"
>
> ### 200 replied upstream:
> 1230756569 uyt67h - 200 INVITE sip:bob at example.net;tag=561t "sip:bob at home.example.net"
>
> ### ACK sent to Bob-1 to acknoledge the 500 response:
> 1230756569 + - ACK sip:bob at home.example.net + + + - uyt67h CLIENT/hb76
>
> ### ACK received by the proxy and relayed to Bob-2:
> 1230756570 192.168.1.10 - ACK sip:bob at home.example.net sip:alice at example.com;tag=hy7 sip:bob at example.net;tag=76y 7yhgt1 at example.com - t6y5 FORK/-
> 1230756570 - - ACK sip:bob at home.example.net sip:alice at example.com;tag=hy7 sip:bob at example.net;tag=76y 7yhgt1 at example.com - t6y5 CLIENT/hb89
> ------------------------------------------------------------------------
>
>
>
> Would make sense a SR module to achieve this purpose? Such module should
> write these logs into a file (not syslog).
>
>
> Regards.
>
>
>
>
> --
> Iñaki Baz Castillo <ibc at aliax.net>
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>



-- 
Victor Pascual Ávila