Problem when caller leave queue before somebody reply him!

General Help
1

hi ,
i have a very big problem ,
i have an ivr system===>if press 1 ======> queue number 30 =======> music on hold untill some one rpely the call

here is above my scenario which i have .

assume some one reached queue 30 and queued at waiting for a short ime on MOH then leaved before anyone reply him ,
i note that the dhahdi cahannel still active for long time , and the queue phone still ringing !!!11 :shock: :shock:

this is a big problem , ===> the caller leaved and close the call but in my fop2 it seems that the caller still calling and the phones inside the queue still ringing !!! :o :o :o :o :o

now asume after all of that , someone of the phones in queue replied this call which its caller has leaved long time ago ,
we hear this annoying sound >

another horrible issue :
at elatsix cdr report , it record the call as being recived call !!! not missed call !!! which really bad issue .

ive recorded this sound and uploaded it , and wish to help what is the cause of this problem
here is the sound file link :

here is the view from fop2 , it still active although the caller ended the call from his side >

========================
here uis my system config :

Kernel
Linux(i386)-2.6.18-238.12.1.el5

Elastix
elastix-2.2.0-14
elastix-firstboot-2.2.0-5
elastix-system-2.2.0-14
elastix-email_admin-2.2.0-9
elastix-vtigercrm-5.1.0-8
elastix-extras-2.0.4-4
elastix-asterisk-sounds-1.2.3-1
elastix-my_extension-2.2.0-5
elastix-agenda-2.2.0-5
elastix-a2billing-1.8.1-16
elastix-addons-2.2.0-4
elastix-im-2.0.4-2
elastix-pbx-2.2.0-14
elastix-security-2.2.0-7
elastix-reports-2.2.0-6
elastix-fax-2.2.0-4

RounCubeMail
RoundCubeMail-0.3.1-10

Mail
postfix-2.3.3-2.3.el5_6
cyrus-imapd-2.3.7-12.el5_7.1

IM
openfire-3.5.1-2

FreePBX
freePBX-2.8.1-7

Asterisk
asterisk-1.8.7.0-0
asterisk-perl-0.10-2
asterisk-addons-1.8.7.0-0

FAX
hylafax-4.3.10-2rhel5
iaxmodem-1.2.0-1.1

DRIVERS
dahdi-2.4.1.2-5
rhino-0.99.4-2.rc1
wanpipe-util-3.5.23-1

========================
with my best regards

2

Your analog phone line is not doing proper remote party disconnect or also known as supervised disconnect. Contact your carrier and make sure they get that setup.

3

As Tony says, if they can’t or won’t set up disconnect supervision rely on:-

busydetect=yes
busycount=8

in chan_dahdi.conf or zapata.conf or WETF elastix uses

(This question only asked and answered at least 10000 times, dr.x. Try the search field first next time maybe?)

4

hiii ,

i will post results from my two config files
======================================================================#####
[root@mimo ~]# vim /etc/wanpipe/wancfg_zaptel/templates/zapata.conf

;autogenerated by /usr/sbin/WANCFG_CONFIG do not hand edit
;autogenrated on DATE
;ZAPATA_STRING Channels Configurations
;For detailed ZAPATA_STRING options, view LOCATION.bak

[trunkgroups]

[channels]
context=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=0.0

[root@mimo ~]# vim /etc/asterisk/dahdi-channels.conf

; Autogenerated by /usr/sbin/dahdi_genconf on Thu May 3 11:33:01 2012
; 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 be #include-d by /etc/chan_dahdi.conf that will include the global settings
;

; Span 1: ATCOM-1600P/16 “ATCOM AX1600P/800P Board 17” (MASTER)
;;; line="1 ATCOM-1600P/16/0 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 1
callerid=
group=
context=default

;;; line="2 ATCOM-1600P/16/1 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 2
callerid=
group=
context=default

;;; line="3 ATCOM-1600P/16/2 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 3
callerid=
group=
context=default

;;; line="4 ATCOM-1600P/16/3 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 4
callerid=
group=
context=default

;;; line="5 ATCOM-1600P/16/4 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 5
callerid=
group=
context=default

;;; line="6 ATCOM-1600P/16/5 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 6
callerid=
; Autogenerated by /usr/sbin/dahdi_genconf on Thu May 4 11:33:01 2012
; 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 be #include-d by /etc/chan_dahdi.conf that will include the global settings
;

; Span 1: ATCOM-1600P/16 “ATCOM AX1600P/800P Board 17” (MASTER)
;;; line="1 ATCOM-1600P/16/0 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 1
callerid=
group=
context=default

;;; line="2 ATCOM-1600P/16/1 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0

========================================
do i need to modifiy somethign from show above ???

regards

5

[root@mimo ~]# cat /etc/asterisk/chan_dahdi.conf
[trunkgroups]

[channels]
context=from-pstn
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=both
echotraining=800
;rxgain=0.0
;txgain=0.0
rxgain=1.2
txgain=2.5
callgroup=1
pickupgroup=1

;Uncomment these lines if you have problems with the disconection of your analog lines
busydetect=yes
busycount=13

immediate=yes

#include dahdi-channels.conf
#include chan_dahdi_additional.conf

6

I have to tell you, this is a mixed Sangoma/Atcom environment. I am hesitant to give you any advise. Whoever set this up knew what they were doing.

7

why there is hesitation>>???/ is my config files is not clear ???/

regards

8

No because one mistake and you will break your system. The variable Tony instructed you to change are right in front of you (in the contents of chan_dahdi.conf that you send and you don’t even see them.

9

so wts the next step ???

10

Whatever you care to do. You have been given all the information (more than once), You however have not as yet identified which of your trunks are broken, now you have to choose, If the Atcom trunks are hanging, call ATcom if the Sangoma Trunks are hanging, similarly. someone is not honoring your busydetect but ultimately choose Elastix or FreePBX for your support, you just can’t have it both ways, they are NOT the same thing. . . . .

11

wt about changing gains tx , rx

or changing any variable to solve the issue .

i would like to say that i changed busydetect to 8 and i began facing echo !!!

any advice ?

12

I can assure you that your busydetect settings have absolutely nothing to do with your echo.

There are many posts “out there” on how to tune your 2/4 wire FXO’s (A couple by me even).

Basically you will use the milliwatt() app included with Asterisk and dahdi_monitor to balance the hybrid as you modify txgain and rxgain.

Both over modulation and under modulation are problematic, disparity between the two of more than a db or two and you WILL get echo.

p.s. I suspect that you suffer from an ADD like lack of concentration, so pre-emptively, I will let you know that I will not be posting step by step instructions for you personally :wink:

13

hi mr dicko ,
i really appreciate ur help cause i fianlly found a solution by using busydetect =6

note that using it 8 will cause a hard echo

anyway , thanks very much ,

and im very sorry if i caused any type of annoying to you or 2 any one .

i may asked alot of questions which may be unsuitable , but as you u im just a beginner and not all the keys of soultions i own it .

thanks agian dickO & for all in freepbx fourms .

with my best regards .

14

Busy disconnect has NO effect on echo cancellation. Believe me your problem lies elsewhere

I guess there will be no way to convince you of that though.

But good luck with your “bull in a china shop” thinking, Asterisk/FreePBX DOES work for everybody else, at least those who actually “read” the answers given.

15