I sort of figured someone would say that. Actually mod_xml_rpc seems to be similar to mod_xml_curl. Since I already have that mod_xml_curl fetches from my app working well I don't think I will switch that. Also just read that fs_cli uses ESL so that has sold me on sticking with it. I just want to make sure I am not using features that are a bit on the fringe where it's not very active, well tested, and fixes don't come along very often. From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Michael Jerris Sent: Wednesday, January 15, 2014 11:17 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] mod_event_socket or mod_xml_rpc? They are completely different tools for different jobs, not a one or the other situation. On Jan 15, 2014, at 1:32 PM, canuck15 <canuck15@hotmail.com <mailto:canuck15@hotmail.com> > wrote: I am trying to update an old abandoned app (WikiPBX) which is written using Django Python and uses mod_event_socket and mod_xml_curl to talk with Freeswitch. I've got most things working except the most important part which is mod_event_socket. Now I found mod_xml_rpc which seems like a better way to go. Just wanted to get some opinions which is the better api interface before I get too far into trying to get mod_even_socket working properly. So far it's been quite the headache. I am currently looking at fusionpbx and bluebox code to see what they are doing.