[asterisk-bugs] [Asterisk 0006683]: [patch] Fix for CallerID on Indian PSTN

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=6683 
====================================================================== 
Reported By:                abhi
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   6683
Category:                   Channels/chan_zap
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     closed
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 45596 
Disclaimer on File?:        Yes 
Request Review:              
Resolution:                 reopened
Fixed in Version:           
====================================================================== 
Date Submitted:             03-08-2006 16:50 CST
Last Modified:              02-25-2008 14:49 CST
====================================================================== 
Summary:                    [patch] Fix for CallerID on Indian PSTN
Description: 
The default asterisk does not detect the caller id in India. Its a DTMF
based system here, where the caller id is sent after the first ring (this
as per tests on the second biggest provider Bharti, still go to test with
VSNL, will update about the same).

Using certain minor changes, could get it working in both the modes.
(polarity and ring), though the polarity mode is more of a hack (since we
initialize the state of the channel with AST_STATE_PRERING rather than
AST_STATE_RING and get the digits). Basically we needed to do dtmf
detection which is done only in PRERING state, so either we could
initialize the state with PRERING (wrong way), or do the detection in RING
state (aftert the first ring) as well.

   For the polarity mode, chan_zap.c diff is  diff.chan_zap.c.polarity.

   For the start of caller id on ring, the present chan_zap.c code detects
the caller id only in bell202 mode. After adding the part to do dtmf
detection, this work, though had to make a hack there to make it stop CID
detection when we receive ZT_EVENT_RINGBEGIN (also this event is not
handled in zt_handle_event). attached diff.chan_zap.c.ring is for the same.

====================================================================== 

---------------------------------------------------------------------- 
 murf - 02-25-08 14:49  
---------------------------------------------------------------------- 
OK, this bug is so old, it appears in the top ten "old, unsolved bugs"
list. The original issue has been solved, and the patch applied to trunk
last June. It's in the 1.6 alpha. Any new similar issues that come up can
be presented in a new bug.
Getting Asterisk to be configurable for all the environments in India will
probably take a long time! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-25-08 14:49  murf           Note Added: 0082896                          
======================================================================