I'm assuming your VOIP is using SIP and generally uses ports 5060 and 5061. Registration and call control goes over those ports. If your range of RTP ports is blocked (usually a wide range of ports like 10000-20000) then you will not hear any voice. I believe pfSense 2.1 has all ports blocked on ipsec remote LANs by default. Did you open it?
If you're using Asterisk for VOIP, then you'll need to add the remote network's internal IP range to /etc/asterisk/sip_nat.conf if you're doing NAT with SIP. Each non-NATed network needs to be listed there get voice traffic going. (In FreePBX, it's in advanced SIP settings.) Larry On Mon, Feb 6, 2012 at 3:44 AM, Gavin Will <[email protected]> wrote: > Hi there, > > I have a PFsense box at our main site with ipsec vpns to 2 other sites > with different firewall / routers (Draytek and Zywall) at the remote sites > there is a voip phone going back to our main office across the VPN with the > private internal ip of the VOIP server. This works fine. > > I have another new site that has another pFsense box and the ipsec VPN > back to the main office (pfSense again) > > Routing and firewall rules are correct and I can access both networks > fine. The voip phone registers and can make a call but both ends cannot > hear each other each other. > > I'm confused with this, since the vpn is up and traffic appears to flow > OK. Im aware of the rules you need to set the outbound NAT to Manual but > this would only apply to stuff from the WAN and not Ipsec. > > I'm going to do a packet capture but any ideas? > > Gavin > > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list >
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
