-
Notifications
You must be signed in to change notification settings - Fork 4
Home
We'll describe the setup using RVM. TinyDialer is developed under 1.9.2, so that's your safest bet on running it.
rvm install 1.9.2
rvm use 1.9.2
Make sure you have PostgreSQL installed for the next steps. Clone TinyDialer, go into the directory root and install the gem dependencies with the right versions:
git clone git://github.com/rubyists/tiny_dialer.git
cd tiny_dialer
gem install ramaze
ruby app.rb
This will also start a Webrick instance for the administration interface on port.
Somewhere in here you'll want to setup your database
export APP_DB="tiny_dialer"
echo "localhost:5432:tiny_dialer:username:password" > ~/.pgpass
chmod 0600 ~/.pgpass
rake migrate
psql -f migrations/data/zips.data.sql tiny_dialer
psql -f migrations/data/states.data.sql tiny_dialer
Your PGSQL DB should be ready to go now. And you can go to http://192.168.1.1:7070/ for the dialer admin interface.
Edit your freeswitch default dialplan context to handle the calls now.
<extension name="dialer_ivr">
<condition field="destination_number" expression="^direct_transfer$">
<action application="sleep" data="500" />
<action application="lua" data="my_call_handler.lua" />
</condition>
</extension>
my_call_handler.lua is just an example that I use for a LUA IVR this part is specific to your installation. However The "direct_transfer" extension is where the dialer will send the call for the local leg (ie: you Agent, IVR or whatever you plan to do)
The Format for the leads file can found in csv/test.csv, once you upload a file via the Admin portal, its pretty much ready to go
start up the dialer process with
bin/dialer
There are several Environment Variables you might want to set to adjust a few things check out options.rb for more info on these
Note: The Rubyists Dev Team intends this software to run under runit for supervision.