Skip to content
Snippets Groups Projects
  1. Oct 06, 2009
  2. Oct 05, 2009
    • Kevin P. Fleming's avatar
      Allow non-compliant T.38 endpoints to be supportable via configuration option. · 20743ec0
      Kevin P. Fleming authored
      Many T.38 endpoints incorrectly send the maximum IFP frame size they can accept
      as the T38FaxMaxDatagram value in their SDP, when in fact this value is
      supposed to be the maximum UDPTL payload size (datagram size) they can accept.
      If the value they supply is small enough (a commonly supplied value is '72'),
      T.38 UDPTL transmissions will likely fail completely because the UDPTL packets
      will not have enough room for a primary IFP frame and the redundancy used for
      error correction. If this occurs, the Asterisk UDPTL stack will emit log messages
      warning that data loss may occur, and that the value may need to be overridden.
      
      This patch extends the 't38pt_udptl' configuration option in sip.conf to allow
      the administrator to override the value supplied by the remote endpoint and
      supply a value that allows T.38 FAX transmissions to be successful with that
      endpoint. In addition, in any SIP call where the override takes effect, a debug
      message will be printed to that effect. This patch also removes the
      T38FaxMaxDatagram configuration option from udptl.conf.sample, since it has not
      actually had any effect for a number of releases.
      
      In addition, this patch cleans up the T.38 documentation in sip.conf.sample
      (which incorrectly documented that T.38 support was passthrough only).
      
      (issue #15586)
      Reported by: globalnetinc
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@222110 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      20743ec0
    • Jeff Peeler's avatar
      Add a few missing events to analog_handle_event. · 10e8ee17
      Jeff Peeler authored
      The reported bug was actually only for pulsedigit, dtmfup, and dtmfdown
      handling. Also added recognition for fax events (just some verbose output) and
      fixed handling for the ec_disabled_event. In order to make comparing the analog
      version of events to the DAHDI events easier, the ordering has been changed to
      follow that of the DAHDI events.
      
      (closes issue #15924)
      Reported by: tzafrir
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@222108 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      10e8ee17
  3. Oct 02, 2009
  4. Oct 01, 2009
  5. Sep 30, 2009
  6. Sep 29, 2009
    • Mark Michelson's avatar
      Fix channel reference leak. · 01181a27
      Mark Michelson authored
      ast_cel_report_event would geet a reference to the
      bridged channel. However, certain return paths, such
      as if CEL was not enabled, would result in a reference
      leak. All return paths now properly unref the channel.
      
      (closes issue #15991)
      Reported by: mmichelson
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@220995 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      01181a27
    • Matthew Nicholson's avatar
      Blocked revisions 220907 via svnmerge · 75725abe
      Matthew Nicholson authored
      ........
        r220907 | mnicholson | 2009-09-29 15:14:29 -0500 (Tue, 29 Sep 2009) | 10 lines
        
        Avoid a deadlock in chanspy, just in case the spyee is masqueraded and chanspy_ds_chan_fixup() is called with the channel locked.
        
        
        (closes issue #15965)
        Reported by: atis
        Patches:
              chanspy-deadlock-fix1.diff uploaded by mnicholson (license 96)
        Tested by: atis
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@220928 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      75725abe
Loading