<div class="gmail_quote">On Thu, Feb 4, 2010 at 9:20 PM, Nikhil Nair <span dir="ltr"><<a href="mailto:nnair@pobox.com">nnair@pobox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
No, again, I can cut off the internet altogether with "ifdown eth1", and<br>
the SIP phones (via eth0) continue to work fine, as does the Zap channel.<br>
It's only if eth1 is up but the ADSL router is down (or, indeed, the phone<br>
line is down), that the problem arises.<br>
<font color="#888888"><br>
N.<br>
</font><div><div></div><br></div></blockquote></div><br>It sounds as though something is wrong with the RTP routing. If you ifdown the connection, you're deleting the routes. If the ADSL modem goes down, your server still thinks it has a route out to the internet. I've noticed a similar issue on one of my client's installations. They lost their internet connection and the phone system went haywire. As soon as it was restored, everything returned to normal. <br>
<br>What happens if you manually execute just ifconfig eth1 down? I haven't tried this, I'm just curious if it will also delete the route, or will it leave it there? If the route is still there, what happens to your phone connections?<br>
<br>Another idea - what happens when you bind your SIP connections to the internal IP address (using bindaddr=10.9.8.1 in the general section of your sip.conf file) , and then unplug the modem?<br><br>I'm sorry I'm unable to offer an exact solution, but I'm very interested in any results you may come up with.<br clear="all">
<br>-- <br>Thanks,<br>--Warren Selby<br><a href="http://www.selbytech.com">http://www.selbytech.com</a><br>