similar to: Channels configuration with DAHDI

Asterisk - 1.8.4.1 Dahdi-linux - 2.4.1.2 Dahdi-tools - 2.4.1 Kernel: 2.6.37.6 Kernel BKL: enabled I am upgrading Asterisk on this box. It has an OpenVox A400P PCI analog card with 1 FXO and 1FXS module. This server has been running just fine for two years with Asterisk 1.6.1.0 I've just upgraded all the OS and installed Asterisk 1.8.4.1. On trying to configure the A400P I get: # modprobe

Hi there, we have a problem with dahdi and overlapdial. We are running an E1 in Germany and are in need of overlapdial. The E1 is connected to a Sangoma A101. As soon as overlapdial is set to "yes" we have problems with incoming audio on the dahdi channels. When set to "no" all audio is fine. Basically we can choose between being able to receive calls or to place calls

I am having problems getting a Nicherons TDM400P wildcard clone to dial out. Everything appears to be configured correctly, but although I see call progress, it never seems to actually pick up the phone. (The following is a test of 911 emergency, where I substitute 811 [repair service] as the actual number dialed.) *CLI> -- Executing [911 at from-internal: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:

----- Original Message ---- > From: Chris Lattner <clattner at apple.com> > To: Yuri <yuri at rawbw.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Sun, February 20, 2011 3:26:35 AM > Subject: Re: [LLVMdev] Announcing: LLVM 2.9 Tentative Release Schedule > > > On Feb 19, 2011, at 8:05 PM, Yuri wrote: > > > On 02/19/2011 14:52, Yuri wrote: > >>

Hello I was editing files manually, and noticed that if I include the familiar "fxsks=1" in /etc/dahdi/system.conf, Dahdi fails loading: ===================== # cat /etc/dahdi/system.conf loadzone = fr defaultzone = fr fxsks=1 ===================== # /etc/init.d/dahdi start Loading DAHDI hardware modules: wctdm: [ OK ] /usr/share/dahdi/waitfor_xpds: Missing

Hi, Im new to llvm and I'm using llvm-2.6 and I know how to extract the metadata in the stoppoints but what I'm interested in is the meta data regarding a local variable. I know that the @llvm.dgb.declare such as: call void @llvm.dbg.declare({ }* %2, { }* bitcast (%llvm.dbg.variable.type* @llvm.dbg.variable9 to { }*)) links to meta data for @llvm.dbg.variable9 which is:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, all! I'm being based on this document [1] to send and to receive calls using ekiga.net. But I'm seeing, in an Asterisk console, several messages of this type: [Feb 17 21:19:15] NOTICE[11875]: chan_sip.c:7715 sip_reg_timeout: -- Registration for 'danib2 at ekiga.net' timed out, trying again (Attempt #4775) -- Got SIP

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

Sorry for the noise. On 10/23/05, Mark Knecht <markknecht@gmail.com> wrote: > On 10/23/05, Mark Knecht <markknecht@gmail.com> wrote: > > Hi, > > Does anyone know what happened to the --debug option in winebuild? > > It seems to have disappeared in more recent versions of Wine. > > > > I am attempting to build a program that uses winebuild with

On Feb 24, 2011, at 4:05 AM, Jan Sjodin wrote: > On Feb 19, 2011, at 8:05 PM, Yuri wrote: >> >>> On 02/19/2011 14:52, Yuri wrote: >>>> Will MC path for JNI be included in 2.9? >>>> >>> >>> Sorry. I meant: Will MC path for JIT be included in 2.9? >> >> While it would be nice, it doesn't seem like anyone is working on

Hello everyone, I have a Atcom AX-1600P(1) card with a FXO module and I can't configure it. I have four extension with this PJSIP settings: --- /etc/asterisk/pjsip.conf --- [transport-udp] type=transport protocol=udp bind=0.0.0.0 [6001] type=endpoint transport=transport-udp context=from-internal disallow=all allow=ulaw auth=6001 aors=6001 direct_media=no rtp_symmetric=yes force_rport=yes

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

Hi I am in the process of installing a new box and using dahdi. I have a tdm410 + hardware echo canceller. I have just read in the read me for dadhi that VPMADT032 support has been removed and unlike with the zaptel stuff i could just download and install the firmware I can't with dahdi what is the best way forward to recompile with hardware echo canceller support. Thanks Alex

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

Hi all LLVMdev! Here is a question: I try to understand how I can realize a debugging in LLVM!? I have written a back end for my target and now I need a debug. I asked developers Chris Lattner and Robert L. Bocchino. They recommend me ask the LLVMdev. Is there a tool like "llvm-db" about Robert said? Here a mail from Robert: On Jun 29, 2009, at 17:14 PM, Robert L. Bocchino

Tengo en una maquia ubuntu 8.10 el kernel es Linux 2.6.27-14-generic Quiero configurar una tarjeta x100p i usarla con asterisk, asi que descague compile e instale lo siguiente: asterisk-1.4.24 dahdi-linux-2.1.0.4 dahdi-tools-2.1.0.2 libpri-1.4.9 Sin embargo no logro configurar la tarjeta con exito, ya probe casi? todo. Esto aparece si ejecuto lspci: 04:06.0 Communication controller: Motorola

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! I'm trying to doing a transfer from an analog extension to a SIP extension but until the moment I was not successful. I was testing both the recall key and uncomment the following lines in the features.conf file: blindxfer => #1 atxfer => *2 verifying previously that the extension uses the arguments "tT" with the Dial

Hi All, I have installed a number of Digium G100 devices in many countries like South Korea, Japan, Singapore and Australia. I have just installed two in New Zealand and both sites are having a problem with Caller ID. Incoming calls are dropping the first digit 0 from the caller ID. I was previously using DAHDI and a TE121 device which may have been adding the 0, I'm not too sure about

I have a TDM400. Just updated Fedora 12 to kernel 2.6.32. Rebuilt and installed dahdi-2.2.1. kernel modules loaded. lsmod | grep wctdm wctdm 37233 0 dahdi 194985 1 wctdm lsmod | grep dahdi dahdi 194985 1 wctdm crc_ccitt 1549 2 dahdi,isdnhdlc dmesg: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.2.1