<HTML><BODY>Thank you very much.<br>And that is great we fixed documentation issue )<br><br><br><blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">
Пятница, 7 сентября 2018, 16:04 +03:00 от Henning Westerholt <hw@kamailio.org>:<br>
<br>
<div id="">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div>
<base target="_self" href="https://e.mail.ru/">
<div id="style_15363254860000000101_BODY">Am Freitag, 7. September 2018, 14:48:01 CEST schrieb Konstantin Polyakov:<br>
> In my configuration file I print into the log information about each SIP<br>
> message transferred by Kamailio. For example, xlog("L_NOTICE", "Request:<br>
> $rm CSeq:$cs CID:$ci from $si:$sp\n");<br>
> <br>
> Request: ACK CSeq:18467 CID:473ae5eb58f9b271 from 192.168.158.139:5060<br>
> <br>
> So when we want to find message flow which belongs to some call, we need<br>
> just grep by Call-Id.<br>
> <br>
> The problem is that messages generated by Kamailio are not passed<br>
> through request_route function of configuration script. So script writer<br>
> cannot log such messages.<br>
> <br>
> My question - is there way to log messages sent by Kamailio itself?<br>
<br>
Hello,<br>
<br>
have a look to the "failure_route" and "sl/tm:local-reponse" route <br>
functionality in the example cfg or in the sl/tm module READMEs. There is some <br>
documentation about this missing in tm, I will just add this.<br>
<br>
This routes allows you to process failures (including local ones) and also <br>
local generated responses.<br>
<br>
Best regards,<br>
<br>
Henning<br>
<br>
-- <br>
Henning Westerholt<br>
<a href="https://skalatan.de/blog/" target="_blank">https://skalatan.de/blog/</a><br>
</div>
<base target="_self" href="https://e.mail.ru/">
</div>
</div>
</div>
</blockquote>
<br>
<br>С уважением,<br>Константин Поляков.<br></BODY></HTML>