Skip to content
Snippets Groups Projects
  1. Nov 17, 2014
  2. Jul 18, 2014
  3. Apr 15, 2014
  4. Mar 27, 2014
  5. Oct 01, 2013
  6. Sep 21, 2013
  7. Sep 18, 2013
  8. Sep 17, 2013
  9. Sep 06, 2013
  10. Aug 30, 2013
  11. Aug 23, 2013
    • Matthew Jordan's avatar
      Update config framework/sorcery with types/options without documentation · e31bd332
      Matthew Jordan authored
      There are times when a configuration option should not have documentation.
      
      1. Some options are registered with a particular object merely as a warning to
         users. These options aren't even really 'deprecated' - which has its own
         separate API call - they are actually provided by a different configuration
         file. The options are merely registered so that the user gets a warning that
         a different configuration file provides the item.
      
      2. Some object types - most notably some used by modules that use sorcery - are
         completely internal and should never be shown to the user.
      
      3. Sorcery itself has several 'hidden' fields that should never be shown to a
         user.
      
      This patch updates the configuration framework and sorcery with additional API
      calls that allow a module to register types as internal and options as not
      requiring documentation. This bypasses the XML documentation checking.
      
      This patch also re-enables the strict XML documentation checking in trunk, as
      well as updates some documentation that was missing.
      
      Review: https://reviewboard.asterisk.org/r/2785/
      
      (closes issue ASTERISK-22359)
      Reported by: Matt Jordan
      
      (closes issue ASTERISK-22112)
      Reported by: Rusty Newton
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@397524 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      e31bd332
  12. Jul 23, 2013
  13. Jul 01, 2013
  14. Jun 24, 2013
  15. Jun 13, 2013
  16. Jun 10, 2013
    • Mark Michelson's avatar
      Temporary fix for people using sample features.conf from previous Asterisk versions. · ba5c97ef
      Mark Michelson authored
      People who use the features.conf.sample file from Asterisk 11 and before in trunk were
      given a rude awakening when features configuration changes were made. Because it uses the
      config framework and the config framework is strict about what is accepted and what isn't,
      people that had parking options configured found that Asterisk no longer started. This is
      because parking options are currently handled in res_parking.conf instead of features.conf.
      
      This fix seeks to create a temporary band-aid fix for the problem, but having parking options
      from the general section be passed to a handler that will simply print that the option is no
      longer supported. This will not cause Asterisk to exit.
      
      The fix only applies to options in the general section. There are two main reasons for this:
      
      1) The sample features.conf file only has parking options in the general section. There are no
      configured parking lots. Therefore it's not quite as "urgent" to get the parking lot parsing
      fixed.
      
      2) The plan is to move parking configuration back from res_parking.conf to features.conf. When
      that happens, the parking lots will also be addressed at that time.
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@391269 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      ba5c97ef
  17. Jun 07, 2013
  18. Jun 06, 2013
Loading