Re: NAT state not deleted after IP change (DHCP)

2005-02-10 Thread Michiel van Baak
On 22:55, Tue 08 Feb 05, Cyrill R?ttimann wrote: Hi Daniel, Thanks for the answer and insights to the lower levels of the networked world. I have now hopefully solved my problem. I can see in the state table, that the state expires and after a few seconds, the state is recreated again

Re: NAT state not deleted after IP change (DHCP)

2005-02-10 Thread Cyrill Rüttimann
Hello, I couldn't resist to comment on some lines here. First of all, if you enable keepalive from the sip proxy to the phones (both SER and asterisk can do that) the state from server to phone won't be expiring. That way it is also not true that SIP is not well suited for firewalled connections.

Re: NAT state not deleted after IP change (DHCP)

2005-02-10 Thread Michiel van Baak
On 21:00, Thu 10 Feb 05, Cyrill R?ttimann wrote: Hello, Keep alive on the server is nat=yes in the sip.conf? yes. Not well suited means, that you have to define the internal ip on the asterisk server (sip.conf) and the external ip on the sip.conf. If you are running several servers,

Re: NAT state not deleted after IP change (DHCP)

2005-02-08 Thread Daniel Hartmeier
On Tue, Feb 08, 2005 at 08:20:26AM +0100, Cyrill Rüttimann wrote: The SIP-Phone sends every 25s (default) a keep alive message to the SIP-Proxy to remain the state on the NAT'ed Firewall. So I have to lower the udp.timeout to be less than 25s to get rid of the state, which results that the

Re: NAT state not deleted after IP change (DHCP)

2005-02-08 Thread Cyrill Rüttimann
Hi Daniel, Thanks for the answer and insights to the lower levels of the networked world. I have now hopefully solved my problem. I can see in the state table, that the state expires and after a few seconds, the state is recreated again (heartbeat 25s, timeout 20s): # voip nat on $ext_if from

Re: NAT state not deleted after IP change (DHCP)

2005-02-07 Thread solarflux.org/pf
Cyrill Rüttimann wrote: The state of the SIP-Connection remains active in the state table after changing the IP, why? The state is not expiring immediately. If I then delete the state, the SIP-Phone registers immediately with the SIP-Proxy. Try 'set optimization aggressive' which removes state

Re: NAT state not deleted after IP change (DHCP)

2005-02-07 Thread Cyrill Rüttimann
Hi, Try 'set optimization aggressive' which removes state entries quicker. That does not resolve the problem. I investigated some more effort: The SIP-Phone sends every 25s (default) a keep alive message to the SIP-Proxy to remain the state on the NAT'ed Firewall. So I have to lower the

NAT state not deleted after IP change (DHCP)

2005-02-06 Thread Cyrill Rüttimann
Hi, My ISP upgraded the cable modem to the DOCSIS-Standard. Since then, the IP changes every 4 hours. Before, I received the same IP for more than a year (the box is always running). The setup is a Soekris box attached to the cable modem on the first interface, and on the second interface