VICIDial Email

[sajiahma]

Hello Team,

I have been trying to setup vicidial email module. I have set everything except for the last part which happens to be setting up cron job for auto email retrieval.

For some odd reason the cron job mentionaed doesnt seems to be working.

*/2 * * * * /usr/share/astguiclient/AST_inbound_email_parser.pl --force-check
*/1 * * * * /usr/share/astguiclient/AST_inbound_email_parser.pl --force-check
* * * * * /usr/share/astguiclient/AST_inbound_email_parser.pl --force-check --debugX
* * * * * /usr/share/astguiclient/AST_inbound_email_parser.pl

VICIDial Version - 2.14b0.5
Asterisk Version - 11.22.0-vici
CentOS Linux release 7.6.1810
Email Server : Gmail
Protocol - IMAP

When I run the AST_inbound_email_parser.pl from command line with --force-check, the emails are retrieved and assigned even to the agent. But it doesnt work with cron.

Any help will be highly appreciated.

[williamconley]

you appear to have posted the crontab version, but you have not posted the cli method that worked. As this is a very technical situation, that would be a good thing to include.

Also: you have not posted a link to your installation instructions (or iso installer if it's a goautodial install cd). once again, this information may prove critical to a solution.

Of course you can also check your system logs to be sure the system is attempting to fire up the process and possibly the system email user as many times the attempt fails but generates an email to the system user explaining the crash.

[sajiahma]

Thanks for your reply. This is a scratch installation done by following the below link :-

http://astguiclient.sourceforge.net/scr ... stall.html

below worked from the command line :-

/usr/share/astguiclient/AST_inbound_email_parser.pl --force-check -debugX.

As per the cron logs, this job does fire but it doesnt fetch any emails.

Can you please tell me precisely which logs to look into ?

[sajiahma]

This is fixed now. Thanks for all your support

When the script was running from CLI, the location of perl libs were identified but when running from cron , it was failing to identify perl lin path.

Can't locate MIME/Decoder.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/share/astguiclient/AST_inbound_email_parser.pl line 6.

Edited the AST_inbound_email_parser.pl and declared the perl path as following :-

use lib '/root/perl5/lib/perl5';

and now it works like a charm.

[williamconley]

The installation link you provided is for Slackware. But you're on CentOS. Did you actually modify a slackware install to work on CentOS? Or is that the wrong link from your install notes?

IF you modified the slackware install to work on CentOS (but forgot to add the perl path,which is not uncommon and easily fixed), posting your final installation script/steps on a blog or even here in this ticket would be very useful for later installers. CentOS is popular and recently the Goautodial installation seems to be outdated.

[sajiahma]

It seems i posted a wrong link. I am running CentOS.

[williamconley]

In which case, posting the instructions (link or full) you actually used is a good idea. If you still have them.

[sajiahma]

I referred to below link while vicidial installation :-

https://swanand18.blogspot.com/2017/06/ ... tos-7.html

The details of fix :-
When the script was running from CLI, the location of perl libs were identified but when running from cron , it was failing to identify perl lin path.

Can't locate MIME/Decoder.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/share/astguiclient/AST_inbound_email_parser.pl line 6.

Edited the AST_inbound_email_parser.pl and declared the perl path as following :-

use lib '/root/perl5/lib/perl5';

Hope this helps.

[williamconley]

I referred to below link while vicidial installation :-

https://swanand18.blogspot.com/2017/06/ ... tos-7.html

The details of fix :-
When the script was running from CLI, the location of perl libs were identified but when running from cron , it was failing to identify perl lin path.

Can't locate MIME/Decoder.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/share/astguiclient/AST_inbound_email_parser.pl line 6.

Edited the AST_inbound_email_parser.pl and declared the perl path as following :-

use lib '/root/perl5/lib/perl5';

Hope this helps.

EXCELLENT postback. Well done. You may want to investigate the PATH for the cron system in your OS. That, too, can be edited to include the perl libraries. It may be a matter of defining the @INC variable properly. But I'm a bit rusty on that. You could try installing a Virtual version of Vicibox somewhere for comparison if you have vSphere, Proxmox, VMware or Virtualbox available to play with. Having a comparison box for the long run may come in very handy.

[sajiahma]

Thanks.

Sure will try to install vicibox.