Hi Walter,
I've been faced with this exactly problem on Amazon EC2
Dahdi started and Asterisk running... but on logs always see that error:
app_meetme.c: Unable to open pseudo device
I remember that I checked that device exists, daemons have
permissions to open the device, dahdi was working as expected,
asterisk working ...all working but always got that error when I tried
the bbb voice app and ended to let it parked till I have some time
again to try it again....
What do you mean with
" I found out that I had to actually execute a command "dahdi start"
which inserts the freshly compiled kernel modules. However that
command is nowhere in the docs"
That command is not the one to start dahdi? i guess I've executed it a
couple of time... dahdi stop , dahdi start ... I've check that it was
running and that dahdi_dummy was loaded...
Can you kind give some hints to me on that?
Those where some of my tests:
Asterisk console I got:
Verbosity is at least 5
-- Registered SIP '3011' at 127.0.0.1 port 5081 expires 3600
-- Saved useragent "mjsip stack 1.6" for peer 3011
[Nov 11 12:20:07] NOTICE[4778]: chan_sip.c:12669
handle_response_peerpoke: Peer '3011' is now Reachable. (1ms / 2000ms)
-- Executing [85115@bbb-voip:1] MeetMe("SIP/3011-081f95f8",
"85115|cdMsT") in new stack
[Nov 11 12:20:07] WARNING[11679]: app_meetme.c:774 build_conf: Unable
to open pseudo device
-- <SIP/3011-081f95f8> Playing 'conf-invalid' (language 'en')
== Spawn extension (bbb-voip, 85115, 1) exited non-zero on 'SIP/3011-081f95f8'
I guess the problem is app_meetme.c:774 build_conf: Unable to open
pseudo device , not sure what is about but at first guess I with
dahdi_dummy wich is currently loaded and running...
executing: modinfo dahdi_dummy
I GET:
filename: /lib/modules/2.6.18-xenU-ec2-v1.0/dahdi/dahdi_dummy.ko
license: GPL v2
author: Robert Pleh <
rober...@hermes.si>
description: Timing-Only Driver
depends: dahdi
vermagic: 2.6.18-xenU-ec2-v1.0 SMP mod_unload 686 REGPARM gcc-4.0
parm: debug:int
executing: dahdi_test -v
Opened pseudo dahdi interface, measuring accuracy...
8192 samples in 8190.560 system clock sample intervals (99.982%)
8192 samples in 8190.096 system clock sample intervals (99.977%)
8192 samples in 8182.424 system clock sample intervals (99.883%)
8192 samples in 8182.376 system clock sample intervals (99.883%)
8192 samples in 8222.616 system clock sample intervals (100.374%)
8192 samples in 8174.175 system clock sample intervals (99.782%)
8192 samples in 8190.512 system clock sample intervals (99.982%)
8192 samples in 8198.399 system clock sample intervals (100.078%)
8192 samples in 8182.384 system clock sample intervals (99.883%)
8192 samples in 8190.480 system clock sample intervals (99.981%)
8192 samples in 8190.440 system clock sample intervals (99.981%)
--- Results after 11 passes ---
Best: 99.982 -- Worst: 99.626 -- Average: 99.898383, Difference: 99.980538
executing: ls /sys/module/
capability commoncap crc_ccitt dahdi dahdi_dummy i8042 keyboard
lockd md_mod mousedev nfs printk tcp_bic
executing: ls /dev/dahdi/
channel ctl pseudo timer
executing: dahdi_cfg -v
DAHDI Tools Version - 2.2.0
DAHDI Version: 2.2.0.2
Echo Canceller(s):
Configuration
======================
0 channels to configure.
So dahdi_tools must be working too..
Regards,
Hugo