Vlad;<br><br>In not seeing the forest for the trees I missed that !loose_route() call, very sloppy on my part. I was also not fully versed in how this mechanism worked to begin with, however, but am now.<br><br>Testing shows this was, indeed, the issue. I thank you again, very much, for your time in helping me out with my problem here.<br>
<br>Have a wonderful week all;<br><br> - Jock<br><br><br><div class="gmail_quote">On Tue, Sep 6, 2011 at 10:45 AM, Vlad Paiu <span dir="ltr"><<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><u></u>
<div bgcolor="#ffffff" text="#000000">
Hello,<br>
<br>
In the latest pastebin config you provided the error is still
present. <br>
You have<br>
if(!is_method("REGISTER")) {<br>
if(loose_route()) {<br>
route(1);<br>
}<br>
}<br>
<br>
So for ACKs, you will do loose_route(), it will succeed and then you
will call route(1), which calls rewritehostport() . So basically,
nothing was different compared to your previous scenario, you still
rewrite the RURI for ACKs.<br>
<br>
Please take a closer look at the default scripting scenario that
comes with OpenSIPS. <br>
Basically, the sequential requests processing ( ACKs, ReINVITEs, etc
) should look something like :<br>
<br>
if (has_totag()) {<br>
# sequential request withing a dialog should<br>
# take the path determined by record-routing<br>
if (loose_route()) {<br>
# route it out to whatever destination was set by
loose_route()<br>
# in $du (destination URI).<div class="im"><br>
if (!t_relay()) {<br>
sl_reply_error();<br></div>
};<br>
exit;<br>
} else {<br>
if ( is_method("ACK") ) {<br>
if ( t_check_trans() ) {<br>
# non loose-route, but stateful ACK; must be an
ACK after-<br>
# a 487 or e.g. 404 from upstream server<br>
t_relay();<br>
exit;<br>
} else {<br>
# ACK without matching transaction -><br>
# ignore and discard<br>
exit;<br>
}<br>
}<br>
sl_send_reply("404","Not here");<div class="im"><br>
}<br>
}<br>
<br>
Regards,<br>
<pre cols="72">Vlad Paiu
OpenSIPS Developer</pre>
<br></div><div><div></div><div class="h5">
On 09/06/2011 06:17 PM, Jock McKechnie wrote:
</div></div><blockquote type="cite"><div><div></div><div class="h5"><br>
<br>
<div class="gmail_quote">On Mon, Sep 5, 2011 at 2:49 AM, Vlad Paiu
<span dir="ltr"><<a href="mailto:vladpaiu@opensips.org" target="_blank">vladpaiu@opensips.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div bgcolor="#ffffff" text="#000000"> Hello Jock,<br>
<br>
I have taken a look at the SIP trace and seems that the
proxy behind Charlie, 192.168.1.1, does some weird stuff to
the ACK. More specifically, it mangles the domain part of
the RURI, so that it points to 192.168.1.4. When Charlie (
192.168.1.4 ) receives this ACK it sees itself in the domain
part of the RURI, so it applies strict routing, by taking
the last route header and putting it in the RURI. This is
why you see the apparent stripping of the username part when
forwarding the ACK.<br>
<br>
I guess a good question is why are you calling <br>
rewritehostport("<a href="http://192.168.1.4:5060" target="_blank">192.168.1.4:5060</a>");
<br>
on the proxy behind Charlie ? Because this is the source of
your problem. I mean why not let the ACK get routed like
every other sequential request, via the Route header.<br>
<br>
</div>
</blockquote>
</div>
<br>
Thank you, Vlad;<br>
<br>
I think I'm following what you're explaining - I'm force-routing
the ACKs instead of letting the handler route them based by the
rules in the header itself. I changed the configuration to the
below, which should only force the INVITE to Charlie, and use a
t_relay() to handle the ACKs, et al, correctly:<br>
<br>
if (is_method("INVITE")) {<br>
# enable Record-Route<br>
record_route();<br>
route(1);<br>
}<br>
<br>
if (!t_relay()) {<br>
sl_reply_error();<br>
}<br>
<br>
Unfortunately this appears to make no difference to how the ACK's
RURI looks. I imagine I'm using the wrong method of forwarding on
the ACK?<br>
(Full config is here, should you want to see it in context: <a href="http://pastebin.com/Zntg2y95" target="_blank">http://pastebin.com/Zntg2y95</a>)<br>
<br>
Thank you, again, for your assistance and suggestions. I am
immensely grateful for all help I receive on this list.<br>
<br>
- Jock<br>
</div></div><pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<div class="im"><a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</div></pre>
</blockquote>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>