Analog trunks won't release

I have two loop start pots lines.

Until asterisk decides to hang up…the lines remain tied up for over a minute (sometimes longer).

Its really apparent when an incoming call is sent to IVR or voice mail.

A call that is answered by a “live” person will hang up if the person on the asterisk side hangs up first but not if the caller hangs up first. (asterisk waits for over a minute or until the user on the asterisk side hangs up. this was done as a test. We don’t normally stay on the line after a customer hangs up. :smile:

what does zapata.conf look like. what are you using for busy detection or call progress detection ?

This is the zapata.conf file. This is in Trixbox 2.0

;
; Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes

usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no

;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

;Include genzaptelconf configs
#include zapata-auto.conf

group=1

;Include AMP configs
#include zapata_additional.conf

go read voip-info.org/wiki-Asterisk+ … apata.conf

and look at the sections for busydetect, busycount and callprogress. they may not apply to you/your telco, but that’s where to start. it’s also worth checking with them to make sure you’re getting loopstart. kewlstart would be better if available, then you can use a polarity reversal to signal call end.