similar to: callprogress issue

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)

My outgoing FXO calls are answered but have no audio in either direction if I have callprogress=no in chan_dahdi.conf. If I change to callprogress=yes then the audio returns. My chan_dahdi.conf file is listed below. Can anyone point-out why callprogress=no isn't working? #cat /tmp/a [trunkgroups] [channels] language=en context=incoming toneduration=40 ;usedistinctiveringdetection=yes

Hi, I am using asterisk 1.4.28 with freepbx and Wildcard TDM410P card. Everything is working fine except the caller ID of incoming call from PSTN line. The phone display is showing "Unknown" when there is an incoming call. *My log file showing this while an incoming call on PSTN line:* tail -f /var/log/asterisk/full [Dec 30 06:36:16] DEBUG[2559] dsp.c: dsp busy pattern set to 0,0

Hi, I am using asterisknow 1.5.0 and Wildcard TDM410P card. Everything is working fine except the caller ID of incoming call from PSTN line. The phone display is showing "Unknown" when there is an incoming call. I think the same problem listed here: https://issues.asterisk.org/view.php?id=6683 There is one patch on this link but i don't know how to apply patch on asterisknow.

Hello, My first attempt to get dahdi running on 1.4.28... with a Rhino 8 port modular card and a single FXS module. Got the Rhino card installed and the machine sees it: root at pbx:/etc/dahdi# dmesg | grep rcbfx [ 71.985309] rcbfx 0000:04:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 71.985440] rcbfx 1: Rhino PCI BAR0 50100000 IOMem mapped at ffffc90008d7c000 [ 71.985504]

Hi All This may be a silly question but... I have this dahdi_genconf generated file: ; Autogenerated by /usr/sbin/dahdi_genconf on Fri Jul 4 22:05:29 2014 ; If you edit this file and execute /usr/sbin/dahdi_genconf again, ; your manual changes will be LOST. ; Dahdi Channels Configurations (chan_dahdi.conf) ; ; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended ; to

Location = US asterisk/zaptel from CVS. Updated last week some time. Currently rebuilding with todays checkout. I have 2 fxo channels hooked up to outside standard Bell South phone lines. If I configure as so [channels] context=pstn group = 1 signalling = fxs_ks callprogress = yes channel => 4,3 Then any call routed from asterisk to the outside line will ring, and can be picked up, but *

Hi , Thanks danny nicholas. Finally we get the things done with following. If i specify busypatten=500,500 then asterisk does not recognize hang up signal. After removing it only all are working fine. I choosed 2nd option as per your suggestions. working chan-dahdi.conf: ==================== signalling = fxs_ks busycount = 3 busydetect = yes callprogress = yes progzone=in usecallerid=yes

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

Here is some more stuff to add to the confusion about the "callprogress" option. I currently have my * system operating with a T100P talking to an ADTRAN TSU600 channel bank with 8 FXO ports connecting to the outside world and Grandstream SIP phones as handset extensions. At first I naively set "callprogress=yes" in zapata.conf. The results were typical of what many

Thanks I had this line in my /etc/asterisk/chan_dahdi.conf : include=/etc/asterisk/dahdi-channels.conf the file /etc/asterisk/dahdi-channels.conf was generated by /usr/sbin/dahdi_genconf I simply did that : cat /etc/asterisk/dahdi-channels.conf >> /etc/asterisk/chan_dahdi.conf It works now. May be the option "include" is not supported within the file chan_dahdi.conf

Hi, Would anyone happen to have experience with the callprogress option? What I'm trying to do is use a couple normal POTS lines in a queue setup where it will call the queue members to pass the call to them. Of course the problem I'm running into is that under normal conditions the lines register as answered immediately and the caller gets transferred to the ringing line which

Hi all... I have a problem with caller id on my asterisk server. here is my configuration : centos-5, asterisk 1.6.2.1, dahdi-linux-complete-2.2.1, libpri-1.4.10.2 ibm X-3200 series, xorcom astribank (16fxo, 8fxs), 16 line telco (hunting) everything fine until I try to feed my app with caller id. My extensions.conf : [incoming1] exten =>

Here's some freaky stuff coming from Areski CDR tool: 101. 2008-10-13 03:41:23 DAHDI/1... 0000000 "unknown" <0000000> BackGround silence/5 s ANSWERED 00:20 102. 2008-10-13 03:11:30 DAHDI/1... 0000000 "unknown" <0000000> BackGround silence/5 s ANSWERED 00:21 103. 2008-10-13 02:41:23 DAHDI/1... 0000000 "unknown" <0000000> BackGround

Hello, if have a problem since I switched to asterisk-1.6: When making an outgoing call through chan_dahdi, I cannot hear anymore early audio, the asterisk generated sound (as defined in indications.conf) is played. Thus, I cannot hear announcements by the operator, and when the line is busy, sometimes I can hear first the ringing indication by asterisk, and some moments later the busy. I

[18884732963 at from-fax-machine:... - your call is hitting the from-fax-machine context - yet your 'fax' exten is in the from-pstn-4 context. See the "[2011-03-17 13:40:29.6] NOTICE[8825] chan_dahdi.c: Fax detected, but no fax extension" line. When Asterisk detects an incoming fax tone - it tries to automagically route the call to the 'fax' extension in the SAME

When I call my Asterisk-server from my cell phone on one of the PSTN-numbers that terminate in a FXO-module on my TDM410P Digium card, and in the dialplan the end of a context is reached and Asterisk needs to execute the Hangup()-command, I notice the following : - Asterisk tells me that the conversation was hung up (the log files tell me the command was executed) - On my cell phone I hear

>From what I've been reading about the callprogress option, it seems like it will work properly only with a T1 or PRI in the US. Is that correct or are there still issues with call progress detection even if those qualifications are met? Thanks, Shaun Tierney

I've set up an outbound .call system for customer callbacks and the like. Calls are going out over analog lines and I'm trying to use the WaitForSilence routine to make sure the phone has stopped ringing before starting message playback. The problem is that if I set the first argument of WaitForSilence to anything other than 1, WaitForSilence never exits. Some general info on my setup:

hello all i have asterisk 1.8.22 and have problem with caller id. this is my scenario: PSTN --> FXO ---> FXS ---> phone(223) when i call from a 223 to another phone, every thing is ok and caller id (223) is shown in called phone. but when i call from another phone to 223, no caller id is shown and just zero is shown. if i set callerid=12345 in chan_dahdi.conf file, when another phone