<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Funny...actually the problem was not that you had a FQDN in
domain contact, but because that FQDN was considered by opensips
as a local domain.<br>
<br>
So, when openspis received the ACK with that contact in RURI,
opensips thought is it his RR header and was acting as prev hop
being a strict router....and this was messing up the entire
routing.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<br>
On 08/31/2012 03:53 PM, Kevin Mathy wrote:
<blockquote
cite="mid:CAOmzhXkvsQdpAB8-LvhbwQEdLXAMOAWQ6cH_2n2zBW23kT+W-Q@mail.gmail.com"
type="cite"><span style="color: rgb(34, 34, 34); font-family:
arial,sans-serif; font-size: 13px; background-color: rgb(255,
255, 255);">Hi Bogdan, </span>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">
<br>
</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">We've
got some news about our problem with record-routes.</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">
</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">In fact,
it seems that if we change Contact header sent by customer's
device, everything work fine. Explanations :</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);"><br>
</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">
Before, in all message sent by customer's device, particularly
200OK, Contact header was like <b>Contact:
<a class="moz-txt-link-rfc2396E" href="sip:+333XXXXXXXX@CUSTOMER_DEVICE_SIP_DOMAIN"><sip:+333XXXXXXXX@CUSTOMER_DEVICE_SIP_DOMAIN></a></b></div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">
In this situation, OpenSIPS was unable to route correctly ACK
messages following this 200OK.</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);"><br>
</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">
Then, we've change the manner which Contact header is sent, and
now it's like <b>Contact:
<a class="moz-txt-link-rfc2396E" href="sip:+333XXXXXXXX@CUSTOMER_DEVICE_IP"><sip:+333XXXXXXXX@CUSTOMER_DEVICE_IP></a></b></div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">
And in this situation, everything seems to be OK, all message,
including ACK, are correctly routed.</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);"><br>
</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">Further,
we are sure that DNS resolution of CUSTOMER_SIP_DOMAIN returns
exactly CUSTOMER_DEVICE_IP, so, it doesn't seems to be a DNS
resolution problem...</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);"><br>
</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">
If it can help you !</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);"><br>
</div>
<div style="color: rgb(34, 34, 34); font-family: arial,sans-serif;
font-size: 13px; background-color: rgb(255, 255, 255);">
Thanks a lot, </div>
<div><br>
</div>
<b>Kevin MATHY</b>
<div><b>HEXANET</b></div>
<b>
<div><span style="font-weight: normal;">--</span></div>
</b>
<div>Téléphone : 03.26.79.30.05</div>
<div>Web : <a moz-do-not-send="true" href="http://www.hexanet.fr"
target="_blank">www.hexanet.fr</a></div>
<div><br>
</div>
<div>Pour toute demande de support, merci de contacter le <b>03.51.08.42.07</b>,
ou bien d'adresser un e-mail à <b><a moz-do-not-send="true"
href="mailto:support@hexanet.fr" target="_blank">support@hexanet.fr</a></b></div>
<div>
<br>
</div>
<br>
<br>
<br>
<div class="gmail_quote">2012/8/29 <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:mickael@winlux.fr"
target="_blank">mickael@winlux.fr</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Hi Bogdan,<br>
we will do this debug before end of week or begin of next week
and we will<br>
send our results.<br>
<br>
bye<br>
<div class="im"><br>
> Hi Kevin,<br>
><br>
> This looks like OpenSIPS does not recognize the Route
as its own IPs and<br>
> also seeing the next hop as a strict router.<br>
><br>
> To sort this out in the fastest way, see my prev
request on the logs for<br>
> ACK processing (with the debug=6).<br>
><br>
> Regards,<br>
><br>
> Bogdan-Andrei Iancu<br>
> OpenSIPS Founder and Developer<br>
> <a moz-do-not-send="true"
href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
><br>
><br>
> On 08/28/2012 03:22 PM, Kevin Mathy wrote:<br>
>> Hi Bogdan,<br>
>><br>
>> I'm working with Mickael about this problem, and we
have some<br>
>> informations which may help you (and then help us
;-) ) :<br>
>><br>
>> We have found that "loose_route" function modify
the Request-URI<br>
>> variable ($ru), as you can see below :<br>
>><br>
>> ACK message comes from provider, with $ru = <a
moz-do-not-send="true"
href="mailto:sip%3A%2B333XXXXXXXX@6.6.6.6">sip:+333XXXXXXXX@6.6.6.6</a><br>
</div>
>> <mailto:<a moz-do-not-send="true"
href="mailto:sip%253A%252B333XXXXXXXX@6.6.6.6">sip%3A%2B333XXXXXXXX@6.6.6.6</a>><br>
<div class="im">>> After, loose_route function is
executed, and $ru become like $ru<br>
>> =<br>
>>
<a class="moz-txt-link-freetext" href="sip:7.7.7.7;lr;r2=on;ftag=c97942d9-13c4-503ca77b-ef8c9eef-760f27a5;xyz=c12.18aedaa5">sip:7.7.7.7;lr;r2=on;ftag=c97942d9-13c4-503ca77b-ef8c9eef-760f27a5;xyz=c12.18aedaa5</a><br>
>><br>
>> The last $ru value results from a Route header<br>
>><br>
>> For information, Record-route of previous message
(200OK) is composed<br>
>> with two record-route in the same field, comma
separated.<br>
>> Is Opensips 1.6.4 able to interpret this type of
Record-route ?<br>
>><br>
>> Is loose_route function using Route headers of
previous messages<br>
>> (200OK before ACK) to route this message ? Or is it
using only actual<br>
>> message's Route headers ?<br>
>><br>
>> Thanks in advance,<br>
>> If you need further informations, feel free to ask
us.<br>
>><br>
>> Regards,<br>
>><br>
</div>
>> *Kevin MATHY*<br>
>> *HEXANET*<br>
>> *<br>
>> --<br>
>> *<br>
>> Téléphone : 03.26.79.30.05<br>
>> Web : <a moz-do-not-send="true"
href="http://www.hexanet.fr" target="_blank">www.hexanet.fr</a>
<<a moz-do-not-send="true" href="http://www.hexanet.fr"
target="_blank">http://www.hexanet.fr</a>><br>
>><br>
>> Pour toute demande de support, merci de contacter le
*03.51.08.42.07*,<br>
>> ou bien d'adresser un e-mail à *<a
moz-do-not-send="true" href="mailto:support@hexanet.fr">support@hexanet.fr</a><br>
>> <mailto:<a moz-do-not-send="true"
href="mailto:support@hexanet.fr">support@hexanet.fr</a>><br>
</blockquote>
</div>
</blockquote>
</body>
</html>