Summary:	ASTERISK-11053: [patch] Add config option to force sms to be disabled
Reporter:	non-poster (non-poster)	Labels:
Date Opened:	2007-12-15 23:45:59.000-0600	Date Closed:	2011-06-07 14:02:59
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Addons/chan_mobile
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) a_patch1.txt
Description:	My bluetooth phone doesn't support SMS with the same commands as the module is implemented with.  This patch allows the config option "disablesms" in mobile.conf to prevent the SMS initialization commands to be sent to the phone.
Comments:	By: non-poster (non-poster) 2007-12-16 01:40:29.000-0600 chan_mobile.c:1005 in rfcomm_write: rfcomm_write() (V3M) [AT+CMGF=1 ] chan_mobile.c:1329 in do_monitor_phone: rfcomm_read() (V3M) [OK] chan_mobile.c:1005 in rfcomm_write: rfcomm_write() (V3M) [AT+CNMI=2,1,0,1,0 ] chan_mobile.c:1329 in do_monitor_phone: rfcomm_read() (V3M) [ERROR] By: Dave Bowerman (dbowerman) 2007-12-17 17:02:22.000-0600 i dont see a need for this. chan-mobile explicitly tests for the commands it needs and disables sms functionality within the driver if it determines sms is not usable. the log you posted below is correct. i.e. the ERROR response causes sms to be disabled. By: Jason Parker (jparker) 2007-12-20 19:19:13.000-0600 Closing, per comment from dbowerman.  Please reopen if you think you'd be able to convince us otherwise ("because it would send one less command" probably isn't enough, IMO). By: non-poster (non-poster) 2007-12-26 23:32:40.000-0600 What is the state of the phone after sending the CNMI command?  CMGF indicates the phone supports Bluetooth-SMS, but some part of the CNMI command isn't compatible with the phone.  What if the phone accepts 4 parameters, and 5 are passed here; do the first 4 parameters take effect, or is the entire command rejected?  Will all phones implement support for this feature the same way? Obviously, something here is non-standard, either in the author's phone, my phone, and/or this module's implementation.  A standard implementation in the phones and in the asterisk module would not cause an error on sending a supposedly supported command. By: jmls (jmls) 2008-02-06 04:21:00.000-0600 any further comments, or can we close ? By: non-poster (non-poster) 2008-02-06 14:48:57.000-0600 If it's okay to leave the phone in an unknown or inconsistent state, it's okay to close this ticket. By: jmls (jmls) 2008-05-03 14:24:42 dbowerman suggests that there is no need for this. Closing due to lack of any other progress.