Thanks Rupa
d i n ok o r a h
Tel: +44 7956 66 52 83
On 23 June 2010 00:27, Rupa Schomaker wrote:
> commit 2c830f84aa8e5a5b05c55c5f02ae0025c4986bd2
> Author: Mathieu Rene
> Date: Wed Apr 7 15:02:00 2010 -0400
>
> remove switch_channel_export_variable's nolocal argument, more
> confu
ah, didn't look at the diff, just the descri[ption. What I get for
assuming.
On Tue, Jun 22, 2010 at 10:49 PM, Mathieu Rene wrote:
> That is completely unrelated. I added that function so one can all
> switch_channel_export_variable() instead of switch_channel_set_variable()
> followed by getti
That is completely unrelated. I added that function so one can all
switch_channel_export_variable() instead of switch_channel_set_variable()
followed by getting "exports" and appending the name of the new variable.
As for nolocal, it actually saves the variable with a prefix so it has no
effect
commit 2c830f84aa8e5a5b05c55c5f02ae0025c4986bd2
Author: Mathieu Rene
Date: Wed Apr 7 15:02:00 2010 -0400
remove switch_channel_export_variable's nolocal argument, more confusing
than anything else
On Tue, Jun 22, 2010 at 5:26 PM, Dino Korah wrote:
> Thanks Brian,
>
> Then by the looks,
Thanks Brian,
Then by the looks, there is something broken.
When a variable (say MyAppName) is exported as "nolocal", it appears in A
leg CDR as "HelloWorldApp", which
then breaks the XML (those strict parsers).
In the line I pointed earlier; as I understand, if the variable being
exported from
nolocal is just like setting inside {} so its not on the A leg but only on the
B leg.
/b
On Jun 16, 2010, at 4:49 AM, Dino Korah wrote:
> Guys,
>
> When I export a variable as nolocal, is it intended to prefix "nolocal:" for
> that variable on A, when that appears in the CDR?
>
> Or is it a
Guys,
When I export a variable as nolocal, is it intended to prefix "nolocal:" for
that variable on A, when that appears in the CDR?
Or is it a glitch?
Ref: src/mod/applications/mod_dptools/mod_dptools.c line 889
Here if you check, the export seems to ignore the local variable altogether.
I am
