32329 Commits (cc59e21409b22c109560b92a6073bffc30006f7c)

 

All Branches   

Search

Author	SHA1	Message	Date
George Joseph	be8d41bd24	CI: Add cleanWs to cleanup steps in jenkinsfiles ... We're at the point where there are enough Jenkins jobs for Asterisk branches than even cleaned checkouts of Asterisk will add up to more disk space than is available on the in-memory workspace mount. Since we archive all relevent artifacts anyway, there's no need to keep the workspace around after the job finishes, whether it succeeds or fails. Change-Id: I1cd3b73ebb045a987df0f62526d152a510210c39	6 years ago
George Joseph	2ba7d3c2b9	Merge "CI: Add install-headers to the install make targets"	6 years ago
George Joseph	960e6dd065	Merge "README.md: Update year"	6 years ago
George Joseph	5167555f8e	Merge "sched: Don't allow ast_sched_del to deadlock ast_sched_runq from same thread"	6 years ago
George Joseph	8b88994b18	CI: Add install-headers to the install make targets ... The testsuite actually needs the headers installed to run it's self_test. Change-Id: Ice41d331131b876ad4a9c056085fe6aac34b32b2	6 years ago
George Joseph	b565fd9cf8	Merge "Build: Separate header install/uninstall"	6 years ago
Joshua Colp	54c1645c29	Merge "manager: Log AMI actions"	6 years ago
Walter Doekes	3c6f11992b	sched: Don't allow ast_sched_del to deadlock ast_sched_runq from same thread ... When fixing ASTERISK~24212, a change was done so a scheduled callback could not be removed while it was running. The caller of ast_sched_del would have to wait. However, when the caller of ast_sched_del is the callback itself (however wrong this might be), this new check would cause a deadlock: it would wait forever for itself. This changeset introduces an additional check: if ast_sched_del is called by the callback itself, it is immediately rejected (along with an ERROR log and a backtrace). Additionally, the AST_SCHED_DEL_UNREF macro is adjusted so the after-ast_sched_del-refcall function is only run if ast_sched_del returned success. This should fix the following spurious race condition found in chan_sip: - thread 1: schedule sip_poke_peer_now (using AST_SCHED_REPLACE) - thread 2: run sip_poke_peer_now - thread 2: blank out sched-ID (too soon!) - thread 1: set sched-ID (too late!) - thread 2: try to delete the currently running sched-ID After this fix, an ERROR would be logged, but no deadlocks (in do_monitor) nor excess calls to sip_unref_peer(peer) (causing double frees of rtp_instances and other madness) should occur. (Thanks Richard Mudgett for reviewing/improving this "scary" change.) Note that this change does not fix the observed race condition: unlocked access to peer->pokeexpire (and potentially other scheduled items in chan_sip), causing AST_SCHED_DEL_UNREF to look at a changing id. But it will make the deadlock go away. And in the observed case, it will not have adverse affects (like memory leaks) because the scheduled item is removed through a different path. ASTERISK-28282 Change-Id: Ic26777fa0732725e6ca7010df17af77a012aa856	6 years ago
George Joseph	c781806e26	Build: Separate header install/uninstall ... Asterisk headers are no longer installed and uninstalled automatically when performing a "make install" or a "make uninstall". To install/uninstall the headers, use "make install-headers" and "make uninstall-headers". The headers also continue to be uninstalled when performing a "make uninstall-all". Also corrects an issue where /usr/include/asterisk.h was never being removed at all. Change-Id: Ia7399f3a0203a4825fc4a9f43b9034dae9a2b643	6 years ago
Kevin Harwell	ba25038fd5	manager: Log AMI actions ... When manager debugging is turned on, this patch makes it so incoming AMI actions are now also logged. Change-Id: I8047524510e7ac97d99482b2448f8e368f29cd47	6 years ago
Joshua Colp	2feac1d361	res_rtp_asterisk: Move where DTLS MTU variable is defined. ... The DTLS MTU variable is not dependent on pjproject and should not exist in its block. Change-Id: I7e97d64dc192f2ac81bfe2b72b8229d321c7d026	6 years ago
Kevin Harwell	d8c207427d	Merge "app_voicemail: Remove dependency on the stasis cache"	6 years ago
Kevin Harwell	857ee76f4b	Merge "MWI: Update modules that subscribe to MWI to use new API calls"	6 years ago
Kevin Harwell	03cc8d16a3	Merge "mwi: Update the MWI core to use stasis_state API"	6 years ago
Kevin Harwell	49d4bd5c78	Merge "stasis_state: Make unsubscribes NULL tolerant"	6 years ago
Friendly Automation	7f76479b7f	Merge "chan_sip: Handle invalid SDP answer to T.38 re-invite"	6 years ago
George Joseph	3c520147e1	res_pjsip_messaging: Check for body in in-dialog message ... We now check that a body exists and it has a length > 0 before attempting to process it. ASTERISK-28447 Reported-by: Gil Richard Change-Id: Ic469544b22ab848734636588d4c93426cc6f4b1f	6 years ago
Francesco Castellano	8438d19b81	chan_sip: Handle invalid SDP answer to T.38 re-invite ... The chan_sip module performs a T.38 re-invite using a single media stream of udptl, and expects the SDP answer to be the same. If an SDP answer is received instead that contains an additional media stream with no joint codec a crash will occur as the code assumes that at least one joint codec will exist in this scenario. This change removes this assumption. ASTERISK-28465 Change-Id: I8b02845b53344c6babe867a3f0a5231045c7ac87	6 years ago
Kevin Harwell	c93c579190	app_voicemail: Remove dependency on the stasis cache ... app_voicemail utilized the stasis cache when polling mailboxes for MWI. This caused a memory leak (items were not being appropriately removed from the cache), and subsequent slowdown in system processing. This patch removes the stasis cache dependency, thus alleviating the memory leak. It does this by utilizing the new MWI API that better manages state lifetime. ASTERISK-28443 ASTERISK-27121 Change-Id: Ie89fedaca81ea1fd03d150d9d3a1ef3d53740e46	6 years ago
Kevin Harwell	9637e1dfdc	MWI: Update modules that subscribe to MWI to use new API calls ... The MWI core recently got some new API calls that make tracking MWI state lifetime more reliable. This patch updates those modules that subscribe to specific MWI topics to use the new API. Specifically, these modules now subscribe to both MWI topics and MWI state. ASTERISK-28442 Change-Id: I32bef880b647246823dbccdf44a98d384fcabfbd	6 years ago
Kevin Harwell	b31ac83900	mwi: Update the MWI core to use stasis_state API ... ** Note ** This patch is meant to be the minimum needed in order for the MWI core to use the now underlying stasis_state module. As such it does not completely remove its reliance on the stasis_cache. Doing so has allowed current consumers to not have to change, and update those code paths for this patch. When time allows, subsequent patches can/will be made to those consumers to take advantage of some of the new MWI API included here. Thus, eventually and ultimately removing MWI dependency on the stasis_cache. ** End Note ** This patch makes it so the MWI core now takes advantage of the new stasis_state API. Consumers of MWI should no longer need to depend upon stasis topic pooling, and the stasis cache directly. Similar functionality and implementation details have now been pushed into the stasis_state module. However, all MWI state should be accessed via the MWI API itself. As such a few new methods, and constructs have been added to the MWI core that facilitate consumer publishing, subscribing, and iterating over MWI state data. * ast_mwi_subscriber * Created via ast_mwi_add_subscriber, a subscriber subscribes to a given mailbox in order to receive updates about the given mailbox. Adding a subscriber will create the underlying topic, and associated state data if those do not already exist for it. The topic, and last known state data is guaranteed to exist for the lifetime of the subscriber. * ast_mwi_publisher * Before publishing to a particular topic a publisher should be created. This can be achieved by using ast_mwi_add_publisher. Publishing to a mailbox should then be done using one of the MWI publish functions. This ensures the message is published to the appropriate topic, and the last known state is maintained. * ast_mwi_observer * Add an observer in order to watch for particular MWI module related events. For instance if a submodule needs to know when a subscription is added to any mailbox an observer can be added to watch for that. * other * Urgent message count is now part of the published MWI state object. Also state can be iterated over using defined callbacks. ASTERISK-28442 Change-Id: I93f935f9090cd5ddff6d4bc80ff90703c05cf776	6 years ago
Kevin Harwell	83c6ebbae8	stasis_state: Make unsubscribes NULL tolerant ... Regular stasis unsubscribes can handle NULL subscription objects. This patch makes it so stasis state unsubscribes handles NULL's as well. ASTERISK-28442 Change-Id: Ic3648e8df043a85b77cff085e9ff10356028e479	6 years ago
Rodrigo Ramírez Norambuena	64a908f897	README.md: Update year ... Change-Id: I746fb94d112c7d797e206bca0fd1e13fcd26bae3	6 years ago
Friendly Automation	99addaff69	Merge "stasis_state: Add new stasis_state module"	6 years ago
Joshua Colp	c080f01d75	Merge "chan_dahdi.c: crash in chan_dahdi"	6 years ago
Chris-Savinovich	0e669712e2	chan_dahdi.c: crash in chan_dahdi ... Fixes a crash in chan_dahdi occurring on 32-bit systems. A previous patch introduced a variable of type unassigned long long which is 64-bits. Casting it as 'ast_json_int_t' along with JSON type 'I' makes it work with 32-bit systems. ASTERISK-28457 Change-Id: I9cef6b5f2d826fc5c93f2f6a1c997c4e3e6c93fe	6 years ago
Kevin Harwell	93936e367d	res_pjsip_sdp_rtp: Remove unused variable ... The variable 'endpoint_caps' in function 'set_caps' is not used, so remove. ASTERISK-28458 Change-Id: Ia8766d05a0738aecb29dd018302c2dafca5cab34	6 years ago
George Joseph	ad720adda7	Merge "app_voicemail.c: Build all three variants for app_voicemail at the same time"	6 years ago
George Joseph	4d0cc7bbc4	Merge "tcptls.c: Add peer hostname and port to some error messages"	6 years ago
Friendly Automation	7034bb1b21	Merge "pjproject_bundled: Add peer information to most SSL/TLS errors"	6 years ago
Kevin Harwell	363bafc29e	stasis_state: Add new stasis_state module ... This new module describes an API that can be thought of as a combination of stasis topic pools, and caching. Except, hopefully done in a more efficient and less memory "leaky" manner. The API defines methods, and data structures for managing, and tracking published message state through stasis. By adding a subscriber or publisher, consumers can more easily track the lifetime of the contained state. For instance, when no more publishers and/or subscribers have need of the topic, and associated state its data is removed from the managed container. * stasis_state_manager * The manager stores and well, manages state data. Each state is an association of a unique stasis topic, and the last known published stasis message on that topic. There is only ever one managed state object per topic. For each topic all messages are forwarded to an "all" topic also maintained by the manager. * stasis_state_subscriber * Topic and state can be created, or referenced within the manager by adding a stasis_state_subscriber. When adding a subscriber if no state currently exists new managed state is immediately created. If managed state already exists then a new subscriber is created referencing that state. The managed state is guaranteed to live throughout the subscriber's lifetime. State is only removed from the manager when no other entities require it. * stasis_state_publisher * Topic and state can be created, or referenced within the manager by also adding a stasis_state_publisher. When adding a publisher if no state currently exists new managed state is created. If managed state already exists then a new publisher is created referencing that state. The managed state is guaranteed to live throughout the publisher's lifetime. State is only removed from the manager when no other entities require it. * stasis_state_observer * Some modules may wish to watch for, and react to managed state events. By registering a state observer, and implementing handlers for the desired callbacks those modules can do so. * other * Callbacks also exist that allow consumers to iterate over all, or some of the managed state. ASTERISK-28442 Change-Id: I7a4a06685a96e511da9f5bd23f9601642d7bd8e5	6 years ago
Chris-Savinovich	6b1f6ea2c4	app_voicemail.c: Build all three variants for app_voicemail at the same time ... Changes made to apps/Makefile to optionally build all three app_voicemail variations at the same time: 1) file (default), 2) odbc, and 3) imap. This functionality was requested by users. modules.conf.sample warns the user to make sure only one voicemail is loaded at a time. Change-Id: Iba3cd8ffb4b7e8b1c64a11dd383e1eafcd3ed0e7	6 years ago
Kevin Harwell	09508e0671	Merge "pjproject: Update to 2.9 release"	6 years ago
George Joseph	c2ffb004aa	tcptls.c: Add peer hostname and port to some error messages ... Where possble, hostname and port has been added to error messages, mostly on the server side. ASTERISK-26006 Reported by: Oleksandr Natalenko Change-Id: Iff4f897277bc36ce8c5b493b71d0a4a7b74e62f0	6 years ago
George Joseph	8b3ee7fe61	pjproject_bundled: Add peer information to most SSL/TLS errors ... Most SSL/TLS error messages coming from pjproject now have either the peer address:port or peer hostname, depending on what was available at the time and code location where the error was generated. ASTERISK-28444 Reported by: Bernhard Schmidt Change-Id: I41770e8a1ea5e96f6e16b236692c4269ce1ba91e	6 years ago
Friendly Automation	2f29c375c1	Merge "res/ari/resource_channels.c: Added hangup reason code for channels"	6 years ago
Kevin Harwell	cfdb567425	Merge "app_amd: issue with silence suppression fixed"	6 years ago
sungtae kim	613a335de5	res/ari/resource_channels.c: Added hangup reason code for channels ... Currently, DELETE /ari/channels/<channelID> supports only few hangup reasons. It's good enough for simple use, but when it needs to set the detail reason, it comes challenges. Added reason_code query parameter for that. ASTERISK-28385 Change-Id: I1cf1d991ffd759d0591b347445a55f416ddc3ff2	6 years ago
George Joseph	ccbc83fed7	Merge "sig_pri: Address gcc9 issues"	6 years ago
Dan Cropp	e52fbae00f	chan_pjsip: Transmit REFER waits for the REFER result setting TRANSFERSTATUS ... Previously, when a Transfer (REFER) was performed, chan_pjsip would set the TRANSFERSTATUS to SUCCESS when the REFER was queued up. This did not reflect a successful/unsuccessful transfer the way chan_sip did. Added a callback module to process the refer subscription information. Now depends on res_pjsip_pubsub so call transfer progress can be monitored and reported ASTERISK-26968 #close Reported-by: Dan Cropp Change-Id: If6c27c757c66f71e8b75e3fe49da53ebe62395dc	6 years ago
George Joseph	c3adb60dac	Merge "CI: New way to determnine libdir"	6 years ago
George Joseph	619a50b7aa	Merge "res_fax: gateway sends T.38 request to both endpoints if V.21 detected"	6 years ago
George Joseph	13e89d372b	sig_pri: Address gcc9 issues ... A few more format truncation issues addressed. Change-Id: I047f373169caaca0eec4889d3c0e5e10f130017a	6 years ago
George Joseph	3a51cdad18	Merge "translate.c do not log WARNING on empty audio frame"	6 years ago
Friendly Automation	0a54b6c26a	Merge "app_confbridge: Attended transfer event fixup"	6 years ago
Nasir Iqbal	29bc7cf6b3	app_amd: issue with silence suppression fixed ... Now AMD algorithm will not ignore AST_FRAME_NULL, As I think using manual wait time instead of `framelength` is enough to fix timeout / TOOLONG issue. ASTERISK-28419 #close Change-Id: I16ea2d6295bc99b975e8c092e5f9fbd9214debdb	6 years ago
Alexei Gradinari	f414ca069c	res_fax: gateway sends T.38 request to both endpoints if V.21 detected ... According T.38 Gateway 'Use case 3' https://wiki.asterisk.org/wiki/display/AST/T.38+Gateway T.38 Gateway should send T.38 negotiation request to called endpoint if FAX preamble (using V.21 detector) generated by called endpoint. But it does not, because fax_gateway_detect_v21 constructs T.38 negotiation request, but forwards it only to other channel, not to the channel on which FAX preamble is detected. Some SIP endpoints could be improperly configured to rely on the other side to initiate T.38 re-INVITEs. With this patch the T.38 Gateway tries to negotiate with both sides by sending T.38 negotiation request to both endpoints supported T.38. Change-Id: I73bb24799bfe1a48adae9c034a2edbae54cc2a39	6 years ago
George Joseph	0ba52ce3cf	CI: New way to determnine libdir ... We were using the presence of /usr/lib64 to determine where shared libraries should be installed. This only existed on Redhat based systems and was safe. If it existed, use it, otherwise use /usr/lib. Unfortunately, Ubuntu 19 decided to create a /usr/lib64 BUT NOT INCLUDE IT IN THE DEFAULT ld.so.conf. So if anything is installed there, it won't work. The new method, just looks for $ID in /etc/os-release and if it's centos or fedora, uses /usr/lib64 and if ubuntu, uses /usr/lib. NOTE: This applies only to the CI scripts. Normal asterisk build and install is not affected. Change-Id: Iad66374b550fd89349bedbbf2b93f8edd195a7c3	6 years ago
Alexei Gradinari	e3866cb714	translate.c do not log WARNING on empty audio frame ... There is WARNING "no samples for ..." on each Playtones. The function ast_playtones_start calls ast_activate_generator, which calls ast_prod. The function ast_prod calls ast_write with empty audio frame. In this case it's spam log. Change-Id: Id4ac309489d9ff281bad02abdef341cecdede660	6 years ago
George Joseph	92d4ec2906	chan_dahdi: Address gcc9 issues ... Fixed format-truncation issues in chan_dahdi.c and sig_analog.c. Since they're related to fields provided by dahdi-tools we can't change the buffer sizes so we're just checking the return from snprintf and printing an errior if we overflow. Change-Id: Idc1f3c1565b88a7d145332a0196074b5832864e5	6 years ago