Displaying 20 results from an estimated 20000 matches similar to: "DAHDI help"
2014 Jul 14
2
Issue with new Te133
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
2009 Feb 25
4
TE121 on Asterisk
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
2009 Aug 25
2
Echo
<!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
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 Aug 10
1
PRI D-channel bouncing
I need some help getting a system running for one of my company's
plants. I am running AsteriskNow 1.7 with Asterisk 1.6.2.10 and
FreePBX 2.8.0.2.
My D-Channel keeps bouncing. The telecom tech told me he thought that
I might be using the wrong sync source, and I think I might have been,
but I changed DAHDI system.conf to "span=1,1,0,ESF,B8ZS" (from
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
======================
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
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:
2008 Dec 27
2
help with DAHDI hangup on calling out.
I installed DAHDI (2.1.0.3) on a machine with asterisk 1.4.22 and libpri
1.4.7
and I am getting the error:
-- Requested transfer capability: 0x00 - SPEECH
-- Called 23/317506XXXX
-- Channel 0/23, span 1 got hangup, cause 99
-- Hungup 'DAHDI/23-1'
on DIALING out. Calling in seems to work just fine.
Seems like everything is configured fine...
system.conf
2011 Jun 14
1
How to set a HA8 board + B400M in NT mode ?
Hi,
1. Is there any manual entry about modprobe's options relative to a given
Dahdi driver (wctdm24xxp, for instance) ?
2. When loading a wctdm24xxp driver, is there any parameter to pass to
modprobe to configure a span in NT/point to point mode ?
3. After running dahdi_cfg -vvvvv , I can read with dmesg :
[ 1986.289277] wctdm24xxp 0000:04:06.0: xhfc: Configuring port 0 span 1 in
TE mode
2009 May 19
2
Unable to make outbound calls
I've got an asterisk 1.4.24 box with dahdi complete 2.1.0.3+2.1.0.2
I've got a 2 port T2XXP card attached with on T1 currently plugged in.
Inbound calls work fine, but outbound fail with the rather cryptic:
[May 19 17:28:07] WARNING[11360]: app_dial.c:1237 dial_exec_full: Unable to
create channel of type 'DAHDI' (cause 0 - Unknown)
There are similar threads I've found on the
2010 Sep 01
2
Freepbx + Asterisk problem - NEED HELP
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)
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
2009 May 27
3
1.6.0.9: Now "Unable to create ... 'DAHDI'"
Still trying to upgrade to 1.6.0.9 for 1.4.
It worked - it worked all day yesterday, but this morning:
-- Executing [646xxxyyyy at longdistance:1]
Answer("SIP/172-08276a60", "") in new stack
..........
-- Executing [646xxxyyy at longdistance:6] Dial("SIP/172-08276a60",
""DAHDI/g2"/1646xxxyyyy") in new stack
May 27 09:56:57]
2010 May 27
2
BRI card(B800P) doesn's work with DAHDI(wcb4xxp) in NT mode
Dear Supports,
I was attempting to install BRI Card(OpenVox B800P) with wcb4xxp in NT mode .But I can not make it worked!
Could you please give me some hints? Thanks in advance!
Here are my environments:
------------------------------
CentOS-5.3
Kernel-2.6.18-164.el5
asterisk-1.6.1.6
dahdi-linux-complete-2.3.0+2.3.0
libpri-1.4.10.2
OpenVox-B800P(the first port is spliting into
2008 Sep 05
1
dahdi & tdm400p: no luck
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 ;
2008 Nov 26
7
Dahdi, b410p and looping from 1 port to another
Hello,
Is it possible, for testing, to connect an cat5 straight patch cord between
2 ports of a Digium B410P card and use these 2 ports as a normal dahdi trunk
?
I've tried this:
One port is set as NT, the other as TE.
I would expect timing to come for system hardware so I choose in
/etc/dahdi/system.conf :
span=1,0,0,ccs,ami
span=2,0,0,ccs,ami
Results:
- both ports lights are green
-
2009 Aug 04
1
dahdi_scan doesn't recognize an OpenVox A400E
Hi everybody,
In an Asterisk 1.6.0.5, dahdi-linux-2.1.0.4, dahdi-tools-2.1.0.2, with a
Digium B410P and an OpenVox A400E, I can't make "dahdi_scan" to recognize
the OpenVox. This card was working correctly but suddenly stopped working
and I cannot make it work again. Both ?lspci? and ?dahdi_hardware? detect it
but ?dahdi_scan? not and I cannot use it.
>lsppci:
*0a:00.0
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
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]: