[asterisk-app-dev] Moving the Asterisk Bridge from one Asterisk to another

[Ben Merrills]

Let me answer your last question first.

Asterisk doesn’t handle multiple Stasis applications connecting with the same name. The relationship between Asterisk and Stasis application is one to one (one web socket per application name). However, you can get round this using an ARI proxy (see below). Using an ARI proxy allows you to

1.      Have multiple instances of your application run on multiple servers

2.      Provide load balancing between application servers

3.      Failover support for your application

There are two implementations of an ARI proxy. The first written by me, in .NET (supports mono)can be found here https://github.com/skrusty/AsterNET-ARI-Proxy
The second is written in GoLang and can be found here: https://github.com/nvisibleinc/go-ari-proxy

You can read about the concepts behind ARI proxy on my blog. http://www.xdev.net/2015/09/18/distributed-applications-with-ari/

With regards to stopping new calls in Asterisk, you can use the stop graceful cli command to prevent new calls from being processed on that asterisk box.

Hope that helps a little,

Ben

From: asterisk-app-dev-bounces at lists.digium.com [mailto:asterisk-app-dev-bounces at lists.digium.com] On Behalf Of Nitesh Bansal
Sent: 13 May 2016 14:56
To: Asterisk Application Development discussion <asterisk-app-dev at lists.digium.com>
Subject: [asterisk-app-dev] Moving the Asterisk Bridge from one Asterisk to another

Hello,
I'm working on an ARI based bridging application.
My concern is how to gracefully handle the failovers, upgrades.
In case of planned upgrade, 0
I can see following possibilities but I have no clue about how they
will work out?
1. Move the Bridge to the new Asterisk?
2. Bridge the old asterisk to the new asterisk, but don't forward any new
    calls to the Asterisk under upgrade. Wait for call count to drop to zero
    for Asterisk under upgrade.

3. Let first Asterisk run until the call count drops to zero, keep accepting calls
for the existing bridge, but forward any new Bridge request to the new Asterisk.
How does Asterisk behaving if multiple ARI clients connect with Asterisk for the same
Stasis application?

Any ideas/recommendations?

Regards,
Nitesh
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7597 / Virus Database: 4568/12208 - Release Date: 05/11/16
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20160513/cb79eb37/attachment.html>