Free dtmf dialer software for linux

Antidialer is a GUI based broadband dialer program for users of Sify Broadband using Linux. Well, Antidialer is not a cracking tool as the name suggests.
It is very much incomplete in the sense that it doesnt quite have the full feature set that the dialer provided by Sify for Windows has.
But it still does its job of connecting and disconnecting your internet whenever you want.
Main features:
- QT based GUI :-) (absent in the stock dialer provided by Sify)
- AutoConnect
- Encrypted password storage
- HeartBeat to keep connection alive
- XML based configuration file
Enhancements:
- MAC address spoofing is now part of the dialer.
- It can be activated by editing the $HOME/.antidialer/antidialerrc configuraton file and entering the desired MAC address in the "value" property of the "MacAddress" element.
- The dialer now adds missing configuration elements into the config file.
- The plugin framework is now cleaner and faster.
- An obscure bug where the dialer crashed when exactly one config element was missing was fixed.

Chestnut Dialer is PPP (Point to Point Protocol) dialing program, written in Python. Many Internet providers, that provide dialup service, use PPP protocol; this program helps you to connect to Internet using a modem.

Current version (0.2.2) can work with GTK2, QT, or without GUI (command line interface). You can run Chestnut Dialer with users priviliges (it doesnt require root permissions), but it requires read and/or write access to some system files (including the modem device). Chestnut Dialer uses standard pppd daemon to set up network interface.

Intelligent Wardialer is a "war dialer" used for auditing your PSTN (phone) network. Its features include random/sequential dialing, Voice over IP using the IAX2 (Intra-Asterisk eXchange) protocol, ASCII flat file and MySQL logging, a curses-based front end, key stroke marking, multiple modem support, several methods of "tone detection", save/load state, banner detections (to determine remote system types) and blacklist support.
Main features:
- Full and Normal logging: Full logging records all possible events during dialing (busy signals, no answers, carriers, etc). By default it only records things that we might find interesting (carriers, possible telco equipment).
- ASCII flat file and MySQL logging: You can log to a traditional ASCII flat file, and record information into a MySQL database.
- Dials randomly or sequentially.
- Remote system identification: When finding a remote modem and connecting, iWar will remain connected and attempt to identify the remote system type.
- Key stroke marking: When actively "listening" to iWar work, if you hear something interesting, you can manually "mark" it by hitting a key. You can also enter a "note" about something you find interesting.
- Multiple modem support, because... well, hey - this is "Unix". iWar will support as many modems you can hook up
- Nice "curses" based display. This means that if youre using iWar from a Linux console or a VT100 based terminal, it should work fine. Its not a escape sequence kludge, but true "curses".
- Full control over the modem: Unlike other kludges, iWar doesnt just open the modem as a typical "file". It controls the baud rate, parity, and CTS/RTS (Hardware flow control) DTR (Data terminal ready). This is important for controlling the modem and making it preform the way you want it to during scanning. For example, DTR hang ups.
- Blacklisted phone number support: For numbers the system should never dial.
- Save state: If within the middle of a "wardialing" session you want to quit, you can save the current state to a file. This allows you to come back later and restart iWar where you left off. (via the -l option)
- Load pre-generated numbers: You can load a file (via the -L option) of numbers that you want to dial. This is useful if you want to load numbers generated by another routine (perl/shell script/etc).
- Tone location, if your modem supports it. iWar uses two different methods. The traditional "ATDT5551212w;" (Toneloc) and "silence" detection.
- Records remote system banners on connection for later review
- iWar can be used to attack PBXs and Voice mail systems
- Terminal window so you can watch modem interactions and carrier results in real time
- Support the IAX2 (Intra-Asterisk eXchange) "Voice over IP" (VoIP) protocol. This allows you to scan without the need of additional hardware! To my knowledge, iWar is the first war dialer with VoIP functionality
- In IAX2 mode, iWar acts as a "full blown" VoIP client. In this mode, key 0-9, * and # play there DTMF equivalents. In this mode, you can also directly "talk" (using a microphone) with the remote target if so desired.
- In IAX2 mode, if your VoIP provider supports it, you can "set" your caller ID number (caller ID spoofing).
- Comes with complete source code and is released under the GNU General Public License.
Enhancements:
- Major bugfixes were made for BSD type systems.
- Some other minor bugs were also fixed. VoIP IAX2 (Intra-Asterisk eXchange) support was added.
- With this, you can scan with no additional hardware (such as an analog modem).
- Instead, calls are placed over the Internet.
- DTMF support for when under IAX2 mode was added.

GnuDialer is a predictive dialer for contact centers. GnuDialer currently supports inbound, outbound, open/closer, and auto campaigns.

GnuDialer project has a multi-process object oriented design and uses the Asterisk PBX. Gnudialer is separate from any agent interface or CRM, but does include a capable (Java-based) CRM application that uses Firefox, Internet Explorer, and Mozilla.

ASwvdial is a WindowMaker dockapp for wvdial.

In my wvdial.conf every Dialer entry is an provider and aswvdial displays these entrys to connect.

ASwvdial is released under the GNU General Public License.

Taylor UUCP project is a Unix UUCP package.
Taylor UUCP provides everything you need to make a UUCP connection.
It includes versions of uucico, uusched, uuxqt, uux, uucp, uustat, uulog, uuname, uuto, uupick, and cu, as well as uuchk (a program to check configuration files), uuconv (a program to convert from one type of configuration file to another), and tstuu (a test harness for the package).
The package currently supports the f, g (in all window and packet sizes), G, t and e protocols, as well a Zmodem protocol and two new bidirectional protocols.
If you have a Berkeley sockets library, it can make TCP connections. If you have TLI libraries, it can make TLI connections. It supports a new configuration file mechanism which I like (but other people dislike).
Main features:
- You get the source code.
- It uses significantly less CPU time than many UUCP packages.
- You can specify a chat script to run when a system calls in, allowing adjustment of modem parameters on a per system basis.
- You can specify failure strings for chat scripts, allowing the chat script to fail immediately if the modem returns BUSY.
- If you are talking to another instance of the package, you can use the new bidirectional protocol for rapid data transfer in both directions at once. You can also restrict file transfers by size based on the time of day and who placed the call.
- It only runs on Unix. The code is carefully divided into system dependent and system independent portions, so it should be possible to port it to other systems. It would not be trivial.
- You dont get uuclean, uusend, uuq, uusnap, uumonitor, uutry, uupoll, etc. If you have current copies of these programs, you may be able to use them. Shell scripts versions of uuclean and uutry are provided, with most, if not all, of the functionality of the usual programs. I believe the supplied uustat program allows you to do everything that uuq, uusnap and uumonitor do. uupoll could be written as a shell script.
- The package does not read modemcap or acucap files, although you can use V2 configuration files with a BNU Dialers file or a dialer file written in my new configuration file format.
- The package cannot use SCO dialer programs directly, although it can with a simple shell script interface.
Enhancements:
- As usual, many bugs were fixed.
- uuchk now reports the configuration file names which it uses.
- This makes it easier to figure out how to configure a binary installation.
- Certain options which could previously be set in Makefile.in are now set as options to configure: --with-user, --with-newconfigdir, --with-oldconfigdir.
- You can now use file names and notification addresses which contain spaces, but only when talking to another instance of version 1.07.
- The exit status of uux now uses values from .
- TCP ports now support IPv6 on modern systems. A new ``version command in the port file may be used to restrict a TCP port to just IPv4 or just IPv6.
- M and m may now be used in any chat script, not just a dialer chat script.
- Added ``max-file-time command to sys file.
- When uucico automatically invokes uuxqt, it no longer passes the -s option.

POE::Filter::FSSocket is a POE filter that parses FreeSWITCH events into hashes.

SYNOPSIS

#!/usr/bin/perl

use warnings;
use strict;

use POE qw(Component::Client::TCP Filter::FSSocket);
use Data::Dumper;

POE::Component::Client::TCP->new(
RemoteAddress => 127.0.0.1,
RemotePort => 8021,
ServerInput => &handle_server_input,
Filter => POE::Filter::FSSocket,
);

POE::Kernel->run();
exit;

my $auth_sent = 0;
my $password = "ClueCon";

sub handle_server_input {
my ($heap,$input) = @_[HEAP,ARG0];

print Dumper $input;


if($input->{Content-Type} eq "auth/request") {
$auth_sent = 1;
$heap->{server}->put("auth $password");
} elsif ($input->{Content-Type} eq "command/reply") {
if($auth_sent == 1) {
$auth_sent = -1;

#do post auth stuff
$heap->{server}->put("events plain all");
}
}
}

POE::Filter::FSSocket parses output from FreeSWITCH into hashes. FreeSWITCH events have a very wide range of keys, the only consistant one being Content-Type. The keys are dependant on the type of events. You must use the plain event type as that is what the filter knows how to parse. You can ask for as many event types as you like or all for everything. You specify a list of event types by putting spaces between them ex: "events plain api log talk"
Currently known event types (Event-Name):

CUSTOM
CHANNEL_CREATE
CHANNEL_DESTROY
CHANNEL_STATE
CHANNEL_ANSWER
CHANNEL_HANGUP
CHANNEL_EXECUTE
CHANNEL_BRIDGE
CHANNEL_UNBRIDGE
CHANNEL_PROGRESS
CHANNEL_OUTGOING
CHANNEL_PARK
CHANNEL_UNPARK
API
LOG
INBOUND_CHAN
OUTBOUND_CHAN
STARTUP
SHUTDOWN
PUBLISH
UNPUBLISH
TALK
NOTALK
SESSION_CRASH
MODULE_LOAD
DTMF
MESSAGE
CODEC
BACKGROUND_JOB
ALL

Currently handled FreeSWITCH messages (Content-Type):

auth/request
command/response
text/event-plain
api/response (data in __DATA__ variable)
log/data (data in __DATA__ variable)POE::Filter::FSSocket is a POE filter that parses FreeSWITCH events into hashes.