Hi Guys,

We are running sipX in EC2 cloud. So far so good. I have a SIP trunk to
a local ITSP and also tested with a Cisco voice GW in our office as well
as soft phones (Zopier). We are using the m1.small. Media seems ok there
but we have not done any load testing yet.

We used ami ami-3284ac46, pretty much just picked a centos image. Copied
the rpms over and installed. We tried bundling a running sipX Image so
we could fire up new instances, but have not gotten that to work because
new instance comes up with new internal and external IP addresses as
well as host name. If we do get that sorted out, we also must consider
all the data that is lost when an instance crashes. Therefore you MUST
use an EBS volume and get all the sipX data to store there or maybe just
have the backups there. We have not gotten that far yet.

Elastic IP addresses is also highly recommended. No cost and makes sure
that all soft phones etc do not have to change when sipX image restarts
with new ip address.

Just some thoughts about cost. The cost of CPU is easy to calculate,
remember using a reserved instance (1 or 3 year) makes CPU cost VERY
reasonable. When it comes to data cost, I calculated one soft phone user
making 10 3 minute calls per day over 1 month will cost approx 0.10$.
Cheap!

Regards,
Sven


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Tony
Graziano
Sent: 28 November 2009 18:27
To: [email protected]
Cc: [email protected]
Subject: Re: [sipx-users] SipXecs on Amazon EC2

No. Not the same.

Your image needs to maintain all data betweens reboots and
shutdown/startup
with aws. Once you add your repo and install sipx, you have no way to
guarantee that image will keep your data at the next use.

The firewall needs to use static (symmetric) nat in order for sipxbridge
to
work.

If you're that confident give it a try and post a how-to.  "Anytime" we
do a
deployment on aws, we use our own images so the data stays intact.

As far as ram, etc., depending on your density (user), the smallest
instance
should be fine.

Good luck!
============================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

----- Original Message -----
From: Robert B <[email protected]>
To: Tony Graziano <[email protected]>
Cc: [email protected] <[email protected]>
Sent: Sat Nov 28 13:21:09 2009
Subject: Re: [sipx-users] SipXecs on Amazon EC2

Tony,

 From what I've seen, EC2 provides a firewall as well as means to
configure ports and such.

I believe there is a CentOS 5.2 AMI available as well.

It should just be a matter of adding the repositories and using yum,
AFAIK...

I agree with 4.2 being the "magic release" in terms of the media server
situation -- at least from what I've read. Still, 1.7gb of RAM included
with m1.small should conceivably be enough. I'm a bit more worried about
the single-CPU issue, however.

-- Robert



Tony Graziano wrote:
> Someone was "playing" with is earlier this month. You would need a
static
> ip, and your own ami image. Remember you have no firewall or real
"server
> behind nat" capability.
>
> You also would have to consider the "load" aspect as it relates to
media
> server in the current version.
>
> You should consult the aws docs about submitting your own ami image.
We
> have
> several ami images of our own, but have not had the need for sipx
there
> yet.
>
> I feel like the 4.2 version "might" be more cloud friendly. I for one
> would
> like an amazon s3 backup agent for it at some point too.
> ============================
> Tony Graziano, Manager
> Telephone: 434.984.8430
> Fax: 434.984.8431
>
> Email: [email protected]
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> Fax: 434.984.8427
>
> Helpdesk Contract Customers:
> http://www.myitdepartment.net/gethelp/
>
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to