Chris,<br><br>This is good stuff! Would you be willing to compare this to what's on the wiki and update the wiki as needed? I believe we have some EC2 information on the wiki...<br><br>Thanks,<br>MC<br><br><div class="gmail_quote">
On Wed, Mar 3, 2010 at 9:17 AM, Chris Fowler <span dir="ltr"><chris@fowler.cc></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Rob,<br>
<br>
We run FreeSWITCH on AWS' EC2. A medium EC2 instance is happily supporting 100 Polycom users, conference bridges etc. Been running for over a year. We also use FlowRoute as our PSTN->SIP Interface, and also Skype Business SIP. Our users are scattered across the globe - so having the box sitting on AWS' network infrastructure is key to avoiding issues with latency, jitter, packet loss (i.e. I don't think we could afford the connectivity AWS gives us if we had to provision this in-house).<br>
<br>
There were no special tricks; you do need to modify/override the following with the box's Elastic IP (EIP).<br>
<br>
modify conf/vars.xml and update<br>
<X-PRE-PROCESS cmd="set" data="domain=<YOUR DOMAIN HERE>"/><br>
<br>
<X-PRE-PROCESS cmd="set" data="default_provider=<a href="http://sip.flowroute.com" target="_blank">sip.flowroute.com</a>"/><br>
<X-PRE-PROCESS cmd="set" data="default_provider_username=<USER>"/><br>
<X-PRE-PROCESS cmd="set" data="default_provider_password=<PASS>"/><br>
<X-PRE-PROCESS cmd="set" data="default_provider_from_domain=<a href="http://flowroute.com" target="_blank">flowroute.com</a>"/><br>
<X-PRE-PROCESS cmd="set" data="default_provider_register=true"/><br>
<br>
<X-PRE-PROCESS cmd="set" data="bind_server_ip=<AWS EIP>"/><br>
<X-PRE-PROCESS cmd="set" data="external_rtp_ip=<AWS EIP>"/><br>
<X-PRE-PROCESS cmd="set" data="external_sip_ip=<AWS EIP>"/><br>
<br>
<X-PRE-PROCESS cmd="set" data="outbound_caller_name=<YOUR NAME>"/><br>
<X-PRE-PROCESS cmd="set" data="outbound_caller_id=<YOUR CID>"/><br>
<br>
conf/sip_profiles/internal.xml<br>
<param name="aggressive-nat-detection" value="true"/><br>
<param name="multiple-registrations" value="true"/><br>
<param name="ext-rtp-ip" value="$${external_rtp_ip}"/><br>
<param name="ext-sip-ip" value="$${external_sip_ip}"/><br>
<param name="NDLB-received-in-nat-reg-contact" value="true"/><br>
<param name="NDLB-force-rport" value="true"/><br>
<param name="NDLB-broken-auth-hash" value="true"/><br>
<param name="enable-timer" value="false"/><br>
<br>
conf/sip_profiles/external.xml<br>
<param name="aggressive-nat-detection" value="true"/><br>
<param name="ext-rtp-ip" value="$${external_rtp_ip}"/><br>
<param name="ext-sip-ip" value="$${external_sip_ip}"/><br>
<param name="NDLB-force-rport" value="true"/><br>
<br>
conf/autoload/switch.conf.xml<br>
<param name="rtp-start-port" value="16384"/><br>
<param name="rtp-end-port" value="32768"/><br>
<br>
<br>
Cheers, Chris.<br>
--<br>
RightScale, Inc.<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:freeswitch-users-bounces@lists.freeswitch.org">freeswitch-users-bounces@lists.freeswitch.org</a> [mailto:<a href="mailto:freeswitch-users-bounces@lists.freeswitch.org">freeswitch-users-bounces@lists.freeswitch.org</a>] On Behalf Of Rob Forman<br>
Sent: Tuesday, March 02, 2010 9:05 PM<br>
To: <a href="mailto:freeswitch-users@lists.freeswitch.org">freeswitch-users@lists.freeswitch.org</a><br>
Subject: [Freeswitch-users] Virtualized FreeSWITCH<br>
<br>
Hi all,<br>
<br>
Is anyone running FreeSWITCH virtualized (xen or vmware) in<br>
production? I saw ec2 and xen mentioned a few places. If so, are<br>
there tips or tricks for handle timer issues which affect virtual<br>
machines in general, such as recommended divider or clocksource<br>
settings? I'm seeing funny timing issues while testing with audio<br>
recording and playback that speed up or slow down.<br>
<br>
I have tried both paravirt and hvm. The default xen kernel has a<br>
timer of 250, so I tried to hvm instead using the stock 5.3 kernel<br>
with the 1khz timer but didn't see much improvement.<br>
<br>
All of this was tested on 64-bit CentOS 5.3.<br>
- Physical host: Linux localhost.localdomain 2.6.18-164.11.1.el5xen #1<br>
SMP Wed Jan 20 08:06:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux<br>
CONFIG_HZ=250<br>
- Paravirt host: Linux localhost.localdomain 2.6.18-128.el5xen #1 SMP<br>
Wed Jan 21 11:12:42 EST 2009 x86_64 x86_64 x86_64 GNU/Linux<br>
CONFIG_HZ=250<br>
- Hvm host: Linux localhost.localdomain 2.6.18-128.el5 #1 SMP Wed Jan<br>
21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux<br>
CONFIG_HZ=1000<br>
<br>
<br>
I'm sure physical hosts are the de-facto best practice, but are<br>
virtual machines not worth it at all?<br>
<br>
Cheers,<br>
Rob<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br>