<br><br><div class="gmail_quote">2012/10/11 Kinsey Moore <span dir="ltr"><<a href="mailto:kmoore@digium.com" target="_blank">kmoore@digium.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 10/11/2012 10:31 AM, Olivier wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/10/11 Kinsey Moore <<a href="mailto:kmoore@digium.com" target="_blank">kmoore@digium.com</a> <mailto:<a href="mailto:kmoore@digium.com" target="_blank">kmoore@digium.com</a>>><div class="im"><br>
<br>
Hi Olivier,<br>
>My questions are:<br>
>1. Is it possible to configure Asterisk 1.8 (I'm using 1.8.12 but<br>
I can<br>
>upgrade to 1.8.17 if, and only if, necessary) so that ADDMEMBER<br>
entries in<br>
>queue_log refers to member name instead of member location ?<br>
>If positive how should this be configured ?<br>
<br>
This feature is not present in Asterisk 1.8.17. It was only<br>
committed to trunk since it is a change in behavior. It is in the<br>
Asterisk 11 branch, betas, and release candidate.<br>
<br>
<br>
Now I'm seeing the related commit in Asterisk 11 changelogs (I closely looked at 1.8 changelog but I didn't looked at Asterisk 11 branch).<br>
I don't know if the corresponding patch is invasive or not but having the option to change Asterisk 1.8 behaviour would have been much appreciated.<br>
<br>
Is there any change to have this option considered ?<br>
</div></blockquote>
It is highly unlikely that this feature will go into an existing branch. In general, new features are not committed to released branches.<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br>
Yes I agree that new features should be committed to new versions but in this specific case, current 1.8 behaviour is all Queue events but two (ADDMEMBER and REMOVEMEMBER) are using members name for logging into queue_log.<br>
<br>So, to me, queue_log content is currently inconsistent.<br><br>But as I also understand current installs might already have found a way around (what I rate as a bug), maybe a configuration option would be acceptable for all.<br>
<br>What do you think ?<br><br><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="HOEnZb"><font color="#888888">
<br>
<br>
Kinsey Moore</font></span><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>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/<u></u>mailman/listinfo/asterisk-<u></u>users</a><br>
</div></div></blockquote></div><br>