viernes, 30 de agosto de 2019
lunes, 26 de agosto de 2019
vicidial_live_agents keeps locking
Re: vicidial_live_agents keeps locking
by mflorell » Mon Mar 02, 2015 10:18 am
The database is the bottleneck, other than off-loading reports to a slave database there is no way to cluster the database. But, for 90 agents there is no reason you can't run that off of a single database server. We have clients with over 500 agents that run on a single database server with no problems. If you have the proper hardware and the proper configuration it can handle a very large number of agents.
I wouldn't recommend a RAID 0 for DB usage, at the least you should use RAID 10, so any single drive failure won't cause data loss. Also, we only recommend LSI Logic MegaRAID cards(Dell Perc cards are NOT the same).
I wouldn't recommend a RAID 0 for DB usage, at the least you should use RAID 10, so any single drive failure won't cause data loss. Also, we only recommend LSI Logic MegaRAID cards(Dell Perc cards are NOT the same).
jueves, 22 de agosto de 2019
VICIDIAL cluster note
installation command vicibox-install
1) Install DB and Web server
Audio server is the same DB and WEB ( need to be changed on the system setting)
Recording server is the telephony server
We need to add the telephony server to the Web server
* * * * * /usr/share/astguiclient/AST_VDhopper.pl
@reboot /sbin/service asterisk start
1) Install DB and Web server
Audio server is the same DB and WEB ( need to be changed on the system setting)
Recording server is the telephony server
We need to add the telephony server to the Web server
voicemails server has to be dialer
* * * * * /usr/share/astguiclient/AST_VDhopper.pl
@reboot /sbin/service asterisk start
domingo, 18 de agosto de 2019
Setting to increase calls on VICIdial
System Setting :
Auto Dial Limit
Max FILL Calls per Second:
CP setting
Auto Dial Level:
Minimum Hopper Level:
Automatic Hopper Level:
Server Setting
Max Trunks:
Max Calls per Second:
Auto Dial Limit
Max FILL Calls per Second:
CP setting
Auto Dial Level:
Minimum Hopper Level:
Automatic Hopper Level:
Server Setting
Max Trunks:
Max Calls per Second:
sábado, 17 de agosto de 2019
recording custom audio vicidial
To record an audio prompt from a phone that is registered on the system, dial 8168 and follow the
instructions for recording a message (the pin number it asks for is 4321). Once the message is recorded,
write down the prompt ID that it will read back to you (the prompt IDs start at 85100001). After two
minutes this recording should be available in the Audio Store.
VICI cluster
1) Instalacion de Web Server IP
2) Slave DB no,
3) Master
--- ViciBox v.8.1 Install Summary ---
Expert : Yes
Legacy : No
Database : Yes
Web : Yes
Redirect : Yes
PMA : Yes
Telephony: No
Archive : No
Firewall : Disabled
--- Configuration Information ---
- Database -
SVN Rev : 3130
IP Addr : 64.154.38.232
Name : asterisk
User : cron
Password : 1234
Cust User: custom
Cust Pass: custom1234
Port : 3306
2) Slave DB no,
3) Master
--- ViciBox v.8.1 Install Summary ---
Expert : Yes
Legacy : No
Database : Yes
Web : Yes
Redirect : Yes
PMA : Yes
Telephony: No
Archive : No
Firewall : Disabled
--- Configuration Information ---
- Database -
SVN Rev : 3130
IP Addr : 64.154.38.232
Name : asterisk
User : cron
Password : 1234
Cust User: custom
Cust Pass: custom1234
Port : 3306
jueves, 15 de agosto de 2019
Re: Restore database backup
Re: Restore database backup
by mflorell » Thu Dec 18, 2014 7:03 am
Here is how we recommend doing a restore onto a fresh vicibox install:
Backup Process:
- /usr/share/astguiclient/ADMIN_backup.pl --help (to see options)
- /usr/share/astguiclient/ADMIN_backup.pl --without-web –debugX
Restore Process:
- ls -lat /var/log/astguiclient/archive/
- cd /var/log/astguiclient/archive/
- tar xvfz 192.168.1.5_ALL_0.tar.gz
- cd var/log/astguiclient/archive/
- mv 192.168.1.5* /
- cd /
- ls -lat
- tar xvf 192.168.1.5_VOICEMAIL_0.tar
- tar xvf 192.168.1.5_CONF_0.tar
- tar xvf 192.168.1.5_BIN_0.tar
- tar xvf 192.168.1.5_LINUX_0.tar
- tar xvf 192.168.1.5_SOUNDS_0.tar
- (check for other tar files if you used other backup options)
- gunzip 192.168.1.5asterisk0.gz
- mysql asterisk
- \. 192.168.1.5asterisk0
- quit
Backup Process:
- /usr/share/astguiclient/ADMIN_backup.pl --help (to see options)
- /usr/share/astguiclient/ADMIN_backup.pl --without-web –debugX
Restore Process:
- ls -lat /var/log/astguiclient/archive/
- cd /var/log/astguiclient/archive/
- tar xvfz 192.168.1.5_ALL_0.tar.gz
- cd var/log/astguiclient/archive/
- mv 192.168.1.5* /
- cd /
- ls -lat
- tar xvf 192.168.1.5_VOICEMAIL_0.tar
- tar xvf 192.168.1.5_CONF_0.tar
- tar xvf 192.168.1.5_BIN_0.tar
- tar xvf 192.168.1.5_LINUX_0.tar
- tar xvf 192.168.1.5_SOUNDS_0.tar
- (check for other tar files if you used other backup options)
- gunzip 192.168.1.5asterisk0.gz
- mysql asterisk
- \. 192.168.1.5asterisk0
- quit
Add FPG number on agent screen
Re: Add FPG number on agent screen
by mflorell » Sat Sep 22, 2018 4:26 pm
We added the dispo_add_FPG.php script for a client to do something similar. They had this trigger based on the Agent Selected Disposition of the call, so it was very easy on the agent side of things.
# dispo_add_FPG.php
#
# This script is designed to be used in the "Dispo URL" field of a campaign
# or in-group. It adds the phone_number of the call to a designated inbound
# Filter Phone Group
#
# This script is part of the API group and any modifications of data are
# logged to the vicidial_api_log table.
#
# Example of what to put in the Dispo URL field:
# VARhttp://192.168.1.1/agc/dispo_add_FPG ... _to_file=1
#
# Definable Fields: (other fields should be left as they are)
# - log_to_file - (0,1) if set to 1, will create a log file in the agc directory
# - sale_status - (SALE---XSALE) a triple-dash "---" delimited list of the statuses that are to be moved
# - FPG_id - (999,etc...) the Filter Phone Group ID that you want the phone number to be inserted into
# dispo_add_FPG.php
#
# This script is designed to be used in the "Dispo URL" field of a campaign
# or in-group. It adds the phone_number of the call to a designated inbound
# Filter Phone Group
#
# This script is part of the API group and any modifications of data are
# logged to the vicidial_api_log table.
#
# Example of what to put in the Dispo URL field:
# VARhttp://192.168.1.1/agc/dispo_add_FPG ... _to_file=1
#
# Definable Fields: (other fields should be left as they are)
# - log_to_file - (0,1) if set to 1, will create a log file in the agc directory
# - sale_status - (SALE---XSALE) a triple-dash "---" delimited list of the statuses that are to be moved
# - FPG_id - (999,etc...) the Filter Phone Group ID that you want the phone number to be inserted into
- mflorell
- Site Admin
- Posts: 17257
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
miércoles, 14 de agosto de 2019
Re: How to Show CallerId used when exporting report
Re: How to Show CallerId used when exporting report
by mflorell » Wed Aug 14, 2019 7:56 pm
In Reports -> Admin Utilities, there is a Dial Log Report that will have the CID used for every call. You can also use the Export Calls Carrier Report to export this information as well.
- mflorell
- Site Admin
- Posts: 17257
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
Re: Cancel Callback Hold
Re: Cancel Callback Hold
by mflorell » Sat Aug 02, 2014 7:43 am
If you set up the "AST_DB_dead_cb_purge.pl" script in your crontab then it can periodically clear out callback entries for leads that have had their status changed. Make sure to read the comments so you set the proper options:
dial1:~ # /usr/share/astguiclient/AST_DB_dead_cb_purge.pl --help
allowed run time options:
[--purge-non-cb] = delete callback records of leads with no CBHOLD/CALLBK status
[--remove-dup-cb] = remove older duplicate callbacks for same user and lead_id
[--test] = test
[--quiet] = quiet
[--debug] = verbose debug messages
[--debugX] = extra verbose debug messages
dial1:~ # /usr/share/astguiclient/AST_DB_dead_cb_purge.pl --help
allowed run time options:
[--purge-non-cb] = delete callback records of leads with no CBHOLD/CALLBK status
[--remove-dup-cb] = remove older duplicate callbacks for same user and lead_id
[--test] = test
[--quiet] = quiet
[--debug] = verbose debug messages
[--debugX] = extra verbose debug messages
jueves, 1 de agosto de 2019
vicidial delete recordings
/usr/bin/find /var/spool/asterisk/monitorDONE -maxdepth 2 -type f -mtime +2 -print | xargs rm -f
http://www.vicidial.org/VICIDIALforum/viewtopic.php?f=4&t=15446&sid=554b40be576253721b989602408ca1b0