[Asterisk-bugs] [Zaptel 0009096]: [patch] DTMF CID without polarity reversal implementation in wctdm for Denmark, Brazil, etc
noreply at bugs.digium.com
noreply at bugs.digium.com
Fri Jul 13 17:04:03 CDT 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=9096
======================================================================
Reported By: fleed
Assigned To:
======================================================================
Project: Zaptel
Issue ID: 9096
Category: wctdm
Reproducibility: always
Severity: minor
Priority: normal
Status: ready for testing
Asterisk Version: 1.4.7.1
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: Yes
Request Review:
======================================================================
Date Submitted: 02-18-2007 19:02 CST
Last Modified: 07-13-2007 17:04 CDT
======================================================================
Summary: [patch] DTMF CID without polarity reversal
implementation in wctdm for Denmark, Brazil, etc
Description:
Caller id signaling in Denmark, Brazil and other places is done through
DTMF tones before the first ring, without polarity reversal to indicate the
start of incoming data. Currently wctdm can only detect dtmf callerid if
there is a polarity reversal before the dtmf digits, so it's not working in
some countries.
This uses the idea reported in bug id 9 for wcfxo, but implements it in
wctdm. It fakes a polarity reversal so that the code already in chan_zap
can take that and pass it through the dtmf bit.
To use, patch and build the zaptel part, load the module with option
dtmf=1. Then use the following in zapata.conf:
callerid=asreceived
usecallerid=yes
cidsignalling=dtmf
hidecallerid=no
cidstart=polarity
Works fine in Brazil, on a Telemar line.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0000009 [patch] DTMF CLIP not supported by Aste...
related to 0009201 Problem with caller ID detection when D...
======================================================================
----------------------------------------------------------------------
hamid - 07-13-07 17:04
----------------------------------------------------------------------
I did test the patch and it didn't work for me. I am in Iran and our clid
is DTMF based and based on my tests with a Panasonic handset it got the
clid before the first ring. I asked for the PSTN switch vendor and it is
EWSD ( Siemens ) switch.
I did test the normal wctdm with asterisk and there was no CLIP and after
I patched the wctdm.c with this patch and used csiebel method for debug I
got this in messages but I didn't have clid on my phone :
Jul 14 01:20:36 home kernel:
Jul 14 01:20:36 home kernel:
Jul 14 01:20:36 home kernel: readchunk = 141 reg0shadow = 203 |
reg1shadow = 232 ios= 20 dead = 0 pos = 0 polarity = -1 polaritydebounce =
0 cidtimer = 215908
Jul 14 01:20:36 home kernel:
Jul 14 01:20:36 home kernel: DTMF CLIP on 2
Jul 14 01:20:36 home kernel: RING on 1/2!
Jul 14 01:20:37 home kernel: NO RING on 1/2!
Jul 14 01:20:41 home kernel:
Jul 14 01:20:41 home kernel:
Jul 14 01:20:41 home kernel: readchunk = 130 reg0shadow = 203 |
reg1shadow = 0 ios= 20 dead = 0 pos = 0 polarity = -1 polaritydebounce = 0
cidtimer = 220698
Jul 14 01:20:41 home kernel:
Jul 14 01:20:41 home kernel: DTMF CLIP on 2
Jul 14 01:20:41 home kernel: RING on 1/2!
Jul 14 01:20:42 home kernel: NO RING on 1/2!
any suggestion ?
Issue History
Date Modified Username Field Change
======================================================================
07-13-07 17:04 hamid Note Added: 0067372
======================================================================
More information about the asterisk-bugs
mailing list