Skip to content
Snippets Groups Projects
  1. Jan 11, 2019
    • Alexei Gradinari's avatar
      res_pjsip: add option to enable ContactStatus event when contact is updated · f0546d1d
      Alexei Gradinari authored
      The commit I2f97ebfa79969a36a97bb7b9afd5b6268cf1a07d removed sending out
      the ContactStatus AMI event when a contact is updated.
      Thist change broke things which rely on old behavior.
      
      This patch adds a new PJSIP global configuration option
      'send_contact_status_on_update_registration' to be able to preserve old
      ContactStatus behavior.
      By default new behavior, i.e. the ContactStatus event will not be sent when a
      device refreshes its registration.
      
      Change-Id: I706adf7584e7077eb6bde6d9799ca408bc82ce46
      f0546d1d
  2. Jan 05, 2019
    • Diederik de Groot's avatar
      RAII: Change order or variables in clang version · 7bd30905
      Diederik de Groot authored
      This prevents use-after-scope issues when unwinding the stack,
      which happens in reverse order. The varname variable needs to
      remain alive for the destruction to be able to access it.
      Issue was found using clang + address-sanitizer.
      
      ASTERISK-28232 #close
      
      Change-Id: I00811c34ae910836a5fb6d22304528aef92624db
      7bd30905
  3. Jan 04, 2019
  4. Jan 03, 2019
  5. Jan 02, 2019
  6. Dec 26, 2018
  7. Dec 24, 2018
    • George Joseph's avatar
      ast_coredumper: Refactor the pid determination process · 809e8362
      George Joseph authored
      In order to get a dump of the running process, we need to find the
      pid of the main asterisk process.  This can be tricky if there are
      also instances of "asterisk -r" running or if an alternate location
      for asterisk.conf was specified on the command line with the -C
      option that also specified an alternation location for the pid file.
      
      So now...
      
      1. We find the asterisk executable with "which" or the --asterisk-bin
         command line option.
      2. If there's only 1 process with an executable path that matches,
         we use that pid.  If not...
      3. We try "<asterisk-bin> -rx 'core show settings'" and parse the
         output to find the pidfile, then read that for the pid.  If that
         didn't work...
      4. We get a list of all the pids matching <asterisk-bin> and look
         in /proc/<pid>/cmdline for a -C argument and retry the "core show
         settings" using the same -C option.  We can't parse the output
         of "ps" to get the -C path because it may contain spaces.  The
         contents of /proc/<pid>/cmdline are delimited by NULLs.  For BSDs
         we may have to mount /proc first. :(
      
      ASTERISK-28221
      Reported by: Andrew Nagy
      
      Change-Id: I8aa1f3f912f949df2b5348908803c636bde1d57c
      809e8362
  8. Dec 19, 2018
  9. Dec 18, 2018
  10. Dec 17, 2018
  11. Dec 14, 2018
  12. Dec 13, 2018
  13. Dec 12, 2018
  14. Dec 11, 2018
  15. Dec 10, 2018
Loading