yes it will be there in ext 500. any vars in {} are set when the channel is created and are present the rest of
the life of the channel.
you can do regex on it in the dialplan by referencing it with a ${} in the field
<condition field="${myvar}" expression="blah"> ... </condition>
and any apps you execute will also be able to get the value of ${myvar}
Here's an example:
bgapi originate {myvar=blah}sofia/gateway/gw/19415551212 &transfer(500
XML default) 9185551212 60
So... I'd like to be able to read ${myvar} from the the 500 extension
in the default context.
--
On 1/8/09, Anthony Minessale <anthony.minessale@gmail.com> wrote:
> the variables should still be set on the channel in your application?
> you mean a remote call-leg or the channel itself once it's in the app?
>
>
> On Thu, Jan 8, 2009 at 5:50 PM, Michael Collins <msc@freeswitch.org> wrote:
>
> > On Thu, Jan 8, 2009 at 9:06 AM, Kristian Kielhofner
> >
> > <kristian.kielhofner@gmail.com> wrote:
> >
> > > On 1/8/09, Anthony Minessale <anthony.minessale@gmail.com> wrote:
> > >> put them in {} comma separated.
> > >>
> > >>
> > >> {foo=bar,test=true}sofia/default/user@dom.com
> > >>
> > >> if you are doing forked dial you can set them per leg with []
> > >>
> > >>
> [var1=foo]sofia/default/user@dom.com,[var1=bar]sofia/default/user2@dom.com
> > >>
> > >
> > > Tony,
> > >
> > > Thanks for getting back to me. This part I understand (using
> > > commas, etc). What I need to figure out is how to get those variables
> > > to be available to the application I am calling after the channel in
> > > the originate command. In this case transfer to put my call back into
> > > the dialplan.
> > >
> > > basically I need a way to set variables in the originate command
> > > that are available to the application I am calling, not just the
> > > channel I am creating with the URL syntax.
> >
> > What application(s) are you calling? Could you post an example?
> > -MC
> >
> >
> >
> >
> >
> > >
> > > Am I making anymore sense?
> > >
> > > Thanks again!
> > >
> > > --
> > > Kristian Kielhofner
> > > http://blog.krisk.org
> > > http://www.submityoursip.com
> > > http://www.astlinux.org
> > > http://www.star2star.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
> > >
> >
> > _______________________________________________
> > 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
> >
>
>
>
> --
> Anthony Minessale II
>
> FreeSWITCH http://www.freeswitch.org/
> ClueCon http://www.cluecon.com/
>
> AIM: anthm
> MSN:anthony_minessale@hotmail.com
> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
> IRC: irc.freenode.net #freeswitch
>
> FreeSWITCH Developer Conference
> sip:888@conference.freeswitch.org
> iax:guest@conference.freeswitch.org/888
> googletalk:conf+888@conference.freeswitch.org
> pstn:213-799-1400
>
> _______________________________________________
> 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
>
>
Kristian Kielhofner
http://blog.krisk.org
http://www.submityoursip.com
http://www.astlinux.org
http://www.star2star.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