| Summary: | ASTERISK-27113: iLBC in Softmix yields choppy audio | ||
| Reporter: | Luke Escude (lukeescude) | Labels: | |
| Date Opened: | 2017-07-07 13:23:21 | Date Closed: | 2020-01-14 11:13:33.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 13.16.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | CentOS 7 x64 | Attachments: | |
| Description: | Assume 2 or more endpoints, all using ilbc:30, in a conference bridge (or page group, same thing).
Audio is extremely choppy - No packet loss, no jitter, just choppy audio. Perform the same test on uLaw, audio seems clear. I am unsure of how to begin diagnosing this issue because there is no debug information available that talks about how audio is being mixed and handled. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-07-07 13:23:21.851-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) 2017-07-07 18:38:00.568-0500 At this stage this seems like more of a support request than a bug triage. The appropriate thing would be to bring an issue like this to the community first on community.asterisk.org or the asterisk-users list to ask for help in diagnosing the issue (as it could still be possibly configuration or system/environment/hardware related). If, after double-checking your configuration and initial troubleshooting against others (who may have run into the issue already) you find no resolution and you also validate your configuration - then you should proceed with the bug tracker. At that point, you would open an issue and provide information such as the exact configuration and hardware needed to reproduce the issue along with any debug available even if it doesn't immediately seem relevant. PCAPs, debug logs including RTP debug and high debug levels. Another thing would be to test the same call, same configuration in a few older versions of the 13 branch to see if a regression happened. By: Asterisk Team (asteriskteam) 2017-07-22 12:00:01.312-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 | ||