[asterisk-bugs] [DAHDI-linux 0009096]: [patch] DTMF CID without polarity reversal implementation in wctdm for Denmark, Brazil, etc

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=9096 
====================================================================== 
Reported By:                fleed
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   9096
Category:                   NewFeature
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Target Version:             2.2.0
====================================================================== 
Date Submitted:             2007-02-18 19:02 CST
Last Modified:              2009-08-31 19:25 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          0012658 [patch] DTMF issues on Zap
related to          0009201 Problem with caller ID detection when D...
====================================================================== 

---------------------------------------------------------------------- 
 (0109879) maturs (reporter) - 2009-08-31 19:25
 https://issues.asterisk.org/view.php?id=9096#c109879 
---------------------------------------------------------------------- 
after i applied the patch, i'm getting this:
  == Starting DTMF CID detection on channel 1
    -- Starting simple switch on 'DAHDI/1-1'
[Aug 31 18:20:08] WARNING[6813]: sig_analog.c:2054 __analog_ss_thread:
DTMFCID timed out waiting for ring. Exiting simple switch
    -- Hanging up on 'DAHDI/1-1'
    -- Hungup 'DAHDI/1-1'
  == Starting DTMF CID detection on channel 1
    -- Starting simple switch on 'DAHDI/1-1'
[Aug 31 18:20:11] WARNING[6814]: sig_analog.c:2054 __analog_ss_thread:
DTMFCID timed out waiting for ring. Exiting simple switch
    -- Hanging up on 'DAHDI/1-1'
    -- Hungup 'DAHDI/1-1'
  == Starting DTMF CID detection on channel 1
    -- Starting simple switch on 'DAHDI/1-1'
    -- Executing [s at from-zaptel:1] Wait("DAHDI/1-1", "2") in new stack
    -- Executing [s at from-zaptel:2] Answer("DAHDI/1-1", "") in new stack   

    -- Executing [s at from-zaptel:3] Verbose("DAHDI/1-1", "Incoming call
from BT line  CallerID=") in new stack
Incoming call from BT line  CallerID=


What can i do to make this work?? ==>  DTMFCID timed out waiting for ring

i'm not getting CID yet. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-31 19:25 maturs         Note Added: 0109879                          
======================================================================