On Saturday 15 November 2003 08:59, firedude@shorelinuxsolutions.com wrote:> Hi guys, > Having a bit of a problem trying to get conference bridges working. > In my meetme.conf file I have the following line > [rooms] > conf => 6000 > > > In my extensions.conf file I have: > exten => 1000,1,MeetMe,6000 > > My problem is that when I dial into extension 1000 it is telling me > "this is not a valid conference number". Can anybody telling me what > I'm doing wrong here?You need to do a restart after defining new conference numbers, otherwise they won't work (i.e. not on a reload). -Tilghman
Hi guys, Having a bit of a problem trying to get conference bridges working. In my meetme.conf file I have the following line [rooms] conf => 6000 In my extensions.conf file I have: exten => 1000,1,MeetMe,6000 My problem is that when I dial into extension 1000 it is telling me "this is not a valid conference number". Can anybody telling me what I'm doing wrong here? AJ
firedude@shorelinuxsolutions.com wrote:> My problem is that when I dial into extension 1000 it is telling me "this > is not a valid conference number". Can anybody telling me what I'm doing > wrong here?I've added the solution to this to the FAQ: http://www.voip-info.org/tiki-index.php?page=Asterisk+FAQ /Olle
firedude@shorelinuxsolutions.com wrote:>Hi guys, >Having a bit of a problem trying to get conference bridges working. In my >meetme.conf file I have the following line >[rooms] >conf => 6000 > >Make sure you have at least one blank line at the bottom of your meetme.conf.. Later..
Hello, I seem to have a strange problem, which appeared out of nowhere. Did anyone see something like this? 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 DEBUG[10721] res_agi.c: Zap/65-1 hungup 2005-06-03 18:44:50 DEBUG[10721] channel.c: Avoiding deadlock for 'Zap/63-1' 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success Once these messages start showing, I must stop my asterisk (stop now) because the load goes sky high. I'm using an Asterisk CVS-HEAD. Looking forward for your answer. Felix
Hello, I seem to have a strange problem, which appeared out of nowhere. Did anyone see something like this? 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 DEBUG[10721] res_agi.c: Zap/65-1 hungup 2005-06-03 18:44:50 DEBUG[10721] channel.c: Avoiding deadlock for 'Zap/63-1' 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success Once these messages start showing, I must stop my asterisk (stop now) because the load goes sky high. I'm using an Asterisk CVS-HEAD. Looking forward for your answer. Felix
Hello, I seem to have a strange problem, which appeared out of nowhere. Did anyone see something like this? 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 DEBUG[10721] res_agi.c: Zap/65-1 hungup 2005-06-03 18:44:50 DEBUG[10721] channel.c: Avoiding deadlock for 'Zap/63-1' 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success Once these messages start showing, I must stop my asterisk (stop now) because the load goes sky high. I'm using an Asterisk CVS-HEAD. Looking forward for your answer. Felix
Hello, I seem to have a strange problem, which appeared out of nowhere. Did anyone see something like this? 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Illegal seek 2005-06-03 18:44:50 DEBUG[10721] res_agi.c: Zap/65-1 hungup 2005-06-03 18:44:50 DEBUG[10721] channel.c: Avoiding deadlock for 'Zap/63-1' 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success 2005-06-03 18:44:50 WARNING[10721] app_meetme.c: Unable to write frame to channel: Success Once these messages start showing, I must stop my asterisk (stop now) because the load goes sky high. I'm using an Asterisk CVS-HEAD. Looking forward for your answer. Felix
hallo, i just experienced that all meetme rooms share the same voice data, if i connect to 499, it could be heard in all other rooms (498,500, 501) could sombody help me, why does asterisk send the voice out of all rooms if i only connect to one? thanks for help, alex meetme.conf conf => 101 conf => 102 conf => 103 conf => 104 extentions.conf exten => 498,1,MeetMe(101,q) ; quiet room exten => 499,1,MeetMe(102,q) ; quiet room exten => 500,1,MeetMe(103,q) ; quiet room exten => 501,1,MeetMe,104
I think I configured the MeetMe right. Since I am using SIP for
inbound calls I followed the
instruction, for 2.6 kernel, from this web page:
http://www.voip-info.org/wiki-Asterisk+timer+ztdummy
When I call the MeetMe number I get the greeting to enter in your
conference room. I do and get invalid conference room. Below is my
configs:
Executing Wait("SIP/192.168.1.2-08c82740", "1") in new stack
-- Executing MeetMe("SIP/192.168.1.2-08c82740", "") in
new stack
-- Playing 'conf-getconfno' (language 'en')
== Parsing '/etc/asterisk/meetme.conf': Found
-- Playing 'conf-invalid' (language 'en')
Sep 19 10:41:58 WARNING[14066]: file.c:554 ast_readaudio_callback: Failed
sip.conf
[15551232432]
type=friend
;username=2432
;secret=2432
host=dynamic
context=voice-mail
dtmfmode=rfc2833
;canreivet=yes
extension.conf
[voice-mail]
exten => _15551232432,1,wait(1)
exten => _15551232432,2,Meetme
exten => _15551232432,3,Hangup
meetme.conf
[voice-mail]
conf => 100
Thanks
Kurt