This has got to be an FAQ, so if someone can point me to where it is answered, I would be greatly appreciated. The documentation for all this stuff is scattered and (to me at least) either very sketchy or hard to find. What I want is a guide for how to convert from 1.4 with zaptel to 1.6 with dahdi. All the recent kernel vulnerabilities are forcing me to upgrade my home server from no-longer-supported Fedora 8 up to Fedora 11, and that means upgrading asterisk as well. It appears that, although the dahdi-tools package is part of Fedora 11, the kernel modules are not. I couldn't get the dahdi tools such as dahdi_scan to work at all until I installed the dahdi-kmdl package from ATrpms. Does that match others' experiences? This also means a translation from extensions.conf to AEL. I tried using the tool whose name I forget that produces an ael file from an old extensions.conf file, but I get tons of errors when I try to load the resulting file. In particular, there are comments about Macros but no detailed documentation as to how to translate something like "GoTo(s| 3)". I try using "goto s|3" and get an error that there is no label "s" in the current context. Is there something else I should be doing to accomplish this, or do I really have to create an explicit label for every extension that is the current target of a Goto() call? Thanks for any advice. A line-by-line translation of my dialplan looks to be a very tedious and time-consuming task with a steep learning curve. There has got to be a better way, I know I'm not the first to have to do this. --Greg
Can I make a non related suggestions? Ditch Fedora and use CentOS. Greg Woods wrote:> This has got to be an FAQ, so if someone can point me to where it is > answered, I would be greatly appreciated. The documentation for all this > stuff is scattered and (to me at least) either very sketchy or hard to > find. > > What I want is a guide for how to convert from 1.4 with zaptel to 1.6 > with dahdi. All the recent kernel vulnerabilities are forcing me to > upgrade my home server from no-longer-supported Fedora 8 up to Fedora > 11, and that means upgrading asterisk as well. > > It appears that, although the dahdi-tools package is part of Fedora 11, > the kernel modules are not. I couldn't get the dahdi tools such as > dahdi_scan to work at all until I installed the dahdi-kmdl package from > ATrpms. Does that match others' experiences? > > This also means a translation from extensions.conf to AEL. I tried using > the tool whose name I forget that produces an ael file from an old > extensions.conf file, but I get tons of errors when I try to load the > resulting file. In particular, there are comments about Macros but no > detailed documentation as to how to translate something like "GoTo(s| > 3)". I try using "goto s|3" and get an error that there is no label "s" > in the current context. Is there something else I should be doing to > accomplish this, or do I really have to create an explicit label for > every extension that is the current target of a Goto() call? > > Thanks for any advice. A line-by-line translation of my dialplan looks > to be a very tedious and time-consuming task with a steep learning > curve. There has got to be a better way, I know I'm not the first to > have to do this. > > --Greg > > > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > AstriCon 2009 - October 13 - 15 Phoenix, Arizona > Register Now: http://www.astricon.net > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- A non-text attachment was scrubbed... Name: wang.vcf Type: text/x-vcard Size: 116 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20090819/f36ed512/attachment.vcf
Hi, On Wed, Aug 19, 2009 at 09:56:38AM -0600, Greg Woods wrote:> This has got to be an FAQ, so if someone can point me to where it is > answered, I would be greatly appreciated. The documentation for all this > stuff is scattered and (to me at least) either very sketchy or hard to > find. > > What I want is a guide for how to convert from 1.4 with zaptel to 1.6 > with dahdi. All the recent kernel vulnerabilities are forcing me to > upgrade my home server from no-longer-supported Fedora 8 up to Fedora > 11, and that means upgrading asterisk as well. > > It appears that, although the dahdi-tools package is part of Fedora 11, > the kernel modules are not. I couldn't get the dahdi tools such as > dahdi_scan to work at all until I installed the dahdi-kmdl package from > ATrpms. Does that match others' experiences?I just finished a transition from the old ATrpms setup for asterisk to a new one that allows you to use asterisk 1.4 on F11 w/o fear of asterisk 1.6 overwriting it. It's not what I recommend, one should try to move to 1.6, but upgrading both the underlying OS and the asterisk/dahdi/zaptel framework can be seperated that way. For RHEL/CentOS/Scientific Linux there will even be asterisk12/zaptel12 support, and there are shiny new 1.6 packages there as well. ATM there are no userland bits to download at ATrpms at all, as I'm trying to move the fax application out of the asterisk14 rpm to using agx-ast-addons instead, but I'll release the packages and make an announcement about it soon. If you feel like a guinea pig, you can contact me off list or on ATrpms-devel to help testing. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20090819/7ffe5f4c/attachment.pgp
I'm a 1.2 Luddite, but... On Wed, 19 Aug 2009, Greg Woods wrote:> What I want is a guide for how to convert from 1.4 with zaptel to 1.6 > with dahdi.If you didn't find it on voip-info.org, please start an article.> All the recent kernel vulnerabilities are forcing me to upgrade my home > server from no-longer-supported Fedora 8 up to Fedora 11, and that means > upgrading asterisk as well.Not to start a flame war, but I'm very happy with CentOS 5.3. Any particular reason you can't compile 1.4 on F11?> This also means a translation from extensions.conf to AEL.Really? AEL is "compiled" by pbx_ael.so into plain old extensions.conf style dialplan. When was extensions.conf deprecated? Did I miss the memo? -- Thanks in advance, ------------------------------------------------------------------------- Steve Edwards sedwards at sedwards.com Voice: +1-760-468-3867 PST Newline Fax: +1-760-731-3000
On Wed, Aug 19, 2009 at 11:56 AM, Greg Woods<greg at gregandeva.net> wrote:> This has got to be an FAQ, so if someone can point me to where it is > answered, I would be greatly appreciated. The documentation for all this > stuff is scattered and (to me at least) either very sketchy or hard to > find. > > What I want is a guide for how to convert from 1.4 with zaptel to 1.6 > with dahdi. All the recent kernel vulnerabilities are forcing me to > upgrade my home server from no-longer-supported Fedora 8 up to Fedora > 11, and that means upgrading asterisk as well.It sounds like you would really rather not convert from 1.4 to 1.6 right now. So don't. I'm going to suggest something controversial. Build from source, and don't even spend more than 1 minute looking for an rpm. http://downloads.asterisk.org/pub/telephony/asterisk/ tar -x ./configure make make install Done.
On Wed, 2009-08-19 at 12:25 -0400, Singer X.J. Wang wrote:> Can I make a non related suggestions? > > Ditch Fedora and use CentOS.Might be a possibility except that this is a catch-all home server. It is used for things other than asterisk, so there are other reasons why I need a more up-to-date distro. --Greg
On Wed, 2009-08-19 at 09:56 -0600, Greg Woods wrote:> This has got to be an FAQ, so if someone can point me to where it is > answered, I would be greatly appreciated. The documentation for all this > stuff is scattered and (to me at least) either very sketchy or hard to > find. >Well at least I'm not crazy, since so far all the suggestions have been ways to avoid doing the conversion at all (I may consider some of them). Unfortunately converting to a whole different OS is likely to be just as big a task (if not bigger) than converting * from 1.4 to 1.6, considering that there is more than asterisk involved. I suspect the zaptel/dahdi conversion won't be that hard. It's the extensions.conf -> extensions.ael conversion that's biting me right now. I confess though that I am surprised to find that I had to install the dahdi-kmdl package from ATrpms given that Fedora does package dahdi-tools and dahdi-linux. If at all possible I want to use the standard packaged version as it makes security updates much easier. If I wanted to maintain all my apps from source, I'd use Gentoo which is at least designed to be installed that way :-) Or more likely I'd avoid the OS upgrade at all and compile the apps I use from source on the old OS in order to be able to apply security fixes. But I'm much more willing to compile things from source on my desktop than on my main home server; I need easily maintainable apps there. That, after all, is the whole reason for upgrading the OS in the first place. I heard one person say that extensions.conf should still work in 1.6; is that true? Mine seems to be completely ignored. Is there some other config file that I need to edit to make this happen? If I could do that, I could get the OS switch done and it would buy me some time to do the AEL conversion. --Greg
Greg Woods wrote:> I heard one person say that extensions.conf should still work in 1.6; is > that true? Mine seems to be completely ignored. Is there some other > config file that I need to edit to make this happen? If I could do that, > I could get the OS switch done and it would buy me some time to do the > AEL conversion.extensions.conf is fully supported in Asterisk 1.6.x; there have been some syntax changes (which are covered in the UPGRADE files) that might be causing failures at loading time, but unless you are explicitly *not* loading pbx_config.so, it will be parsed and loaded. -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA skype: kpfleming | jabber: kpfleming at digium.com Check us out at www.digium.com & www.asterisk.org