[asterisk-bugs] [JIRA] (ASTERISK-24825) Caller ID not recognized using Centrex/Distinctive dialing
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Mon Mar 23 12:15:45 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-24825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan updated ASTERISK-24825:
-----------------------------------
Target Release Version/s: 13.3.0
> Caller ID not recognized using Centrex/Distinctive dialing
> ----------------------------------------------------------
>
> Key: ASTERISK-24825
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24825
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_dahdi
> Affects Versions: 11.16.0
> Reporter: Richard Mudgett
> Assignee: Richard Mudgett
> Target Release: 11.17.0, 13.3.0
>
> Attachments: jira_asterisk_24825_v11.10.2.patch, post-rx.wav, pre-rx.wav
>
>
> Asterisk is not displaying Caller ID on incoming calls.
> Attached is a couple recordings with dahdi_monitor that show the FSK spill between the first and second rings.
> * The incoming call has the ring-ring pattern followed by a Caller-ID spill.
> * The recordings appear to have a polarity reversal before and after the Caller-ID spill.
> Looking at the code, an unexpected polarity reversal can cause the Caller-ID monitoring to be aborted early as that event is not filtered out when recording event times.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list