Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: olivers on May 14, 2008, 04:20:15 PM

Title: Meetme problem in Sail -
Post by: olivers on May 14, 2008, 04:20:15 PM
I am trying to get the MeetMe conference calling working in Sail 2.2.1-619

I have the default 300 through 307 extensions defined in the meetme.conf header.
The top IVR menu, option 3 is set to 'Default Open'.

When I call extension 301, I get a 'That is not a valid conference number ...' message.
The console log shows an error 'Unable to open pseudo device', as follows:


-- Executing [301@internal:1] AGI("SIP/5115-09b21ba8", "selintra|OutCluster|301") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
    -- Executing [301@XXXXXXX:1] MeetMe("SIP/5115-09b21ba8", "301|Mpi") in new stack
  == Parsing '/etc/asterisk/meetme.conf': Found
[May 13 17:32:14] WARNING[27725]: app_meetme.c:772 build_conf: Unable to open pseudo device
    -- <SIP/5115-09b21ba8> Playing 'conf-invalid' (language 'en')

Googling the error suggests some problematic pseudo device in /dev/zap, which is a directory that does not exist on my machine (a vanilla SME 7.3).

There are no Zaptel/Digium devices in the machine, only VOIP trunks.  Could this be a timer card issue?

The machine is set up as a server-gateway and dial in/out from both internal and external extensions is working fine.

Any ideas?

Thanks,
Oliver
Title: Re: Meetme problem in Sail -
Post by: SARK devs on May 14, 2008, 11:05:58 PM
Quote
There are no Zaptel/Digium devices in the machine, only VOIP trunks.  Could this be a timer card issue?

Yes indeed.  Meetme will not work without a timing source.  This is why in the installation notes we tell you that you MUST run a PCI card probe, even if you don't have any zap devices.  The PCI probe will detect that you have no cards and automatically set the system up to load ZTDUMMY, the asterisk soft timer.

Kind Regards

S