Your trunks should be "close" to your AWS region. You should use a plain vanilla Centos 5.5/5.6 x64 image and install from yum by adding the repo. The image needs to be set to not terminate (delete your data). I think in AWS it means your should be using a bootable EBS volume.
Other than firewall and scaling it for your needs there are no gotchas to get it up and running if you understand the firewall and dns in amazon-ese. If you expect a lot of media server activity you might lean towards a physical machine though. There are still going to be issues with media and latency that can't be overcome ina virtual environment just yet as I understand it anyway. On Fri, Jun 10, 2011 at 9:00 AM, Nalin Mistry <[email protected]> wrote: > Hi all, > Just wanted to check if there is an image for SipX 4.4 available for Amazon > EC2 AMI that has been tried and tested. Any pointers would be appreciated > including any gotcha's to watch out for. > Thanks.....Nalin > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
