No subject
Thu Jul 12 09:23:04 CDT 2007
such file or directory" on pure-IP platform in which I installed
asterisk-libpri-dahdi trilogy.
Maybe, it's me while following README instructions, maybe README
instructions could be improved or maybe it's wrongly labeled messages ?
That's why I told myself : I'm waiting too much from doc ? is a pure-IP
platform too specific ? what is the official policy ?
README starts with "check hardware compliance".
So maybe, the policy is to have a "somehow functional system with any of
mentioned compliant hardware, with all enhancements such as running as
non-root, set apart".
>
> >
> > 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
That's the point : if optimizing modules load could be postponed to a later
stage, that would be better, IMHO, as installing from source is already a
long process.
>
> # 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'
IMHO, setting a policy would help to guide efforts of many people involved.
That done, maybe we would conclude an interactive script would be the
missing piece to incorporate user choices that are hard to default to.
>
> --
> Tzafrir Cohen
> icq#16849755 jabber:tzafrir.cohen at xorcom.com<jabber%3Atzafrir.cohen at xorcom.com>
> +972-50-7952406 mailto:tzafrir.cohen at xorcom.com
> http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
------=_Part_97736_32562651.1228213031240
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div class="gmail_quote">2008/12/2 Tzafrir Cohen <span dir="ltr"><<a href="mailto:tzafrir.cohen at xorcom.com">tzafrir.cohen at xorcom.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Tue, Dec 02, 2008 at 08:30:34AM +0100, Olivier wrote:<br>
> Hi,<br>
><br>
> Testing latest 1.6.1, it occurred to me I had to add a couple of noload<br>
> statements in /etc/asterisk/modules.conf to remove ERROR messages, when<br>
> starting Asterisk.<br>
> (I don't imply those ERROR messages were fatal to Asterisk but as a general<br>
> rule, I tried to start Asterisk without any of those).<br>
<br>
</div>Could you be specific? I think that some messages may be<br>
wrongly-labeled.</blockquote><div><br>From memory, I had for instance "Failed to open /dev/dahdi/transcode: No such file or directory" on pure-IP platform in which I installed asterisk-libpri-dahdi trilogy.<br>
<br>Maybe, it's me while following README instructions, maybe README instructions could be improved or maybe it's wrongly labeled messages ?<br>That's why I told myself : I'm waiting too much from doc ? is a pure-IP platform too specific ? what is the official policy ?<br>
<br>README starts with "check hardware compliance".<br>So maybe, the policy is to have a "somehow functional system with any of mentioned compliant hardware, with all enhancements such as running as non-root, set apart".<br>
<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div class="Ih2E3d"><br>
><br>
> As I'm not very familiar with module concepts at the moment, I told myself<br>
> it would be helpful, if strictly following instructions included in README<br>
> files, I did get a system that starts without any ERROR message of any kind<br>
> and still could provide some basic telephony services.<br>
><br>
> So my question is :<br>
> - is there a policy fixing the target of README files ?<br>
> - for example, if someone installs Asterisk (according README files) on a<br>
> platform equipped with a Digium analog board, should this board be<br>
> automatically discovered, configured and ready to run ?<br>
<br>
</div>Not yet:<br>
<br>
# which modules to load: a temporary workaround</blockquote><div><br>That's the point : if optimizing modules load could be postponed to a later stage, that would be better, IMHO, as installing from source is already a long process.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
# dahdi_modules is a simple two-liner scrippt that is currently not<br>
# installed by default. I figure I should get that functionality added<br>
# to dahdi_genconf<br>
dahdi_modules >/etc/dahdi/modules<br>
/etc/init.d/dahdi start<br>
# generate /etc/dahdi/system.conf and /etc/asterisk/dahdi-channels.conf<br>
dahdi_genconf<br>
dahdi_cfg<br>
<br>
# edit chan_dahdi.conf accordingly. e.g.:<br>
echo '#include dahdi-channels.conf' >>/etc/asterisk/chan_dahdi.conf<br>
<br>
# apply changes: start/restart asterisk, or:<br>
asterisk -rx 'dahdi restart'</blockquote><div><br>IMHO, setting a policy would help to guide efforts of many people involved.<br>That done, maybe we would conclude an interactive script would be the missing piece to incorporate user choices that are hard to default to.<br>
<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
--<br>
Tzafrir Cohen<br>
icq#16849755 <a href="mailto:jabber%3Atzafrir.cohen at xorcom.com">jabber:tzafrir.cohen at xorcom.com</a><br>
+972-50-7952406 mailto:<a href="mailto:tzafrir.cohen at xorcom.com">tzafrir.cohen at xorcom.com</a><br>
<a href="http://www.xorcom.com" target="_blank">http://www.xorcom.com</a> <a href="http://iax:guest@local.xorcom.com/tzafrir" target="_blank">iax:guest at local.xorcom.com/tzafrir</a><br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote></div><br>
------=_Part_97736_32562651.1228213031240--
More information about the asterisk-users
mailing list