<div class="gmail_quote">On Fri, May 11, 2012 at 8:31 AM, Matthew Jordan <span dir="ltr"><<a href="mailto:mjordan@digium.com" target="_blank">mjordan@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
In your particular case, if I were writing a system that wanted to associate<br>
a created channel with an Originate Action, after I issue the Originate,<br>
I'd listen for a NewChannel event. If that NewChannel event specified a<br>
channel that was created in the context I specified and with a<br>
technology/extension that I specified, I'd set that as the channel I just<br>
asked to be created. From there on, subsequent events (VarSet, NewExten,<br>
Hangup, etc.) that are associated with that channel will contain a Channel:<br>
header with that value.<br><br></blockquote><div><br>Isn't that likely to cause race issues if for instance he Originates 30 calls all at the same time? I would think a better approach would be to set a unique channel variable for each originated call and track based on that?<br>
</div></div>-- <br>Thanks,<br>--Warren Selby, dCAP<br><a href="http://www.selbytech.com" target="_blank">http://www.SelbyTech.com</a><br><br>