[Asterisk-Users] Distinctive Ring Detection not working

[Gonzalo Servat]

Hi there.

I'm having a strange issue with the distinctive ring detection in
Asterisk (I have a FXO card).
It certainly seems to be enabled as I can see the Asterisk console
spitting out the cadences (same cadence every time: 0,0,0) but the
problem is that it is not waiting 2 seconds after "Starting switch on
Zap/1-1" like it used to, long enough to determine the cadences,
presumably the reason why it is always 0,0,0 as it hasn't had enough
time to detect the ring pattern.

My zapata.conf looks like the following:

[trunkgroups]
[channels]
language=es
context=incoming-landline
signalling=fxs_ks
usedistinctiveringdetection=yes
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
busydetect=yes
busycount=8
dring1=334,146,0
dring1context=secondnumber
channel => 1

I've looked through some of the chan_zap.c code to try and increase
the wait period, but after making a couple of attempts at fixing it
decided to leave it alone before I break something :-)

Another thing I've noticed is that if I *don't* add a dring pattern
for "0,0,0", when a call comes in, it tries to find the dring pattern
for 0,0,0, fails to do so, so it tries to go to context ",s,1" (notice
the missing context name as the first argument), fails to do so and it
supposedly hangs up the chan, then detects the ringing again (it's
still the same call, only in its 5th ring by now) and successfully
detects a pattern different to 0,0,0. This is the only way to have it
"somewhat" working, although it's pretty unreliable. It's coming up
with quite a few different patterns, still, I shouldn't have to do it
this way. A lot of people hang up after the 4th or 5th ring.

Does anyone have any ideas on this?

Any suggestions would be greatly appreciated.

Cheers,
Gonzalo