1. 17 Apr, 2013 1 commit
    • Shaun Ruffell's avatar
      dahdi_scan: Support gaps in channel numbering. · 17027df0
      Shaun Ruffell authored
      If, via the sysfs attributed introduced in DAHDI-Linux 2.5.0, a user has
      configured spans that do not have contiguous channel numbers, dahdi_scan will
      not print several of the span attributes in addition to a bad basechan number.
      This patch allows dahdi_scan to try and get the basechan for a span from sysfs
      as opposed to calculating based on the number of channels in the previous span
      Signed-off-by: default avatarShaun Ruffell <sruffell@digium.com>
  2. 10 Nov, 2010 1 commit
  3. 25 Oct, 2010 1 commit
    • Russ Meyerriecks's avatar
      Fixed up the loss of crc4-multiframe alignment logic · 3140dfc4
      Russ Meyerriecks authored
      Loss of crc4-multiframe alignment on an E1 link is not a condition which
      brings the span down. The span will continue to run as long as it can
      maintain double frame alignment. Because of this, we cannot place the
      LMFA alarm in the usual spaninfo.alarms member, due to userspace
      programs using this as a catch-all for a span being up or down.
      We can detect the alarm by watching the frame error counter (fecount).
      If it continuously increments, the span is configured for crc4, and the
      span remains OK (alarms = 0), then we are in loss of crc4-multiframe
      In order to test this alarm, you'll need to synthesize a loss of crc4
      alignment on the span. You can usually do this by configuring the local
      span to use crc4 and the remote end to not use crc4. I used the Fireberd
      6000 in my lab to do this.
      dahdi-743 & dahdi-420
      Acked-by: default avatarShaun Ruffell <sruffell@digium.com>
      git-svn-id: http://svn.astersk.org/svn/dahdi/tools/trunk@9458 17933a7a-c749-41c5-a318-cba88f637d49
  4. 18 Aug, 2010 1 commit