vicidial.org

I updated my vicibox 5.02 cluster to SVN trunk r2040 a few days ago (I know we're a bit past that revision now, but I like to test things!). Anyway i was trying out the 'AST_phone_update.pl' script and the new '--agent-lookup' option but it does not seem to work.

Code: Select all

vicidial-1:/usr/share/astguiclient # ./AST_phone_update.pl --agent-lookup --debugX

|SELECT telnet_host,telnet_port,ASTmgrUSERNAME,ASTmgrSECRET,ASTmgrUSERNAMEupdate,ASTmgrUSERNAMElisten,ASTmgrUSERNAMEsend,max_vicidial_trunks,answer_transfer_agent,local_gmt,ext_context FROM servers where server_ip = '192.168.0.12';|
|SELECT distinct server_phone from vicidial_user_log where server_ip='192.168.0.12' and phone_ip='LOOKUP' and event_date > "20131125095456" and extension LIKE "SIP%";|


SIP EXTENSIONS:
|SELECT extension,phone_ip,login from phones where server_ip='192.168.0.12' and protocol='SIP' and login IN('102','109','110','112','111','105','103','101','114','113','106');|
command timed-out at ./AST_phone_update.pl line 233


I am running this on the dialling server obviously. It seems to be having an issue when talking to the asterisk server. I've fixed the asterisk version issue in the server settings, so I don't think it's that. Everything else works just fine.

Just looked at the code and it seams like that script has not been modified to work with asterisk 1.8 yet.
You can do this for a quick and dirty fix in the wait for a proper update in the svn:

Code: Select all

sed -i 's/Response:\ Pong/Response:\ Success\\nPing:\ Pong/g' AST_phone_update.pl

added this to the issue tracker http://www.vicidial.org/VICIDIALmantis/view.php?id=724 so Matt will take a look at it

Thanks Domedan, I figured it might be something like that. Unfortunately my Perl skills aren't up to scratch to fix it myself. It's not critical I have this functionality so I will wait for the official fix in SVN from matt.

Please post this to the issue tracker and I will get to it before the next release.

Domedan has logged it as Issue #724 on the tracker matt.

I can confirm this is fixed in SVN r2047. I have left a note on the bugtracker too.