vicidial.org

Hello;

vicibox 4.0.3, vicidial 2.8-404a, Build 130605-0841, asterisk 1.4.39.1-vici, Single Machine, Vtiger 5.4

Is there any limitation that cause the campaign to stop dialing?

About the calling time, it was within the calling time. The agent (remote agent is logged in) and actually the campaign worked .. but then it stopped.

Ratio is 3

At the hopper, I see there is one lead (actually I loaded the list with 1 lead) and in the list, I see there is one lead not called. Why the campaign is not calling?

At asterisk console, I do not see any thing is coming.

Again, the campaign was working fine .. suddenly it is not doing calls !!

Regards
Bilal

At the bottom of the campaign how many leads are listed in:

This campaign has ??? leads to be dialed in those lists

It was having 100 leads to be dialed which is the number of the leads in the list. I feel, it was related to the call time .. or for multiple things (for example, Reset Lead-Called-Status for this list: Y) .. I am trying to recognize it and check what exactly the problem.

Regards
Bilal

Did you fix your problem,I have the same problem like you and dont know what is happen?
Campaign just stop working, I use ratio 2,leads ok,voip provider alo ok,cli dont show any strange messages,
I try with another campaign but everything is the same.
I use the same campaign 30 days but suddenly dialer not to placing calls and show that all agents ready?
Campaign works fine about 15 minutes and then suddenly stop to placing calls?

there are many reasons for this from "you forgot to pay your carrier" to "broken DB".

check your db:

Code: Select all

mysql asterisk -e "show table status where comment like '%crashed%'" --user=cron -p1234

And check your asterisk CLI to see if the calls are being rejected:

Code: Select all

asterisk -R

Asterisk cli just stop with debug and nothing happens.
When I restarted server campaign works fine about 15 minutes and after that just stop to placing calls?
I setup manual method and my agents works fine till I found problem about ratio and adapt method.
Tommorow I will check mysql...hm. ..totaly strange problem.


If I would install new fresh goautodial is there any possibility to load leads with callback statuses from old system?

If db crashed what I should to do. Can I repair mysql or optimize via phpmyadmin?

scenarist wrote:If db crashed what I should to do. Can I repair mysql or optimize via phpmyadmin?

first find out why the db crashed if possible and make sure it won't happen again.

is the hd full?

Code: Select all

df -h

Power outage? If so ... purchase and install a UPS!

If the prior mysqlcheck command results in a table named as crashed ... repair the table like this:

Code: Select all

mysqlcheck --auto-repair asterisk TABLENAME -u cron -p1234

Hello @williamconley
When I tried to run

Code: Select all

[root@go ~]# mysql asterisk -e "show table status where comment like '%crashed%'" --user=cron -p1234

[root@go ~]#



Disk is ok

Code: Select all

[root@go ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2             131G  4.7G  119G   4% /
/dev/sda1              99M   12M   83M  13% /boot
tmpfs                 4.0G     0  4.0G   0% /dev/shm


I run

Code: Select all

mysqlcheck -c asterisk -u root -p

and I got the following

Code: Select all

[root@go ~]# mysqlcheck -c asterisk -u root -p
Enter password:
asterisk.call_log                                  OK
asterisk.call_log_archive                          OK
asterisk.callcard_accounts                         OK
asterisk.callcard_accounts_details                 OK
asterisk.callcard_log                              OK
asterisk.conferences                               OK
asterisk.custom_221                                OK
asterisk.custom_302                                OK
asterisk.custom_401                                OK
asterisk.custom_601                                OK
asterisk.custom_602                                OK
asterisk.custom_603                                OK
asterisk.custom_813                                OK
asterisk.custom_814                                OK
asterisk.custom_815                                OK
asterisk.custom_816                                OK
asterisk.custom_817                                OK
asterisk.custom_818                                OK
asterisk.custom_819                                OK
asterisk.custom_820                                OK
asterisk.custom_821                                OK
asterisk.custom_822                                OK
asterisk.custom_823                                OK
asterisk.custom_825                                OK
asterisk.custom_826                                OK
asterisk.groups_alias                              OK
asterisk.inbound_numbers                           OK
asterisk.live_channels
note     : The storage engine for the table doesn't support check
asterisk.live_inbound                              OK
asterisk.live_inbound_log                          OK
asterisk.live_sip_channels
note     : The storage engine for the table doesn't support check
asterisk.park_log                                  OK
asterisk.parked_channels
note     : The storage engine for the table doesn't support check
asterisk.phone_favorites                           OK
asterisk.phones                                    OK
asterisk.phones_alias                              OK
asterisk.recording_log                             OK
asterisk.server_performance                        OK
asterisk.server_updater
note     : The storage engine for the table doesn't support check
asterisk.servers                                   OK
asterisk.system_settings                           OK
asterisk.twoday_call_log                           OK
asterisk.twoday_recording_log                      OK
asterisk.twoday_vicidial_agent_log                 OK
asterisk.twoday_vicidial_closer_log                OK
asterisk.twoday_vicidial_log                       OK
asterisk.twoday_vicidial_xfer_log                  OK
asterisk.user_call_log                             OK
asterisk.vicidial_admin_log                        OK
asterisk.vicidial_agent_log                        OK
asterisk.vicidial_agent_log_archive                OK
asterisk.vicidial_agent_sph                        OK
asterisk.vicidial_api_log                          OK
asterisk.vicidial_auto_calls
note     : The storage engine for the table doesn't support check
asterisk.vicidial_call_menu                        OK
asterisk.vicidial_call_menu_options                OK
asterisk.vicidial_call_notes                       OK
asterisk.vicidial_call_notes_archive               OK
asterisk.vicidial_call_times                       OK
asterisk.vicidial_callbacks                        OK
asterisk.vicidial_campaign_agents                  OK
asterisk.vicidial_campaign_dnc                     OK
asterisk.vicidial_campaign_hotkeys                 OK
asterisk.vicidial_campaign_server_stats
note     : The storage engine for the table doesn't support check
asterisk.vicidial_campaign_stats                   OK
asterisk.vicidial_campaign_statuses                OK
asterisk.vicidial_campaigns                        OK
asterisk.vicidial_campaigns_list_mix               OK
asterisk.vicidial_carrier_log                      OK
asterisk.vicidial_carrier_log_archive              OK
asterisk.vicidial_closer_log                       OK
asterisk.vicidial_closer_log_archive               OK
asterisk.vicidial_conf_templates                   OK
asterisk.vicidial_conferences                      OK
asterisk.vicidial_cpd_log                          OK
asterisk.vicidial_custom_cid                       OK
asterisk.vicidial_did_log                          OK
asterisk.vicidial_dnc                              OK
asterisk.vicidial_drop_rate_groups                 OK
asterisk.vicidial_extension_groups                 OK
asterisk.vicidial_filter_phone_groups              OK
asterisk.vicidial_filter_phone_numbers             OK
asterisk.vicidial_grab_call_log                    OK
asterisk.vicidial_hopper
note     : The storage engine for the table doesn't support check
asterisk.vicidial_inbound_dids                     OK
asterisk.vicidial_inbound_group_agents             OK
asterisk.vicidial_inbound_groups                   OK
asterisk.vicidial_ivr                              OK
asterisk.vicidial_lead_filters                     OK
asterisk.vicidial_lead_recycle                     OK
asterisk.vicidial_lead_search_log                  OK
asterisk.vicidial_lead_search_log_archive          OK
asterisk.vicidial_list                             OK
asterisk.vicidial_list_alt_phones                  OK
asterisk.vicidial_list_pins                        OK
asterisk.vicidial_list_update_log                  OK
asterisk.vicidial_lists                            OK
asterisk.vicidial_lists_fields                     OK
asterisk.vicidial_live_agents                      OK
asterisk.vicidial_live_inbound_agents              OK
asterisk.vicidial_log                              OK
asterisk.vicidial_log_archive                      OK
asterisk.vicidial_log_extended                     OK
asterisk.vicidial_manager                          OK
asterisk.vicidial_manual_dial_queue                OK
asterisk.vicidial_music_on_hold                    OK
asterisk.vicidial_music_on_hold_files              OK
asterisk.vicidial_nanpa_prefix_codes               OK
asterisk.vicidial_override_ids                     OK
asterisk.vicidial_pause_codes                      OK
asterisk.vicidial_phone_codes                      OK
asterisk.vicidial_postal_codes                     OK
asterisk.vicidial_process_trigger_log              OK
asterisk.vicidial_process_triggers                 OK
asterisk.vicidial_qc_codes                         OK
asterisk.vicidial_remote_agent_log                 OK
asterisk.vicidial_remote_agents                    OK
asterisk.vicidial_scripts                          OK
asterisk.vicidial_server_carriers                  OK
asterisk.vicidial_server_trunks                    OK
asterisk.vicidial_shifts                           OK
asterisk.vicidial_state_call_times                 OK
asterisk.vicidial_stations                         OK
asterisk.vicidial_status_categories                OK
asterisk.vicidial_statuses                         OK
asterisk.vicidial_territories                      OK
asterisk.vicidial_timeclock_audit_log              OK
asterisk.vicidial_timeclock_log                    OK
asterisk.vicidial_timeclock_status                 OK
asterisk.vicidial_tts_prompts                      OK
asterisk.vicidial_user_closer_log                  OK
asterisk.vicidial_user_groups                      OK
asterisk.vicidial_user_log                         OK
asterisk.vicidial_user_territories                 OK
asterisk.vicidial_user_territory_log               OK
asterisk.vicidial_users                            OK
asterisk.vicidial_voicemail                        OK
asterisk.vicidial_xfer_log                         OK
asterisk.vicidial_xfer_presets                     OK
asterisk.vicidial_xfer_stats                       OK
asterisk.vtiger_rank_data                          OK
asterisk.vtiger_rank_parameters                    OK
asterisk.vtiger_vicidial_roles                     OK
asterisk.web_client_sessions
note     : The storage engine for the table doesn't support check
[root@go ~]#



Should I run mysqlcheck when agents working on dialer ? Above result I got when no logged agents on goautodial ?
Which table in asterisk database where dialer placing calls ?

Hello;

vicibox 4.0.3, vicidial 2.8-404a, Build 130605-0841, asterisk 1.4.39.1-vici, Single Machine, Vtiger 5.4

Again, Suddenly the campaign is not working.

Currently, the not called and the diable is 500 and LEADS IN HOPPER is 12 (I have two remote agents logged in where number of lines for each one is 2).

CCMachine:/ # df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 910G 8.7G 900G 1% /
devtmpfs 5.9G 36K 5.9G 1% /dev
tmpfs 5.9G 0 5.9G 0% /dev/shm
tmpfs 5.9G 416K 5.9G 1% /run
/dev/sda3 910G 8.7G 900G 1% /
tmpfs 5.9G 0 5.9G 0% /sys/fs/cgroup
tmpfs 5.9G 416K 5.9G 1% /var/run
tmpfs 5.9G 416K 5.9G 1% /var/lock
tmpfs 5.9G 0 5.9G 0% /media
tmpfs 6.0G 0 6.0G 0% /var/spool/asterisk/monitor

At the CLI, no dialing is happening (nothing).

The call time is 24 hours.

What could be the reason?

Regards
Bilal

check the vicidial auto-calls table. see if there are calls stuck in there for illegal phone numbers.

what can happen is that a number that does not match any dialplan comes up and vicidial sends it to be dialed.

but if NO dialplan matches the number, no "dialplan" ever executes from it. thus no scripts ever remove the call from the autocalls table. vicidial believes it is being dialed, but it is not and never will be.

so ... does vicidial believe calls are being dialed, when none are?

check the campaign (does it say any calls are being dialed?) and check in asterisk: sip show channels

compare them. if vicidial is wrong ... there's got to be a reason. on a heavy use system, it will be off by a few as they change before you can run the second "check'. but with a small system dialing a few calls ... it should be "spot on".

@williamconley
Dialplan is not a problem in my and @bghayad case. Asterisk cli show nothing. Dialer just stop to placing calls and cli being stoped. Where is located autocalls table ?

Vicidial_autocall table: I found one record in it and I deleted. Now when I do query, 0 record return so it is empty.
But still it is not working, although there is calls diable and calls in hopper, remote agents are assigned to the campaign and active and I can see this at the real time.

I removed the campaign and create new one and import one number (which is my mobile), I can see it at the hopper but it is not dialing and nothing at the Asterisk CLI.

Is there a command to restart the dialer or I have to restart my machine completely?
What other possibilities for this fail?
Regards
Bilal

By the way, I restarted the machine and did not resolve.
Diable existed, hopper contains calls and nothing come at the asterisk CLI.

100 % problem on your network device,switch,router or on side your internet provider.
Try to use dialer from another network i.e from another internet provider.

Why?
I don't see anything at the Asterisk CLI, so why u r assuming this?
Why I have to change my service provider or network?
Asterisk and vicidial as call center is working except this campaign is not working.

scenarist wrote:100 % problem on your network device,switch,router or on side your internet provider.
Try to use dialer from another network i.e from another internet provider.

Um ... no. Networking problems will not stop vicidial from dialing when it should dial. I'm not sure where you got that. Cool that you're trying to help, but you're off base.

Back to the party ...

So you say you have agents in "READY" on the campaign. And on the same campaign you have both Dialable leads and Leads in the hopper. And your server has the proper screens running (screen -list). It will be time to check the /var/log/astguiclient logs (activate them if necessary under Admin->Servers->{choose your server}, set to FILE or BOTH) and find the log that pertains to "how many calls should I dial right now on this campaign". Somehow a calculation is incorrect or you have turned something off inadvertently or merely misunderstood something.

Internet service provider on your side block some ports and vicidial dont see any softphone or have freeze situation and because that dialer have no live agents and softphones and he did not to placing calls.
Try to manual dial method and everything will work fine,try and inform.
If you have some friend who have internet from another internet service provider try to call from him and you will see what will happens.

won't stop vicidial from showing the call in the CLI. if vicidial never generates the call ... there's nothing to block!

if vicidial's realtime screen shows a READY agent, the logic is in place to generate a call for the campaign. that's the "live agents".

Hm...yes I know and I completly understand you and concept of vicidial but I have the same situatio and when I try call from the same campaign from my home everything works fine.
I also installed new fresh server in company but I got the same situation, reports show ready status of agents but dont want to placing calls.
But from my home everything worka fine,how can you explain that situation?

williamconley wrote:So you say you have agents in "READY" on the campaign. And on the same campaign you have both Dialable leads and Leads in the hopper. And your server has the proper screens running (screen -list). It will be time to check the /var/log/astguiclient logs (activate them if necessary under Admin->Servers->{choose your server}, set to FILE or BOTH) and find the log that pertains to "how many calls should I dial right now on this campaign". Somehow a calculation is incorrect or you have turned something off inadvertently or merely misunderstood something.

there is a decision-making process being run. decipher that to find the flaw in the process ... and fix the flaw. we like to call it troubleshooting.

It seems that the problem was because we imported the file with wrong list number (it is written list 111 and I was selecting list 120 which is the required list).

After I deleted the list and recreated new one and importing new leads with correct list, it is fixed.

Still I need to do some tests.

Regards
Bilal

not sure that was related. after all, you had leads in the list and the hopper. (you said)

so having other leads in a nonexistent list should not make any difference.

if you can duplicate that and make it stop dialing again, i'd be interested to hear about it.

good post back!

I`m facing the same issue..
what exactly happening at my end is,i`m running 2 campaings with ratio dialing method.they were both getting off calls at the same time even there were leads in list and hopper of both campaings. i reinstalled my server, changed my machine. swithed from vicidial v2 to v3. but nothing changed.. then i realised that from 2 of my campaigns, one campaign was working completely fine, and as soon as other campaign gys loged in.. within next 10 min. server stops auto dialing.. manual dialing works fine. then i mad a single campaign and ask agent of both campaigns to log in from that single campaign.. but nothing changed.. then i seperated both camaigns server.
Now,same citi same leads files and same configuaration is been made on both server.. but there were no issues in one campaign and other campaign were showing same issues.. dialing stopped after a while by server. just before the dialing stoped by server. CLI show a warning regaring app_meetme that some conference extension not found or like this.. but that thing was only happing with the B campaign. A campaign was working fine with same config,version and same network and same voip provider.
2day when i figure out that there is some internal issues after making a thousand cross check on the network, on ov ma coleague who was on vication ask me 2 come outside. what he told me was shocking but expected.. he told me that there is an agent in ur B campaign who has been fired in last call center and reason was the same.. there dialing server was collapsed.. and after every possible effort sumhow they manage to trace that it was this agent who was doing sum tricks from his end during dialing which cause server auto dialing stop. and after figuring out. they have to fire not only him but the whole campaign as he spread thing trick of him to all..

now what i did, i rebooted my server after the dialing got stopped again. and i asked that agent ov mine to leave the floor till i ask him to take calls..
Seriously gys, my server dialing didnt crashed till shift stopped..

As for now, i`ve no idea what exactly he is doing at user end to make dialing stop but do you gys have any idea how anybody can do this thing from USER ENDs.
2ndly ,is there anyway to c it from server end what exactly he is doing on server to make it stop dialing? as v cant monitor live cli 24 hrs...
thank u so much for your help in advance but kindly do consider my request and help me please to get myself out ov this situation and to get enough evidence for that AGENT..

thank u so much again.

Asterisk 1.4.39.1-vici.go RPM by Copyright (C) 1999 - 2010 Digium, Inc. and others.
Created by Mark Spencer

Yes I can resolve your problem.

It is mainly related to the remote agents and allowed number of calls per remote agent and the auto dial level and then to the Max Trunks in the Servers settings.

In the end the Max Trunks is the bottle neck that will effect and cause this problem! It should be enough number that is able to cover the overall calculations of all the active campaigns. That is why you will notice that one campaign is working and the other is not working (and vice versa). In this case, or you increase the Auto Dial level or you reduce the number of remote agents (and I think, the number of allowed calls per remote agent is effecting).

When I am talking about the number of remote agents, you need also to take care if you are using normal agents and not remote agents .. the same principle is applied.

Regards
Bilal

thanks for ur response...!!
as for now.. i think u didn`t read my post completely... i caught that agent .. it was him doing that thing..
the only precaution in that bug is as for now is to disable manual dialling feature by every mean.. once this thing done.. they can never create that thing again bro..

I'm intrigued, but are there logs? How is it known for a fact that the user was doing this? Rather, how is it established, with logs?

Hi,

We are also facing the same issue but unable to trace the agent can you please suggest what was he doing ? We will do the configuration accordingly.

Regards,
Thanks...

zohaibhassan4u wrote:I`m facing the same issue..
what exactly happening at my end is,i`m running 2 campaings with ratio dialing method.they were both getting off calls at the same time even there were leads in list and hopper of both campaings. i reinstalled my server, changed my machine. swithed from vicidial v2 to v3. but nothing changed.. then i realised that from 2 of my campaigns, one campaign was working completely fine, and as soon as other campaign gys loged in.. within next 10 min. server stops auto dialing.. manual dialing works fine. then i mad a single campaign and ask agent of both campaigns to log in from that single campaign.. but nothing changed.. then i seperated both camaigns server.
Now,same citi same leads files and same configuaration is been made on both server.. but there were no issues in one campaign and other campaign were showing same issues.. dialing stopped after a while by server. just before the dialing stoped by server. CLI show a warning regaring app_meetme that some conference extension not found or like this.. but that thing was only happing with the B campaign. A campaign was working fine with same config,version and same network and same voip provider.
2day when i figure out that there is some internal issues after making a thousand cross check on the network, on ov ma coleague who was on vication ask me 2 come outside. what he told me was shocking but expected.. he told me that there is an agent in ur B campaign who has been fired in last call center and reason was the same.. there dialing server was collapsed.. and after every possible effort sumhow they manage to trace that it was this agent who was doing sum tricks from his end during dialing which cause server auto dialing stop. and after figuring out. they have to fire not only him but the whole campaign as he spread thing trick of him to all..

now what i did, i rebooted my server after the dialing got stopped again. and i asked that agent ov mine to leave the floor till i ask him to take calls..
Seriously gys, my server dialing didnt crashed till shift stopped..

As for now, i`ve no idea what exactly he is doing at user end to make dialing stop but do you gys have any idea how anybody can do this thing from USER ENDs.
2ndly ,is there anyway to c it from server end what exactly he is doing on server to make it stop dialing? as v cant monitor live cli 24 hrs...
thank u so much for your help in advance but kindly do consider my request and help me please to get myself out ov this situation and to get enough evidence for that AGENT..

thank u so much again.

Asterisk 1.4.39.1-vici.go RPM by Copyright (C) 1999 - 2010 Digium, Inc. and others.
Created by Mark Spencer

campagn not work opensuse 12.1 can't show comment

Eglant wrote:campagn not work opensuse 12.1 can't show comment

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) I don't know what "can't show comment" means, but based on "not wok" my ONLY viable response is "you should probably get that fixed".

I was going nuts with the same issue. I could simply not get any predictive dialing going for a small campaign.

I created a new campaign, new list, checked the DB, checked cli from asterisk, nothing!

I was ignoring time sync error from users because I was busy with this, my firewall was strict and I forgot to open up ntp ports, so yeah.

SO

On all servers
service ntp stop
ntpdate -b time.nist.gov
servicentp start

Done, dialing, good!

I wanted to share for someone else with the same issue

I am having the same issues...Can anyone please help...
Thanks