I definitely have dahdi-complete installed,
root@pbx1:~ $ /etc/init.d/dahdi start
Loading DAHDI hardware modules:
dahdi_dummy: [ OK ]
No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg: [ OK ]
although I get the feeling this is "out of freepbx's hands".
[Jun 14 00:21:53] VERBOSE app_meetme.c: -- Created MeetMe conference 1023 for conference '500'
[Jun 14 00:21:53] WARNING app_meetme.c: No DAHDI channel available for conference, user introduction disabled (is chan_dahdi loaded?)
After doing some bumbling on the asterisk.org forums, I have come up with this
- digium dev has simply pulled the rug out from under us
- https://issues.asterisk.org/view.php?id=17959 says that the core of dahdi supposedly handles all timing, and dahdi_dummy has been removed, the documentation backs this up
BUT at the bottom it gives an entirely contradicting disclaimer that meetme is definitely dependant on dahdi_dummy.
The thing that utterly drives me mad
- I have this running on VZ containers and Xen also, and both have meetme that does work, and that does NOT work (meaning lacking dahdi_dummy/pseudo in asterisk), using asterisk 1.8.4, and 1.4.3x
- and nobody can point me to what in the config or loaded modules makes this actually work or break.