OK, so that means multiple extensions not possible. Yes, it's not overly intensive, but nevertheless I actually have to parse regex in the second condition to find out which extension matches incoming number and I wanted instead to let FS do that for me. It is a bit complex since we store complete extension XML in DB, so I have to retrieve all the extensions matching first condition, extract their second condition, then run them in loop... Looks like I can be better off using JS for that instead. Thank you everybody. On Sun, Mar 7, 2010 at 7:32 PM, Brian West <brian@freeswitch.org> wrote:
You generate exactly ONE extension which was the exact way it was designed to be used. You don't have to parse anything only look at the variables you care about and run with it. Its nothing too complex or overly intensive to do.
/b
On Mar 7, 2010, at 4:13 PM, paul gore wrote:
Thanks fro the input. I thought about such approach, the only problem I see is there that I essentially would have to duplicate FS dial plan parsing functionality, so my question basically is there a way to avoid that? I have seen a Ruby dial plan example on XML curl wiki page which actually seem to generate response with multiple extensions, but unfortunately FS cannot read such response.
_______________________________________________ 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