Hi Alex, I got your answer about loose route earl mesagess , saved and still keeping it. I try to figure out , what s the best way handle refer message with kamailio if there is a route header.
When there is route header more than one , smth is going wrong. Today , I worked so many cases , all of them may be mixed in my mind. I will work on it again. Rfc3261 16.12<https://tools.ietf.org/html/rfc3261#section-16.12> Summary of Proxy Route Processing Best regards. Yasin C. Alex Balashov <[email protected]<mailto:[email protected]>> şunları yazdı (22 Şub 2019 16:22): 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 <[email protected]<mailto:[email protected]>> 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>], a proxy should process a REFER request the same way it processes an OPTIONS request. For example, ---------->[email protected]>>[email protected]> 1 -- REFER : sip:[email protected] ... Route:<sip:[email protected];lr>,<sip:[email protected];lr>,<sip:[email protected]> To: <>;tag=asdads From:<>;tag=asd123 --- 2 - After Kamailio Process --- REFER : sip:[email protected] ... <sip:[email protected]>,<sip:[email protected]> To: <>;tag=asdads From:<>;tag=asd123 _______________________________________________ Kamailio (SER) - Users Mailing List [email protected]<mailto:[email protected]> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List [email protected]<mailto:[email protected]> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
