DAHDI Timing

Home » Asterisk Users » DAHDI Timing
Asterisk Users 5 Comments

Hi,

I have a box that I suspect had timing issues. I added a TE131 to see if that would help. Is there any way for me to verify that Dahdi is using the card for timing and not the kernel?

5 thoughts on - DAHDI Timing

  • I get:
    as2-c3-njr2*CLI> timing test Attempting to test a timer with 50 ticks per second. Using the ‘DAHDI’ timing module for this test. It has been 1019 milliseconds, and we got 51 timer ticks as2-c3-njr2*CLI>

    The question is if it’s using the card or the card or dahdi dummy (or whatever it’s called) or if the card itself is being used.

    On a box with no hardware I get almost the same output as1-c3-njr2*CLI> timing test Attempting to test a timer with 50 ticks per second. Using the ‘DAHDI’ timing module for this test. It has been 1016 milliseconds, and we got 51 timer ticks as1-c3-njr2*CLI>

  • Does this yield a clue?

    pbx10:newline:13:47:53> module show like tim Module Description Use Count Status Support Level res_timing_pthread.so pthread Timing Interface 0 Running extended res_timing_timerfd.so Timerfd Timing Interface 1 Running core

    (I don’t have any boxes using cards so I can’t test.)

    —
    Thanks in advance,
    ————————————————————————-
    Steve Edwards sedwards@sedwards.com Voice: +1-760-468-3867 PST
    https://www.linkedin.com/in/steve-edwards-4244281

    —

  • Yes but it does not tell me if the actual hardware is being used or if its using the kernel (in place of hardware).

  • Shaun,

    Thank you. It seems like it is:
    Span 1: WCT13x/0 “Wildcard TE131/TE133 Card 0” (MASTER) ESF/B8ZS RED
    ClockSource