Conference call error

Please help on the error show below. I having the error when try to make call to conference.

-- <SIP/9844-00000002> Playing 'enter-conf-pin-number.gsm' (language 'en')
-- User entered '1111'
-- Executing [8888@from-internal:10] GotoIf("SIP/9844-00000002", "1?USER") in new stack
-- Goto (from-internal,8888,18)
-- Executing [8888@from-internal:18] Set("SIP/9844-00000002", "MEETME_OPTS=cIM") in new stack
-- Executing [8888@from-internal:19] Goto("SIP/9844-00000002", "STARTMEETME,1") in new stack
-- Goto (from-internal,STARTMEETME,1)
-- Executing [STARTMEETME@from-internal:1] ExecIf("SIP/9844-00000002", "0?Set(CHANNEL(musicclass)=)") in new stack
-- Executing [STARTMEETME@from-internal:2] Set("SIP/9844-00000002", "GROUP(meetme)=8888") in new stack
-- Executing [STARTMEETME@from-internal:3] GotoIf("SIP/9844-00000002", "0?MEETMEFULL,1") in new stack
-- Executing [STARTMEETME@from-internal:4] MeetMe("SIP/9844-00000002", "8888,cIM,1111") in new stack

== Parsing ‘/etc/asterisk/meetme.conf’: == Found
== Parsing ‘/etc/asterisk/meetme_additional.conf’: == Found
[Nov 30 10:07:12] WARNING[1543]: app_meetme.c:1221 build_conf: Unable to open DAHDI pseudo device
== Spawn extension (from-internal, STARTMEETME, 4) exited non-zero on ‘SIP/9844-00000002’
– Executing [h@from-internal:1] Hangup(“SIP/9844-00000002”, “”) in new stack
== Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/9844-00000002

Your expertise are much appreciated. Thank you

Regards,
Jimmy

MeetMe is probably looking for the DAHDI provided timing module.

Even if you do not run a TDM card, you should load the DAHDI kernel module (dahdi.ko)

If that is loaded, is Asterisk running as a non-root user? If so, you may have a permissions problem on the /dev/dahdi directory and the files within it. The should be owned by the same user as is running Asterisk.

Finally, we should not overlook the negative impact of SELINUX on Asterisk. If you have SELINUX enabled, I suggest turning it off.

If none of that helps, please respond with Asterisk and DAHDI versions as well as OS version.

MeetMe uses dahdi to do the actual conference bridging, not just to provide timing.