<div>because, a this time, the sip stack doesn't have asynchronous DNS... so ALL the sip code is stucked waiting timeouts for DNS queries (that are long timeouts).</div>
<div>When you try to dial a LAN device, the sip code is trying to resolve your voISP service providers' addresses.</div>
<div>We workaround this putting all external sip peers in a separate file, say "sip_peers.conf", included in sip.conf with "#include filename".</div>
<div>Then, a daemon on the box try to resolve well-known addresses on well-known DNS servers on the net, every 5 minutes. If the demon fails ALL the well-known DNS queries, it assumes no internet connection is available: then it renames sip_peers.conf, and ask asterisk a "sip reload". So all external sip references are out, and sip still continue working for internal phones. Needless to say, when connection come up again, the daemon do the opposite thing.
<br><br>hope this helps</div>
<div> </div>
<div> </div>
<div><span class="gmail_quote">2006/4/11, Brent Torrenga <<a href="mailto:lists@torrenga.com">lists@torrenga.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Out internet connection was out this morning. It seems that the SIP<br>extensions on our LAN were affected. Behavior like:
<br><br>Call comes in over POTS to a TDM400P, there is a delay then before the Cisco<br>79[46]0's start to ring.<br>If we were lucky enough to get a call through, then we could not transfer<br>the call, or place the call on hold, or park the call.
<br>Outbound calls seemed to have a delay between the time they were dialed at<br>the SIP phone and when they were connected.<br><br>I know this has been brought up before, in fact there is a bit of a<br>discussion going on now about DNS SRV (in
sip.conf, set srvlookup=no, or put<br>all the phone ip's on /etc/hosts). But what is really causing the issue<br>here? Yes, it is DNS, or something related to DNS, but why does that have<br>anything to do with * trying to make a phone ring on the LAN?
<br><br>I would think that by using qualify=yes for any outbound voip trunks we<br>avoid an issue of trying to call out is the net is down, but why are any<br>operations on the LAN affected?<br><br><br>Sincerely,<br><br>Brent A. Torrenga
<br><a href="mailto:brent.torrenga@torrenga.com">brent.torrenga@torrenga.com</a><br><br>Torrenga Engineering, Inc.<br>907 Ridge Road<br>Munster, Indiana 46321-1771<br><br>+1 219 836 8918 x325 Voice<br>+1 219 836 1138 Facsimile
<br><a href="http://www.torrenga.com">www.torrenga.com</a><br><br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>Asterisk-Users mailing list
<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></div><br>