| Summary: | ASTERISK-27135: CallerID not detected in India | ||
| Reporter: | luttan (luttan) | Labels: | |
| Date Opened: | 2017-07-16 20:15:28 | Date Closed: | 2020-01-14 11:13:38.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_dahdi |
| Versions: | 13.17.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Debian 8 | Attachments: | ( 0) 04772264853.raw |
| Description: | 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 | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-07-16 20:15:28.740-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: luttan (luttan) 2017-07-16 20:18:57.962-0500 attaching raw wav file By: Richard Mudgett (rmudgett) 2017-07-17 12:09:57.845-0500 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. :( By: Asterisk Team (asteriskteam) 2017-08-02 12:00:01.669-0500 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 | ||