similar to: Intermittent DAHDI issue with a PRI line causing asterisk to crash!

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

Hi. My configuration is Elastix 1.5.2-2 (asterisk 1.4.24, libpri-1.4.3-5, dahdi-2.1.0.4-7 ) and OpenVox d210e connected to telco provider (Euro ISDN). Here is my /etc/dahdi/system.conf: # Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) HDB3/CCS ClockSource span=1,1,0,ccs,hdb3 # termtype: te bchan=1-15,17-31 dchan=16 echocanceller=oslec,1-15,17-31 # Span 2: TE2/0/2 "T2XXP

Hello, I seem to be having an issue with the configuration of my PRI on a new asterisk server I've created to replace an old install that I have. The card is Digium Wildcard TE133. I continually get messages like "Primary D-Channel on span 1 down", rather irregularly: [2013-07-29 17:31:39] VERBOSE[3621] sig_pri.c: == Primary D-Channel on span 1 up [2013-07-29 17:31:39]

Hi, Starting in Asterisk 1.8.0, Asterisk supports connected line updates. This is fantastic for SIP. How can I prevent them from being sent to a PRI channel? I'm having problems when a call is answered by an internal SIP extension, then transferred (blind or attended) to another internal SIP extension. One of my PRI providers can't handle the ROSE_ETSI_EctInform APDU and drops the

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]

Hello, I am trying to diagnose an intermittent error when a call comes in over our PRI lines. The problem appears random, however I have feeling it has something to do with the call volume, as the frequency increases with more calls on the system. I am not an expert when it comes to reading the PRI Span Debug statements but here is a call that had a problem and I bolded, italicized, and

i belong to india. i am making pbx using sangoma fxo card. i want that when ever call comes to my PSTN line i should see the no from where call is coming. so i have to configures chan_dahdi.conf according to my region. i checked dahdi.conf and in that they have mentioned for india

When I restart or reboot I can not dial out. The dial() incorrectly sees dahdi/1 as busy. I call in once from a cell phone, which is successful then I can call out with out issue. Any ideas would be much appreciated. Sangoma B600de asterisk-1.6.0.9 dahdi-linux-2.1.0.4 linux-2.6.28-gentoo-r5 wanpipe-3.3.16 ###chan_dahdi.conf ;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit

Asterisk 1.8.4-rc2 (and 1.8.3) DAHDI Version: 2.4.1.2 libpri version: 1.4.12-beta3 We are having a problem with getting the nationalprefix option of chan_dahdi.conf to work. National calls do not have a "1" added to them when nationalprefix=1. The PRI debug shows the call coming in as a National Call, but the dialplan sees the call without a 1. chan_dahdi.conf: <snip>

We fairly recently switched service providers for our 4 PRI circuits. Since that time, we started to notice some failed inbound calls. These calls terminate with an ISDN cause code 47 'resource unavailble'. Most of the time I see this error on the first or second channel on the second span in a trunk group (This is the providers trunk group for hunting, not an Asterisk trunk group). All

[Dec 23 17:58:49] ERROR[3091]: chan_dahdi.c:8413 dahdi_pri_error: XXX Missing handling for mandatory IE 12 (cs0, Connected Number) XXX I am seeing the above error on DAHDI 2.1.0, asterisk 1.4.22 and libpri 1.4.7 I am using a TE120P card. I am also getting this VERY frequently: -- Channel 0/1, span 1 got hangup request, cause 16 -- Hungup 'DAHDI/0-1' Versus a normal hangup:

Hello List, it is a very long time since I wrote here.... It has been still in Zaptel times.... Today I am run into a related problem: I can't get a DAHDI setup to work 100%. I am configuring an Astribank XR00013 (BRI, two ISDN ports). At some degree the installation (latest DAHDI drivers, Asterisk 1.6.0.18 on Centos 5.x) works. I can get incoming calls to the dialplan context that is

Hello, I have an Asterisk system in the UK using ISDN service from BT. My problem is that the called number is always passed to the provider with the Type Of Number declared as ?national? despite pridialplan (and prilocaldialplan) is set to ?unknown?. My questions are: - How can I find out what the effective value is for the above two variables without actually making a call? (I have very

hello i had configured a Dial plan in which i am using application time base i.e 1 - if? call comes to PSTN line??? from 8pm? evening till morning 8am the call should? automatically forward to guard exten i.e exten 211, and if guard dosent receive call in 30 secs message should be saved in voicemail. 2 - if call comes in working hours than it should be received by ext 112 n from there using

Hello, I have the same problem, you said that was a configuration problem. I play with configuration but can not get it working. Can you please show you working configuration. Any help appreciated. -------------------------------------------original messages----------------------------------------------------------------------------------- Hi, it was some configuration error. I droped the

I have a PRI E1 link between Asterisk 1.4.24 and Alcatel-Lucent OmniPCX Enterprise R9.0. As EuroISDN it works fine. However, I need to move to QSIG because of a firmware upgrade on the Alcatel PBX which doesn't support EuroISDN (please don't ask why). Besides, I've read somewhere that 2 B Channel Transfers "should" work with * 1.4, the latest 1.4 libpri and QSIG. So this

Hello everyone, I am facing a strange problem on my asterisk box (using isdn lines with pri card installed on it). Normal incoming/outgoing calls are working perfectly fine. When a user dial a wrong/out-of-service number they don't hear back any such message like "The number is wrong or user is switched off" in some cases, and it's just a silence for the user. Now while

I just updated libpri 1.4 on my system to the latest from that branch and my QSIG connection to an NEC SV8300 stopped working. The trace showing the problem is below: q931.c:5640 q931_connect: Call 7168 enters state 10 (Active). Hold state: Idle > DL-DATA request > Protocol Discriminator: Q.931 (8) len=21 > TEI=0 Call Ref: len= 2 (reference 7168/0x1C00) (Sent to originator) >

I am trying to setup Asterisk to act like a PBX connected via a PRI gateway to a voice netowrk where Asterisk is doing outbound overlap dialing for calls that terminate via that PRI. AFter researching through the archives and online dcocs, I thought I had everyting setup right, dialplan configured for '_X!' and the 'overlapdial=yes' in the chan_dahdi.conf file, but when I try and

Some recent issues I had with hardware seem to come back to not understanding two very similarly named files: /etc/asterisk/dahdi-channels.conf /etc/asterisk/chan_dahdi.conf I've modified the chan_dahdi.conf to work now, but it would appear all I needed to do was include dahdi-channels.conf in chan_dahdi.conf and the problem would not have persisted? Is it me or is that a bit Monty Python?