I’m trying to create a conference service for my Asterisk-based IP-PBX using Meetme application.
The meetme.conf file has this:
[rooms]
conf=>2
The extensions.conf file has this:
exten => 200,1,MeetMe(2,DpM,1234)
The problem is that when I dial “200” always get a message of invalid conference number.
Any ideas please.
Hi
Plz do this
in meetmet.conf
[rooms]
conf = 398,2408,8901
where 398 is conf room & 2408 is PIN to enter in conf & 8901 is admin PIN to start conf
in extension.conf
exten => 398,1,MeetMe(398|Mcwx)
This sud work correctly so try this
Amit
The same thing happens.
Any other ideas??
why dnt u try
conf => 2, 1234
then
exten => 200,1,MeetMe(2,DpM,1234)
U have specified password in the exten but none exists for the hall. May be this could be the reason
Still the same thing.
The log show this:
Dec 14 10:38:02 VERBOSE [10772] logger.c: – Executing MeetMe(“SIP/102-08466148”, 200|DpM|123) in new stack
Dec 14 10:38:02 DEBUG [10772] app_meetme.c: Building dynamic conference '200’
Dec 14 10:38:02 WARNING [10772] chan_zap.c: Unable to open ‘/dev/zap/pseudo’: No such file or directory
Dec 14 10:38:02 ERROR [10772] chan_zap.c: Unable to dup channel: No such file or directory
Dec 14 10:38:02 WARNING [10772] app_meetme.c: Unable to open pseudo channel - trying device
Dec 14 10:38:02 WARNING [10772] app_meetme.c: Unable to open pseudo device
Dec 14 10:38:02 VERBOSE [10772] logger.c: – Playing ‘conf-invalid’ (language ‘en’)
Dec 14 10:38:02 DEBUG [10747] chan_sip.c: Stopping retransmission on ‘DE963A6B-7E91-41F1-A74E-6FE5FACC916C@192.168.2.41’ of Response2: Match Found
Dec 14 10:38:06 VERBOSE [10772] logger.c: == Spawn extension (default, 200, 1) exited non-zero on ‘SIP/102-08466148’
Anything that I can do??
I think its not creating a dynamic conference hall
why dont u avoid D
exten => 200,1,MeetMe(2,pM)
u will be prompted for a password here anyways
Did u try this ?
I tried and get the sames results, including the same log.
Anything else that I can do??
exten => 200,1,MeetMe(200)
meetme.conf
conf => 200, 1234
This works for me …
Log show this:
Dec 14 11:54:14 VERBOSE [11889] logger.c: – Executing MeetMe(“SIP/102-08466148”, “200”) in new stack
Dec 14 11:54:14 DEBUG [11889] logger.c: == Parsing ‘/etc/asterisk/meetme.conf’: Dec 14 11:54:14 DEBUG [11889] logger.c: == Parsing ‘/etc/asterisk/meetme.conf’: Found
I think this is the problem but don’t have any idea about the solution
Dec 14 11:54:14 WARNING [11889] chan_zap.c: Unable to open ‘/dev/zap/pseudo’: No such file or directory
Dec 14 11:54:14 ERROR [11889] chan_zap.c: Unable to dup channel: No such file or directory
Dec 14 11:54:14 WARNING [11889] app_meetme.c: Unable to open pseudo channel - trying device
Dec 14 11:54:14 WARNING [11889] app_meetme.c: Unable to open pseudo device
Dec 14 11:54:14 VERBOSE [11889] logger.c: – Playing ‘conf-invalid’ (language ‘en’)
Dec 14 11:54:14 DEBUG [11884] chan_sip.c: Stopping retransmission on ‘DE963A6B-7E91-41F1-A74E-6FE5FACC916C@192.168.2.41’ of Response2: Match Found
Dec 14 11:54:18 VERBOSE [11889] logger.c: == Spawn extension (default, 200, 1) exited non-zero on ‘SIP/102-08466148’
Meetme needs a zaptel card or the ztdummy module for timings, did you have a zaptel card installed or the ztdummy kernel module loaded ?
Cheers.
Marco Bruni
Hi,
I got the same problem, getting
"app_meetme.c:769 build_conf: Unable to open pseudo device"
And a message on the phone “that is not a valid conference number” (while it is ofc valid, according to the configuration).
So i found this thread. Of course my ztdummy module wasn’t loaded, so i loaded it manually and restarted asterisk. Then lsmod to see if the ztmodules are there - they are.
Retried calling the conf room number - but the logs and the error message are still the same. What else are we missing?
Ok, my solution was: chown -R asterisk:asterisk /dev/zap
(gentoo x86_64)