D.I.Y. (Build Your Own Dialer)

You can download the DVD image below and "burn" it onto a DVD. Then install the DVD in a server, boot off it and it will create a ready to go dialer. Once the install is complete you need to complete the configuration. 10 Agent logins, 10 phone extensions and one manual dial campaign are automatically created by the install process.

The Operating System is now based on the 64 bit version of RedHat/CentOS 6.

Depending on the hardware used the maximum number of seats is likely to be 30 or less. To expand you need multiple servers which in turn require our assistance. (See 'We Install'.)

See a feature list of OSDial.

The hardware requirements for a reliable dialer are higher than a media server. It quickly reaches thousands of read & write operations per second, which are also time sensitive. Please note that our specifications are aimed towards a higher standard of operation and reliability. Lesser components may work well under lower load, or for testing purposes.

•  More cores are better than a faster computer, use a minimum of two cores, four recommended

•  Only use SCSI or SAS Drives. SATA drives will wear out prematurely (6-10 months)

•  Depending on load your dialer may need 4GB RAM, minimum 2GB

•  The Agent computer should have 1GB RAM, minimum 768MB

•  More than a few agents requires a timing source such as Sangoma UT51/51 or A200 (FXO) for each dialer, or you will have missed hangups, cross connects, etc

•  If you record calls use an Archive server to process and store the audio files on

•  Archive server can use SATA drives, always use the best drives available

•  Use the best switch(es) you can afford

•  Ideally use one dedicated switch for the cluster traffic and another for agents

•  Ensure the network wiring is done per specifications

•  Use APC battery backup power supplies for all servers, with max 30% load on the UPS

An additional Archive server may be needed to process and store recordings. Storing recordings on each dialer is not cost effective and will degrade the performance of your dialers. Our Archive server automatically receives the recordings (two for each conversation), mix them into one file and convert it to an easily accessable format.

OSDial has an automated system for transferring files to the archive server continously. In turn it can copy files to a remote location, for example, a client's FTP server. Full logging keeps you informed of any issues that might occur, such as network issues or a busy remote server.

Please note that our license has certain requirements, but the limitations applies mainly if you redistribute the software or provide it as a hosted service. In the case of the latter you may need a different agreement.

Know the FCC Telemarketing rules. New rules were adopted on Feb 15, 2012.

Download OSDial images here: OSDial
NOTE: As soon as the install is completed, update to the latest version by logging in as root on the server and run:

  yum clean all;yum update

Verify the downloaded iso file is not corrupted:
If you know how, it's a good idea to verify that the .iso image has been downloaded properly. Browse to Sourceforge, select osdial. That in turn will list the different versions. Select the version you are interested in, and on that page you will see an 'i' in a grey circle to indicate information. That information contains the SHA1 and MD5 checksums.

Once you have booted from the install DVD you have the option to customize the installation to the function it will serve. In other words you can choose from these:

We have starter documentation.

Update instructions and Announce List.

Support is also available, including training, customizations, including documentation and certified hardware.

NEW! OSDial forum! Post questions and answers to the community. (This may not have a high, or accurate, response rate.)

On older versions you may need to manually add carriers. If this is the case we highly recommend that you upgrade to a current version and get that function integrated into the Administrative menus.