[asterisk-bugs] [Asterisk 0019006]: Caller ID on TDM410P *UK* PSTN

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19006 
====================================================================== 
Reported By:                danfloun
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19006
Category:                   Channels/chan_dahdi
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.17.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-03-21 14:18 CDT
Last Modified:              2011-03-22 02:04 CDT
====================================================================== 
Summary:                    Caller ID on TDM410P *UK* PSTN
Description: 
On an incoming call, Asterisk answers the channel before waiting for the
caller id retrieve to complete.
This bug occurred on ZAP also and is referenced in more detail on the
following links. Patches were created to work around the bug but never
officially implemented.

Ref: http://forums.digium.com/viewtopic.php?t=8477
Ref:
http://fonality.com/trixbox/forums/trixbox-forums/help/uk-caller-id-issues-dahdi


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

---------------------------------------------------------------------- 
 (0133062) iasgoscouk (reporter) - 2011-03-22 02:04
 https://issues.asterisk.org/view.php?id=19006#c133062 
---------------------------------------------------------------------- 
@donfloun
There is a couple of differences in the  chan_dahdi.conf, but wasn't until
this morning did I rememeber the issues I had when moved to dahdi 2.4

My server is built with Fedora (14 currently), and had issues with
modprobe with moved to 2.4 from an earlier version.

Can you check for the server startup for modprobe, i.e. /etc/modprobe.d/ 
and make sure that there is only files ending in '.conf' - earlier versions
of dahdi didn't end with .conf, and left both versions is place.  I removed
the files not containing the '.conf'; I found that if there was a dahdi and
a dahdi.conf, it caused bridging problems and hence callerid issues with
incoming calls.

Also, I have the following options set in /etc/modprobe.d/dahdi.conf: 

# You should place any module parameters for your DAHDI modules here
# Example:
#
# options wctdm24xxp latency=6 
options wctdm24xxp opermode=UK fwringdetect=1



Also, i would confirm whether asterisk actually sees the callerid; try
putting a NoOP on the callerid in your dialplan and check the console
output to see that asterisk is definately not seeing callerid, or whether
it's not getting from asterisk to you phone/extension.  I have a DECT
cordless multi-set running of a Handytone ATA box;  I had another analog
converter which failed/didn't support callerid

Hope this might help, so far.

Ian 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-22 02:04 iasgoscouk     Note Added: 0133062                          
======================================================================