[Asterisk-Users] Re: Zap channel calling back after hangup (dueto
polarity CID detection)
Bartek Kania
mrbk at gnarf.org
Tue Mar 1 08:10:47 MST 2005
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 1 Mar 2005, Anders F Eriksson wrote:
> > > I'm running CVS-HEAD-02/28/05-23:18:39 at the moment, and
> > it still happens.
> > > I've seen the bugs in Mantis, but the answeronpolarity
> > doesn't seem to
> > > make any difference ...
> > Could you post a debug-log of when it happens?
> > (enable debug and verbose in logger.conf)
> This is the log:
Ok, it seems the zaptel-driver is a little sensitive in your case:
<snip>
> Mar 1 13:57:22 VERBOSE[15246]: == Starting post polarity CID detection on
> channel 4
> Mar 1 13:57:22 VERBOSE[15256]: -- Starting simple switch on 'Zap/4-1'
> Mar 1 13:57:22 DEBUG[15256]: Receiving DTMF cid on channel Zap/4-1
> Mar 1 13:57:23 DEBUG[15256]: Exception on 19, channel 4
> Mar 1 13:57:23 DEBUG[15256]: Got event Ring/Answered(2) on channel 4 (index
> 0)
> Mar 1 13:57:23 DEBUG[15256]: Setting IDLE polarity due to ring. Old
> polarity was 1
The problem is the "Got event Ring/Answered(2)" line.
Normally, a ring should not be detected and the DTMF-cid times out and
no incoming call is registered.
Make sure you load wctdm with the parameter 'opermode=SWEDEN', it might help.
You might also try to increase the 'RING_DEBOUNCE' define in wctdm.c.
If you load wctdm with debug=1 it prints some useful information to
the kernel log for tuning the RING_DEBOUCE.
/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)
iD8DBQFCJIX7WYjaxM2wIe4RAmh+AJ9IUZ81zd2vztjGnOXmtoSpQvN/sQCghu5/
/zBjljG1pe0pm+/zIhfTnVY=
=A7M1
-----END PGP SIGNATURE-----
More information about the asterisk-users
mailing list