[OpenSIPS-Devel] [Blog] Running OpenSIPS in the Cloud

Mundkowsky, Robert rmundkowsky at ets.org
Wed Oct 25 13:47:04 EDT 2017

Nice info. There might be some more complex AWS setups people might want to use, but I really do not know from a telephony architecture if they are viable or useful:

- AWS Nat gateway (basically a NAT for a subnet of AWS instances rather than 1-to-1 NAT instances)
- Use of AWS ELB: AWS can assign multiple IPs to a AWS ELB per explicit request to AWS to allow for scaling the ELB (hence you might have multiple external IPs mapping to your private IP).
- I vaguely remember there are some settings for low latency subnet, maybe called "placement groups"
- I vaguely remember some AMIs are better for low latency (I think AWS makes some)
- Might want to use larger instances to reduce change of instance being shared or directly request dedicated instances or dedicated hosts

Robert Mundkowsky

-----Original Message-----
From: Devel [mailto:devel-bounces at lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
Sent: Wednesday, October 25, 2017 12:09 PM
To: users at lists.opensips.org; developensips <Devel at lists.opensips.org>; news at lists.opensips.org
Subject: [OpenSIPS-Devel] [Blog] Running OpenSIPS in the Cloud

Cloud computing is a more and more viable option for running and providing SIP services. The question is how compatible are the SIP services with the Cloud environment ? So let’s have a look at this compatibility from the most sensitive (for SIP protocol) perspective – the IP network topology.......



Bogdan-Andrei Iancu
   OpenSIPS Founder and Developer

Devel mailing list
Devel at lists.opensips.org


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.


More information about the Devel mailing list