Fallos modulo Call Center

This site is best viewed in a modern browser with JavaScript enabled.

Fallos modulo Call Center

Miguel88

Buenos días señores,

Soy algo nuevo en este mundo de vozip, estamos usando issabel en un centos 7.9 y asterisk 11.25.3 y falla con agentes logueados una 2 veces por semana se tiene que reiniciar, los fallos son los siguentes.
- dejan de funcionar los formularios
- se mezclan las campañas
- deja de funcionar los botones del panel de agente
- pierde la conexion con la base de datos y dejan de funcionar los formularios y si intentas refrescar para entrar de nuevo tampoco van.
Hay alguno mas pero no recuerdo exactamente pero vamos es el modulo call center lo que tiene que ver con el panel que tienen los agentes .

Mi pregunta es, si subimos a Asterisk 13 va a ir mejor, estos fallos son normales ?
Tengo leído por aqui que en asterisk 16 no funciona el Call Center?
En nuestro entorno se usa eso lo del call center con campañas y formularios y las llamadas que entran automáticas a agentes logueados.

Ruego si me pueden aclarar un poco.

Muchas gracias

benjange

Miguel88 Buen día. Te recomiendo que leas esto: https://lavariega.com/tips-para-reportar-un-problema-en-issabel/
por otra parte, el módulo call center funciona de manera estable con Asterisk 11, con los otros he leído que trae problemas.
Aguardamos tu respuesta.
Saludos,

Miguel88

Buenas tardes,
Muchas gracias Benja por tu aporte y el enlace.
Y muchas gracias a todo que puede aportar cualquier pista o solución.
Voy a intentar exponer mejor el problema.

Se esta usando issabel desde una vps contratada desde el proveedor de la telefonia y se usa zoiper para iniciar sesión y después se atienden las llamadas desde el panel de agente.
Adjunto las versiones:

[root@136-245 ~]# rpm -qa | grep issabel
issabel-pbx-4.0.0-6.noarch
issabel-agenda-4.0.0-3.noarch
issabel-framework-4.0.0-10.noarch
issabel-asterisk-sounds-1.2.3-2.noarch
issabel-security-4.0.0-11.noarch
issabel-reports-4.0.0-3.noarch
issabel-callcenter-4.0.0-5.noarch
issabel-fax-4.0.0-3.noarch
issabel-email_admin-4.0.0-2.noarch
issabel-addons-4.0.0-5.noarch
issabelPBX-2.11.0-48.noarch
issabel-my_extension-4.0.0-1.noarch
issabel-portknock-4.0.0-2.x86_64
issabel-system-4.0.1-0.noarch
issabel-extras-4.0.0-4.noarch
issabel-4.0.0-1.noarch
issabel-firstboot-4.0.0-4.noarch
[root@136-245 ~]# rpm -qa | grep asterisk
issabel-asterisk-sounds-1.2.3-2.noarch
asterisk-perl-1.03-1.el7.centos.noarch
asterisk11-addons-11.25.3-6.el7.x86_64
asterisk-fr-sounds-1.0.0-0.el7.centos.x86_64
asterisk11-devel-11.25.3-6.el7.x86_64
asterisk11-11.25.3-6.el7.x86_64
asterisk-es-sounds-1.0.0-0.el7.centos.x86_64

tail -f /var/log/asterisk/full
En los logs estoy observando los siguientes errores de perdida de conexión con la base de datos
Antes el error era "cdr_mysql.c: Cannot connect to database server localhost: (2002) Can't connect to local MySQL server through socket"
Para ello se han modificado los siguientes ficheros cdr_mysql.conf (/etc/asterisk) y my.conf ( /etc/) poniendo la ip del localhost y ahora el error el de abajo.

[2023-09-13 15:48:03] VERBOSE[7969][C-0000013f] pbx.c: == Spawn extension (app-announcement-25, s, 5) exited non-zero on 'SIP/TroncalNetelip-00000168'
[2023-09-13 15:48:03] ERROR[7969][C-0000013f] cdr_mysql.c: Unknown connection error: (2003) Can't connect to MySQL server on '127.0.0.1' (111)
[2023-09-13 15:48:03] ERROR[7969][C-0000013f] cdr_mysql.c: Cannot connect to database server 127.0.0.1: (2003) Can't connect to MySQL server on '127.0.0.1' (111)
[2023-09-13 15:48:03] ERROR[4445] cdr_mysql.c: Cannot connect to database server 127.0.0.1: (2003) Can't connect to MySQL server on '127.0.0.1' (111)
[2023-09-13 15:48:03] ERROR[7444] cdr_mysql.c: Cannot connect to database server 127.0.0.1: (2003) Can't connect to MySQL server on '127.0.0.1' (111)
[2023-09-13 15:48:03] ERROR[7366] cdr_mysql.c: Cannot connect to database server 127.0.0.1: (2003) Can't connect to MySQL server on '127.0.0.1' (111)
[2023-09-13 15:48:03] ERROR[7962][C-0000013e] cdr_mysql.c: Cannot connect to database server 127.0.0.1: (2003) Can't connect to MySQL server on '127.0.0.1' (111)
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: -- Executing [s@macro-hangupcall:64] GotoIf("SIP/TroncalNetelip-00000166", "1?skiprg") in new stack
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: -- Goto (macro-hangupcall,s,67)
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: -- Executing [s@macro-hangupcall:67] GotoIf("SIP/TroncalNetelip-00000166", "0?skipblkvm") in new stack
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: -- Executing [s@macro-hangupcall:68] NoOp("SIP/TroncalNetelip-00000166", "Cleaning Up Block VM Flag: BLKVM/42/SIP/TroncalNetelip-00000166") in new stack
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: -- Executing [s@macro-hangupcall:69] NoOp("SIP/TroncalNetelip-00000166", "Deleting: BLKVM/42/SIP/TroncalNetelip-00000166 TRUE") in new stack
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: -- Executing [s@macro-hangupcall:70] GotoIf("SIP/TroncalNetelip-00000166", "1?theend") in new stack
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: -- Goto (macro-hangupcall,s,72)
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: -- Executing [s@macro-hangupcall:72] AGI("SIP/TroncalNetelip-00000166", "hangup.agi") in new stack
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] res_agi.c: -- Launched AGI Script /var/lib/asterisk/agi-bin/hangup.agi
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] res_agi.c: -- <SIP/TroncalNetelip-00000166>AGI Script hangup.agi completed, returning 0
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: -- Executing [s@macro-hangupcall:73] Hangup("SIP/TroncalNetelip-00000166", "") in new stack
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] app_macro.c: == Spawn extension (macro-hangupcall, s, 73) exited non-zero on 'SIP/TroncalNetelip-00000166' in macro 'hangupcall'
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: == Spawn extension (ext-queues, h, 1) exited non-zero on 'SIP/TroncalNetelip-00000166'
[2023-09-13 15:48:03] ERROR[7935][C-0000013d] cdr_mysql.c: Cannot connect to database server 127.0.0.1: (2003) Can't connect to MySQL server on '127.0.0.1' (111)
[2023-09-13 15:48:03] VERBOSE[4752] chan_agent.c: == Agent '013' logged out
[2023-09-13 15:48:03] ERROR[4752] cdr_mysql.c: Cannot connect to database server 127.0.0.1: (2003) Can't connect to MySQL server on '127.0.0.1' (111)
[2023-09-13 15:48:03] VERBOSE[7935][C-0000013d] pbx.c: == Spawn extension (ext-queues, 42, 40) exited non-zero on 'SIP/TroncalNetelip-00000166'
[2023-09-13 15:48:03] VERBOSE[2336] asterisk.c: Asterisk cleanly ending (0).
[2023-09-13 15:48:03] VERBOSE[2336] asterisk.c: Executing last minute cleanups
[2023-09-13 15:48:03] VERBOSE[2336] res_musiconhold.c: == Destroying musiconhold processes
[2023-09-13 15:48:03] VERBOSE[2336] manager.c: == Manager unregistered action DBGet
[2023-09-13 15:48:03] VERBOSE[2336] manager.c: == Manager unregistered action DBPut
[2023-09-13 15:48:03] VERBOSE[2336] manager.c: == Manager unregistered action DBDel
[2023-09-13 15:48:03] VERBOSE[2336] manager.c: == Manager unregistered action DBDelTree
[2023-09-13 15:50:03] Asterisk 11.25.3 built by issabel @ rpm7.issabel.com on a x86_64 running Linux on 2020-02-27 19:27:59 UTC

tail -f /opt/issabel/dialer/dialerd.log

2023-09-12 15:46:43 PID= 2293 : (SQLWorkerProcess) WARN: SQLWorkerProcess::requerir_nuevaListaAgentes: agente estÃ¡tico SIP/122,2,Jania,hint:122@ext-local encontrado en cola 46 - puede causar problemas.
2023-09-12 15:46:43 PID= 2293 : (SQLWorkerProcess) WARN: SQLWorkerProcess::requerir_nuevaListaAgentes: agente estÃ¡tico SIP/130,1,Jorge U,hint:130@ext-local encontrado en cola 46 - puede causar problemas.
2023-09-12 15:46:43 PID= 2293 : (SQLWorkerProcess) WARN: SQLWorkerProcess::requerir_nuevaListaAgentes: agente estÃ¡tico SIP/125,1,Karen,hint:125@ext-local encontrado en cola 46 - puede causar problemas.
2023-09-12 15:46:43 PID= 2293 : (SQLWorkerProcess) WARN: SQLWorkerProcess::requerir_nuevaListaAgentes: agente estÃ¡tico SIP/126,1,Julieth,hint:126@ext-local encontrado en cola 46 - puede causar problemas.
2023-09-12 15:46:43 PID= 2293 : (SQLWorkerProcess) WARN: SQLWorkerProcess::requerir_nuevaListaAgentes: agente estÃ¡tico SIP/127,1,Jorge,hint:127@ext-local encontrado en cola 46 - puede causar problemas.
2023-09-12 15:46:43 PID= 2293 : (SQLWorkerProcess) WARN: SQLWorkerProcess::requerir_nuevaListaAgentes: agente estÃ¡tico SIP/104,2,Pedro,hint:104@ext-local encontrado en cola 46 - puede causar problemas.
2023-09-12 15:46:43 PID= 2288 : (AMIEventProcess) WARN: QueueShadow::msg_QueueStatusComplete: para mejorar el desempeÃ±o de campaÃ±as salientes, se recomienda activar eventwhencalled y eventmemberstatus en las siguientes colas: [006 009 010 011 012 013 014 015 016 017 018 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 0100 0101 0102 0103 0104 0105 0106 0107 0108 0109 0121 0122 0123 0124 0125 0126 0127 0130 0140 0141]
2023-09-12 15:46:43 PID= 2288 : (AMIEventProcess) INFO: evaluar pertenencia agente Agent/011 tiene estado consola logged-out

/var/loc/messages

Sep 13 15:49:37 136-245 auditd[69]: Started dispatcher: /sbin/audispd pid: 71
Sep 13 15:49:37 136-245 auditd[69]: Error sending status request (Operation not permitted)
Sep 13 15:49:37 136-245 auditd[69]: Error sending enable request (Operation not permitted)
Sep 13 15:49:37 136-245 auditd[69]: Unable to set initial audit startup state to 'enable', exiting
Sep 13 15:49:37 136-245 auditd[69]: The audit daemon is exiting.
Sep 13 15:49:37 136-245 auditd[69]: Error setting audit daemon pid (Operation not permitted)
Sep 13 15:49:37 136-245 auditd: Cannot daemonize (Success)
Sep 13 15:49:37 136-245 auditd: The audit daemon is exiting.
Sep 13 15:49:37 136-245 systemd: auditd.service: control process exited, code=exited status=1
Sep 13 15:49:37 136-245 audispd: No plugins found, exiting
Sep 13 15:49:37 136-245 systemd: Failed to start Security Auditing Service.
Sep 13 15:49:37 136-245 systemd: Unit auditd.service entered failed state.
Sep 13 15:49:37 136-245 systemd: auditd.service failed.
Sep 13 15:49:37 136-245 systemd: Starting Update UTMP about System Boot/Shutdown...
Sep 13 15:49:37 136-245 systemd: Started Update UTMP about System Boot/Shutdown.
Sep 13 15:49:37 136-245 systemd: Reached target System Initialization.
Sep 13 15:49:37 136-245 systemd: Started Daily Cleanup of Temporary Directories.
Sep 13 15:49:37 136-245 systemd: Reached target Timers.
Sep 13 15:49:37 136-245 systemd: Started Flexible branding.
Sep 13 15:49:37 136-245 systemd: Reached target Paths.
Sep 13 15:49:37 136-245 systemd: Listening on D-Bus System Message Bus Socket.
Sep 13 15:49:37 136-245 systemd: Reached target Sockets.
Sep 13 15:49:37 136-245 systemd: Reached target Basic System.
Sep 13 15:49:37 136-245 systemd: Starting SASL authentication daemon....
Sep 13 15:49:37 136-245 systemd: Starting Authorization Manager...
Sep 13 15:49:37 136-245 systemd: Starting Resets System Activity Logs...
Sep 13 15:49:37 136-245 systemd: Starting IP sets for iptables...
Sep 13 15:49:37 136-245 systemd: Started irqbalance daemon.
Sep 13 15:49:37 136-245 systemd: Starting Permit User Sessions...
Sep 13 15:49:37 136-245 systemd: Starting Builds and install new kernel modules through DKMS...
Sep 13 15:49:37 136-245 systemd: Started D-Bus System Message Bus.
Sep 13 15:49:37 136-245 saslauthd[88]: detach_tty : master pid is: 88
Sep 13 15:49:37 136-245 saslauthd[88]: ipc_init : listening on socket: /run/saslauthd/mux
Sep 13 15:49:37 136-245 polkitd[74]: Started polkitd version 0.112
Sep 13 15:49:37 136-245 /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken
Sep 13 15:49:37 136-245 systemd: Starting Login Service...
Sep 13 15:49:37 136-245 systemd: Started SASL authentication daemon..
Sep 13 15:49:37 136-245 systemd: Started Resets System Activity Logs.
Sep 13 15:49:37 136-245 systemd: Started Permit User Sessions.
Sep 13 15:49:37 136-245 systemd: Starting Cleanup of Temporary Directories...
Sep 13 15:49:37 136-245 systemd: Started Command Scheduler.
Sep 13 15:49:37 136-245 systemd: Started Cleanup of Temporary Directories.
Sep 13 15:49:37 136-245 systemd: Started Login Service.
Sep 13 15:49:37 136-245 systemd-logind: New seat seat0.
Sep 13 15:49:37 136-245 systemd: Started Authorization Manager.
Sep 13 15:49:37 136-245 systemd: Started IP sets for iptables.
Sep 13 15:49:37 136-245 systemd: Starting IPv4 firewall with iptables...
Sep 13 15:49:37 136-245 iptables.init: iptables: Applying firewall rules: [ OK ]
Sep 13 15:49:37 136-245 systemd: Started IPv4 firewall with iptables.
Sep 13 15:49:37 136-245 dkms: Error! Your kernel headers for kernel 4.15.18-27-pve cannot be found at /lib/modules/4.15.18-27-pve/build or /lib/modules/4.15.18-27-pve/source.
Sep 13 15:49:37 136-245 dkms: Please install the linux-headers-4.15.18-27-pve package or use the --kernelsourcedir option to tell DKMS where it's located.
Sep 13 15:49:37 136-245 dkms: dkms autoinstall on 4.15.18-27-pve/x86_64 failed for dahdi-linux(1)
Sep 13 15:49:37 136-245 dkms: Error! One or more modules failed to install during autoinstall.
Sep 13 15:49:37 136-245 dkms: Refer to previous errors for more information.
Sep 13 15:49:37 136-245 systemd: dkms.service: main process exited, code=exited, status=11/n/a
Sep 13 15:49:37 136-245 systemd: Failed to start Builds and install new kernel modules through DKMS.
Sep 13 15:49:37 136-245 systemd: Unit dkms.service entered failed state.
Sep 13 15:49:37 136-245 systemd: dkms.service failed.
Sep 13 15:49:37 136-245 systemd: Reached target Network (Pre).
Sep 13 15:49:37 136-245 systemd: Starting LSB: Bring up/down networking...
Sep 13 15:49:38 136-245 systemd-sysctl: Failed to write '0' to '/proc/sys/kernel/yama/ptrace_scope': Read-only file system
Sep 13 15:49:38 136-245 systemd-sysctl: Failed to write '16' to '/proc/sys/kernel/sysrq': Read-only file system
Sep 13 15:49:38 136-245 systemd-sysctl: Failed to write '1' to '/proc/sys/kernel/core_uses_pid': Read-only file system
Sep 13 15:49:38 136-245 systemd-sysctl: Failed to write '1' to '/proc/sys/kernel/kptr_restrict': Read-only file system
Sep 13 15:49:38 136-245 systemd-sysctl: Failed to write '1' to '/proc/sys/fs/protected_hardlinks': Read-only file system
Sep 13 15:49:38 136-245 systemd-sysctl: Failed to write '1' to '/proc/sys/fs/protected_symlinks': Read-only file system
Sep 13 15:49:38 136-245 network: Bringing up loopback interface: [ OK ]
Sep 13 15:49:42 136-245 network: Bringing up interface eth0: [ OK ]
Sep 13 15:49:42 136-245 systemd-sysctl: Failed to write '0' to '/proc/sys/kernel/yama/ptrace_scope': Read-only file system
Sep 13 15:49:42 136-245 systemd-sysctl: Failed to write '16' to '/proc/sys/kernel/sysrq': Read-only file system
Sep 13 15:49:42 136-245 systemd-sysctl: Failed to write '1' to '/proc/sys/kernel/core_uses_pid': Read-only file system
Sep 13 15:49:42 136-245 systemd-sysctl: Failed to write '1' to '/proc/sys/kernel/kptr_restrict': Read-only file system
Sep 13 15:49:42 136-245 systemd-sysctl: Failed to write '1' to '/proc/sys/fs/protected_hardlinks': Read-only file system
Sep 13 15:49:42 136-245 systemd-sysctl: Failed to write '1' to '/proc/sys/fs/protected_symlinks': Read-only file system
Sep 13 15:49:42 136-245 systemd: Started LSB: Bring up/down networking.
Sep 13 15:49:42 136-245 systemd: Reached target Network.
Sep 13 15:49:42 136-245 systemd: Starting MariaDB database server...
Sep 13 15:49:42 136-245 systemd: Reached target Network is Online.
Sep 13 15:49:42 136-245 systemd: Starting LSB: DAHDI kernel modules...
Sep 13 15:49:42 136-245 systemd: Starting System Logging Service...
Sep 13 15:49:42 136-245 systemd: Starting Dynamic System Tuning Daemon...
Sep 13 15:49:42 136-245 systemd: Starting The Apache HTTP Server...
Sep 13 15:49:42 136-245 systemd: Starting Cyrus-imapd IMAP/POP3 email server...
Sep 13 15:49:42 136-245 systemd: Starting /etc/rc.d/rc.local Compatibility...
Sep 13 15:49:42 136-245 systemd: Starting Fail2Ban Service...
Sep 13 15:49:42 136-245 systemd: Starting OpenSSH server daemon...
Sep 13 15:49:42 136-245 systemd: Starting Postfix Mail Transport Agent...
Sep 13 15:49:42 136-245 systemd: Starting Xinetd A Powerful Replacement For Inetd...
Sep 13 15:49:42 136-245 rsyslogd: [origin software="rsyslogd" swVersion="8.24.0-57.el7_9.3" x-pid="636" x-info="http://www.rsyslog.com"] start
Sep 13 15:49:42 136-245 systemd: Starting Crash recovery kernel arming...
Sep 13 15:49:42 136-245 systemd: Started System Logging Service.
Sep 13 15:49:42 136-245 systemd: Started Fail2Ban Service.
Sep 13 15:49:42 136-245 systemd: Can't open PID file /var/run/xinetd.pid (yet?) after start: No such file or directory
Sep 13 15:49:42 136-245 systemd: Started Xinetd A Powerful Replacement For Inetd.
Sep 13 15:49:42 136-245 systemd: Started OpenSSH server daemon.
Sep 13 15:49:42 136-245 dahdi: Loading DAHDI hardware modules:
Sep 13 15:49:42 136-245 systemd: Created slice User Slice of cyrus.
Sep 13 15:49:42 136-245 xinetd[670]: xinetd Version 2.3.15 started with libwrap loadavg labeled-networking options compiled in.
Sep 13 15:49:42 136-245 xinetd[670]: Started working: 0 available services
Sep 13 15:49:42 136-245 systemd: Started Session c1 of user cyrus.
Sep 13 15:49:42 136-245 kdumpctl: No memory reserved for crash kernel
Sep 13 15:49:42 136-245 kdumpctl: Starting kdump: [FAILED]
Sep 13 15:49:42 136-245 systemd: kdump.service: main process exited, code=exited, status=1/FAILURE
Sep 13 15:49:42 136-245 systemd: Failed to start Crash recovery kernel arming.
Sep 13 15:49:42 136-245 systemd: Unit kdump.service entered failed state.
Sep 13 15:49:42 136-245 systemd: kdump.service failed.
Sep 13 15:49:42 136-245 rc.local: Cannot open /etc/fxotune.conf!
Sep 13 15:49:43 136-245 mariadb-prepare-db-dir: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Sep 13 15:49:43 136-245 mariadb-prepare-db-dir: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir.
Sep 13 15:49:43 136-245 fail2ban-server: 2023-09-13 15:49:43,323 fail2ban [659]: ERROR Failed during configuration: File contains no section headers.
Sep 13 15:49:43 136-245 fail2ban-server: file: /etc/fail2ban/jail.local, line: 1
Sep 13 15:49:43 136-245 fail2ban-server: 'START issabel\n'
Sep 13 15:49:43 136-245 fail2ban-server: 2023-09-13 15:49:43,326 fail2ban [659]: ERROR Async configuration of server failed
Sep 13 15:49:43 136-245 systemd: fail2ban.service: main process exited, code=exited, status=255/n/a
Sep 13 15:49:43 136-245 systemd: Unit fail2ban.service entered failed state.
Sep 13 15:49:43 136-245 systemd: fail2ban.service failed.
Sep 13 15:49:43 136-245 systemd: Started The Apache HTTP Server.
Sep 13 15:49:44 136-245 mysqld_safe: 230913 15:49:44 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.

benjange

Miguel88 hola, tu versión del módulo de Call Center es 4.0.5 y la estable es la 4.0.4.
Mira en esta entrada https://forum.issabel.org/d/5049-modulo-de-call-center-si-o-no/5
Vas a tener que hacer un downgrade a dicha versión.
Saludos,

Miguel88

Buenos días.

Muchas gracias por tu respuesta, tiene pinta ser eso que me comentas, voy a tratar de bajar la versión a 4.0.4 y os comento en unos días.

Gracias, un saludo