Summary:	ASTERISK-25926: DAHDI PRI calls echo only when no caller ID is present
Reporter:	Steve Orner (sorner)	Labels:
Date Opened:	2016-04-15 07:49:40	Date Closed:	2016-04-15 09:50:51
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_dahdi
Versions:	13.6.0 13.7.2	Frequency of Occurrence	Constant
Related Issues:
Environment:	Debian 7, Sangoma A108E card	Attachments:
Description:	We are experiencing an issue where calls coming in from a PRI that have no caller ID are having a lot of echo, where the recipient on our end hears themselves talking. I have searched the internet high and low, and even reached out to a local support vendor who has not been able to track this issue down. I've experimented with many different settings in asterisk and there has been no improvement. I was on 13.6 and upgraded to 13.7.2 to fix another issue we were having, so that is why I listed both versions, but I do not believe this to be version specific. The vast majority of our calls come in with a caller ID and there are no issues, but these ones that don't are echoing for some reason. The calls look like this in the logs: DAHDI/i6/-14a1. Another important observation with this is we can do a chanspy AND go back and listen to recorded calls, and the echo is not present there. It is only on the talking party's handset or head set. I have also enabled echo cancel on the phones which did not make a difference with this. I'm probably in the wrong place for this, but I am running out of sources of information and staff is running out of patience with this issue. We went live on Asterisk in October 2015 and this issue has been present from that time.
Comments:	By: Asterisk Team (asteriskteam) 2016-04-15 07:49:41.544-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: Rusty Newton (rnewton) 2016-04-15 09:45:49.235-0500 We appreciate the difficulties you are facing, however this does not appear to be a bug report and your request or comments would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Rusty Newton (rnewton) 2016-04-15 09:50:43.408-0500 As mentioned in the above comment we don't track or handle support requests on the bug tracker. You might consider also trying community.asterisk.org. Once you have log files, dialplan and can describe how we can reproduce the bug or can at least provide sufficient demonstration of the issue, then we can reopen this ticket. The asterisk issue guidelines linked in the comments above describes what all is needed for a bug report. Thanks!