Missed you all at DevCon this year! Happy to chime in on this one, having
had some experience with relatively large fleets of Asterisk servers for
various purposes. Certainly seen a few themes...
* Dialplan versioning and deployment. I have relied on static
dialplans with HTTP or func_odbc calls
Hi,
* in asterisk cli, display instance name to which is attached, in other
words, if the being controlled instance has "systemname => bar" on a
host with hostname "foo", then instead of the prompt being:
foo*CLI>
Either:
foo*bar*CLI>
or simply:
bar*CLI>
Would be great. This is actually
Hi,
On 2020/10/20 23:32, Michael Cargile wrote:
> Towards the end of DevCon, Matt asked if there were any pain points
> for provisioning large numbers of Asterisk instances and I mentioned I
> would talk to my colleague who handles such things. He provided this
> list:
>
> * Sanity checks within
On 10/20/2020 5:32 PM, Michael Cargile wrote:
* Reliable module reloading without core restarts
Example: Client lets their SSL certificate lapse on an Asterisk
server and they only figure this out when their
agents attempting to log in using WebRTC clients. They have
dozens or even
Towards the end of DevCon, Matt asked if there were any pain points for
provisioning large numbers of Asterisk instances and I mentioned I would
talk to my colleague who handles such things. He provided this list:
* Sanity checks within Asterisk at start up and module reload. this
include:
