similar to: Problems With DAHDI on Ubuntu

Displaying 20 results from an estimated 9000 matches similar to: "Problems With DAHDI on Ubuntu"

2009 Mar 15
1
No hardware timing source found in /proc/dahdi
Hello all, Ok it is Sunday afternoon and I am going crazy. I have been running in circles so long that I can't think straight. As an example, I sent this message to the wrong address the first try, AAARRRRGGGGGGHHHHH. I have Asterisk 1.6.0.6 and DAHDI Tools Version - 2.1.0.2, DAHDI Version: 2.1.0.4, OpenSuSE 10.3 x86_64, tdm422 at the end of installing dahdi-linux and dahdi-tools I get:
2014 Feb 12
1
Problem/error with DAHDI tools 2.9.0.1
Hello, Getting this error on dahdi_cfg. Reverting to 2.8 the error goes away: *line 15: Unable to create 'dahdi_cfg' mutex.* Is this a problem? Thanks in advance. Full detail: [ebox]> dahdi_cfg -vvvvvvv DAHDI Tools Version - 2.9.0.1 DAHDI Version: 2.9.0 Echo Canceller(s): HWEC Configuration ====================== SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 2:
2010 May 23
2
Dahdi problems with kernel 2.6.32
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
2011 Apr 05
2
dahdi and linux-2.6.38
Under linux-2.6.38 I was able to compile and install dahdi, however when I ran dahdi_cfg -vv, I got an invalid argument on my fxs port. I have an old 400P card with one FXS and one FXO module. I have dahdi-trunk r9868 and dahdi-tools-trunk 8670. How can I get this to work correctly? Thanks in advance for any ideas. -- Your life is like a penny. You're going to lose it. The question
2010 May 28
1
[Dahdi/system.conf] "fxsks = 1" deprecated?
Hello I was editing files manually, and noticed that if I include the familiar "fxsks=1" in /etc/dahdi/system.conf, Dahdi fails loading: ===================== # cat /etc/dahdi/system.conf loadzone = fr defaultzone = fr fxsks=1 ===================== # /etc/init.d/dahdi start Loading DAHDI hardware modules: wctdm: [ OK ] /usr/share/dahdi/waitfor_xpds: Missing
2010 May 26
1
[Dahdi] "DAHDI_CHANCONFIG failed on channel 1"?
Hello I'm trying to install Dahdi through source code on a Fedora 13 host to use an OpenVox PCI card with a single FXO port, but dahdi_cfg -vv isn't happy. 1. After successfully running "make all; make install; make config", I edited /etc/dahdi/system.conf thusly: loadzone=fr defaultzone=fr fxsks=1 2. Then ran "dahdi_cfg -vv" which says: ------------- DAHDI Tools
2013 Nov 23
1
DAHDI Missing '/sys/bus/astribanks/drivers/xppdrv/sync'
Hello group, I am installing Asterisk on a new pc running Ubuntu 12.04.3 Server. ?I have dahdi-complete-2.7.0.1+2.7.0.1, and have tried 2.6.1 and 2.8.0-rc1 and 2.8.0-rc2. ?I am following along in the ASTERISK The Definitive Guide 4th Edition and on page 116 when I issue the command $ sudo /etc/init.d/dahdi start I get the following error: Loading DAHDI hardware modules: ? ?wctdm24xxp: done
2009 Apr 29
2
Something wrong with DAHDI signalling according to the CLI
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
2009 Mar 09
4
DAHDI and B410P (BRI)
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
2010 Mar 07
5
dahdi-2.2.1 & kernel-2.6.32: working for anyone?
I have a TDM400. Just updated Fedora 12 to kernel 2.6.32. Rebuilt and installed dahdi-2.2.1. kernel modules loaded. lsmod | grep wctdm wctdm 37233 0 dahdi 194985 1 wctdm lsmod | grep dahdi dahdi 194985 1 wctdm crc_ccitt 1549 2 dahdi,isdnhdlc dmesg: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.2.1
2016 Apr 12
3
Debian 8.4 : dahdi startup scripts ?
Hi Eric, > On 12 avr. 2016, at 17:48, Eric Cooper <ecc at cmu.edu> wrote: > > On Tue, Apr 12, 2016 at 04:36:58PM +0200, Bertrand LUPART - Linkeo.com wrote: >> I just made a asterisk / dahdi fresh install on Debian 8.4, and ended up with the following packages : >> [...] >> However, i can't find any dahdi startup script, neither init.d neither systemd
2009 Nov 03
1
dahdi channel not showing up
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 ======================
2013 Mar 28
3
dahdi-channels.conf vs. chan_dahdi.conf
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,
2009 Mar 10
3
configuring channels for dahdi
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]:
2009 Sep 27
2
DAHDI congestion problem
I am unable to dial out over a Wildcard TDM400P. This was working previously, so must have messed up the config somehow. I'm running Asterisk 1.6.0.15, with FreePBX 2.5.2.2. When I dial, I see: -- Executing [s at macro-dialout-trunk:19] Dial("DAHDI/1-1", "DAHDI/g0/9239220,300,") in new stack == Everyone is busy/congested at this time (1:0/1/0) It looks like the
2009 Mar 31
2
DAHDI with OSLEC
Hi, I've a problem: I can't configure DAHDI with ech canceller OSLEC. I have Asterisk 1.4.24 and DAHDI 2.1.0.2. I compiled also OSLEC. But when in /etc/dahdi/systems.conf I insert value echocanceller=oslec,1-4, command dahdi_cfg -vvvvvvvvvvvv give me an error about oslec. Someone can help me? Thanks Marco -------------- next part -------------- An HTML attachment was scrubbed... URL:
2013 Sep 04
1
dahdi configuration issue
Hello List, I have configure 2 sangoma card each with 8 PRI lines with dahdi 2.6 the problem is i can see all channels configured in dahdi_cfg 480 channels configured but when I see /dev/dahdi i can only see 240 channels. what could be problem I am using it wanrouter and when I put PRI in new card i only got calls on new line that means one of the card is inactive at same time all the lines and
2011 Jul 25
1
dahdi channels busy/congested
Dear all, i have a problem with a system running - Ubuntu 10.04 ( all updates done ) - ii asterisk 1:1.8.5.0-1digium1~lucid Open Source Private Branch Exchange (PBX) - ii asterisk-dahdi 1:1.8.5.0-1digium1~lucid DAHDI devices support for the Asterisk PBX I also use freepbx 2.9 for the configuration. Hardware is a Dell R410 and a Digium
2010 Aug 11
1
DAHDI config file system.conf
I have DAHDI 2.2.1 my system.conf file is : span=1,0,0,esf,b8zs bchan=1-23 dchan=24 echocanceller=mg2,1-23 loadzone = us defaultzone = us Its telling me: Running dahdi_cfg: DAHDI_SPANCONFIG failed on span 1: Invalid argument (22) [FAILED] What am I missing. Its straight PRI NI2.
2009 May 20
1
Channels configuration with DAHDI
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! Days ago I bought a OpenVox A400P card with a port FXS and another FXO that I am testing with my Asterisk installation in my house. I'm using Asterisk 1.4.24.1 with DAHDI Linux 2.1.0.4 and DAHDI Tools 2.1.0.2 on Debian GNU/Linux Lenny. I was reading "The future of telephony" and this [1] document looking for information about