[asterisk-users] AEL #include file
Hi, Does anyone know how to include a file in AEL using the #include filename syntax in .conf files? Regards, Philipp -- amooma GmbH - Bachstr. 126 - 56566 Neuwied - http://www.amooma.de Let's use IT to solve problems and not to create new ones. Asterisk? - http://www.das-asterisk-buch.de Geschäftsführer: Stefan Wintermeyer Handelsregister: Neuwied B 14998 ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AEL #include file
Philipp Kempgen wrote: Does anyone know how to include a file in AEL using the #include filename syntax in .conf files? Seems like #include test.ael works but #include test.conf does not. Regards, Philipp -- amooma GmbH - Bachstr. 126 - 56566 Neuwied - http://www.amooma.de Let's use IT to solve problems and not to create new ones. Asterisk? - http://www.das-asterisk-buch.de Geschäftsführer: Stefan Wintermeyer Handelsregister: Neuwied B 14998 ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AEL #include file
On Fri, Mar 09, 2007 at 07:49:45PM +0100, Philipp Kempgen wrote: Hi, Does anyone know how to include a file in AEL using the #include filename syntax in .conf files? Yes, it is supported. (Technically: It is not part of the ael syntax. #include and #exec are preprocessing done before the ael parser gets to read the text.) -- Tzafrir Cohen icq#16849755jabber:[EMAIL PROTECTED] +972-50-7952406 mailto:[EMAIL PROTECTED] http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AEL #include file
Tzafrir Cohen wrote: On Fri, Mar 09, 2007 at 07:49:45PM +0100, Philipp Kempgen wrote: Hi, Does anyone know how to include a file in AEL using the #include filename syntax in .conf files? Yes, it is supported. (Technically: It is not part of the ael syntax. #include and #exec are preprocessing done before the ael parser gets to read the text.) Is there a way to include a .conf file from within .ael? Or the other way round? BTW: Never heard of #exec. What does that do? Shell exec? Regards, Philipp -- amooma GmbH - Bachstr. 126 - 56566 Neuwied - http://www.amooma.de Let's use IT to solve problems and not to create new ones. Asterisk? - http://www.das-asterisk-buch.de Geschäftsführer: Stefan Wintermeyer Handelsregister: Neuwied B 14998 ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AEL #include file
On Fri, 2007-03-09 at 20:42 +0100, Philipp Kempgen wrote: Tzafrir Cohen wrote: On Fri, Mar 09, 2007 at 07:49:45PM +0100, Philipp Kempgen wrote: Hi, Does anyone know how to include a file in AEL using the #include filename syntax in .conf files? Yes, it is supported. Correct. It should assume that files are in /etc/asterisk, if that's what the config file dir is. If they are somewhere, use absolute paths. (Technically: It is not part of the ael syntax. #include and #exec are preprocessing done before the ael parser gets to read the text.) Well, mostly true; the #include directives are obeyed at the lexical level of the AEL parser, which is underneath the parser. Is there a way to include a .conf file from within .ael? Or the other way round? No, there isn't. the extensions.conf format is entirely different than the AEL format, and the AEL parser will not read in extensions.conf formatted files. BTW: Never heard of #exec. What does that do? Shell exec? The #exec option is available in the extensions.conf (and all config files, for that matter). It basically will run the command provided, and the output from it had better be the config file it wants to read in. This is NOT available for AEL files (at the moment, at least). Regards, Philipp smime.p7s Description: S/MIME cryptographic signature ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AEL #include file
Steve Murphy wrote:
On Fri, 2007-03-09 at 20:42 +0100, Philipp Kempgen wrote:
Tzafrir Cohen wrote:
On Fri, Mar 09, 2007 at 07:49:45PM +0100, Philipp Kempgen wrote:
Hi,
Does anyone know how to include a file in AEL using the
#include filename
syntax in .conf files?
Yes, it is supported.
Correct. It should assume that files are in /etc/asterisk, if that's
what the config file dir is. If they are somewhere, use absolute paths.
Sure.
(Technically: It is not part of the ael syntax. #include and #exec are
preprocessing done before the ael parser gets to read the text.)
Well, mostly true; the #include directives are obeyed at the lexical
level of the AEL parser, which is underneath the parser.
Ok. Thanks.
Is there a way to include a .conf file from within .ael?
Or the other way round?
No, there isn't. the extensions.conf format is entirely different than
the AEL format, and the AEL parser will not read in extensions.conf
formatted files.
Ok, that's what I tried to do. Now I understand how things
are processed.
BTW: Never heard of #exec. What does that do? Shell exec?
The #exec option is available in the extensions.conf (and all config
files, for that matter). It basically will run the command provided, and
the output from it had better be the config file it wants to read in.
Found it on the bug tracker. This seems really old but it's
not well known, is it?
This is what I do:
in extensions.conf:
context voicemail
{
mailbox = {
VoiceMailMain(${user_name},s);
}
#include e-number-vmm.ael
}
in e-number-vmm.ael:
80 = jump mailbox;
So if the user wants to change the number to reach VoicemailMain
- provided they use a web interface for that - e-number-vmm.ael
can easily be parsed and adjusted accordingly by some script.
Regards,
Philipp
--
amooma GmbH - Bachstr. 126 - 56566 Neuwied - http://www.amooma.de
Let's use IT to solve problems and not to create new ones.
Asterisk? - http://www.das-asterisk-buch.de
Geschäftsführer: Stefan Wintermeyer
Handelsregister: Neuwied B 14998
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AEL #include file
On Fri, 2007-03-09 at 22:21 +0100, Philipp Kempgen wrote:
Steve Murphy wrote:
On Fri, 2007-03-09 at 20:42 +0100, Philipp Kempgen wrote:
Tzafrir Cohen wrote:
On Fri, Mar 09, 2007 at 07:49:45PM +0100, Philipp Kempgen wrote:
Hi,
Does anyone know how to include a file in AEL using the
#include filename
syntax in .conf files?
Yes, it is supported.
Correct. It should assume that files are in /etc/asterisk, if that's
what the config file dir is. If they are somewhere, use absolute paths.
Sure.
(Technically: It is not part of the ael syntax. #include and #exec are
preprocessing done before the ael parser gets to read the text.)
Well, mostly true; the #include directives are obeyed at the lexical
level of the AEL parser, which is underneath the parser.
Ok. Thanks.
Is there a way to include a .conf file from within .ael?
Or the other way round?
No, there isn't. the extensions.conf format is entirely different than
the AEL format, and the AEL parser will not read in extensions.conf
formatted files.
Ok, that's what I tried to do. Now I understand how things
are processed.
BTW: Never heard of #exec. What does that do? Shell exec?
The #exec option is available in the extensions.conf (and all config
files, for that matter). It basically will run the command provided, and
the output from it had better be the config file it wants to read in.
Found it on the bug tracker. This seems really old but it's
not well known, is it?
I can't really judge how known it is; but when it's handy, it can be
REAL handy. At Digium, for instance, we keep all our config files under
SVN, and the config
files are just #exec's for svn checkouts. All the admins have to do is
commit a change to the configs, and they will be loaded the next time
asterisk is reloaded or restarted
This is what I do:
in extensions.conf:
context voicemail
{
mailbox = {
VoiceMailMain(${user_name},s);
}
#include e-number-vmm.ael
}
in e-number-vmm.ael:
80 = jump mailbox;
So if the user wants to change the number to reach VoicemailMain
- provided they use a web interface for that - e-number-vmm.ael
can easily be parsed and adjusted accordingly by some script.
Just one little mistake I hadn't pointed out earlier; the
extensions.conf would probably really be extensions.ael ! Ignoring this,
the above is perfectly valid use of #include; just remember that the
include
would only happen when asterisk loads, reloads, or AEL is reloaded.
and, hehe, you can rotate the vmm hourly/daily to keep your users on
their toes!
Regards,
Philipp
smime.p7s
Description: S/MIME cryptographic signature
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AEL #include file
Thanks for the reply! Steve Murphy wrote: At Digium, for instance, we keep all our config files under SVN, and the config files are just #exec's for svn checkouts. Nice. Just one little mistake I hadn't pointed out earlier; the extensions.conf would probably really be extensions.ael ! Right. I have that in extensions.ael. Sorry for the confusion. just remember that the include would only happen when asterisk loads, reloads, or AEL is reloaded. and, hehe, you can rotate the vmm hourly/daily to keep your users on their toes! The admin is not supposed to change the mailbox extension once a day. :-) I thought about matching _. and doing a database lookup every time but that would probably be overkill. Regards, Philipp -- amooma GmbH - Bachstr. 126 - 56566 Neuwied - http://www.amooma.de Let's use IT to solve problems and not to create new ones. Asterisk? - http://www.das-asterisk-buch.de Geschäftsführer: Stefan Wintermeyer Handelsregister: Neuwied B 14998 ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
I use the goto to jump across contexts with labels all the time. goto(context,exten,label). works for me. Jason Michael Collins wrote: Oh Crud. So, if I want to jump to another extension or context, I have to specify the full context, extension and priority? I can't specify a label? It's a bit tricky trying to jump to a specific priority in an extension when they're all called 'n' ! Why is something so simple such a mess... Doug, I believe that it has to be one or the other - either labels are unique across the entire dialplan or they are not. However, you may have uncovered a great feature request: allowing the Goto() commands to jump outside the extension and priority while still using a label. I'll post this on the wish list and see what happens. -MC ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
-Original Message- From: Jason Bachman [mailto:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 7:13 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] AEL #include I use the goto to jump across contexts with labels all the time. goto(context,exten,label). works for me. Cool. If you have some time, tell the developer to update the docs! ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
I use the goto to jump across contexts with labels all the time. goto(context,exten,label). works for me. Cool. If you have some time, tell the developer to update the docs! Definitely cool. I will test this out and if I can make it work on my test machine then I will be happy to update the wiki myself. We can always use more documentation and I've never been accused of practicing brevity... -MC ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
-Original Message- From: Michael Collins [mailto:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 12:07 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] AEL #include I use the goto to jump across contexts with labels all the time. goto(context,exten,label). works for me. Cool. If you have some time, tell the developer to update the docs! Definitely cool. I will test this out and if I can make it work on my test machine then I will be happy to update the wiki myself. We can always use more documentation and I've never been accused of practicing brevity... I really wish the developers could do it. I've found that when others contribute to documentation, they make assumptions. These assumptions are sometimes wrong, and incorrect documentation gets posted, which just fuels more incorrect info. One of the limitations of open source I guess (not that it would be that way if developers could update the docs themselves). Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+Goto show application goto -= Info about application 'Goto' =- [Synopsis] Jump to a particular priority, extension, or context [Description] Goto([[context|]extension|]priority): This application will cause the calling channel to continue dialplan execution at the specified priority. If no specific extension, or extension and context, are specified, then this application will jump to the specified priority of the current extension. If the attempt to jump to another location in the dialplan is not successful, then the channel will continue at the next priority of the current extension. Am I being stupid here ? Julian Douglas Garstang wrote: -Original Message- From: Michael Collins [mailto:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 12:07 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] AEL #include I use the goto to jump across contexts with labels all the time. goto(context,exten,label). works for me. Cool. If you have some time, tell the developer to update the docs! Definitely cool. I will test this out and if I can make it work on my test machine then I will be happy to update the wiki myself. We can always use more documentation and I've never been accused of practicing brevity... I really wish the developers could do it. I've found that when others contribute to documentation, they make assumptions. These assumptions are sometimes wrong, and incorrect documentation gets posted, which just fuels more incorrect info. One of the limitations of open source I guess (not that it would be that way if developers could update the docs themselves). Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
There's no mention of labels. -Original Message- From: Julian Lyndon-Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 12:21 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] AEL #include http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+Goto show application goto -= Info about application 'Goto' =- [Synopsis] Jump to a particular priority, extension, or context [Description] Goto([[context|]extension|]priority): This application will cause the calling channel to continue dialplan execution at the specified priority. If no specific extension, or extension and context, are specified, then this application will jump to the specified priority of the current extension. If the attempt to jump to another location in the dialplan is not successful, then the channel will continue at the next priority of the current extension. Am I being stupid here ? Julian Douglas Garstang wrote: -Original Message- From: Michael Collins [mailto:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 12:07 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] AEL #include I use the goto to jump across contexts with labels all the time. goto(context,exten,label). works for me. Cool. If you have some time, tell the developer to update the docs! Definitely cool. I will test this out and if I can make it work on my test machine then I will be happy to update the wiki myself. We can always use more documentation and I've never been accused of practicing brevity... I really wish the developers could do it. I've found that when others contribute to documentation, they make assumptions. These assumptions are sometimes wrong, and incorrect documentation gets posted, which just fuels more incorrect info. One of the limitations of open source I guess (not that it would be that way if developers could update the docs themselves). Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include (Labels and Goto app)
http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+Goto show application goto -= Info about application 'Goto' =- [Synopsis] Jump to a particular priority, extension, or context [Description] Goto([[context|]extension|]priority): This application will cause the calling channel to continue dialplan execution at the specified priority. If no specific extension, or extension and context, are specified, then this application will jump to the specified priority of the current extension. If the attempt to jump to another location in the dialplan is not successful, then the channel will continue at the next priority of the current extension. Am I being stupid here ? Julian, Nope, not stupid. This documentation is adequate if your dialplan uses only hard-numbered priorities, which was all you could do before Asterisk 1.2 came out. In Asterisk 1.2+ you can now use unnumbered priorities (aka the 'n' priority) and you can assign a label to an 'n' priority. (You can also assign a label to a hard-numbered priority if you wish.) However, the goto documentation is a bit thin on what can and cannot be done with the use of labels. What the goto docs needs is an additional entry, something akin to this: Goto(label) - jump to a named priority within the current extension Goto(context,extension,label) - jump to a named priority in the specific context and extension. Some questions arise that aren't specifically answered. Example: is this syntax allowed: Goto(extension,label) ?? Or should the official usage of Goto() with labels be this: Goto([[context|]extension|]label) ?? So, in this case the confusion (and resulting complaints) stem from the fact that none of the official documentation covers the use of Goto() when trying to jump to a label outside the current extension. Also, as of Asterisk 1.2.7, show application goto doesn't even mention the use of labels at all, even though they are specifically supported. Hope that sheds light on the discussion! -MC ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include (Labels and Goto app)
Mea culpa. Did not read properly :) Julian Michael Collins wrote: http://www.voip-info.org/wiki/index.php?page=Asterisk+cmd+Goto show application goto -= Info about application 'Goto' =- [Synopsis] Jump to a particular priority, extension, or context [Description] Goto([[context|]extension|]priority): This application will cause the calling channel to continue dialplan execution at the specified priority. If no specific extension, or extension and context, are specified, then this application will jump to the specified priority of the current extension. If the attempt to jump to another location in the dialplan is not successful, then the channel will continue at the next priority of the current extension. Am I being stupid here ? Julian, Nope, not stupid. This documentation is adequate if your dialplan uses only hard-numbered priorities, which was all you could do before Asterisk 1.2 came out. In Asterisk 1.2+ you can now use unnumbered priorities (aka the 'n' priority) and you can assign a label to an 'n' priority. (You can also assign a label to a hard-numbered priority if you wish.) However, the goto documentation is a bit thin on what can and cannot be done with the use of labels. What the goto docs needs is an additional entry, something akin to this: Goto(label) - jump to a named priority within the current extension Goto(context,extension,label) - jump to a named priority in the specific context and extension. Some questions arise that aren't specifically answered. Example: is this syntax allowed: Goto(extension,label) ?? Or should the official usage of Goto() with labels be this: Goto([[context|]extension|]label) ?? So, in this case the confusion (and resulting complaints) stem from the fact that none of the official documentation covers the use of Goto() when trying to jump to a label outside the current extension. Also, as of Asterisk 1.2.7, show application goto doesn't even mention the use of labels at all, even though they are specifically supported. Hope that sheds light on the discussion! -MC ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
-Original Message-
From: Michael Collins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 10:28 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] AEL #include
How would goto work if all the priorities where n?
...
Example from one of my dial plans:
exten = talk,1,ForkCDR
exten = talk,n,Set(NUMTRIES=1)
exten = talk,n,GotoIf($[${NUMTRIES} = 1]?first)
exten = talk,n(repeat),Background(Initial-greeting)
exten = talk,n(first),Wait(.1)
exten = talk,n,Festival(${fname})
exten = talk,n,Festival(${lname})
exten = talk,n,Background(If-person1)
exten = talk,n,GotoIf($[${NUMTRIES} 2]?repeat)
exten = talk,n,Set(NUMTRIES=$[${NUMTRIES}+1])
exten = talk,n,Goto(t,1)
Doug,
Like Kevin said, the label takes the place of the hard-numbered
priorities. In the example of my talk extension, I have a pair of
GotoIf() commands. This particular extension is used for an
experimental voice-broadcasting system that I'm playing with.
As you can see, the first priority is hard-coded as '1' but each
subsequent priority is simply 'n'. It starts at 1, does the ForkCDR,
then moves on to the next priority. Since there is no '2'
priority, it
simply moves to the next 'n' priority the extension. In this case, it
just sets my NUMTRIES variable then moves to the next 'n' priority,
which is the first of the two GotoIf() commands. Notice the first
after the ? in the GotoIf(). Instead of putting in a
numbered priority,
I put in a label. In this case, the GotoIf() is saying, If
this is the
first attempt, i.e. NUMTRIES equals 1, then goto the priority labeled
'first', otherwise just move on to the next priority. If NUMTRIES is
'1' then the GotoIf sends the processing to this priority:
exten = talk,n(first),Wait(.1)
From there the processing continues.
I have a feeling that if you aren't using labels and you have many
Goto()'s and GotoIf()'s then you'll LOVE labels. Once you get your
labels in place you will almost never have to renumber your
priorities.
Thanks Michael. I was not aware that labels where available.
In converting though, I've already hit a limitation. There's a single name
space for all labels I assume?
When you have multiple loops and things of a similar nature, you have to start
making you label names unique, to the point where they are no longer simple,
and don't make a lot of sense anymore.
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
Thanks Michael. I was not aware that labels where available. In converting though, I've already hit a limitation. There's a single name space for all labels I assume? Doug, According to TFOT's Goto() application reference entry (page 254) the namespace is actually the current extension: Named priorities only work within the current extension. So you can have 50 different labels called start as long as you use start only once per extension. If you're in extension 555 and you Goto(start) it will look for exten = 555,n(start),... If it doesn't find a label start in exten 555 then the Goto() will fail, even if you have start in another extension: exten = 556,n(start),Noop(this start good only from exten 556) HtH. I can see a potential issue if you need to jump from one exten to another exten using Goto(). You still need to use Goto(context,extension,priority) to jump around like that. Do you have any scenarios like that? If so, it might be possible to create numbered jump-to points that will never change, and therefore won't require renumbering each time you make an addition to the dialplan. Example: [test_context] exten = 555,1,Noop(Starting exten 555) exten = 555,n,dialplan stuff exten = 555,n,Goto(test_context,556,999) ; previous line will end up at 556,n(start) exten = 556,1,Noop(Starting exten 556) exten = 556,n,dialplan stuff exten = 556,n(start),Noop(This is where I want to be) exten = 556,n,more dialplan stuff exten = 556,999,Goto(start) ; previous line used to allow other exten's to jump to 556,n(start) FYI, your other post just came in. I think I just answered a few of your questions. Let us know if this helps! -MC ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
Oh Crud. So, if I want to jump to another extension or context, I have to specify the full context, extension and priority? I can't specify a label? It's a bit tricky trying to jump to a specific priority in an extension when they're all called 'n' ! Why is something so simple such a mess... -Original Message- From: Michael Collins [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 31, 2006 9:22 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] AEL #include Thanks Michael. I was not aware that labels where available. In converting though, I've already hit a limitation. There's a single name space for all labels I assume? Doug, According to TFOT's Goto() application reference entry (page 254) the namespace is actually the current extension: Named priorities only work within the current extension. So you can have 50 different labels called start as long as you use start only once per extension. If you're in extension 555 and you Goto(start) it will look for exten = 555,n(start),... If it doesn't find a label start in exten 555 then the Goto() will fail, even if you have start in another extension: exten = 556,n(start),Noop(this start good only from exten 556) HtH. I can see a potential issue if you need to jump from one exten to another exten using Goto(). You still need to use Goto(context,extension,priority) to jump around like that. Do you have any scenarios like that? If so, it might be possible to create numbered jump-to points that will never change, and therefore won't require renumbering each time you make an addition to the dialplan. Example: [test_context] exten = 555,1,Noop(Starting exten 555) exten = 555,n,dialplan stuff exten = 555,n,Goto(test_context,556,999) ; previous line will end up at 556,n(start) exten = 556,1,Noop(Starting exten 556) exten = 556,n,dialplan stuff exten = 556,n(start),Noop(This is where I want to be) exten = 556,n,more dialplan stuff exten = 556,999,Goto(start) ; previous line used to allow other exten's to jump to 556,n(start) FYI, your other post just came in. I think I just answered a few of your questions. Let us know if this helps! -MC ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Douglas Garstang wrote: Oh Crud. So, if I want to jump to another extension or context, I have to specify the full context, extension and priority? I can't specify a label? It's a bit tricky trying to jump to a specific priority in an extension when they're all called 'n' ! No. Labels are interpreted in their target context. Why is something so simple such a mess... It's not. If instead of posting all these message you spent two minutes actually trying it, you would have seen that it already works exactly the way you want it to. assuming there is only a single namespace for labels does not mean it is that way, and when it is so easy to determine that your assumption is incorrect it seems rather pointless as well. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
That's why you *name* certain n priorities, so you can Goto them later easily Douglas Garstang wrote: Oh Crud. So, if I want to jump to another extension or context, I have to specify the full context, extension and priority? I can't specify a label? It's a bit tricky trying to jump to a specific priority in an extension when they're all called 'n' ! Why is something so simple such a mess... -Original Message- From: Michael Collins [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 31, 2006 9:22 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] AEL #include Thanks Michael. I was not aware that labels where available. In converting though, I've already hit a limitation. There's a single name space for all labels I assume? Doug, According to TFOT's Goto() application reference entry (page 254) the namespace is actually the current extension: Named priorities only work within the current extension. So you can have 50 different labels called start as long as you use start only once per extension. If you're in extension 555 and you Goto(start) it will look for exten = 555,n(start),... If it doesn't find a label start in exten 555 then the Goto() will fail, even if you have start in another extension: exten = 556,n(start),Noop(this start good only from exten 556) HtH. I can see a potential issue if you need to jump from one exten to another exten using Goto(). You still need to use Goto(context,extension,priority) to jump around like that. Do you have any scenarios like that? If so, it might be possible to create numbered jump-to points that will never change, and therefore won't require renumbering each time you make an addition to the dialplan. Example: [test_context] exten = 555,1,Noop(Starting exten 555) exten = 555,n,dialplan stuff exten = 555,n,Goto(test_context,556,999) ; previous line will end up at 556,n(start) exten = 556,1,Noop(Starting exten 556) exten = 556,n,dialplan stuff exten = 556,n(start),Noop(This is where I want to be) exten = 556,n,more dialplan stuff exten = 556,999,Goto(start) ; previous line used to allow other exten's to jump to 556,n(start) FYI, your other post just came in. I think I just answered a few of your questions. Let us know if this helps! -MC ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Mojo [EMAIL PROTECTED] Office Manger, Horan Company, LLC (907) 747- x112 ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
I apologize for my silly prior response, I didn't read the thread enough :( Douglas Garstang wrote: Oh Crud. So, if I want to jump to another extension or context, I have to specify the full context, extension and priority? I can't specify a label? It's a bit tricky trying to jump to a specific priority in an extension when they're all called 'n' ! Why is something so simple such a mess... -Original Message- From: Michael Collins [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 31, 2006 9:22 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] AEL #include Thanks Michael. I was not aware that labels where available. In converting though, I've already hit a limitation. There's a single name space for all labels I assume? Doug, According to TFOT's Goto() application reference entry (page 254) the namespace is actually the current extension: Named priorities only work within the current extension. So you can have 50 different labels called start as long as you use start only once per extension. If you're in extension 555 and you Goto(start) it will look for exten = 555,n(start),... If it doesn't find a label start in exten 555 then the Goto() will fail, even if you have start in another extension: exten = 556,n(start),Noop(this start good only from exten 556) HtH. I can see a potential issue if you need to jump from one exten to another exten using Goto(). You still need to use Goto(context,extension,priority) to jump around like that. Do you have any scenarios like that? If so, it might be possible to create numbered jump-to points that will never change, and therefore won't require renumbering each time you make an addition to the dialplan. Example: [test_context] exten = 555,1,Noop(Starting exten 555) exten = 555,n,dialplan stuff exten = 555,n,Goto(test_context,556,999) ; previous line will end up at 556,n(start) exten = 556,1,Noop(Starting exten 556) exten = 556,n,dialplan stuff exten = 556,n(start),Noop(This is where I want to be) exten = 556,n,more dialplan stuff exten = 556,999,Goto(start) ; previous line used to allow other exten's to jump to 556,n(start) FYI, your other post just came in. I think I just answered a few of your questions. Let us know if this helps! -MC ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Mojo [EMAIL PROTECTED] Office Manger, Horan Company, LLC (907) 747- x112 ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
Oh Crud. So, if I want to jump to another extension or context, I have to specify the full context, extension and priority? I can't specify a label? It's a bit tricky trying to jump to a specific priority in an extension when they're all called 'n' ! Why is something so simple such a mess... Doug, I believe that it has to be one or the other - either labels are unique across the entire dialplan or they are not. However, you may have uncovered a great feature request: allowing the Goto() commands to jump outside the extension and priority while still using a label. I'll post this on the wish list and see what happens. -MC ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include ( Now Labels Goto() )
I apologize for my silly prior response, I didn't read the thread enough :( Your humility is much appreciated!! ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
On 5/31/06, Kevin P. Fleming [EMAIL PROTECTED] wrote:
Douglas Garstang wrote:
Oh Crud. So, if I want to jump to another extension or context, I have to
specify the full context, extension and priority? I can't specify a label? It's a
bit tricky trying to jump to a specific priority in an extension when they're all
called 'n' !
No. Labels are interpreted in their target context.
Why is something so simple such a mess...
It's not. If instead of posting all these message you spent two minutes
actually trying it, you would have seen that it already works exactly
the way you want it to. assuming there is only a single namespace for
labels does not mean it is that way, and when it is so easy to determine
that your assumption is incorrect it seems rather pointless as well.
Not to mention that labels documented and have been for months on a
single wiki page! My problem is remembering where the parenthesis go
so I google for it when needed:
asterisk dialplan labels. Try it:
http://www.google.com/search?q=asterisk+dialplan+labels
True, it'd be even nicer if the n wasn't needed at all such as
exten = fax,notafax,noop(this ain't a fax) instead of
exten = fax,n(notafax),noop(this ain't a fax)
I just pretend the 'n(' is a google ad :)
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] AEL #include
Anyone know if #include works in ael yet?
extensions.ael:
#include inc/pbx/global.conf
context test_context {
};
*CLI ael reload
May 30 13:56:45 NOTICE[8516]: pbx_ael.c:1120 handle_root_token: Unknown root
token '#include'
May 30 13:56:45 WARNING[8516]: pbx.c:3758 ast_merge_contexts_and_delete:
Requested contexts didn't get merged
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
No, only works in the old language, or in AEL2 which is released in trunk.
On Tue, 30 May 2006, Douglas Garstang wrote:
Anyone know if #include works in ael yet?
extensions.ael:
#include inc/pbx/global.conf
context test_context {
};
*CLI ael reload
May 30 13:56:45 NOTICE[8516]: pbx_ael.c:1120 handle_root_token: Unknown root
token '#include'
May 30 13:56:45 WARNING[8516]: pbx.c:3758 ast_merge_contexts_and_delete:
Requested contexts didn't get merged
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
In non-developer-speak, that means, 'not in current release', correct?
-Original Message-
From: Aaron Daniel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 2:00 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] AEL #include
No, only works in the old language, or in AEL2 which is
released in trunk.
On Tue, 30 May 2006, Douglas Garstang wrote:
Anyone know if #include works in ael yet?
extensions.ael:
#include inc/pbx/global.conf
context test_context {
};
*CLI ael reload
May 30 13:56:45 NOTICE[8516]: pbx_ael.c:1120
handle_root_token: Unknown root token '#include'
May 30 13:56:45 WARNING[8516]: pbx.c:3758
ast_merge_contexts_and_delete: Requested contexts didn't get merged
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Douglas Garstang wrote:
In non-developer-speak, that means, 'not in current release', correct?
-Original Message-
From: Aaron Daniel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 2:00 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] AEL #include
No, only works in the old language, or in AEL2 which is
released in trunk.
On Tue, 30 May 2006, Douglas Garstang wrote:
Anyone know if #include works in ael yet?
extensions.ael:
#include inc/pbx/global.conf
context test_context {
};
*CLI ael reload
May 30 13:56:45 NOTICE[8516]: pbx_ael.c:1120
handle_root_token: Unknown root token '#include'
May 30 13:56:45 WARNING[8516]: pbx.c:3758
ast_merge_contexts_and_delete: Requested contexts didn't get merged
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Not in the 1.2 release series, no. It only receives bug fixes and this
would not be a bug fix.
--
Joshua Colp
Software Developer
Digium
P - 256-428-6066
C - 506-878-0147
[EMAIL PROTECTED]
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Douglas Garstang wrote: In non-developer-speak, that means, 'not in current release', correct? That is correct. AEL was an experimental feature in Asterisk 1.2.x, and was never fully implemented in that release. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Actually... it means not in the production release. the subversion
trunk is a release but it is not for the faint at heart. While
generally everything works pretty well, it is expected that you will
find bugs and have issues :)
Sean
Douglas Garstang wrote:
In non-developer-speak, that means, 'not in current release', correct?
-Original Message-
From: Aaron Daniel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 2:00 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] AEL #include
No, only works in the old language, or in AEL2 which is
released in trunk.
On Tue, 30 May 2006, Douglas Garstang wrote:
Anyone know if #include works in ael yet?
extensions.ael:
#include inc/pbx/global.conf
context test_context {
};
*CLI ael reload
May 30 13:56:45 NOTICE[8516]: pbx_ael.c:1120
handle_root_token: Unknown root token '#include'
May 30 13:56:45 WARNING[8516]: pbx.c:3758
ast_merge_contexts_and_delete: Requested contexts didn't get merged
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
-Original Message- From: Joshua Colp [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 30, 2006 2:22 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] AEL #include ...[stuff removed] Not in the 1.2 release series, no. It only receives bug fixes and this would not be a bug fix. Well, it looks like not in the svn trunk either. Asterisk-addons doesn't seem to compile, and from the searching I just did, it appears to be a known issue, and to have been around for a while, with no immediate plans for a fix. Considering that I would imagine it's not a good idea to use the asterisk-addons from Asterisk 1.2.7.1, then this makes the svn trunk code completely unusable, as we need asterisk-addons. So... bottom line appears to be that AEL2 is not usable. Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
-Original Message- From: Kevin P. Fleming [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 30, 2006 2:25 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] AEL #include Douglas Garstang wrote: In non-developer-speak, that means, 'not in current release', correct? That is correct. AEL was an experimental feature in Asterisk 1.2.x, and was never fully implemented in that release. Is it going to be sticking around? I sure hope so, because the extensions.conf language is a management nightmare. Every time you add logic, you have to renumber everything, and hope you don't make mistakes in re-setting all the dependant goto's. It ain't exactly easy to read later on either. Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
Yes, like asterisk-addons not compiling, which for anyome that wants to use
cdr-mysql, or realtime, makes it useless.
-Original Message-
From: Sean Cook [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 2:40 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] AEL #include
Actually... it means not in the production release. the subversion
trunk is a release but it is not for the faint at heart. While
generally everything works pretty well, it is expected that you will
find bugs and have issues :)
Sean
Douglas Garstang wrote:
In non-developer-speak, that means, 'not in current
release', correct?
-Original Message-
From: Aaron Daniel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 2:00 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] AEL #include
No, only works in the old language, or in AEL2 which is
released in trunk.
On Tue, 30 May 2006, Douglas Garstang wrote:
Anyone know if #include works in ael yet?
extensions.ael:
#include inc/pbx/global.conf
context test_context {
};
*CLI ael reload
May 30 13:56:45 NOTICE[8516]: pbx_ael.c:1120
handle_root_token: Unknown root token '#include'
May 30 13:56:45 WARNING[8516]: pbx.c:3758
ast_merge_contexts_and_delete: Requested contexts didn't get merged
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
What do you need out of asterisk addons exactly? AEL2 is included in SVN trunk, it replaced AEL completely, so theoretically pbx_ael should compile just like it did before. On Tue, 30 May 2006, Douglas Garstang wrote: -Original Message- From: Joshua Colp [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 30, 2006 2:22 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] AEL #include ...[stuff removed] Not in the 1.2 release series, no. It only receives bug fixes and this would not be a bug fix. Well, it looks like not in the svn trunk either. Asterisk-addons doesn't seem to compile, and from the searching I just did, it appears to be a known issue, and to have been around for a while, with no immediate plans for a fix. Considering that I would imagine it's not a good idea to use the asterisk-addons from Asterisk 1.2.7.1, then this makes the svn trunk code completely unusable, as we need asterisk-addons. So... bottom line appears to be that AEL2 is not usable. Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- Aaron Daniel Computer Systems Technician Sam Houston State University [EMAIL PROTECTED] (936) 294-4198 ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Douglas Garstang wrote: So... bottom line appears to be that AEL2 is not usable. Interesting logic.. you need asterisk-addons, so that means AEL2 is not usable. I'm sure all the people who worked hard on the code and its testing would disagree with you, since it works fine :-) The fact that _YOU_ can't use it does not mean it is not usable; SVN trunk is not meant for production use anyway, it's for development and developer testing. When it gets to beta quality, then it will be usable/testable by non-developers, but should still not be used in production. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Sean Cook wrote: Actually... it means not in the production release. the subversion trunk is a release but it is not for the faint at heart. While generally everything works pretty well, it is expected that you will find bugs and have issues :) No, SVN trunk is not a 'release'. It's a development area. A 'release' involves packaging it, documenting the changes, and handling bug reports against it in a different way. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
Yes, the (newly rewritten, but compatible with older AEL files) version of AEL that is currently in trunk is staying and I think personally it's a big step forward. I still haven't gotten used to it myself, but then the folks who used to write everything in assembler probably took a while to get used to higher-level languages as well. It's certainly a boon to those with complex dialplans, which means just about any of us who use it for more than trivial applications. I'm actually in the process of rewriting my stock dialplan with AEL, and it's going more painlessly than I expected. Regards, - Brad -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Garstang Sent: Tuesday, May 30, 2006 5:16 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] AEL #include -Original Message- From: Kevin P. Fleming [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 30, 2006 2:25 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] AEL #include Douglas Garstang wrote: In non-developer-speak, that means, 'not in current release', correct? That is correct. AEL was an experimental feature in Asterisk 1.2.x, and was never fully implemented in that release. Is it going to be sticking around? I sure hope so, because the extensions.conf language is a management nightmare. Every time you add logic, you have to renumber everything, and hope you don't make mistakes in re-setting all the dependant goto's. It ain't exactly easy to read later on either. Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
*cough* Last I checked, nobody expected trunk to compile exactly right
every time it was downloaded :)
On Tue, 30 May 2006, Douglas Garstang wrote:
Yes, like asterisk-addons not compiling, which for anyome that wants to use
cdr-mysql, or realtime, makes it useless.
-Original Message-
From: Sean Cook [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 2:40 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] AEL #include
Actually... it means not in the production release. the subversion
trunk is a release but it is not for the faint at heart. While
generally everything works pretty well, it is expected that you will
find bugs and have issues :)
Sean
Douglas Garstang wrote:
In non-developer-speak, that means, 'not in current
release', correct?
-Original Message-
From: Aaron Daniel [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 30, 2006 2:00 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] AEL #include
No, only works in the old language, or in AEL2 which is
released in trunk.
On Tue, 30 May 2006, Douglas Garstang wrote:
Anyone know if #include works in ael yet?
extensions.ael:
#include inc/pbx/global.conf
context test_context {
};
*CLI ael reload
May 30 13:56:45 NOTICE[8516]: pbx_ael.c:1120
handle_root_token: Unknown root token '#include'
May 30 13:56:45 WARNING[8516]: pbx.c:3758
ast_merge_contexts_and_delete: Requested contexts didn't get merged
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
Aaron Daniel
Computer Systems Technician
Sam Houston State University
[EMAIL PROTECTED]
(936) 294-4198
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
On 30/05/06, Douglas Garstang [EMAIL PROTECTED] wrote: Yes, like asterisk-addons not compiling, which for anyome that wants to use cdr-mysql, or realtime, makes it useless. It's a development snapshot, you can't expect it not to have issues. -- Peter Bowyer Email: [EMAIL PROTECTED] ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Douglas Garstang wrote: Yes, like asterisk-addons not compiling, which for anyome that wants to use cdr-mysql, or realtime, makes it useless. Again, not true. Realtime works just fine in SVN trunk, except for the direct MySQL driver. There is the ODBC driver and the PostgreSQL driver available already. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
Is it going to be sticking around? I sure hope so, because the
extensions.conf language is a management nightmare. Every time you add
logic, you have to renumber everything, and hope you don't make
mistakes
in re-setting all the dependant goto's. It ain't exactly easy to read
later on either.
Doug,
This may be a dumb question but I wanted to make sure: are you using the
'n' priority in your number plans? (If not, could you let us know why?
Very curious here.) Same question regarding the giving of names to 'n'
priorities.
Example from one of my dial plans:
exten = talk,1,ForkCDR
exten = talk,n,Set(NUMTRIES=1)
exten = talk,n,GotoIf($[${NUMTRIES} = 1]?first)
exten = talk,n(repeat),Background(Initial-greeting)
exten = talk,n(first),Wait(.1)
exten = talk,n,Festival(${fname})
exten = talk,n,Festival(${lname})
exten = talk,n,Background(If-person1)
exten = talk,n,GotoIf($[${NUMTRIES} 2]?repeat)
exten = talk,n,Set(NUMTRIES=$[${NUMTRIES}+1])
exten = talk,n,Goto(t,1)
I know you have specific needs for your application and none of this may
apply, but I figure it's better to be certain.
Thanks for your input!
-MC
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Aaron Daniel wrote: AEL2 is included in SVN trunk, it replaced AEL completely, so theoretically pbx_ael should compile just like it did before. No, it has a number of sub-components and some Makefile rules now, so I don't think it could be backported to 1.2.x. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Uh, yup. I'm using it now. Well, learning it now :) Julian Kevin P. Fleming wrote: Douglas Garstang wrote: So... bottom line appears to be that AEL2 is not usable. Interesting logic.. you need asterisk-addons, so that means AEL2 is not usable. I'm sure all the people who worked hard on the code and its testing would disagree with you, since it works fine :-) The fact that _YOU_ can't use it does not mean it is not usable; SVN trunk is not meant for production use anyway, it's for development and developer testing. When it gets to beta quality, then it will be usable/testable by non-developers, but should still not be used in production. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
On Tue, 30 May 2006, Kevin P. Fleming wrote: Aaron Daniel wrote: AEL2 is included in SVN trunk, it replaced AEL completely, so theoretically pbx_ael should compile just like it did before. No, it has a number of sub-components and some Makefile rules now, so I don't think it could be backported to 1.2.x. ___ I wasn't talking about backporting it to 1.2 :) I was talking about not needing asterisk addons to compile trunk with ael2. -- Aaron Daniel Computer Systems Technician Sam Houston State University [EMAIL PROTECTED] (936) 294-4198 ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
No, SVN trunk is not a 'release'. It's a development area. A 'release' involves packaging it, documenting the changes, and handling bug reports against it in a different way. I guess I see release as a verb and not a noun. Probably is a good idea to use the appropriate terminology... my bad :P ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
Michael,
Well I don't know if I am missing something or not, but we have various
loops and other things in there. So, we need to use the good old ugly goto().
How would goto work if all the priorities where n?
Doug.
-Original Message-
From: Michael Collins [mailto:[EMAIL PROTECTED]
Sent: Tue 5/30/2006 4:01 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Cc:
Subject: RE: [Asterisk-Users] AEL #include
Is it going to be sticking around? I sure hope so, because the
extensions.conf language is a management nightmare. Every time you add
logic, you have to renumber everything, and hope you don't make
mistakes
in re-setting all the dependant goto's. It ain't exactly easy to read
later on either.
Doug,
This may be a dumb question but I wanted to make sure: are you using the
'n' priority in your number plans? (If not, could you let us know why?
Very curious here.) Same question regarding the giving of names to 'n'
priorities.
Example from one of my dial plans:
exten = talk,1,ForkCDR
exten = talk,n,Set(NUMTRIES=1)
exten = talk,n,GotoIf($[${NUMTRIES} = 1]?first)
exten = talk,n(repeat),Background(Initial-greeting)
exten = talk,n(first),Wait(.1)
exten = talk,n,Festival(${fname})
exten = talk,n,Festival(${lname})
exten = talk,n,Background(If-person1)
exten = talk,n,GotoIf($[${NUMTRIES} 2]?repeat)
exten = talk,n,Set(NUMTRIES=$[${NUMTRIES}+1])
exten = talk,n,Goto(t,1)
I know you have specific needs for your application and none of this may
apply, but I figure it's better to be certain.
Thanks for your input!
-MC
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] AEL #include
Douglas Garstang wrote: Well I don't know if I am missing something or not, but we have various loops and other things in there. So, we need to use the good old ugly goto(). How would goto work if all the priorities where n? That is what labels are for. Goto can use labels as targets, just like numbers. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] AEL #include
How would goto work if all the priorities where n?
...
Example from one of my dial plans:
exten = talk,1,ForkCDR
exten = talk,n,Set(NUMTRIES=1)
exten = talk,n,GotoIf($[${NUMTRIES} = 1]?first)
exten = talk,n(repeat),Background(Initial-greeting)
exten = talk,n(first),Wait(.1)
exten = talk,n,Festival(${fname})
exten = talk,n,Festival(${lname})
exten = talk,n,Background(If-person1)
exten = talk,n,GotoIf($[${NUMTRIES} 2]?repeat)
exten = talk,n,Set(NUMTRIES=$[${NUMTRIES}+1])
exten = talk,n,Goto(t,1)
Doug,
Like Kevin said, the label takes the place of the hard-numbered
priorities. In the example of my talk extension, I have a pair of
GotoIf() commands. This particular extension is used for an
experimental voice-broadcasting system that I'm playing with.
As you can see, the first priority is hard-coded as '1' but each
subsequent priority is simply 'n'. It starts at 1, does the ForkCDR,
then moves on to the next priority. Since there is no '2' priority, it
simply moves to the next 'n' priority the extension. In this case, it
just sets my NUMTRIES variable then moves to the next 'n' priority,
which is the first of the two GotoIf() commands. Notice the first
after the ? in the GotoIf(). Instead of putting in a numbered priority,
I put in a label. In this case, the GotoIf() is saying, If this is the
first attempt, i.e. NUMTRIES equals 1, then goto the priority labeled
'first', otherwise just move on to the next priority. If NUMTRIES is
'1' then the GotoIf sends the processing to this priority:
exten = talk,n(first),Wait(.1)
From there the processing continues.
I have a feeling that if you aren't using labels and you have many
Goto()'s and GotoIf()'s then you'll LOVE labels. Once you get your
labels in place you will almost never have to renumber your priorities.
Check this out for more info:
http://www.voip-info.org/wiki/index.php?page=Asterisk%20priorities
Specifically the info under the 'n' priorities. I know that there's
some info on this in the TFOT book but I can't find it right now. But I
highly recommend that you check out using labels and 'n' priorities - it
will decrease your blood pressure significantly!
-MC
___
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
