RES: [asterisk-users] Mr. Spencer Written

[cleviton.araujo at caixa.gov.br]

Perfect, Auriol!

Exactly this.


Cléviton.


-----Mensagem original-----
De: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] Em nome de Seb Auriol
Enviada em: terça-feira, 15 de maio de 2007 12:45
Para: 'Asterisk Users Mailing List - Non-Commercial Discussion'
Assunto: RE: [asterisk-users] Mr. Spencer Written

Kristian Kielhofner wrote:
> On 5/15/07, cleviton.araujo at caixa.gov.br
> <cleviton.araujo at caixa.gov.br> wrote:
>> Hi,
>> 
>> Mr. Spencer written the article "Using DUNDi with a Cluster of
>> Asterisk Servers" in the VoIP Magazine and the piece follow:
>> 
>> [lookupdundi]
>>  exten => _X,1,Goto(${ARG1},1)
>>  switch => DUNDi/priv
>>  exten => i,1,Goto(lookupmysql,${INVALID_EXTEN},1)
>> 
>> 
>> I didn't get understand the usage ARG1 argument in the context. Do
>> use ARG1 variable only into macro? Is not this usage apparent
>> contradiction with Asterisk documents? Do anyone get explain this?
>> 
>> 
>> Regards,
>> 
>> Cleviton
>> 
> 
> Cleviton,
> 
>   You can pass arguments into a macro:
> 
> exten => 500,1,Macro(something,${EXTEN})
> 
> [macro-something]
> exten => s,1,Dial(SIP/${ARG1},60)
> 
>   This is perfectly valid.  You can pass multiple arguments and read
> them with ${ARG1}, ${ARG2}, etc, etc:
> 
> http://www.voip-info.org/wiki-Asterisk+variables#Macrospecificvariables

Kristian, I think Cleviton's point was that [lookupdundi] does not appear to
be a macro, and so how can it have arguments if it just a normal context /
extension?

Kind regards,

Sebastian