I have a working, stable sipX system (4.4.0 from ISO) with various same-subnet phones and sipxbridge to an ITSP (Voip.ms). The entire system is behind a port restricted NAT. All is well.
Recently I tried to add remote workers to the mix, very carefully. The first - and only - thing I did was port forward 5060 TCP/UDP and 30000-31000 UDP. When I did this I experienced what I suspect is the sipvicious problem described elsewhere in this list. Every 24 hours or so, sipxproxy and sipxregistrar prevent phones from registering and the only cure is to restart those two. My questions: 1) What is the best way to confirm that my problem is due to sipvicious. 2) Is the detailed reason that sipvicious causes an irrecoverable lockup well known? 3) Does 4.6 handle this situation better and make it into a (self) recoverable situation? 4) Does 4.6 offer sipvicious protection to minimise this from happening in the first place? 5) In the meantime, is pfsense my best option to block sipvicious (and also change me to symmetric)? 6) Is there an ISO for pfsense that is appropriate for sipx? Or an ISO with instructions for configuring for sipx? Any help would be appreciated. Keith
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
