[test-results] [Bamboo] No agents to build plan Asterisk Testing - Asterisk 1.8 Branch - Asterisk 1.8 CentOS 6 32-Bit

Bamboo bamboo at asterisk.org
Mon Sep 17 09:24:06 CDT 2012


-------------------------------------------------------------------------------
TESTING-ASTERISK18BRANCH-AST18CENTOS32-390 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------

http://bamboo.asterisk.org/browse/TESTING-ASTERISK18BRANCH-AST18CENTOS32/log

--------------
Code Changes
--------------
mjordan (373061):

>Resolve memory leaks in TLS initialization and TLS client connections
>
>This patch resolves two sources of memory leaks when using TLS in Asterisk:
>1) It removes improper initialization (and multiple re-initializations) of
>   portions of the SSL library.  Asterisk calls SSL_library_init and
>   SSL_load_error_strings during SSL initialization; collectively this
>   obviates the need for calling any of the following during initialization
>   or client connection handling:
>   * ERR_load_crypto_strings (handled by SSL_load_error_strings)
>   * OpenSSL_add_all_algorithms (synonym for SSL_library_init)
>   * SSLeay_add_ssl_algorithms (synonym for SSL_library_init)
>2) Failure to completely clean up all memory allocated by Asterisk and by
>   the SSL library for TLS clients.  This included not freeing the SSL_CTX
>   object in the SIP channel driver, as well as not clearing the error
>   stack when the TLS client exited.
>
>Note that these memory leaks were found by Thomas Arimont, and this patch
>was essentially written by him with some minor tweaks.
>
>(closes issue AST-889)
>Reported by: Thomas Arimont
>Tested by: Thomas Arimont
>patches:
>  (bugAST-889.patch) by Thomas Arimont (license 5525)
>
>Review: https://reviewboard.asterisk.org/r/2105
>
>

rmudgett (373090):

>Made companding law for SS7 calls only determined by SS7 signaling type.
>
>For SS7, the companding law for a call was chosen inconsistently depending
>upon ss7type (ITU vs ANSI) and the DAHDI companding default (T1 vs E1).
>For incoming calls, the companding law was determined by ss7type.  For
>outgoing calls, the companding law was determined by the DAHDI default.
>With the wrong combination you would get A-law/u-law conflicts.  An
>A-law/u-law conflict sounds like bad static on the line.
>
>SS7 ITU  signaling with E1 line: ok
>SS7 ITU  signaling with T1 line: noise
>SS7 ANSI signaling with E1 line: noise
>SS7 ANSI signaling with T1 line: ok
>
>* Fix the companding law used to be determined by the SS7 signaling type
>only.
>


--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20120917/34a33c01/attachment.htm>


More information about the Test-results mailing list