<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
there is no particular reason to avoid extending the code so that
onsend_route is executed for replies. It wasn't done because no
developer/contributed needed it (or didn't make the code public).<br>
<br>
I had it in mind, but lack of time and no real need for myself set
lower priority.<br>
<br>
If Marius has a patch, once we branch the 3.3 series, he can put it
on git master. Meanwhile he can share the patch as he wants, by
tracker, mailing list or personal branch...<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 5/14/12 8:00 PM, Konstantin M.
wrote:<br>
</div>
<blockquote
cite="mid:CAEYtTzcn0__iTkp1RcP39sAfLdK8RQU0zF+aiYduh88s=4j71Q@mail.gmail.com"
type="cite">Hi Marius,<br>
<br>
My opinion that a replies should be routed to onsend_route after
onreply_route in order unless they are dropped in onreply_route.<br>
It's by a common sense I think. All the traffic that is being
sent/replied/forwarded and so on (in a short, all outgoing
traffic) should trigger some callback.<br>
A good point to use onsend_route for replies/forwardings/etc too I
think.<br>
<br>
There is a good reason (at least to me) which I need to see/parse
them: my outgoing provider has a highly unwanted feature to us:
forked calls.<br>
I have some program which is analyzing a remote leg connection
state (no answer/busy/reorder, etc...) and this app is also
analyzing <br>
all RTP which are sending within SDP on 180/181/183 messages.
Let's say that Telco can send a multiple 183 SDP with a different
IP/audio ports (c=/m=)<br>
and our application (which hasn't support for forking calls) is
receive a multiple rtp streams to the same rtp port.<br>
Sure thing I did a proper logic to drop >1 of 180/181/183 sdp
with a different contact info but I need to capture all the
outgoing traffic<br>
that is routing to outbound from kamailio.<br>
I have to use wireshark just to see which replies are being set
instead of just log them into a syslog/file.<br>
<br>
Could you please share with me that patch ?<br>
<br>
Thanks,<br>
<br>
<br>
<br>
<br>
<br>
<div class="gmail_quote">2012/5/14 Marius Zbihlei <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:marius.zbihlei@1and1.ro"
target="_blank">marius.zbihlei@1and1.ro</a>></span><br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">Hello, <br>
<br>
Normally, onsend_route is not triggered for replies, only
for messages. If there are some good reasons behind it, I
don't know, as we have a simple patch that enables this (we
are reviewing it before pushing it to upstream). Of course,
no changes to the messages/replies are permitted ...<br>
<br>
So again, is there a cause why onsend_route is not triggered
for replies atm?<br>
<br>
<span class="HOEnZb"><font color="#888888">
<pre cols="72">--
Zbihlei Marius
Head of
Linux Development Services Romania
1&1 Internet Development srl Tel KA: 754-9152
Str Mircea Eliade 18 Tel RO: <a moz-do-not-send="true" href="tel:%2B40-31-223-9152" value="+40312239152" target="_blank">+40-31-223-9152</a>
Sect 1, Bucuresti mailto: <a moz-do-not-send="true" href="mailto:marius.zbihlei@1and1.ro" target="_blank">marius.zbihlei@1and1.ro</a>
71295, Romania
</pre>
</font></span></div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a></pre>
<br>
<br>
</body>
</html>