<div dir="ltr">Ahhhhhh...</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 18, 2014 at 1:32 PM, Kaloyan Kovachev <span dir="ltr"><<a href="mailto:kkovachev@varna.net" target="_blank">kkovachev@varna.net</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I meant that for "accessing bridge configuration for a Legacy (Dial, Queue, FollowMe)" from your other email<span class=""><br>
<br>
On 2014-12-18 13:26, Nir Simionovich wrote:<br>
<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
In deed, that is interesting - but truly stirs away from ARI - not something that I'm trying to do.<br>
<br>
On Thu, Dec 18, 2014 at 1:00 PM, Kaloyan Kovachev <<a href="mailto:kkovachev@varna.net" target="_blank">kkovachev@varna.net</a>>wrote: Hi,<br>
<br>
On 2014-12-18 01:01, Nir Simionovich wrote:<br>
<br>
Let's try to stick to the tech for now and answer the first two questions:<br>
<br>
1. Is there a way to obtain the information in ast_bridge_config for each of the iterated bridges?<br>
2. Is there a way to manipulate the configuration of the bridge, via modifying the associated bridge configuration in real time?<br>
<br>
Nir You may take a look at my old RTCC patch for Dial() [1]:<br>
In the last version [2] I have ended with adding the bridge_config and both channels to a data store, which is accessed from a scheduled callback and modifies the call limit.<br>
Once you have the data store attached to the channel it is easy to access it from a hook or another thread/app<br>
<br></span>
[1] <a href="https://issues.asterisk.org/jira/browse/ASTERISK-6175" target="_blank">https://issues.asterisk.org/<u></u>jira/browse/ASTERISK-6175</a> [1]<br>
[2] <a href="https://issues.asterisk.org/jira/secure/attachment/40666/rtcc_trunk_327742.diff" target="_blank">https://issues.asterisk.org/<u></u>jira/secure/attachment/40666/<u></u>rtcc_trunk_327742.diff</a> [2]<br>
<br>
--<br>
______________________________<u></u>______________________________<u></u>_________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> [3] --<span class=""><br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
</span><a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/<u></u>mailman/listinfo/asterisk-dev</a> [4]<br>
</blockquote>
<br>
<br>
<br>
Links:<br>
------<span class=""><br>
[1] <a href="https://issues.asterisk.org/jira/browse/ASTERISK-6175" target="_blank">https://issues.asterisk.org/<u></u>jira/browse/ASTERISK-6175</a><br>
[2] <a href="https://issues.asterisk.org/jira/secure/attachment/40666/rtcc_trunk_327742.diff" target="_blank">https://issues.asterisk.org/<u></u>jira/secure/attachment/40666/<u></u>rtcc_trunk_327742.diff</a><br></span>
[3] <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a><br>
[4] <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/<u></u>mailman/listinfo/asterisk-dev</a><div class="HOEnZb"><div class="h5"><br>
<br>
-- <br>
______________________________<u></u>______________________________<u></u>_________<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/<u></u>mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div></div>