Score:0

Issabel PBX with call-center addon crashes

eg flag

I am using Issabel PBX with Asterisk 11.25.3 and Call center module (free edition). Every day once or more the system crashes. We mostly use outgoing calls. There are always 2 list. One with around 300 numbers and one with 5k numbers. The dialer.log starts rapidly filling with logs and it crashes because the memory gets used up and agents can't hangup or save form. This is the message from Dialer log that reapets:

2023-02-14 08:38:04 PID=  6149 : (AMIEventProcess) ERR: Llamada::_cb_Originatecampania outgoing ID=2007  cola 500 no se puede llamar a número: Array
(
    [Response] => Follows
    [Privilege] => Command
    [data] => Usage: database put <family> <key> <value>
       Adds or updates an entry in the Asterisk database for
       a given family, key, and value.

    [local_timestamp_received] => 1676360284.8541
    [local_timestamp_sent] => 1676360282.8254
)

2023-02-14 08:38:04 PID=  6149 : (AMIEventProcess) ERR: AMIClientConn::process_event se pierde respuesta porque no hay callback encolado: Array
(
    [Response] => Success
    [ActionID] => 6151-2007-4524479
    [Message] => Originate successfully queued
    [local_timestamp_received] => 1676360284.8608
)

2023-02-14 08:38:04 PID=  6156 : (SQLWorkerProcess) ERR: SQLWorkerProcess::_procesarUnaAccion: no se puede realizar operación de base de datos: 23000 - 1048 - Column 'new_status' cannot be null
2023-02-14 08:38:04 PID=  6156 : (SQLWorkerProcess) ERR: traza de pila: 
#0 /opt/issabel/dialer/SQLWorkerProcess.class.php(1109): PDOStatement->execute(Array)
#1 /opt/issabel/dialer/SQLWorkerProcess.class.php(1044): SQLWorkerProcess->_construirEventoProgresoLlamada(Array)
#2 [internal function]: SQLWorkerProcess->_notificarProgresoLlamada(Array)
#3 /opt/issabel/dialer/SQLWorkerProcess.class.php(213): call_user_func_array(Array, Array)
#4 /opt/issabel/dialer/SQLWorkerProcess.class.php(184): SQLWorkerProcess->_procesarUnaAccion()
#5 /opt/issabel/dialer/HubProcess.class.php(196): SQLWorkerProcess->procedimientoDemonio()
#6 /opt/issabel/dialer/HubProcess.class.php(142): HubProcess->_iniciarTareaClase('SQLWorkerProces...', 'SQLWorkerProces...')
#7 /opt/issabel/dialer/HubProcess.class.php(104): HubProcess->_iniciarTarea('SQLWorkerProces...')
#8 /opt/issabel/dialer/dialerd(405): HubProcess->procedimientoDemonio()
#9 /opt/issabel/dialer/dialerd(209): iniciarTarea('dialerd', 'HubProcess', Array, Object(AppLogger))
#10 /opt/issabel/dialer/dialerd(61): main(Array, 'Marcador predic...', 'dialerd', 'HubProcess')
#11 {main}

After that I see before a lot of RECURSION* Messages in log. Currently I am fixing it by rebooting or restarting services.

I went over all configuration, validated csv for imported numbers and it seems okay. Went on Issabel docs but I can't find a solution. We have 20 agents, 10 of them are on VPN form home.

Score:0
vc flag

I am facing the same issue of logs being filled with the above log. But my issue is different. I can't make blind transfer neither any reports under the call center module works after this starts kicking in. Did you find the solution for this, if yes please help

DzoniPfc avatar
eg flag
No , I didn't find any solution. I'm still deleting logs and rebooting.
fission avatar
in flag
This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://serverfault.com/questions/ask). To get notified when this question gets new answers, you can [follow this question](https://meta.stackexchange.com/q/345661). Once you have enough [reputation](https://serverfault.com/help/whats-reputation), you can also [add a bounty](https://serverfault.com/help/privileges/set-bounties) to draw more attention to this question. - [From Review](/review/late-answers/547592)
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.