Hi Mathieu,

Is there any update on this issue ? I stumbled onto it just now.

I'm doing something like this:

1 - inbound context: set a-leg identity_id as channel variable identity_id
2 - lookup context: set b-leg identity_id as channel variable nolocal:identity_id
3 - outbound context: use nolocal:identity_id in condition to do some actions and eventually bridge
4 - generate separate a- and b-leg xml cdr's

My xml cdr parser breaks on the nolocal: prefix on some variables in the a-leg cdr. (4)

One other issue I'm having is that it seems I can't use nolocal: channel variables in xml dialplan conditions. (3) This is probably because the colon is used in for example ${foo:5} to get the 5 first characters, so I can't do something like this:

<extension name="foo">
<condition field="${nolocal:identity_id}" expression="bar">
<action etc....

Is there any solution to doing this ?

Thanks a lot,

Leon




On Jun 23, 2010, at 5:49 AM, 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 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 on the A-leg, what would be the proper fix for the xml without completely wiping the entry away? Its sometimes useful to know something was exported for the B-leg. Can we escape the : ?

Mathieu Rene
Avant-Garde Solutions Inc
Office: + 1 (514) 664-1044 x100
Cell: +1 (514) 664-1044 x200




On 2010-06-22, at 7:27 PM, Rupa Schomaker wrote:

commit 2c830f84aa8e5a5b05c55c5f02ae0025c4986bd2
Author: Mathieu Rene <mrene@avgs.ca>
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 <dckorah@gmail.com> wrote:
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 "<nolocal:MyAppName>HelloWorldApp</nolocal:MyAppName>", which then breaks the XML (those strict parsers).

In the line I pointed earlier; as I understand, if the variable being exported from dial_plan is set "nolocal" should be ignored for A.

I can fix and checkin or send a patch; but not sure if it will break anything else.

"dk"



On 22 June 2010 17:25, Brian West <brian@freeswitch.org> wrote:
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 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 quite new to freeswitch; any help much appreciated.
>
> Many thanks,
> "dk"


_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org


_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org




--
-Rupa
_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org

_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org