Hi Vinicius
Thanks for replying.
>Sorry for the probably obvious question, but it's better to cover all
bases.
>The DBMS is running on the same box as Asterisk is? If that's the case then
maybe the DBMS is using too much CPU and starving Asterisk?
I don't think so - I think I have a locking
Since the issue seems to be table locking, why not take a shot with
PostgreSQL? It's way better and more robust than MySQL/MariaDB.
You should be able to create an additional DSN and output CEL to both
PostgreSQL and MariaDB.
2015-12-11 8:59 GMT-02:00 Stefan Viljoen :
On Thu, Dec 10, 2015 at 8:57 AM, Stefan Viljoen
wrote:
> Hi Matthew
>
> Thank you very much for the reply.
>
> I must have something seriously wrong somewhere else then - I retested now
> and the "apparent" effect is as I describe but your info definitely
> contradicts
Hi Matthew
Thank you very much for the reply.
I must have something seriously wrong somewhere else then - I retested now
and the "apparent" effect is as I describe but your info definitely
contradicts that. But you're obviously correct.
One more question - I've noted that if I run a
Sorry for the probably obvious question, but it's better to cover all bases.
The DBMS is running on the same box as Asterisk is? If that's the case then
maybe the DBMS is using too much CPU and starving Asterisk?
2015-12-10 12:57 GMT-02:00 Stefan Viljoen :
> Hi Matthew
Hi guys
I'm running 1.8.32.3 with CEL logging over ODBC to MariaDB 5.5.41 on the
same Centos 7 machine.
I've noticed that the CDR entries made are all in-time, e. g. the call will
take place and the CDR entry is immediately written into the CDR table in
the MariaDB database.
However, CEL events
On Wed, Dec 9, 2015 at 6:32 AM, Stefan Viljoen
wrote:
> Hi guys
>
> I'm running 1.8.32.3 with CEL logging over ODBC to MariaDB 5.5.41 on the
> same Centos 7 machine.
>
> I've noticed that the CDR entries made are all in-time, e. g. the call will
> take place and the CDR