Hi Kyle, Thanks for your response. I wasn't being clear though. I understand that <action application="httapi" data="http://192.168.100.197/cgi-bin/test.cgi"/> in the dialplan will cause Freeswitch to retrieve the XML to perform work in the dialplan. However in the wiki http://wiki.freeswitch.org/wiki/Mod_httapi under the "Work Tag" section, each type of work describes two attributes: action and temp-action, described as "change the new target url" and "change url to submit to just for the next loop". What is the "loop" it is describing here, and is this a kind of 'callback' to the test.cgi allowing the application to keep control of the dialplan after it has sent the initial response? Thanks again Tom On 22/04/12 18:51, Tom Parrott wrote:
Thanks Michael, yes will certainly help keep the page updated if any more info comes to light.
Thanks Avi, when you say "future httpapi requests" do you think that is when the httapi application is executed again, or is it a type of 'callback' so that when that step in the dialplan is finished the HTTP API being called can instruct Freeswitch to perform another step in the dialplan.
Tom
On 22/04/12 17:46, Tom Parrott wrote:
Hi,
Does anyone have a short guide or blog post on using the mod_httapi.
The wiki page is a bit sparse on details of how to actually use this new module, and have not been able to make much progress with it.
One of my main questions is what is the "action" property of the work element for.
The wiki says it "Change the new target url."
http://wiki.freeswitch.org/wiki/Mod_httapi
But what does that mean?
Thanks Tom