More interesting-ness...
Okay so I believe I've got my system using the DAHDI timing hardware now for asterisk (Sangoma UT50). Here's this:
Code:
[FONT=Fixedsys]pbx*CLI> module show like timing
Module Description Use Count
res_timing_dahdi.so DAHDI Timing Interface 1
res_timing_pthread.so pthread Timing Interface 1
2 modules loaded[/FONT]
You'll note that something is still hooking into
pthread. I believe it's
res_musiconhold.c. I get tons of complaints in
/var/log/asterisk/full if I try to spin up asterisk with pthread timing disabled (
noload=>res_timing_pthread.so).
res_musiconhold.c is littered with references to pthread, so I think it needs it enabled. Perhaps Digium did this to avoid the DAHDI timer requirements of yore (they rewrote MeetMe afaik as well for that reason...) Still not sure how to see which asterisk apps are using which timing modules (anyone know how to do that?)
I made one additional "nice" discovery. Streaming MOH was previously NOT working with
res_timing_dahdi enabled. I played around with the
/etc/asterisk/modules.conf a bit and despite the suggestions of others to make this change:
noload => res_timing_dahdi.so
I instead found that if I commented out those explicit load= commands in the "Ensure that format_* modules are loaded before res_musiconhold" section:
;load => format_mp3.so
;load => res_musiconhold.so
Instead I just allow the modules to load in the order that they normally would, and I can now successfully load DAHDI and
also still have working streaming MOH. Hoo-rah!
This is with ast 1.8.2-rc1.