Telephony systems are an integral part of business, and it's important that the framework used is flexible enough to cover as many areas of application as possible, and at the same time is user friendly. This book is an attempt at exploring one such system—Asterisk.
Chapter 1 introduces Asterisk and talks about the possible scenarios that would demand its usage, and the realistic trade-offs that you should consider when choosing it.
Chapter 2 discusses a basic deployment plan, and takes you through various aspects such as requirements and the how-tos of choosing the right terminal equipment and hardware.
Chapter 3 discusses installation of Asterisk. It starts with a section on preparing a system for installation, takes you through installation of necessary components, and ends with an introduction to the way Asterisk behaves.
Chapter 4 deals with the basic Asterisk configuration, and discusses the Zaptel interfaces in detail, and then the configuration of protocols and various features.
Chapter 5 deals with creating a dialplan. This involves creating a context and extensions, and the chapter also discusses advanced call distribution and automatic attendants.
Chapter 6 discusses quality assurance issues that concern most companies, and gives an overview of call detail records, call monitoring, and recording, etc.
Chapter 7 talks about Asterisk@Home—a simplified Asterisk solution that retains most of its functionality for its so-called "home" users—and a customer relationship management system, SugarCRM.
In Chapter 8 we've shown a few case studies of working Asterisk-based phone systems, and have discussed scenarios for home offices and small businesses.
Chapter 9 deals with Asterisk's maintenance and security aspects. The topics range from backups of configuration files to disaster management plans to server security. This chapter also discusses Asterisk's scalability aspects and support channels.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
There are three styles for code. Code words in text are shown as follows: "We can include other contexts through the use of the include directive."
A block of code will be set as follows:
[default] exten => s,1,Dial(Zap/1|30) exten => s,2,Voicemail(u100) exten => s,102,Voicemail(b100) exten => i,1,Voicemail(s0)
When we wish to draw your attention to a particular part of a code block, the relevant lines or items will be made bold:
[default]
exten => s,1,Dial(Zap/1|30)
exten => s,2,Voicemail(u100)
exten => s,102,Voicemail(b100)exten => i,1,Voicemail(s0)
Any command-line input and output is written as follows:
# cp /usr/src/asterisk-addons/configs/cdr_mysql.conf.sample /etc/asterisk/cdr_mysql.conf
New terms and important words are introduced in a bold-type font. Words that you see on the screen, in menus or dialog boxes for example, appear in our text like this: "clicking the Next button moves you to the next screen".
Feedback from our readers is always welcome. Let us know what you think about this book, what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply drop an email to <[email protected]>, making sure to mention the book title in the subject of your message.
If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on www.packtpub.com or email <[email protected]>.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Although we have taken every care to ensure the accuracy of our contents, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in text or code—we would be grateful if you would report this to us. By doing this you can save other readers from frustration, and help to improve subsequent versions of this book. If you find any errata, report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the Submit Errata link, and entering the details of your errata. Once your errata have been verified, your submission will be accepted and the errata added to the list of existing errata. The existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
You can contact us at <[email protected]> if you are having a problem with some aspect of the book, and we will do our best to address it.