similar to: Delay on sip channel

I updated Asterisk to 1.6.2.7 and now the user introduction in the meetme application is no longer working: [May 27 09:26:51] WARNING[2407]: channel.c:4034 ast_request: No channel type registered for 'DAHDI' -- Created MeetMe conference 1023 for conference '800' [May 27 09:26:51] WARNING[2407]: app_meetme.c:3640 find_conf: No DAHDI channel available for conference, user

Hi to all. I'm trying to use meetme on asterisk 1.4.22.1. On a debian i've compiled (as i need h323 support) openh323_v1_18_0 pwlib_v1_10_0 dahdi-linux-2.1.0.3 dahdi-tools-2.1.0.2 asterisk-1.4.22.1 All works fine, dahdi status is: asterik:/data/programmi# /etc/init.d/dahdi status ### Span 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: RTC) 1" (MASTER) asterik:/data/programmi#

Usually I used real Digium cards in asterisk systems, so I'm running into this for the first time. dahdi_tool reports that dahdi_dummy is in state UNCONFIGURED. This isn't super surprising, as it seems like the configuration files for DAHDI are really intended only for configuring real physical cards. But that begs the question: Is there any legal DAHDI configuration for dahdi_dummy such

Hi. I have a Debian Leni system with asterisk-1.8. I was trying to get meetme to work and it depends on dahdi, so I compiled dahdi-trunk and dahdi-tools-trunk, however, when trying to insert dahdi_dummy, it complained about symbol crc_ccitt_table, although the module was actually there in the kernel tree. So, I took the Debian source, and I had the config and I did make Bzimage, make modules

Howdy, I am playing around with asterisk within an LXC container on Ubuntu 11.04. I have asterisk (1.4.42) running fine, but want access to dahdi_dummy for timing (meetme). I have dahdi installed on the "host", and dahdi_dummy is loaded: root at astnorth:/# ls -ltr /dev/dahdi total 0 crw-rw---- 1 root root 196, 250 2011-06-08 13:59 transcode crw-rw---- 1 root root 196, 253

Hi, I have some servers that are dedicated to do meetme conferencing. From some previous test i concluded that I need to use dahdi_dummy as it is more accurate. If I did use the core timers in dahdi (not loading dahdi_dummy) I got bad quality in the conferences and dahdi_test showed 99.6% as worst. I thought maybe the issue as bad hardware for the timing or something else. But today I

So historically I've done one of two things on systems where I've needed to use MeetMe * used a real Digium card, and I've only ever used a TE400 or a TE420 for that purpose, and I know they have the timing chip * used dahdi_dummy, which works well with light load, but I had it running on a very overloaded server and had audio quality issues. I may have had quality issues even with a

I'm playing around with an ALIX 2D2 board (http://www.pcengines.ch/alix2d2.htm). It's a fanless, x86 system using an AMD Geode processor with 256MB of RAM. Also available are two network interfaces, two USB ports and one serial port (no keyboard or VGA). I'm using the Voyage Linux distro, which basically is Debian Lenny optimized for this board. Asterisk 1.6.1.12 runs fine on the

Running * version 1.6.1.17. My meetme conferences automagically disconnect users approximately 5-15 seconds after the user is connected. This occurs regardless of whether music on hold is active or not. [Mar 23 11:34:36] -- Executing Macro("SIP/SDN_TMCKEE-000000e9", "confroom,1808") [Mar 23 11:34:36] -- Executing [s at macro-confroom: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

hi,all i install MeetMe module on Asterisk 1.6.2.10. when i use MeetMe to open a conference. even without 'r' option .it will record too. is this the bug of this module? my dialplan is : [95040] exten => 95040263007,1,MeetMe(95040,sM,123) the CLI output is : *CLI> == Using SIP RTP CoS mark 5 -- Executing [95040263007 at 95040:1] MeetMe("SIP/999-00000021",

Hello, Page http://www.voip-info.org/wiki/view/Asterisk+config+meetme.conf seems to include some old content. Which is the simplest way to add MeetMe to a pure SIP 1.6.1 install on a recent kernel ? Is dahdi_dummy still required ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I am running Fedora 7 VM. On an earlier configuration with zaptel and Asterisk 1.4.21 , meetme worked alright. I upgraded to Dahdi and Asterisk 1.4.26, and the result is choppy sound via Meeme, while a simple Musiconhold works OK with descent audio quality. So I am sure its a Dahdi_dummy problem. Running dahdi_test gave me very poor results. Opened pseudo dahdi interface, measuring

asterisk*CLI> dahdi show status Description Alarms IRQ bpviol CRC4 T2XXP (PCI) Card 0 Span 1 OK 0 0 0 T2XXP (PCI) Card 0 Span 2 RED 0 0 0 On Thu, Apr 2, 2009 at 9:40 PM, Martin <asterisklist at callthem.info> wrote: > That's very strange ... the code when is

I have an X100P clone hocked up to an analog line of my PRI. I can use it to dial out. but when I call the extension it answers and says "GOODBY" I have a Livevoip DID which successfuly rings to ext 202 I am using asterisk@home and through the AMP inface the line should ring to ext 202 Below are Asterisk Messages, Extensions.conf and Extensions_additional.conf Extensions.conf

Hi. The UPGRADE.txt of asterisk distribution contains the following snippet under the MeetMe heading: /"MeetMe: * The conference application now allows users to increase/decrease their speaking volume and listening volume (independently of each other and other users); the 'admin' and 'user' menus have changed, and new sound files are included with this release.

Hi, We heavily use meetme/SLA functionality in Asterisk, and continuously run into issues with dahdi timing. The two errors we get are: ERROR[6518] res_timing_dahdi.c: Failed to configure DAHDI timing fd for 0 sample timer ticks WARNING[22024] app_meetme.c: Unable to write frame to channel Right now, dahdi in our setup uses the software timer (with res_timing_dahdi.so which gives much better

Hi Peoples I am having problems with meetme, in that it responds with "conf-invalid" when I dial a conference number. I notice that there is a note with regards to ztdummy, and the need for that to be loaded. Is this still the case? Is meetme dependent on this module? I do NOT use zaptel cards in my system, and there for zaptel is not loading. Can anyone shed some light

Greetings- I'm about to dive into the process of virtualizing some of my Asterisk (primarily 1.4.x) infrastructure. In the past, when looking at virt solutions, the primary issue preventing me from moving was the lack of proper timing. We do not need it for MeetMe but rather for IAX2 trunking. I'd like to use either OpenVZ or KVM, but each seem to have independent "issues" that

Hello System: Debian etch with kernel 2.6.18-4-686 or 2.6.18 custom. Asterisk Version: SVN-branch-1.4-r55483M Zaptel Version: SVN-branch-1.4-r2302 modules all ok in compilation time. And modules loaded: ztdummy 5928 0 rtc 13364 1 ztdummy zaptel 181540 1 ztdummy crc_ccitt 3200 1 zaptel In /dev/zap directory I have: