for what it's worth i think management of codec restrictions and requirements should really be the responsibility of the channel drivers alone. that said i do like the concept of having a individual context for each conference room and the advantages that could have down the line( more configuration options ;) )
<br><br>-anthony<br><br><br><div><span class="gmail_quote">On 3/21/07, <b class="gmail_sendername">Clod Patry</b> <<a href="mailto:cpatry@gmail.com">cpatry@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
hi guys,<br>Since, i didnt get any feedback on: <a href="http://lists.digium.com/pipermail/asterisk-dev/2007-January/025772.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.digium.com/pipermail/asterisk-dev/2007-January/025772.html
</a><br>post #2.<br><br> I'd like your feelings about that new structure.<br><br><br clear="all"><br>-- <br><span class="sg">Clod Patry </span><br>_______________________________________________<br>--Bandwidth and Colocation provided by
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://Easynews.com" target="_blank">Easynews.com</a> --<br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">
http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br><br></blockquote></div><br>