similar to: dahdi "strange state" error

I've got a Digium Wildcard TDM410P with one POTS line and three extensions. One of the extensions is connected to a fax modem. This kind of works, but there's a gotcha. If I set faxdetect=incoming in chan_dahdi.conf, then incoming faxes do get routed to the modem and this all works, but outbound faxes fail, with a message like this: [Oct 29 21:57:09] WARNING[16732][C-00000000] app_dial.c:

The TDM410P doesn't support 'hvac', only the obsolete TDM400P supports that option was for the old phones that have a neon light (or equivalent LED+ZENER ciruit). Are other phones off the TDM410P (other than the VTECH) working, or is the Vtech the only model with VMWI available to you. I'm not able to check at the moment, I have copied the asterisk-users list, someone else may

Hi, I have the following setup: Ubuntu 12.04.02 LTS (64 bit) Asterisk 11.2.1 Sangoma 4-Port-Card (A104d) with firmware 43 (german e1-ports connected) WANPIPE Release: 3.5.28 DAHDI Version: 2.6.1 Echo Canceller: HWEC libpri version: 1.4.12 I call via sip into the dialplan. Then I do a "Dial(DAHDI/g1/voicenumber,r)". The call is bridged and everything is fine. "dahdi show

In Asterisk 1.8, I used the following line in extensions.conf to allow me to pass "*82" in front of a dialed number, to disable the callerid block that's normally on that POTS line: ; disable callerid block exten => _*82.,1,Dial(${POTS}/${EXTEN}) But this seems to have stopped working when I upgraded to Asterisk 11.7. I get the following debug output, with a "no

Hello, I have just installed an Asterisk server with a Digium TDM410P card with 3 FXO modules (no module in the 4th slot). It's lived on two different machines (a test machine, which had Linux kernel 2.6.28, and a new dedicated machine which has Linux kernel 2.6.32). On the test machine (2.6.28), I used the Zaptel drivers. Once the kernel modules were loaded, the lights on the TDM410P came

Greetings, This may be a dumb question, but here goes. When I was on 1.4.21.2 using Zaptel, I had (at least as far as I could tell) access to line supervision on my POTS lines using a TDM400P/TDM410P. Since upgrading to the DAHDI branches of 1.4 (SVN and 1.4.26.1), I've only been able to duplicate the success of the 1.4.21 functionality once. To test what I'm talking

Hi, I've been very puzzled lately. I installed a phone system for a friend a few weeks ago, and they're having a problem that I can't get rid of, actually 2 problems. Before I go into the problems, let me tell you about the setup. It's a pretty small setup with only 4 handsets, all Polycom 320s, the server is a Dell SC440 with Intel E2180 CPU (dual core, 2GHz) and 512MB Ram.

In order solve my incoming caller ID problem, I upgrade the dahdi to version 2.6.1 from version 2.4.x. After upgrade, I found the echo cancellation doesn't working (I'm using Digium AEX800B PCI Express card). I can hear my self talking on the phone. How to solve this? I think I need to recompile dahdi 2.6.1 with OSLEC support? how? [root at callcenter ~]# dahdi_cfg -vvv DAHDI Tools

Something new to me. Recently installed a 1.4.30 box for a small office with four POTS lines in a hunt (Digium TDM410P). Had the telco put a "call forward" option on the main line of the hunt. They dial a feature code from their desk phones (Polycom IP450) that results in forwarding the main number to our VoIP service. This is all to let them "try out" our dialtone

Hi All, I have just latest branch of asterisk 1.8 and i didn't found dahdi command in CLI everything seem fine. am i missing something ? campbx2*CLI> dahdi <tab tab> No such command 'dahdi' (type 'core show help dahdi' for other possible commands) campbx2*CLI> root at campbx1:/etc/wanpipe# wanrouter hwprobe ------------------------------- | Wanpipe Hardware

Hi, Continuing with the saga of Digium vs MTNL Mumbai, looking for suggestions on handling incoming Caller-ID issues. The card manages to grab a couple of (random) digits of the incoming CID, but they're more or less useless. Is there any way to fix this? Asterisk 1.8.13, Dahdi 2.5.0.1 on Debian Testing (Wheezy), MTNL Mumbai. Digium, Inc. Wildcard AEX410 4-port analog card (PCI-Express)

Upgrading an ancient customer installation... was running 1.4.23.1 (Trixbox) with Zaptel 1.4.12.9 and a Sangoma A102D, which has been running fine for 5+ years. Customer getting anxious about hardware failure, so we built a new box and installed 1.8.24.0, Dahdi 2.7.0.1, and a new Sangoma A104D. The single active span is an RBS T1 B8ZS/ESF/E&M Wink. I tried to move one span over one

Is there any known reason that the DISA() routine should behave differently than WaitExten() as far as recognizing DTMF tones? If not, I suspect there's a bug here. Try it yourself--two DID's on our PRI, numbers below let you test each routine: It is my observation that some setups/phones DO and some DO NOT express this variance. --I could not show any variance on a sprint mobile phone

Hi gang, We are moving our computers from a cluster of physical machines to a VMWARE server with virtual machines. We investigated and are looking to replace our TDM400P/TDM410P with AEX410P cards. Can we run asterisk with the DAHDI drivers from one of the Virtual machines or is DAHDI going to have to be a native process on the "REAL" machine? Thanks Danny Nicholas

Hi all, I was using dahdi 1.6.2.0.9 version for a long time. We decided to upgrade to 1.6.2.22 a few days ago. After that we started to have some problems with dahdi channels. PS:DAHDI Version: 2.6.0 Echo Canceller: HWEC, MG2 We have 2 PRIs between Ericsson pbx and asterisk and a sip trunk for outside calls. At begining everything works fine but in a few hours, calls from asterisk to ericsson

Greeting list, I hope this isn't a "lazy" question. I have been running TDM400P and TDM410P cards in Dell PowerEdge Servers for a few years now. We are moving from physical servers to VMWARE servers. What opportunities should I expect moving these cards into the new machines? Or should I leave the existing machines intact and use IAX to get to the DAHDI lines

Hi Listers, I'm running 1.4.25-rc1 on opensuse 11.0 with dahdi-linux-2.1.0.3, dahdi-tools-2.1.0.2, libpri-1.4.7 and snapdsp.0.0.2. Incoming calls work fine. Outgoing calls made directly (exten => s,1,Dial(DAHDI/G1) then number work fine. The problem I have is trying to let Asterisk make the call (exten => s,1,Dial(DAHDI/G1/5551212,,r). If I use "m" (moh) the

Good day , I have configured TDM410P (asterisk 1.6.x) on Cent OS 5, but dahdi take some time to hangup the call when playing the IVR..(it will send the hangup signal after finishing the IVR promt..) is there any specific setting to avoid such incidents ? iam using busycount as 3, signalling=fxs_ks ;toneduration=100 callwaiting=yes threewaycalling=yes callreturn=yes

Hi, Trying to configure my tdm410p card, my dahdi in asterisk cli was missing. ! ael agent agi cdr channel cli config console core database devstate dialplan dnsmgr dundi features file group hangup help http iax2 indication keys

Hi, I know it sounds weird, and this is part of the reason I have not reported that sooner. As I upgraded from 1.6.2.x to 1.8.x several months ago I am experiencing this problem. If a call is initiated from a DAHDI extension after no DAHDI extensions were used for some time, arbitrary DTMF digits are skipped and the call fails. If the call is redialed it goes through. Normally just one (1)