Skip to content
Snippets Groups Projects
  1. Apr 15, 2015
  2. Mar 28, 2015
    • Matthew Jordan's avatar
      clang compiler warnings: Fix a variety of "unused" warnings · 29e6597f
      Matthew Jordan authored
      This patch fixes the -Wunused-value -Wunused-variable -Wunused-const-variable
      errors caught by clang. Specifically:
      
      * apps/app_queue.c: removed unused qpm_cmd_usage[], qum_cmd_usage[],
                          qsmp_cmd_usage[]
      * cel/cel_sqlite3_custom.c: removed unused name[] = "cel_sqlite3_custom"
      * codecs/gsm/src/gsm_create.c: removed unused ident[] = "$Header$"
      * funcs/func_env.c:729: Fixed ast_str_append_substr.
      * main/editline/np/strlcat.c: removed unused rcsid variable
      * main/editline/np/strlcpy.c: removed unused rcsid variable
      * utils/conf2ael.c: removed unused cfextension_states
      * utils/extconf.c: removed unused cfextension_states
      
      Review: https://reviewboard.asterisk.org/r/4526
      
      ASTERISK-24917
      Reported by: dkdegroot
      patches:
        rb4526.patch submitted by dkdegroot (License 6600)
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/11@433693 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      29e6597f
  3. Nov 15, 2014
  4. Jun 16, 2014
  5. May 09, 2014
  6. Jan 28, 2014
  7. Jan 15, 2014
  8. Jan 03, 2014
  9. Dec 31, 2013
    • Kevin Harwell's avatar
      cel_pgsql: deadlock on unload and core_event_dispatcher · 27eb7cc7
      Kevin Harwell authored
      A deadlock can happen between a thread unloading or reloading the cel_pgsql
      module and the core_event_dispatcher taskprocessor thread. Description of
      what is happening:
      
      Thread 1 (for example, a netconsole thread):
      
          a "module reload cel_pgsql" is launched
          the thread enter the "my_unload_module" function (cel_pgsql.c)
          the thread acquire the write lock on psql_columns
          the thread enter the "ast_event_unsubscribe" function (event.c)
          the thread try to acquire the write lock on ast_event_subs[sub->type]
      
      Thread 2 (core_event_dispatcher taskprocessor thread):
      
          the taskprocessor pop a CEL event
          the thread enter the "handle_event" function (event.c)
          the thread acquire the read lock on ast_event_subs[sub->type]
          the thread callback the "pgsql_log" function (cel_pgsql.c), since it's a subscriber of CEL events
          the thread try to acquire a read lock on psql_columns
      
      (closes issue ASTERISK-22854)
      Reported by: Etienne Lessard
      Patches:
           cel_pgsql_fix_deadlock_event.patch uploaded by hexanol (license 6394)
      ........
      
      Merged revisions 404603 from http://svn.asterisk.org/svn/asterisk/branches/1.8
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/11@404604 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      27eb7cc7
  10. Sep 02, 2013
  11. Sep 05, 2012
  12. Mar 07, 2012
  13. Feb 14, 2012
  14. Feb 01, 2012
    • Richard Mudgett's avatar
      Remove inconsistency in CEL eventtype for user defined events. · 797d6331
      Richard Mudgett authored
      The CEL eventtype field for ODBC and PGSQL backends should be USER_DEFINED
      instead of the user defined event name supplied by the CELGenUserEvent
      application.  If the field is output as a number, the user defined name
      does not have a value and is always output as 21 for USER_DEFINED and the
      userdeftype field would be required to supply the user defined name.
      
      The following CEL backends (cel_odbc, cel_pgsql, cel_custom, cel_manager,
      and cel_sqlite3_custom) can be independently configured to remove this
      inconsistency.
      
      * Allows cel_manager, cel_custom, and cel_sqlite3_custom to behave the
      same way.
      
      (closes issue ASTERISK-17189)
      Reported by: Bryant Zimmerman
      
      Review: https://reviewboard.asterisk.org/r/1669/
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@353648 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      797d6331
  15. Jan 13, 2012
    • Richard Mudgett's avatar
      Add missing CEL logging fields to various CEL backends. · 523c95e1
      Richard Mudgett authored
      Multiple revisions 350555,350571
      
      ........
        r350555 | rmudgett | 2012-01-13 11:12:51 -0600 (Fri, 13 Jan 2012) | 12 lines
        
        Add missing CEL logging fields to various CEL backends.
        
        * Add missing eventextra to cel_psql.c and cel_odbc.c.
        
        * Add missing PeerAccount and EventExtra to cel_manager.c.
        
        * Add missing userdeftype support for cel_custom.conf.sample and
        cel_sqlite3_custom.conf.sample.
        
        (closes issue ASTERISK-17190)
        Reported by: Bryant Zimmerman
      ........
        r350571 | rmudgett | 2012-01-13 11:23:57 -0600 (Fri, 13 Jan 2012) | 8 lines
        
        Use compatible names for event extra data for various CEL backends.
        
        * Change eventextra to extra in cel_psql.c and cel_odbc.c.
        
        * Change EventExtra to Extra in cel_manager.c.
        
        (issue ASTERISK-17190)
      ........
      
      Merged revisions 350555,350571 from http://svn.asterisk.org/svn/asterisk/branches/1.8
      ........
      
      Merged revisions 350585 from http://svn.asterisk.org/svn/asterisk/branches/10
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@350605 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      523c95e1
  16. Jan 05, 2012
  17. Dec 22, 2011
  18. Sep 26, 2011
    • Richard Mudgett's avatar
      Merged revisions 337974 via svnmerge from · 55b70ae6
      Richard Mudgett authored
      https://origsvn.digium.com/svn/asterisk/branches/10
      
      ................
        r337974 | rmudgett | 2011-09-26 14:35:23 -0500 (Mon, 26 Sep 2011) | 37 lines
        
        Merged revisions 337973 via svnmerge from 
        https://origsvn.digium.com/svn/asterisk/branches/1.8
        
        ........
          r337973 | rmudgett | 2011-09-26 14:30:39 -0500 (Mon, 26 Sep 2011) | 30 lines
          
          Fix deadlock when using dummy channels.
          
          Dummy channels created by ast_dummy_channel_alloc() should be destoyed by
          ast_channel_unref().  Using ast_channel_release() needlessly grabs the
          channel container lock and can cause a deadlock as a result.
          
          * Analyzed use of ast_dummy_channel_alloc() and made use
          ast_channel_unref() when done with the dummy channel.  (Primary reason for
          the reported deadlock.)
          
          * Made app_dial.c:dial_exec_full() not call ast_call() holding any channel
          locks.  Chan_local could not perform deadlock avoidance correctly.
          (Potential deadlock exposed by this issue.  Secondary reason for the
          reported deadlock since the held lock was part of the deadlock chain.)
          
          * Fixed some uses of ast_dummy_channel_alloc() not checking the returned
          channel pointer for failure.
          
          * Fixed some potential chan=NULL pointer usage in func_odbc.c.  Protected
          by testing the bogus_chan value.
          
          * Fixed needlessly clearing a 1024 char auto array when setting the first
          char to zero is enough in manager.c:action_getvar().
          
          (closes issue ASTERISK-18613)
          Reported by: Thomas Arimont
          Patches:
                jira_asterisk_18613_v1.8.patch (license #5621) patch uploaded by rmudgett
          Tested by: Thomas Arimont
        ........
      ................
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@337975 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      55b70ae6
  19. Jul 14, 2011
  20. Jun 03, 2011
    • Richard Mudgett's avatar
      Merged revisions 321926 via svnmerge from · c8548bad
      Richard Mudgett authored
      https://origsvn.digium.com/svn/asterisk/branches/1.8
      
      ........
        r321926 | rmudgett | 2011-06-03 17:09:36 -0500 (Fri, 03 Jun 2011) | 18 lines
        
        Asterisk crash when unloading cdr_radius/cel_radius.
        
        The rc_openlog() API call is passed a string that is used by openlog() to
        format log messages.  The openlog() does not copy the string it just keeps
        a pointer to it.  When the module is unloaded, the string is gone from
        memory.  Depending upon module load order and if the other module then has
        an error, a crash happens.
        
        * Pass rc_openlog() a strdup'd string with the understanding that there
        will be a small memory leak if the cdr_radius/cel_radius modules are
        unloaded.
        
        * Call rc_destroy() to free the rc handle memory when the module is
        unloaded.
        
        JIRA AST-483
        JIRA SWP-3062
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@321927 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      c8548bad
  21. May 19, 2011
  22. May 05, 2011
  23. Mar 29, 2011
  24. Feb 04, 2011
  25. Feb 01, 2011
  26. Aug 29, 2010
  27. Aug 23, 2010
  28. Jul 20, 2010
  29. Jul 14, 2010
  30. Mar 20, 2010
  31. Mar 14, 2010
  32. Jan 15, 2010
  33. Dec 30, 2009
  34. Oct 07, 2009
  35. Aug 10, 2009
  36. Jun 26, 2009
    • Russell Bryant's avatar
      Merge the new Channel Event Logging (CEL) subsystem. · 0264eef1
      Russell Bryant authored
      CEL is the new system for logging channel events.  This was inspired after
      facing many problems trying to represent what is possible to happen to a call
      in Asterisk using CDR records.  For more information on CEL, see the built in
      HTML or PDF documentation generated from the files in doc/tex/.
      
      Many thanks to Steve Murphy (murf) and Brian Degenhardt (bmd) for their hard
      work developing this code.  Also, thanks to Matt Nicholson (mnicholson) and
      Sean Bright (seanbright) for their assistance in the final push to get this
      code ready for Asterisk trunk.
      
      Review: https://reviewboard.asterisk.org/r/239/
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@203638 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      0264eef1
Loading