Skip to content
Snippets Groups Projects
  1. Feb 23, 2009
  2. Feb 22, 2009
  3. Feb 21, 2009
  4. Feb 20, 2009
  5. Feb 19, 2009
  6. Feb 18, 2009
    • Tilghman Lesher's avatar
      5b220b3e
    • Steve Murphy's avatar
      Merged revisions 177225 via svnmerge from · 6c2a537c
      Steve Murphy authored
      https://origsvn.digium.com/svn/asterisk/branches/1.4
      
      ........
        r177225 | murf | 2009-02-18 15:43:14 -0700 (Wed, 18 Feb 2009) | 34 lines
        
        This patch fixes a regression of sorts that was introduced in 
        rev 24425.
        
        It basically fixes AST-190/ABE-1782.
        
        What was wrong: the user has 6000 extensions in one context; and
        then 6000 contexts, one per extension. The parser could only handle
        about 4893 of the 6000 extens in the single context.
        
        This was due to the regression I mentioned. To get rid of
        shift/reduce conflicts, Luigi set up right-recursive lists
        for globals, context elements, switch lists, and statements.
        Right recursive lists got rid of the warnings, but instead, they
        use up a tremendous amount of stack space when the lists are long.
        
        I saw this a few years back, and resolved not to fix it until
        someone complained. That day has arrived!
        
        After the changes were made, I ran the regression test suite,
        and there were no problems.
        
        I took the test case the user provided, and added 100,000 
        extensions to the single context, that already had 6,000 extens
        in it. (I'll see your 6, and raise you 100!) It takes a few minutes
        to read it all in, check it and generate code for it, but no
        problems.
        
        So, I think I can say that fundamentally, there are no longer
        any limits on the number of items you can place in contexts,
        statement blocks, switches, or globals, beyond your virt mem
        constraints.
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@177286 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      6c2a537c
    • Kevin P. Fleming's avatar
      fix two very minor bugs: if anyone ever uses SLINEAR16 as a format in RTP,... · b2d959c7
      Kevin P. Fleming authored
      fix two very minor bugs: if anyone ever uses SLINEAR16 as a format in RTP, ensure that the samples are byte-swapped to network order if needed. also, when a smoother is operating on a format that has a sample rate other than 8000 samples per second, use the proper sample rate for computing delivery timestamps.
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@177229 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      b2d959c7
    • David Vossel's avatar
      Locking issue in action_bridge and bridge_exec · e30d2c1d
      David Vossel authored
      action_bridge() and bridge_exec() both search for the channels to bridge to, and then immediately drop the lock.  Instead, they should hold the lock until the masquerade is complete.  This will guarantee the channel remains and prevent any other weirdness from occurring.  In action_bridge() some more weirdness comes into play.  Both channels are needlessly locked at the same time and perform the exact same logic.  It makes sense from a coding organizational standpoint, but could cause a theoretical deadlock so I split the code up.  There is an issue associated with this, but since its a rather complicated thing to reproduce I'm not certain this alone will close it.
      
      issue# 14296
      Review: http://reviewboard.digium.com/r/167/
      
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@177226 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      e30d2c1d
    • Jeff Peeler's avatar
      Modify h323 to build against PTLib as well as the older PWLib · c8fe75da
      Jeff Peeler authored
      Several changes in PTLib have occurred requiring build time detection. Changes
      accounted for include the library name change, config option change, install
      location change, and a boolean type change which is handled by ast_ptlib.h.
      Also, the sed check has been modified to properly work with autoconf >= 2.62.
      
      (closes issue #14224)
      Reported by: bergolth
      Patches:
            asterisk-autoconf-sed.patch uploaded by bergolth (license 661)
            asterisk-pwlib-v3.patch uploaded by bergolth (license 661)
      Tested by: jpeeler
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@177162 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      c8fe75da
    • Jeff Peeler's avatar
      Blocked revisions 177160 via svnmerge · 0fb9712a
      Jeff Peeler authored
      ........
        r177160 | jpeeler | 2009-02-18 14:06:45 -0600 (Wed, 18 Feb 2009) | 15 lines
        
        Modify h323 to build against PTLib as well as the older PWLib
        
        Several changes in PTLib have occurred requiring build time detection. Changes
        accounted for include the library name change, config option change, install
        location change, and a boolean type change which is handled by ast_ptlib.h.
        Also, the sed check has been modified to properly work with autoconf >= 2.62.
        
        (closes issue #14224)
        Reported by: bergolth
        Patches:
              asterisk-autoconf-sed.patch uploaded by bergolth (license 661)
              asterisk-pwlib-v3.patch uploaded by bergolth (license 661)
        Tested by: jpeeler
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@177161 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      0fb9712a
    • Russell Bryant's avatar
      Re-add 'o' option to MeetMe, reverting rev 62297. · 8065dc57
      Russell Bryant authored
      Enabling this option by default proved to be a bad idea, as the talker detection
      is not very reliable.  So, make it optional again, and off by default.
      
      (issue #13801)
      Reported by: justdave
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@177101 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      8065dc57
    • Tilghman Lesher's avatar
      Merged revisions 177096 via svnmerge from · 39d57392
      Tilghman Lesher authored
      https://origsvn.digium.com/svn/asterisk/branches/1.4
      
      ........
        r177096 | tilghman | 2009-02-18 12:30:38 -0600 (Wed, 18 Feb 2009) | 2 lines
        
        Document the return value of the update method (as requested on -dev list)
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@177098 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      39d57392
    • Doug Bailey's avatar
      79493453
    • Joshua Colp's avatar
      Fix ordering of output for a ChannelUpdate manager event. · 2ff89e81
      Joshua Colp authored
      (closes issue #14497)
      Reported by: vinsik
      Patches:
            chan_update_fix-chan_sip.c.diff uploaded by vinsik (license 623)
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@177005 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      2ff89e81
    • Doug Bailey's avatar
    • Steve Murphy's avatar
      · 0fe1df19
      Steve Murphy authored
      This patch fixes merge_contexts_and_delete so it does not deadlock when hints are present.
      
      Reason: when I re-engineered the merge_and_delete func to
      reduce its lock time, I failed to notice that the 
      functions it calls still also do locking as before.
      This leads to deadlocks on dialplan reloads, when
      there are actually living, subscribed hints registered
      in the system.
      
      While the reporter come across this problem while using
      AEL, I might note that these deadlocks should also happen
      if extensions.conf were used.
      
      Here I added these routines to pbx.c:
      
      ast_add_extension_nolock
      add_pri_lockopt
      ast_add_extension2_lockopt
      find_context
      add_hint_nolock
      
      All of the above routines are static and restricted
      to be used only within pbx.c, and more specifically
      within the merge_contexts_and_delete routine.
      
      They are pretty much the same as their counterparts
      except they don't lock contexts or hints.
      
      Most of them now do the real work of their
      name-alike, with optional locking via extra arguments,
      and are called by their name-alike. The goal was to
      have the original functions so they would behave
      exactly as before.
      
      Both PJ and I tested these fixes, and the deadlocking
      problem is no longer encountered.
      
      (closes issue #14357)
      Reported by: pj
      Patches:
            14357.diff uploaded by murf (license 17)
      Tested by: pj, murf
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@176943 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      0fe1df19
Loading