Skip to content
Snippets Groups Projects
  1. Nov 21, 2013
  2. Nov 19, 2013
  3. Nov 16, 2013
  4. Nov 15, 2013
  5. Nov 14, 2013
  6. Nov 13, 2013
  7. Nov 12, 2013
  8. Nov 11, 2013
  9. Nov 08, 2013
  10. Nov 07, 2013
    • Jonathan Rose's avatar
      PJSIP: Improve error handling in digest authenticator · 3c645e85
      Jonathan Rose authored
      Previously, regardless of whether failure to authenticate was due to
      lacking any authentication or actually failing authentication, the
      Digest Authenticator would simply return that a challenge was still
      needed. It will continue to do that when no authentication information
      is in the received SIP digest, but when authentication information
      is present and does not pass authentication, that will be treated as
      an authentication error. This is to ensure that PJSIP will issue
      security events indicated failed auths.
      ........
      
      Merged revisions 402537 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@402538 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      3c645e85
    • David M. Lee's avatar
      ari: User better nicknames for ARI operations · 7d0d1a1e
      David M. Lee authored
      While working on building client libraries from the Swagger API, I
      noticed a problem with the nicknames.
      
          channel.deleteChannel()
          channel.answerChannel()
          channel.muteChannel()
      
      Etc. We put the object name in the nickname (since we were generating C
      code), but it makes OO generators redundant.
      
      This patch makes the nicknames more OO friendly. This resulted in a lot
      of name changing within the res_ari_*.so modules, but not much else.
      
      There were a couple of other fixed I made in the process.
      
       * When reversible operations (POST /hold, POST /unhold) were made more
         RESTful (POST /hold, DELETE /unhold), the path for the second operation
         was left in the API declaration. This worked, but really the two
         operations should have been on the same API.
       * The POST /unmute operation had still not been REST-ified.
      
      Review: https://reviewboard.asterisk.org/r/2940/
      ........
      
      Merged revisions 402528 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@402529 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      7d0d1a1e
  11. Nov 06, 2013
    • Kevin Harwell's avatar
      app_queue: crash if first agent is "busy" · cdfbc02d
      Kevin Harwell authored
      If the first agent/member (via CLI "queue show") in a queue is "busy" (dnd,
      circuit busy, etc...) and no agents answered then app_queue would crash.
      This occurred because while the calling of agent(s) remained valid the channel
      on "busy" agent would be set to NULL and then later dereferenced upon a second
      "rna" function call.  The original intention of the code is to have only valid
      "call attempt" objects (channels != NULL) checked while attempting to call
      agent(s).  It does this by building a "call_next" list of valid "call attempt"
      objects.  In the case of the "busy" agent subsequent builds of the valid "call
      attempt" list would sometimes include (the case mentioned above) an invalid
      "call attempt" object.
      
      The fix was to make sure the "call attempt" list was appropriately built on
      every iteration.  A NULL sanity check was also added at the original offending
      spot of the crash just in case another one slipped by somehow.
      
      (closes issue ASTERISK-22644)
      Reported by: Marco Signorini
      Review: https://reviewboard.asterisk.org/r/2983/
      ........
      
      Merged revisions 402517 from http://svn.asterisk.org/svn/asterisk/branches/12
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@402518 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      cdfbc02d
Loading