vicidial.org

Hi all,
when I try to upgrade my Asterisk server from 1.4.22 to 1.6.0.9 I've seen a problem that prevent me to connect in CLI ( == Connect attempt from '192.168.1.150' unable to authenticate) and when I launch the script ( /usr/share/astguiclient/AST_update.pl --debugX) I got this:

----- SUPER-DUPER DEBUGGING -----
BUILD: 61227-1659
SHOW CHANNELS format: 1
LOOKING FOR Zap clients assigned to this server:
|SELECT extension FROM phones where protocol = 'Zap' and server_ip='192.168.1.114'|
LOOKING FOR IAX2 clients assigned to this server:
|SELECT extension FROM phones where protocol = 'IAX2' and server_ip='192.168.1.114'|
LOOKING FOR SIP clients assigned to this server:
|SELECT extension FROM phones where protocol = 'SIP' and server_ip='192.168.1.114'|
2000
1000
1111
Zap Clients: |
IAX2 Clients: |
SIP Clients: |2000|2000@2000|1000|1000@1000|1111|1111@1111|
pattern match timed-out at /usr/share/astguiclient/AST_update.pl line 370


Here the sql statement:
SELECT telnet_host,telnet_port,ASTmgrUSERNAME,ASTmgrSECRET,ASTmgrUSERNAMEupdate,ASTmgrUSERNAMElisten,ASTmgrUSERNAMEsend,max_vicidial_trunks,answer_transfer_agent,local_gmt,ext_context,asterisk_version,sys_perf_log,vd_server_logs FROM servers where server_ip = "192.168.1.114";
+---------------+-------------+----------------+--------------+----------------------+----------------------+--------------------+---------------------+-----------------------+-----------+-------------+------------------+--------------+----------------+
| telnet_host | telnet_port | ASTmgrUSERNAME | ASTmgrSECRET | ASTmgrUSERNAMEupdate | ASTmgrUSERNAMElisten | ASTmgrUSERNAMEsend | max_vicidial_trunks | answer_transfer_agent | local_gmt | ext_context | asterisk_version | sys_perf_log | vd_server_logs |
+---------------+-------------+----------------+--------------+----------------------+----------------------+--------------------+---------------------+-----------------------+-----------+-------------+------------------+--------------+----------------+
| 192.168.1.114 | 5038 | test | mysecret | updatecron | listencron | sendcron | 23 | 8365 | 1.00 | default | CVS_HEAD | Y | Y |
+---------------+-------------+----------------+--------------+----------------------+----------------------+--------------------+---------------------+-----------------------+-----------+-------------+------------------+--------------+----------------+

manager_additional.conf :
[listencron]
secret = mysecret
deny=0.0.0.0/0.0.0.0
permit=192.168.1.150/255.255.255.0
read = system,call,log,verbose,command,agent,user
write = command,

[sendcron]
secret = mysecret
deny=0.0.0.0/0.0.0.0
permit=192.168.1.150/255.255.255.0
read = command,
write = system,call,log,verbose,command,agent,user

[updatecron]
secret = mysecret
deny=0.0.0.0/0.0.0.0
permit=192.168.1.150/255.255.255.0
read = command,
write = command,

I can see sometimes message that inform me about [sendcron] logged in etc...
but I still receive ( == Connect attempt from '192.168.1.150' unable to authenticate) I guess it's about [listencron] and [updatecron]

Please help me to fix this issue. THX

screen -ls
There are screens on:
30310.ASTlisten (11.05.2009 15:50:02) (Detached)
30304.ASTupdate (11.05.2009 15:50:02) (Detached)
30307.ASTsend (11.05.2009 15:50:02) (Detached)
2402.ASTVDadapt (08.05.2009 11:52:02) (Detached)
2408.ASTVDautoFILL (08.05.2009 11:52:02) (Detached)
2405.ASTfastlog (08.05.2009 11:52:02) (Detached)
6 Sockets in /var/run/screen/S-root.

Is asterisk 1.6 branch supported at all? Search the forum, I've seen posts from vicidial maintainers regarding 1.6 and why it's not yet supported as far as I remember.

I don't know the result of this discussion:
http://www.eflo.net/VICIDIALforum/posti ... ply&t=7958

but I confirm the related problem with manager.conf in this version (1.6).

ViciDial does not support Asterisk 1.6. It is not stable under any kind of load so we do not support it at this time.

It's clear that Asterisk 1.6 is unsupported but it should be mentioned in documentation provided with Vicidial, here is the solution (Asterisk 1.4.24.1)
http://www.eflo.net/VICIDIALforum/viewtopic.php?t=6700

Thanks for the suggestion, a note will go into the REQUIREMENTS.txt doc on the next SVN trunk commit I do.