<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;" class=""><div class="">Hello Daniel,</div><div class=""><br class=""></div><div class="">Thanks for your reply, i saw your thread, it seemed to be solved with last updates, so i was confident in keeping trying… :)</div><div class=""><br class=""></div><div class="">So i’m wondering what is the best solution for topology hiding.</div><div class=""><br class=""></div><div class="">It is changing from time to time:</div><div class=""><br class=""></div><div class="">- Kamailio + Freeswitch : but in this case, outgoing requests are done with freeswitch which seems much less performant than Kamailio for gateway dispatching according to their availability, their load and so on</div><div class="">- Kamailio + SEMS SBC module : but it seems to be no more maintained (replaced by commercial ABC SBC from TRAFOS)</div><div class=""><br class=""></div><div class="">Kamalio is very good for a lot of things, and would be perfect if it might better manage topology hiding, as TOPOS begin to be able to do.</div><div class=""><br class=""></div><div class="">In my case i suppose that is related to topos not to manage multiple branches, or more precisely, not doing its direction detection, that seems to be the most influencing parameter for him to know which domain to use on forwarder requests.</div><div class="">As, if i well understood, re-invite is an new branch, or maybe there is something to do in the routes to help TOPOS knowing what to do…</div><div class=""><br class=""></div><div class="">Maybe Daniel (miconda) has some ideas on that, as we already fixed some TOPOS problems in the past…</div><div class=""><br class=""></div><div class="">Best regards</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><blockquote type="cite" class="">Date: Fri, 30 Dec 2016 10:23:45 +0100<br class="">From: Daniel Tryba <<a href="mailto:d.tryba@pocos.nl" class="">d.tryba@pocos.nl</a>><br class="">To: "Kamailio (SER) - Users Mailing List"<br class=""><span class="Apple-tab-span" style="white-space: pre;"> </span><<a href="mailto:sr-users@lists.sip-router.org" class="">sr-users@lists.sip-router.org</a>><br class="">Subject: Re: [SR-Users] TOPOS contact issue on RE-INVITE<br class="">Message-ID: <<a href="mailto:20161230092344.GN31818@office.pocos.nl" class="">20161230092344.GN31818@office.pocos.nl</a>><br class="">Content-Type: text/plain; charset=us-ascii<br class=""><br class="">On Thu, Dec 29, 2016 at 09:45:39PM +0100, Daren FERREIRA wrote:<br class=""><blockquote type="cite" class="">I wonder if that is a bug, related to RE-INVITE, or if there is any variable i can change to say topos which domain to be advertised on Contact headers?<br class=""></blockquote><br class="">I encountered the same problem.<br class=""><a href="http://lists.sip-router.org/pipermail/sr-users/2016-September/094403.html" class="">http://lists.sip-router.org/pipermail/sr-users/2016-September/094403.html</a><br class=""><br class="">The topos module is a very nice feature of 4.4 (and the only reason I<br class="">consider updating) but it is to new and buggy for production. <br class=""><br class=""><br class=""></blockquote></body></html>