Also to follow up, i would set them inside of [] instead of {} OR use the nolocal: before the variables if you're setting them via export so inline: [realm=xyz]sofia/internal/123 dialplan: <action application="export" data="nolocal:realm=xyz"/> On Sat, Aug 9, 2014 at 7:58 AM, Chris Tunbridge <blasterjr@gmail.com> wrote:
Juan are you trying to do a <condition field="realm" expression="xyz"> if so, those in my experience are not accessible if they've been set inside of the call, what you'll have to do is run a lua/javascript/python/ect and do your comparisons in there, its easy enough, and gives you far more flexibility on how to handle the underlying data.
On Fri, Aug 8, 2014 at 11:05 PM, Juan Cabrio <juancabrio@gmail.com> wrote:
Hi,
I know this has been discussed before but i'm failing to either understand fundamentals or just tie it together. I'm using originate to submit a tiff to the txfax application. No problem there. In my originate command i'm also setting a custom variable called "realm" which I use to tie an originate command to a customer. So i was trying to match the realm in a dialplan and set a bunch of other variables per realm. I believe that I cannot use the custom variable in the dial plan to match on in an expression search.. So.. I'm kinda stuck and looking for suggestions. I really dont want to set all the variables in the originate command in this case.
thanks.
Juan.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org