At this point we will initiate the process to Create an EC2 Instance using Sangoma's SBC AMI.Login to your AWS Console and go to your EC2 dashboard:.(For testing purposes you can start with a Free Tier Elegible Instance such as t2.micro - 1.5 Gig, 1 Core).External Interface in the Public subnet at: 10.0.0.133.Internal interface in the Private subnet at: 10.0.1.133.
Our VPC Will have the following attributes:
(For more details about this VPC scenario see: )įor our exercise we will be using a VPC similar to this one: In our example we are using a VPC with Public and Private Subnets, as this scenario perfectly fits the need to have VoIP resources in a private subnet, not accesibe from the exterior, and the SBC located in the Public Subnet enabling remote endpoints and Service providers to reach VoIP resoruces in a controlled and secured fasion.
There are several VPC scenarios offered in AWS (See: ). Here we are going to show you how to deploy Sangoma SBC VM as an EC2 (Elastic Compute Cloud) Instance inside a VPC (Virtual Private Cloud). One of the interesting use cases for Sangoma SBC is to provide VoIP Edge connectivity between Softswitches or IPPBX's and VoIP End Points of IP Telephony Service providers (ITSP's)
0 kommentar(er)
