Displaying 20 results from an estimated 10000 matches similar to: "dahdi driver not getting install"
2012 Nov 02
1
Unable to create channel of type 'DAHDI' (cause 17 - User busy)
Hi,
I have 6 Red FXO with TDM2400p in my PC. I have install asterisk and dahdi
driver.
Scenario is
jitsi-----> asterisk server-----> analog PBX ----> landline phone
I configured this scenario as follow
in chan_dahdi.conf file
; General options
[channels]
usecallerid=yes
hidecallerid=no
callwaiting=yes
threewaycalling=yes
transfer=yes
2012 Nov 15
1
Detected alarm on channel 5: Red Alarm
Dear,
i using this scenario.
jitsi---> asterisk---->EPABX------> Local Telephone
when i am calling from jitsi to no 88 its giving this message and getting
busy tone.
== Using SIP RTP CoS mark 5
-- Executing [88 at myphones:1] Dial("SIP/sandeep-00000004",
"DAHDI/g0/88,20,rt") in new stack
-- Called g0/88
[Nov 15 09:53:54] WARNING[3169]: chan_dahdi.c:7536
2006 Jun 26
1
domU to domU configuration
Was setting up 2 domUs on the same xen machine. Is there any benefit in using
the same bridge vs. two separate bridges (one for each domU) incases where we
are interested in only domU-domU network traffic? What will be the preferred
configuration?
thanks in advance,
harish
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
2014 Jun 13
1
dahdi-linux 2.6.2 failing to compile with linux 3.13
Hello,
I'm getting the following errors when compiling dahdi-linux 2.6.2 under
Ubuntu 14.04 with kernel 3.13.0-24-generic.
I did google and found one thread suggesting the errors should be fixed in
2.6.2, and another suggesting to try 2.4 which didn't make sense but I
tried anyway, and it gave similar warnings.
Would anyone know how to make it compile? Thanks in advance.
make[1]:
2013 Feb 15
2
dahdi-linux dahdi-tools and libpri/libpri-
hello ,
i try to install dahdi-linux/dahdi-linux-current.tar.gz
,dahdi-tools/dahdi-tools-current.tar.gz
and libpri/libpri-1.4-current.tar.gz
but got these error msg
make -C drivers/dahdi/firmware firmware-loaders
make[1]: Entering directory
`/usr/src/dahdi-linux-2.6.1/drivers/dahdi/firmware'
make[1]: Leaving directory
`/usr/src/dahdi-linux-2.6.1/drivers/dahdi/firmware'
make -C
2013 Aug 14
3
DAHDI wct4xxp high system CPU on idle?
I have a system running CentOS 5.9 and DAHDI 2.6.2 with a 2-port E1 card
using the wct4xxp driver (also using Asterisk 11.5.0, but that isn't
relevant to the question).
With DAHDI and Asterisk started, the system appears to run normally, as
far as I can tell from limited testing.
I am monitoring User, System and Nice CPU usage using SNMP and MRTG, and I
have noticed that when I have started
2013 Jun 02
1
Missing dahdi-firmware RPM in asterisk-current repo at http://packages.asterisk.org
Hi,
The dahdi-firmware package seems to be missing in the asterisk-current
repo on http://packages.asterisk.org
--> Finished Dependency Resolution
Error: Package: dahdi-linux-2.6.2-1_centos6.x86_64 (asterisk-current)
Requires: dahdi-firmware
Can this please be fixed.
Thanks,
Patrick
2013 Jun 13
2
A quick question in terms of DAHDI channel
Hello,
I have an Asterisk 1.8.11 installation. When I built up this Asterisk, I didn't install DAHDI channel, if I issue command
connect*CLI> core show channeltypes
I would have response like:
connect*CLI> core show channeltypes
Type Description Devicestate Indications Transfer
---------- -----------
2013 Apr 16
2
erro compiling dahdi
Hello,
when compiling dahdi (CentOS 2.6.18-348.3.1.el5) I get the following error :
In file included from
/usr/src/dahdi-linux-complete-2.6.1+2.6.1/linux/drivers/dahdi/xpp/xpd.h:26,
from
/usr/src/dahdi-linux-complete-2.6.1+2.6.1/linux/drivers/dahdi/xpp/card_bri.c:29:
/usr/src/dahdi-linux-complete-2.6.1+2.6.1/linux/drivers/dahdi/xpp/xdefs.h:152:
error: conflicting types for
2013 May 27
2
RED on DAHDI channel
Asterisk 11.1
We have a situation where one of our incomings POTS lines will not
answer. There are 2 lines configured by the Telco as a rollover group
(rings the line that is not busy) and they feed into a Digium AEX410 on
the server. The most recent time this happened, I did a
/etc/init.d/dahdi status and saw this:
### Span 4: WCTDM/1 "Wildcard AEX410"
*53 FXO FXSKS
2013 Jun 05
1
incoming DAHDI Channel explained
Hi,
I use a Sangoma A104d-Card (with 4 x germany E1). I process some calls
via an AGI-Script. When parsing the AGI-Variables I can see one that
look like that:
[agi_channel] => DAHDI/i3/211123456-89c
What hat do the values mean in detail, please?
DAHDI : this is clear
i3 : does it mean, that the call comes in via E1-Port 3?
211123456 : Incoming-Call Caller-ID
-89c : ?
WANPIPE Release:
2006 Jan 17
1
Asterisk & Genesys integration
Hi All,
Would it be possible to integrate Asterisk with Genesys CTI?
Has anyone done any work on Asterisk/Genesys integration?
Regards
Ivan Marakovic
Operations Manager
Link:Q
<mailto:ivan@qita.com.au>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060117/bcb10257/attachment.htm
2015 Sep 26
8
CentOS 6 - Support for CanoScan LiDE 210
Hi folks,
for some time I used a HP 2840 AiO device, connected via LAN, to scan
documents. As scanning application I use xsane. I want to replace that
HP scanner by a CanoScan LiDE 210.
# LANG="" yum info libsane-hpaio
...
Installed Packages
Name : libsane-hpaio
Arch : x86_64
Version : 3.14.6
Release : 3.el6
Size : 148 k
Repo : installed
From repo
2015 Sep 30
1
CentOS 6 - Support for CanoScan LiDE 210
Am 26.09.2015 um 14:22 schrieb Akemi Yagi:
> On Sat, Sep 26, 2015 at 3:08 AM, Meikel <meikel at fn.de> wrote:
>
>> scanner by a CanoScan LiDE 210.
>> Installed Packages
>> Name : sane-backends
>> Arch : x86_64
>> Version : 1.0.21
>
>> I have no idea what I can do now. It is not clear to me if sane-backends
>> package really
2013 Jun 03
1
DAHDI 2.6 and OPENVOX cards
B.H.
Hello, all :-)
We have some OPENVOX D410P PRI cards and we are successfully using them
with Asterisk boxes which are based on stock ubuntu 12.04 DAHDI and
Asterisk packages.
The card is recognized by DAHDI as 'Wildcard TE410P (2nd Gen)' and it uses
wct4xxp driver.
Now, i'm trying to run this hardware with DAHDI 2.6.2 package which is
available from asterisk.org site and looks
2016 Mar 01
1
DAHDI-Linux and DAHDI-Tools 2.11.1 Now Available
The Asterisk Development Team has announced the releases of:
DAHDI-Linux-v2.11.1
DAHDI-Tools-v2.11.1
dahdi-linux-complete-2.11.1+2.11.1
This release is available for immediate download at:
http://downloads.asterisk.org/pub/telephony/dahdi-linux
http://downloads.asterisk.org/pub/telephony/dahdi-tools
http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete
Notable changes:
Raised E1
2016 Mar 01
1
DAHDI-Linux and DAHDI-Tools 2.11.1 Now Available
The Asterisk Development Team has announced the releases of:
DAHDI-Linux-v2.11.1
DAHDI-Tools-v2.11.1
dahdi-linux-complete-2.11.1+2.11.1
This release is available for immediate download at:
http://downloads.asterisk.org/pub/telephony/dahdi-linux
http://downloads.asterisk.org/pub/telephony/dahdi-tools
http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete
Notable changes:
Raised E1
2013 Mar 08
0
DAHDI-Linux and DAHDI-Tools 2.6.2 Now Available
The Asterisk Development Team has announced the release of:
DAHDI-Linux 2.6.2
DAHDI-Tools 2.6.2
DAHDI-Linux-Complete 2.6.2+2.6.2
This release is available for immediate download at:
http://downloads.asterisk.org/pub/telephony/dahdi-linux
http://downloads.asterisk.org/pub/telephony/dahdi-tools
http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete
2.6.2 is a bugfix release of which the
2013 Mar 08
0
DAHDI-Linux and DAHDI-Tools 2.6.2 Now Available
The Asterisk Development Team has announced the release of:
DAHDI-Linux 2.6.2
DAHDI-Tools 2.6.2
DAHDI-Linux-Complete 2.6.2+2.6.2
This release is available for immediate download at:
http://downloads.asterisk.org/pub/telephony/dahdi-linux
http://downloads.asterisk.org/pub/telephony/dahdi-tools
http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete
2.6.2 is a bugfix release of which the
2009 Nov 28
1
DAHDI/1-2 v. DAHDI/2-1 ??
I've got a single TDM 400P board with two internal ports and 1 external.
chan_dahdi.conf:
context=internal ; Uses the [internal] context in extensions.conf
signalling=fxo_ks ; fxo_ks not auto Use FXO signalling for FXS
group=0
channel => 1 ; Telephone attached to port 1
channel => 2 ; Telephone attached to port 2
context=incoming-pstn-line ; Incoming calls