Conference Unable to enter Pin: Unable to open pseudo device

General Help
1

I wanted to try conferencing, so I set up an IPKall number to forward to a conference I configured via the GUI, but I keep getting a message about a bad pin, even though it shows the correct one I entered. When looking at the logs, I noticed the following lines (after all the stuff about getting into to server and entering the pin)

…
[Jul 10 15:29:34] WARNING[8902] app_meetme.c: Unable to open pseudo device
[Jul 10 15:29:34] VERBOSE[8902] logger.c: – <SIP/ipkall1-
00000002> Playing ‘conf-invalid’ (language ‘en’)
…

From other posts in various places, I checked for, and do not have a pseudo device running, but since I’ve been using FreePBX, I never compiled anything on this system, nor do I have the sources. I just use the GUI to administer modules.

Some other possibly relevant info:
Core 2.9.0.5 FreePBX Enabled and up to date
Conferences 2.9.0.2 FreePBX Enabled and up to date

Thanks for any help.

Yaakov

2

Is this a physical machine? Do you have Dahdi working? You will need a timing source to conference.

3

No physical devices at all. Only SIP endpoints and SIP trunking.

4

I don’t know much about it, but doesn’t playing prompts also need a timing source, and that works fine.

5

No, but to mix rtp channels, you will need it.

6

http://forums.digium.com/viewtopic.php?t=69408

need to run dahdi driver which will load dahdi_dummy, and now it works!

/etc/init.d/dahdi start
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
xpp_usb: [ OK ]

No hardware timing source found in /proc/dahdi, loading dahdi_dummy
Running dahdi_cfg: [ OK ]

7

As I said from the beginning . .

"Do you have Dahdi working? "

8

As I said, I just did a simple complete install of an image, and got it working right away. If dadhi was needed regardless of hardware, I’m surprised it didn’t set it up automatically.

Anyway, thank you very much for your help.

Yaakov