similar to: 1.6.0.9: Now "Unable to create ... 'DAHDI'"

Hello List, Im just dipping my feet into the asterisk world, and im having major fxo problems Im running Asterisk (from svn) + libpri (from svn) + asterisk-addons (from svn) + asterisk gui (svn 1.4 branch) + zaptel (svn 1.4) on a Debian Etch box, with 1gb ram, running all of the services for my home server (web / db / music server etc), and i would like to run my PSTN line from Kingston Comms,

I've spent a week playing with Asterisk 1.6 and I love it. What a brilliant piece of software! Progress and learning have been reasonably good. I have external SIP provider calls coming in and have put together a little call platform and I'm stunned at the flexibility. There is one issue for me. I took me a while to click that ZAPTEL now equals Dahdi, but now I'm there I have an

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 ======================

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 ;

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)

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

Hi, On a (bogus) system equiped with a Digium HA8 and 8 BRI ports, I'm reading this: # asterisk -rx "dahdi show status" Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO HA8-0000 RED 109 0 0 CCS AMI YEL 0 db (CSU)/0-133 feet (DSX-1) HA8-0000 UNCONFI 109 0

Calling out on PSTN over a TDM400P seems to generate a Red Alarm - whatever that is. I have another extension on the PSTN, and I can dial out over that. zttool shows no alarms. asterisk*CLI> zap show status Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO Wildcard TDM400P REV I Board 1 OK 0 0 0 CAS Unk YEL 0 db

Hi Guys, An 8 channel Astribank is connected to Trixbox 2.8 and I ran freepbx-module-zapauto but I get the following when running these commands and can't make calls out: [Trixbox]# dahdi_genconf xpporder /usr/sbin/dahdi_genconf: warning - OLD DRIVER: missing '/sys/bus/xpds/devices/00:0:0/timing_priority'. Fall back to /proc pbx*CLI> dahdi show channels Chan Extension Context

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

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

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

Hi all.. I`m with a problem in some E1 cards. The value of Bipolar Viol is too big, and some times the link seems well, but isn`t work correctly, like as if the link is down. Normally, I use to stop asterisk, remove the modules from my card, use modprove to set up they again, and start asterisk, and it come to work, but in some times I have to reboot the server, and then the value of

Hi, On my system I've got : CLI> dahdi show status Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO B4XXP (PCI) Card 0 Span 1 OK 0 0 0 CCS AMI YEL 0 db (CSU)/0-133 feet (DSX-1) B4XXP (PCI) Card 0 Span 2 OK 0 0 0 CCS AMI YEL 0 db (CSU)/0-133 feet (DSX-1) B4XXP (PCI)

I am having a problem with a new PRI turn-up on dahdi 2.5.0 and asterisk 1.8.5 that I have not seen before. The PRI is setup as B8ZS, ESF and the span shows up and ok. This PRI is merely a crossover T1 going into an old DC0 class 5 switch. I am getting the following errors over and over again [Aug 16 10:26:10] NOTICE[8002]: chan_dahdi.c:3043 my_handle_dchan_exception: PRI got event: HDLC Bad FCS

I have a system setup with two T1 circuits, the customer complains of call quality issues. I've checked logs and don't see anything too strange, but when I run "dahdi show status" I see: Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO T2XXP (PCI) Card 0 Span 1 OK 0 0 19 ESF B8ZS YEL 0 db

Hello When ever i try to use Dial DAHDI / SIP i get the following warning and nothing happens and Asterisk moves to next instruction Even i know that channel is free no one else is using it [Dec 22 12:43:39] WARNING[11915]: app_dial.c:1547 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) == Everyone is busy/congested at this time (1:0/0/1) Previously every

Running * version 1.6.1.17. My meetme conferences automagically disconnect users approximately 5-15 seconds after the user is connected. This occurs regardless of whether music on hold is active or not. [Mar 23 11:34:36] -- Executing Macro("SIP/SDN_TMCKEE-000000e9", "confroom,1808") [Mar 23 11:34:36] -- Executing [s at macro-confroom:1]

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:

I have a 45 x 16 data frame consisting of dissimilarities among 10 colors, giving in each column the 45 = 10*9/2 pairwise judgments for one of 16 subjects. The rownames identify each pair of colors, e.g, "AC" = ("A","C"), and the pairs are ordered by columns in the lower triangle of each distance matrix. > helm.raw <-