<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi Bogdan,<br><br>as that FQDN is in opensips domain table or alias, thats why the opensips considerd it as internal domain , Is that correct?<br>It should be only in the domain table of the opensips responsible for that customer.<br><br>thanks<br>//Binan<br><br>--- On <b>Fri, 8/31/12, Hubert Mickael <i><mickael@winlux.fr></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Hubert Mickael <mickael@winlux.fr><br>Subject: Re: [OpenSIPS-Users] [Re: Routing problem with Record-Route]<br>To: "OpenSIPS users mailling list" <users@lists.opensips.org><br>Cc: "Binan AL Halabi" <binanalhalabi@yahoo.com><br>Date: Friday, August 31, 2012, 12:18 PM<br><br><div id="yiv1311870341">
<div>
Hi,<br>
Yes,<b> CUSTOMER_DEVICE_SIP_DOMAIN </b>is insert to "domain" table in
opensips's database.<br>
<br>
Le 31/08/2012 15:48, Binan AL Halabi a écrit :
<blockquote type="cite">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="font-family:inherit;font-style:inherit;font-variant:inherit;font-weight:inherit;font-size:inherit;line-height:inherit;font-size-adjust:inherit;font-stretch:inherit;" valign="top">Hi,<br>
Is <b>CUSTOMER_DEVICE_SIP_DOMAIN defined in opensips</b> ?<br>
<br>
//Binan<br>
<br>
--- On <b>Fri, 8/31/12, Kevin Mathy <i><a rel="nofollow" class="yiv1311870341moz-txt-link-rfc2396E" ymailto="mailto:k.mathy@hexanet.fr" target="_blank" href="/mc/compose?to=k.mathy@hexanet.fr"><k.mathy@hexanet.fr></a></i></b>
wrote:<br>
<blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;"><br>
From: Kevin Mathy <a rel="nofollow" class="yiv1311870341moz-txt-link-rfc2396E" ymailto="mailto:k.mathy@hexanet.fr" target="_blank" href="/mc/compose?to=k.mathy@hexanet.fr"><k.mathy@hexanet.fr></a><br>
Subject: Re: [OpenSIPS-Users] [Re: Routing problem with Record-Route]<br>
To: "Bogdan-Andrei Iancu" <a rel="nofollow" class="yiv1311870341moz-txt-link-rfc2396E" ymailto="mailto:bogdan@opensips.org" target="_blank" href="/mc/compose?to=bogdan@opensips.org"><bogdan@opensips.org></a>, "OpenSIPS users
mailling list" <a rel="nofollow" class="yiv1311870341moz-txt-link-rfc2396E" ymailto="mailto:users@lists.opensips.org" target="_blank" href="/mc/compose?to=users@lists.opensips.org"><users@lists.opensips.org></a><br>
Date: Friday, August 31, 2012, 5:53 AM<br>
<br>
<div id="yiv1311870341"><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:
<sip:+333XXXXXXXX@CUSTOMER_DEVICE_SIP_DOMAIN></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:
<sip:+333XXXXXXXX@CUSTOMER_DEVICE_IP></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 rel="nofollow" target="_blank" href="http://www.hexanet.fr">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 rel="nofollow">support@hexanet.fr</a></b></div>
<div><br>
</div>
<br>
<br>
<br>
<div class="yiv1311870341gmail_quote">2012/8/29 <span dir="ltr"><<a rel="nofollow">mickael@winlux.fr</a>></span><br>
<blockquote class="yiv1311870341gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;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="yiv1311870341im"><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 rel="nofollow" target="_blank" href="http://www.opensips-solutions.com">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 rel="nofollow">sip:+333XXXXXXXX@6.6.6.6</a><br>
</div>
>> <mailto:<a rel="nofollow">sip%3A%2B333XXXXXXXX@6.6.6.6</a>><br>
<div class="yiv1311870341im">>> After, loose_route
function is executed, and $ru become like $ru<br>
>> =<br>
>>
sip:7.7.7.7;lr;r2=on;ftag=c97942d9-13c4-503ca77b-ef8c9eef-760f27a5;xyz=c12.18aedaa5<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 rel="nofollow" target="_blank" href="http://www.hexanet.fr">www.hexanet.fr</a> <<a rel="nofollow" target="_blank" href="http://www.hexanet.fr">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 rel="nofollow">support@hexanet.fr</a><br>
>> <mailto:<a rel="nofollow">support@hexanet.fr</a>><br>
</blockquote>
</div>
</div>
<br>
-----Inline Attachment Follows-----<br>
<br>
<div class="yiv1311870341plainMail">_______________________________________________<br>
Users mailing list<br>
<a rel="nofollow">Users@lists.opensips.org</a><br>
<a rel="nofollow" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div>
</blockquote>
</td>
</tr>
</tbody>
</table>
<pre><fieldset class="yiv1311870341mimeAttachmentHeader"></fieldset>
_______________________________________________
Users mailing list
<a rel="nofollow" class="yiv1311870341moz-txt-link-abbreviated" ymailto="mailto:Users@lists.opensips.org" target="_blank" href="/mc/compose?to=Users@lists.opensips.org">Users@lists.opensips.org</a>
<a rel="nofollow" class="yiv1311870341moz-txt-link-freetext" target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</div></blockquote></td></tr></table>