On Oct 15, 2009, at 11:03 AM, Simon J Mudd wrote: > OK. That looks clear. However it doesn't look as if it's possible to > pass parameters this way which means that data can only be passed to > the "extension" via variables. That works but isn't so clean. I'll > check this out further shortly. I'm planning later to pass info like > "which gateway to talk to" and perhaps some sort of flag which > indicates "record: yes/no", and even include the bridge application > into this extension/macro. That reduces the original dialplan pattern > matching to a much simpler and easier to configure setup for me.
here's a tip from a recovering asterisk user: don't feel like you have to do everything via the dialplan. this was a constant mantra in asterisk, because calling AGI scripts was expensive. this is not the case with FreeSWITCH. the general rule of thumb is: as soon as it gets hard to do in the dialplan, farm it out to a script. it's the way FreeSWITCH is designed, so don't fight it ;) that said, you still might be able to use execute_extension along with setting some channel variables before you call it. those channel variables will be available in the executed extension, and can act pretty much like the arguments to a macro. _______________________________________________ FreeSWITCH-users mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
