Hi - I've been considering deployment options for 3CX for our multisite office (40 extns at one site plus 10 extns at a remote warehouse) I was initially going to run it locally on a MS 2008 server VM in our VMware environment, but then though it might benefit from greater resilience and connectivity if it ran on a MS 2008 cloud server at Rackspace (we have a managed account there) I spun up a server at rackspace and installed the free 3CX to test - First thing I had to consider was the internal FQDN & external FQDN settings in the wizard setup... the rackspace server has 2 virtual NICS, 1 for its public IP and the other for its internal IP. The internal IP allows it to communicate with other private rackspace servers you may have - which for this scenario is redundant. So I created a DNS A record on a test domain (3cx.testdomain.com) and pointed it to the Rackspace servers external IP - I then used that same FQDN for both the Internal FQDN and the External FQDN in the 3CX setup wizard. I figured that in this deployment scenario all our users would be external - so having the same FQDN in both wouldn't matter ? On the face of it it works - had a few issues with handsets connecting to the 3CX server through our main office firewall - but that turned out to be various Intrusion Detection signatures, and another with oneway audio - but that I'm pretty sure is due to SIP ALG on our cisco router which I'm still working out how to disable. I'm concerned that security on the Rackspace server is completely dependent on the native windows firewall - any suggestions for other software based firewalls to beef this up? I'd be interested if anyone else has deployed 3CX remotely like this and what issues they came across... cheers.