[asterisk-bugs] [JIRA] (ASTERISK-28269) chan_mobile can't connect to phone again

[George Joseph (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246102#comment-246102 ] 

George Joseph commented on ASTERISK-28269:
------------------------------------------

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

> chan_mobile can't connect to phone again
> ----------------------------------------
>
>                 Key: ASTERISK-28269
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28269
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/chan_mobile
>    Affects Versions: 16.1.1
>         Environment: ubuntu 18.04, asterisk 16.1.1
>            Reporter: Pete Kirkham
>            Severity: Minor
>
> 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



--
This message was sent by Atlassian JIRA
(v6.2#6252)