<div class="gmail_quote">Hello,<br><br>We're attempting to use Asterisk for distributing calls via SIP in a large-scale speech recognition/VXML environment. We currently use DNS SRV with weights and priorities to instruct VoIP gateways (not Asterisk) to route calls to pools of servers. This works extremely well and provides for load balancing, fail-over, and by setting the TTL low (several minutes) we can easily take machines out of service for maintenance just by adjusting the appropriate DNS SRV records. For business reasons, we now need to achieve a similar setup using Asterisk instances hosted by a partner of ours.<br>
<br>We've done a lot of reading on Asterisk and based on that our current understanding is:<br><br>- chan_sip DOES now process DNS SRV weights and priorities (as of 1.4.X) but only uses the first record (but correctly sorted by priority & weight)<br>
- chan_sip DOES NOT use the dnsmgr for caching/update of DNS records<br>- Asterisk in general DOES NOT respect DNS TTL values (unclear if that was addressed in recent versions)<br><br>In testing Asterisk 1.4.18, we are running into an even more basic issue -- changes to a host in DNS (with a single DNS SRV record) are never picked up by Asterisk. Our simple test scenario is:<br>
<br>- Set SRV record in DNS for hostname X to point to server foo<br>- Place calls and observe that Asterisk correctly routes call to server foo<br>- Update SRV record in DNS for hostname X to point to server bar (with TTL of hostname X originally set to 5 minutes)<br>
- Subsequent calls still go to the original server foo, even after waiting hours or even days<br><br>Asterisk never seems to pick up the changed DNS info.<br><br>There are vague references on the web to being able to configure Asterisk with DNS related settings. ("Unless specifically configured, Asterisk 1.2 does not honor DNS Time To Live (TTL)." from <b><a href="http://tinyurl.com/2ossv6" target="_blank">http://tinyurl.com/2ossv6</a>) </b>We've tried doing:<br>
<br>[dnsmgr.conf]<br>enable=yes ; enable creation of managed DNS lookups<br>refreshinterval=300 ; refresh managed DNS lookups every <n> seconds<br><br>But this doesn't work, apparently since chan_sip doesn't use dnsmgr. <br>
<br>We figure that many other people must need to have Asterisk process updated DNS info and that we must just be missing some configuration. Is that the case or is this a fundamental limitation of Asterisk in its current form?<br>
<br>Thanks in advance for the help,<br><font color="#888888">
-Joe<br></font><br>P.S. I'm subscribed to the list in digest form so a copy to this e-mail on replies would be most appreciated. Thanks!<br><br></div>