Asterisk does not hang up DAHDI calls longer than 3 minutes

Asterisk Asterisk Support
1

We’ve recently upgraded to Asterisk 1.8.13 (Debian-patched), using DAHDI v2.6.1 and since upgrading Asterisk (and only Asterisk), we’ve run into an odd bit of behaviour.

I can call in with my cell phone through our DAHDI line, and if I hang up before 3 minutes have elapsed, the call terminates like it should. If I hang up my cell phone after 3 minutes have elapsed however, then the call remains active on the SIP phone. This is problematic, since that SIP phone remains busy if the user doesn’t hang it up on purpose, and any further calls cannot be routed to the SIP phone.

I haven’t observed this behaviour between SIP phones though, so my guess is that it’s purely a DAHDI issue. Is this a bug? Is it a configuration issue? Any help in troubleshooting this behaviour is welcome.

2

Bump!

3

check your dahdi settings, if is an anlog line check the signalling and the busydetect & busycount settings.

4

We use a PRI, and those settings haven’t changed since well before the upgrade. I don’t know why this behaviour would suddenly change after we upgraded from 1.8.6 to 1.8.13.1.

Here’s our DAHDI configuration anyway:

usecallerid=yes
cidsignalling=bell
; This one causes problems with Bell telephone numbers, or something.
cidstart=polarity
; The default is “ring”
; cidstart=ring

facilityenable=yes
hidecallerid=no
callwaitingcallerid=yes
callwaiting=no
threewaycalling=yes
transfer=yes
echocancel=yes
;echotraining=yes
echocancelwhenbridged=no
immediate=no
group=1
signalling=pri_cpe
switchtype=national
;context=incoming
; Added Mar 13, 2012
; Don’t use this. It breaks incoming faxes.
; relaxdtmf=yes
context=local
channel=>1-23
dchannel=>24
;channel=25-47,49-71,73-95
rxgain=0
txgain=0
busydetect=yes
busycount=5

resetinterval=1800

5

Bump!