<p dir="ltr">I had a similar problem happen behind a certain router it was the routers sip alg, try to do a wireshark behind the router if it has proper invite try disabling sip alg, if not possible change router </p>
<div class="gmail_quote">On Nov 7, 2012 8:16 PM, "Bogdan-Andrei Iancu" <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
See in the logs:<br>
<br>
Nov 7 08:58:34 opensips /usr/local/opensips_proxy_1.8.<u></u>2/sbin/opensips[8167]: DBG:uri:has_totag: totag found\<br>
Nov 7 08:58:34 opensips /usr/local/opensips_proxy_1.8.<u></u>2/sbin/opensips[8167]: ######LOG: Individuo TO_TAG\<br>
Nov 7 08:58:34 opensips /usr/local/opensips_proxy_1.8.<u></u>2/sbin/opensips[8167]: DBG:core:parse_headers: flags=200\<br>
Nov 7 08:58:34 opensips /usr/local/opensips_proxy_1.8.<u></u>2/sbin/opensips[8167]: ERROR:core:parse_nameaddr: no< found\<br>
Nov 7 08:58:34 opensips /usr/local/opensips_proxy_1.8.<u></u>2/sbin/opensips[8167]: ERROR:core:do_parse_rr_body: failed to parse name-addr\<br>
Nov 7 08:58:34 opensips /usr/local/opensips_proxy_1.8.<u></u>2/sbin/opensips[8167]: ERROR:core:do_parse_rr_body: failed to parse RR headers\<br>
Nov 7 08:58:34 opensips /usr/local/opensips_proxy_1.8.<u></u>2/sbin/opensips[8167]: DBG:core:set_err_info: ec: 1, el: 3, ei: 'error parsing RR headers'\<br>
Nov 7 08:58:34 opensips /usr/local/opensips_proxy_1.8.<u></u>2/sbin/opensips[8167]: ERROR:rr:find_first_route: failed to parse Route HF\<br>
Nov 7 08:58:34 opensips /usr/local/opensips_proxy_1.8.<u></u>2/sbin/opensips[8167]: DBG:rr:loose_route: There is no Route HF\<br>
<br>
<br>
The Route header in the INVITE is wrong. Instead of:<br>
Route: sip:10.9.6.3<br>
<br>
You should have:<br>
Route: <sip:10.9.6.3><br>
<br>
That is the correct SIP format according to SIP RFC3261 :<br>
<br>
Route = "Route" HCOLON route-param *(COMMA route-param)<br>
route-param = name-addr *( SEMI rr-param )<br>
name-addr = [ display-name ] LAQUOT addr-spec RAQUOT<br>
<br>
So, the caller party (<a href="http://10.9.6.40:5060" target="_blank">10.9.6.40:5060</a>) is broken :)<br>
<br>
Regards,<br>
<br>
Bogdan-Andrei Iancu<br>
OpenSIPS Founder and Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.<u></u>com</a><br>
<br>
<br>
On 11/07/2012 10:03 AM, spady wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Bogdan, thanks for your time.<br>
<br>
Log, in debug 6, is attached as file.<br>
<br>
Regards Opnesips_log.txt<br>
<<a href="http://opensips-open-sip-server.1449251.n2.nabble.com/file/n7582829/Opnesips_log.txt" target="_blank">http://opensips-open-sip-<u></u>server.1449251.n2.nabble.com/<u></u>file/n7582829/Opnesips_log.txt</a><u></u>><br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Help-Understanding-ACK-loop-tp7582796p7582829.html" target="_blank">http://opensips-open-sip-<u></u>server.1449251.n2.nabble.com/<u></u>Help-Understanding-ACK-loop-<u></u>tp7582796p7582829.html</a><br>
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.<br>
<br>
______________________________<u></u>_________________<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-<u></u>bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<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-<u></u>bin/mailman/listinfo/users</a><br>
</blockquote></div>