Siproxd errors in system logs

[1dhhintx]

Hello,

I had installed pfsense 1.2.3 along with siproxd package almost a year ago.  Everything has been working just fine with my Asterisk sip connections back to callcentric.com and voip.ms.  I then had a smart idea and decided to upgrade to pfsense 2.0.  The upgrade went just fine until I noticed that my telephone like coming in was not hitting my asterisk box all the time.  I logged into callcentric and see that it would show periodically "Your phone is not registered".  I didn't have this problem before I upgraded!  So in my research to resolve this I find the following errors in the system logs for pfsense.

Nov 7 01:24:52	siproxd[53118]: sock.c:469 ERROR:tcp_connect() failed
Nov 7 01:25:00	siproxd[53118]: proxy.c:706 ERROR:proxy_response: list_get via failed
Nov 7 01:25:16	siproxd[53118]: proxy.c:706 ERROR:proxy_response: list_get via failed
Nov 7 01:25:20	siproxd[53118]: proxy.c:706 ERROR:proxy_response: list_get via failed
Nov 7 01:25:46	siproxd[53118]: sock.c:469 ERROR:tcp_connect() failed
Nov 7 01:25:56	siproxd[53118]: sock.c:469 ERROR:tcp_connect() failed
Nov 7 01:26:41	siproxd[53118]: proxy.c:706 ERROR:proxy_response: list_get via failed
Nov 7 01:27:00	siproxd[53118]: proxy.c:706 ERROR:proxy_response: list_get via failed
Nov 7 01:27:07	siproxd[53118]: sock.c:469 ERROR:tcp_connect() failed
Nov 7 01:28:03	siproxd[53118]: sock.c:310 WARNING:recv() returned error [Connection reset by peer], disconnecting TCP [192.168.123.200] fd=13
Nov 7 01:28:26	siproxd[53118]: proxy.c:706 ERROR:proxy_response: list_get via failed
Nov 7 01:28:30	siproxd[53118]: proxy.c:706 ERROR:proxy_response: list_get via failed

So I figure that something is broken for this package in the new version of pfsense 2.0.  I did search on the forums here to see if I can find any resolution for this but came up empty.  Maybe someone could help me out as I need to have my phones working  ;D

Thanks

Doug
–

[marcelloc]

Tcp connect failed? Are you using encryption?

If only asterisk server goes to internet, you just need nat.

Try to disable sipproxy and remove outbound proxy info from sip.

[dhatz]

Quoting from siproxd 0.8.1 README

Known interoperability issues with SIP service providers:

• callcentric.com      (afaik callcentric fails with "500 network failure"
                          during REGISTER if more than one Via header is
                          present in a SIP packet. Having multiple Via headers
                          is completely in compliance with RFC3261. This might
                          be related to their "NAT problem avoidance magic".
                          There is nothing that can be done within siproxd
                          to avoid this issue as callcentric does not comply
                          with the SIP specification.