ToD routing when using xml_curl makes no sense, You can already answer the request with exactly what needs to run for the current time the request is being made.

/b


On Mon, May 15, 2017 at 11:41 AM, Piccinin Francesco <francesco.piccinin@insiel.it> wrote:
Hi all,
we are trying to setup Freeswitch ToD routing using XML curl for XML dialplan dynamic generation.

Please note that our dialplan is mainly stored on static file (plus lua support) with few exceptions like IVRs.
In order to avoid freeswitch sending http post on every call (as would happen adding binding=directory on xml_curl configuration module), we would like to find a way to generate dynamic xml dialplan only on particular case like ToD.

Can you please give us some clues about this?

Thanks
Regards

Francesco

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.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



--

Brian West
brian@freeswitch.org

Twitter: @FreeSWITCH , @briankwest

http://www.freeswitchbook.com 
http://www.freeswitchcookbook.com

Book a phone call (CST)

Allison prompts for FreeSWITCH:

https://www.gofundme.com/allison-prompts-for-freeswitch

Got Bugs? Report them here! | Reddit: /r/freeswitch

T:+19184209001 | F:+19184209002 | M:+1918424WEST (9378)
Skype:briankwest