vicidial.org

As I can verify the correct operation of VICIDIAL?

Como puedo verificar el correcto funcionamiento de VICIDIAL ?

Thanks in advance

Gracias de Antemano!

Code: Select all

SO : Centos
Asterisk : 1.4.21.2
VICIDIAL : 2.2.1

Code: Select all

[root@VICIDIAL ~]# screen -ls
There are screens on:
        3314.ASTVDadapt (Detached)
        3339.asterisk   (Detached)
        3488.ASTlisten  (Detached)
        3282.astshell20120507152701     (Detached)
        3495.ASTVDremote        (Detached)
        3492.ASTVDauto  (Detached)
        3317.ASTfastlog (Detached)
        3483.ASTupdate  (Detached)
        3486.ASTsend    (Detached)

Code: Select all

/var/spool/mail/root

From root@localhost.localdomain  Mon May  7 15:26:37 2012
Return-Path: <root@localhost.localdomain>
Received: from localhost.localdomain (VICIDIAL [127.0.0.1])
        by localhost.localdomain (8.13.8/8.13.8) with ESMTP id q47KQbRA003013
        for <root@localhost.localdomain>; Mon, 7 May 2012 15:26:37 -0500
Received: (from root@localhost)
        by localhost.localdomain (8.13.8/8.13.8/Submit) id q47KPFNv004506;
        Mon, 7 May 2012 15:25:15 -0500
Date: Mon, 7 May 2012 15:25:15 -0500
Message-Id: <201205072025.q47KPFNv004506@localhost.localdomain>
From: root@localhost.localdomain (Cron Daemon)
To: root@localhost.localdomain
Subject: Cron <root@VICIDIAL> /usr/share/astguiclient/AST_manager_kill_hung_congested.pl
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>

DBD::mysql::st execute failed: MySQL server has gone away at /usr/share/astguiclient/AST_manager_kill_hung_congested.pl line 189.
executing: SELECT channel FROM live_sip_channels where server_ip = '127.0.0.1' and extension = 'CONGEST' and channel LIKE "Local%" limit 99 MySQL server has gone away at /usr/share/astguiclient/AST_manager_kill_hung_congested.pl line 189.



From root@localhost.localdomain  Mon May  7 15:27:01 2012
Return-Path: <root@localhost.localdomain>
Received: from localhost.localdomain (VICIDIAL [127.0.0.1])
        by localhost.localdomain (8.13.8/8.13.8) with ESMTP id q47KR1qt003289
        for <root@localhost.localdomain>; Mon, 7 May 2012 15:27:01 -0500
Received: (from root@localhost)
        by localhost.localdomain (8.13.8/8.13.8/Submit) id q47KR1MK003287;
        Mon, 7 May 2012 15:27:01 -0500
Date: Mon, 7 May 2012 15:27:01 -0500
Message-Id: <201205072027.q47KR1MK003287@localhost.localdomain>
From: root@localhost.localdomain (Cron Daemon)
To: root@localhost.localdomain
Subject: Cron <root@VICIDIAL> /usr/share/astguiclient/AST_conf_update.pl
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>

problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_conf_update.pl line 239


From root@localhost.localdomain  Mon May  7 15:27:01 2012
Return-Path: <root@localhost.localdomain>
Received: from localhost.localdomain (VICIDIAL [127.0.0.1])
        by localhost.localdomain (8.13.8/8.13.8) with ESMTP id q47KR1KK003290
        for <root@localhost.localdomain>; Mon, 7 May 2012 15:27:01 -0500
Received: (from root@localhost)
        by localhost.localdomain (8.13.8/8.13.8/Submit) id q47KR1HE003288;
        Mon, 7 May 2012 15:27:01 -0500
Date: Mon, 7 May 2012 15:27:01 -0500
Message-Id: <201205072027.q47KR1HE003288@localhost.localdomain>
From: root@localhost.localdomain (Cron Daemon)
To: root@localhost.localdomain
Subject: Cron <root@VICIDIAL> /usr/share/astguiclient/AST_vm_update.pl
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>

problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_vm_update.pl line 174

you verify correct operating by using it as a dialer. (usually if it works in auto-dial mode ... it should be fully functional).

the first error above is the server shutting down (kinda makes things not work for a few minutes) and the port 5038 is a script failing to update. You should manually execute that script to see what it does and why it's failing ... if you care about VM being Updated.