Skip to content
Snippets Groups Projects
  1. May 15, 2014
  2. May 12, 2014
  3. May 09, 2014
  4. May 08, 2014
  5. May 07, 2014
  6. Apr 21, 2014
  7. Apr 19, 2014
  8. Apr 18, 2014
  9. Apr 15, 2014
  10. Apr 11, 2014
  11. Apr 09, 2014
  12. Apr 08, 2014
  13. Apr 07, 2014
  14. Apr 01, 2014
  15. Mar 27, 2014
  16. Mar 20, 2014
  17. Mar 17, 2014
  18. Mar 12, 2014
  19. Mar 07, 2014
    • Scott Griepentrog's avatar
      uniqueid: channel linkedid, ami, ari object creation with id's · 80ef9a21
      Scott Griepentrog authored
      Much needed was a way to assign id to objects on creation, and
      much change was necessary to accomplish it.  Channel uniqueids
      and linkedids are split into separate string and creation time
      components without breaking linkedid propgation.  This allowed
      the uniqueid to be specified by the user interface - and those
      values are now carried through to channel creation, adding the
      assignedids value to every function in the chain including the
      channel drivers. For local channels, the second channel can be
      specified or left to default to a ;2 suffix of first.  In ARI,
      bridge, playback, and snoop objects can also be created with a
      specified uniqueid.
      
      Along the way, the args order to allocating channels was fixed
      in chan_mgcp and chan_gtalk, and linkedid is no longer lost as
      masquerade occurs.
      
      (closes issue ASTERISK-23120)
      Review: https://reviewboard.asterisk.org/r/3191/
      ........
      
      Merged revisions 410157 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@410158 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      80ef9a21
  20. Mar 06, 2014
  21. Feb 28, 2014
  22. Feb 21, 2014
  23. Feb 20, 2014
  24. Feb 10, 2014
  25. Feb 01, 2014
  26. Jan 31, 2014
    • Matthew Jordan's avatar
      CDRs: fix a variety of dial status problems, h/hangup handler creating CDRs · 66c46fba
      Matthew Jordan authored
      This patch fixes a number of small-ish problems that were noticed when
      witnessing the records that the FreePBX dialplan produces:
      (1) Mid-call events (as well as privacy options) have the ability to change the
          overall state of the Dial operation after the called party answers. This
          means that publishing the DialEnd event when the called party is premature;
          we have to wait for the execution of these subroutines to complete before
          we can signal the overall status of the DialEnd. This patch moves that
          publication and adds handlers for the mid-call events.
      (2) The AST_FLAG_OUTGOING channel flag is cleared if an after bridge goto
          datastore is detected. This flag was preventing CDRs from being recorded
          for all outbound channels that had a 'continue' option enabled on them by
          the Dial application.
      (3) The CDR engine now locks the 'Dial' application as being the CDR
          application if it detects that the current CDR has entered that app. This
          is similar to the logic that is done for Parking. In general, if we entered
          into Dial, then we want that CDR to record the application as such - this
          prevents pre-dial handlers, mid-call handlers, and other shenaniganry
          from changing the application value.
      (4) The CDR engine now checks for the AST_SOFTHANGUP_HANGUP_EXEC in more places
          to determine if the channel is in hangup logic or dead. In either case, we
          don't want to record changes in the channel.
      (5) The default option for "endbeforehexten" has been changed to "yes". In
          general, you don't want to see CDRs in the 'h' exten or in hangup logic.
          Since the semantics of that option changed in 12, it made sense to update
          the default value as well.
      (6) Finally, because we now have the ability to synchronize on the messages
          published to the CDR topic, on shutdown the CDR engine will now synchronize
          to the messages currently in flight. This helps to ensure that all
          in-flight CDRs are written before shutting down.
      
      (closes issue ASTERISK-23164)
      Reported by: Matt Jordan
      
      Review: https://reviewboard.asterisk.org/r/3154
      ........
      
      Merged revisions 407084 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@407085 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      66c46fba
    • Matthew Jordan's avatar
      app_dial: Allow macro/gosub pre-bridge execution to occur on priorities · f9229127
      Matthew Jordan authored
      The parsing for the destination of the macro/gosub uses the '^' character to
      separate out context, extension, and priority. However, the logic for the
      macro/gosub execution was written such that it would only do the actual
      macro/gosub jump if a '^' character existed. This doesn't apply when the
      macro/gosub jump occurs in a priority/priority label. This patch changes
      the logic so that the parsing still occurs, but the jump will occur even
      for priorities/priority labels.
      
      (issue ASTERISK-23164)
      
      Review: https://reviewboard.asterisk.org/r/3154
      ........
      
      Merged revisions 407041 from http://svn.asterisk.org/svn/asterisk/branches/1.8
      ........
      
      Merged revisions 407074 from http://svn.asterisk.org/svn/asterisk/branches/11
      ........
      
      Merged revisions 407082 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@407083 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      f9229127
    • Richard Mudgett's avatar
      ChanSpy: Add ability to specify channel uniqueids as well as channel names. · aeb44666
      Richard Mudgett authored
      * Made ChanSpy accept a channel uniqueid or a fully specified channel name
      as the chanprefix parameter if the 'u' option is specified.
      
      (closes issue AFS-42)
      
      Review: https://reviewboard.asterisk.org/r/3160/
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@407033 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      aeb44666
  27. Jan 22, 2014
  28. Jan 17, 2014
  29. Jan 14, 2014
    • Richard Mudgett's avatar
      verbosity: Fix performance of console verbose messages. · 828f339a
      Richard Mudgett authored
      The per console verbose level feature as previously implemented caused a
      large performance penalty.  The fix required some minor incompatibilities
      if the new rasterisk is used to connect to an earlier version.  If the new
      rasterisk connects to an older Asterisk version then the root console
      verbose level is always affected by the "core set verbose" command of the
      remote console even though it may appear to only affect the current
      console.  If an older version of rasterisk connects to the new version
      then the "core set verbose" command will have no effect.
      
      * Fixed the verbose performance by not generating a verbose message if
      nothing is going to use it and then filtered any generated verbose
      messages before actually sending them to the remote consoles.
      
      * Split the "core set debug" and "core set verbose" CLI commands to remove
      the per module verbose support that cannot work with the per console
      verbose level.
      
      * Added a silent option to the "core set verbose" command.
      
      * Fixed "core set debug off" tab completion.
      
      * Made "core show settings" list the current console verbosity in addition
      to the root console verbosity.
      
      * Changed the default verbose level of the 'verbose' setting in the
      logger.conf [logfiles] section.  The default is now to once again follow
      the current root console level.  As a result, using the AMI Command action
      with "core set verbose" could again set the root console verbose level and
      affect the verbose level logged.
      
      (closes issue AST-1252)
      Reported by: Guenther Kelleter
      
      Review: https://reviewboard.asterisk.org/r/3114/
      ........
      
      Merged revisions 405431 from http://svn.asterisk.org/svn/asterisk/branches/11
      ........
      
      Merged revisions 405432 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@405436 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      828f339a
  30. Jan 12, 2014
  31. Jan 09, 2014
    • Matthew Jordan's avatar
      app_confbridge: Fix crash caused when waitmarked/marked users leave together · 50b2d6ee
      Matthew Jordan authored
      When waitmarked users join a ConfBridge, the conference state is transitioned
      from EMPTY -> INACTIVE. In this state, the users are maintined in a waiting
      users list. When a marked user joins, the ConfBridge conference transitions
      from INACTIVE -> MULTI_MARKED, and all users are put onto the active list of
      users. This process works correctly.
      
      When the marked user leaves, if they are the last marked user, the MULTI_MARKED
      state does the following:
      (1) It plays back a message to the bridge stating that the leader has left the
          conference. This requires an unlocking of the bridge.
      (2) It moves waitmarked users back to the waiting list
      (3) It transitions to the appropriate state: in this case, INACTIVE
      
      However, because it plays the prompt back to the bridge before moving the users
      and before finishing the state transition, this creates a race condition: with
      the bridge unlocked, waitmarked users who leave the conference (or are kicked
      from it) can cause a state transition of the bridge to another state before
      the conference is transitioned to the INACTIVE state. This causes the state
      machine to get a bit wonky, often leading to a crash when the MULTI_MARKED state
      attempts to conclude its processing.
      
      This patch fixes this problem:
      (1) It prevents kicked users from being kicked again. That's just a nicety.
      (2) More importantly, it fixes the race condition by only playing the prompt
          once the state has transitioned correctly to INACTIVE. If waitmarked users
          sneak out during the prompt being played, no harm no foul.
      
      Review: https://reviewboard.asterisk.org/r/3108/
      
      Note that the patch committed here is essentially the same as uploaded by
      Simon Moxon on ASTERISK-22740, with the addition of the double kick prevention.
      
      (closes issue AST-1258)
      Reported by: Steve Pitts
      
      (closes issue ASTERISK-22740)
      Reported by: Simon Moxon
      patches:
        ASTERISK-22740.diff uploaded by Simon Moxon (license 6546)
      ........
      
      Merged revisions 405215 from http://svn.asterisk.org/svn/asterisk/branches/11
      ........
      
      Merged revisions 405216 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@405217 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      50b2d6ee
    • Walter Doekes's avatar
      "Minimun" typo. · c94e4ee1
      Walter Doekes authored
      ........
      
      Merged revisions 405160 from http://svn.asterisk.org/svn/asterisk/branches/1.8
      ........
      
      Merged revisions 405161 from http://svn.asterisk.org/svn/asterisk/branches/11
      ........
      
      Merged revisions 405162 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@405163 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      c94e4ee1
Loading