similar to: DAHDI config file system.conf

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

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

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

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

# Span 1 span=1,1,0,esf,b8zs bchan=1-23 dchan=24 echocanceller=mg2,1-23 # Span 2 span=2,2,0,esf,b8zs bchan=25-47 dchan=48 echocanceller=mg2,25-47 # Span 3 span=3,3,0,esf,b8zs bchan=49-71 dchan=72 echocanceller=mg2,49-71 # Span 4 span=4,4,0,esf,b8zs bchan=73-95 dchan=96 echocanceller=mg2,73-95 # Global loadzone = us defaultzone = us Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1"

Hey Guys! Please help me to find out issue. I have two PRI ## Span 1: WPT1/0 "wanpipe1 card 0" span=1,1,0,esf,b8zs bchan=1-23 hardhdlc=24 echocanceller=mg2,1-23 ## Span 2: WPT1/1 "wanpipe2 card 1" span=2,2,0,esf,b8zs bchan=25-47 hardhdlc=48 echocanceller=mg2,25-47 Sometime my calls got through but some time i am getting pri cause 44 sebpbx1*CLI> == Using SIP RTP

Hi, I'm getting the following error from an asterisk 1.6.0.9 installation: [May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error: Asked to delete sched id -1??? [May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error: No more room in scheduler This repeats a few times, then asterisk crashes. I can't seem to locate any info on this error at all. I'm using

Hi, I have a client that has a 24 channel voice T1 that I have been using e&m signalling over for a number of years. The local telco finally got an ISDN switch and wants to move them to PRI. I didn't see this as a big problem - I've done a few others on this particular Caribbean island without issues, but this would be the first time with a Xorcom unit involved. We tried to do

Greetings folks- I'm experiencing issues with a freshly installed box. When a call comes in via PRI (Sangoma AFT-A104), I see this in my logs: [Dec 15 14:26:10] WARNING[23546] chan_dahdi.c: Unable to enable echo cancellation on channel 12 (Invalid argument) [Dec 15 14:26:10] WARNING[23546] chan_dahdi.c: Unable to enable echo cancellation on channel 8 (Invalid argument) [Dec 15 14:26:10]

Looking for someone with a successful experience similar to this; I have a need to cross connect a 3COM NBX PBX PRI interface to asterisk, but over a long distance. We do not need any IP connectivity and the solution requires G.711u audio so there is no benefit to using IP. Has anyone here successfully cross connected any PBX PRI interface expecting NI2 PRI signaling B8ZS/ESF with an

Hello all. I have an NEC PBX connected via a TE210p E1 line to an asterisk 1.6 box. NEC -> E1 -> TE210P:1 -> * -> TE210P:2 -> E1 -> Telco Incomming calls from the telco to the asterisk box to the NEC work fine with indials and everything. Works sweet. Outbound from the NEC to the Asterisk box fail. Giving an long dial tone that then times out. Ie, pick up NEC handset, dial

Following is my scenario to connect back to back PRI of two asterisk server. PRI cards are Sangoma A102D [Asterisk1]------------[PRI]-Cross Cable---------[Asterisk2] Asterisk1 ; Span 1 (MASTER) switchtype = national ; commonly referred to as NI2 context = from-pstn group = 0,24 echocancel = yes signalling = pri_net channel => 1-23 Asterisk2 ; Span 1 switchtype = national ; commonly

Hi, I running into the following problem on my Asterisk setup: --snip-- [Sep 3 01:40:59] NOTICE[9170] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 3 [Sep 3 01:47:07] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:07] ERROR[9170] chan_dahdi.c: Asked to delete sched id -1??? [Sep 3 01:47:07] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep

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)

The card you installed has FXO or FXS modules in it ????? are you getting your lines directly from the telco co??? Doug D On Mon 23/08/10 8:37 AM , Cassius Smith cassius at cassius.org sent: * -----Original Message----- * From: Todd Reese * Reply-to: Asterisk Users Mailing List - Non-Commercial Discussion * To: asterisk-users at lists.digium.com [3] * Subject: [asterisk-users] Dahdi

Hi All; To overcome the echo problem, what mainly I have to do in the configuration other than the following line in the system.conf under dahdi directory? echocanceller=mg2,1-16 1) How can I know if the digium card supporting echo cancellator? 2) If I am getting a message in the consol that unable to enable the echo cancelator, then what does it means? The hardware is not supporting echo

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:

Hello group, I am installing Asterisk on a new pc running Ubuntu 12.04.3 Server. ?I have dahdi-complete-2.7.0.1+2.7.0.1, and have tried 2.6.1 and 2.8.0-rc1 and 2.8.0-rc2. ?I am following along in the ASTERISK The Definitive Guide 4th Edition and on page 116 when I issue the command $ sudo /etc/init.d/dahdi start I get the following error: Loading DAHDI hardware modules: ? ?wctdm24xxp: done

I've been working with a telco for the past two days trying to get a PRI span up and running. This is a small-ish telco and I get the feeling they don't do this very often. Anyway, they specified a pretty standard setup: ni2 switchtype, esf framing, b8zs coding, etc. All of my b-channels are up, but we're having a heck of a time getting the d-channel to come up. He finds out that