[asterisk-bugs] [Asterisk 0013744]: Blackberry Pearl (8100) rarely initialises

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Nov 27 13:16:21 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13744 
====================================================================== 
Reported By:                ciaranm
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   13744
Category:                   Addons/chan_mobile
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-20 08:18 CDT
Last Modified:              2008-11-27 13:16 CST
====================================================================== 
Summary:                    Blackberry Pearl (8100) rarely initialises
Description: 
Fedora 9, bluez-3.35-1 (rpms) Asterisk 1.6.0-beta9 from RPM and
asterisk-addons-1.6.0-rc1 from source.

When using a blackberry pearl (8100) I need to unload and load chan_mobile
multiple times before the state moves from Init to Free. Chan mobile
working great with other phones (e.g. Nokia).
Blackberry appears to not respond consistently to (or response may be
missed?) AT+CIND=? however if I attempt to work around this by issuing
AT+CMER=3,0,0,1 manually the BB appears to initialise but the connection is
lost when I recieve a call (has occasionally caused BB to reboot also!). If
the BB does (after repeated attempts) initialise properly then it works
correctly for the duration of that connection.
====================================================================== 

---------------------------------------------------------------------- 
 (0095581) ciaranm (reporter) - 2008-11-27 13:16
 http://bugs.digium.com/view.php?id=13744#c95581 
---------------------------------------------------------------------- 
Thanks ughnz and yep I know it has taken me ages to look at this again
but... and there´s always a but...
Isnt that code already present in chan_mobile? Even with that code present
the init timeout does not meet the condition as from my investigation the
failure to respond to AT+CIND happens when we are at MBL_STATE_INIT1. Even
if I do get the command AT+CMER=3,0,0,1 sent by either changing the code so
this condition is met at MBL_STATE_INIT1 or issuing it manually at the
command line in asterisk the initialisation may fail at a later stage or as
has happened also the initialisation may suceed only for the bluetooth
connection to be dropped when a call is received.
The only way I have got this to work is by repeatedly unloading and
loading chan_mobile until the initialisation suceeds and if it does then
the connection and calls behave perfectly. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-27 13:16 ciaranm        Note Added: 0095581                          
======================================================================




More information about the asterisk-bugs mailing list