[asterisk-bugs] [Asterisk 0019006]: Caller ID on TDM410P *UK* PSTN
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Mar 22 20:05:45 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 20:05 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
======================================================================
----------------------------------------------------------------------
(0133084) danfloun (reporter) - 2011-03-22 20:05
https://issues.asterisk.org/view.php?id=19006#c133084
----------------------------------------------------------------------
Ian,
It's now 12.55am and I'm knackered. But, the good news I've have caller id
working.
Not sure how reliably yet, but it appears to be passing some mobile phone
ids happily.
Will check it further tomorrow.
Unfortunately I can't tell you what the fix was.
I did a clean install of 1.8 today with dahdi 2.4 and used the confs in my
initial report.
Using those confs, everything just worked.
I also noticed that the option 'immediately=yes/no' had no affect on my
system at all, so I have set it to 'no' as that is what I think it should
be.
My output from /var/log/messages on an incoming call is now like this;
Mar 23 01:02:27 localhost kernel: wctdm24xxp 0000:00:0a.0: 11333131
Polarity reversed (-1 -> 1)
Mar 23 01:02:29 localhost kernel: wctdm24xxp 0000:00:0a.0: FW RING on
1/1!
Mar 23 01:02:29 localhost kernel: wctdm24xxp 0000:00:0a.0: FW NO RING on
1/1!
Mar 23 01:02:29 localhost kernel: wctdm24xxp 0000:00:0a.0: FW RING on
1/1!
It starts with polarity reversal as it should.
It's a shame I can't give an answer as to why, but that's life.
Thanks for taking time to help me out on this issue, maybe now I can start
setting the system up properly.
Cheers
Danny
Issue History
Date Modified Username Field Change
======================================================================
2011-03-22 20:05 danfloun Note Added: 0133084
======================================================================
More information about the asterisk-bugs
mailing list