Moderators: enjay, williamconley, Staydog, mflorell, MJCoate, mcargile, Kumba
mysql asterisk -e "show table status where comment like '%crashed%'" --user=cron -p1234
asterisk -R
scenarist wrote:If db crashed what I should to do. Can I repair mysql or optimize via phpmyadmin?
df -h
mysqlcheck --auto-repair asterisk TABLENAME -u cron -p1234
[root@go ~]# mysql asterisk -e "show table status where comment like '%crashed%'" --user=cron -p1234
[root@go ~]#
[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
mysqlcheck -c asterisk -u root -p
[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 ~]#
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.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.
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.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.
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
Eglant wrote:campagn not work opensuse 12.1 can't show comment
Return to ViciBox Server Install and Demo
Users browsing this forum: No registered users and 7 guests