Hello,
I have a problem with the meetme application, but I'm not sure if it's a
bug or just a misuse.
I'm trying to get a 3 way call system working as follow :
A calls C
B calls C
C who's speaking with A or B, presses one keypad (only one)
and the 2 incoming SIP (A, B) and C are redirected into a conference room.
Therefore, I created an entry in the applicationmap (features.conf) to
run a C program.
The C program forks a child process which executes a TCL script after
two seconds.
The parent process returns as soon as possible and lets the feature
execution finish.
The TCL script searches for the channels which involve C (the user which
wants to make the conference, and redirect the corresponding channels to
a conference room).
The configured extension is as follow :
exten => _cXXXXX,1,Answer()
exten => _cXXXXX,2,MeetMe(${EXTEN},sp)
exten => _cXXXXX,3,Hangup()
You'll find the TCP stream of the interaction between the script and AMI
in the attached file (you can open it using the wireshark's application)
The problem is that after the execution of the script, I get the
following messages which loops in the CLI, in a random order (I just put
here the three kinds of messages I got, so don't pay attention to the
dates) :
[Apr 20 10:02:01] WARNING[7352]: app_meetme.c:2183 conf_run: Failed to
read frame: No such file or directory
[Apr 20 10:05:00] WARNING[7433]: app_meetme.c:2183 conf_run: Failed to
read frame: Success
[Apr 20 10:05:02] WARNING[7433]: app_meetme.c:2183 conf_run: Failed to
read frame: Resource temporarily unavailable
Sometimes the conference works, sometimes it doesn't; however, the
messages appear in all the cases.
Am I just misusing meetme for something it's not supposed to do ? Or is
it really a bug ? Has anybody already heard of this bug ? Or does
somebody knows another way to achieve the same functionnality (3 way
calling with two ingoing calls) ?
Thanks in advance.
J-M HEITZ & LM
Linux Distribution : Ubuntu edgy
Kernel : Linux asterisk2 2.6.17-10-server #2 SMP Fri Oct 13 18:47:26 UTC
2006 i686 GNU/Linux
Zaptel version :
Apr 20 10:18:48 asterisk2 kernel: [44924783.590000] Zapata Telephony
Interface Registered on major 196
Apr 20 10:18:48 asterisk2 kernel: [44924783.590000] Zaptel Version:
SVN-trunk-r2396 Echo Canceller: MG2
Apr 20 10:18:51 asterisk2 kernel: [44924785.930000] ztdummy: RTC rate is
1024
Asterisk version : Asterisk SVN-trunk-r61152 built by root @ asterisk2
on a i686 running Linux on 2007-04-11 08:00:04 UTC
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3wayconf.cap
Type: application/cap
Size: 7736 bytes
Desc: not available
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20070424/d3539f63/3wayconf.bin
