AstriCon 2018

By inserting OpenSIPS as edge server for an Asterisk deployment, you can expand your service with a minimal set of changes. The expansions can be in terms of load, of geo-scaling or of extra services. The OpenSIPS edge is able to off load traffic and load by acting as mid-registrar, as a presence server or a dispatcher for call queues. Even more, the presence of an edge server in your network, allows you to scale up the system by moving from a single Asterisk box to a cluster of Asterisk boxes; a cluster where OpenSIPS edge is perfectly capable to perform traffic load balancing (with realtime ARI integration).The scaling as load is just the first step. An geographically distributed platform is the ultimate goal. The load and the service is distributed over multiple PoP / DataCenters, with data redundancy across the entire platform. The OpenSIPS edge server is responsible for providing failover between the Asterisk servers, but also to provide High Availability when comes to reaching your platform from outside network. And what great tool Anycast is for doing multi-site failover. OpenSIPS 2.4 masters the anycast support, being able to failover ongoing calls between different sites.In the same time, the OpenSIPS edge is a good way of inserting new services into your platform, without touching the rest of it. Cname or LNP lookups, LCR routing or Push Notification services, all can be made available for your users by a direct deployment on OpenSIPS.