- Mar 12, 2018
-
-
Jenkins2 authored
-
- Mar 11, 2018
-
-
Jenkins2 authored
-
- Mar 09, 2018
-
-
Jenkins2 authored
-
- Mar 08, 2018
-
-
Jenkins2 authored
-
Kevin Harwell authored
-
Jenkins2 authored
-
Jenkins2 authored
-
- Mar 07, 2018
-
-
Jenkins2 authored
-
Richard Mudgett authored
Doing a 'make clean', 'make distclean', or 'make dist-clean' gets errors about an invalid shell option: "/bin/sh: 0: Illegal option -". The clean targets do not include the makeopts file which defines GREP and LDCONFIG because the file may not exist and the distclean/dist-clean targets will delete it anyway. ASTERISK-27715 Change-Id: I33d40acdb03862bc89aeb6fb1ff497894a8ea7f5
-
Ross Beer authored
ASTERISK-27554 Change-Id: If61c7faab7d2fa1031c056ed6268fe928e2391cf
-
Sungtae Kim authored
Fixed wrong voicemail mailbox reference for Action: VoicemailUsersList. ASTERISK-27703 Change-Id: Ie6578ad80bba2bfaf34b84f0be978f59045ce6cd
-
Alexander Traud authored
When HAVE_GETHOSTBYNAME_R_5 was set by the script ./configure, GCC 7.3.0 found an unused variable. Actually, the variable was used (set to a dummy value) but the compiler optimization might have removed that. Instead, this change ensures that the variable 'res' is only used when it is really required. Change-Id: Ic3ea23ccf84ac4bc2d501b514985b989030abab5
-
Corey Farrell authored
astosp.h is leftover from when logic was split between app_osplookup and res_osp. All logic was moved into app_osplookup by 109737eb in 2006, but astosp.h remained. This moves the remaining defines into app_osplookup and deletes astosp.h. Change-Id: I0a6c4debd7c9543b608520b1765abfa4fab7b2fd
-
Jean Aunis authored
The "ptime" SDP parameter received in a SIP response was not honoured. Moreover, in the abscence of this "ptime" parameter, locally configured framing was lost during response processing. This patch systematically stores the framing information in the ast_rtp_codecs structure, taking it from the response or from the configuration as appropriate. ASTERISK-27674 Change-Id: I828a6a98d27a45a8afd07236a2bd0aa3cbd3fb2c
-
- Mar 06, 2018
- Mar 05, 2018
-
-
Jenkins2 authored
-
Joshua Colp authored
-
Jenkins2 authored
-
Jenkins2 authored
-
Jenkins2 authored
-
Jenkins2 authored
-
Alexander Traud authored
ASTERISK-27719 Change-Id: I230c5f9f316b2e9465c093c13580f72ebbaf67a7
-
Jenkins2 authored
-
Alexander Traud authored
ASTERISK-27716 Change-Id: I52525e35e1620341272219911d054a1e3d3ec01e
-
Alexander Traud authored
ASTERISK-27715 Reported by: Corey Farrell Change-Id: I0d6d9572d1352dc7ad30c9917173f1e980d8c938
-
- Mar 03, 2018
-
-
Alexander Traud authored
ASTERISK-27714 Reported by: John Nemeth Change-Id: I1b84a89315a5f61222123d21bf35c59224da8990
-
Alexander Traud authored
ASTERISK-27713 Change-Id: I90c769e3c7f8c26de8a3af11335862cec15a1b22
-
Alexander Traud authored
ASTERISK-27712 Reported by: Joerg Sonnenberger, D'Arcy Cain Change-Id: Idf1c9d43617a3e13028b95b313415903d80ef807
-
Alexander Traud authored
ASTERISK-27711 Change-Id: Idc9194035b2958b99f6b01eb5b438d45a074565b
-
- Mar 02, 2018
-
-
Alexander Traud authored
ASTERISK-27710 Change-Id: I4c777e41b31d4415bbe21cb435ad47b43ebb5467
-
Alexander Traud authored
ASTERISK-27709 Reported by: John Nemeth Change-Id: I11b1ae8fd404c04066f1458f5d71f9536359d58d
-
- Mar 01, 2018
- Feb 28, 2018
-
-
Richard Mudgett authored
The pool cache gets in the way of finding use after free errors of memory pool contents. Tools like valgrind and MALLOC_DEBUG don't know when a pool is released because it gets put into the cache instead of being freed. * Added the "cache_pools" option to pjproject.conf. Disabling the option helps track down pool content mismanagement when using valgrind or MALLOC_DEBUG. The cache gets in the way of determining if the pool contents are used after free and who freed it. To disable the pool caching simply disable the cache_pools option in pjproject.conf and restart Asterisk. Sample pjproject.conf setting: [startup] cache_pools=no * Made current users of the caching pool factory initialization and destruction calls call common routines to create and destroy cached pools. ASTERISK-27704 Change-Id: I64d5befbaeed2532f93aa027a51eb52347d2b828
-
- Feb 26, 2018
-
-
Jenkins2 authored
-
- Feb 25, 2018
-
-
Corey Farrell authored
Change-Id: I459dc320a8c9452a01eed6f403d786741587c890
-
Michael Cargile authored
Between Asterisk 11 and Asterisk 13 there was a significant increase in the number of AST_FRAME_NULL frames being processed by app_amd.c's main loop. Each AST_FRAME_NULL frame was being counted as 100ms towards the total time and silence. This may have been accurate when app_amd.c was orginally added, but it is not in Asterisk 13. As such the total analysis time and silence calculations were way off effectively breaking app_amd.c * Additional debug messages were added * AST_FRAME_NULL are now ignored ASTERISK-27610 Change-Id: I18aca01af98f87c1e168e6ae0d85c136d1df5ea9
-