[asterisk-bugs] [Asterisk 0019006]: Caller ID on TDM410P *UK* PSTN
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Mar 22 06:57:53 CDT 2011
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 06:57 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
======================================================================
----------------------------------------------------------------------
(0133064) danfloun (reporter) - 2011-03-22 06:57
https://issues.asterisk.org/view.php?id=19006#c133064
----------------------------------------------------------------------
Hi,
I don't think you received my email. It could be my mail server, thats
been playing up also.
To address your queries in order;
--
It was a clean install I was running with no patches but updated fully for
1.6.2.17.2.
Because of this Dahdi 2.4 was the only version I ever had on my system,
therefore only the following files are in /etc/modprobe.d/ directory;
-rw-r--r-- 1 root root 810 Apr 10 2010 blacklist
-rw-r--r-- 1 root root 833 Oct 11 12:31 blacklist-compat
-rw-r--r-- 1 root root 83 Jan 6 02:18 blacklist-firewire
-rw-r--r-- 1 root root 329 Nov 23 21:49 dahdi.blacklist.conf
-rw-r--r-- 1 root root 149 Mar 19 23:48 dahdi.conf
-rw-r--r-- 1 root root 6111 Oct 11 12:31 modprobe.conf.dist
--
Unfortunately I had set this already in my dahdi.conf;
options wctdm24xxp opermode=UK fwringdetect=1 battthresh=4 debug=1
--
I tried NoOp for CALLERID(num) on my dialplan and it's empty on every
call.
== Starting post polarity CID detection on channel 1
-- Starting simple switch on 'DAHDI/1-1'
[Mar 22 11:47:45] NOTICE[3846]: chan_dahdi.c:1777 my_distinctive_ring: Got
event 18 (Ring Begin)...
-- Detected ring pattern: 0,0,0
-- Checking 0,0,0
-- Ring pattern check range: 10
-- Ring pattern matched in range: -10 to 10
-- Ring pattern check range: 10
-- Ring pattern matched in range: -10 to 10
-- Ring pattern check range: 10
-- Ring pattern matched in range: -10 to 10
-- Distinctive Ring matched context avo-pstn-inbound
-- Executing [s at avo-pstn-inbound:1] NoOp("DAHDI/1-1", "Caller ID is:")
in new stack
-- Executing [s at avo-pstn-inbound:2] Dial("DAHDI/1-1", "DAHDI/4") in
new stack
-- Called 4
-- DAHDI/4-1 is ringing
-- DAHDI/4-1 is ringing
-- DAHDI/4-1 is ringing
-- DAHDI/4-1 is ringing
-- DAHDI/4-1 is ringing
I tried setting the NoOp in various places of the dialplan i.e. before
answer, after answer, etc. Not sure whether it makes any difference but I
still got an empty callerid.
--
This morning I upgraded to 1.8.3.2 - Still the same.
I am at a loss.
Issue History
Date Modified Username Field Change
======================================================================
2011-03-22 06:57 danfloun Note Added: 0133064
======================================================================
More information about the asterisk-bugs
mailing list