PostalCode or State based dialing

 

Re: PostalCode or State based dialing

by mflorell » Sat Oct 30, 2021 5:56 pm

Yes, you can for postal code, but not for state, because several states are split by timezones so it wouldn't work very well.

You can switch your whole system to use postal code time-zone encoding, or just do it per list. Either way, you will need to modify the crontab entry for the GMT-offset script to do so:

For whole system by postal-code:
ADMIN_adjust_GMTnow_on_leads.pl --debug --postal-code-gmt

For per-list choice encoding:
ADMIN_adjust_GMTnow_on_leads.pl --debug --list-settings

VICIdial recording folders

 Stages:

1: /var/spool/asterisk/monitor - During the call (representing "don't mess with this", usually a virtual drive for speed)
2: /var/spool/asterisk/monitorDONE - After the call (representing "ok, process this")
3: /var/spool/asterisk/monitorDONE/ORIG - After compression, this file contains the "now redundant" uncompressed file. Can be deleted immediately. but keep the folder, just delete the files inside.
4: /var/spool/asterisk/monitorDONE/MP3 - After compression, the MP3 is dropped here indicating "ready for permanent storage" (this is a TEMPORARY folder, files here will not stay long)
5: /var/spool/asterisk/monitorDONE/FTP - After the FTP process pushes the file to an FTP service, the MP3 file is moved from MP3 to FTP to indicate archiving has completed. If everything worked as planned, this file is now redundant.
6: /var/spool/asterisk/monitorDONE/FTP2 - If, however, you have a "redundant backup" configured and are pushing files to a 2nd FTP server, the ".mp3" that was in the FTP folder will get pushed to the 2nd FTP service, and then the file will be moved from FTP to FTP2 indicating that process has completed as well.

The recording scripts in the crontab manage the movement via FTP and FTP2. Each script has its own options (avilable by running the script with "--help" after it) and notes in the trunk /DOCS/ folder and manual.

https://vicidialforum.com/threads/recordings-directory.20646/

VICIdial filter

Re: How to filter out specific local call time hours?

by mflorell » Mon Oct 25, 2021 4:20 pm

We don't really have a single reference for filter examples, but there are probably dozens spread out through the Forums. Here are a few:

Below are several examples of Filters that can be used to further limit VICIdial outbound calling

72 hour block on auto-Answering-Machine detected calls -
This specific example was used to comply with the UK's OFCOM auto-dialing regulations to not call back auto-detected answering machines within 3 days of the last attempt:
( ( (status='AA') and (last_local_call_time < CONCAT(DATE_ADD(CURDATE(), INTERVAL -3 DAY),' ',CURTIME()) ) ) or (status != 'AA') )

Two examples for blocking areacodes -
These examples are for two areacodes in Puerto Rico:
(left(phone_number,3) NOT IN('787','939'))
(phone_number NOT LIKE '787%' AND phone_number NOT LIKE '939%')

Exclude a list of cities:
(city NOT IN('london','paris','tampa'))

Include only specific states:
state IN('FL','NY','CA')

Do not call NI(Not Interested) leads for 7 days
( ( (status='NI') and (last_local_call_time < CONCAT(DATE_ADD(CURDATE(), INTERVAL -7 DAY),' ',CURTIME()) ) ) or (status != 'NI') )

No more than one call per lead per 24 hours:
(last_local_call_time < CONCAT(DATE_ADD(CURDATE(), INTERVAL -1 DAY),' ',CURTIME()) )

Multiple filters in one -
This filter was designed to limit the call attempts, states and time zones of leads:
called_count IN('7','8','9') and state NOT IN('CA','OR','WA') and gmt_offset_now IN('-4','-5')

This Filter would exclude the 12-oclock hour for EST(Eastern Standard Time) leads on an EST-configured system, during standard time only(not during daylight savings time):

( (hour(now()) <= 11) and (hour(now()) >=13) and (gmt_offset_now='-4.0') )

mflorell

Site Admin

 

Posts: 17877

Joined: Wed Jun 07, 2006 3:45 pm

Location: Florida

Regarding Server Requirement

 

Re: Regarding Server Requirement

by mflorell » Mon Oct 25, 2021 9:51 am

You will definitely need a cluster.

I would recommend:
1 dedicated database server
1 dedicated web server
5-10 dialers

The database server should be a dual-quad-core CPU with 16+GB RAM and a fast drive system(preferably SSD drives in a RAID 10 on a MegaRAID card)
The webserver and dialers can be single-quad-code CPUs with 8GB RAM and standard drives

Modify vicidial realtime report

 

If you are going to just hard-code the new column, you should only need to modify the AST_timeonVDADall.php script. If you want to make it an option you will also need to modify the realtime_report.php script.

http://www.vicidial.org/VICIDIALforum/viewtopic.php?f=2&t=41049&sid=520fd832a108a0a94a32622d2030c61b

Re: Regarding SVN upgrade impact

 

Re: Regarding SVN upgrade impact

by mflorell » Thu Oct 07, 2021 6:19 am

As long as you follow the instructions in the UPGRADE document, and upgrade and install the same updated VICIdial code on every server in your cluster you should be fine.

We recommend upgrading the DB schema first, then the webserver then the dialers. Making sure to reboot the dialers after they have been upgraded.

change time zone

 

1) change system time on yast

2) change time zone on php

/etc/php7/cli/php.ini

/etc/php7/apache2/php.ini

[Date]

; Defines the default timezone used by the date functions

; http://php.net/date.timezone

date.timezone = America/Los_Angeles

3) reboot