asterisk users - Dec 2008 - Which installation policy is behind Asterisk doc delivered with source code ?

Hi,

Testing latest 1.6.1, it occurred to me I had to add a couple of noload
statements in /etc/asterisk/modules.conf to remove ERROR messages, when
starting Asterisk.
(I don't imply those ERROR messages were fatal to Asterisk but as a general
rule, I tried to start Asterisk without any of those).

As I'm not very familiar with module concepts at the moment, I told myself
it would be helpful, if strictly following instructions included in README
files, I did get a system that starts without any ERROR message of any kind
and still could provide some basic telephony services.

So my question is :
- is there a policy fixing the target of README files ?
- for example, if someone installs Asterisk (according README files) on a
platform equipped with a Digium analog board, should this board be
automatically discovered, configured and ready to run ?

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20081202/162ae013/attachment.htm

On Tue, Dec 02, 2008 at 08:30:34AM +0100, Olivier wrote:
> Hi,
> 
> Testing latest 1.6.1, it occurred to me I had to add a couple of noload
> statements in /etc/asterisk/modules.conf to remove ERROR messages, when
> starting Asterisk.
> (I don't imply those ERROR messages were fatal to Asterisk but as a
general
> rule, I tried to start Asterisk without any of those).
Could you be specific? I think that some messages may be
wrongly-labeled.
> 
> As I'm not very familiar with module concepts at the moment, I told
myself
> it would be helpful, if strictly following instructions included in README
> files, I did get a system that starts without any ERROR message of any kind
> and still could provide some basic telephony services.
> 
> So my question is :
> - is there a policy fixing the target of README files ?
> - for example, if someone installs Asterisk (according README files) on a
> platform equipped with a Digium analog board, should this board be
> automatically discovered, configured and ready to run ?
Not yet:

# which modules to load: a temporary workaround
# dahdi_modules is a simple two-liner scrippt that is currently not
# installed by default. I figure I should get that functionality added
# to dahdi_genconf
dahdi_modules >/etc/dahdi/modules
/etc/init.d/dahdi start
# generate /etc/dahdi/system.conf and /etc/asterisk/dahdi-channels.conf
dahdi_genconf
dahdi_cfg

# edit chan_dahdi.conf accordingly. e.g.:
echo '#include dahdi-channels.conf'
>>/etc/asterisk/chan_dahdi.conf

# apply changes: start/restart asterisk, or:
asterisk -rx 'dahdi restart'

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir