[asterisk-bugs] [Asterisk 0011679]: REGRESSION: broken callerid

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11679 
====================================================================== 
Reported By:                meneault
Assigned To:                dbailey
====================================================================== 
Project:                    Asterisk
Issue ID:                   11679
Category:                   Channels/chan_zap
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 78227 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-04-2008 12:09 CST
Last Modified:              01-13-2008 12:25 CST
====================================================================== 
Summary:                    REGRESSION: broken callerid
Description: 
I recently switched from a trunk 49XXX revision to a 80XXX and then to
91983 and callerid seems to be broken at least since revision 80XXX.

Callerid detection fails randomly (usually 1/4 calls) with:
in callerid_feed: Caller*ID failed checksum
====================================================================== 

---------------------------------------------------------------------- 
 meneault - 01-13-08 12:25  
---------------------------------------------------------------------- 
Here you have:
idna_rx : asterisk not running (only zaptel), CLID start at time 4,95s
approx.
Content: short-ring/CLID/ring

id_rx : asterisk running, CLID start at time 2,64s approx.
Content: short-ring/CLID/answer

I forgot to mention but here we use V23 modulation CLID start after first
short ring.

To recreate the situation use id_rx's CLID.
Try it various times, maybe starting decoding from different offsets as
would chan_zap do. Because it may work once, twice but maybe not the third
time. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-13-08 12:25  meneault       Note Added: 0076861                          
======================================================================