Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted by | Date Submitted |
---|---|---|---|---|
Printed | Page 130 Second and third lines of code sample from the top of the page |
The example lines with the errors are: |
bgilmer | Dec 03, 2016 |
Printed | Page 110 6th paragraph |
This paragraph, beginning, "Following the type option, we've set host to dynamic..." is technically incorrect. The example it refers to on page 109 does not contain a 'type=dynamic' entry. |
bgilmer | Dec 02, 2016 |
ePub | Page 87 Tip around Figure 3-1 |
"minimum screen size ... is 80x27 pixels" should be "characters" or "cells". |
Jörg Sonnenberger | Jul 08, 2015 |
ePub | Page 128 Password tip |
The tip for generating a random password uses /dev/random, which is nowadays considered bad practice. It provides no security advantage over /dev/urandom, except to waste resources by "draining" the entropy pool. It might be useful to also reference pwgen or apg, which can be often found. |
Jörg Sonnenberger | Jul 08, 2015 |
Printed | Page 103 IPv6 in sip.conf |
The book says: |
Lukas Hauser | Jan 28, 2015 |
Printed | Page 56 Setting File Permissions - near the end - setting dahdi.rules |
The test says "change the last line....". When doing this on Ubuntu server 14.04, it is the first line of the file which needs to be changed, not the last. |
William Colls | Jul 07, 2014 |
Printed | Page 468 1st paragraph |
This table structure definition doesn't appear to work with Digium's DPMA when fetching voicemails. The only way I was able to get the phone interface to actually fetch voicemails without throwing errors was to add the keywords NOT NULL next to the label field definition. |
David Martin | Feb 22, 2014 |
Page 442 In the box, code under [SQL] |
If you use the ${SQL_ESC()} function to escape all the sql that you send to the GENERIC_SQL function, then you won't be able to do something like WHERE column='m', because any way you do that (e.g. WHERE column='m'; or WHERE column=\'m\') the quotes will show up twice. It is better to do the escaping outside of the func_odbc.conf file. |
Shafique Jamal | Dec 20, 2013 | |
Page 459 last paragraph - the part with the SQL commands to create the cdr table |
The line |
Shafique Jamal | Dec 19, 2013 | |
Page 439 In the box, 4rth paragraph |
Shouldn't |
Shafique Jamal | Dec 19, 2013 | |
Page 443 In the box, 2nd paragraph |
You have: |
Shafique Jamal | Dec 19, 2013 | |
Page 54 Code at the top |
The code for RHLinux 64 bit if followed will result in an error because the dahdi linux program must be loaded BEFORE loading the tools program. The modified procedure is as follows: |
Peter Beauregard | Oct 30, 2013 | |
Page 111 botton |
On the botton legend: |
Alberto Lorenzo Pulido | Jun 07, 2013 | |
PDF, Mobi | Page 58 Tip section at the bottom of the page |
The tip states: |
Phil Sharpe | May 23, 2013 |
Other Digital Version | 999 Table 24.2. Default CDR fields |
Noticed today while doing some review, that some fields are missing from the table on CDR records. As of 1.8 the values have existed, but not been documented in the CDR() function. |
Leif Madsen |
Mar 20, 2013 |