<!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">
Raymond Chandler wrote:
<blockquote
cite="mid:C685C86C-EC90-4568-8E31-6C05ED44FB53@freeswitch.org"
type="cite">
<div>
<div>very true, but i've been reading over the RFCs on this, and it
seems that FreeSWITCH isn't doing anything incorrectly.</div>
<div><br>
</div>
<div>in RFC3263 (section 4), when talking about client usage of SRV:</div>
<div><span class="Apple-style-span"
style="font-family: Arial,'Times New Roman',Times,serif; font-size: 16px; line-height: 26px;">
<pre><span class="Apple-style-span"
style="font-family: Arial,'Times New Roman',Times,serif; white-space: normal;"><pre><font
class="Apple-style-span" face="Monaco" size="1"><span
class="Apple-style-span" style="font-size: 9px;">The procedures here MUST be done exactly once per transaction, where transaction is as defined in [1]. </span></font></pre><pre><font
class="Apple-style-span" face="Monaco" size="1"><span
class="Apple-style-span" style="font-size: 9px;"><span
class="Apple-style-span"
style="font-family: Helvetica,'Times New Roman',Times,serif; font-size: medium; line-height: normal; white-space: normal;">[1] being RFC3261</span></span></font></pre></span></pre>
</span></div>
<div><br>
</div>
<div>in RFC3261 (section 8.1.3.5), when talking about 4xx responses:</div>
<span class="Apple-style-span"
style="font-family: Arial,'Times New Roman',Times,serif; font-size: 16px; line-height: 26px;">
<pre><font class="Apple-style-span" size="1"><span
class="Apple-style-span" style="font-size: 9px;">In all of the above cases, the request is retried by creating a new
request with the appropriate modifications. This new request
constitutes a new transaction and SHOULD have the same value of the
Call-ID, To, and From of the previous request, but the CSeq should
contain a new sequence number that is one higher than the previous.
</span></font></pre>
<div><font class="Apple-style-span"
face="monospace, 'Times New Roman', Times, serif"><span
class="Apple-style-span" style="white-space: pre;"><br>
</span></font></div>
</span></div>
</blockquote>
<br>
I'd say that based on my own and brief perusal of the relevant RFC's,
you are right that Freeswitch is operating without violating the specs.
Therefore, there is no bug in Freeswitch.<br>
<br>
<br>
<blockquote
cite="mid:C685C86C-EC90-4568-8E31-6C05ED44FB53@freeswitch.org"
type="cite">
<div><br>
<blockquote type="cite">
<div>Is there a way to make Freeswitch behave <br>
differently?<br>
</div>
</blockquote>
</div>
disable-srv on the profile
<div><br>
</div>
</blockquote>
<br>
In Callcentric's case, it doesn't help either. A request for 'A' recods
for 'callcentric.com' returns a bunch. The only way appears to select
and stick with only one.<br>
<br>
<blockquote
cite="mid:C685C86C-EC90-4568-8E31-6C05ED44FB53@freeswitch.org"
type="cite">
<div>All that said, if it has to be a "bug", then it seems to me that
it's more of a "bug" in callcentric's service. They'd probably be
better of actually prioritizing their SRV records. If they want load
balancing and want to do checking for stale nonces, then they should be
sharing nonces across all of their proxies or using a proper load
balancer.<br>
<div><br>
</div>
</div>
</blockquote>
<br>
Agreed. That being said, having a way to force Freeswitch to stick to
the same IP address in the middle of authorization/authentication
wouldn't violate any specs but would certainly make things easier when
dealing with not so well implemented round robin scenarios. Do you
think a new option could be added to Freeswitch to achieve round robin
avoidance in these cases?<br>
<br>
Thanks!<br>
<br>
Carlos Antunes<br>
Nowthor Corporation<br>
<br>
</body>
</html>