<div class="gmail_quote">On Tue, Jun 15, 2010 at 1:26 PM, Tilghman Lesher <span dir="ltr"><<a href="mailto:tlesher@digium.com">tlesher@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tuesday 15 June 2010 12:57:19 Jared Smith wrote:<br>
> ----- Original Message -----<br>
><br>
> > When using GLOBAL() function it looks like that querying is case<br>
> > sensitive, but reading no (as it overwrites the existing variable).<br>
> > This is inconsistent with normal channel variables which are always<br>
> > case insensitive:<br>
><br>
> I was under the impression that Asterisk channel variables were always case<br>
> sensitive... Have I missed a change along the way?<br>
<br>
</div>As far as I know, both global and channel variables are supposed to be case-<br>
sensitive, other than a few DEPRECATED builtin variables that have now been<br>
largely replaced with dialplan functions.<br>
<font color="#888888"><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#888888"><br></font></font></font></blockquote><div><br></div><div>As for as I know, they're both supposed to be case insensitive. I also can't seem to find anything in the asterisk docs that says one way or another. But <a href="http://www.voip-info.org/wiki/view/Asterisk+variables">http://www.voip-info.org/wiki/view/Asterisk+variables</a> states so, so maybe that's where I heard it. I'm pretty sure there exist dialplans that will break if you change it to be case sensitive.</div>
<div><br></div></div>