<div dir="ltr">Thank you, that makes sense now. I will keep that in mind for the future.<div>In the meantime I have raised a query with our provider.</div><div><br></div><div>Additionally, I realised this morning that at our request, our provider is sending calls to us via a domain name instead of an IP. Would that likely cause the issue even if they are using RFC 3261? I have asked for it to be removed.</div><div><br></div><div>Best regards</div><div>Mark.</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 25 Apr 2019 at 16:50, Liviu Chircu <<a href="mailto:liviu@opensips.org">liviu@opensips.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_1245809717298552556moz-cite-prefix">On 25.04.2019 17:11, Mark Farmer wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Thanks so much for helping
with this.
<div><br>
</div>
<div>I have applied the suggested config
but the result is the same. OpenSIPS
routes the RE-INVITE to itself and it
never gets routed back to the Asterisk
box.</div>
<div>If the 2nd Route header in the
RE-INVITE is the IP of the other
interface - will that not always be the
case? It's as though the 2nd Route
header needs to be changed to have the
IP of the Asterisk server.</div>
<div><br>
</div>
<div>Sanitized RE-INVITE from provider:</div>
<div><br>
</div>
<div>
<div>INVITE <a href="http://sip:asterisk@my.host.name:5060" target="_blank">sip:asterisk@my.host.name:5060</a>
SIP/2.0</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<p><tt>If OpenSIPS identifies "<a href="http://my.host.name:5060" target="_blank">my.host.name:5060</a>" as a local domain,
this will screw up the routing,<br>
as it will go from loose (RFC 3261) to strict (old, deprecated
RFC 2543 mechanism). Notice how<br>
its not preserving the R-URI when it routes to itself as should
happen with RFC 3261 routing,<br>
because it has fallen back to RFC 2543 routing.<br>
</tt></p>
<p><tt>Your provider needs to follow RFC 3261 and use as Re-INVITE
Request-URI the exact Contact<br>
advertised by the caller: <a class="gmail-m_1245809717298552556moz-txt-link-rfc2396E" href="mailto:sip:asterisk@10.98.0.102:5060" target="_blank"><sip:asterisk@10.98.0.102:5060></a>,
and not confuse your routing engine<br>
with a random target such as:</tt><tt> INVITE
<a class="gmail-m_1245809717298552556moz-txt-link-abbreviated" href="mailto:sip:asterisk@my.host.name:5060" target="_blank">sip:asterisk@my.host.name:5060</a>.</tt></p>
<pre class="gmail-m_1245809717298552556moz-signature" cols="72">--
Liviu Chircu
OpenSIPS Developer
<a class="gmail-m_1245809717298552556moz-txt-link-freetext" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
</div>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Mark Farmer<br><a href="mailto:farmorg@gmail.com" target="_blank">farmorg@gmail.com</a></div>