<div dir="ltr"><div class="gmail_default" style="color:#660000">That sounds like asterisk was working 100% correctly. If you receive an INVITE from an unknown IP address, then it should fail. Unless you want to allow anonymous, which is genearlly a very bad idea.</div><div class="gmail_default" style="color:#660000"><br></div><div class="gmail_default" style="color:#660000">If you are registering to IP X, but the provider may be transmitting invites from any number of other IP addresses, then you need a list of IP addresses, and have a trunk configuration set up for each one so that they are all recognized (with insecure=port,invite).</div><div class="gmail_default" style="color:#660000"><br></div><div class="gmail_default" style="color:#660000">If the provider is requiring you to accept invites from random IP addresses, get a new provider.</div><div class="gmail_default" style="color:#660000"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 2, 2015 at 3:23 PM, Daniel Heckl <span dir="ltr"><<a href="mailto:daniel.heckl@gmail.com" target="_blank">daniel.heckl@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Okay, Scott, I think we are on the wrong path. Maybe I'm wrong though.
</div><div><br></div><div>I will summarize again briefly the problems together:</div><div><ul><li>The peer ip address could be another than the ip address of incoming invites</li><li>After an re-register the REGISTER is send to the new SIP server, answered with OK. But the peer ip address is still the old one (sip show peers).</li><li>If now is a INVITE, the request is answered with 401 Unauthorized.</li></ul><div><br></div><div>That’s why I would say, the problem is not the port or a needed authentication. My Asterisk works behind a NAT without port forwarding and nat=no, I have qualify=yes that it does not come to a NAT timeout.</div><div><br></div><div>Here is an example. The peer ip address was at this time 217.0.23.100, the INVITE came from 217.0.23.68 an was rejected with 401 Unauthorized:</div><div><br></div><div><div>INVITE <a>sip:06123456789@80.000.111.222:45061</a> SIP/2.0</div><div>Max-Forwards: 58</div><div>Via: SIP/2.0/UDP 217.0.23.68:5060;branch=z9hG4bKg3Zqkv7ib7h2smv8whryjnos88srot1i7</div><div>To: <<a>sip:6123456789@telekom.de</a>></div><div>From: <<a>sip:+49123456789@tel.t-online.de;user=phone</a>>;tag=h7g4Esbg_44c62525</div><div>Call-ID: <a href="mailto:af71bbfbf269b895@62.155.0.75" target="_blank">af71bbfbf269b895@62.155.0.75</a></div><div>CSeq: 3950540 INVITE</div><div>Contact: <<a>sip:sgc_c@217.0.23.68;transport=udp</a>></div><div>Record-Route: <<a>sip:217.0.23.68;transport=udp;lr</a>></div><div>Min-Se: 900</div><div>P-Asserted-Identity: <<a>sip:+49123456789@tel.t-online.de;user=phone</a>></div><div>Session-Expires: 3600</div><div>Supported: histinfo</div><div>Supported: timer</div><div>Supported: norefersub</div><div>Content-Type: application/sdp</div><div>Content-Disposition: session</div><div>Content-Length: 204</div><div>Allow: ACK, BYE, CANCEL, INFO, INVITE, OPTIONS, PRACK, REFER, REGISTER, UPDATE</div><div><br></div><div>v=0</div><div>o=- 0 0 IN IP4 217.0.23.68</div><div>s=-</div><div>c=IN IP4 217.0.4.134</div><div>t=0 0</div><div>m=audio 36480 RTP/AVP 9 8 102</div><div>a=rtpmap:9 G722/8000</div><div>a=rtpmap:8 PCMA/8000</div><div>a=rtpmap:102 telephone-event/8000</div><div>a=maxptime:20</div><div>a=ptime:20</div></div><div><br></div></div><div><div class="h5"><div><blockquote type="cite"><div>Am 02.04.2015 um 22:00 schrieb Scott Griepentrog <<a href="mailto:sgriepentrog@digium.com" target="_blank">sgriepentrog@digium.com</a>>:</div><br><div><div dir="ltr"><div class="gmail_default" style="color:#660000">Actually, the IP address is still used to identify the incoming invite. With the insecure=port option set, Asterisk will presume the invite to still match the trunk account even if the NAT router has mangled (changed) the port number. My suspicion is that when the new register goes out, it's creating a new state in the firewall, resulting in a new port number, which is why you would have to allow anonymous calls to then accept it without insecure=port. The other possibility is that you have a port forward in the router set, which is similarly mangling the port number. With a valid registration being held, and assuming the router does not drop UDP states faster than 30 minutes, and also assuming that the provider is sending you invites on the registered port rather than always on 5060, there should not be a need for an inbound port forward to Asterisk, and you should not need insecure=port.</div><div class="gmail_default" style="color:#660000"><br></div><div class="gmail_default" style="color:#660000">The invite option disables authentication - which means only that Asterisk will not force a check of the password on the other end. Where the IP address is well known and trusted, the extra overhead and delay of authenticating incoming INVITEs is not needed.</div><div class="gmail_default" style="color:#660000"><br></div><div class="gmail_default" style="color:#660000"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 2, 2015 at 2:28 PM, Daniel Heckl <span dir="ltr"><<a href="mailto:daniel.heckl@gmail.com" target="_blank">daniel.heckl@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Scott, I have changed the configuration as said it and will test it. I’m curious.
</div><div><br></div><div>Can you briefly explain what insecure=invite,port does?</div><div><br></div><div><span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;line-height:18px;white-space:pre-wrap">;insecure=port ; Allow matching of peer by IP address without</span></div><div><span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;line-height:18px;white-space:pre-wrap"> </span><span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;line-height:18px;white-space:pre-wrap">; matching port number</span></div><div><span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;line-height:18px;white-space:pre-wrap">;insecure=invite </span><span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;line-height:18px;white-space:pre-wrap">; Do not require authentication of incoming INVITEs</span></div><div><span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;line-height:18px;white-space:pre-wrap">;insecure=port,invite ; (both)</span></div><div><span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;line-height:18px;white-space:pre-wrap"><br></span></div><div><span style="color:rgb(51,51,51);line-height:18px;white-space:pre-wrap">Do I understand correctly that in this mode the IP address is not checked and no authentication is required? </span></div><div><div><div><span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Menlo,Courier,monospace;line-height:18px;white-space:pre-wrap"><br></span></div><div><blockquote type="cite"><div>Am 02.04.2015 um 20:11 schrieb Scott Griepentrog <<a href="mailto:sgriepentrog@digium.com" target="_blank">sgriepentrog@digium.com</a>>:</div><br><div><div dir="ltr"><div class="gmail_default" style="color:rgb(102,0,0)">I'd be curious if setting</div><div class="gmail_default" style="color:rgb(102,0,0)"><br></div><div class="gmail_default" style="color:rgb(102,0,0)">insecure=invite,port</div><div class="gmail_default" style="color:rgb(102,0,0)"><br></div><div class="gmail_default" style="color:rgb(102,0,0)">makes any difference either (without alllowguest on).</div><div class="gmail_default" style="color:rgb(102,0,0)"></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 2, 2015 at 9:03 AM, Daniel Heckl <span dir="ltr"><<a href="mailto:daniel.heckl@gmail.com" target="_blank">daniel.heckl@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ok, I have tested dnsmgr. This is not a solution, the situation has not changed. With dnsmgr I can not place outbound calls. I do not know why and what dnsmgr really do.<br>
<br>
My current solution is as follows:<br>
<br>
Say allowguest=yes, configure the default context that there can not be placed outbound calls. Use iptables to DROP all at your SIP port and allow only your local phones and the sip trunk ip range. I think srvlookup must be set to yes to place outbound calls if there is an ip address change.<br>
<br>
I think with the restriction of the firewall that should be a secure solution.<br>
<div><div><br>
> Am 01.04.2015 um 19:23 schrieb Sebastian Kemper <<a href="mailto:sebastian_ml@gmx.net" target="_blank">sebastian_ml@gmx.net</a>>:<br>
><br>
> On Wed, Apr 01, 2015 at 11:00:56AM -0400, Andres wrote:<br>
>> On 4/1/15 10:48 AM, Daniel Heckl wrote:<br>
>>> John,<br>
>>><br>
>>> thank you four your answer. I think you have misunderstood the<br>
>>> problem. It’s about a ip address change of the sip trunk, not of my<br>
>>> asterisk server.<br>
>> You would probably benefit by enabling the DNS Manager to allow for<br>
>> dynamic IP changes:<br>
>><br>
>> # cat dnsmgr.conf [general] enable=yes ; enable creation<br>
>> of managed DNS lookups ; default is 'no' refreshinterval=180 ;<br>
>> refresh managed DNS lookups every <n> seconds ; default is 300 (5<br>
>> minutes)<br>
><br>
> Hello Andres,<br>
><br>
> I read that same suggestion elsewhere in connection with Deutsche<br>
> Telekom, so it seems there's some benefit in it.<br>
><br>
> Daniel, did you try it out already?<br>
><br>
> Kind regards,<br>
> Sebastian<br>
><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>
<br>
<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></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><img alt="Digium logo" src="https://my.digium.com/images/graphics/digium_RGB_signature.gif" width="288" height="50" style="font-family:Arial,Helvetica,sans-serif;font-size:12px"><div>Scott Griepentrog<br>Digium, Inc · Software Developer<br>445 Jan Davis Drive NW · Huntsville, AL 35806 · US<br>direct/fax: +1 256 428 6239 · mobile: +1 256 580 6090<br>Check us out at: <a href="http://digium.com/" target="_blank">http://digium.com</a> · <a href="http://asterisk.org/" target="_blank">http://asterisk.org</a><br></div></div></div>
</div>
-- <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></div></blockquote></div><br></div></div></div><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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><img alt="Digium logo" src="https://my.digium.com/images/graphics/digium_RGB_signature.gif" width="288" height="50" style="font-family:Arial,Helvetica,sans-serif;font-size:12px"><div>Scott Griepentrog<br>Digium, Inc · Software Developer<br>445 Jan Davis Drive NW · Huntsville, AL 35806 · US<br>direct/fax: +1 256 428 6239 · mobile: +1 256 580 6090<br>Check us out at: <a href="http://digium.com/" target="_blank">http://digium.com</a> · <a href="http://asterisk.org/" target="_blank">http://asterisk.org</a><br></div></div></div>
</div>
-- <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></div></blockquote></div><br></div></div></div><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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><img alt="Digium logo" src="https://my.digium.com/images/graphics/digium_RGB_signature.gif" width="288" height="50" style="color:rgb(0,0,0);font-family:Arial,Helvetica,sans-serif;font-size:12px"><div>Scott Griepentrog<br>Digium, Inc · Software Developer<br>445 Jan Davis Drive NW · Huntsville, AL 35806 · US<br>direct/fax: +1 256 428 6239 · mobile: +1 256 580 6090<br>Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> · <a href="http://asterisk.org" target="_blank">http://asterisk.org</a><br></div></div></div>
</div>