Asterisk: The Future of Telephony
by Jared Smith, Jim Van Meggelen, Leif Madsen

The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated July 20, 2007.


UNCONFIRMED  errors and comments from readers: 

{unknown} unknown;
Creative commons link is missing the 2nd slash after http:, and the
link as such does not work!


[sec. 12.5] sec 12.5;
section 12.5 says "We are going to explore some of the
fundamentals of AEL", but there is no more mention of AEL in the entire book!

(59)  last paragraph;
This is a small suggestion for an otherwise excellent book:

I was adding a TDM400P to an Asterisk system, and following the instructions in
chapters 3 and 4.  When I first started up, I was getting the error message "Ignoring
signalling" as Asterisk parsed my zapata.conf file.  I ran an Internet search, and
turned up nothing.  I searched the PDF of this book, and didn't find anything,
either.  Ultimately, I found the answer by reading the source code to chan_zap.c.

On re-reading the book, I did find a hint in the book.  On page 59, there's a
sentence that reads "Changes made in zapata.conf will require a reload from the
Asterisk console; however, changing signaling methods requires a restart."  However,
to make the hint clearer, you may wish to consider making this clearer by quoting the
"Ignoring signalling" error message in a footnote or in the text.


{160}  first footnote;

  In the footnote phrase:
      "If safe_9780596009625 was used to start Asterisk, the first Asterisk console will
be on TTY9, which means that you will not be able to view AGI errors remotely".

  In really, we can use the 'conspy' software for view TTY9 from remote access. It
works like a vnc access, but to console instead X. You can access the server via ssh
or telnet, then run

   conspy 9


{272} becasue;
the word "because"
is misspelled "becasue"