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

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27135:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> 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
>            Assignee: 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)