Asterisk versions do not need to match on the same VICIdial cluster. We have many clients running clusters with mismatched Asterisk versions, from 1.8 to 11 to 13, they all play well together.
domingo, 28 de julio de 2019
sábado, 25 de mayo de 2019
Re: How calls are being pushed through to an agent
by mflorell » Tue May 07, 2019 11:21 pm
The "agi-VDAD_ALL_outbound.agi" script routes outbound auto-dial calls, and the "agi-VDAD_ALL_inbound.agi" script routes inbound calls. Each of these use quite a few database tables to figure out how to route calls and log everything they need to log.
A common reason for delays in routing of calls is database load issues which could be caused by either too many log records or some other kind of slow query issues which can be identified if you have slow query logging enabled on your database.
A common reason for delays in routing of calls is database load issues which could be caused by either too many log records or some other kind of slow query issues which can be identified if you have slow query logging enabled on your database.
martes, 7 de mayo de 2019
DID description in Agent Screen
Re: View DID description in Agent Screen
You should be able to display the did_description as a Script variable in the SCRIPT tab.
--A--did_description--B--
--A--did_custom_one--B--
sábado, 4 de mayo de 2019
goatodial set userver level 9
update vicidial_users set user_level=9 where user='admin'\G;
lunes, 29 de abril de 2019
Re: How to play prerecorded message for all dropped calls
Set the campaign's "Drop Action" to AUDIO and set the "Safe Harbor Audio" to the audio file you want to be played
jueves, 18 de abril de 2019
Re: Automatic callbacks re-queue in cbhold after missed call
Re: Automatic callbacks re-queue in cbhold after missed call
Have you looked at this recently added campaign setting:
Scheduled Callbacks Auto Reschedule -
This feature only affects ANYONE scheduled callbacks. If DAY_1 is used, it will automatically reschedule lead lead to be called back on the next calling day at the same time they were called if the resulting disposition of the call was not a Human Answer -Y- status. The next calling day is determined by the Call Time that is set for the campaign. In the case of DAY_1, if tomorrow is not an allowed calling day, the system will look at the next day and then the next day until it finds the next allowable calling day to set the ANYONE scheduled callback for. There are up to 6 DAY options, then there are up to 3 WEEK options, then there are up to 6 MONTH options. Default is DISABLED.
Scheduled Callbacks Auto Reschedule -
This feature only affects ANYONE scheduled callbacks. If DAY_1 is used, it will automatically reschedule lead lead to be called back on the next calling day at the same time they were called if the resulting disposition of the call was not a Human Answer -Y- status. The next calling day is determined by the Call Time that is set for the campaign. In the case of DAY_1, if tomorrow is not an allowed calling day, the system will look at the next day and then the next day until it finds the next allowable calling day to set the ANYONE scheduled callback for. There are up to 6 DAY options, then there are up to 3 WEEK options, then there are up to 6 MONTH options. Default is DISABLED.
lunes, 18 de marzo de 2019
Re: Auto Alt Dialing uses what timezone / GMT offset?
Re: Auto Alt Dialing uses what timezone / GMT offset?
There are several ways to set the timezone on a lead:
- by country-code / areacode
- by postal code
- by the 'owner' field timezone
- by country-code / areacode
- by postal code
- by the 'owner' field timezone
- mflorell
- Site Admin
- Posts: 17148
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
Suscribirse a:
Entradas (Atom)