Skip to content
Snippets Groups Projects
  1. Sep 07, 2016
  2. Sep 06, 2016
    • zuul's avatar
    • zuul's avatar
    • zuul's avatar
      eac6eef4
    • zuul's avatar
    • zuul's avatar
      b5e4445b
    • zuul's avatar
    • George Joseph's avatar
      build: Add download capability for external packages · 6caf6bcd
      George Joseph authored
      The DPMA and g729a, silk, siren7 and siren14 codecs hosted at
      http://downloads.digium.com/pub/telephony/ are now listed in the
      "External" sections of the "Resource Modules" and "Codec Translators"
      pages in menuselect.  Any that are selected will automatically be
      downloaded and installed when "make install" is run.  Their LICENSE and
      README (if avaialble) files will be installed to
      ASTVARLIBDIR/documentation/thirdparty/<product_name>.
      
      Example use with codecs:
      
      The codecs/codecs.xml file is a menuselect style xml file that lists
      the codecs to be included.  Their support levels are 'external', which
      triggers the download and install, and defaultenabled is no.  Also
      because codec_g729a is actually in a directory named codec_g729 on the
      download server, the newly added 'member_data' element is used to
      override the default of the directory name being the package name.  You
      can use the 'directory_name' attribute to keep default base URL
      (http://downloads.digium.com/pub/telephony/) but use the new directory,
      or you use the 'remote_url' attribute to specify a full URL to the
      download directory.  In this case, you must still follow the same
      subdirectory naming conventions as that used for the packages located
      at 'http://downloads.digium.com/pub/telephony'.
      
      A new configure option '--with-externals-cache' was added and like
      '--with-sounds-cache' it allows the installer to cache tarballs so
      they're not downloaded every time.
      
      To assist with the download and install process, each external package
      now has a manifest.xml file that, among other things, contains a package
      version and checksums for each file in the tarball.  The manifest is
      saved to both the cache directory and ASTMODDIR and together with the
      manifest.xml on the downloads site, tells the install scripts whether
      a download and/or update is needed.
      
      bash and xmlstarlet are required for downloader operation.  If they're
      not installed, the external items in menuselect will be unavailable.
      
      Change-Id: Id3dcf1289ffd3cb0bbd7dfab3cafbb87be60323a
      6caf6bcd
    • Joshua Colp's avatar
    • zuul's avatar
      d57242a1
    • Walter Doekes's avatar
      chan_sip: Don't refuse calls with "optional crypto"; fall back to RTP. · d80b2856
      Walter Doekes authored
      Certain SNOM phones send so-called "optional crypto" in their SDP body.
      Regular SRTP setup looks like this:
      
          m=audio 64620 RTP/SAVP 8 0 9 99 3 18 4 101
          a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:...
      
      SNOM-style "optional crypto" looks like this:
      
          m=audio 61438 RTP/AVP 8 0 9 99 3 18 4 101
          a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:...
      
      A crypto line is supplied, but the m-line does not have SAVP.
      
      When res_srtp.so is *not* loaded, then chan_sip.so treats the optional
      crypto as regular RTP, but when res_srtp.so *is* loaded, it refuses the
      incoming call with the following message:
      
          WARNING: process_sdp: Failed to receive SDP offer/answer with
          required SRTP crypto attributes for audio
      
      For platforms that want to start providing SRTP this presents a
      compatibility problem.
      
      This changeset lets chan_sip handle the SDP as if no crypto-line was
      supplied: i.e. accept the call as regular RTP, just like it did before
      res_srtp was loaded.
      
      Now you'll get this informative warning instead:
      
          WARNING: Ignoring crypto attribute in SDP because RTP transport is
          insecure
      
      ASTERISK-23989 #close
      Reported by: Olle Johansson
      
      Change-Id: I91a15ae05a0296e398d6b65f53bb11afde1d80e2
      d80b2856
  3. Sep 04, 2016
  4. Sep 02, 2016
  5. Sep 01, 2016
    • zuul's avatar
    • Joshua Colp's avatar
    • Michael Kuron's avatar
      app_mp3: Use correct buffer size and the same sample rate as the channel · 48fd4c81
      Michael Kuron authored
      Previously, the buffer used for MP3 streamed from HTTP servers had a size of
      1 MB. For 8 kHz mono audio at 16 bit resolution, such a buffer covers about 1
      minute. Only when the buffer is full does audio start to play.
      For MP3 files streamed from a server, that is usually not a big deal as long as
      the connection to the server is fast enough to supply that much data within a
      second or two. For MP3 live streams however, it takes 1 minute to download 1
      minute of audio, so without this change, app_mp3 wasn't really usable for MP3
      live streams.
      This commit changes the buffer size so that it covers 6 seconds of an MP3 file
      streamed from a server and 0.5 seconds of an MP3 live stream. The latter is
      identified by the use of a .m3u file extension.
      
      app_mp3 so far only supported 8 kHz audio.
      Now it always runs at the sample rate of the channel.
      
      ASTERISK-26085 #close
      
      Change-Id: Id1ee274733cd804a0edecf7450329b72f1235af0
      48fd4c81
  6. Aug 31, 2016
    • Jean Aunis's avatar
      resource_channels.c: add hangup reason "answered_elsewhere". · 91993eba
      Jean Aunis authored
      In ARI, the channels API allows to hangup a channel with a hangup reason.
      This commit adds a new reason "answered_elsewhere".
      When using a SIP channel, this will eventually allow Asterisk to add a proper
      "Reason" header to a CANCEL message.
      
      ASTERISK-26321
      
      Change-Id: Ia97675bd4acd6a7f58eb467953dfb94559f6583d
      91993eba
  7. Aug 30, 2016
    • Alexei Gradinari's avatar
      res_pjsip: qualify/unqualify added/deleted realtime endpoints · faf9bdeb
      Alexei Gradinari authored
      If the PJSIP endpoint's AOR with the permanent contact
      was deleted from the realtime storage the res_pjsip module
      continues trying to qualify this contact.
      The error 'Unable to find an endpoint to qualify contact'
      appeares every 'qualify_frequency' seconds.
      This patch deletes this contact in this case.
      
      The PJSIP endpoint's AOR with the permanent contact
      is never qualified if it is added to realtime storage
      after asterisk started.
      This patch adds qualifying for the AOR's permanent contacts
      on the first handling of this AOR.
      
      ASTERISK-26319 #close
      
      Change-Id: Ib93dded9121edb113076903d1aa95402f799f8fe
      faf9bdeb
    • zuul's avatar
      e7d06a80
  8. Aug 29, 2016
Loading