<div dir="ltr">Thanks<br><div class="gmail_extra"><br><div class="gmail_quote">On 11 June 2013 20:02, Anthony Minessale <span dir="ltr"><<a href="mailto:anthony.minessale@gmail.com" target="_blank">anthony.minessale@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Probably 1 is the path of least resistance.<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
<div><div class="h5">On Tue, Jun 11, 2013 at 9:57 AM, Richard Brady <span dir="ltr"><<a href="mailto:rnbrady@gmail.com" target="_blank">rnbrady@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi guys<div><br></div><div>A variable (e.g. liberal_dtmf) which has an underlying channel flag (e.g. CF_LIBERAL_DTMF) or some other internal representation or associated state can only be set at the beginning of the channel's lifetime, i.e. at the start of the call. </div>
<div><br></div><div>What is the best place to add custom code to allow this to happen for a particular variable while the call is in progress?</div><div><br></div><div>1. With a variable-specific command (e.g. "uuid_liberal_dtmf <uuid> true")</div>
<div><br></div><div>2. By modifying uuid_setvar to carry out some custom logic</div><div><br></div><div>3. With the addition of a new generic command, e.g. uuid_setvar_deep, which could serve as a single point for folks to add their custom code, and to return an error for any variable which is not explicitly supported. </div>
<div><br></div><div>Any thoughts?</div><div><br></div><div>Regards,</div><div>Richard</div><div><br></div></div></div></div></blockquote></div></div></blockquote></div></div></div>