Dynamic Asterisk Realtime Architecture (ARA)

Colleagues, I have a question about Dynamic Asterisk Realtime Architecture (ARA).

I want to move local SIP accounts to an external dynamic database to make it possible to manage them from an external application.
However, several people expressed the opinion to me that this mode of operation (Dynamic ARA) is unstable, causing Asterisk memory leaks and various other problems.

Colleagues, please tell me how justified this opinion is? Is it worth using this mode now?


It’s not inherently unstable and doesn’t cause memory leaks. What it does is come with consequences, and doubles what can cause issues.

Database has issues? Asterisk has issues.

I apologize, I did not quite understand the meaning of the answer, and with your permission I will rephrase the question.

If I use this mode on an installation that is designed taking into account the load it creates, and the same applies to the database, can I say that the solution as a whole will be stable?

I will not say anything is stable. I will say that with a properly managed database you can reduce the risk of issues in Asterisk in conjunction with the database.

Thank you. But that’s not exactly what I meant.
Did I understand correctly that dynamic ARA now does not have a reputation as an unstable and poorly debugged solution?

It does not have such a reputation. I can say that we’ve had a commercial product using it for more than 10 years I think. Any problems I’ve seen or encountered with it have been the result of the database itself OR conditions that impact the database or the connectivity.

Thank you!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.