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 May 09, 2025 17:11
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
IBMPortablePC: It appears that I can receive, however the PDU's are listed as "Offhook", the modem is definitely in PDU mode, however the 'offhook' signal appears to be occurring where SMSTools expects the PDU to start. This is a PSTN modem with a GSM command stack. Any thoughts? Error: Cannot decode PDU, see text part for details. From: Received: 15-10-06 23:07:45 Subject: GSM1 Modem: GSM1 IMSI: Report: no Alphabet: ISO Length: 535 PDU: Offhook Pos: ^^~here(1) First tried with PDU mode new (with CSA): PDU ERROR: Position 1,2: While reading first octet: invalid character(s) in string Next tried with PDU mode old (without CSA): PDU ERROR: Position 1,2: While reading First octet of the SMS-DELIVER PDU: invalid character(s) in string No success. This PDU cannot be decoded. There is something wrong.
IBMPortablePC: Okay, that worked! Thanks :) Now, how about ignoring AT+CIMI? The modem is a Z-Text PSTN modem, A V.23bis modem which contains a GSM command stack, however it only implements some of the GSM commands. 2015-10-07 04:30:52,7, GSM1: -> AT+CIMI 2015-10-07 04:30:52,7, GSM1: Command is sent, waiting for the answer 2015-10-07 04:30:58,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1. 2015-10-07 04:30:58,7, GSM1: <- Error
IBMPortablePC: I know this has been covered in other posts and threads, and I have tried adding loglevel_lac_ci = 8 to the modem section of my conf file (see below), however the CREG command is still sent to my modem, which does not respond. devices = GSM1 outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked incoming = /var/spool/sms/incoming logfile = /var/log/smstools/smsd.log infofile = /var/run/smstools/smsd.working pidfile = /var/run/smstools/smsd.pid outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed incoming = /var/spool/sms/incoming sent = /var/spool/sms/sent stats = /var/log/smstools/smsd_stats receive_before_send = no autosplit = 3 loglevel = 7 [GSM1] loglevel_lac_ci = 8 report_device_details = yes loglevel = 7 device = /dev/ttyUSB2 incoming = yes pin = ignore baudrate = 2400 The error is: 2015-10-06 10:06:37,6, GSM1: Checking if Modem is registered to the network 2015-10-06 10:06:37,7, GSM1: -> AT+CREG? 2015-10-06 10:06:37,7, GSM1: Command is sent, waiting for the answer 2015-10-06 10:06:48,7, GSM1: put_command expected (\+CREG:.*OK)|(ERROR), timeout occurred. 1. 2015-10-06 10:06:48,7, GSM1: <- Error 2015-10-06 10:06:48,3, GSM1: Error: Unexpected answer from Modem after +CREG?, waiting 1 sec. before retrying I've spent hours on this and simply cannot work out what I am missing. How to I prevent CREG from being sent, or have the response ignored?

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.