SMS Server Tools 3
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. The forum is currently read-only, but will open soon. Fri Nov 28, 2025 03:33
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
berrymorr: Try with 3.1.16beta. "Invalid first byte of PDU" was caused because there was no SMSC number. However, this number is not mandatory, and the new version accepts PDU without the number. Thanxs alot, subj beta solved my problem! I would like to thank you for the great tool, too. You did really nice work, man)
berrymorr: Huh, can't edit my post now... O_o So, some news: 4088 isn't error's number, it's just message number. Also, there're troubles only with delivery status messages (that said that your message is successfully delivered to recepient's phone), regular messages parsed ok. I can disable requesting of delivery messages on my phone, but it'll be pretty good to know if sms was successfully delivered or not.
berrymorr: OS: CentOS 5.11: Installed from: smstools3-3.1.15.tar.gz: Motorola SLVR L7 thru USB: Hi! I have subj phone and compiled smstools from original tar. Can send sms, but can not receive, having mysterious error 4088. But PDU converter works perfect with messages from log. So, could somebody help me: what's the right config for that case to receive messages from phone, put them to /var/spool/sms/incoming and delete from phone? smsd.conf: devices = GSM1 logfile = /var/log/smsd.log loglevel = 7 phonecalls = /var/spool/sms/calls incoming_utf8 = yes decode_unicode_text = yes [GSM1] device = /dev/ttyACM0 mode = new incoming = yes incoming = high report = yes send_delay = 20 baudrate = 115200 rtscts = no report_device_details = yes check_memory_method = 31 loglevel_lac_ci = 8 memory_start = 0 hangup_incoming_call = yes phonecalls = clip phonecalls_purge = yes detect_unexpected_input = yes log: 2016-10-22 12:12:34,2, smsd: Smsd v3.1.15 started. 2016-10-22 12:12:34,2, smsd: Running as root:root. 2016-10-22 12:12:34,7, smsd: Running startup_check (shell): /var/spool/sms/incoming/smsd_script.ddyLEx /tmp/smsd_data.SjJ0FF 2016-10-22 12:12:34,7, smsd: Done: startup_check (shell), execution time 0 sec., status: 0 (0) 2016-10-22 12:12:34,4, smsd: File mode creation mask: 022 (0644, rw-r--r--). 2016-10-22 12:12:34,5, GSM1: Modem handler 0 has started. PID: 6910. 2016-10-22 12:12:34,5, smsd: Outgoing file checker has started. PID: 6909. 2016-10-22 12:12:34,7, smsd: All PID's: 6909,6910 2016-10-22 12:12:34,5, GSM1: Using check_memory_method 31: CMGL is used and messages are taken from the list. 2016-10-22 12:12:34,6, GSM1: Checking device for incoming SMS 2016-10-22 12:12:34,6, GSM1: Checking if modem is ready 2016-10-22 12:12:34,7, GSM1: -> AT 2016-10-22 12:12:34,7, GSM1: Command is sent, waiting for the answer 2016-10-22 12:12:34,7, GSM1: <- OK 2016-10-22 12:12:34,6, GSM1: Pre-initializing modem 2016-10-22 12:12:34,7, GSM1: -> ATE0+CMEE=1;+CLIP=1 2016-10-22 12:12:35,7, GSM1: Command is sent, waiting for the answer 2016-10-22 12:12:35,7, GSM1: <- +CME ERROR: 4 (operation not supported) 2016-10-22 12:12:35,3, GSM1: Modem did not accept the pre-init string 2016-10-22 12:12:35,6, GSM1: Checking if modem needs PIN 2016-10-22 12:12:35,7, GSM1: -> AT+CPIN? 2016-10-22 12:12:35,7, GSM1: Command is sent, waiting for the answer 2016-10-22 12:12:36,7, GSM1: <- +CPIN: READY OK 2016-10-22 12:12:36,7, GSM1: -> AT+CSQ 2016-10-22 12:12:36,7, GSM1: Command is sent, waiting for the answer 2016-10-22 12:12:36,7, GSM1: <- +CSQ: 27,99 OK 2016-10-22 12:12:36,6, GSM1: Signal Strength Indicator: (27,99) -59 dBm (Excellent), Bit Error Rate: not known or not detectable 2016-10-22 12:12:36,6, GSM1: Checking if Modem is registered to the network 2016-10-22 12:12:36,7, GSM1: -> AT+CREG? 2016-10-22 12:12:36,7, GSM1: Command is sent, waiting for the answer 2016-10-22 12:12:37,7, GSM1: <- +CREG: 0,1 OK 2016-10-22 12:12:37,6, GSM1: Modem is registered to the network 2016-10-22 12:12:37,6, GSM1: Selecting PDU mode 2016-10-22 12:12:37,7, GSM1: -> AT+CMGF=0 2016-10-22 12:12:37,7, GSM1: Command is sent, waiting for the answer 2016-10-22 12:12:37,7, GSM1: <- OK [here goes output of AT+CIMI and AT+CGSN, cuted out] 2016-10-22 12:12:38,6, GSM1: Checking if reading of messages is supported 2016-10-22 12:12:39,7, GSM1: -> AT+CPMS? 2016-10-22 12:12:39,7, GSM1: Command is sent, waiting for the answer 2016-10-22 12:12:39,7, GSM1: <- +CPMS: "MT",7,254,"MT",0,254,"MT",7,254 OK 2016-10-22 12:12:39,7, GSM1: ## Start of device details 2016-10-22 12:12:39,7, GSM1: # Manufacturer identification: 2016-10-22 12:12:39,7, GSM1: -> AT+CGMI 2016-10-22 12:12:40,7, GSM1: <- +CGMI: "Motorola CE, Copyright 2000" OK 2016-10-22 12:12:40,7, GSM1: # Model identification: 2016-10-22 12:12:40,7, GSM1: -> AT+CGMM 2016-10-22 12:12:40,7, GSM1: <- +CGMM: "GSM900","GSM1800","GSM1900","GSM850","MODEL=L7" OK 2016-10-22 12:12:40,7, GSM1: # Revision identification: 2016-10-22 12:12:40,7, GSM1: -> AT+CGMR 2016-10-22 12:12:41,7, GSM1: <- +CGMR: "R4513_G_08.B7.DCR_RB" OK 2016-10-22 12:12:41,7, GSM1: # New message indications, list of supported modes: 2016-10-22 12:12:41,7, GSM1: -> AT+CNMI=? 2016-10-22 12:12:41,7, GSM1: <- +CNMI: (0,3),(0-2),(0),(0),(0) OK 2016-10-22 12:12:41,7, GSM1: # New message indications, current settings: 2016-10-22 12:12:42,7, GSM1: -> AT+CNMI? 2016-10-22 12:12:42,7, GSM1: <- +CNMI: 0,0,0,0,0 OK 2016-10-22 12:12:42,7, GSM1: # Preferred message storage, list of supported mem's: 2016-10-22 12:12:42,7, GSM1: -> AT+CPMS=? 2016-10-22 12:12:43,7, GSM1: <- +CPMS: ("MT","ME","SM","IM","OM","BM","DM"),("MT","ME","SM","OM","DM"),("MT","ME","SM","IM") OK 2016-10-22 12:12:43,7, GSM1: # Phonebook storage, available mem's: 2016-10-22 12:12:43,7, GSM1: -> AT+CPBS=? 2016-10-22 12:12:43,7, GSM1: <- +CPBS: ("ME","SM","MT","ON","DC","MC","RC","AD","QD","FD") OK 2016-10-22 12:12:43,7, GSM1: # List messages, list of supported stat's: 2016-10-22 12:12:43,7, GSM1: -> AT+CMGL=? 2016-10-22 12:12:44,7, GSM1: <- +CMGL: (0,1,2,3,4) OK 2016-10-22 12:12:44,7, GSM1: # Delete message, list of supported values: 2016-10-22 12:12:44,7, GSM1: -> AT+CMGD=? 2016-10-22 12:12:44,7, GSM1: <- +CME ERROR: 4 (operation not supported) 2016-10-22 12:12:44,7, GSM1: # Phone activity status, list of supported stat's: 2016-10-22 12:12:45,7, GSM1: -> AT+CPAS=? 2016-10-22 12:12:45,7, GSM1: <- +CPAS: (0,2-4) OK 2016-10-22 12:12:45,7, GSM1: # TE character set, list of supported charset's: 2016-10-22 12:12:45,7, GSM1: -> AT+CSCS=? 2016-10-22 12:12:46,7, GSM1: <- +CSCS: ("8859-1","ASCII","GSM","UCS2","UTF8") OK 2016-10-22 12:12:46,7, GSM1: # TE character set, current setting: 2016-10-22 12:12:46,7, GSM1: -> AT+CSCS? 2016-10-22 12:12:46,7, GSM1: <- +CSCS: "ASCII" OK 2016-10-22 12:12:46,7, GSM1: ## End of device details 2016-10-22 12:12:46,6, GSM1: Checking memory size 2016-10-22 12:12:46,7, GSM1: -> AT+CMGL=4 2016-10-22 12:12:47,7, GSM1: Command is sent, waiting for the answer 2016-10-22 12:12:47,7, GSM1: <- +CMGL: 4088,1,,21 00000B919705213951F91F1961012240953221020020 +CMGL: 4087,1,,33 07919740430900F3000B919705213951F90008610112817325210E043F044B04400438043204350434 +CMGL: 4085,1,,21 00000B919705213951F91F1961011281127521020020 +CMGL: 4086,1,,21 00000B919705213951F91F1961011281121521020020 OK 2016-10-22 12:12:47,3, GSM1: CMGL handling error: message 4088, Invalid first byte of PDU 2016-10-22 12:12:47,6, GSM1: No SMS received And so on repeating. Thanks a lot!

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.