similar to: dahdi show status command not avilable in CLI

Hello, After installing on Ubuntu 10.04 using the tutorial on http://hmontoliu.blogspot.com/2010/03/installing-asterisk-and-freepbx-on.html I have a running instance of Asterisk. PROBLEM: result of dahdi_cfg: DAHDI Tools Version - 2.2.1 DAHDI Version: 2.2.1 Echo Canceller(s): MG2 Configuration ====================== Channel map: Channel 01: FXS Kewlstart (Default) (Echo Canceler: mg2)

Have a new TE133 in a dell R320. dahdi_cfg -vvv shows: DAHDI Tools Version - 2.9.1 DAHDI Version: 2.9.1 Echo Canceller(s): Configuration ====================== SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1) Channel map: Channel 01: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 01) Channel 02: Clear channel (Default) (Echo Canceler: mg2) (Slaves: 02) Channel 03: Clear

The TDM410P doesn't support 'hvac', only the obsolete TDM400P supports that option was for the old phones that have a neon light (or equivalent LED+ZENER ciruit). Are other phones off the TDM410P (other than the VTECH) working, or is the Vtech the only model with VMWI available to you. I'm not able to check at the moment, I have copied the asterisk-users list, someone else may

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 All, Running asterisk 11.25.3, the /proc/cpuinfo says Intel(R) Xeon(R) CPU X5675 @ 3.07GHz lsmod | grep dahdi gives dahdi_transcode 16384 1 wctc4xxp dahdi_voicebus 61440 2 wctdm24xxp,wcte12xp dahdi 225280 11 wctdm24xxp,wcfxo,wctdm,dahdi_transcode,oct612x dahdi_voicebus,wcb4xxp,wct1xxp,wct4xxp,wcte11xp,wcte12xp crc_ccitt 16384 2

Hi all! I'm new with telephony cards and DAHDI drivers. I have installed Asterisk NOW 3.0.0 and update to Asterisk 11.7.0, modules are update too. I'm following the installation guide of Atcom [1] for AX1600P analogic card, modules are loaded [root at pbx ~]# lsmod | grep -E "hisax|netjet|dahdi" netjet 14618 0 isdnhdlc 4523 1 netjet mISDNipac

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]:

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

Looking for some help from the UK please. I backed up all my Asterisk configuration before re-installing the server from 32 -> 64 bit. Unfortunately I did not transfer the backup to another machine!!!!! I now have a TDM400P that is not picking up the line. Can you see what I have done wrong when I have rebuilt the config please: dahdi_scan ---------- [1] active=yes alarms=OK

As best i could figure it out, I've installed dahdi and rc4. My TDM400P doesn't answer fxo or fxs. /etc/dahdi/system.conf: loadzone = us defaultzone=us fxoks=1,2 fxsks=4 /etc/asterisk/chan_dahdi.conf: [house-phones] context=internal ; Uses the [internal] context in extensions.conf signalling=fxo_ks ; fxo_ks Use FXO signalling for an FXS chanel dahdichan => 1 ;

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]

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

The card you installed has FXO or FXS modules in it ????? are you getting your lines directly from the telco co??? Doug D On Mon 23/08/10 8:37 AM , Cassius Smith cassius at cassius.org sent: * -----Original Message----- * From: Todd Reese * Reply-to: Asterisk Users Mailing List - Non-Commercial Discussion * To: asterisk-users at lists.digium.com [3] * Subject: [asterisk-users] Dahdi

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> I recently upgraded my Asterisk system to Dahdi and now I have an echo <br> problem. <br> <br> I am running Asterisk 1.4.25 with Dahdi Complete 2.2.0, on a Digium <br> TE121B PCI express

Hi All; To overcome the echo problem, what mainly I have to do in the configuration other than the following line in the system.conf under dahdi directory? echocanceller=mg2,1-16 1) How can I know if the digium card supporting echo cancellator? 2) If I am getting a message in the consol that unable to enable the echo cancelator, then what does it means? The hardware is not supporting echo

Hi, I have a X101P card and am running Asterisk SVN-trunk-r226890. The X101P card seems to be identified properly: debian:/usr/src/dahdi-tools# dahdi_hardware pci:0000:01:01.0 wcfxo+ e159:0001 Wildcard X101P debian:/usr/src/dahdi-tools# dahdi_cfg -vv DAHDI Tools Version - SVN-trunk-r7409 DAHDI Version: SVN-trunk-r7445 Echo Canceller(s): MG2 Configuration ======================

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

Hi. I am having problems with dahdi using kernel 2.6.32. I am using 2.6.30 kernel and it works fine -- here is the output of dahdi_cfg -vv ++ dahdi_cfg -vv DAHDI Tools Version - SVN-trunk-r8670 DAHDI Version: SVN-trunk-r7445M Echo Canceller(s): Configuration ====================== Channel map: Channel 01: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01) Channel 04: FXS Kewlstart

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]

I am running Asterisk 1.6.2.17.2 with a Openvox A400 card with 2FXO/2FXS modules. I'm trying to set-up things to route analog fax calls from a FXO port to an analog fax machine on a FXS port on the same card. Outgoing faxes work just fine. But incoming faces are routed to the right DAHDI extension, but the call dropped right as the fax machine rings for the first time. The fax machine