Displaying 20 results from an estimated 6000 matches similar to: "Dropped calls when all DAHDI lines in use"
2019 Jun 06
3
error compiling dahdi for recent kernels
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
2010 May 22
2
About Sangoma cards and Asterisk integration with other PBX
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all!
I had the opportunity to test a Sangoma A200 card and I have some doubts
that I would like to consult:
I tried to detect the card and I had no success using the wctdm module
with DAHDI. I guess this is because electronics is different because the
TDM400P and OpenVox A400P cards have separate modules for each channel,
while the Sangoma A200
2012 Oct 16
1
B200p card - use dahdi or mISDN?
I've just bought an OpenVOX B200p ISDN card - and if I remember
correctly from last time I used one of these - it is possible to use
either DAHDI or mISDN with it. Are there any factors to consider when
choosing which software to use? Is one better than the other - or does
one have features which are not present in the other?
I will be using it for a simple PBX, with 2 ISDN channels as
2010 Jun 17
4
Asterisk + Dahdi does not work with BRI NT mode
Hi all,
As i tested with Asterisk+dahdi+libpri with openvox BRI with NT mode, the
ISDN phone does not work.
There is the setting and error.
***********************Enviroment**********************************
Asterisk-1.6.1.18
dahdi-linux-2.3.0.1
dahdi-tool-2.30.
libpri-1.4.11.2
CentOS-5.5
OpenVox B400P
********************************************************************
In my case , I set prot 1
2010 Nov 16
1
DAHDI / dial in / overlap digits / timeout
Hi,
our Asterisk is connected to an E1 port. So we are using the
DAHDI-Driver. Please , how do I tell the driver/Asterisk to wait for
overlap digits for in-calls? I found the option "overlapdial=yes" but I
did not try yet. Is that "my" option? Is there any option for setting an
timeout?
Thorsten
2009 Dec 08
2
Starting and installing Dahdi (2.2.0)?
Hello
Unless I overlooked it, the "Asterisk Reference Information
Version 1.6.1.6" at www.asterisk.org/docs doesn't include instruction
on how to start Dahdi when used to drive a TDP PCI card (OpenVox A400P
with a single FXO module
www.openvox.cn/products/show.php?itemid=20&lang=2).
I'd like to know...
1. How to start Dahdi manually. Is this the right way?
modprobe
2009 Sep 25
4
DAHDI disconnect supervision timing
Ok so this is officially driving me crazy. I have an Asterisk 1.6.1.6
install with DAHDI/DAHDI tools (latest) and an OpenVOX TDM400 card with 1
FXO port and 1 FXS port. I have a POTS line from my phone company attached
to the POTS line.
I have asked for "disconnect supervision" to be provisioned on my line and
they claim to have added it. However, my scenario is as follows:
I receive a
2009 Apr 27
4
[UK SPECIFIC] DAHDI and a OpenVox Card
Hi,
Built a new server at the weekend and install Asterisk 1.6.0.9 and IAX and SIP work great :) The one problem I am having is getting the OpenVox (TDM400 type card) to work. It is successfully identified using WCTDM kernel module and dahdi_scan picks it up just fine. The issue is when I try and setup dahdi_channel.conf as it fails everytime. When running asterisk -rvvvv I see the port pick
2018 Jun 24
2
Recommended Linux version or how to compile DAHDI on Fedora?
Hi,
I’m currently using 32 CENTOS 5 but it’s now unsupported. I only
have a 32 bit processor and CENTOS no longer supports 32 bit so
I need to move on. I’ve installed the current version of 32 bit
Fedora and I can’t get the latest Dahdi to build. Even tried
downloading the early release DAHDI from github with no luck.
Any recommendation for which 32 bit LINUX to use going forward?
Or
2010 Feb 20
0
outgoing callerid problem
Hi,
I have a B410P card with bri_cpe signalling and two Openvox analog card
(A1200p, A800P) with fxo_ks signalling. From the ISDN we have
Point-Point 10 connection with a 10 public phone number range. If I
receive a public call, the asterisk recevies the last two digit from
this range, so it works, I can receive all the 10 numbers. If I'd like
to dial from an exten which I have to
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
2010 Feb 17
2
asterisk dahdi fax problem
Hi,
I run into a problem and I'm not shure what do I misconfigure. I've a
B410P ISDN card with bri_cpe signalling and two Openvox (A1200, A800)
cards with fxo_ks signalling, all with dahdi drivers. I can receive fax
from a public number, but I can't send fax. The CLI says it picks up the
line but no dialing. I tried the extension with an analog phone, it
works fine, I can dial
2010 May 18
1
Callerid with DAHDI
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all!
I'm testing a telephone connected to FXS port of a Sangoma A200 card.
But I'm observing that callerid is not working. The configuration that
I'm using in chan_dahdi.conf is the following one:
- ---------------------------------------------------------------------
;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
2008 Nov 12
4
test OpenVox B400P and junghans card for dahdi BRI wcb4xxp
hello:
thanks for Tzafrir Cohen for dahdi testing.
I installed dahdi-2.1-r3c svn code and asterisk1-6
for testing OpenVox B400P and junghans card. i fund that there is bug (i think) to dectect NT or TE mode. actually on the board,
i set it as TE mode, but after start wcb4xxp, but
it show the port is NT mode. to detect the TE mode, I modefy the code in base.c
2009 Sep 15
1
DAHDI hangup detection
I am running Asterisk 1.6.1.6 and DAHDI/DAHDI tools 2.2.0.2 compiled
from source on a Debian Lenny box, also running FreePBX 2.5.2. I also
have an OpenVOX TDM400 card installed with an FXO port on port 1, and an
FXS port on port 2. I have a POTS line installed and working on the FXO
port.
However I've encountered a weird problem that I can't seem to figure
out. I have incoming POTS
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
2010 Nov 13
1
CallerID from Samsung PBX line on FXO
Hi,
I've now set up Asterisk to interface with our current Samsung iDCS 100 PBX via an 8SLI analogue extension card in the Samsung and an Openvox A400P04 4-FXO card in the Asterisk box. It all works in that I can place calls in both directions from the office Samsung extensions and Asterisk SIP extensions. The only tricky bit was getting the FXO to detect hang-up from the Samsung correctly -
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
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 Jun 21
1
DAHDI: Inbound BRI call, DDI not presented
Hello-
I have a system with one D410P and one B200P (both OpenVox). All is
well with the D410P, inbound and outbound, and I can initiate calls on
the B200P BRI span, but there may be something wrong with my inbound
BRI setup: there is no indication of an inbound call when I dial in to
it from the PSTN.
When I run "pri intense debug" and make a call to the BRI span, I can
see a