What is the policy regarding Digium repositories in regards to updates? I only see Asterisk 1.8.7.2-1 despite this release note from yesterday. Does that take time to update even when there is a security update?<div><br></div>
<div>Thanks<br><br><div class="gmail_quote">On Fri, Dec 9, 2011 at 12:13 PM, Asterisk Development Team <span dir="ltr"><<a href="mailto:asteriskteam@digium.com">asteriskteam@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The Asterisk Development Team has announced the fifth release candidate of<br>
Asterisk 1.8.8.0. This release candidate is available for immediate download at<br>
<a href="http://downloads.asterisk.org/pub/telephony/asterisk/" target="_blank">http://downloads.asterisk.org/<u></u>pub/telephony/asterisk/</a><br>
<br>
The release of Asterisk 1.8.8.0-rc5 resolves several issues reported by the<br>
community and would have not been possible without your participation.<br>
Thank you!<br>
<br>
The following is a sample of the issues resolved in this release candidate:<br>
<br>
* Don't crash on INFO automon request with no channel<br>
<br>
AST-2011-014. When automon was enabled in features.conf, it was possible<br>
to crash Asterisk by sending an INFO request if no channel had been<br>
created yet.<br>
<br>
* Fixed crash from orphaned MWI subscriptions in chan_sip<br>
<br>
This patch resolves the issue where MWI subscriptions are orphaned<br>
by subsequent SIP SUBSCRIBE messages.<br>
<br>
* Default to nat=yes; warn when nat in general and peer differ<br>
<br>
AST-2011-013. It is possible to enumerate SIP usernames when the general and<br>
user/peer nat settings differ in whether to respond to the port a request is<br>
sent from or the port listed for responses in the Via header. In 1.4 and<br>
1.6.2, this would mean if one setting was nat=yes or nat=route and the other<br>
was either nat=no or nat=never. In 1.8 and 10, this would mean when one<br>
was nat=force_rport and the other was nat=no.<br>
<br>
In order to address this problem, it was decided to switch the default<br>
behavior to nat=yes/force_rport as it is the most commonly used option<br>
and to strongly discourage setting nat per-peer/user when at all<br>
possible.<br>
<br>
For a full list of changes in this release candidate, please see the ChangeLog:<br>
<br>
<a href="http://downloads.asterisk.org/pub/telephony/asterisk/ChangeLog-1.8.8.0-rc5" target="_blank">http://downloads.asterisk.org/<u></u>pub/telephony/asterisk/<u></u>ChangeLog-1.8.8.0-rc5</a><br>
<br>
Thank you for your continued support of Asterisk!<br><font color="#888888">
<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>
</font></blockquote></div><br></div>