similar to: Unable to create channel of type 'DAHDI' (cause 17 - User busy)

Displaying 20 results from an estimated 5000 matches similar to: "Unable to create channel of type 'DAHDI' (cause 17 - User busy)"

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
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
2011 Nov 11
2
10.0.0-rc1: dahdi doesn't see card
From asterisk -cvvvvv == Parsing '/etc/asterisk/chan_dahdi.conf': == Found == Parsing '/etc/asterisk/users.conf': == Found -- Automatically generated pseudo channel [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23. [Nov 11 17:43:28] WARNING[5756]: chan_dahdi.c:18155 process_dahdi:
2009 Feb 24
2
Configuring chan_dahdi.conf for Sangoma A200/Remora FXO/FXS Analog AFT card
Hi I have been having a rough time getting a Sangoma A200/Remora FXO/ FXS Analog AFT card set up properly. The main issue is that the card has four ports and as far as I can tell Asterisk is only seeing two. On the two that it recognizes the "Green" FXS ports are not green, they just are not lit. The "RED" FXO ports are indeed red, but from what I have read your not
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]:
2011 Mar 23
1
dahdi restart warning
What is this error ? is this harmful ? *CLI>*CLI> dahdi restart [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23. [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422 process_dahdi: Ignoring any changes to 'vmsecret' (on reload) at line 31. [Mar 23 14:01:06] WARNING[4314]: chan_dahdi.c:17422
2009 Sep 04
1
1.4.26-2, DAHDI-2.2.0, B410P and BRI
Hello everybody, I try to install -Ubuntu 8.04 server- a B410P and a TDM2400P together with Asterisk 1.4.26-2, dahdi-linux-2.2.0.2 and dahdi-tools-2.2.0. Problem I face is the following one: CLI> module load chan_dahdi.so == Registered application 'DAHDISendKeypadFacility' == Registered application 'ZapSendKeypadFacility' == Parsing
2018 Feb 15
2
Problem with DAHDI
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]
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 Mar 09
0
Asterisk 1.6.2.5 crash with chan_capi upon calling to PSTN
Hi, I am having a problem with (Asterisk is crashing) with a Fritz card PCI / chan_capi. Receiving Calls from PSTN works, but outbound calls make asterisk crash (Speicherzugriffsfehler/Segmentation fault). The crash occurs upon dialing with the other phone not even ringing. I hereby ask if somebody reading this list can confirm or disprove my issue. Does anbody run a recent asterisk 2.6 with
2009 May 23
1
1.6.0.9: Unknown signalling method 'pri_cpe' ??
I'm trying to upgrade from 1.4.24.1 to 1.6.0.9 with a TE120P card. I can't make any connection over the T1. From CLI: ERROR[26017]: chan_dahdi.c:14300 process_dahdi: Unknown signalling method 'pri_cpe' at line 37. cat chan_dahdi.conf cat chan_dahdi.conf [trunkgroups] [channels] language=en ;internationalprefix = 00 ;nationalprefix = 0 context=from-pstn switchtype=national
2009 Sep 01
2
chan_dahdi.so fails to load : Inappropriate ioctl for device
Aloha, I'm not sure why I'm getting this error, but I can't seem to get chan_dahdi to load. SIP & IAX2 are working fine. Debian 4 w/ 2.6.28 kernel. Asterisk 1.6.1.5, dahdi-linux 2.2.0.2, dahdi-tools-2.2.0 CLI> module load chan_dahdi.so Unable to load module chan_dahdi.so Command 'module load chan_dahdi.so' failed. [Sep 1 10:57:51] WARNING[31696]: pbx.c:4550
2013 Mar 14
3
ERROR: Unknown signalling method ss7
Hi all I installed DAHDI Version - 2.6.1 DAHDI Tools Version - 2.6.1 libss7-trunk Asterisk 11.0.1 from source on Fedora 12 x86_64. Now i`m unable to load chan_dahdi and libss7: myserver*CLI> module load chan_dahdi.so ?ERROR[10124]: chan_dahdi.c:17842 process_dahdi: Unknown signalling method 'ss7' at line 37. myserver*CLI> module load libss7.so Unable to load module libss7.so
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 Jan 14
2
Dahdi issues
Hello, My first attempt to get dahdi running on 1.4.28... with a Rhino 8 port modular card and a single FXS module. Got the Rhino card installed and the machine sees it: root at pbx:/etc/dahdi# dmesg | grep rcbfx [ 71.985309] rcbfx 0000:04:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 71.985440] rcbfx 1: Rhino PCI BAR0 50100000 IOMem mapped at ffffc90008d7c000 [ 71.985504]
2008 Mar 27
3
problem about voice when using TDM2400p with VPMADT032 echo canceller module
hi you, I'm having problem with voice quality on my trixbox using TDM2400B.The trixbox is connected via 20 FXO ports on a TDM2400 with the hardware echo cancel module. Echo cancel almost works, but the users hear what they describe as a 'background crackle/buzz' coming back when they talk. anyone have the same problem? pls help me. thanks a lot. my trixbox and config
2011 Mar 01
3
TLS/SRTP calls go to circuit busy.
I'm in the process of testing a TLS/SRTP install. My experience is improving with each new challenge, but this one is a great test of my 2 month experience with Asterisk. When I dial 6003 from 6001, it takes 35 seconds until I get the error message that 6003 is circuit-busy. Any help would greatly be appreciated. Below is the error message and the extensions and sip.conf files. *CLI>
2009 Feb 28
2
clone X100p+dahdi dial out works only after receiving call
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
2010 Jan 18
0
TDM2400P "Unable to set SW Companding on channel .."
Hi: I?Bought TDM2400P ,with 24 FXO ports , I installed? the asterisk 1.4.28 and?dahdi 2.2.0?and then i compiled them and configured all, i pluged into 8 pstn line into the Rj connector and then i got messages on asterisk console that alarm cleared on channels 1->8??, at this step everything should go fine ,but when i try to make a call?through the TDM?there is silence and no audio,and then i
2008 Nov 11
1
What makes TDM400 FXS Connection to TELCO go into Off Hook State?
I've been having trouble with making outbound calls to my TELCO from a TDM400 card (FXS KS signalling) after upgrading from 1.6-beta9 to 1.6.0. The problem is completely intermittent. When it fails, I get this message: [Nov 9 19:12:26] WARNING[18916] app_dial.c: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) At some point, it starts working, but I don't know what