2008/12/2 Tzafrir Cohen <[EMAIL PROTECTED]> > 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.
>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. 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:[EMAIL PROTECTED]<[EMAIL PROTECTED]> > +972-50-7952406 mailto:[EMAIL PROTECTED] > http://www.xorcom.com iax:[EMAIL PROTECTED]/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 >
_______________________________________________ -- 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
