SIP stops working after a while

leenooks

Hi, I'm looking for advise on how to diagnose some problems with SIP.

I have configured SIPPROXYD, NAT rules and when first configured (and after a reboot of pfsense), my SIP connections work very well.

I am running freeswitch on my LAN (not on pfsense), and it successfully registers with two SIP providers on my WAN (I use an ADSL PPPOE link, with my modem in bridge mode, and pfsense brings up the ADSL connection).

After about 1 or 2 hour, registrations to one of the providers stops working, and then after a while longer (havent actually checked, but by the next day), registration to the other provider stops.

The only way I can fix this at the moment is to reboot my pfsense machine - and then it works great for an hour or two, and eventually both providers fail. I was running 1.2.3, and have sinse upgraded to 2.0 (1st April snapshot), and the same problem exists (with the same symptoms).

I'm new to FreeBSD and have no idea where to start looking to fix problems. I was running Endian for a little while, and I had no trouble there, so I can only assume that there is something about pfsense/freebsd that stops working after time.

(I switch to freebsd, as I now have an ALIX box - and I'm just so impressed :) If only I can get the SIP part going… ???

Any tips, pointers would be appreciated.

leenooks

OK, maybe related or not?

/usr/local/sbin/siproxd -h shows version
siproxd-0.7.1-4807

yet System -> Packages says 0.7.3? Do I have a bad package?

Also the configuration file shows
if_outbound = ng0

but I dont have an interface ng0?

ifconfig: interface ng0 does not exist?

Also, starting sipproxy manually shows this error:
18:42:02 ERROR:readconf.c:310 unknown keyword in config file, line:"log_calls = 1"

cmb

@leenooks:

/usr/local/sbin/siproxd -h shows version
siproxd-0.7.1-4807

yet System -> Packages says 0.7.3? Do I have a bad package?

No, there is no relation there.

@leenooks:

Also the configuration file shows
if_outbound = ng0

but I dont have an interface ng0?

ng0 is your PPPoE WAN.

Your problem isn't likely related to any of that, it's probably #2 here:
http://doc.pfsense.org/index.php/VoIP_Configuration

leenooks

@cmb:

ng0 is your PPPoE WAN.

Your problem isn't likely related to any of that, it's probably #2 here:
http://doc.pfsense.org/index.php/VoIP_Configuration

So should ifconfig ng0 show anything? (It doesnt other than interface doesnt exist).

So, I copied the sipproxy configuration file to tmp, changed ng0 to pppoe0, manually started sipproxyd using my tmp configuration and now I have successful registration to 1 provider. It has also been up for days.

A tcpdump shows that pfsense is not communicating at all to the other provider (no SIP packets go out pppoe0 to my 2nd provider, even though my freeswitch server is sending them).

I've looked through that document and applied everything as it suggested. Any other tips?

danswartz

I found siproxd to not work at all, so I ended up not using it.

cmb

@danswartz:

I found siproxd to not work at all, so I ended up not using it.

It works fine, but in most cases you don't need it. Only where you have to rewrite any private IPs inside of SIP packets do you need it, which isn't necessary with most providers.

g4m3c4ck

I have found that pfsense has to be rebooted when you have two providers on the same or separate interface being when you use VLANs, PPPoe or Load balancing. Also, if I register on one interface with the same provider then try to do it on another pfsense refuses to allow it to work unless you reboot.