similar to: How does Digium Repo install Dahdi on a virtual container while I can't do the same trying from source install?

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

Hi, I try to find some information about CAS E1 signalling and how it's handled by Asterisk. My customer wants to connect to a BT ITS Netrix by CAS E1 E&M. The system is intended to take the channels and mix them (meetme / confbridge) and send the audio back mixed to each. The layout: BT ITS Netrix: CAS E1 E&M <-> MUX - WAN - MUX <-> Digium TE220, Asterisk I've

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

Hi All, I want packets [request/response] capture for ISUP packets , i have E1 line terminated to my digium card i just want a packets flow between my machine and teleco side, is any tool or utility [command] availabele for observation this packets and data. any help appericiated Thanks Dhaval -------------- next part -------------- An HTML attachment was scrubbed... URL:

When I compile dahdi I see these warnings: WARNING: "kasprintf" [dahdi-linux-2.5.0.2/drivers/dahdi/wctdm24xxp/wctdm24xxp.ko] undefined! WARNING: "kasprintf" [dahdi-linux-2.5.0.2/drivers/dahdi/dahdi.ko] undefined! And "modinfo dahdi" shows that the driver was built for a 2.6.17 kernel, SMP mod_unload 586 4KSTACKS gcc-4.1 If I "modprobe -a dahdi", I get

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

We're encountering no audio issues in ConfBridge. Only the moderator and the 1st invited have audio. When the 2nd invited number picks up the phone, only the announcement is heard, then followed by silence. This occurs frequently. Only 1 out of 5 test calls do not have this problem. We were hoping that switching from MeetMe to ConfBridge will solve the no audio issue, since there's no

hello , i try to install dahdi-linux/dahdi-linux-current.tar.gz ,dahdi-tools/dahdi-tools-current.tar.gz and libpri/libpri-1.4-current.tar.gz but got these error msg make -C drivers/dahdi/firmware firmware-loaders make[1]: Entering directory `/usr/src/dahdi-linux-2.6.1/drivers/dahdi/firmware' make[1]: Leaving directory `/usr/src/dahdi-linux-2.6.1/drivers/dahdi/firmware' make -C

Hi all, I'm getting compilation error as trying to install latest version of dahdi on CentOS box 5.9 which I now updated from 5.6. I also installed the dependencies but still not getting the clue to get install the driver. Listing down the errors below; CC [M]

Hello, I have at my disposal, 2, TE410P cards. I have setup an asterisk box that will function ONLY to handle meetme conferences over SIP. No PRI lines to be plugged into the 410 card. MeetMe requires an external timing source. Right now, using the dummy driver. Is it possible to use the card solely for timing purposes? Any benefit to doing so? Or should I just sell the cards? Matthew

Hi list, we have 2 asterisk boxes in VM (kvm) on 2 different Dell servers, one is Lenny kernel 2.6.26 asterisk 1.6.2.20, the second CentOS 2.6.18 asterisk 1.4.36 (Elastix). Both 64bits, no hardware involved, dahdi on both machines for meetme timing. Doing core show translation give on the Lenny server Translation times between formats (in microseconds) for one second of data

On fedora 21, trying to build dahdi for kernel 4.0.4. gcc-4.9.2-6.fc21.x86_64 make -C /lib/modules/4.0.4-202.fc21.x86_64/build SUBDIRS=/home/asterisk/rpmbuild/BUILD/dahdi-linux-2.10.1/drivers/dahdi DAHDI_INCLUDE=/home/asterisk/rpmbuild/BUILD/dahdi-linux-2.10.1/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: Entering directory

Hi all, On an Asterisk/Zaptel 1.4 system, one way to gather diagnostic info is: ~# cat /proc/zaptel/* Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER) AMI/CCS 1 ZTHFC1/0/1 Clear (In use) 2 ZTHFC1/0/2 Clear (In use) 3 ZTHFC1/0/3 HDLCFCS (In use) Span 2: ZTHFC2 "HFC-S PCI A Zaptel Driver card 1 [TE]" AMI/CCS 4 ZTHFC2/0/1 Clear 5 ZTHFC2/0/2

Hello, I just installed a Debian Jessie box from scratch which sports a Digium TE435 digital card. I installed the software, built and loaded the kernel modules: # dpkg -l|grep dahdi ii asterisk-dahdi 1:11.13.1~dfsg-2+b1 amd64 DAHDI devices support for the Asterisk PBX ii dahdi 1:2.10.0.1-1 amd64

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

Is a normal functionality? when I do #dahdi_cfg -vvvvvv In my Asterisk console shows this.... [Jul 24 13:39:08] NOTICE[30263]: chan_dahdi.c:9461 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 If I do this a lot of times...then [Jul 24 13:39:20] NOTICE[30263]: chan_dahdi.c:9461 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 [Jul 24

Hello folks. I've got a strange issue. When I modprobe TE220 I do not see mesages like Launching card: 0 <..> Setting up global serial parameters. You can see how I loaded and unloaded the card for several times - http://asteriskpbx.ru/pastebin/11 lspci can detect the card: 03:08.0 Communication controller: Digium, Inc. Device 0220 (rev 02) dahdi_hardware also: astpbx ~ # dahdi_hardware

On 06/01/2015 04:49 PM, Shaun Ruffell wrote: > On Mon, Jun 01, 2015 at 04:24:31PM -0400, sean darcy wrote: >> On fedora 21, trying to build dahdi for kernel 4.0.4. >> >> gcc-4.9.2-6.fc21.x86_64 >> >> make -C /lib/modules/4.0.4-202.fc21.x86_64/build SUBDIRS=/home/asterisk/rpmbuild/BUILD/dahdi-linux-2.10.1/drivers/dahdi

On Tue, Apr 26, 2016 at 11:07 AM, Administrator TOOTAI <admin at tootai.net> wrote: > Le 26/04/2016 17:23, Mamadou NGOM a ?crit : > >> Hello, >> >> >> Having installed DAHDI to be able to use the meetme() application , when >> I start the dahdi service it generates me the following error: >> >> -bash: /etc/init.d/dahdi: No such file or

Hi, Until now I've been using my Digium B410P cards with misdn 1.0.x. I would like to upgrade my systems and am now wondering which is the "best" route to take: - use the latest release of misdn v1 - upgrade to the latest "stable" kernel and use the built-in misdn v2 - use misdn v2 as a seperate package (disable misdn in the kernel) - use dahdi's support for misdn