How leads are being dialed by asterisk?

[jessiekidfernando]

Hello Everyone,

I would like to know how calls are being invoked on asterisk from the DB's data? What specific config file or script that allows the asterisk to dial a specific lead automatically from the database or leads hopper?

Is this related and being executed by AST_VDauto_dial.pl?

Assuming I am using dial method adapt or ratio.

Thanks in advance.

Regards,

Jessie

[williamconley]

Your target should be the hopper script. that makes the decision to load. after that they are dialed in order from the hopper.

[jessiekidfernando]

Okay got it. But what specific script or is there any specific application that commands the asterisk to dial the leads in the hopper?

[ambiorixg12]

Take a look to at AST_VDauto_dial.pl
#
# DESCRIPTION:
# Places auto_dial calls on the VICIDIAL dialer system

Also you can view the list of scripts related to dialing here https://github.com/inktel/Vicidial/tree/master/bin

[mflorell]

That github project goes to 8-year-old code from an abandoned fork of VICIdial managed by someone else.

For the current svn/trunk VICIdial codebase, go here:
http://wiki.vicidial.org/doku.php?id=svn

[williamconley]

Okay got it. But what specific script or is there any specific application that commands the asterisk to dial the leads in the hopper?

a basic description is ...

a perl script runs to determine that there is a need to dial a number. that script grabs the lead from the hopper.

the script then writes the lead into the vicidial_manager table with the necessary commands for the asterisk API to understand, in the proper syntax and order.

There is then another perl script that constantly watch the asterisk_manager table, grabs any calls that should be made, and issue those commands to asterisk. It becomes the "bottleneck" on EACH DIALER that issues and gets responses to commands, this way there is no other script interacting with asterisk that could "accidentally" get a cross-threaded response from asterisk's API. It also (obviously) continuously updates the vicidial_manager table. Thus this one vicidial manager perl script is really what makes the calls and manages the table where they "need" for calls is stored.

There are many peripheral concerns, such as the auto-calls table. The best way to get all references and access points and initiators is to search the code for the auto calls table name and the vicidial manager table name. Writing to either of these two tables is an indication that autodialing controls are in play. If you search in the svn trunk folder (assuming an svn trunk folder is available), your recursive search for those table names will get all instances of access of those tables whether they are in the perl folder or the asterisk agi-bin folder or anywhere else.

[jessiekidfernando]

Hello Everyone,

Thank you so much for your inputs. Appreciate all of it. Will review those inputs.