[asterisk-doc] Asterisk: The Definitive Guide -- Call For Reviewers

Leif Madsen leif.madsen at asteriskdocs.org
Mon Jan 10 08:32:46 CST 2011


On 11-01-07 09:49 AM, Tzafrir Cohen wrote:
> On Thu, Jan 06, 2011 at 10:06:20AM -0500, Leif Madsen wrote:
>
>> For now, head on over to http://ofps.oreilly.com and check out the book
>> (updated this morning). There are a couple of bugs in the OFPS software
>> which are causing comments to not be available after chapter 8, but we're
>> hoping to have those resolved by Friday. However, we do have this fancy
>> mailing list that we can use.
>
> Chapter 7: regarding DAHDI
>
> 1. Please avoid mentioning dahdi_dummy, as much as possible. It is
> legacy. Also, if you need dahdi_dummy, maybe you're after a different
> timing/conferencing source?
>
> What I generally do is run:
>
>    dahdi_genconf modules
>
> This creates a proper modules file that "empty" for the case of no
> hardware. If you have hardware, it will only put there the relevant
> modules.
>
>
> 2. In the example output you have:
>
>    $ sudo /etc/init.d/dahdi restart
>    Unloading DAHDI hardware modules: done
>    Loading DAHDI hardware modules:
>    No hardware timing source found in /proc/dahdi, loading dahdi_dummy
>    Running dahdi_cfg: [ OK ]
>
> If one actually has hardware, and one has an empty (completely
> remmed-out) modules file (as shown in the example above), he would run
> that and would thing his system is properly configured, when in fact the
> hardware was not configured.
>
> Maybe give a note about system.conf before instructing to restart?
>
>
> 3. BRI
>
> The simple and common case of BRI is quite similar to that of E1 PRI,
> with slight change of signalling and such. Give a basic stnaza of it
> as well?
>
>
> 4. I'm generally disappointed not to see no mention of dahdi_hardware,
> dahdi_scan and dahdi_genconf. Not to mention lsdahdi (or
> cat /proc/dahdi/* ) .
>
> For a "typical" case, dahdi_genconf gives a rather usable configuration.
> If you think it doesn't - patches are welcomed. "dahdi_hardware; lsdahdi"
> is the basic diagnostic question I ask from people.
>
> Do you really want people to do needless manual work just because they
> can?


I've taken a lot of your suggestions into consideration and have added several 
notes and moved some things around. I added references to using all the tools 
(dahdi_genconf, lsdahdi, dahdi_hardware, etc...) somewhere in this chapter now 
as well.

Thanks!
Leif.



More information about the asterisk-doc mailing list