Hi,Bogdan<div><br></div><div>Thank you for your reply.</div><div><br></div><div>I have a question on your comment.</div><div><br></div><div>in RFC3261 16.12 (in the following)</div><div>The first step of proxy should lookup location table to replace request-uri if there is.</div>
<div>In my case I think proxy should first replace ACK's request uri to callee's sip identity and then go to loose_route....</div><div><br></div><div>I added lookup script before loose_route then it works.</div><div>
<br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><span class="Apple-style-span" style="font-family: iYaHei; font-size: medium; "><pre style="word-wrap: break-word; white-space: pre-wrap; ">
1. The proxy will inspect the Request-URI. If it indicates a
resource owned by this proxy, the proxy will replace it with
the results of running a location service. Otherwise, the
proxy will not change the Request-URI.
2. The proxy will inspect the URI in the topmost Route header
field value. If it indicates this proxy, the proxy removes it
from the Route header field (this route node has been
reached).
3. The proxy will forward the request to the resource indicated
by the URI in the topmost Route header field value or in the
Request-URI if no Route header field is present. The proxy
determines the address, port and transport to use when
forwarding the request by applying the procedures in [4] to
that URI.
</pre><div><br></div></span></div><div><br></div><div><br></div><div><br><div class="gmail_quote">On Thu, Jan 6, 2011 at 7:27 PM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<br>
<br>
The ACK gets to our opensips because of the Route hdr (Route: <sip:10.61.20.146;lr=on>); opensips will further route the ACK based on RURI which is "<a href="mailto:sip%3Astct_1000@siptest.org" target="_blank">sip:stct_1000@siptest.org</a>"...is this domain resolvable by DNS and pointing to callee (<a href="http://10.61.20.200:5060" target="_blank">10.61.20.200:5060</a>) ? Callee has to place in 200 OK its contact address that can be used to route back to it...so if its contact "<a href="mailto:sip%3Astct_1000@siptest.org" target="_blank">sip:stct_1000@siptest.org</a>" does not point back to callee, it is a callee issue.<br>
<br>
Regards,<br>
Bogdan<br>
<br>
fengbin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class="h5">
Hi,Mogdan,<br>
<br>
Thank you for your help.<br>
<br>
The enclosed is the pcap file.<br></div></div><div class="im">
------------------------------------------------------------------------<br>
<br>
_______________________________________________<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" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</div></blockquote><div><div></div><div class="h5">
<br>
<br>
-- <br>
Bogdan-Andrei Iancu<br>
OpenSIPS Event - expo, conf, social, bootcamp<br>
2 - 4 February 2011, ITExpo, Miami, USA<br>
<a href="http://www.voice-system.ro" target="_blank">www.voice-system.ro</a><br>
<br>
<br>
_______________________________________________<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" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>arithdon<br>
</div>