• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2706
  • Last Modified:

VOIP over IPSEC VPN has no audio

I have 2 pfsense firewalls with an IPSEC VPN between them.  everything seems to work fine except voip.  Sometimes I'll get two way audio, but generally its silent on both ends.  What's odd is that if I reset firewall states, or change settings and apply them, i can usually get the first call I try to work.  After that, it goes back to no audio.  

Here's the layout:

phones (192.168.10.0/24)  >>  pfsense  >>  VPN  >>  pfsense  >>  (192.168.0.0/24) asterisk

Phones are registering to the local IP of the PBX (192.168.0.25) just fine.  I do not have any static routes.  Automatic NAT is on (for ipsec passthrough).  All ports are open properly to my SIP trunks.  Any ideas?
0
lorsungcu
Asked:
lorsungcu
  • 3
1 Solution
 
namolCommented:
can we see your sip_nat.conf file and any logs so we can attempt to troubleshoot? Shooting from the hip I'd say one of the phones is sending some of the traffic to the internet after it makes a connection.
0
 
lorsungcuAuthor Commented:
I'd love to give you my sip_nat.conf file, but we're using Switchvox, which gives you no access to configuration files.  Also, as this should be all over the VPN, NAT shouldn't be an issue.  If it helps, I can take screenshots of my pfsense configuration.
0
 
lorsungcuAuthor Commented:
When I make a call, these are the states the firewall has for the phone:
Proto   	Source -> Router -> Destination   	State   	
udp	192.168.10.199:5060 -> 192.168.0.25:5060	MULTIPLE:MULTIPLE	
udp	192.168.0.25:5060 <- 192.168.10.199:5060	MULTIPLE:MULTIPLE	
udp	192.168.1.1:123 <- 192.168.10.199:1074	NO_TRAFFIC:SINGLE	
udp	192.168.10.199:1074 -> 173.165.229.145:5945 -> 192.168.1.1:123	SINGLE:NO_TRAFFIC	
udp	192.168.0.25:55244 <- 192.168.10.199:2250	NO_TRAFFIC:SINGLE	
udp	192.168.10.199:2250 -> 192.168.0.25:55244	SINGLE:NO_TRAFFIC	
udp	192.168.0.25:55245 <- 192.168.10.199:2251	NO_TRAFFIC:SINGLE	
udp	192.168.10.199:2251 -> 192.168.0.25:55245	SINGLE:NO_TRAFFIC

Open in new window

0
 
lorsungcuAuthor Commented:
I had 1:1 NAT for the PBX, with firewall rules deciding where things can go, but apparently that wasn't enough.  I added NAT entries for RTP ports, and everything works.  Not sure I get that, but I'll take it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now