Summary:ASTERISK-12719: No pseudo device with DAHDI
Reporter:tootai (tootai)Labels:
Date Opened:2008-09-12 05:09:28Date Closed:2008-09-21 12:06:51
Versions:Frequency of
Description:When running conference with chan_dahdi on a server using dummy, we receive

-- Executing [880@HOME-Numbers:4] MeetMe("Local/880@HOME-Numbers-598d,2", "880|Mmpw") in new stack
 == Parsing '/etc/asterisk/meetme.conf': Found
[Sep 12 12:11:09] WARNING[13014]: app_meetme.c:778 build_conf: Unable to open pseudo device
   -- <Local/880@HOME-Numbers-598d,2> Playing 'conf-invalid' (language 'fr')
 == Spawn extension (from-HOME, 880, 23) exited non-zero on 'SIP/8081773619-08285548'
 == Spawn extension (HOME-Numbers, 880, 4) exited non-zero on 'Local/880@HOME-Numbers-598d,2'

In /dev/dahdi everything is OK.

lsmod|grep dahdi:

lsmod|grep dahdi
dahdi_dummy             5224  0
dahdi                 186280  1 dahdi_dummy
crc_ccitt               2240  1 dahdi
rtc                    12404  1 dahdi_dummy
Comments:By: Evandro C├ęsar Arruda (ecarruda) 2008-09-12 06:48:34

Hi tootai,

Didi you check your > dahdi status on your asterisk console? Check chan_dahdi.conf, because if this have errors chan_dahdi isn't load on asterisk.


By: Tzafrir Cohen (tzafrir) 2008-09-14 18:36:49

Might be a udev rules issue.

ls /sys/class/dahdi /dev/zap*

By: tootai (tootai) 2008-09-21 11:37:41

I went back to zaptel, the server had to go in production. I think we should close this bug, on next possibility to test I will eventually reopen it if necessary.

By: Tzafrir Cohen (tzafrir) 2008-09-21 12:06:49

And with zaptel it worked?

Asterisk is built vs. either zaptel or dahdi. This is a build-time decision.

If you reopen this, please also include the output of:

 strings /usr/sbin/asterisk | egrep '/dev/(zap|dahdi)'