Summary:	ASTERISK-26142: chan_mobile: Audio issues when connected to chan_sip or chan_pjsip
Reporter:	Nilesh G (nileshgr)	Labels:
Date Opened:	2016-06-23 03:25:15	Date Closed:
Priority:	Minor	Regression?
Status:	Open/New	Components:	Addons/chan_mobile
Versions:	13.9.1	Frequency of Occurrence	Constant
Related Issues:
Environment:	Ubuntu 16.04, Debian 8	Attachments:
Description:	I configured 2 asterisk systems - one on Debian 8 (with asterisk 11) and another on Ubuntu 16.04 (with asterisk 13) and configured chan_mobile, res_pjsip and chan_sip accordingly. The same usb bluetooth dongles with latest firmware were used. When a call is received and bridged to SIP phone in asterisk 11, sound is perfectly clear on both sides, but when the same test is done on asterisk 13, sound coming from the other end (ie. from person connected to the mobile phone) is not audible in SIP (either chan_sip or res_pjsip, doesn't matter). There's just some noise in the SIP receiver. Also, it's not about the difference between the Linux distributions. I have experienced the same when I was trying asterisk 13 on Debian 8 too. Devices used: 1. Nokia C1-01 2. Cisco 7940 3. Kinivo BTD-400 Bluetooth dongle with proper Broadcom firmware loaded in /lib/firmware. Steps to reproduce: 1. Configure chan_mobile using documentation provided at https://wiki.asterisk.org/wiki/display/AST/Mobile+Channel 2. Configure res_pjsip using documentation at https://wiki.asterisk.org/wiki/display/AST/PJSIP+Configuration+Sections+and+Relationships & https://wiki.asterisk.org/wiki/display/AST/Configuring+res_pjsip 3. Make a call from SIP to some other number. Whatever is spoken in the mic of the SIP phone is audible at the other end, but whatever other end speaks comes out as noise from the SIP phone's speaker / handset. 4. Make a call from outside to the mobile phone connected to asterisk and after it is connected to the SIP phone by dialing extension, same behaviour as in 3 is observed. 5. Configure chan_sip using documentation, and disable res_pjsip and repeat the tests 3 and 4 - again same behaviour. This is happening on asterisk 13, but follow the same steps and documentation for asterisk 11 and it works flawlessly!
Comments:	By: Asterisk Team (asteriskteam) 2016-06-23 03:25:16.941-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: Joshua C. Colp (jcolp) 2016-06-23 08:06:57.954-0500 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Nilesh G (nileshgr) 2016-06-25 07:30:01.782-0500 I have updated the ticket with relevant documentation links and steps to reproduce. I don't have the environment right now to produce the packet trace and bluetooth capture. Will provide the same later. But in short, something that is working in version 11 is broke in version 13 for the same set of steps provided in documentation!