Hello Daniel, No I don't want to store in pcap format, I have it already. I would like to have a text logs instead of database. About log format, I would like to have a functionality like log4cpp, for example: # Call Logging log4cplus.appender.CALL_LOG_APPENDER=log4cplus::NullAppender log4cplus.appender.CALL_LOG_APPENDER.Directory=logs/call-logs log4cplus.appender.CALL_LOG_APPENDER.ImmediateFlush=true log4cplus.appender.CALL_LOG_APPENDER.layout=log4cplus::PatternLayout log4cplus.appender.CALL_LOG_APPENDER.layout.ConversionPattern=%D{%Y-%m-%d %H:%M:%S:%%q} [%t] %p - %c : %m%n I'm a very curious why we still have so absolete logging system ? There are too many cute logging frameworks. Why we don't switch to some soft of log4c or log4cpp ? 2012/6/12 Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com>> Hello, On 6/9/12 8:59 PM, Konstantin M. wrote: Hello, Is it possible to log SIP sessions using sipcapture module to log files by log format instead of database ? what do you mean by log format? If you just want to store pure pcap files, then you can use tools such as ngrep, wireshark/tshark. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hello Daniel, 2012/6/12 Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com>> Hello, I am a bit confused now. sipcapture role is to store the SIP signaling messages in database for the purpose of later analysis -- you can export pcap from the database later. Well, I don't have enough experience with sipcapture module but (maybe I'm wrong) I don't think it is a good idea to store so huge data in mysql in high loading environment. Rather that I would suggest to keep them in some flat databases, like mongo, redis, kassandra, etc... Eventually, by looking to the sources, I don't think there is another way except mysql... What is the obsolete logging system you think about? If you look to log custom info messages, then see the xlog module: * http://kamailio.org/docs/modules/3.3.x/modules_k/xlog.html You can print your own message to syslog (or stderr), in the format you wish. Yes, I'm using syslog but personally it's a backward way. Nowadays there is a lot of logging frameworks. I think that, unofficial, log4XXXX (where XXXX - one of c, cpp, java, python, etc) already a standard of logging system. When using syslog/logrotate - the only one way to modify a root settings, no way to configure only userland part by configuring a logging strategy inside application like a many software allows. Cheers, Daniel On 6/12/12 11:54 AM, Konstantin M. wrote: -- Daniel-Constantin Mierla -http://www.asipto.com http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 -http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 -http://asipto.com/u/kpw _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users