similar to: configuring channels for dahdi

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

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

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)

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]

Hello, I just bought a TE121 T1/E1 card, and now trying to install it on a 1.4.23.1 asterisk with dahdi 2.1.0.4 Actually first everything went on well and i managed to see my card on dahdi. Here's the output: #asterisk# dahdi_hardware pci:0000:04:08.0 wcte12xp+ d161:8000 Wildcard TE121 and this is the scan: -------------------------- asterisk# dahdi_scan [1] active=yes alarms=RED

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

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]

Hi All, Sorry if this has been around a millions times.. I have been off this list for a few months now.. I have installed the latest asterisknow (upgraded asterisk to 1.6 as well) and I am having a hard time getting my X100P and TDM400P working.. Its all new to me with dahdi because my old server is still running Asterisk 1.0.2 so there have been lost of changes.. Can someone point me in

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]

From asterisk -cvvvvv == Parsing '/etc/asterisk/chan_dahdi.conf': == Found == Parsing '/etc/asterisk/users.conf': == Found -- Automatically generated pseudo channel [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23. [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi:

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

Hi all, I am having trouble setting the signalling method for the B410P using DAHDI. Asterisk complains that it has never heard of 'bri_cpe' or 'bri_net' - but it doesn't mind having 'pri_cpe' etc. ERROR[4294]: chan_dahdi.c:11327 process_dahdi: Unknown signalling method 'bri_net' Dahdi - dahdi-linux-complete-2.1.0.4+2.1.0.2 Asterisk - 1.4.23.1 Libpri - 1.4.9

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

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, Running 1.4.26.1 here. I have installed TE420B card in my server, and followed the appropriate steps (as far as I know to configure it). This TE420B is connected to a CLEC (T1s), so I am using pri_cpe as singalling type. When I dial out, I get this message: Dec 4 11:37:31] WARNING[27983]: app_dial.c:1275 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0

I keep getting a red alarm when trying to setup asterisk to use my TE420B EC. I only have a blank context setup in my extensions.conf as I haven't started to config that until I can clear this red alarm. I don't have physical access to the server, so I can't go reseat the modules/card/ethernet cable, though I have hands on location that have done this a couple times

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 ;

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