I know this has been asked several times before and answered too, but cant seem to figure it out.
We have 1 number 020XXXXXXX with 3 physical lines for same number plugged into the PBX. We are having problems detecting the hangup on this line. Following is config. Can someone please help.
; Auto-generated by /usr/sbin/hardware_detector
[trunkgroups]
[channels]
cidsignalling=v23
cidstart=polarity
callprogress=yes
context=from-pstn
signalling=fxo_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hanguponpolarityswitch=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
hanguponpolarityswitch=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
echotraining=800
rxgain=0.0
txgain=0.0
callgroup=1
pickupgroup=1
relaxdtmf=yes
;Uncomment these lines if you have problems with the disconection of your analog lines
busydetect=yes
busycount=3
busypattern=400/375,0/375
immediate=no
#include dahdi-channels.conf
#include chan_dahdi_additional.conf
That is the busy tone not generally the same as the BT “Howler tone”
so disconnect supervision needs to match what the provider sends polarityswitch or regular CPC
if neither then busydetect will just notice repetitive tones on the line, I would stick a butt set on the line and try and diagnose if the telco doesn’t provide disconnect supervision and make your best guess
And how do they signal the disconnect? if polarity switch a red/green led with a 10 k resistor in series across the line will change color briefly, if CPC it will blink off on disconnect, a 300 dollar line analyzer also works
No help really available barring another user here who uses the same telco, my 10 cent solution would discover , no blinks or flashes, then they are lying , but I would escalate your question to your provider to some-one who does. That response is patently absurd.
Ok I have put a ticket to set the disconnect clear time to be set to 800ms as I have read on multiple places that people had same problem and setting the DCT to 800ms resolved the issue.