Asterisk 1.6 + DAHDI = no meetme?

Hi,

I’ve recently installed asterisk 1.6-current+addons 1.6-current+last DADHI full package on a test server.

All work wonderfull execpt one thing : meetme WANT zaptel in menuselect options of asterisk…but, correct me if i’m wrong, DAHDI is the successor of zaptel right ??

so why asterisk configurator still want zaptel if DAHDI is installed and functionnal and how to fix this ??

Thx in advance for you help,

John

I add CLI output in case of soething usefull in there :

    -- Executing [1011@interne:1] Answer("SIP/1001-08329a00", "") in new stack
    -- Executing [1011@interne:2] Authenticate("SIP/1001-08329a00", "1011") in new stack
    -- <SIP/1001-08329a00> Playing 'agent-pass.gsm' (language 'fr')
    -- <SIP/1001-08329a00> Playing 'auth-thankyou.gsm' (language 'fr')
[Aug 12 21:18:35] WARNING[10420]: pbx.c:2873 pbx_extension_helper: No application 'MeetMe' for extension (interne, 1011, 3)
  == Spawn extension (interne, 1011, 3) exited non-zero on 'SIP/1001-08329a00'

Zaptel cause Asterisk 1.4.x branch to hang when present (i suppose it will be the same with 1.6.x branch, and zaptel have no uninstall script so it’s a pain to clean) and DAHDI IS the successor of Zaptel so why meetme complain about zaptel when dahdi is installed ??

Ok I get it, simple :

DAHDI’s Timer is NOT implemented in Asterisk 1.6.0-beta8 (and probably not in 1.4.x branch, no more time to lose in testing) so NO MEETME for the moment…

Why release DAHDI if you cannot use it properly with core features of asterisk…

Delete this thread, i’ve switched to an Asterisk’s Fork with more features, integrated GUI for easy configuration and full support of core applications.

Your right, it doesn’t work!
Thanks for bringing this to my attention.
I’m going back to zaptel.