1. 19 Feb, 2018 1 commit
  2. 18 Feb, 2018 9 commits
  3. 23 Jan, 2018 10 commits
  4. 23 Oct, 2017 1 commit
    • bbabic's avatar
      q931.c: Fix subaddress finding octet 4. · a7a2245b
      bbabic authored
      Some switches have extended subaddress ie octet 3 encoding to be
      multi-octet.
      
      * Update dump and receive helper functions to search for the end of octet
      3 encoding to determine where octet 4 starts.
      
      ASTERISK-27342
      
      Change-Id: I5b2706f668e1a4664b020a58de41dad4cbc5c7e6
      a7a2245b
  5. 05 Dec, 2016 1 commit
    • Tzafrir Cohen's avatar
      Makefile: Use CPPFLAGS · c038af78
      Tzafrir Cohen authored
      * Include the value of CPPFLAGS in CFLAGS
      
      Change-Id: Id8e6f3a231bf7581f3f37576b9ee6849ed59540a
      c038af78
  6. 04 Oct, 2016 1 commit
    • Richard Mudgett's avatar
      q931.c: Lucent switch implementation bug workaround (Part 2) · f8e6096b
      Richard Mudgett authored
      Work around a bug in a Lucent switch implementation that sets the
      extension bit in octet 3 even though octet 3a is present.
      
      The same issue was seen in a NI2 switch implementation.  It was probably a
      Lucent switch configured for NI2 operation.  To avoid further surprises,
      I'm going to enable the work around for all North American switch types.
      
      PRI-183
      Reported by: Richard Mudgett
      
      Change-Id: I7eedbf68b7c3d9c868d9533012e4cea5142af281
      f8e6096b
  7. 20 Jul, 2016 1 commit
    • Richard Mudgett's avatar
      q931.c: Lucent switch implementation bug workaround. · d2585d6d
      Richard Mudgett authored
      A bug in a Lucent switch implementation sets the Connected Number
      information element octet 3 extension bit.  When set that means octet 3 is
      complete and thus there is no optional octet 3a.  However, the buggy
      switch still sends octet 3a.  The unexpected octet 3a is interpreted as
      the first octet 4 and thus the first character in the connected line
      number is a garbage character.
      
      * Work around the switch bug by checking octet 3 and the potential octet
      3a extension bits.  If they are both set then assume that octet 3a is
      actually present for the buggy switch types.
      
      PRI-183 #close
      Reported by: Richard Mudgett
      
      Change-Id: I378af37bfd852737a0bfe6263ef3473ea6acfbad
      d2585d6d
  8. 01 Jul, 2016 1 commit
  9. 24 Mar, 2016 1 commit
  10. 17 Mar, 2016 2 commits
    • Richard Mudgett's avatar
      q931.c: Fix DISCONNECT Progress Indicator ie handling. · 2952e957
      Richard Mudgett authored
      There are two scenarios that are exposed by DISCONNECT not initializing
      the progress indicator value before processing the message when the
      chan_dahdi.conf inbanddisconnect=yes option is set.
      
      1) If a DISCONNECT comes in without a Progress Indicator ie and an earlier
      message (such as SETUP-ACKNOWLEDGE or PROCEEDING) came in with the
      indicator #8 (Inband audio present) then the DISCONNECT would not cause an
      immediate hangup.  We would be letting the user hear the inband audio even
      though there isn't any.
      
      2) If a DISCONNECT message comes in with the indicator #8 (Inband audio
      present) and then later the DISCONNECT message is repeated without a
      Progress Indicator ie we would still ignore the second DISCONNECT to let
      the user hear inband audio even though it likely isn't there anymore.
      
      PRI-180 #close
      Reported by: Alexandr Dranchuk
      
      Change-Id: Ic88aafb45053146b5701d666e6212f7555573624
      2952e957
    • Richard Mudgett's avatar
      q931.c: Substitute PROGRESS for DISCONNECT with progress indicator #8 · 7da3366c
      Richard Mudgett authored
      When the pri_set_inbanddisconnect() option is enabled and the call has not
      been answered when a DISCONNECT with progress indicator #8 (Inband audio
      present) is received, then report the event as a PROGRESS with progress
      indicator #8 (Inband audio present) instead.  Substituting a PROGRESS
      event allows the upper layer to open the media path if it isn't already
      open so the user can hear the inband audio message.
      
      PRI-180
      Reported by: Alexandr Dranchuk
      
      Change-Id: I62313bf9cc1d2f3b0231f0c07a784717ddba0415
      7da3366c
  11. 16 Mar, 2016 1 commit
  12. 17 Feb, 2016 1 commit
    • Richard Mudgett's avatar
      q931.c: Tighten mandatory ie checks. · a9722804
      Richard Mudgett authored
      Libpri was lax in checking if a missing channel identification ie is
      mandatory for the SETUP ACKNOWLEDGE, PROCEEDING, ALERTING, and CONNECT
      messages.  That ie is mandatory when those messages are the first response
      to a SETUP message sent by the CPE side.
      
      * Made those messages check if a missing channel identification ie is
      mandatory and send a STATUS with cause 96 "Mandatory information element
      is missing" in response.
      
      Libpri did not care if a mandatory ie had a coding error.
      
      * Made coding errors in mandatory ie's send a STATUS with cause 100
      "Invalid information element contents" in response.
      
      * Fixed detection of coding errors in channel identification ie.
      
      SWP-8721
      SWP-8722
      
      
      git-svn-id: https://origsvn.digium.com/svn/libpri/branches/1.4@2337 2fbb986a-6c06-0410-b554-c9c1f0a7f128
      a9722804
  13. 09 Feb, 2016 1 commit
  14. 17 Nov, 2014 2 commits
  15. 04 Nov, 2014 1 commit
  16. 18 Aug, 2014 1 commit
  17. 16 Jun, 2014 3 commits
  18. 02 Jun, 2014 1 commit
  19. 12 May, 2014 1 commit