<div class="gmail_quote">On Mon, Mar 24, 2008 at 5:21 PM, Watkins, Bradley <<a href="mailto:Bradley.Watkins@compuware.com">Bradley.Watkins@compuware.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>
<div class="Ih2E3d"><br><br> </div>Being able to pass variables around between systems is by *definition*<br>channel-specific, since the channel driver is the module responsible for<br>speaking a given protocol. Besdies, SIP already has (and has had for a<br>
long time) a method for doing this (SIP headers). So does ISDN, for<br>that matter (IEs).<br><br></blockquote>
<div>I stand corrected. This is, in effect, I guess, completing a feature set. It is just "catching" IAX up with the other channels. I have no problem with that at all. Honestly, I never thought about using SIP headers to pass variables. </div>
<div> </div>
<div>I see it as a good feature, I was just ticked that a patch that had been worked on for so long was killed only because it was channel specific, and then this patch gets added. I understand now that feature wise, this wasn't really adding anything, it was more or less completing the feature set, a feature that I was not aware of to begin with until now.</div>
<div> </div>
<div> </div></div>