similar to: Meetme Question

Hello. I have a strange problem with the MeetMe application. Configured is a misdn msn to go into a preconfigured MeetMe room. exten => 12,1,MeetMe(1234,pIM) The first caller gets the prompt to enter the pin and then gets connected to the MeetMe room. The second caller gets also the prompt but after entering the right key he hears a dialtone followed by the message: The number you have

Hi i am experiencing this problem: MEETME_RECORDINGFILE=/data/asterisk_data/_${DATETIME}_CONFERENCE exten => 9999,1,MeetMe(666|1Arxq) exten => 9998,1,MeetMe(666|1Axq) exten => 9997,1,MeetMe(666|1xq) I make a conference between 3 person dialing A dials 9999 B dials 9998 C dials 9997 all works fine but the datetime won't be updated, it still remain for example 13:40 until i do a

Hello, all. I must be brain cramping badly on our Asterisk 1.6.1.1 installation. Our MeetMe macros are working fine except they do not prompt for a PIN. So I made a very simple conference room: exten => 7777,1,MeetMe(123456,cMaAsx,123456) Shouldn't this prompt the user who dials 7777 to enter a PIN before entering the conference room whether or not a PIN is defined in meetme.conf? I

Hi, I was just wondering how would the application be where the Asterisk calls a number and that number joins the conference as soon as the call connects. There would be only one conference already defined in meetme.conf and there is one person already joined the conference. Currently MeetMe requires a person dialing into it and the joining the conference. How could this be done using MeetMe or

Hi, I've just observed something a bit odd - I'm wondering if this is the expected behaviour, a bug/feature, or something I'm doing stupid! 1st person gets into MeetMe. Nothing fancy, just: exten => 987,1,MeetMe(400,iM) They enter the passcode and their name, then listen to MoH. So-far so good. Now the 2nd person dials in. They enter the pin-code, and at that point, the MoH

hi guys: recently I want to buinding a meeting confence on asterisk and use the meetme application. I have a ztdummy kernel afteri the lsmod commond: ztdummy 5768 0 zaptel 182660 28 zttranscode,ztdummy crc_ccitt 3008 1 zaptel I also configure the meetme.conf conf => 1000; my extensions.conf [default] exten =>

I'm having some problems getting meetme to work now that I have upgraded to .5 I am able to conference calls but every time I try to manage the conference through meetme it just says "No users in this conference" Any ideas why it doesn't see the conference call? Thanks for any help! Jason This message along with any attachments is intended only for the use of the individual or

Hey Guy! I have following dialplan for meetme and i want if someone type wrong meetme extension it should say invalid extension. But look like following doesn't work. its just hangup if i type wrong number. how to fix this code.. ;Conference rooms/lines: exten => 7580,1,Goto(ivr-meetme,s,1) [ivr-meetme] include => meetme exten => s,1,Answer() exten => s,n,Wait(1) exten =>

We are developing an on-demand teleconferencing solution. We will be billing per-minute/per-user. I've successfully gotten Asterisk to write CDR data to a postgres database, but with the way I've got things setup right now the CDR does not have the dialed conference number. We need this information in order to be able to bill. As teleconferencing is the only application of the

I have two asterisk machines. One of them has a Digium board (server A) and the other is simply using ztdummy (server B). Server A is running on Debian and Server B is running Gentoo. Server A is running Asterisk CVS-Nv1-0-7-06/01/05-01:27:25 and Server B is running Asterisk 1.0.7. The problem I have is that when I try to transfer a call into a meetme room in server B, it simply hangs

Hi, This is pretty much a repost but I still havent been able to get MeetMe to work.. I am using a Dev Kit lite.. so that should satisfy the Zaptel requirement for MeetMe.. meetme.conf looks like this.. [rooms] conf => 7500 In extensions.conf I have an [extensions] context and within that same context I have the line.. exten => 7500,1,MeetMe(7500) When I dial 7500 I get the message

I have meetme working with BLF on polycom phones however when meetme is not actually being used by anyone the 'status' of meetme becomes "idle". Which the Polycom phone sees and produces a clock symbol and FLASHING red LED. Are there any 'tricks' or work-arounds to change this status to something that does not blink the phone's LED making it look busy when meetme is

I'm trying to migrate from MeetMe to ConfBridge: [conferences] exten=>_8[1-9],1,Answer() ;;exten=>_8[1-9],1,Meetme(${EXTEN},1Ms,1234) exten=>_8[1-9],2,ConfBridge(${EXTEN},1Ms) exten=>_8[1-9],n,Hangup And that works. Also changed the hints: ;;exten => 81,hint,MeetMe:81 exten => 81,hint,ConfBridge:81 ;;exten => 82,hint,MeetMe:82 exten => 82,hint,ConfBridge:82 ;;exten

One of the features that I thought would be popular with the Web-MeetMe suite is the ability to start all non-admin callers in a muted state and selectively unmute them. For example any large conference that is of an announcment nature with a Q&A session. It's probably a feature I should have tested better, but I just discovered that a caller that is joined to a MeetMe with the |m flag

Hi, I know this question may have been asked before (although the archives don't seem to suggest it), but has anyone had any problems with Asterisk accepting a PIN number for a conference room. At this point in time I have established the conference definition in the meetme.conf file as well as specifying the appropriate lines in the extensions.conf file. meetme.conf file: conf =>

With 1.6.1, I'm trying to set up a test of meetme for creating dynamic conferences. cat meetme.conf [rooms] conf => 600 extensions.conf: [meetme] exten => 2663,1,MeetMe(,D) exten => 2663,n,Hangup() exten => 2666,1,MeetMe() exten => 2666,n,Hangup() What I'm expecting is to dial 2663, get a conference room number ( 600, I suppose since it's the only room ), and set

While researching Areski's new Web-MeetMe management gui, I found some odd (from what I expected) behaviour). Using the CLI to set un/mute status works but does not update the flags, or so it appears. Starting with a fresh conference (1 user) *CLI> meetme list 3456 User #: 1 Channel: OH323/R61 Using the CLI to mute the caller (no change in the user status0 *CLI> meetme mute 3456 1

Dollars to donuts it is related to these two posts, but no one seems to know where or why it happens - this issue doesn't seem to be related to one specific piece of hardware: Post 1) ********************************************************* Anyone ever seen MeetMe cause * to crash? Specifically, it happens consistantly if someone begins to enter a conference and then decides to hangup while

I do not have any zaptel hardware on the Asterisk box, I could not have meetme functioning. I did modify the Makefile in zaptel directory on line 168 by including ztdummy as one of the modules to compile in. The error message from the concole: -- Executing MeetMe("SIP/1002-e9ca", "4700") in new stack == Parsing '/etc/asterisk/meetme.conf': Found

I'm trying to use the password entered with Authenticate to create dynamic meetme conferences with the following dial plan: exten => _XXXXXXXXXX18467,1,Authenticate(/etc/asterisk/meetme.pw|a) exten => _XXXXXXXXXX18467,n,MeetMe(CDR(accountcode)) ; 281-8467 However CDR(accountcode) is always being set to 1022 no matter what password is used. The passwords are stored in a file so they can