<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
try setting again the missed calls flag for each step of serial
forking -- I cannot remember by hart if it needs rearming or not...<br>
<br>
Alternative, try to use acc_db_request(...) to missed_calls table in
failure route.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
On 4/2/12 3:52 PM, Stephen Dodge (Bistech) wrote:
<blockquote
cite="mid:63C98A4100A7D34C9D3B85021AA8F0EA149DBFA3E9@BIS-EXS01-VIC-V.office.bistech.co.uk"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We currently use the acc module to capture
information to generate CDR missed call info.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have now introduced serial forking and I
would like to see if I can improve how accounting is working
for missed calls.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am using the following configuration.<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:9.0pt;mso-fareast-language:EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;mso-fareast-language:EN-GB"># turn
accounting on for all new calls<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;mso-fareast-language:EN-GB"> if
(is_method("INVITE")){<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;mso-fareast-language:EN-GB">
setflag(1); # do accouting<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;mso-fareast-language:EN-GB">
setflag(2); # missed calls<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;mso-fareast-language:EN-GB">
record_route();<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;mso-fareast-language:EN-GB"> }<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;mso-fareast-language:EN-GB"># Handle
requests within SIP dialogs<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">route[WITHINDLG]
{<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> if
(has_totag()) {<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
# sequential request withing a dialog should<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
# take the path determined by record-routing<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
if (loose_route()) {<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
if (is_method("BYE")){<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
setflag(1); # do accounting<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
setflag(3); # even if the
transaction fails<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
xdbg("## BISNET ## - RTPPROXY CHECK \n");<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
# clear any rtpproxy sessions in progress<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
unforce_rtp_proxy();<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">
} <o:p>
</o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal">I’ve noticed that accounting for missed
calls is generated for the main branch (1<sup>st</sup>
destination) only, whether this is a 486 response or a 408 on
expiry of the ‘fr_inv_timer’. After a receiving a failure
another destination is created/tried by the script, we are
allowing up to 4 serial forks. I do see the 183 message for
each fork and if the call is answered then the acc table is
updated correctly.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">How can I log the missed call response for
each fork, or only log the final failure message for the call?
Logging failed transactions seems to put them into the main
acc table and not the missed call table which I would have
expected.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Steve.<o:p></o:p></p>
</div>
<br>
<hr>
<font color="Gray" face="Arial" size="1">Information in this
message, including any attachments, is confidential to the
person to whom it is addressed and may be legally privileged. If
you are not the intended recipient please notify the sender and
delete the message from your system. Please note that Bistech
Group plc, Bistech plc, Bisnet Limited and the sender do not
accept any responsibility for viruses. It is your responsibility
to check the e-mail and any attachments for viruses. Calls may
be monitored and recorded.<br>
</font>
<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
Kamailio Advanced Training, April 23-26, 2012, Berlin, Germany
<a class="moz-txt-link-freetext" href="http://www.asipto.com/index.php/kamailio-advanced-training/">http://www.asipto.com/index.php/kamailio-advanced-training/</a></pre>
</body>
</html>