Summary:	ASTERISK-29606: garbled or absent bluetooth audio due to hardcoded frame size
Reporter:	V S (shadowcaster3)	Labels:
Date Opened:	2021-08-22 10:13:01	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	Addons/chan_mobile
Versions:	GIT	Frequency of Occurrence	Constant
Related Issues:
Environment:	raspberry pi (as tested), most modern Bluetooth implementations	Attachments:
Description:	Asterisk chan_mobile uses a hard-coded Bluetooth (e)SCO packet size of 48 bytes, instead of using the packet size negotiated at the eSCO connect (ex 60 bytes). As a result, depending on Bluetooth adapter, audio may be one-way, missing at all or garbled. Quick fix: Change #define DEVICE_FRAME_SIZE in chan_mobile.c to match specific setup and recompile https://github.com/asterisk/asterisk/blob/master/addons/chan_mobile.c#L81 Proper fix: Implement packet size detection negotiated at the eSCO connect
Comments:	By: Asterisk Team (asteriskteam) 2021-08-22 10:13:04.804-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Benjamin Keith Ford (bford) 2021-08-23 08:50:49.169-0500 The module you're having difficulty with is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available. Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1] If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way. [1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process [2]: http://www.asterisk.org/community/discuss [3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties