Skip to end of metadata
Go to start of metadata

What Is Asterisk?

People often tend to think of Asterisk as an "open source PBX" because that was the focus of the original development effort.  But calling Asterisk a PBX is both selling it short (it is much more) and overstating it (it can be much less).  It is true that Asterisk started out as a phone system for a small business (see the "Brief History" section for the juicy details) but in the decade since it was originally released it has grown into a universal tool for building communications applications.  Today Asterisk powers not only IP PBX systems but also VoIP gateways, call center systems, conference bridges, voicemail servers and all kinds of other applications that involve real-time communications.

Asterisk is not a PBX but is the engine that powers PBXs.  Asterisk is not an IVR but is the engine that powers IVRs.  Asterisk is not a call center ACD but is the engine that powers ACD/queueing systems.

Asterisk is to communications applications what the Apache web server is to web applications.  Apache is a web server.  Asterisk is a communication server.  Apache handles all the low-level details of sending and receiving data using the HTTP protocol.  Asterisk handles all the low level details of sending and receiving data using lots of different communication protocols.  When you install Apache, you have a web server but its up to you to create the web applications.  When you install Asterisk, you have a communications server but its up to you to create the communications applications.

Web applications are built out of HTML pages, CSS style sheets, server-side processing scripts, images, databases, web services, etc.  Asterisk communications applications are built out Dialplan scripts, configuration files, audio recordings, databases, web services, etc.  For a web application to work, you need the web server connected to the Internet.  For a communications application to work, you need the communications server connected to communication services (VoIP or PSTN).  For people to be able to access your web site you need to register a domain name and set up DNS entries that point "www.yourdomain.com" to your server.  For people to access your communications system you need phone numbers or VoIP URIs that send calls to your server.

In both cases the server is the plumbing that makes your application work.  The server handles the low-level complexities and allows you, the application developer, to concentrate on the application logic and presentation.  You don't have to be an expert on HTTP to create powerful web applications, and you don't have to be an expert on SIP or Q.931 to create powerful communications applications.

Here's a simple example.  The following HTML script, installed on a working web server, prints "Hello World" in large type:

The following Dialplan script answers the phone, waits for one second, plays back "hello world" then hangs up.

In both cases the server components are handling all of the low level details of the underlying protocols.  Your application doesn't have to worry about the byte alignment, the packet size, the codec or any of the thousands of other critical details that make the application work.  This is the power of an engine.

Who Uses Asterisk?

Asterisk is created by communication system developers, for communication system developers.  As an open source project, Asterisk is a collaboration between many different individuals and companies, all of which need a flexible communications engine to power their applications.  

  • No labels