thr3ads.net - asterisk users - [Asterisk-Users] AEL #include [May 2006]

If this information is useful, please help other people find it:
Share via:

Douglas Garstang

2006-May-30 12:57 UTC

[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

Aaron Daniel

2006-May-30 12:59 UTC

head link

[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
amdtech@shsu.edu
(936) 294-4198

Douglas Garstang

2006-May-30 13:08 UTC

head link

[Asterisk-Users] AEL #include

In non-developer-speak, that means, 'not in current release', correct?
> -----Original Message-----
> From: Aaron Daniel [mailto:amdtech@shsu.edu]
> 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
> amdtech@shsu.edu
> (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
>

Douglas Garstang

2006-May-30 13:54 UTC

head link

[Asterisk-Users] AEL #include

> -----Original Message-----
> From: Joshua Colp [mailto:jcolp@digium.com]
> 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.

Douglas Garstang

2006-May-30 14:15 UTC

head link

[Asterisk-Users] AEL #include

> -----Original Message-----
> From: Kevin P. Fleming [mailto:kpfleming@digium.com]
> 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.

Douglas Garstang

2006-May-30 14:28 UTC

head link

[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:scook@kinex.net]
> 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:amdtech@shsu.edu]
> >> 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
> >> amdtech@shsu.edu
> >> (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
>

Watkins, Bradley

2006-May-30 14:55 UTC

head link

[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: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] 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:kpfleming@digium.com]
> 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.

Michael Collins

2006-May-30 15:01 UTC

head link

[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

Kevin P. Fleming

2006-May-30 15:17 UTC

head link

[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.

Douglas Garstang

2006-May-30 20:13 UTC

head link

[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:mcollins@fcnetwork.com] 
	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

Michael Collins

2006-May-30 21:28 UTC

head link

[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

Douglas Garstang

2006-May-31 07:45 UTC

head link

[Asterisk-Users] AEL #include

> -----Original Message-----
> From: Michael Collins [mailto:mcollins@fcnetwork.com]
> 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.

Michael Collins

2006-May-31 08:21 UTC

head link

[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

Douglas Garstang

2006-May-31 08:48 UTC

head link

[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:mcollins@fcnetwork.com]
> 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
>

Michael Collins

2006-May-31 09:42 UTC

head link

[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

Douglas Garstang

2006-Jun-01 10:55 UTC

head link

[Asterisk-Users] AEL #include

> -----Original Message-----
> From: Jason Bachman [mailto:jason@bachman.cc]
> 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!

Michael Collins

2006-Jun-01 11:06 UTC

head link

[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

Oliver Vermeulen

2006-Jun-01 11:10 UTC

head link

[Asterisk-Users] SkypeOUT proxy

Dose anybody know how to put skype behind a usa proxy ?

Thanks,
O

Douglas Garstang

2006-Jun-01 11:12 UTC

head link

[Asterisk-Users] AEL #include

> -----Original Message-----
> From: Michael Collins [mailto:mcollins@fcnetwork.com]
> 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.

Douglas Garstang

2006-Jun-01 11:44 UTC

head link

[Asterisk-Users] AEL #include

There's no mention of labels.
> -----Original Message-----
> From: Julian Lyndon-Smith [mailto:asterisk@dotr.com]
> 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:mcollins@fcnetwork.com]
> >> 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
>

Dovid Bender

2006-Jun-13 14:25 UTC

head link

[Asterisk-Users] SkypeOUT proxy

Get a VPS machine in the US

Oliver Vermeulen <oliver@wvg-tele.com> wrote: Dose anybody know how to put
skype behind a usa proxy ?

Thanks,
O

_______________________________________________
--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


 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060613/7fddfae8/attachment.htm

Reasonably Related Threads

Search for more seemingly similar threads

asterisk users - May 2006 - AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] SkypeOUT proxy

[Asterisk-Users] AEL #include

[Asterisk-Users] AEL #include

[Asterisk-Users] SkypeOUT proxy

Reasonably Related Threads