Displaying 20 results from an estimated 1000 matches similar to: "Problems with conference on FreeBSD 5.2.1 w/* 1.0.1"
2005 Feb 09
2
Problem with meetMe
I try to use meetme app
after reading manual i compile and install zaptel with ztdummy
when i make lsmod
i have
ztdummy 2532 0 (unused)
wcusb 20064 0 (unused)
zaptel 179168 4 [ztdummy wcusb]
usb-uhci 26348 0 [ztdummy]
usbcore 51616 0 [wcusb usb-uhci]
after it i recompile asterisk and after it i have
2005 Jun 16
1
MeetMe ERROR "Unable to dup channel"
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
2005 Sep 19
2
ztdummy configuration help
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",
2003 Oct 13
2
Problems with MeetMe.
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
2007 Mar 30
1
Asterisk 1.4 with Digium B410P - Timing problem
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
2007 Apr 18
2
MeetMe Error
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]:
2003 Sep 25
7
Meetme question
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
2003 Jul 17
2
conference problem without zapata interface
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
2006 Oct 24
10
Meetme... No channel type registered for 'zap'
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
2013 Jun 06
1
asterisk 1.8.22 - : app_meetme.c:1248 build_conf: Unable to open DAHDI pseudo devic
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
2006 Mar 07
1
MeetMe 'i' option not working correctly?
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
2004 Sep 28
2
Unable to open pseudo channel
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
2004 Aug 27
1
Problems dialing out with T100P and Adtran
I have a T100P card connected to an Adtran and then a T1.
I have added the following configurations to Asterisk...but, when I dial
9 and then a local phone number, it bounces between the dial tone and
silence and the *error* light on the Adtran blinks.
zaptel.conf
span=1,0,0,esf,b8zs
fxsks=1-8
loadzone=us
defaultzone=us
zapata.conf
[channels]
context=from-sip
signalling=fxs_ks
2003 Dec 18
2
Zaprtc compile error - virtual device for conferencing
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
2005 Jan 30
4
Processing incoming calls with multiple contextst over PRI
So I have a problem. A customer of mine wants a PBX, owns an office
building. I want to sell him on asterisk. He has 4 tenants. I am using
my asterisk box to simulate it. My asterisk box has a TDM400P card, not
a PRI card. Don't know if it makes any difference.
Anyway, I want to route incoming phone calls to different contexts based
on the phone number being called.
Here is my
2003 Aug 07
1
MWI bug ?
Hi Lee,
You need to specify the VM context that you are using..
so using your examples..
extensions.conf entry..
exten => 1000,1,Dial(SIP/1000,20)
exten => 1000,2,Voicemail2(u1000)
exten => 1000,102,Voicemail2(b1000)
exten => 1000,103,Hangup
should be..
exten => 1000,1,Dial(SIP/1000,20)
exten => 1000,2,Voicemail2(u1000@sip)
exten => 1000,102,Voicemail2(b1000@sip)
exten
2008 Aug 11
1
1.4 SVN / dahdi / meetme / -> unable to open pseudo device
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
2003 Jun 23
1
(no subject)
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'
2006 Mar 03
1
Meetme Timing Interface
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
2004 Jan 15
4
meetme without zaptel hardware
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