[asterisk-bugs] [JIRA] (ASTERISK-27135) CallerID not detected in India

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237718#comment-237718 ] 

Richard Mudgett edited comment on ASTERISK-27135 at 7/17/17 12:38 PM:
----------------------------------------------------------------------

The caller id is coming in between the first and second ring as a FSK spill like it is in the US.  The FSK spill is either cidsignaling=bell or v23 and the cidstart needs to be ring.  To get the caller id, the call must not be answered until the second ring.  However, the call is answered in the middle of the caller id spill so you don't get the caller id.  When the call is answered, I hear what appears to be a partial tt-monkeys file.

P.S.: I had initially loaded the raw capture file using the wrong parameters.  The bad load gave me some incorrect conclusions until I discovered that I loaded it incorrectly.

FYI: If you capture the file to a .wav filename then dahdi_monitor is smart enough to add a header to indicate how the file is encoded.   Which after some looking doesn't seem to be documented anywhere except as code in the source file. :(


was (Author: rmudgett):
The caller id is coming in between the first and second ring as a FSK spill like it is in the US.  The FSK spill is either cidsignaling=bell or v23 and the cidstart needs to be ring.  To get the caller id, the call must not be answered until the second ring.  However, the call is answered in the middle of the caller id spill so you don't get the caller id.  When the call is answered, I hear what appears to be a partial tt-monkeys file.

> CallerID not detected in India
> ------------------------------
>
>                 Key: ASTERISK-27135
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27135
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: 13.17.0
>         Environment: Debian 8
>            Reporter: luttan
>         Attachments: 04772264853.raw
>
>
> I am using asterisk with PSTN in India and are able to get callerid detection in most of the cases. But in some specific cases no configuration helps in callerid detection. The provider these cases is BSNL.
> I am attaching the raw wav file captured using dahdi_monitor along with the screen shot of the said files opened in audacity.
> I am willing to help with testing of patches or getting any additional information to pinpoint this issue.
> I have attached the raw files captured using dahdi_monitor and it's corresponding audacity screen shots. In both cases I have attempted all combination of cid_signalling and cid_start with no result. In both cases callerid is not getting detected is consistent. Do let me know if any additional information is required to nail this issue



--
This message was sent by Atlassian JIRA
(v6.2#6252)