On 12/01/2018 05:30 PM, Marcelo Terres wrote:> Queue_logThanks! That's not really it; however, how do I make it so that asterisk writes this information right away into a mariadb database instead of into a file so that I could actually use it?
On Tuesday 04 December 2018 at 16:11:39, hw wrote:> On 12/01/2018 05:30 PM, Marcelo Terres wrote: > > Queue_log > > Thanks! > > That's not really it; however, how do I make it so that asterisk writes > this information right away into a mariadb database instead of into a > file so that I could actually use it?Send your queue_log entries to odbc? It's a setting in extconfig.conf. Antony. -- A few words to be cautious of between American and English: - momentarily - suspenders - chips - pants - jelly - pavement - vest - pint (and gallon) - pissed Please reply to the list; please *don't* CC me.
On 12/04/2018 07:07 PM, Antony Stone wrote:> On Tuesday 04 December 2018 at 16:11:39, hw wrote: > >> On 12/01/2018 05:30 PM, Marcelo Terres wrote: >>> Queue_log >> >> Thanks! >> >> That's not really it; however, how do I make it so that asterisk writes >> this information right away into a mariadb database instead of into a >> file so that I could actually use it? > > Send your queue_log entries to odbc?odbc? Seriously?> It's a setting in extconfig.conf.Does mysql not work? It's mentioned there, too.
Maybe Matching Threads
- figuring out what happened to a call
- how to use a database (was: figuring out what happened to a call)
- Realtime mapping for 'queue_log' found to engine 'odbc', but the engine is not available
- figuring out what happened to a call
- Is not yet available ODBC support for queue_log in asterisk 1.6?