[Home]

Summary:ASTERISK-28269: chan_mobile can't connect to phone again
Reporter:Pete Kirkham (pkirkham)Labels:
Date Opened:2019-01-30 10:55:09.000-0600Date Closed:
Priority:MinorRegression?Yes
Status:Open/NewComponents:Addons/chan_mobile
Versions:16.1.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:ubuntu 18.04, asterisk 16.1.1Attachments:
Description:I'd like to reopen bug 16357 on Ubuntu 18.04 with Asterisk 16.1.1

My phone connects and disconnects as follows:
[Jan 30 16:16:36] DEBUG[13226]: chan_mobile.c:3275 handle_response_ok: [galaxy] BSRF sent successfully
]Jan 30 16:16:36] DEBUG[13226]: chan_mobile.c:1453 rfcomm_write_full: rfcomm_write() (22) [AT+CIND=?
[Jan 30 16:16:36] DEBUG[13226]: chan_mobile.c:3926 do_monitor_phone: [galaxy] read +CIND: ("call",(0,1)),("callsetup",(0-3)),("service",(0-1)),("signal",(0-5)),("roam",(0,1)),("battchg",(0-5)),("callheld",(0-2))
[Jan 30 16:16:36] DEBUG[13226]: chan_mobile.c:3926 do_monitor_phone: [galaxy] read OK
[Jan 30 16:16:36] DEBUG[13226]: chan_mobile.c:3292 handle_response_ok: [galaxy] CIND test sent successfully
[Jan 30 16:16:36] DEBUG[13226]: chan_mobile.c:3294 handle_response_ok: [galaxy] call: 1
[Jan 30 16:16:36] DEBUG[13226]: chan_mobile.c:3295 handle_response_ok: [galaxy] callsetup: 2
[Jan 30 16:16:36] DEBUG[13226]: chan_mobile.c:3296 handle_response_ok: [galaxy] service: 3
]Jan 30 16:16:36] DEBUG[13226]: chan_mobile.c:1453 rfcomm_write_full: rfcomm_write() (22) [AT+CIND?
[Jan 30 16:16:46] DEBUG[13226]: chan_mobile.c:3894 do_monitor_phone: [galaxy] timeout waiting for rfcomm data, disconnecting
[Jan 30 16:16:46] DEBUG[13226]: chan_mobile.c:3912 do_monitor_phone: [galaxy] timeout while waiting for AT+CIND in response to AT+CIND
[Jan 30 16:16:46] – Error initializing Bluetooth device galaxy.
[Jan 30 16:16:46] – Bluetooth Device galaxy has disconnected.

This looks to me like the same problem although I see that the code of chan_mobile seems to have integrated the patch proposed in 16357
Comments:By: Asterisk Team (asteriskteam) 2019-01-30 10:55:10.743-0600

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].

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.
By: George Joseph (gjoseph) 2019-01-30 12:51:49.175-0600

chan_mobile is supported entirely by the community.

Your issue is in the queue. Your patience is appreciated as a 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