On 11/02/2011 06:03 AM, Chris Buechler wrote:
On Wed, Nov 2, 2011 at 12:35 AM, Craig Drown<[email protected]> wrote:
Hi,
we have a Linksys/Sipura SIP client behind pfSense 2 on an Alix board.
Usually after about a week we can no longer make calls.
Clearling pfSense states or a reboot fixes it, whereas a reboot of the Sipura
box makes no difference, so it's something with pfSense.
Couldn't see anything in the logs.
Any ideas?
What do the states look like?
Tons of 2.0 boxes out there with VoIP behind them, including all ours,
definitely not a widespread issue.
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list
There was an issue like this on pfsense 1.2.3 when you have a dynamic
DSL WAN IP address, and your ISP forces a DSL disconnect and IP renew
every few days.
Not sure if this is fixed in 2.0 ?
Basically, when your WAN IP changes the NAT states with the old WAN IP
are not cleared from the state table.
The SIP device looses its connection and starts reconnecting every 20
orso seconds as defined in the SIP protocol.
This keeps the old state alive, and therefore it keeps using the
incorrect old NAT'ed WAN IP.
Again, this may be fixed in 2.0 but I have not tested that.
In 1.2.3 there was a quickfix in some package that cleared SIP states on
a WAN DHCP renew.
More info: http://forum.pfsense.org/index.php/topic,18053.0.html
Regards,
Hans
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list