[Asterisk-Users] AEL #include (Labels and Goto app)
Michael Collins
mcollins at fcnetwork.com
Thu Jun 1 12:03:36 MST 2006
> 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
More information about the asterisk-users
mailing list