<div dir="ltr">Thanks Daniel. Config can be found here: <a href="https://gist.github.com/benlangfeld/1b61f41c31129e8f2db3">https://gist.github.com/benlangfeld/1b61f41c31129e8f2db3</a><div><br></div><div>INVITEs as provided (with a Route with two comma-separated elements) get routed via the Contact header (instead of the second Route element).</div><div><br></div><div>When I use loose_route() on the INVITE, it goes into a loop in the edge proxy (<a href="https://gist.github.com/benlangfeld/99af9045e70a9bb4eeed">https://gist.github.com/benlangfeld/99af9045e70a9bb4eeed</a>), even though the IP it selects to route to (.14) is not the same server.</div><div><br></div><div>Ben</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 4 December 2014 at 12:16, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
You should put the config somewhere for review. Note that default
kamailio.cfg ignores Route headers for initial requests. You have to
handle initial requests with loose_route().<br>
<br>
Cheers,<br>
Daniel<div><div class="h5"><br>
<br>
<div>On 04/12/14 13:35, Ben Langfeld wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">In that case the issue would have to be with the
Kamailio-based edge proxy which is not routing based on the
second Route in the list. Is that a known issue? I can provide
more details if you think I'm on the right track.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 4 December 2014 at 10:09,
Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hello,<br>
<br>
having more record-route addresses in the same header,
separated by comma, it is valid. Other headers (Via,
Record-Route, Supported, Required ...) can have same
format, it is a matter of UAC how it builds them, each
with a header name or all under same header name.<br>
<br>
Cheers,<br>
Daniel
<div>
<div><br>
<br>
<div>On 04/12/14 12:24, Ben Langfeld wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">I'm facing a problem which I believe
may be a bug in the registrar module's lookup.
When a registration comes with multiple Path
headers, these are recorded in the location table
as comma separated. When the lookup is performed
and these are used to construct the Route
header(s) on an INVITE, this comma-separated list
is not split into multiple Route headers, but
instead included verbatim in a single header.
<div><br>
</div>
<div>Here comes my theory for how this breaks my
scenario:<br>
<div><br>
</div>
<div>When the INVITE then reaches the first hop
(first Path header, also Kamailio), relay()
sees that the Route header is itself and/or
sees that there is only one Route header.</div>
<div><br>
</div>
<div>The observed result is that the first hop
then sends the INVITE directly to the Contact,
instead of via the second hop.<br>
<div><br>
</div>
<div>An example of the situation I'm facing is
shown in <a href="https://gist.github.com/benlangfeld/b374a0ce0bdb6bdc35e7" target="_blank">https://gist.github.com/benlangfeld/b374a0ce0bdb6bdc35e7</a>.</div>
</div>
</div>
<div><br>
</div>
<div>Is there a particular reason the combined
path is not split on lookup? Is this a bug /
oversight? Am I crazy?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>Ben</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><span><font color="#888888">
</font></span></pre>
<span><font color="#888888"> </font></span></blockquote>
<span><font color="#888888"> <br>
<pre cols="72">--
Daniel-Constantin Mierla
<a href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
</font></span></div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre cols="72">--
Daniel-Constantin Mierla
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
</div></div></div>
</blockquote></div><br></div>