Hey Jesse,

I would create a simple web service that resides on the Kamailio instances. Have the IVR’a call this web service when that spin up. The web service will take the ip as a parameter and add the ip to the dispatcher table. Likewise, you can call the web service to remove it from the list when you spin it down

Mack Hendricks dOpenSource.com

Sent from my iPhone

On Jan 15, 2019, at 10:31 AM, Jesse Strahn jesse.strahn@gmail.com wrote:

Hi all,

I'm new to Kamailio. I am using Kamailio/dispatcher to distribute calls to several SIP IVRs. I'm trying to determine the best solution to autoscale in AWS when call capacity of the IVRs is reached.

The most straight forward solution is to spin up a new IVR on a dedicated subnet when required. I would configure dispatcher such that the whole IP range of this subnet is in the dispatcher.list so that once a new instance becomes available, Kamailio starts sending calls there.

My question is, how much overhead would this add as Kamailio/dispatcher would be polling the IPs in the subnet that were not yet active. The plan would be to have a /28 subnet with 16 IPs. To start, there would be 2 active IVRs up and responding and 14 IPs in dispatcher.list that would not be responding.

Appreciate any insight.

Thanks, Jesse _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users