[asterisk-commits] mjordan: tag 1.8.8.0-rc5 r347862 - /tags/1.8.8.0-rc5/ChangeLog

[SVN commits to the Asterisk project]

Author: mjordan
Date: Fri Dec  9 08:58:33 2011
New Revision: 347862

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=347862
Log:
Updated ChangeLog

Modified:
    tags/1.8.8.0-rc5/ChangeLog

Modified: tags/1.8.8.0-rc5/ChangeLog
URL: http://svnview.digium.com/svn/asterisk/tags/1.8.8.0-rc5/ChangeLog?view=diff&rev=347862&r1=347861&r2=347862
==============================================================================
--- tags/1.8.8.0-rc5/ChangeLog (original)
+++ tags/1.8.8.0-rc5/ChangeLog Fri Dec  9 08:58:33 2011
@@ -1,3 +1,47 @@
+2011-12-09  Asterisk Development Team <asteriskteam at digium.com>
+
+	* Asterisk 1.8.8.0-rc5 Released.
+
+	* Fixed crash from orphaned MWI subscriptions in chan_sip
+
+	  This patch resolves the issue where MWI subscriptions are orphaned
+	  by subsequent SIP SUBSCRIBE messages.  When a peer is removed, either
+	  by pruning realtime SIP peers or by unloading / loading chan_sip, the
+	  MWI subscriptions that were orphaned would still be on the event engine
+	  list of valid subscriptions but have a pointer to a peer that no longer
+	  was valid.  When an MWI event would occur, this would cause a seg fault.
+
+	  (closes issue ASTERISK-18663)
+	  Review: https://reviewboard.asterisk.org/r/1610/
+
+	* Don't crash on INFO automon request with no channel
+
+	  AST-2011-014. When automon was enabled in features.conf, it was possible
+	  to crash Asterisk by sending an INFO request if no channel had been
+	  created yet.
+
+	  (closes issue ASTERISK-18805)
+
+	* Default to nat=yes; warn when nat in general and peer differ
+
+	  AST-2011-013.  It is possible to enumerate SIP usernames when the general and
+	  user/peer nat settings differ in whether to respond to the port a request is
+	  sent from or the port listed for responses in the Via header. In 1.4 and
+	  1.6.2, this would mean if one setting was nat=yes or nat=route and the other
+	  was either nat=no or nat=never. In 1.8 and 10, this would mean when one
+	  was nat=force_rport and the other was nat=no.
+
+	  In order to address this problem, it was decided to switch the default
+	  behavior to nat=yes/force_rport as it is the most commonly used option
+	  and to strongly discourage setting nat per-peer/user when at all
+	  possible.
+
+	  For more discussion of the issue, please see:
+	    http://lists.digium.com/pipermail/asterisk-dev/2011-November/052191.html
+
+	    (closes issue ASTERISK-18862)
+	    Review: https://reviewboard.asterisk.org/r/1591/
+
 2011-11-16  Asterisk Development Team <asteriskteam at digium.com>
 
 	* Asterisk 1.8.8.0-rc4 Released.