Hello FS gurus, I'm using xml_curl for external dialplan fetch, but I like to split static and dynamic parts of configuration, so for example, leave call unloop logic, and voicemail extension in static xml file while having all other parts dynamic. It will allow to avoid unnecessary call to costly external source and also avoid xml parse of content that is static. Currently FS first look in xml_curl and only after that falls back to static files. Is that behavior possible to change, so FS will work like that: 1 - Look in static xml file and execute all extensions that have 'continue="true"' 2 - If previous step didn't stop on matching extension than look in xml_curl or other source specified in dialplan param of sofia config. Looks like <param name="dialplan" value="XML:/path_to_dialplan_default.xml,XML"/> don't do the trick. I'm sorry if my question is really noobish or goes against FS logic. Thanks in advance. -- Mike Tkachuk
On Feb 8, 2010, at 6:19 AM, Mike Tkachuk wrote:
I'm using xml_curl for external dialplan fetch, but I like to split static and dynamic parts of configuration, so for example, leave call unloop logic, and voicemail extension in static xml file while having all other parts dynamic. It will allow to avoid unnecessary call to costly external source and also avoid xml parse of content that is static.
Currently FS first look in xml_curl and only after that falls back to static files. Is that behavior possible to change, so FS will work like that:
1 - Look in static xml file and execute all extensions that have 'continue="true"' 2 - If previous step didn't stop on matching extension than look in xml_curl or other source specified in dialplan param of sofia config.
Looks like <param name="dialplan" value="XML:/path_to_dialplan_default.xml,XML"/> don't do the trick.
This is exactly how you do this. What is not working about it? Mike
participants (2)
-
Michael Jerris
-
Mike Tkachuk