[asterisk-users] Update peer IP address

[Daniel Heckl]

Sebastian,

If I have understood you correctly, the SIP communication is now via NAT instead forwarded ports. For safety, it is much better.

I think it is not because of a UDP timeout, but rather because of a NAT timeout. For this is "qualify" exactly the right thing to let the NAT port opened. 

Daniel

> Am 14.09.2015 um 21:51 schrieb Marie Fischer <marie at vtl.ee>:
> 
> 
> On 14.09.2015, at 21:58, Sebastian Kemper <sebastian_ml at gmx.net> wrote:
> 
>> So I got rid of the firewall rule that opened the RTP ports. And then it
>> dawned on me that I don't even need to open the 5060 port. The REGISTER
>> requests established a UDP connection that the kernel's conntrack module
>> was tracking anyway. The only issue was that the REGISTERs occurred only
>> every 480s and the UDP connections were removed after 180s already.
>> 
>> So at first I raised net.netfilter.nf_conntrack_udp_timeout_stream to
>> 500. That worked. But I didn't really want to raise the default. So
>> instead I added "qualify=yes" to the dtag_inbound peer. Now asterisk is
>> sending an OPTIONS request to Telekom every 120s (I raised the frequency
>> from 60 to 120 by setting "qualifyfreq=120" under [general]), which
>> keeps the connection open.
> 
> As far as I understand, raising the UDP session timeout (or lowering the REGISTER timeout, if possible) is actually the better solution. Most Telcos I know don't answer the OPTIONS request anyway and some might object to the traffic overhead.
> 
> -- 
> marie
> -- 
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users