From personal experience, I would strongly recommend running the VPN within the network layer rather than directly on the server.

You could use a pre-built appliance for this (such as Halon VSR), or build your own router using iptables, or even use a Cisco etc.

This means you don't have to maintain a tunnel for each individual machines, and keeps a nice clean separation of layers which makes debugging networking problems easier.

If you use this approach, then running FreeSWITCH over any tunnel should *just work*.. if you use it locally, then strange things might happen..

This is just based on my own personal experience, others may disagree.. YMMV :)

Hope this helps

Cal

On Tue, Apr 9, 2013 at 5:44 PM, sibu <sibxol@btconnect.com> wrote:
Dear Freeswitch-Users/Developers

I am new to this  list and freeswitch.

I would like to know if anyone has tried freeswitch with an ipsec VPN such as
openswan or strongswan and what were/should-be the  settings (eg transport-
mode, tunnel-mode etc), results  and  requirements vis a vis cpu-power,
network-speed etc etc

all hints and suggestions welcomed
thanks in advance
sibu xolo

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org