No channel type registered for DAHDI

[Joss2103]

What's up,

Today I have seen this in the vicidial space, I started having predictive call problems, but I don't know if this has anything to do with it.

-- Executing [8600055@meetme-enter-login:1] MeetMe("SIP/5009-00000024", "8600055,FG(http//IP server/ypq83h2z4d25nh0qnjk5gh6v4j11mh)") in new stack
== Parsing '/etc/asterisk/meetme.conf': Found
== Parsing '/etc/asterisk/meetme-vicidial.conf': Found
[Mar 6 13:40:11] WARNING[4111][C-00000062]: channel.c:6009 ast_request: No channel type registered for 'DAHDI'
-- Created MeetMe conference 1016 for conference '8600055'
[Mar 6 13:40:11] WARNING[4111][C-00000062]: file.c:701 ast_openstream_full: File http//104.254.244.239/ypq83h2z4d25nh0qnjk5gh6v4j11mh does not exist in any format
[Mar 6 13:40:11] WARNING[4111][C-00000062]: file.c:1017 ast_streamfile: Unable to open http//IP server/ypq83h2z4d25nh0qnjk5gh6v4j11mh (format (ulaw)): No such file or directory
-- <SIP/5009-00000024> Playing 'conf-onlyperson.gsm' (language 'en')
== Manager 'sendcron' logged off from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
-- Executing [8600056@meetme-enter-login:1] MeetMe("SIP/5012-00000025", "8600056,FG(http//IP server/ypq83h2z4d25nh0qnjk5gh6v4j11mh)") in new stack
== Parsing '/etc/asterisk/meetme.conf': Found
== Parsing '/etc/asterisk/meetme-vicidial.conf': Found
[Mar 6 13:40:14] WARNING[4118][C-00000063]: channel.c:6009 ast_request: No channel type registered for 'DAHDI'
-- Created MeetMe conference 1015 for conference '8600056'
[Mar 6 13:40:14] WARNING[4118][C-00000063]: file.c:701 ast_openstream_full: File http//IP server/ypq83h2z4d25nh0qnjk5gh6v4j11mh does not exist in any format
[Mar 6 13:40:14] WARNING[4118][C-00000063]: file.c:1017 ast_streamfile: Unable to open http//IP server/ypq83h2z4d25nh0qnjk5gh6v4j11mh (format (ulaw)): No such file or directory
-- <SIP/5012-00000025> Playing 'conf-onlyperson.gsm' (language 'en')

It is possible, you can tell me what this error is due to, please

Thanks

[carpenox]

is dahdi running? type "dahdi_cfg -v" within your linux cli and check the results, your can fix the issue if you have dahdi installed by following this article: https://cyburityllc.com/?p=1521

I hope this helps