[asterisk-bugs] [Asterisk 0014781]: Initializing Samsung GT-C6620

Mon Mar 30 03:05:56 CDT 2009

The following issue has been SUBMITTED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14781 
====================================================================== 
Reported By:                nikkk
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14781
Category:                   Addons/chan_mobile
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.1-rc1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 823 
Request Review:              
====================================================================== 
Date Submitted:             2009-03-30 03:05 CDT
Last Modified:              2009-03-30 03:05 CDT
====================================================================== 
Summary:                    Initializing Samsung GT-C6620
Description: 
I'm getting an error with Samsung GT-C6620 on intializing phase.
I have modified chan_mobile to let it to connect, this is what I get:

    -- Bluetooth Device GT-C6620 has connected, initilizing...
[Mar 30 09:27:28] DEBUG[26566]: chan_mobile.c:1338 rfcomm_write_full:
rfcomm_write() (21) [AT+BRSF=4
[Mar 30 09:27:28] DEBUG[26566]: chan_mobile.c:1338 rfcomm_write_full:
rfcomm_write() (21) [AT+CIND=?
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:1338 rfcomm_write_full:
rfcomm_write() (21) [AT+CIND?
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:1338 rfcomm_write_full:
rfcomm_write() (21) [AT+CMER=3,0,0,1
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:1338 rfcomm_write_full:
rfcomm_write() (21) [AT+CLIP=1
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:1986 hfp_init: [GT-C6620]
error enabling calling line notification
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:1338 rfcomm_write_full:
rfcomm_write() (21) [AT+VGS=15
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:1992 hfp_init: [GT-C6620]
error synchronizing gain settings
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:1338 rfcomm_write_full:
rfcomm_write() (21) [AT+CMGF=1
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:1338 rfcomm_write_full:
rfcomm_write() (21) [AT+CNMI=2,1,0,1,0
    -- Bluetooth Device GT-C6620 initialised and ready.
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:3306 do_monitor_phone:
[GT-C6620]           ERROR
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:3034 handle_response_error:
[GT-C6620] recieved unexpected AT message 'ERROR'
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:3306 do_monitor_phone:
[GT-C6620]           ERROR
[Mar 30 09:27:29] DEBUG[26566]: chan_mobile.c:3034 handle_response_error:
[GT-C6620] recieved unexpected AT message 'ERROR'

after initialization (partial as you see) I can issue previously failed
commands and I get OK!

localhost*CLI> mobile rfcomm GT-C6620 AT+CLIP=1
[Mar 30 09:34:21] DEBUG[26571]: chan_mobile.c:1338 rfcomm_write_full:
rfcomm_write() (21) [AT+CLIP=1
[Mar 30 09:34:23] DEBUG[26566]: chan_mobile.c:3306 do_monitor_phone:
[GT-C6620] OK
[Mar 30 09:34:23] DEBUG[26566]: chan_mobile.c:2974 handle_response_ok:
[GT-C6620] recieved OK for unhandled request: UNKNOWN

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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-30 03:05 nikkk          New Issue                                    
2009-03-30 03:05 nikkk          Status                   new => assigned     
2009-03-30 03:05 nikkk          Assigned To               => mnicholson      
2009-03-30 03:05 nikkk          Asterisk Version          => 1.6.1-rc1       
2009-03-30 03:05 nikkk          Regression                => No              
2009-03-30 03:05 nikkk          SVN Branch (only for SVN checkouts, not tarball
releases) =>  trunk          
2009-03-30 03:05 nikkk          SVN Revision (number only!) => 823             
======================================================================