Rupa-

Can you offer up a tcpdump command he could run on the box that would catch all of this for later diagnosis if it happens again?

On Feb 9, 2010, at 5:55 PM, Rupa Schomaker wrote:

That is a different keep-alive.  I'm specifically talking about the keep-alive packet that we get via upnp multicast.  Whenever we receive one from the gateway we republish the nat mappings to.. um... keep them alive. :)

On Tue, Feb 9, 2010 at 8:52 AM, Kim Culhan <w8hdkim@gmail.com> wrote:
On Mon, February 8, 2010 11:21 pm, Troy Anderson wrote:
> I have been using pfSense (1.2.3) and FS.  FS nicely uses UPnP to poke
> holes in the firewall, but it seems that the holes close after a while.  I
> cannot find any documentation in FS nor in pfSense as to what the timeout
> is.  Is there a setting in FS to do some kind of keep-alive thing with
> UPnP to keep, e.g. 5060, open?  Or is it already doing that and pfSense is
> the issue?

FS has provisions for keep-alive, see the bottom of the page for ping
time value:

http://wiki.freeswitch.org/wiki/SIP_Provider_Examples

To watch the pf firewall hole timing you can install pftop from
FreeBSD ports/sysutils
which displays the filter states 'and more'.

-kim



--
-Rupa
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org