28879 Commits (a8f8c5d857a41e43b5ea0d8c9dd671336710ec05)

 

All Branches   

Search

Author	SHA1	Message	Date
George Joseph	a8f8c5d857	Merge "res_agi: Allow configuration of audio format of EAGI pipe" into 13	8 years ago
George Joseph	a2d15b93f1	Merge "unittests: Add a unit test that causes a SEGV and..." into 13	8 years ago
Jenkins2	558199e5dd	Merge "res_agi: Prevent crash when SET VARIABLE called without arguments" into 13	8 years ago
Jenkins2	a3684b74e6	Merge "res_agi: Clarify 'RECORD FILE' documentation" into 13	8 years ago
George Joseph	65898c3af8	unittests: Add a unit test that causes a SEGV and... ... ...that can only be run by explicitly calling it with 'test execute category /DO_NOT_RUN/ name RAISE_SEGV' This allows us to more easily test CI and debugging tools that should do certain things when asterisk coredumps. To allow this a new member was added to the ast_test_info structure named 'explicit_only'. If set by a test, the test will be skipped during a 'test execute all' or 'test execute category ...'. Change-Id: Ia3a11856aae4887df9a02b6b081cc777b36eb6ed	8 years ago
Joshua Colp	1bddf1efc3	Merge "chan_sip: Better ICE handling for RTCP-MUX" into 13	8 years ago
Jenkins2	a69905af69	Merge "res_rtp_asterisk: rtcp mux using the wrong srtp unprotecting algorithm" into 13	8 years ago
Jenkins2	4dfcccdb70	Merge "res_format_attr_h26x: Trim blanks in fmtp attributes" into 13	8 years ago
Jenkins2	bc4ef72394	Merge "app_queue: Fix members showing as being in call when not." into 13	8 years ago
Sean Bright	90237dca11	res_agi: Allow configuration of audio format of EAGI pipe ... This change allows the format of the EAGI audio pipe to be changed by setting the dialplan variable 'EAGI_AUDIO_FORMAT' to the name of one of the loaded formats. ASTERISK-26124 #close Change-Id: I7a10fad401ad2a21c68c2e7246fa357d5cee5bbd	8 years ago
Sean Bright	3eb7fbba72	res_agi: Clarify 'RECORD FILE' documentation ... Documented the 'beep' option in both the parameters list and the command description. ASTERISK-23839 #close Change-Id: I4970395c922dbdce3f7cf0f56d5b065ec9aa53ea	8 years ago
Sean Bright	f306e451f6	res_agi: Prevent crash when SET VARIABLE called without arguments ... Explicitly check that the appropriate number of arguments were passed to SET VARIABLE before attempting to reference them. Also initialize the arguments array to zeroes before populating it. ASTERISK-22432 #close Change-Id: I5143607d80a2724f749c1674f3126b04ed32ea97	8 years ago
Sean Bright	700ef6861a	res_format_attr_h26x: Trim blanks in fmtp attributes ... Some devices separate format attributes with a semicolon followed by a space, so trim blanks before trying to match them. ASTERISK-27008 #close Change-Id: Ia44cb2e4fef5c73dc541a29da79cb0e19c22d9cc	8 years ago
Joshua Colp	6bfcb1acc7	app_queue: Fix members showing as being in call when not. ... A change was done which added an 'in_call' flag to queue members that was set to true while talking to an agent. Unfortunately in practice this does not accurately reflect whether they are talking to an agent or not. If a Local channel is involved and a transfer is performed then the app_queue application would incorrectly think the agent was still in a call with the caller. This was done to fix a race condition between an agent becoming available by device state and the checking of the last call information for the wrapup time. There was a small window where the last call information would be the previous value instead of the new one. This change goes about fixing the original issue in a different way by considering the call completed if device state is received which would make the agent available and if they are currently in a call. If this occurs the last call information is updated before the agent becomes available ensuring that old information is not present when checking if the member should be called. This also improves the transfer situation by actually updating and enforcing the wrapup time. ASTERISK-26399 ASTERISK-26400 ASTERISK-26715 ASTERISK-26975 Change-Id: Ife1cb686e3173b3a6d368601adef9aff69d4beea	8 years ago
Jenkins2	d0a1239f55	Merge "res_pjsip_session : fixed wrong From Header number On Re-invite" into 13	8 years ago
Kevin Harwell	e91efef2bb	res_rtp_asterisk: rtcp mux using the wrong srtp unprotecting algorithm ... When using rtcp mux if an rtcp payload came in it would still use the srtp unprotect algorithm instead of the srtp unprotect rtcp method. Since rtcp data was being passed to the rtp unprotect method this would result in an error. This patch ensures that the correct unprotect method is chosen by making sure the passed in rtcp flag is appropriately set when rtcp mux is enabled and an rtcp payload is received. ASTERISK-26979 #close Change-Id: Ic5409f9d1a267f1d4785fc5aed867daaecca6241	8 years ago
Sean Bright	4479038073	chan_sip: Better ICE handling for RTCP-MUX ... If we are offered or are offering RTCP-MUX, don't consider RTCP ICE candidates. This confuses certain browsers (current Firefox for example) and causes intial audio setup delays. ASTERISK-26982 #close Change-Id: Ifeaf47e83972fe8dbe58b7fb3d6d1823400cfb91	8 years ago
Jenkins2	7af41de364	Merge "app_queue: Fix duplicate queue_log entries for EXITEMPTY and ABANDON" into 13	8 years ago
Yasin CANER	36628cc9c4	res_pjsip_session : fixed wrong From Header number On Re-invite ... ASTERISK-26964 #close Change-Id: I55a9caa7dc90e6c4c219cb09b5c2ec08af84a302	8 years ago
Jenkins2	ff6d179864	Merge "res_hep_rtcp: Add support level to module info" into 13	8 years ago
Jenkins2	7919b7287f	Merge "AST-2017-004: chan_skinny: Add EOF check in skinny_session" into 13	8 years ago
Jenkins2	6aa11c4b31	Merge "AST-2017-003: Handle zero-length body parts correctly." into 13	8 years ago
Mark Michelson	919ccdb9ac	AST-2017-002: Ensure transaction key buffer is large enough. ... ASTERISK-26938 #close Change-Id: I266490792fd8896a23be7cb92f316b7e69356413	8 years ago
Mark Michelson	49c032abef	AST-2017-003: Handle zero-length body parts correctly. ... ASTERISK-26939 #close Change-Id: I7ea235ab39833a187db4e078f0788bd0af0a24fd	8 years ago
George Joseph	1cc18d4025	AST-2017-004: chan_skinny: Add EOF check in skinny_session ... The while(1) loop in skinny_session wasn't checking for EOF so a packet that was longer than a header but still truncated would spin the while loop infinitely. Not only does this permanently tie up a thread and drive a core to 100% utilization, the call of ast_log() in such a tight loop eats all available process memory. Added poll with timeout to top of read loop ASTERISK-26940 #close Reported-by: Sandro Gauci Change-Id: I2ce65f3c5cb24b4943a9f75b64d545a1e2cd2898	8 years ago
Sean Bright	c107ab4c04	res_hep_rtcp: Add support level to module info ... Change-Id: I5661478f9cf12d431f730e42be79323b62831e92	8 years ago
Ivan Poddubny	cfeae52c0f	app_queue: Fix duplicate queue_log entries for EXITEMPTY and ABANDON ... There are 2 places in app_queue.c that log EXITEMPTY event: one in wait_our_turn, and another one in queue_exec in the loop trying to call an agent after wait_our_turn. In most cases it leads to logging EXITEMPTY twice. ABANDON is also logged on two places, and in the rare case when an agent and caller hang up simultaneously it's also possible to get duplicates in queue_log. This commit changes wait_our_turn to return -1 ("the caller should exit the queue") instead of 0 ("the caller's turn has arrived") in case of leaving when empty, so queue_exec skips the agent calling loop. Also, leave_queue is now executed only once in this case, because 2nd time is just a noop when the queue entry has already been removed. Also, it sets qe->handled to -1 to indicate that the call was not answered by an agent, but the necessary handling has already been done in order to avoid logging an extra ABANDON entry. ASTERISK-25665 #close Reported by: Ove Aursand Change-Id: I4578dd383bf2ac41589cf167865e8aaebcd4c11e	8 years ago
Jenkins2	722ec0671e	Merge "res_pjsip_session.c: Process initial INVITE sooner. (key exists)" into 13	8 years ago
Rodrigo Ramírez Norambuena	5da91c65be	Fix spelling queues.conf.sample file ... Change-Id: Ie1c2d83af66f27a449da09a68d987e0992627fee	8 years ago
Richard Mudgett	b67363006f	res_pjsip_session.c: Process initial INVITE sooner. (key exists) ... Retransmissions of an initial INVITE could be queued in the serializer before we have processed the first INVITE message. If the first INVITE message doesn't get completely processed before the retransmissions are seen then we could try to setup the same call from the retransmissions. A symptom of this is seeing a (key exists) message associated with an INVITE. An earlier change attempted to address this kind of problem by calculating a distributor serializer to use for unassociated messages. Part of that change also made incoming calls keep using that distributor serializer. (ASTERISK-26088) However, some leftover code was still deferring the INVITE processing to the session's serializer even though we were already in that serializer. This not only is unnecessary but would cause the same call resetup problem. * Removed the code to defer processing the initial INVITE to the session's serializer because we are already running in that serializer. ASTERISK-26998 #close Change-Id: I1e822d82dcc650e508bc2d40d545d5de4f3421f6	8 years ago
Vitezslav Novy	1bcce442d0	chan_sip: Change sip_get_codec() to return correct codec list ... Return cahnnel nativeformats to fix bridge technology selection process. Same approach as in pjsip module. ASTERISK-26143 Reported-by: Henning Holtschneider Change-Id: I64e863753954d6ad67a9e722df2ebc328705ad48	8 years ago
Jenkins2	6383d9214a	Merge "res_hep_rtcp: Provide chan_sip Call-ID for RTCP messages." into 13	8 years ago
Jenkins2	3cfbb8b481	Merge "logger: Added logger_queue_limit to the configuration options." into 13	8 years ago
Jenkins2	ddbc68b68a	Merge "tcptls: Improve error messages for TLS connections." into 13	8 years ago
Jenkins2	a546e16cdb	Merge "Prevent Undefined Capath Crash" into 13	8 years ago
Jenkins2	a2c0d8c25d	Merge "cel_odbc: Fix timestamp processing for microseconds" into 13	8 years ago
Joshua Colp	6fba0a41f0	tcptls: Improve error messages for TLS connections. ... This change uses the functions provided by OpenSSL to query and better construct error messages for situations where the connection encounters a problem. ASTERISK-26606 Change-Id: I7ae40ce88c0dc4e185c4df1ceb3a6ccc198f075b	8 years ago
Joshua Elson	8ec6e19c86	Prevent Undefined Capath Crash ... It is possible to initialize a valid config without a capath or cafile definition. This will cause a crash on a reload. This fix ensures capath is always allocated. ASTERISK-26983 #close Change-Id: I63ff715d9d9023427543a5b8a4ba7b0d82533c12	8 years ago
George Joseph	d6325373ac	cel_odbc: Fix timestamp processing for microseconds ... When a column is of type timestamp, the fraction part of the event field's seconds was frequently parsed incorrectly especially if there were leading zeros. For instance "2017-05-23 23:55:03.023" would be parsed into an int as "23" then when the timestamp was formatted again to be inserted into the database column it'd be "2017-05-23 23:55:03.23" which is now 230 milliseconds instead of 23 milliseconds. "03.000001" would be transformed to "03.1", etc. * If the event field is 'eventtime' and the db column is timestamp, then existing processing has already correctly formatted the timestamp so now we simply use it rather than parsing it and re-printing it. This is the most common use case anyway. * If the event field is other than 'eventtime' and the db column is timestamp, we now parse the seconds, including the fractional part into a double rather than 2 ints. This preserves the magnitude and precision of the fractional part. When we print it, we now print it as a "%09.6lf" which correctly represents the input. To be honest, why we parse the string timestamp into components, test the components, then print the components back into a string timestamp is beyond me. We should use parse it, test it, then if it passes, use the original string representation in the database call. Maybe someone thought that some implementations wouldn't take a partial timestamp string like "2017-05-06" and decided to always produce a full timestamp string even if an abbreviated one was supplied. Anyway, I'm leaving it as it is. ASTERISK-25032 #close Reported-by: Etienne Lessard Change-Id: Id407e6221f79a5c1120e1a70bc7e893bbcaf1938	8 years ago
Joshua Colp	10a49ab362	res_hep_rtcp: Provide chan_sip Call-ID for RTCP messages. ... This change adds the required logic to allow the SIP Call-ID to be placed into the HEP RTCP traffic if the chan_sip module is used. In cases where the option is enabled but the channel is not either SIP or PJSIP then the code will fallback to the channel name as done previously. Based on the change on Nir's branch at: team/nirs/hep-chan-sip-support ASTERISK-26427 Change-Id: I09ffa5f6e2fdfd99ee999650ba4e0a7aad6dc40d	8 years ago
Joshua Colp	371213217c	Merge "func_cdr: Allow empty value for CDR dialplan function." into 13	8 years ago
George Joseph	7d4a22bf2e	logger: Added logger_queue_limit to the configuration options. ... All log messages go to a queue serviced by a single thread which does all the IO. This setting controls how big that queue can get (and therefore how much memory is allocated) before new messages are discarded. The default is 1000. Should something go bezerk and log tons of messages in a tight loop, this will prevent memory escalation. When the limit is reached, a WARNING is logged to that effect and messages are discarded until the queue is empty again. At that time another WARNING will be logged with the count of discarded messages. There's no "low water mark" for this queue because the logger thread empties the entire queue and processes it in 1 batch before going back and waiting on the queue again. Implementing a low water mark would mean additional locking as the thread processes each message and it's not worth it. A "test" was added to test_logger.c but since the outcome is non-deterministic, it's really just a cli command, not a unit test. Change-Id: Ib4520c95e1ca5325dbf584c7989ce391649836d1	8 years ago
Joshua Colp	e3fa458440	Merge "netsock2.c: Made get/set addr port avoid potential uninitialized memory." into 13	8 years ago
Joshua Colp	4d0bc3e5fc	Merge "bridge: Fix returning to dialplan when executing Bridge() from AMI." into 13	8 years ago
Richard Mudgett	614eda785d	netsock2.c: Made get/set addr port avoid potential uninitialized memory. ... Change-Id: I532052bd7cd95a4b3565485fc01e2a1ea07ee647	8 years ago
Jenkins2	250fee82aa	Merge "app_confbridge: Fix reference to cfg in menu_template_handler" into 13	8 years ago
Joshua Colp	c3ed63cb2c	func_cdr: Allow empty value for CDR dialplan function. ... A regression was introduced in 12 where passing an empty value to the CDR dialplan function was not longer allowed. This change returns to the behavior of 11 where it is permitted. ASTERISK-26173 Change-Id: I3f148203b54ec088007e29e30005a5de122e51c5	8 years ago
George Joseph	bed6c0d04b	app_confbridge: Fix reference to cfg in menu_template_handler ... menu_template_handler wasn't properly accounting for the fact that it might be called both during a load/reload (which isn't really valid but not prevented) and by a dialplan function. In both cases it was attempting to use the "pending" config which wasn't valid in the latter case. aco_process_config is also partly to blame because it wasn't properly cleaning "pending" up when a reload was done and no changes were made. Both of these contributed to a crash if CONFBRIDGE(menu,template) was called in a dialplan after a reload. * aco_process_config now sets info->internal->pending to NULL after it unrefs it although this isn't strictly necessary in the context of this fix. * menu_template_handler now uses the "current" config and silently ignores any attempt to be called as a result of someone uses the "template" parameter in the conf file. Luckily there's no other place in the codebase where aco_pending_config is used outside of aco_process_config. ASTERISK-25506 #close Reported-by: Frederic LE FOLL Change-Id: Ib349a17d3d088f092480b19addd7122fcaac21a7	8 years ago
Joshua Colp	ce1985b099	Merge "res_rtp_asterisk: Clearing the remote RTCP address causes RTCP failures" into 13	8 years ago
Joshua Colp	7ffd80cc04	bridge: Fix returning to dialplan when executing Bridge() from AMI. ... When using the Bridge AMI action on the same channel multiple times it was possible for the channel to return to the wrong location in the dialplan if the other party hung up. This happened because the priority of the channel was not preserved across each action invocation and it would fail to move on to the next priority in other cases. This change makes it so that the priority of a channel is preserved when taking control of it from another thread and it is incremented as appropriate such that the priority reflects where the channel should next be executed in the dialplan, not where it may or may not currently be. The Bridge AMI action was also changed to ensure that it too starts the channels at the next location in the dialplan. ASTERISK-24529 Change-Id: I52406669cf64208aef7252a65b63ade31fbf7a5a	8 years ago