<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">OK, Răzvan, maybe my avp’s are null at this moment - much more important, that really sip code not presented in this row. Completely filled row for this leg creates in missed_call table. I.e. 2 rows creates for one leg with error - one in acc table and one in missed_calls.<div><br></div><div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Best regards,</div><div>Alexander Mustafin</div><div><a href="mailto:mustafin.aleksandr@gmail.com">mustafin.aleksandr@gmail.com</a></div><div><br></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br><div><div>02 дек. 2013 г., в 15:07, Răzvan Crainea <<a href="mailto:razvan@opensips.org">razvan@opensips.org</a>> написал(а):</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Hi, Alexander!<br><br>Are you sure you are populating all the multi_leg_info AVPs for each<br>leg? In your case, you have two legs, therefore you should populate each variable two times - once for the initial leg and second for the redirect.<br><br>Best regards,<br><br>Razvan Crainea<br>OpenSIPS Core Developer<br><a href="http://www.opensips-solutions.com/">http://www.opensips-solutions.com</a><br><br>On 11/30/2013 05:07 AM, Alexander Mustafin wrote:<br><blockquote type="cite">Hi, Răzvan.<br><br>Thank you for this hint!<br><br>I set multi-leg acc support now, and it’s almost works )))<br><br>1) If first GW drop my call and return error - ACC generate row in table<br>for this leg, BUT sip_code is 200 (not error code)<br>2) I set modparam("acc", "multi_leg_info»,…) with avp I would to store<br>in database, but almost all columns are empty for unsuccessfull leg -<br>for other legs they are present.<br><br><br>Best regards,<br>Alexander Mustafin<br><a href="mailto:mustafin.aleksandr@gmail.com">mustafin.aleksandr@gmail.com</a><span class="Apple-converted-space"> </span><<a href="mailto:mustafin.aleksandr@gmail.com">mailto:mustafin.aleksandr@gmail.com</a>><br><br><br><br><br>29 нояб. 2013 г., в 14:44, Răzvan Crainea <<a href="mailto:razvan@opensips.org">razvan@opensips.org</a><br><<a href="mailto:razvan@opensips.org">mailto:razvan@opensips.org</a>>> написал(а):<br><br><blockquote type="cite">Hi, Alexander!<br><br>If you want to have multiple rows for each leg, then you should use<br>multi-leg acc support[1]. Note that you should not use the CDR flag,<br>since you are doing old two-steps accounting.<br><br>[1] <a href="http://www.opensips.org/html/docs/modules/1.8.x/acc#multi-call-legs">http://www.opensips.org/html/docs/modules/1.8.x/acc#multi-call-legs</a><br><br>Best regards,<br><br>Razvan Crainea<br>OpenSIPS Core Developer<br><a href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a><br><br>On 11/28/2013 02:36 PM, Alexander Mustafin wrote:<br><blockquote type="cite">If first gateway in drouting return error - I need a CDR with sip code<br>of error. Then, if next gw is setup the call - I need a CDR, after BYE<br>message.<br><br>First attempt - generate one row INVITE in the table (with error code),<br>and second attempt generate two rows - INVITE and BYE<br><br>I believe that it should work like that!<br><br>Best regards,<br>Alexander Mustafin<br>mustafin.aleksandr@gmail.com <mailto:mustafin.aleksandr@gmail.com><br><br><br><br><br>28 нояб. 2013 г., в 15:42, Alexander Mustafin<br><mustafin.aleksandr@gmail.com <mailto:mustafin.aleksandr@gmail.com>><br>написал(а):<br><br><blockquote type="cite">Hi, Razvan!<br><br>I’m tried set ACC_FAILED in places, where call may be failed. In<br>request route too.<br><br>Best regards,<br>Alexander Mustafin<br>mustafin.aleksandr@gmail.com <mailto:mustafin.aleksandr@gmail.com><br><br><br><br><br>28 нояб. 2013 г., в 15:35, Răzvan Crainea <razvan@opensips.org<br><mailto:razvan@opensips.org>> написал(а):<br><br><blockquote type="cite">Hi, Alexander!<br><br>Have you tried setting the ACC_FAILED flag in the request route?<br><br>Best regards,<br><br>Razvan Crainea<br>OpenSIPS Core Developer<br>http://www.opensips-solutions.com <http://www.opensips-solutions.com/><br><br>On 11/28/2013 10:35 AM, Alexander Mustafin wrote:<br><blockquote type="cite">Hello!<br><br>I need to store all CDRs for all calls, but some failed calls are<br>not to<br>handled by ACC.<br><br>modparam("acc", "failed_transaction_flag", "ACC_FAILED»)<br><br>failure_route[MISSED_CALL] {<br> if (t_check_status("[4|5][0-9][0-9]")) {<br>setflag(ACC_FAILED);<br>}<br>}<br><br>But call which rejected with 503 (example) error is missed in acc<br>table.<br><br>Best regards,<br>Alexander Mustafin<br>mustafin.aleksandr@gmail.com<br><mailto:mustafin.aleksandr@gmail.com><mailto:mustafin.aleksandr@gmail.com><br><br><br><br><br><br><br>_______________________________________________<br>Users mailing list<br>Users@lists.opensips.org <mailto:Users@lists.opensips.org><br>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br><br></blockquote><br>_______________________________________________<br>Users mailing list<br>Users@lists.opensips.org <mailto:Users@lists.opensips.org><br>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br></blockquote><br></blockquote><br><br><br>_______________________________________________<br>Users mailing list<br>Users@lists.opensips.org<br>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br><br></blockquote><br>_______________________________________________<br>Users mailing list<br>Users@lists.opensips.org<br>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br></blockquote><br><br><br>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br><br></blockquote><br>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></div></blockquote></div><br></div></body></html>