similar to: dahdi "hungup" after each ring

So, tweaking configs, rebuilding this and that... restarting, twiddling, it works (yeah!), but fails on re-boot to work at all. Consistently, though. I believe it comes down to this: I can call out only *after* I've received a call. So, cold boot. Then: modprobe dahdi modprobe wctc4xxp modprobe wcfxo dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.1.0.3

Good day , I have configured TDM410P (asterisk 1.6.x) on Cent OS 5, but dahdi take some time to hangup the call when playing the IVR..(it will send the hangup signal after finishing the IVR promt..) is there any specific setting to avoid such incidents ? iam using busycount as 3, signalling=fxs_ks ;toneduration=100 callwaiting=yes threewaycalling=yes callreturn=yes

Hi, I am using TDM400 card with 3 fxs and 1 fxo. I am struggling to detect hangup tone or disconnect supervision tone from my CO. I attached the recorded wav file which contains my telco's disconnect supervision. I am using , asterisk-1.4.33.1 dahdi-linux-complete-2.3.0.1+ 2.3.0 OS => Debian-lenny 5 users.conf ------------- [trunk_1] trunkname = pstn ; GUI

Hi! I have an analog line connected to my asterisk and when I try to answer a call I get this -- Starting simple switch on 'DAHDI/7-1' -- Executing [s at from-pstn:1] Answer("DAHDI/7-1", "") in new stack -- Executing [s at from-pstn:2] Playback("DAHDI/7-1", "vm-intro") in new stack -- <DAHDI/7-1> Playing 'vm-intro' (language

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

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

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

Hey, all. Just added an analog card to our dual-T1 system... and clearly I'm doing something wrong. Less interested in having the specifics pointed out than in finding out how/why certain things work. So, really, three things: * What the bloody Hell is the difference between dahdi-channels.conf and chan_dahdi.conf? (And who thought it was a good idea to have two files with,

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

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 =>

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

-- Attempting call on DAHDI/1wwwwww for smvoice_callprogress at smvoice-dialout:1 (Retry 1) [Oct 16 14:36:42] WARNING[16408]: chan_dahdi.c:8132 dahdi_request: Unknown option 'w' in '1wwwwww' [Oct 16 14:36:43] WARNING[16408]: chan_dahdi.c:1481 dahdi_enable_ec: Unable to enable echo cancellation on channel 1 (No such device) Does DAHDI not know about the W ??? I think zaptel used

Hi, I've always used dahdi-genconf to just create the dahdi-channels.conf and since our PRI is fairly simple (just dump all the channels into one group) it works with dialing with dahdi/g1/(number). I'm trying to understand the file though for my own reference. It seems the file looks like this: group=0,11 context=from-pstn switchtype = national signalling = pri_cpe channel => 1-23

Hi, I noticed that Dahdi starting producing these error messages: ERROR[29250] chan_dahdi.c: No more room in scheduler ERROR[29250] chan_dahdi.c: Asked to delete sched id -1??? during which time I could not send any calls or receive calls on at least one of my Dahdi spans. The only way to clear the problem seemed to be to restart Asterisk. It appears to start after the following message

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

Hi, I'm trying to install voicemail-imap support but there seems to be a missing module: imap_tk checking for mandatory modules: IMAP_TK... fail configure: *** configure: *** The IMAP_TK installation appears to be missing or broken. configure: *** Either correct the installation, or run configure configure: *** including --without-imap. My configuration Ubuntu 14.04 LTS Asterisk

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

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