I was asking you to call do_accounting() in failure route, for each leg.

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 01/16/2017 12:02 PM, Khalil Khamlichi wrote:
sorry mistype, I am calling do_accounting() twice.

On Mon, Jan 16, 2017 at 9:47 AM, Khalil Khamlichi <[email protected] <mailto:[email protected]>> wrote:

    thanks for your much appreciated help,
    I am calling do_routing twice.

    Here is my actual opensips.cfg :

    route {
    ...
    ...

    ...
    ...
            if (has_totag()) {
    # sequential request withing a dialog should
    # take the path determined by record-routing
                   if (loose_route()) {

    # validate the sequential request against dialog
                           if ( $DLG_status!=NULL &&
    !validate_dialog() ) {
     xlog("In-Dialog $rm from $si (callid=$ci) is not valid according
    to dialog\n");
                           }

                           if (is_method("BYE")) {
    # do accounting even if the transaction fails
     do_accounting("db|log","failed|missed",);
                           } else if (is_method("INVITE")) {
    # even if in most of the cases is useless, do RR for
    # re-INVITEs alos, as some buggy clients do change route set
    # during the dialog.
     record_route();
                           }
    ...
    ...

    ...
    ...
            $acc_extra(gwid)=$avp(gw_id);

           t_on_failure("GW_FAILOVER");

           do_accounting("db|log","cdr|missed",);
    #NAT
           if (isbflagset(NAT)) setflag(NAT);
    #NAT
           route(RELAY);
    }

    # END OF MAIN ROUTE


    On Mon, Jan 16, 2017 at 8:51 AM, Răzvan Crainea
    <[email protected] <mailto:[email protected]>> wrote:

        Hi, Khalil!

        Did you try to call the do_accounting() function for each leg
        going to the next gateway?

        Best regards,

        Răzvan Crainea
        OpenSIPS Solutions
        www.opensips-solutions.com <http://www.opensips-solutions.com>

        On 01/15/2017 12:24 AM, Khalil Khamlichi wrote:
        Hi,
        I am testing opensips 2.2, 2.3 I have tried to configure acc
        module to save to db failed calls on drouting configuration,
        I have found that it does save only the first failed call
        (that is the first gateway) it does not save to database any
        other failures on second and third gateways that are tried
        for the call.
        is this the expected behavioure ?
        Thanks for your help.

        regards,
        kh


        _______________________________________________
        Users mailing list
        [email protected] <mailto:[email protected]>
        http://lists.opensips.org/cgi-bin/mailman/listinfo/users
        <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
        _______________________________________________ Users mailing
        list [email protected]
        <mailto:[email protected]>
        http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to