[OpenSIPS-Users] Removing ISUP part from sip dialog

[Arto Kuiri]

Hi Alexey,

I did this with t_on_reply(). Something like this:

route {
       if (has_totag()) {
                # sequential requests within a dialog should
                # take the path determined by record-routing
                if ($si=="10.10.20.20") {
                        xlog ("Removing ISUP body part in sequential requests to host which dont want it...\n");
                        remove_body_part("application/isup");
                        t_on_reply("reply_normal_sip_leg");
                }
        }
       if (is_method("INVITE") && ($si=="10.10.20.20") ) {
                xlog ("Routing INVITE \n");
                # telecom trunk  - outbound calls
                rewritehostport("195.***.***.66:5060");
                # Do cut SIP-T, here it working
                remove_body_part("application/isup");
                xlog ("And activate topology hiding B2B\n");
                b2b_init_request("top hiding");
                exit; #do not forward this request, another on will be generated

        }

}
onreply_route[reply_normal_sip_leg] {
              remove_body_part("application/isup");
}


-Arto

________________________________
Lähettäjä: Users <users-bounces at lists.opensips.org> käyttäjän Alexey Hamstr <homstr at gmail.com> puolesta
Lähetetty: torstai 29. heinäkuuta 2021 0.21
Vastaanottaja: OpenSIPS users mailling list <users at lists.opensips.org>
Aihe: Re: [OpenSIPS-Users] Removing ISUP part from sip dialog

Hi Vlad,
Thankyou for response
I'm saying that i need to remove the ISUP not only in INVITE method, but in the whole dialog
now i have in script
route {
       if (has_totag()) {
                # sequential requests within a dialog should
                # take the path determined by record-routing
                if ($si=="10.10.20.20") {
                        xlog ("Removing ISUP body part in sequential requests to host which dont want it...\n");
                        remove_body_part("application/isup");
                }
        }
       if (is_method("INVITE") && ($si=="10.10.20.20") ) {
                xlog ("Routing INVITE \n");
                # telecom trunk  - outbound calls
                rewritehostport("195.***.***.66:5060");
                # Do cut SIP-T, here it working
                remove_body_part("application/isup");
                xlog ("And activate topology hiding B2B\n");
                b2b_init_request("top hiding");
                exit; #do not forward this request, another on will be generated

        }

}

This code removes the ISUP part from the INVITE request, from  10.10.20.20  to the upper trunk but when I receive the 180 ringing signal with the ISUP part I need to remove it too.

Regards, Alexey.


ср, 28 июл. 2021 г. в 19:46, Vlad Patrascu <vladp at opensips.org<mailto:vladp at opensips.org>>:

Hi Alexey,

The remove_body_part() function should work for any method and replies as well. So are you saying that you have actually tried the function and it has no effect ?

Regards,

--
Vlad Patrascu
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 28.07.2021 18:15, Alexey Hamstr wrote:
good day.
Could anybody advise me if it is possible to remove ISUP part from whole SIP dialogue
Now I have only found that there is no problem to remove it from the common methods
like
        if (is_method("INVITE") ) {
                remove_body_part("application/isup");
        }
but i see ISUP part in the 180 or 186 messages or in the BYE method

Thanks.



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


_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210729/e14645b6/attachment-0001.html>