Skip to content
Snippets Groups Projects
  1. Jun 26, 2014
  2. Jun 25, 2014
  3. Jun 24, 2014
  4. Jun 23, 2014
  5. Jun 20, 2014
  6. Jun 19, 2014
  7. Jun 18, 2014
    • Matthew Jordan's avatar
      stasis_channels: Update the stasis cache if manager variables are needed · a965613c
      Matthew Jordan authored
      In r416211, the publishing of variable changes was modified such that a
      cached channel snapshot was used if manager variables were not requested
      with each AMI event. This was done to reduce the amount of channel snapshots
      created.
      
      However, an assumption was made that generating a channel snapshot and
      publishing the snapshot to the channel topic was sufficient to ensure that
      the cache would be updated; this is not the case. The channel snapshot type
      must be used to force a snapshot update.
      
      This patch updates the publication of channel variables such that the cache
      is updated prior to publication of the channel variable message if manager
      variables are in use. This ensures that all AMI events receive the variable
      update when they are supposed to.
      
      Note that this issue was caught by the Asterisk Test Suite (go go testing)
      ........
      
      Merged revisions 416557 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@416561 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      a965613c
  8. Jun 16, 2014
  9. Jun 15, 2014
  10. Jun 13, 2014
  11. Jun 12, 2014
  12. Jun 11, 2014
  13. Jun 10, 2014
  14. Jun 09, 2014
  15. Jun 08, 2014
  16. Jun 06, 2014
  17. Jun 05, 2014
  18. May 30, 2014
  19. May 29, 2014
  20. May 28, 2014
    • Matthew Jordan's avatar
      Logger/CLI/etc.: Fix some aesthetic issues; reduce chatty verbose messages · fb5690ce
      Matthew Jordan authored
      This patch addresses some aesthetic issues in Asterisk. These are all just
      minor tweaks to improve the look of the CLI when used in a variety of
      settings. Specifically:
       * A number of chatty verbose messages were removed or demoted to DEBUG
         messages. Verbose messages with a verbosity level of 5 or higher were -
         if kept as verbose messages - demoted to level 4. Several messages
         that were emitted at verbose level 3 were demoted to 4, as announcement
         of dialplan applications being executed occur at level 3 (and so the
         effects of those applications should generally be less).
       * Some verbose messages that only appear when their respective 'debug'
         options are enabled were bumped up to always be displayed.
       * Prefix/timestamping of verbose messages were moved to the verboser
         handlers. This was done to prevent duplication of prefixes when the
         timestamp option (-T) is used with the CLI.
       * Verbose magic is removed from messages before being emitted to
         non-verboser handlers. This prevents the magic in multi-line verbose
         messages (such as SIP debug traces or the output of DumpChan) from
         being written to files.
       * _Slightly_ better support for the "light background" option (-W) was
         added. This includes using ast_term_quit in the output of XML
         documentation help, as well as changing the "Asterisk Ready" prompt to
         bright green on the default background (which stands a better chance of
         being displayed properly than bright white).
      
      Review: https://reviewboard.asterisk.org/r/3547/
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@414798 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      fb5690ce
  21. May 25, 2014
    • Matthew Jordan's avatar
      core_unreal: Prevent double free of core_unreal pvt · 09bbfa76
      Matthew Jordan authored
      When a channel is destroyed (such as via ast_channel_release in off nominal
      paths in core_unreal), it will attempt to free (via ast_free) the channel tech
      pvt. This is problematic for a few reasons:
      1. The channel tech pvt is an ao2 object in core_unreal. Free'ing the pvt
         directly is no good.
      2. The channel tech pvt's reference count is dropped just prior to calling
         ast_channel_release, resulting in the pvt's destruction. Hence, the
         channel destructor is free'ing an invalid pointer.
      
      This patch keeps the dropping of the reference count, but sets the pvt to
      NULL on the channel prior to releasing it. This models what would occur if the
      channel was hung up directly.
      ........
      
      Merged revisions 414542 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@414543 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      09bbfa76
  22. May 23, 2014
  23. May 22, 2014
    • Scott Griepentrog's avatar
      ARI: Add ability to raise arbitrary User Events · cf21644d
      Scott Griepentrog authored
      User events can now be generated from ARI.  Events can be signalled with
      arbitrary json variables, and include one or more of channel, bridge, or
      endpoint snapshots.  An application must be specified which will receive
      the event message (other applications can subscribe to it).  The message
      will also be delivered via AMI provided a channel is attached.  Dialplan
      generated user event messages are still transmitted via the channel, and
      will only be received by a stasis application they are attached to or if
      the channel is subscribed to.
      
      This change also introduces the multi object blob mechanism used to send
      multiple snapshot types in a single message.  The dialplan app UserEvent
      was also changed to use multi object blob, and a new stasis message type
      created to handle them.
      
      ASTERISK-22697 #close
      Review: https://reviewboard.asterisk.org/r/3494/
      ........
      
      Merged revisions 414405 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@414406 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      cf21644d
    • Jonathan Rose's avatar
      res_pjsip_refer: Fix bugs involving Parking/PJSIP/transfers · d0088210
      Jonathan Rose authored
      PJSIP would never send the final 200 Notify for a blind transfer
      when transferring to parking. This patch fixes that. In addition,
      it fixes a reference leak when performing blind transfers to
      non-bridging extensions.
      
      Review: https://reviewboard.asterisk.org/r/3485/
      ........
      
      Merged revisions 414400 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@414403 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      d0088210
    • Matthew Jordan's avatar
      res_corosync: Update module to work with Stasis (and compile) · 9cee08f5
      Matthew Jordan authored
      This patch fixes res_corosync such that it works with Asterisk 12. This
      restores the functionality that was present in previous versions of
      Asterisk, and ensures compatibility with those versions by restoring the
      binary message format needed to pass information from/to them.
      
      The following changes were made in the core to support this:
       * The event system has been partially restored. All event definition and
         event types in this patch were pulled from Asterisk 11. Previously, we had
         hoped that this information would live in res_corosync; however, the
         approach in this patch seems to be better for a few reasons:
         (1) Theoretically, ast_events can be used by any module as a binary
             representation of a Stasis message. Given the structure of an ast_event
             object, that information has to live in the core to be used universally.
             For example, defining the payload of a device state ast_event in
             res_corosync could result in an incompatible device state representation
             in another module.
         (2) Much of this representation already lived in the core, and was not
             easily extensible.
         (3) The code already existed. :-)
       * Stasis message types now have a message formatter that converts their
         payload to an ast_event object.
       * Stasis message forwarders now handle forwarding to themselves. Previously
         this would result in an infinite recursive call. Now, this simply creates a
         new forwarding object with no forwards set up (as it is the thing it is
         forwarding to). This is advantageous for res_corosync, as returning NULL
         would also imply an unrecoverable error. Returning a subscription in this
         case allows for easier handling of message types that are published directly
         to an aggregate topic that has forwarders.
      
      Review: https://reviewboard.asterisk.org/r/3486/
      
      ASTERISK-22912 #close
      ASTERISK-22372 #close
      ........
      
      Merged revisions 414330 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@414331 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      9cee08f5
Loading