similar to: Dahdi 2.4.0 and Squeeze

After a reboot, I can't reproduce the problem anymore which is quite frustating. 2011/6/14 Tzafrir Cohen <tzafrir.cohen at xorcom.com> > On Tue, Jun 14, 2011 at 03:44:32PM +0200, Olivier wrote: > > 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

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

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

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

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

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

Hello everybody, I try to install -Ubuntu 8.04 server- a B410P and a TDM2400P together with Asterisk 1.4.26-2, dahdi-linux-2.2.0.2 and dahdi-tools-2.2.0. Problem I face is the following one: CLI> module load chan_dahdi.so == Registered application 'DAHDISendKeypadFacility' == Registered application 'ZapSendKeypadFacility' == Parsing

Hi i have a tdm2400p and installed asterisk 1.4.11 with zaptel 1.4.5 im having an error message when in running asterisk with the tdm card in. here's the error from the console of asterisk: [Nov 18 10:30:44] ERROR[5557]: chan_zap.c:7489 mkintf: Unable to get span status: Inappropriate ioctl for device [Nov 18 10:30:44] ERROR[5557]: chan_zap.c:10466 build_channels: Unable to register channel

Hi All; Suddenly the zaptel channel look like stop working and it is giving me this error when I do zap restart: [May 24 19:30:21] ERROR[2772]: chan_zap.c:7219 mkintf: Unable to open channel 1: Device or resource busy here = 0, tmp->channel = 1, channel = 1 [May 24 19:30:21] ERROR[2772]: chan_zap.c:10582 build_channels: Unable to register channel '1,2' To what it could be related?

I have spent some time this morning trying to add an Astribank to our current Asterisk, but it failed, so I just removed the hardware, restore the config files to the original setup and started asterisk.; I could see that no Zap channels are started so I did load chan_zap.so: pbx*CLI> module load chan_zap.so [Feb 26 10:32:18] WARNING[3809]: pbx.c:2968 ast_register_application: Already have an

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

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

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

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

What is this error ? is this harmful ? *CLI>*CLI> dahdi restart [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23. [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to 'vmsecret' (on reload) at line 31. [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422

Hi, I tried again getting DTMF detection on my ISDN devices with dahdi going again. I used the channel debug to see whether asterisk sees the frames and detects them as DTMF. Interestingly here's what works: 1. GSM phone -> chan_dahdi g1 -> asterisk -> can_sip -> SIP phone Both the GSM phone and the SIP phone can issue DTMF that will be detected as features (transfer) 2.

Hi, When reading logs, I can see a couple of lines such as : full.6:[Jun 30 15:53:26] NOTICE[6599] chan_dahdi.c: PRI got event: Alarm (4) on Primary D-channel of span 1 full.6:[Jun 30 15:53:32] NOTICE[6599] chan_dahdi.c: PRI got event: No more alarm (5) on Primary D-channel of span 1 full.6:[Jun 30 15:53:32] NOTICE[6607] chan_dahdi.c: Alarm cleared on channel 1 full.6:[Jun 30 15:53:32]

Aloha, I'm finishing up the final touches on this install, and have run into an odd problem. I can't seem to get Caller ID on the analog phone lines working. It's a Digium AEX 410 card. I have Verbose set and a line to print the CID: I have usecallerid=yes and callerid=asreceived set in both chan_dahdi.conf and users.conf [analog] include=>default exten =>