The issue you are having is your outbound nat type. The outbound mac should be automatic for the entire network with the exception of the sip server. Siproxd Will only make things worse. Your outbound nat type for the sip server should be Manual But not for the whole subnet Which should be automatic.
I have never had a problem Registering multiple trunks to the same Provider Or using multiple providers in this fashion. And yes, I use pfsense quite a bit in this method. ===================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.326.5325 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Helpdesk Contract Customers: http://support.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/ tony-graziano/14/4a6/7a4 On Apr 5, 2011 4:37 PM, "Tim Byng" <t...@missioninc.com> wrote: > I am currently running some tests with a pfSense 2.0 RC1 box as my router. > This is due to remote worker issues I was experiencing when a D-Link DIR-655 > was the router. This has resolved my remote worker issues and almost > everything is working as expected. > > Unfortunately, switching to pfSense has caused one problem: I am no longer > able to register multiple SIP devices to the same external IP address (ITSP) > at the same time. This is a known issue, see here: > http://doc.pfsense.org/index.php/VoIP_Configuration > > There is an add-on package available for pfSense called siproxd which helps > with this issue and allows multiple SIP devices to register to the same > ITSP: > http://siproxd.sourceforge.net/ > > Before I go down the path of trying out siproxd, I was wondering if anyone > knows if this will cause issues with sipXecs? > > FYI: As a fail over for sipXecs, I have an IVR set up at voip.ms. All of my > Polycom SoundPoint phones register to my ITSP with their own sub account on > the second line. Currently only one of the phones has successfully > registered to the ITSP. There are no issues with sipXecs registering to my > ITSP, nor with my phones registering to sipXecs on line 1. > > I did not have this issue with the DIR-655; all of my internal SIP devices > could successfully register with my ITSP at the same time when the DIR-655 > was the router. > > Regards, > Tim
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
