https://shouts.dev/articles/allow-remote-access-to-mariadb-server-on-rhel-centos
lunes, 25 de julio de 2022
Re: Custom caller ID per area code randomness
CAMPAIGN CID AREACODES
If the System Setting for Areacode CIDs is enabled and the Campaign setting for Use Custom CallerID is set to AREACODE then you have the ability to define Areacode CIDs that will be used when outbound calling to leads in this specific campaign. You can add multiple callerIDs per areacode and you can activate and deactivate them each in real time. If more than one callerID is active for a specific areacode then the system will use the callerid that has been used the least number of times today. If no callerIDs are active for the areacode then the campaign CallerID or list override CallerID will be used. An areacode in this section can be from 2 to 5 digits in length, and if a shorter defined areacode overlaps with a longer areacode then the longer areacode will be used. For example, if the areacodes 31 and 312 are both defined and active for a campaign, then areacode 312 would be used for phone number 3125551212.
Re: Custom caller ID per area code randomness
by mflorell » Mon Nov 20, 2017 7:52 am
The counters reset every day, so it will most likely dial the same one first on the second day since there is no random generator on the query that pulls it.
martes, 19 de julio de 2022
Re: AMD Calls Response Dead Air
Re: AMD Calls Response Dead Air
by mflorell » Tue Oct 29, 2019 11:54 am
Have you tried not using AMD at all? We usually recommend to our clients that they try to not use it because of the delay it adds to routing calls to agents.
sábado, 9 de abril de 2022
Re: option in ingroup to goto voicemail
Re: option in ingroup to goto voicemail
by williamconley » Mon Mar 05, 2018 2:37 pm
Vicibox version is incomplete. 7.0.XX (there's a third digit missing).
This is what call menus are for. Send the caller to a menu before the ingroup. If they then land in an ingroup and you want them to have the option to exit, look at "Wait Time Option Callmenu" and "Hold Time Option Callmenu", either of which can be used to route a caller who presses a button while in an Ingroup. You can also "drop call" to a call menu, offer the caller the option to go somewhere else (such as VM) and then put them back into the ingroup if they do not choose the call menu, but they'll lose their place in line when that happens.
This is what call menus are for. Send the caller to a menu before the ingroup. If they then land in an ingroup and you want them to have the option to exit, look at "Wait Time Option Callmenu" and "Hold Time Option Callmenu", either of which can be used to route a caller who presses a button while in an Ingroup. You can also "drop call" to a call menu, offer the caller the option to go somewhere else (such as VM) and then put them back into the ingroup if they do not choose the call menu, but they'll lose their place in line when that happens.
miércoles, 17 de noviembre de 2021
Zypper Cheat Sheet
https://en.opensuse.org/images/1/17/Zypper-cheat-sheet-1.pdf
lunes, 15 de noviembre de 2021
O leads on the hooper
by mcargile » Wed Jun 02, 2010 9:36 am
There are three main things that can prevent leads from loading into the hopper when the server is setup and running correctly.
1. There are no leads in the local call time you have specified. Remember this is local to the leads location. So if you have it set to 12pm to 5pm and it is 9am where all your leads are it will not load leads. Change the local call time for the campaign.
2. No dialable Dial statuses. If your campaign only has NEW set as a dial status and you have no leads in your list that are NEW it wont be able to load leads. Add other dial statuses to the campaign.
3. All leads with a Dial status allowed by the campaign are marked as CALLED. Vicidial will only call leads that are set to NOT CALLED in the list. Reset the list and the leads will be marked as NOT CALLED. Note, resetting the list will NOT change the dial statuses just the called status for a lead.
If none of these help there is most likely something wrong on your server, or you are using an advanced feature of Vicidial (lead filters, lead recycling, etc) and should read up on it more before continuing.
1. There are no leads in the local call time you have specified. Remember this is local to the leads location. So if you have it set to 12pm to 5pm and it is 9am where all your leads are it will not load leads. Change the local call time for the campaign.
2. No dialable Dial statuses. If your campaign only has NEW set as a dial status and you have no leads in your list that are NEW it wont be able to load leads. Add other dial statuses to the campaign.
3. All leads with a Dial status allowed by the campaign are marked as CALLED. Vicidial will only call leads that are set to NOT CALLED in the list. Reset the list and the leads will be marked as NOT CALLED. Note, resetting the list will NOT change the dial statuses just the called status for a lead.
If none of these help there is most likely something wrong on your server, or you are using an advanced feature of Vicidial (lead filters, lead recycling, etc) and should read up on it more before continuing.
Michael Cargile | Director of Consulting | ViciDialGroup | www.vicidial.com
The official source for VICIDIAL services and support. 1-888-894-VICI (8424)
The official source for VICIDIAL services and support. 1-888-894-VICI (8424)
- mcargile
- Site Admin
- Posts: 571
- Joined: Tue Jan 16, 2007 10:38 am
http://www.vicidial.org/VICIDIALforum/viewtopic.php?t=11596
domingo, 31 de octubre de 2021
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
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
Suscribirse a:
Entradas (Atom)