[asterisk-bugs] [DAHDI-linux 0013930]: dahdi_dummy does not tick on some systems

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13930 
====================================================================== 
Reported By:                tzafrir
Assigned To:                
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   13930
Category:                   dahdi_dummy
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2008-11-19 08:34 CST
Last Modified:              2009-01-27 04:38 CST
====================================================================== 
Summary:                    dahdi_dummy does not tick on some systems
Description: 
On some systems dahdi_dummy (or ztdummy, in the case of Zaptel) fails to
"tick" DAHDI and hence DAHDI does not provide a working timing source.

Indications that DAHDI (Zaptel) provides no timing source:

1. dahdi_test (zttest) does not give an error on startup, but hangs.
2. Asterisk >= 1.4.20 fails to start, and gives the ugly "no timing
source" error message:

ERROR[10981]: asterisk.c:3036 main: Asterisk has detected a problem
with your DAHDI configuration and will shutdown for your protection.
You have options:
        1. You only have to compile DAHDI support into Asterisk if you
need it.  One option is to recompile without DAHDI support.
        2. You only have to load DAHDI drivers if you want to take
advantage of DAHDI services.  One option is to unload DAHDI modules if
you don't need them.
        3. If you need DAHDI services, you must correctly configure
DAHDI.

An indication that dahdi_dummy should be the timing source for dahdi could
be:

  lsmod | grep ^dahdi
  dahdi                 231888  1 dahdi_dummy

Or to see that /proc/dahdi/1 is dahdi_dummy and is listed as "MASTER".


I have seen various suggestions on how to solve this. None seems to be a
silver bullet. 
====================================================================== 

---------------------------------------------------------------------- 
 (0098832) nullpointer (reporter) - 2009-01-27 04:38
 http://bugs.digium.com/view.php?id=13930#c98832 
---------------------------------------------------------------------- 
yan83330-
that is exactly what i experience; if i start asterisk without DAHDI
running, it works fine. however, if DAHDI is running first, asterisk will
not start, and will give the error messages you describe.

also worth noting, if i start asterisk, AND THEN START DAHDI, asterisk
will work for about 30 seconds of a call, then will lock up (silence).

tzafrir -
i do still have the problem on my dual proc 64 bit AMD box.

i moved to a (literally) $20 32 bit INTEL dell desktop for development,
just to keep moving.

i'm guessing its a hardware issue - i do, however, intend to circle back
around, wipe the 64 bit box, and give it another shot to see if i can get
it working (maybe i did something dumb in the install process?). i also
have to wonder if using an even older SPANDSP might remedy the situation?

thanks for following up though, i do appreciate it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-27 04:38 nullpointer    Note Added: 0098832                          
======================================================================