Thanks for the feedback.<div><br></div><div>I said previously, Asterisk receives packets like <a href="mailto:extension@192.168.0.10">extension@192.168.0.10</a> is trying to register to it. So, Asterisk sends out to local LAN an ACK which obviously is not right. SPA-2102 should send SIP request like <a href="mailto:extension@123.123.123.123">extension@123.123.123.123</a> (public IP).</div>
<div><br></div><div>Thanks<br><br><div class="gmail_quote">On Fri, Oct 8, 2010 at 3:32 PM, Kevin P. Fleming <span dir="ltr"><<a href="mailto:kpfleming@digium.com">kpfleming@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 10/06/2010 02:50 PM, bruce bruce wrote:<br>
> Hi Guys,<br>
><br>
> This is such an annoying issue whenever it comes up. The sender and<br>
> receive always receive the source public IP no matter what in the IP<br>
> packets but then SIP packets go out with something like 192.168.0.20.<br>
><br>
> In this instance, a Bell Canada DSL modem is installed and I saw the<br>
> SPA-2102 register properly but only to fail later on due to sending it's<br>
> LAN IP to the Asterisk server.<br>
><br>
> So, I put NAT=yes and NAT_ALIVE=yes but that didn't help at all. I also<br>
> put the device on DMZ in the Bell Canada DSL modem and still the same issue.<br>
><br>
> I am wondering when would manufacturers finally fully comply the SIP RFC?!<br>
<br>
</div>Exactly how is this behavior non-compliant with "the" (sic) SIP RFC?<br>
There is nothing in any SIP RFC that mandates that a SIP UA must be<br>
aware of multiple IP addresses over which it can be reached, and select<br>
the proper one to include in SIP requests and responses.<br>
<br>
In fact, many SIP UAs, Asterisk included, work just fine behind NAT<br>
devices without ever knowing what their external IP addresses are.<br>
<br>
If you had actually described how the device failed, we might be able to<br>
tell you what you could do to resolve the problem. In general, Asterisk<br>
works just fine with endpoints that are behind NAT devices and never<br>
send their external IP addresses in their SIP messages... there are<br>
probably millions of devices working that way every day.<br>
<font color="#888888"><br>
--<br>
Kevin P. Fleming<br>
Digium, Inc. | Director of Software Technologies<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA<br>
skype: kpfleming | jabber: <a href="mailto:kfleming@digium.com">kfleming@digium.com</a><br>
Check us out at <a href="http://www.digium.com" target="_blank">www.digium.com</a> & <a href="http://www.asterisk.org" target="_blank">www.asterisk.org</a><br>
</font><div><div></div><div class="h5"><br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</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" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br></div>