Displaying 3 results from an estimated 3 matches for "local_200".
2015 Apr 08
2
dial out with channel variable; sub-string usage
...; _9011.,1,Dial(Dial({TOLL}/${EXTEN})
(adapted from the book)
but don't know where to put those lines. I have BABY defined as channel
variable:
BABY = SIP/babytel_out
but that seems circular, somehow.
inbound calls work fine:
[inbound-calls]
exten => 16046289850,1,Dial(SIP/200)
[local_200]
exten => _9x.,1,Set(CALLERID(all)="Ali Baba" <123456789>)
exten => _9x.,1,Dial(SIP/${EXTEN:1}@babytel_out)
exten => 201,1,Dial(SIP/201)
[local_201]
exten => 200,1,Dial(SIP/200)
in local_200, that just seems suspect. Yes, dial out, but shouldn't it
be using BABY...
2015 Apr 09
0
dial out with channel variable; sub-string usage
...ok)
>
>
> but don't know where to put those lines. I have BABY defined as
> channel variable:
>
> BABY = SIP/babytel_out
>
> but that seems circular, somehow.
You put them in the context for your clients... From what you show
below, I'd say they go in the "local_200" context. You can verify
this by looking in sip.conf, in the section that starts with [200],
find the line that starts with "context=". It's probably
"context=local_200". Then you put the outbound dialplan in that context
in extensions.conf. Mind you, then 200 is th...
2015 Apr 13
1
dial out with channel variable; sub-string usage
...put those lines. I have BABY defined as
>> >channel variable:
>> >
>> >BABY = SIP/babytel_out
>> >
>> >but that seems circular, somehow.
> You put them in the context for your clients... From what you show
> below, I'd say they go in the "local_200" context. You can verify
> this by looking in sip.conf, in the section that starts with [200],
> find the line that starts with "context=". It's probably
> "context=local_200". Then you put the outbound dialplan in that context
> in extensions.conf. Mind...