<div dir="ltr">I don't fully understand the confusion here. api/bgapi are just there to simplify how to send commands (since they are the mosy commonly used I guess).<div><br></div><div>I'm pretty sure it would cause huge problems for everyone using ESL today, if we'd just remove those functions.</div>
<div><br></div><div>/Peter</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-07-19 0:18 GMT+02:00 Normando Hall <span dir="ltr"><<a href="mailto:nhall@unixlan.com.ar" target="_blank">nhall@unixlan.com.ar</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi guys<br>
<br>
After 2 days I understand some issues with ESL and the NodeJS ESL
wrapper (modesl).<br>
<br>
Learning to use event socket I read that has commands like: api -
bgapi - linger, nolinger etc. <br>
Then, when reading the ESL wrapper for NodeJS I can't found those
sockets commands. Only found api and bgapi, but not linger,
nolinger, etc. So, the wrapper has the same methods as ESL has. But
why I can't found those linger and nolinger methods? Here is the
answer from the ESL wiki:<br>
<br>
<b>api($command, $args) is identical to sendRecv("api $command
$args")</b><br>
<br>
and<br>
<br>
<b>bgapi($command, $args) is identical to sendRecv("bgapi $command
$args")</b><br>
<br>
So... I can figured that "linger" or other commands should send into
the "send" or "sendRecv" methods. This cause me a confussion.<br>
<br>
So, all ESL commands must be send through "send" or "sendRecv"
methods, and "api" or "bgapi" are shorthands of "send" method for
api/bgapi.<br>
<br>
I think these methods (api-bgapi) should be remove from ESL, to
avoid future confussion.<br>
<br>
Regards<span class="HOEnZb"><font color="#888888"><br>
Normando<br>
<b><i><span style="color:rgb(0,0,0);font-family:sans-serif;font-size:13px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:19.200000762939453px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;display:inline!important;float:none;background-color:rgb(255,255,255)"></span></i></b>
</font></span></div>
<br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br></div>