asterisk users - Jun 2018 - Best way to update ever changing dialplans

I am working on a system where I connect to an external API and based on
what it gives me I generate the Asterisk dial plan accordingly. I am
thinking about my different options and wanted feedback from others on how
to best do it.
1) Generate conf files for Asterisk - This seems the easiest but then I
will be doing a dial plan reload on all of my dial plan for handful of
lines of code. The plus side is once reload is don the dial plan is in
memory.
2) Using real time + mysql - Seems like an overkill to have mysql running
taking resources for a few lines.
3) Using real time + sqlite3 - This seems like the best option but then we
go to disk every time there is a call.

Any other options that I am not thinking of?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180625/e8128439/attachment.html>

On Mon, 25 Jun 2018, Dovid Bender wrote:
> I am working on a system where I connect to an external API and based on 
> what it gives me I generate the Asterisk dial plan accordingly. I am 
> thinking about my different options and wanted feedback from others on 
> how to best do it.1) Generate conf files for Asterisk - This seems the 
> easiest but then I will be doing a dial plan reload on all of my dial 
> plan for handful of lines of code. The plus side is once reload is don 
> the dial plan is in memory.
> 2) Using real time + mysql - Seems like an overkill to have mysql 
> running taking resources for a few lines.
> 3) Using real time + sqlite3 - This seems like the best option but then 
> we go to disk every time there is a call.
> Any other options that I am not thinking of?
I think that you have enumerated the reasonable options. I'd vote for #1.

1) Easier to implement and debug.

2) Easier to 'snapshot' for backup and restore.

Other factors that may bias my choice would be the size of the dialplan 
and the frequency of the updates.

Maybe another option would be to use the CLI 'dialplan add' and
'dialplan
remove' commands.

-- 
Thanks in advance,
-------------------------------------------------------------------------
Steve Edwards       sedwards at sedwards.com      Voice: +1-760-468-3867 PST
             https://www.linkedin.com/in/steve-edwards-4244281

> Maybe another option would be to use the CLI 'dialplan add' and
'dialplan remove' commands.

… followed by 'dialplan save'

-- 
Bertrand LUPART
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180626/7431d4c2/attachment.html>

On 06/25/2018 09:54 AM, Dovid Bender wrote:
> I am working on a system where I connect to an external API and based on
what it gives me I generate the Asterisk dial plan accordingly. I am thinking
about my different options
> and wanted feedback from others on how to best do it.
> 1) Generate conf files for Asterisk - This seems the easiest but then I
will be doing a dial plan reload on all of my dial plan for handful of lines of
code. The plus side is once
> reload is don the dial plan is in memory.
> 2) Using real time + mysql - Seems like an overkill to have mysql running
taking resources for a few lines.
> 3) Using real time + sqlite3 - This seems like the best option but then we
go to disk every time there is a call.
> 
> Any other options that I am not thinking of?
> 
I don't think you missed any options.

Call me silly, number 2 has always been my preference.  Flat file configuration
bugs me except for the simplest
of things.

Since you mention the external API, you already have a fairly complex
environment... And pretty likely to have, at
some point, multiple asterisk instances.  Surprise! The realtime mysql dialplan
can be shared among them.

But I'm crazy that way.

Depends on how complex the generated dial-plan is.If it is in a
monitored production environment, you could have an ARI app and just
let it handle it all, especially if it needs to make complex decisions
that end in simple choices (like: detecting the caller, asking them
some questions but finally routing to queue A versus B).

2018-06-25 18:54 GMT+02:00 Dovid Bender <dovid at
telecurve.com>:
> I am working on a system where I connect to an external API and based on
> what it gives me I generate the Asterisk dial plan accordingly. I am
> thinking about my different options and wanted feedback from others on how
> to best do it.
> 1) Generate conf files for Asterisk - This seems the easiest but then I
will
> be doing a dial plan reload on all of my dial plan for handful of lines of
> code. The plus side is once reload is don the dial plan is in memory.
> 2) Using real time + mysql - Seems like an overkill to have mysql running
> taking resources for a few lines.
> 3) Using real time + sqlite3 - This seems like the best option but then we
> go to disk every time there is a call.
>
> Any other options that I am not thinking of?
>
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at:
> https://community.asterisk.org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users


-- 
Loway - home of QueueMetrics - http://queuemetrics.com
Try the WombatDialer auto-dialer @ http://wombatdialer.com