The Asterisk Development Team has announced release candidates of Asterisk for versions 1.4.35 and 1.6.2.11. These releases are available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/
These release candidates address issues that were reported by the community and resolved since the last round of bug fix releases.
The following is a sampling of issues resolved in these release candidates:
- Send DialPlanComplete as a response, not as a separate event.
(Closes issue #17504. Reported, patched by rrb3942) - Ensure channel placed into MeetMe in ringing state is properly hung up.
(Closes issue #15871. Reported, patched by Ivan) - Fix a problem with RFC 2833 DTMF not being accepted.
(Closes issue #17571. Reported by mdeneen. Tested by richardf, maxochoa, JJCinAZ) - Add option to not do a call forward on a 482 Loop Detected.
(Reviewboard: https://reviewboard.asterisk.org/r/764/ ) - Fix logging message for a stale nonce.
(Closes issue #17582. Reported, patched by kenner) - Fix some issues related to dynamic feature groups in features.conf
(Closes issue #17589. Reported,tested by lmadsen. Patched,tested by russell) - cdr_pgsql does not detect when a table is found. Add an ERROR message letting you know when a failure to get the columns from the database exists.
(Closes issue #17478. Reported, patched by kobaz) - Delete IMAP messages in reverse order to ensure reordering after each expunge does not cause deletion of the wrong message.
(Closes issue #16350. Reported by noahisaac. Patched by tilghman)
For a full list of changes in the current release candidates, please see the ChangeLogs:
- http://downloads.asterisk.org/pub/telephony/asterisk/ChangeLog-1.4.35-rc1
- http://downloads.asterisk.org/pub/telephony/asterisk/ChangeLog-1.6.2.11-rc1
Issues found in any of these release candidates should be reported to the Asterisk issue tracker at https://issues.asterisk.org
Thank you for your continued support of Asterisk!
