asterisk users - Feb 2003 - Re: [Asterisk] Major new * Dialplan Features

On Mon, 10 Feb 2003 around 23:28:59 -0600, Mark Spencer wrote:

[snip]
> You can now do:
> 
> [macro-stdexten]
> exten => s,1,Dial(${ARG2},20)
> exten => s,2,Voicemail(u${ARG1})
> exten => s,102,Voicemail(b${ARG2})
> 
> [default]
> exten => 6275,Macro(stdexten,6275,Zap/1)
> exten => 6236,Macro(stdexten,6236,Zap/2)
What I dont like is the fact suddenly the context is prepended
with macro-. In all other cases * takes the context as we
have given it, not zap-remote is we have context=remote
in zaptel.conf etc etc. Why this sudden changeofhart?
Nothing really is gained by it and it throws off the
esthalished set of ground rules :)

    Met vriendelijke groet,
        Pauline Middelink
-- 
GPG Key fingerprint = 2D5B 87A7 DDA6 0378 5DEA  BD3B 9A50 B416 E2D0 C3C2
For more details look at my website http://www.polyware.nl/~middelink
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2107 bytes
Desc: not available
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20030218/dd60315e/attachment.bin>

You don't have to use Macro. Instead you can use Goto and everything
stays the way it used to be.

regards
Martin

On Tue, 18 Feb 2003, Pauline Middelink wrote:
> On Mon, 10 Feb 2003 around 23:28:59 -0600, Mark Spencer wrote:
>
> [snip]
>
> > You can now do:
> >
> > [macro-stdexten]
> > exten => s,1,Dial(${ARG2},20)
> > exten => s,2,Voicemail(u${ARG1})
> > exten => s,102,Voicemail(b${ARG2})
> >
> > [default]
> > exten => 6275,Macro(stdexten,6275,Zap/1)
> > exten => 6236,Macro(stdexten,6236,Zap/2)
>
> What I dont like is the fact suddenly the context is prepended
> with macro-. In all other cases * takes the context as we
> have given it, not zap-remote is we have context=remote
> in zaptel.conf etc etc. Why this sudden changeofhart?
> Nothing really is gained by it and it throws off the
> esthalished set of ground rules :)
>
>     Met vriendelijke groet,
>         Pauline Middelink
> --
> GPG Key fingerprint = 2D5B 87A7 DDA6 0378 5DEA  BD3B 9A50 B416 E2D0 C3C2
> For more details look at my website http://www.polyware.nl/~middelink
>

> What I dont like is the fact suddenly the context is prepended
> with macro-. In all other cases * takes the context as we
> have given it, not zap-remote is we have context=remote
> in zaptel.conf etc etc. Why this sudden changeofhart?
> Nothing really is gained by it and it throws off the
> esthalished set of ground rules :)
I guess the logic was to make it clearer that these contexts are truly
macros, for visibility.  Clearly, in the general case, a context for a
macro will not be useful as a general purpose context due to ${ARG1} et
al.  I'm open to feedback on this though.  Anybody else have feelings one
way or another?

Mark

At 10:54 18-2-2003 -0600, you wrote:
> > What I dont like is the fact suddenly the context is prepended
> > with macro-. In all other cases * takes the context as we
> > have given it, not zap-remote is we have context=remote
> > in zaptel.conf etc etc. Why this sudden changeofhart?
> > Nothing really is gained by it and it throws off the
> > esthalished set of ground rules :)
>
>I guess the logic was to make it clearer that these contexts are truly
>macros, for visibility.  Clearly, in the general case, a context for a
>macro will not be useful as a general purpose context due to ${ARG1} et
>al.  I'm open to feedback on this though.  Anybody else have feelings
one
>way or another?

I must say I'm sympathetic to Paulines views on this matter. Maybe it is 
even more usefull to create a different syntax to indicate a macro which 
does not have a high risk of confusion with contexts. Maybe:

@stdexten
exten => s,1,Dial(${ARG2},20)
exten => s,2,Voicemail(u${ARG1})
exten => s,102,Voicemail(b${ARG2})

[default]
exten => 6275,Macro(stdexten,6275,Zap/1)
exten => 6236,Macro(stdexten,6236,Zap/2)

Or something similar.

Best regards,
Florian