similar to: dahdi and asterisk 1.4.22

I am installing dahdi on a machine lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge 00:01.0 PCI bridge: Hewlett-Packard Company Unknown device 9602 00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0) 00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 1) 00:06.0 PCI bridge: Advanced Micro Devices [AMD]

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#

Hello there: I think I have a silly kernel configuration problem. I'm running: * vanilla 2.6.27.10 kernel built from source * dahdi-2.1.0.4 built from source So far so good, dahdi module loads just fine: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.1.0.4 when I try to: hal04 dahdi # modprobe dahdi_dummy FATAL: Error inserting dahdi_dummy

Hello all, Ok it is Sunday afternoon and I am going crazy. I have been running in circles so long that I can't think straight. As an example, I sent this message to the wrong address the first try, AAARRRRGGGGGGHHHHH. I have Asterisk 1.6.0.6 and DAHDI Tools Version - 2.1.0.2, DAHDI Version: 2.1.0.4, OpenSuSE 10.3 x86_64, tdm422 at the end of installing dahdi-linux and dahdi-tools I get:

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

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. 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

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

Hi! I have Asterisk 1.6.1 installed on OpenSuSE 11.0 running with choppy sound. One specialist on the forums asked me if I have DAHDI configured, he assumed that this could be cause of choppy sound problem. > dahdi_test Unable to open dahdi interface: No such file or directory Do I need to configure DAHDI even if I do not have any Zaptel devices? Is there any guide for configuring

1. Is it normal to see : # lsmod Module Size Used by dahdi_dummy 3236 0 Shouldn't it be used by asterisk or is this 0 value meaning something specific ? 2. How can you check dahdi is running ? Here, "ps aux | grep dahdi " replies "grep dahdi". Cheers ------=_Part_2692_19661943.1228286635399 Content-Type: text/html; charset=ISO-8859-1

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

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 Eric, > On 12 avr. 2016, at 17:48, Eric Cooper <ecc at cmu.edu> wrote: > > On Tue, Apr 12, 2016 at 04:36:58PM +0200, Bertrand LUPART - Linkeo.com wrote: >> I just made a asterisk / dahdi fresh install on Debian 8.4, and ended up with the following packages : >> [...] >> However, i can't find any dahdi startup script, neither init.d neither systemd

I have a TDM400. Just updated Fedora 12 to kernel 2.6.32. Rebuilt and installed dahdi-2.2.1. kernel modules loaded. lsmod | grep wctdm wctdm 37233 0 dahdi 194985 1 wctdm lsmod | grep dahdi dahdi 194985 1 wctdm crc_ccitt 1549 2 dahdi,isdnhdlc dmesg: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.2.1

Hello I was editing files manually, and noticed that if I include the familiar "fxsks=1" in /etc/dahdi/system.conf, Dahdi fails loading: ===================== # cat /etc/dahdi/system.conf loadzone = fr defaultzone = fr fxsks=1 ===================== # /etc/init.d/dahdi start Loading DAHDI hardware modules: wctdm: [ OK ] /usr/share/dahdi/waitfor_xpds: Missing

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Days ago I bought a OpenVox A400P card with a port FXS and another FXO that I am testing with my Asterisk installation in my house. I'm using Asterisk 1.4.24.1 with DAHDI Linux 2.1.0.4 and DAHDI Tools 2.1.0.2 on Debian GNU/Linux Lenny. I was reading "The future of telephony" and this [1] document looking for information about

The Asterisk Development Team has announced the releases of: DAHDI-Linux 2.6.1 DAHDI-Linux 2.5.1 DAHDI-Tools 2.6.1 DAHDI-Tools 2.5.1 DAHDI-Linux-Complete 2.6.1+2.6.1 DAHDI-Linux-Complete 2.5.1+2.5.1 These releases are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools

The Asterisk Development Team has announced the releases of: DAHDI-Linux 2.6.1 DAHDI-Linux 2.5.1 DAHDI-Tools 2.6.1 DAHDI-Tools 2.5.1 DAHDI-Linux-Complete 2.6.1+2.6.1 DAHDI-Linux-Complete 2.5.1+2.5.1 These releases are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools

Hello, ? I have a Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] card which seems to work on 1 machine but not on another. It SHOULD load this driver: ? >dahdi_hardware -v pci:0000:00:00.0 wcb4xxp+ 1397:08b4 Junghanns QuadBRI ISDN card Instead of: >dahdi_hardware -v pci:0000:00:00.0 qozap- 1397:08b4 Generic Cologne ISDN card There is no qozap modul in