i realized that with writing Custom values to astDB.<br>But i dont understand why we could not change existing state.<br>Is that a possibility of writing a state to memory and not the astDB or multi-thread will cause severe damage?
<br><br><div class="gmail_quote">On Jan 16, 2008 6:44 AM, Kevin P. Fleming <<a href="mailto:kpfleming@digium.com">kpfleming@digium.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Clod Patry wrote:<br><br>> After a quick discussion with Russell on IRC, he told me the answers is<br>> pretty long why we can explicitly change a device state.<br>><br>> So let's start a discussion around this :)
<br><br></div>There's no discussion to be had; you can't change the state of a real<br>device, only virtual (custom ) devices. The device state of a *real*<br>device will be managed by the module that provides that device (channel
<br>driver, parking, etc.).<br><br>--<br>Kevin P. Fleming<br>Director of Software Technologies<br>Digium, Inc. - "The Genuine Asterisk Experience" (TM)<br><br>_______________________________________________<br>--Bandwidth and Colocation Provided by
<a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">
http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote></div><br><br clear="all"><br>-- <br>Clod Patry