On Tue, Dec 4, 2012 at 4:08 PM, David M. Lee <span dir="ltr"><<a href="mailto:dlee@digium.com" target="_blank">dlee@digium.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div class="im"><div>On Dec 4, 2012, at 1:23 PM, Tim Ringenbach wrote:</div><br><blockquote type="cite"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium">This is supposed to be a higher level interface, right? How about guidelines about what's taboo to it.<div>
<br></div><div>Will you be able to use it to direct call/access any of: channel variables, global variables, functions that don't require a channel, functions that require a channel, applications, agi commands, cli commands, manager commands or manager events?</div>
<div><br></div><div>I suspect the answer might be "no", to all of those.</div></span></blockquote><div><br></div></div><div>Pretty much. With an API, what you leave out is as important as what you put in.</div></div>
</div></blockquote><div><br></div><div>So, how will the API accomplish things like logging an agent into a queue, or redirecting to voicemail, or more exotic things like running an Echo test, or playing a telezapper tone? Or asked another way, which use cases aren't in scope of this API?</div>
<div><br></div><div>One frustation I've had in the past, is realizing whatever it is I'm trying to do, I need to use another interface to accomplish it. Most commonly, I'm writing an AGI script, and find myself needing to do something only the AMI can do. But I've seen other odd combinations too, e.g. I've seen people resort to using System(asterisk -rx 'some command') from the dialplan.</div>
<div><br></div><div>But it sounds like you're going to be exposing the Stasis-core API to the manager, so at least I should never have to connect to both the AMI and Stasis to do something.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div class="im"><blockquote type="cite">I'm happy there is is finally going to be a UUID that track the channel that won't have the problem that the current uniqueids have with masquerades. But I do kind of wonder why a third channel identifier is being added, as opposed to fixing one of the two existing ones. (Maybe append the uuid to the channel name?) But maybe that was discussed at AstriDevCon.</blockquote>
<div><br></div></div><div>Yeah; my intention is to fix what's there rather than add a ReallyUniqueID field. I'm also realizing that it's going to take a bit of software archeology to figure out masquerades, uniqueid, etc. and come up with a plan for how to fix it.</div>
</div></div></blockquote><div><br></div><div>On the subject of uniqueids and channel masquerades, I can point you to my own email from a few years ago: <a href="http://lists.digium.com/pipermail/asterisk-dev/2010-June/044754.html">http://lists.digium.com/pipermail/asterisk-dev/2010-June/044754.html</a> and an old reviewboard patch <a href="https://reviewboard.asterisk.org/r/760/">https://reviewboard.asterisk.org/r/760/</a></div>
<div><br></div></div></div>