Skip to content
Snippets Groups Projects
  1. May 04, 2015
    • Matt Jordan's avatar
      contrib/ast-db-manage: Add Postgres ENUM type support in auto DTMF mode update · 75c0aa69
      Matt Jordan authored
      The upgrade script for auto DTMF mode (31cd4f4891ec) added in 88b0fa77
      failed to add ENUM support for Postgres databases. This requires a
      specific import from the sqlalchemy.dialects.postgresql package. This
      patch corrects this error, which allows for Postgres update scripts to
      be generated.
      
      ASTERISK-24706
      
      Change-Id: I4742ac8efa533cd6f18e0bdd907b339a9aedf015
      75c0aa69
  2. Apr 27, 2015
    • Corey Farrell's avatar
      Astobj2: Allow reference debugging to be enabled/disabled by config. · 5c1d07ba
      Corey Farrell authored
      * The REF_DEBUG compiler flag no longer has any effect on code that uses
        Astobj2.  It is used to determine if reference debugging is enabled by
        default.  Reference debugging can be enabled or disabled in asterisk.conf.
      * Caller information is provided in logger errors for ao2 bad magic numbers.
      * Optimizes AO2 by merging internal functions with the public counterpart.
        This was possible now that we no longer require a dual ABI.
      
      ASTERISK-24974 #close
      Reported by: Corey Farrell
      
      Change-Id: Icf3552721fe999365ba8a8cf00a965aa6b897cc1
      5c1d07ba
  3. Apr 24, 2015
  4. Apr 16, 2015
    • George Joseph's avatar
      res_pjsip: Add global option to limit the maximum time for initial qualifies · c6ed6816
      George Joseph authored
      
      Currently when Asterisk starts initial qualifies of contacts are spread out
      randomly between 0 and qualify_timeout to prevent network and system overload.
      If a contact's qualify_frequency is 5 minutes however, that contact may be
      unavailable to accept calls for the entire 5 minutes after startup.  So while
      staggering the initial qualifies is a good idea, basing the time on
      qualify_timeout could leave contacts unavailable for too long.
      
      This patch adds a new global parameter "max_initial_qualify_time" that sets the
      maximum time for the initial qualifies.  This way you could make sure that all
      your contacts are initialy, randomly qualified within say 30 seconds but still
      have the contact's ongoing qualifies at a 5 minute interval.
      
      If max_initial_qualify_time is > 0, the formula is initial_interval =
      min(max_initial_interval, qualify_timeout * random().  If not set,
      qualify_timeout is used.
      
      The default is "0" (disabled).
      
      ASTERISK-24863 #close
      
      Change-Id: Ib80498aa1ea9923277bef51d6a9015c9c79740f4
      Tested-by: default avatarGeorge Joseph <george.joseph@fairview5.com>
      c6ed6816
    • George Joseph's avatar
      pjsip_options: Add qualify_timeout processing and eventing · 51886c68
      George Joseph authored
      This is the second follow-on to https://reviewboard.asterisk.org/r/4572/ and the
      discussion at
      http://lists.digium.com/pipermail/asterisk-dev/2015-March/073921.html
      
      
      
      The basic issues are that changes in contact status don't cause events to be
      emitted for the associated endpoint.  Only dynamic contact add/delete actions
      update the endpoint.  Also, the qualify timeout is fixed by pjsip at 32 seconds
      which is a long time.
      
      This patch makes use of the new transaction timeout feature in r4585 and
      provides the following capabilities...
      
      1.  A new aor/contact variable 'qualify_timeout' has been added that allows the
      user to specify the maximum time in milliseconds to wait for a response to an
      OPTIONS message.  The default is 3000ms.  When the timer expires, the contact is
      marked unavailable.
      
      2.  Contact status changes are now propagated up to the endpoint as follows...
      When any contact is 'Available', the endpoint is marked as 'Reachable'.  When
      all contacts are 'Unavailable', the endpoint is marked as 'Unreachable'.  The
      existing endpoint events are generated appropriately.
      
      ASTERISK-24863 #close
      
      Change-Id: Id0ce0528e58014da1324856ea537e7765466044a
      Tested-by: Dmitriy Serov
      Tested-by: default avatarGeorge Joseph <george.joseph@fairview5.com>
      51886c68
  5. Apr 10, 2015
  6. Mar 27, 2015
  7. Mar 19, 2015
  8. Mar 17, 2015
  9. Mar 13, 2015
  10. Mar 09, 2015
  11. Feb 15, 2015
  12. Jan 23, 2015
  13. Jan 20, 2015
  14. Jan 09, 2015
  15. Nov 19, 2014
  16. Nov 03, 2014
  17. Oct 31, 2014
  18. Oct 17, 2014
  19. Oct 09, 2014
  20. Oct 02, 2014
  21. Sep 29, 2014
  22. Sep 26, 2014
  23. Sep 18, 2014
  24. Sep 15, 2014
  25. Aug 11, 2014
    • Matthew Jordan's avatar
      app_queue: Add RealTime support for queue rules · add46fd2
      Matthew Jordan authored
      This patch gives the optional ability to keep queue rules in RealTime. It is
      important to note that with this patch:
       (a) Queue rules in RealTime are only examined on module load/reload
       (b) Queue rules are loaded both from the queuerules.conf file as well as the
           RealTime backend
      To inform app_queue to examine RealTime for queue rules, a new setting has been
      added to queuerules.conf's general section "realtime_rules". RealTime queue
      rules will only be used when this setting is set to "yes".
      
      The schema for the database table supports a rule_name, time, min_penalty, and
      max_penalty columns. min_penalty and max_penalty can be relative, if a '-' or
      '+' literal is provided. Otherwise, the penalties are treated as constants.
      
      For example:
      rule_name, time, min_penalty, max_penalty
      'default', '10', '20', '30'
      'test2', '20', '30', '55'
      'test2', '25', '-11', '+1111'
      'test2', '400', '112', '333'
      'test3', '0', '4564', '46546'
      'test_rule', '40', '15', '50'
      
      which would result in :
      
      Rule: default
       - After 10 seconds, adjust QUEUE_MAX_PENALTY to 30 and adjust
         QUEUE_MIN_PENALTY to 20
      Rule: test2
       - After 20 seconds, adjust QUEUE_MAX_PENALTY to 55 and adjust
         QUEUE_MIN_PENALTY to 30
       - After 25 seconds, adjust QUEUE_MAX_PENALTY by 1111 and adjust
         QUEUE_MIN_PENALTY by -11
       - After 400 seconds, adjust QUEUE_MAX_PENALTY to 333 and adjust
         QUEUE_MIN_PENALTY to 112
      Rule: test3
       - After 0 seconds, adjust QUEUE_MAX_PENALTY to 46546 and adjust
         QUEUE_MIN_PENALTY to 4564
      Rule: test_rule
       - After 40 seconds, adjust QUEUE_MAX_PENALTY to 50 and adjust
         QUEUE_MIN_PENALTY to 15
      
      If you use RealTime, the queue rules will be always reloaded on a module
      reload, even if the underlying file did not change. With the option disabled,
      the rules will only be reloaded if the file was modified.
      
      Review: https://reviewboard.asterisk.org/r/3607/
      
      ASTERISK-23823 #close
      Reported by: Michael K
      patches:
        app_queue.c_realtime_trunk.patch uploaded by Michael K (License 6621)
      ........
      
      Merged revisions 420624 from http://svn.asterisk.org/svn/asterisk/branches/13
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@420625 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      add46fd2
  26. Aug 06, 2014
  27. Jul 16, 2014
  28. Jul 13, 2014
  29. Jul 03, 2014
  30. Jun 30, 2014
  31. Jun 27, 2014
  32. Jun 12, 2014
  33. Jun 09, 2014
  34. Jun 04, 2014
Loading