Does not dial phone after login

[mspangler]

I have an issue which I've seen come up in the forums, but my problem is that it came at me from out of the blue.

I am not in the office today, but I was told that all of a sudden the phones appeared to jam and ever since, vicidial does not attempt to dial the agen phone after logging into vicidial.php. Of course, this is then followed by the error message claiming that there is nobody in session.

I have watched the asterisk CLI output during a login and I do not even see the dial attempt. I have attempted to dial out from those phones, and they dial out just fine manually, so they appear to register fine with asterisk.

Below is the screen -r output

8183.ASTVDauto (Detached)
8196.ASTupdate (Detached)
8195.ASTVDremote (Detached)
2805.ASTsend (Detached)
8174.ASTlisten (Detached)
7541.ASTVDadapt (Detached)

Any thoughts?

[mflorell]

Asterisk version?

astGUIclient version?

Is server logging turned on for this server?

[ykhan]

I am again facing the same issue. Agent does not get a call upon login to vicidial.

Asterisk 1.2.14
Vicidial 2.0.2

No tsure how to check if server logging is enabled.

Rest of the issue is the same as mspangler. I had to manually update the sever entries in the following tables:

vicidial_conferences
server_updater
servers
astguiclient.conf

The conferences are working ok when dialled directly.

Please help. Thanks.

[ykhan]

I have created a user with a level of 5, but error:


Sorry, you are not allowed to login to this campaign:

Thanks for your help.

[mflorell]

Do you see any warnings or notices in your Asteirsk CLI?

Have you checked all of your asterisk log files to see if any of them have reached 2GB?

[ykhan]

I checked the crontab and the scripts were commented out by someone. Now the agent is receiving the login call. But another issue has appeared:

Executing DeadAGI("Local/9447811550074@default-7534,2", "agi://127.0.0.1:4577/call_log") in new stack
Jan 26 15:58:20 WARNING[6068]: res_agi.c:210 launch_netscript: Connect to 'agi://127.0.0.1:4577/call_log' failed: Connection refused

Because of this a call never gets hung up and another is dialled.

[mflorell]

post results of "screen -r"

Make sure your settings in astguiclient.conf are correct to run the FastAGI log process.

[ykhan]

Iam unsure of what the correct settings for this would be. Following is the screen -r output:

here are several suitable screens on:
3897.ASTupdate (Detached)
3899.ASTsend (Detached)
3901.ASTlisten (Detached)
3903.ASTVDauto (Detached)
3905.ASTVDremote (Detached)
3907.ASTVDadapt (Detached)

[mflorell]

Looks like your FASTAGI process is not running.

open up the /etc/astguiclient.conf file and tell me what you have VARactive_keepalives => set to

It should include "6" for the FastAGI process.

If it is and the ADMIN_keepalive_ALL.pl script is running, then make sure you have installed the Net::Server perl module.

[jonsolbg]

Hi, I'm experiencing the same problem, and I checked in the /etc/astguiclient.conf
for VARactive_keepalives and has this:
VARactive_keepalives => 123456

in the /etc/crontab I have this:
### recording mixing for Asterisk run every 5 minutes
1,6,11,16,21,26,31,36,41,46,51,56 * * * 1,2,3,4,5,6 /usr/share/astguiclient/AST_CRON_mix_recordings_BASIC.pl

### keepalive script for astguiclient processes
* * * * * /usr/share/astguiclient/ADMIN_keepalive_ALL.pl

### kill Hangup script for Asterisk updaters
* * * * * /usr/share/astguiclient/AST_manager_kill_hung_congested.pl

### updater for voicemail
* * * * * /usr/share/astguiclient/AST_vm_update.pl

### updater for conference validator
* * * * * /usr/share/astguiclient/AST_conf_update.pl

### flush queue DB table every hour for entries older than 1 hour
11 * * * * /usr/share/astguiclient/AST_flush_DBqueue.pl -q

### fix the vicidial_agent_log once every hour
33 * * * * /usr/share/astguiclient/AST_cleanup_agent_log.pl

### updater for VICIDIAL hopper
* * * * * /usr/share/astguiclient/AST_VDhopper.pl -q

###
* * * * * /usr/share/astguiclient/AST_VDauto_dial.pl

### adjust the GMT offset for the leads in the vicidial_list table
1 1 * * * /usr/share/astguiclient/ADMIN_adjust_GMTnow_on_leads.pl --debug

### reset several temporary-info tables in the database
2 1 * * * /usr/share/astguiclient/AST_reset_mysql_vars.pl

### optimize the database tables within the asterisk database
3 1 * * * /usr/share/astguiclient/AST_DB_optimize.pl

## adjust time on the server with ntp
30 * * * * /usr/local/bin/ntpdate -u localhost 2>/dev/null 1>&2

### VICIDIAL agent time log weekly summary report generation
2 0 * * 0 /usr/share/astguiclient/AST_agent_week.pl

But when I type screen -r in the console appears this:
> There is no screen to be resumed.

This is my first time with astguiclient, althought I've had some experience with asterisk.

[jonsolbg]

: )
Now I want to tell you how was it.
In the installation everything was ok, but I needed to add in every single line of the crontab the user root, so this:
* * * * * /usr/share/astguiclient/ADMIN_keepalive_ALL.pl
changes for this:
* * * * * root /usr/share/astguiclient/ADMIN_keepalive_ALL.pl

Also had to add "export SCREENDIR=/root/tmp" every single time that you use the screen command in /usr/share/astguiclient/ADMIN_keepalive_ALL.pl file
So, this line (351):
/usr/bin/screen -d -m -S ASTsend $PATHhome/AST_manager_send.pl
Change to this:
export SCREENDIR=/root/tmp && /usr/bin/screen -d -m -S ASTsend $PATHhome/AST_manager_send.pl

It was all, at least for now.
I post in several topics, so I will copy and paste this same explanation.
Now if someone could tell me off (with politely) about what was doing wrong, I'll really appreciate it.
Thanks all for your responses.

[mflorell]

What Linux distro are you using?

How were you editing the crontab?

[jonsolbg]

I'm using Mandriva Linux, December Club 2006.
Kernel 2.6.12-12mdk

I made the entries in the crontab like this:
> pico /etc/crontab

I tried with "crontab -e" but after the changes I couldn't save the file (never use that editor before), so the above way seems more practical.

[mflorell]

Thanks for the info, I haven't used Mandrake(Mandriva) for over 3 years now so I had never seen this issue with their crontab entries.

[jonsolbg]

Then it's better to use the one pointed at the scratch installation: Slackware 10.2 ?

Right now I'm just making some tests, this is my first time with vicidial, I hope works fine with my distro.

Thanks for everything.

[mflorell]

I recommend Slackware because it is a very basic and stripped down pure Linux distro that makes it easy to install all of VICIDIAL's required components.

Many other users have Fedora which also works fine for VICIDIAL.