Asterisk Redundancy via Pseudo Cluster .

Pseudo Cluster to provide Asterisk Redundancy.
Today I came across this post via Astpligg, (If you do not know what Astpligg is it is time you check it out. The pure reason that you are connected to VoIP is enough to pay a visit to astpligg!)
Well have you ever wondered how to provide redundancy to your Asterisk setup. What do I do if the Asterisk Server goes down?
We all have tried many solutions, I prefer active /passive linux cluster/mirror that is too complex to explain here. It has to be a separate article. And that statement it self explain the simplicity of the method I am going show you.
I will state the obvious and let you grab the technical information from the main article.

"Main points in the proposed solution are:

• each local call from IP phones arrives in the cluster-local context. Here we only manage the local calls in the dial plan, but we could easily add standard external routing, voicemail or any kind of call.
• each call arriving from another cluster node is pushed to the cluster-from-remote context.
• FROM_CLUSTER variable is set to avoid loops between cluster members. It is set when receiving a call from a remote member et checked before routing the call to another member. If we install more than two members, this principle should be enhanced with a variable passed in the call or a specific prefix.
• when a call is passed from one member to another, the caller identifier is changed in order not to collide with SIP local extensions. Here we are using 9999 as prefix and suppress it at arrival.

This is a really simple way of providing redundancy to our Asterisk solution. It is called “cluster” but is really not a real cluster. "

Asterisk redundancy, a very simple approach by Panoramisk

Tags: Asterisk, Asterisk cluster, Asterisk redundancy, astpligg