|
|
SMS Server Tools 3 Community |
Welcome, Guest. Please login or register. |
Tue Apr 23, 2024 06:58 |
This topic is locked
Page: 1
Author |
Post |
|
#1 Tue Mar 23, 2010 08:07, 171 months ago.
|
Member
Registered: Mar 2010
Location: Chelyabinsk, Russian Federation
|
Operating system name and version: ASP Linux, 12 (FC4) Version of smsd: 3.1.6 Smsd installed from: sources Name and model of a modem / phone: Nokia 6131 Interface: bluetooth via rfcomm (/dev/rfcomm0)
Hi!
I plugged my Nokia 6131 via bluetooth, smsd sees it correctly, connection is stable. But I cannot send\recieve sms at all.
Config is below: [GSM1] device = /dev/rfcomm0 incoming = yes
Log is below: 2010-03-19 18:54:59,6, GSM1: Checking if Modem is registered to the network 2010-03-19 18:55:00,7, GSM1: -> AT+CREG? 2010-03-19 18:55:00,7, GSM1: Command is sent, waiting for the answer 2010-03-19 18:55:00,7, GSM1: <- +CREG: 0,1 OK 2010-03-19 18:55:00,6, GSM1: Modem is registered to the network 2010-03-19 18:55:00,6, GSM1: Selecting PDU mode 2010-03-19 18:55:00,7, GSM1: -> AT+CMGF=0 2010-03-19 18:55:00,7, GSM1: Command is sent, waiting for the answer 2010-03-19 18:55:00,7, GSM1: <- OK 2010-03-19 18:55:01,7, GSM1: -> AT+CMGS=21 2010-03-19 18:55:01,7, GSM1: Command is sent, waiting for the answer 2010-03-19 18:55:01,7, GSM1: <- > 2010-03-19 18:55:01,7, GSM1: -> 0011000B919720067149F30000FF07F4329E1E93CD00. 2010-03-19 18:55:01,3, GSM1: Could not send character 0, cause: Resource temporarily unavailable 2010-03-19 18:55:11,3, GSM1: The modem answer was not OK: >
Then I set check_memory_method as described in manual: check_memory_method = 2
Log is below: 2010-03-23 12:46:43,6, GSM1: Checking if reading of messages is supported 2010-03-23 12:46:44,7, GSM1: -> AT+CPMS? 2010-03-23 12:46:44,7, GSM1: Command is sent, waiting for the answer 2010-03-23 12:46:44,7, GSM1: <- +CPMS: "SM",0,10,"SM",0,10,"MT",42,4105 OK 2010-03-23 12:46:44,6, GSM1: Checking memory size 2010-03-23 12:46:44,7, GSM1: -> AT+CMGD=? 2010-03-23 12:46:44,7, GSM1: Command is sent, waiting for the answer 2010-03-23 12:46:44,7, GSM1: <- +CMGD: (1-10),(0-4) OK 2010-03-23 12:46:44,6, GSM1: Used memory is 1, list: 1-10 2010-03-23 12:46:44,6, GSM1: Trying to get stored message 1 2010-03-23 12:46:45,7, GSM1: -> AT+CMGR=1 2010-03-23 12:46:45,7, GSM1: Command is sent, waiting for the answer 2010-03-23 12:46:45,7, GSM1: <- +CMS ERROR: 321 (Invalid memory index)
Does anybody know what's the problem?
|
|
#2 Tue Mar 23, 2010 10:24, 171 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Perhaps you could try a modem setting: send_delay = 50There has been a similar issue (this post), and that setting helped when bluetooth was used. It looks like check_memory_method 2 is not supported by your phone. It does list indexes of messages which are available. In the "MT" storage there are 42 messages currently, and lot of space. You could try to use check_memory_method = 1 and and init = AT+CPMS="SM". If your phone still uses "MT" storage for incoming messages, change the init string to AT+CPMS="MT", or AT+CPMS="MT","MT","MT".
|
|
#3 Wed Mar 24, 2010 06:22, 171 months ago.
|
Member
Registered: Mar 2010
Location: Chelyabinsk, Russian Federation
Topic owner
|
send_delay = 50 helps, thanks.
Now my phone sends sms.
But I cannot get recieved sms:
AT+CPMS="MT generates ERROR, check_memory_method takes no effect with any number (1,3,4,31,41,5), AT+CPMS="SM takes no effect too.
2010-03-24 10:47:17,6, GSM1: Checking if reading of messages is supported 2010-03-24 10:47:17,7, GSM1: -> AT+CPMS? 2010-03-24 10:47:17,7, GSM1: Command is sent, waiting for the answer 2010-03-24 10:47:17,7, GSM1: <- +CPMS: "SM",0,10,"SM",0,10,"MT",65,4105 OK 2010-03-24 10:47:17,6, GSM1: Checking memory size 2010-03-24 10:47:18,7, GSM1: -> AT+CPMS? 2010-03-24 10:47:18,7, GSM1: Command is sent, waiting for the answer 2010-03-24 10:47:18,7, GSM1: <- +CPMS: "SM",0,10,"SM",0,10,"MT",65,4105 OK 2010-03-24 10:47:18,6, GSM1: Used memory is 0 of 10 2010-03-24 10:47:18,6, GSM1: No SMS received
2010-03-24 11:01:23,6, GSM1: Checking if reading of messages is supported 2010-03-24 11:01:23,7, GSM1: -> AT+CPMS? 2010-03-24 11:01:24,7, GSM1: Command is sent, waiting for the answer 2010-03-24 11:01:24,7, GSM1: <- +CPMS: "SM",0,10,"SM",0,10,"MT",69,4105 OK 2010-03-24 11:01:24,6, GSM1: Checking memory size 2010-03-24 11:01:24,7, GSM1: -> AT+CMGL=4 2010-03-24 11:01:25,7, GSM1: Command is sent, waiting for the answer 2010-03-24 11:01:25,7, GSM1: <- OK 2010-03-24 11:01:25,6, GSM1: Used memory is 0 2010-03-24 11:01:25,6, GSM1: No SMS received
In addition
AT+CPMS=? as init string: 2010-03-24 10:38:22,6, GSM1: Initializing modem 2010-03-24 10:38:23,7, GSM1: -> AT+CPMS=? 2010-03-24 10:38:23,7, GSM1: Command is sent, waiting for the answer 2010-03-24 10:38:23,7, GSM1: <- +CPMS: ("ME","SM"),("ME","SM"),("MT") OK
AT+CMGL=? as init string: 2010-03-24 11:19:33,6, GSM1: Initializing modem 2010-03-24 11:19:33,7, GSM1: -> AT+CMGL=? 2010-03-24 11:19:33,7, GSM1: Command is sent, waiting for the answer 2010-03-24 11:19:34,7, GSM1: <- +CMGL: (0-4) OK
|
|
#4 Wed Mar 24, 2010 10:07, 171 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
znaeff wrote 2010-03-24 10:47:18,7, GSM1: <- +CPMS: "SM",0,10,"SM",0,10,"MT",65,4105 OK
...
2010-03-24 10:38:23,7, GSM1: <- +CPMS: ("ME","SM"),("ME","SM"),("MT") OK
Try with: init = AT+CPMS="ME"or init = AT+CPMS="ME","ME","MT"Ensure that there are both/all quotation marks included.
|
|
#5 Wed Mar 24, 2010 13:23, 171 months ago.
|
Member
Registered: Mar 2010
Location: Chelyabinsk, Russian Federation
Topic owner
|
Both init = AT+CPMS="ME" and init = AT+CPMS="ME","ME","MT" work.
But server starts polling of messages from 0 to 4095 for every new message. It seems to be feature of my phone - CMGL is not supported so server cannot get the list.
Thanks a lot.
And last: I saw the "AT Command Set For Nokia GSM And WCDMA Products, v.1.2" : AT+CPMS Preferred Message Storage Selects memory storages. <mem1> is for read/delete procedures, <mem2> for writing/sending, and <mem3> is the preferred memory for received messages
But there is no explaination about ME and MT values.
SM means SIM card, ME and MT - phone memory, ok? What's the difference between ME and MT?
|
|
#6 Wed Mar 24, 2010 13:57, 171 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
znaeff wrote SM means SIM card, ME and MT - phone memory, ok? What's the difference between ME and MT?
Usually "ME" means storage in Mobile Equipment (chip), and "MT" means all storage which is available in terminal. This include both "ME" and "SM". You could try some commands using a communication mode: Stop the smsd if it's running. Start it with: smsd -C GSM1Follow the instructions on screen. Type ATE1 (and Enter) to set echo on. Select storages: AT+CPMS="ME","ME","MT"Get the counters: AT+CPMS?Get the list of messages: AT+CMGL=4Show the results here. You can use Private tags to protect the data.
|
|
#7 Wed Mar 24, 2010 16:41, 171 months ago.
|
Member
Registered: Mar 2010
Location: Chelyabinsk, Russian Federation
Topic owner
|
Results:
Opening device /dev/rfcomm0 Ready. ATE1 OK AT+CPMS="ME","ME","MT" +CPMS: 1,4095,1,4095,1,4105
OK AT+CPMS? +CPMS: "ME",1,4095,"ME",1,4095,"MT",1,4105
OK AT+CMGL=4
OK
|
|
#8 Wed Mar 24, 2010 18:36, 171 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
You are right, this problem is a feature of your phone. Because smsd cannot get the list, it cannot know indexes and as you have already tried, indexes are not from 0 to 4095. 6131 is based on S40 platform, and... DAMN! it's S40 3rd edition, which is also included in the F.A.Q. : "can send but cannot receive.". That's one reason why I'm asking "Name and model of a modem / phone" when a question is posted. But in this case I did not check this at the first view... So, the case is clear: buy a new device ...
|
|
#9 Thu Mar 25, 2010 03:47, 171 months ago.
|
Member
Registered: Mar 2010
Location: Chelyabinsk, Russian Federation
Topic owner
|
I need this Nokia just for testing. I use SIEMENS modem in production. Thanks!
|
This topic is locked
Page: 1
Time in this board is UTC.
|
|
|
|
|
|
|