<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: ltr;">mod xml rpc</div><div style="direction: ltr;">or php esl</div><br>Envoyé de mon iPhone</div><div><br>Le 3 mai 2017 à 11:41, Oivvio Polite <<a href="mailto:mylists@polite.se">mylists@polite.se</a>> a écrit :<br><br></div><blockquote type="cite"><div><span>I have a simple call recording solution set up with a Twilio-like PaaS.</span><br><span></span><br><span>The user interacts with a web app where she enters a destination number.</span><br><span>My web app then instructs the PaaS to </span><br><span></span><br><span> 1. Call the users phone</span><br><span> 2. Wait for the user to answer</span><br><span> 3. Start a recording.</span><br><span> 4. Connect the destination number.</span><br><span></span><br><span>The resulting wav is available for the user to download in the web app.</span><br><span></span><br><span>I now want to replace the PaaS with FreeSwitch. I've done a lot of</span><br><span>experimenting with FS during the last year, and managed to get</span><br><span>callrecording of PSTN and WebRTC calls to work.</span><br><span></span><br><span>With those calls origination was from PSTN or WebRTC. Now I want to do</span><br><span>origination with a HTTP request. When leafing through the FreeSwitch</span><br><span>book from PACKT I see that I have multiple options for doing this.</span><br><span></span><br><span>1. fs_cli</span><br><span></span><br><span>Have the browser talk to a separate web app (written in node or python</span><br><span>or whatever) that the initiates the call with fs_cli. </span><br><span></span><br><span></span><br><span>2. mod_httapi</span><br><span></span><br><span>Have the browser talk to a webapp that talks to FS via mod_httapi. In</span><br><span>this scenario I can't find any info on how to originate calls in</span><br><span>mod_httapi though.</span><br><span></span><br><span></span><br><span>3. mod_event_socket</span><br><span></span><br><span>Have a the browser talk to a webapp that talks to FS via</span><br><span>mod_event_socket.</span><br><span></span><br><span></span><br><span>In all of these scenarios I figure that I'll have the webapp running on</span><br><span>the same box as FS and that I'll do all authentication/authorization of</span><br><span>the user in the webapp.</span><br><span></span><br><span>But which option should I go with?</span><br><span></span><br><span></span><br><span>regards Oivvio</span><br><span></span><br><span>_________________________________________________________________________</span><br><span>Professional FreeSWITCH Consulting Services: </span><br><span><a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a></span><br><span><a href="http://www.freeswitchsolutions.com">http://www.freeswitchsolutions.com</a></span><br><span></span><br><span>Official FreeSWITCH Sites</span><br><span><a href="http://www.freeswitch.org">http://www.freeswitch.org</a></span><br><span><a href="http://confluence.freeswitch.org">http://confluence.freeswitch.org</a></span><br><span><a href="http://www.cluecon.com">http://www.cluecon.com</a></span><br><span></span><br><span>FreeSWITCH-users mailing list</span><br><span><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a></span><br><span><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a></span><br><span>UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a></span><br><span><a href="http://www.freeswitch.org">http://www.freeswitch.org</a></span><br></div></blockquote></body></html>