similar to: Problem with meetMe

Hello, I'm trying to set up a conference room. When I dial it's extension, I get an audible error saying "Not a valid conference room, please try again" followed by a disconnect. I've got debug sip peer 1001 (my X-Lite client) and I see this in the logs: (I'm pretty sure it has something to do with ztdummy, but I dunno... I have the port installed, but I

Upon setting up and configuring the my extension.conf, meetme.conf and following the instruction outlined at this web page: http://www.voip-info.org/wiki-Asterisk+timer+ztdummy I get the following errors when calling the meetme number. Executing Wait("SIP/216.53.118.2-f41196e0", "1") in new stack -- Executing MeetMe("SIP/216.53.118.2-f41196e0",

I would us Meetme for conferance SIP-->SIP fist. my Meetme.conf: [rooms] conf => 9999 my extensions.conf: exten => 9999,1,MeetMe(9999) But : == Parsing '/etc/asterisk/meetme.conf': Found Jun 16 10:33:22 WARNING[12100]: chan_zap.c:916 zt_open: Unable to open '/dev/zap/pseudo': No such file or directory Jun 16 10:33:22 ERROR[12100]: chan_zap.c:6969 chandup: Unable

Good afternoon, I'm trying to use MeetMe in an AGI script written in Perl, as follows: print "EXEC MeetMe 2000|p \n"; $res = checkresult(); The problem that I have is that when a user press '#' in order to exit from the conference, everybody goes out. This is randomized because sometimes doesn't happened. My current version of asterisk is: Asterisk

Hi list, we have a dual Xeon server with 2GB RAM running Debian Etch 2.6.18.4-686 kernel. The server has 2 B410P cards plugged in. No other card. We installed Asterisk 1.4 trunk with zaptel trunk, ran make b410p, the install mISDN1.1.0 (for bug 9064) configure and compile Asterisk with chan_misdn, all is fine. In misdn-init.conf we have added option=1,master_clock. Asterisk is up and

Hi! i have an error using the meetme aplication, and just dont work.. my meetme.conf is: [rooms] conf = 700 i calling from a sip phone, the extension number is 600. there is the error: Executing [700@numberplan-custom-1:1] MeetMe("SIP/600-09111e58", "700|MI") in new stack WARNING[20055]: channel.c:3024 ast_request: No channel type registered for 'zap' WARNING[20055]:

Ok.. I got * and SIP working internally now .. still wrestling with connecting two remote * pbx's together.. I'll save that for another day though :) I setup Meetme on this new * PBX, but when I try to dial to join the conference, I hear a recording saying the conference is invalid or something to that effect. Here's a copy of my log files: == Parsing

Hello ! In file app_meetme.c we can read A ZAPTEL INTERFACE MUST BE\n" "INSTALLED FOR CONFERENCING FUNCTIONALITY.\n" I receive message, when I try conference WARNING[28686]: File app_meetme.c, Line 151 (build_conf): Unable to open pseudo channel -- Playing 'conf-invalid' Does it means that I cannot establish conference without any hardware zaptel interface ??? What

When I call meetme: exten => 1000,1,Answer exten => 1000,n,Meetme(|||d) Asterisk is complaing with: -- Executing Answer("IAX2/xxx.yyy.142.204:4569-2", "") in new stack -- Executing MeetMe("IAX2/xxx.yyy.142.204:4569-2", "|||d") in new stack -- Playing 'conf-getconfno' (language 'en') Warning, flexible rate not

Hello All, I upgraded Asterisk 1.8.10 to Asterisk 1.8.22 since upgrading I can't get meetme feature to work when dial meetme extension, can you please help? It always worked before, also I do not have dahdi installed on this machine, never did. -- Executing [104 at sipphones:1] MeetMe("SIP/101-00000813", "104") in new stack == Parsing

I'm running 2.4.5 and app_meetme never plays conf-hasleft or conf-hasjoined with user names. I looked at app_meetme.c, but couldn't determine the cause. Any suggestions are greatly appreciated. exten => 600,1,MeetMe(600|i) I get the following: -- Executing MeetMe("SIP/jon-21f8", "600|aciMps") in new stack == Parsing '/etc/asterisk/meetme.conf': Found

Hi All, I've had a great time exploring * on & off over the past month and have had a deal of success, very impressed with this product... I have an issue on a debian unstable system with the zap interface. I've compiled and loaded the ztdummy successfully, but when attempting to connect to a conference room I get failure. I get the error chan_zap.c:757 zt_open: Unable to open

Hi, I don't have a zaptel device for conferencing. I read from the lists, that ztdummy and zaprtc need to be installed to get conferencing. I could able to compile successfully with ztdummy and when i receive the call it says, -- Goto (13732,s,1) -- Executing MeetMe("SIP/-08118800", "1234") in new stack == Parsing

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

Hi, I was switching from zaptel to dahdi and got latest SVN from everything. Compiling works fine. kernel module dahdi_dummy is loaded. /dev/dahdi/pseudo exists Trying to go into a meetme does not work: [Aug 11 14:04:45] -- Executing [8001 at client_int_sgmobile:1] MeetMe("SCCP/6000-00000001", "444|dcIM") in new stack [Aug 11 14:04:45] WARNING[4184]: app_meetme.c:775

Is this me or what? -- Playing 'demo-congrats' -- Executing MeetMe("H323:996", "") in new stack -- Playing 'conf-getconfno' == Parsing '/etc/asterisk/meetme.conf': Found WARNING[17425]: File app_meetme.c, Line 151 (build_conf): Unable to open pseudo channel -- Playing 'conf-invalid' -- Playing 'conf-getconfno'

I have ztdummy installed: Module Size Used by ztdummy 3464 0 zaptel 218756 1 ztdummy crc_ccitt 2176 1 zaptel ohci_hcd 16388 0 floppy 49028 0 pcspkr 2180 0 piix 8580 0 [permanent] ehci_hcd 24456 0 uhci_hcd 26256 0 rtc

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 originally built my Asterisk server without installing the Zaptel package as it was going to be a purely SIP based system. However when I went to setup conferencing using meetme I found out that app_meetme is dependant on the ztdummy for timing. I have now installed the zaptel package and I believe the ztdummy module is loading ok [root@astro asterisk-1.4.0-beta2]# lsmod Module

Hi all, I have a problem starting the ztdummy. Here is what happens: [root@asterisk /]# modprobe ztdummy Notice: Configuration file is /etc/zaptel.conf line 0: Unable to open master device '/dev/zap/ctl' 1 error(s) detected FATAL: Error running install command for ztdummy After this, ztdummy is visible with lsmod, but when I try MeetMe, I get following: == Parsing