Same as with any other daemon - redirect stdout/stderr into whatever logging system is used. SystemD does that automatically. In a shellscript-style supervisor, "logger" tool would come in handy:
pcapsipdump doesn't emit all that many messages though, even at verbosity level 3, which is the most verbose.
On the other hand, if you want to have a transaction log, for example CDR, or registration log - have a look at the trigger system (-t option). Right now it can only do things when .pcap file is opened/closed, but it should be easy to extend that to individual SIP messages.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same as with any other daemon - redirect stdout/stderr into whatever logging system is used. SystemD does that automatically. In a shellscript-style supervisor, "logger" tool would come in handy:
( pcapsipdump -f other-options-go-here | logger -t pcapsipdump ) &pcapsipdump doesn't emit all that many messages though, even at verbosity level 3, which is the most verbose.
On the other hand, if you want to have a transaction log, for example CDR, or registration log - have a look at the trigger system (-t option). Right now it can only do things when .pcap file is opened/closed, but it should be easy to extend that to individual SIP messages.