[asterisk-bugs] [Asterisk 0015549]: [patch] Initialization error in chan_mobile

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=15549 
====================================================================== 
Reported By:                medtoledo
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   15549
Category:                   Addons/chan_mobile
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.0-beta4 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-07-21 14:29 CDT
Last Modified:              2009-10-16 10:31 CDT
====================================================================== 
Summary:                    [patch] Initialization error in chan_mobile
Description: 
we get error: "error inicializing bluetooth devise"


====================================================================== 

---------------------------------------------------------------------- 
 (0112369) mnicholson (administrator) - 2009-10-16 10:31
 https://issues.asterisk.org/view.php?id=15549#c112369 
---------------------------------------------------------------------- 
I should have seen this sooner.  This will not work on 1.6.2 without major
changes to the way initialization works.  It should work fine on trunk,
because in that version, the initialization code was rewritten to support
cases like this (as your testing indicates).

In 1.6.2 the code will not handle unsolicited result messages during
initialization, so when the device sends the BSIR message, the code rejects
it because it was expecting an OK message.  In trunk this has been
completely reworked so that the code will ignore unsolicited result codes,
or deal with them separately.

Your best option is probably to backport the trunk version of chan_mobile
to 1.6.2.  This should not be very difficult. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-16 10:31 mnicholson     Note Added: 0112369                          
2009-10-16 10:31 mnicholson     Status                   ready for testing =>
closed
======================================================================