Re: [SR-Users] How to easily remove top most header and set destination uri

Hello, I found the problem. I am sending Refer request with SIPP so writing wrong R-URI name address that is already responsible Proxy instead of B2Bua contact name address. Thus , loose_route function re-write RURI and removed top most route header as specified RFC 3261 16.12 Thanks Yasin CANER ________________________________ From: sr-users &lt;sr-users-bounces(a)lists.kamailio.org&gt; on behalf of Alex Balashov &lt;abalashov(a)evaristesys.com&gt; Sent: Friday, February 22, 2019 4:21 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] How to easily remove top most header and set destination uri Hi, First, a proxy should only remove the topmost Route headers whose URI domains correspond to addresses the proxy perceives to be its own, not another element’s. Are you sure that is not a possibility in your case? Second, the loose_route() should set the network and transport-layer next-hop destination ($du) to the next Route hop. However, if another Route hop is not present because all of them have been consumed by the proxy on the basis that the proxy perceives them to correspond to itself, then it will consume the RURI domain to determine the final hop. I think there is something missing with regard to the actual content of the Route hops and their relationship to your Kamailio instance. — Sent from mobile, with due apologies for brevity and errors. On Feb 22, 2019, at 8:01 AM, YASIN CANER <caner_yaso@hotmail.com<mailto:caner_yaso@hotmail.com>> wrote: Hello, I have trouble with REFER method that has to-tag and Route header , more than one. When it pass loose_route() method , loose_route function remove all route headar then sets RURI with top most Route. Is there a function that removing own route header and sets destination uri ($du) with top most uri. Best Regards. Yasin CANER https://tools.ietf.org/html/rfc3515 2.6<https://tools.ietf.org/html/rfc3515#section-2.6> Behavior of SIP Proxies SIP proxies do not require modification to support the REFER method. Specifically, as required by [1<https://tools.ietf.org/html/rfc3515#ref-1>]1>], a proxy should process a REFER request the same way it processes an OPTIONS request. For example, ---------->mykamailio@test2.test----------->>nextroute@test3.test------> 1 -- REFER : sip:alice@test.test ... Route:<sip:mykamailio-local@test2.test;lr>,<sip:nextroute@test3.test;lr>,<sip:nextroute2@test4.test> To: <>;tag=asdads From:<>;tag=asd123 --- 2 - After Kamailio Process --- REFER : sip:alice@test.test ... <sip:nextroute@test3.test>,<sip:nextroute2@test4.test> To: <>;tag=asdads From:<>;tag=asd123 _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users