tor, 10.04.2008 kl. 13.44 +0200, skrev kokoska rokoska:
Hi all,
I try to implement "continue on fail" with different actions (Forward, Voicemail, InbandInfo...) based on failure type (No Answer, Busy...)and come into troubles how to do :-)
From what I know about FreeSWITCH (very few :-) I see three solutions, but I do not like any of them :-)
Pre: My dialplan si served by http server through mod_xml_curl.
1. After the failure use something "Asterisk like" <action application="transfer" data="${originate_disposition}"/> But why should I invoke transfer (new dialplan parsing, garbage in CDR) for such a simple thing? An idea: You can use execute_extension which behaves similar to Asterisk's Macro. Transfer has a closer resemblance to Goto.
2. Use ...break="never"... and serve next extension through mod_xml_curl. Bur it invokes unnecessary http request and even I ask, why should I send it in parts if I know all I need at the beginning of the call?
3. Use custom app to handle processing of failed bridge. <action application="bridge" data="sofia/xxx/yyy%zzz"/> <action application="whatever_lang" data="whatever_name ${originate_disposition}"/> But I dislike to start new process/thread (performance) and, like in previous cases, why to do it i parts, if have all info at the beginnig?
If I look to my ideas, I'm sure I miss something important :-) Could you, please, point me to right way? Or just tell me your "rating" of cases above :-)
Please tell me how it goes and post some examples of your configs if you get it to work.
Thank you very much!
Best regards,
kokoska.rokoska
_______________________________________________ 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