asterisk users - Feb 2005 - Zap channel calling back after hangup (due to polarity CID detection)

Today I received a TDM11B (1 FXO and 1 FXS) and got it installed just fine.
I bought the card mainly to get caller ID to work properly in Sweden, and
that works just fine.

However, if the called or calling party hangs up after I hangup my SIP
channel, polarity CID detection kicks in and dials a couple of signals to my
incoming context. This happens with Asterisk 1.0.6 and CVS-HEAD. I have
tried various combinations of hanguponpolarityswitch and
answeronpolarityswitch (and without them).

I'm sure this has been solved several times, but I can't seem to find it
anywhere - any help appreciated :)

My zapata.conf at the moment looks as follows:

;*************************************************************************
; zapata.conf
;*************************************************************************
;
[channels]
;
; TDM11B plugged into PSTN
;
signalling=fxo_ks
busydetect=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=400
usecallerid=yes
callerid="Siemens" <450>
group=1
threewaycalling=yes
transfer=yes
context=norby  
channel => 1

signalling=fxs_ks
txgain=0.0
rxgain=15.0
usecallerid=yes
callerid=asreceived
cidsignalling=dtmf
cidstart=polarity
transfer=no
group=2
context=analog_in 
answeronpolarityswitch=no
hanguponpolarityswitch=yes
channel => 4

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 28 Feb 2005, Anders F Eriksson wrote:
> Today I received a TDM11B (1 FXO and 1 FXS) and got it installed just fine.
> I bought the card mainly to get caller ID to work properly in Sweden, and
> that works just fine.
> However, if the called or calling party hangs up after I hangup my SIP
> channel, polarity CID detection kicks in and dials a couple of signals to
my
> incoming context. This happens with Asterisk 1.0.6 and CVS-HEAD. I have
> tried various combinations of hanguponpolarityswitch and
> answeronpolarityswitch (and without them).
That issue is fixed in the CVS HEAD version of asterisk.
There are a couple of workarounds possible with 1.0.6. Check the bugtracker
for the bug where it was implemented for more information. (sorry, don't
remember the bug-number and don't have time to look it up right now).

You might also try the following patch:
http://evil.gnarf.org/creativity/asterisk/20050110-answeronpolarity.diff which
is what is in HEAD.
But I don't know if it will work against asterisk stable. If you know C it
should be no problem adapting it though.

/B
- -- 
* GPG-Key: http://evil.gnarf.org/mrbk.pgp

A: Because we read from top to bottom, left to right.
Q: Why should i start my reply below the quoted text?
- -- http://www.i-hate-computers.demon.co.uk/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCJDdgWYjaxM2wIe4RAln/AKDWh1FCK0n8yXrz0vxd/1bqpzgNkACfe6Ix
ewEGA8Idz6uUIOFIXRSTZnQ=OUHe
-----END PGP SIGNATURE-----