<html><head></head><body bgcolor="#FFFFFF"><div>Forgot to say that you should also look at failed transaction flag parameter in acc, it should handle your needs, iirc.<br><br>Daniel-Constantin Mierla<div><a href="http://www.asipto.com">http://www.asipto.com</a></div></div><div><br>On 10 Nov 2012, at 08:41, Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div>Hello,</div><div><br></div><div>With latest stable you should be able to execute acc_db_request() for the reply in onreply_route. Then it should take the totag from reply.</div><div><br></div><div>When doing in failure route, it processes the incoming invite that has no totag.</div><div><br></div><div>Cheers,</div><div>Daniel<br><br>--<br>Daniel-Constantin Mierla<div><a href="http://www.asipto.com">http://www.asipto.com</a></div></div><div><br>On 8 Nov 2012, at 10:17, Uri Shacked <<a href="mailto:ushacked@gmail.com">ushacked@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div dir="ltr"><div><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">Hi,</span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">OK, i do not use drop reply.</span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">I do fork the call to the secondary
destination.</span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">Still, I need this (busy/no_answer)
reply to be inserted into the acc table.</span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">Ho do i do that?</span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">I tried acc_db_request() but the
to_tag is missing and the sip_code is missing as well. </span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">How do i force the sip_code to be
the one i generated or received? how do i use the to_tag from the last reply i
got (183 for example)?</span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">I know i can probably save the to_tag
and the sip_code, use update with sqlops or on the other hand do everything in
the database afterwards - but this is very tricky and i think not efficient.</span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">So, any way to write the reply i do
not send to the caller to the DB with the 183 to_tag and the relevant sip_code?</span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">Thanks,</span></p><font size="3" face="Times New Roman">
</font><p style="margin:0cm 0cm 0pt;line-height:normal" class="MsoNormal"><span style="font-family:"Times New Roman","serif";font-size:12pt">Uri</span></p><font size="3" face="Times New Roman">
</font></div><div><br><br> </div><div class="gmail_quote">On Wed, Nov 7, 2012 at 7:35 PM, Uri Shacked <span dir="ltr"><<a href="mailto:ushacked@gmail.com" target="_blank">ushacked@gmail.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
<p>Thanks.<br>
I am doing the reroutes on the failure route. I am using drop reply to prevent the caller from receiving the 4xx reply from the first destination. If i would just t_relay with the new deatination, the 4xx will not be forward to the caller?</p>
<div class="gmail_quote">בתאריך 7 בנוב 2012 18:46, מאת "Klaus Darilion" <<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@pernau.at</a>>:<div><div class="h5"><br type="attribution">
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
As I said I can not comment on the accounting, but dropping replies to forward the request to another destination is the wrong approach. Sequential forking should be done in a failure route.<br>
<br>
Klaus<br>
<br>
On 07.11.2012 17:31, Uri Shacked wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
So if I wont use the drop reply I might get what I need?<br>
<br>
בתאריך 7 בנוב 2012 18:10, מאת "Klaus Darilion"<br>
<<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@pernau.at</a> <mailto:<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@<u></u>pernau.at</a>>>:<br>
<br>
Ingoring accounting, such "sequential forking" scenarios are usually<br>
solved by having the forkin logic in a failure-route.<br>
<br>
- 1st callee sends 486<br>
- failure route is executed, if winning response is 486, set the new<br>
destination and t_relay().<br>
<br>
I do not know how this single transaction with 2 branches is<br>
reflected in the acc table, but I guess you can implement any acc<br>
behavior using manual accounting.<br>
<br>
regards<br>
Klaus<br>
<br>
On 07.11.2012 16:29, Uri Shacked wrote:<br>
<br>
To be more accurate - I am using the "t_set_fr()" it generates<br>
408 and<br>
sends cancel to the destination.<br>
<br>
This is the case that i do not see a final reply for the first<br>
invite.<br>
<br>
<br>
<br>
On Wed, Nov 7, 2012 at 5:24 PM, Uri Shacked <<a href="mailto:ushacked@gmail.com" target="_blank">ushacked@gmail.com</a><br>
<mailto:<a href="mailto:ushacked@gmail.com" target="_blank">ushacked@gmail.com</a>><br>
<mailto:<a href="mailto:ushacked@gmail.com" target="_blank">ushacked@gmail.com</a> <mailto:<a href="mailto:ushacked@gmail.com" target="_blank">ushacked@gmail.com</a>>>> wrote:<br>
<br>
Hi,<br>
I am trying to make an option of "route when no answer" or<br>
" route<br>
when busy".<br>
What I am doing is checking the reply and if "busy", for<br>
example, I<br>
use "t_drop_replies". Then, I set the new number and<br>
route[relay] again.<br>
On the accdb table, I get the first invite with 183 and<br>
after that<br>
the second invite with 183 and with 200.<br>
I would like to do exactly what i do, but would like to see<br>
on the<br>
accdb the 486 reply from the first invite.<br>
how do i do it?<br>
BR,<br>
Uri<br>
<br>
<br>
<br>
<br>
______________________________<u></u>___________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users<br>
mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a> <mailto:<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-<u></u>router.org</a>><br>
<a href="http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users" target="_blank">http://lists.sip-router.org/__<u></u>cgi-bin/mailman/listinfo/sr-__<u></u>users</a> <<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>users</a>><br>
<br>
</blockquote>
</blockquote></div></div></div>
</blockquote></div><br></div>
</div></blockquote></div></blockquote></body></html>