VOIP thru IpSec VPN problems
-
First, remember that everything worked until I setup my SIP provider as an alias to insert the 'alias' into the firewall rules to accept traffic ONLY from SIP provider. Once this was in place (to stop the blacklist IP address attacks) RTP stopped working for the extensions at home location "B".
There is no way a rule on WAN at location A can impact SIP over IPsec between A & B. You must be blocking something now that needs to be passed to/from the SIP provider. Perhaps site A and B were using the actual public IP address from B to A for RTP and not IPsec at all? Add the WAN address of Site B to the alias and see what happens.
Check your firewall logs.
-
Thank you for your suggestion.
Sorry, please notice that it says "newbie" below my login so, simplest of questions.
You said "Add the WAN address of Site B to the alias and see what happens." By that you mean to add the Site B WAN Address as an alias of the site A firewall rules?
But, that confuses me. All other computers, I have no problem ssh into, etc. through the VPN tunnel.
I am correct in that site B should be communicating back to the FreePBX box through the IPsec tunnel NOT site B connecting to my SIP provider over the internet?
-
No. Add it to the alias you are using to limit connections from the SIP provider. To also pass those connections from site B (if they exist).
-
Your suggestion has solved my problem. Adding the ip address of location "B" to the location "A" alias gave permission for a voice connection.
I believe, as you have suggested, that it has to do with the extension responding to FreePBX with location "B" wan address in the RTP requests strings. As PfSense would allow ONLY my SIP provider then PfSense was rejecting the extensions RTP request.
Thank you. Your patience and help are greatly appreciated.
-
Glad that worked.
There is probably something in the PBX that will treat the site B subnet as an inside subnet so it gets the PBX's inside address in the SIP/RTP requests so that site connects over the VPN instead of over the WAN.
It would probably be a good idea to fix that.
-
I'm using an older version of FreePBX with a similar setup.
Have a look at sip_nat.conf, mine is like this:
localnet=192.168.1.0/255.255.255.0 ;SiteA localnet=192.168.2.0/255.255.255.0 ;SiteB nat=yes externip=1.2.3.4 fromdomain=example.comYou can also set similar in Settings/Asterisk SIP Settings (- my system highlights an Error because the contents are different: I've chosen to leave this, while it works, until I change the network again).
 -
Yes, thank you, I am aware of this FreePBX option.
My issue was NOT with FreePBX connecting ONLY with my SIP provider it was the extensions located through IPSec VPN that could not properly connect.
Every situation is unique, mine more unique than many, I suspect but, the issue was PfSense (doing it's job) allowing ONLY my SIP provider to connect and NOT allowing my extensions through VPN to connect. Once the VPN alias I setup was added then, my extensions connected and worked properly.
I appreciate your suggestion.
-
I believe you are still missing the point. But they're your phone conversations going over the clear internet instead of the VPN so no skin off my nose.
-
I'll see what FreePBX forum thinks about this.
But, it appears to me that this is a PfSense issue not allowing connection. I think your right that the ipaddress is being changed (probably by FreePBX) and therefore PfSense will block but, I am still working this out.
By your comment, I just now realize that you are right the conversions could be connecting over the net.
We'll see.
-
Look.
Your WAN rules have ZERO effect on connections over IPsec.
The problem is your other site is connecting RTP over the internet instead of IPsec. That is because your PBX is giving them the public address to connect to instead of the private address that would be interesting to IPsec.
pfSense is just doing what it is told to do.
It's not pfSense. It is your broken PBX configuration.
-
I believe you. Currently working with FreePBX forum to resolve this.
