1. 18 Feb, 2018 3 commits
  2. 23 Jan, 2018 10 commits
  3. 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
  4. 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
  5. 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
  6. 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
  7. 01 Jul, 2016 1 commit
  8. 24 Mar, 2016 1 commit
  9. 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
  10. 16 Mar, 2016 1 commit
  11. 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
  12. 09 Feb, 2016 1 commit
  13. 17 Nov, 2014 2 commits
  14. 04 Nov, 2014 1 commit
  15. 18 Aug, 2014 1 commit
  16. 16 Jun, 2014 3 commits
  17. 02 Jun, 2014 1 commit
  18. 12 May, 2014 1 commit
  19. 18 Apr, 2014 1 commit
    • Richard Mudgett's avatar
      libpri: Make TE-PTP mode respond to MDL TEI check requests. · 13beaacc
      Richard Mudgett authored
      Some BRI devices in France insist on checking TEI's when in point-to-point
      mode.  If they don't get a response for TEI 0 they drop layer 1 even
      though libpri keeps trying to bring layer 2 up.
      
      * Made q921_mdl_receive() handle TEI check request messages in TE-PTP
      mode.  Had to change q921_mdl_send()/Q921_INIT() because the PTP modes do
      not setup a link structure specifically for MDL as the PTMP modes do.
      
      * Fixed q921_tei_check()/t201_expire() to check TEI's even if the network
      side doesn't have any assigned.  This should make TE's that request the
      TEI verify procedure (Q.921 Section 5.3.5) happy when the network side
      doesn't have any TEI's allocated.
      
      PRI-165
      Reported by: Denis Alberto Martinez
      Patches:
            jira_pri_165_ptp_respond_tei_check.patch (license #5621) patch uploaded by rmudgett
      Review: https://reviewboard.asterisk.org/r/3434/
      
      
      
      git-svn-id: https://origsvn.digium.com/svn/libpri/branches/1.4@2318 2fbb986a-6c06-0410-b554-c9c1f0a7f128
      13beaacc
  20. 28 Mar, 2013 1 commit
    • Richard Mudgett's avatar
      Fix hole in layer2_persistence option for TE PTMP links. · 84b2560d
      Richard Mudgett authored
      If the network stops responding, according to Q.921 we are supposed to
      remove the TEI.  With the layer2_persistence option enabled, we are
      supposed to keep trying to bring layer 2 back up.  Unfortunately, when the
      network stops responding, we stopped the restart timer and removed the
      TEI.  As a result, layer 2 does not immediately come back up.
      
      * Made not stop the restart timer if we are removing the TEI on the CPE
      side.  Also handle the timer expiration in relevant unassigned TEI states.
      
      (closes issue LIBPRI-72)
      Reported by: Trey Blancher
      Patches:
            jira_dahdi_1001_libpri_v1.4.patch (license #5621) patch uploaded by rmudgett
      
      
      git-svn-id: https://origsvn.digium.com/svn/libpri/branches/1.4@2315 2fbb986a-6c06-0410-b554-c9c1f0a7f128
      84b2560d
  21. 10 Dec, 2012 1 commit
  22. 13 Nov, 2012 2 commits
  23. 29 Oct, 2012 1 commit
  24. 26 Sep, 2012 1 commit