similar to: Dahdi 2.4.0 and Squeeze [SOLVED]

Hi, I'm using a two-years old installation script for the first time on a Squeeze (linux 2.6.32) platform. For an unknown reason (might be an obvious one), Dahdi can't be loaded anymore. 1. First of all, it seems /dev/dahdi content was previously (ie in Lenny) owned by asterisk:asterisk (asterisk is run as asterisk). Now it is owned by root. Any clue about this ? 2. Secondly, I changed

Hi again! I tried to attach two VoIP-phones to my new Asterisk 13.14.1 on a Banana PI with Armbian/Debian 9. First test was to call a test service that say the time. Works! Second test was to record my voice and play it again. Works! Third test was to call the other VoIP-phone. It does NOT work... :( Then I noticed that, by starting, Asterisk says the following messages: [Feb 15 18:42:54]

On Thu, Jun 6, 2019 at 12:17 PM Malcolm Davenport <malcolmd at sangoma.com> wrote: > Howdy, > > There's a dahdi-linux-complete-3.1.0-rc1+3.1.0-rc1.tar.gz. > > Try that. > I noticed that was there, but I didn't try it originally because it's obviously a beta version. However, I did download it and try it. It does compile, but doesn't work correctly. For one

On Tue, Mar 21, 2017 at 09:36:21AM +0100, Olivier wrote: > Thanks to Tzafrir help, Now I have an Asterisk-Dahdi system installed from > Stretch repository. > This system has a Digium HX8 card with BRI modules, Asterisk 13.14.0, Dahdi > 2.11.1. > BRI spans appears as up and active but I've not tested them yet: > CLI> pri show spans > PRI span 1/0: Up, Active > PRI

Seems like I post about this about once a year, when it's time to upgrade Fedora. I first got this error trying to compile a patched version of dahdi-linux-2.11.1; I noticed that there is now a dahdi-linux-complete-3.0.0+3.0.0, so I tried that one with the same result. If I compile it while running kernel-4.16.8-300.fc28.x86_64, it compiles fine, but when I try to compile it while running

after installing asterisk 1.4.23.1 and dahdi-linux-2.1.0.4 and at CLI> module load chan_dahdi.so receive the following: signalling must be specified before any channels are. CLI> Warning [4663]: chan_dahdi.c:11627 process_dahdi: Ignoring signalling Error[4663]: chan_dahdi.c:10946 build_channels: Unable to reconfigure channel '1' Error[4663]:

Hello, My first attempt to get dahdi running on 1.4.28... with a Rhino 8 port modular card and a single FXS module. Got the Rhino card installed and the machine sees it: root at pbx:/etc/dahdi# dmesg | grep rcbfx [ 71.985309] rcbfx 0000:04:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 71.985440] rcbfx 1: Rhino PCI BAR0 50100000 IOMem mapped at ffffc90008d7c000 [ 71.985504]

> On Thu, May 28, 2009 at 02:00:15PM -0500, research at businesstz.com wrote: >> Hello >> >> May i please know if asterisk is now supporting sip call encryption. It >> has been a requirement from one of my client to ensure that all >> conversation is well secured from any potential sniffers or inside >> hackers >> >> I have reviewed and shall

Aloha, I'm not sure why I'm getting this error, but I can't seem to get chan_dahdi to load. SIP & IAX2 are working fine. Debian 4 w/ 2.6.28 kernel. Asterisk 1.6.1.5, dahdi-linux 2.2.0.2, dahdi-tools-2.2.0 CLI> module load chan_dahdi.so Unable to load module chan_dahdi.so Command 'module load chan_dahdi.so' failed. [Sep 1 10:57:51] WARNING[31696]: pbx.c:4550

What is dahdi.auto_assign_spans and why should you care? In later versions the kernel module dahdi[Q] includes a new parameter: auto_assign_spans. It defaults to 1, and if you set it to 0, DAHDI can start behaving in strange and completely expected ways. Chances are the default will be set to 1 in a future version. Here is why you'll want to set it yourself. Up until DAHDI 2.5, hardware

such file or directory" on pure-IP platform in which I installed asterisk-libpri-dahdi trilogy. Maybe, it's me while following README instructions, maybe README instructions could be improved or maybe it's wrongly labeled messages ? That's why I told myself : I'm waiting too much from doc ? is a pure-IP platform too specific ? what is the official policy ? README starts with

On Thu, Jul 15, 2010 at 10:19:10AM -0700, Steve Casto wrote: > > https://issues.asterisk.org/view.php?id=17529 > Thanks Tzafrir: > Unclear on how to apply patch, here is what I get: > [root at localhost asterisk-1.4.32]# patch -p1 < ../bug17529.diff.txt > can't find file to patch at input line 5 > Perhaps you used the wrong -p or --strip option? > The text

Hi list, I'm trying to setup an asterisk 1.8.0 with MFC/R2, but I'm having these error messages loading chan_dahdi: > module load chan_dahdi.so ERROR[9241]: chan_dahdi.c:11848 mkintf: Signalling requested on channel 1 is MFC/R2 but line is in ISDN PRI signalling ERROR[9241]: chan_dahdi.c:16180 build_channels: Unable to register channel '1-15' I got the config in

Hi, After upgrading to DAHDI 2.4.0 from Zaptel, I noticed a lot of HDLC errors on my console: [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 These errors prevented calls from being made and received on my PRI spans. This seems

Hi I have been having a rough time getting a Sangoma A200/Remora FXO/ FXS Analog AFT card set up properly. The main issue is that the card has four ports and as far as I can tell Asterisk is only seeing two. On the two that it recognizes the "Green" FXS ports are not green, they just are not lit. The "RED" FXO ports are indeed red, but from what I have read your not

Some recent issues I had with hardware seem to come back to not understanding two very similarly named files: /etc/asterisk/dahdi-channels.conf /etc/asterisk/chan_dahdi.conf I've modified the chan_dahdi.conf to work now, but it would appear all I needed to do was include dahdi-channels.conf in chan_dahdi.conf and the problem would not have persisted? Is it me or is that a bit Monty Python?

Hi All, I must be doing something really stupid as I can't get DAHDi working in Asterisk. It is loaded and working in Linux fine. *CLI> module load chan_dahdi Unable to load module chan_dahdi Command 'module load chan_dahdi' failed. [2010-03-08 14:05:34 CST] WARNING[26926]: loader.c:393 load_dynamic_module: Error loading module 'chan_dahdi': libpri.so.1.4: cannot

Hi all, Last night I went to replace an Asterisk 1.4 + mISDN + b410p box with Asterisk 1.6.2 and DAHDI BRI - to no avail. I had two servers so copied network setting etc from the working one, moved the card across, ran dahdi_genconf etc and it didn't work. Here's the console output with notices disabled: lucas*CLI> pri intense debug span 1 Enabled debugging on span 1 [Dec 16

I have Asterisk 1.4.24 en a Digium TDM410 with EC and with 3 FXO modules. When I plug one PSTN-line into a FXO-port I am able to receive calls on this line and I can also make calls from an internal SIP-phone to the external PSTN-network. Still I am bothered about something that appears on the CLI when I do a reload chan_dahdi.so : asterisk*CLI> reload chan_dahdi.so -- Reloading module

I am having problems getting a Nicherons TDM400P wildcard clone to dial out. Everything appears to be configured correctly, but although I see call progress, it never seems to actually pick up the phone. (The following is a test of 911 emergency, where I substitute 811 [repair service] as the actual number dialed.) *CLI> -- Executing [911 at from-internal:1]