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. Wed Mar 12, 2025 20:07
SMSTools3 Community » Search Bottom

Page:  1

Keywords:
Mode: All keywords (AND)
mzahor: Hi, I have issues with Q2406B modems that they are not able (or I'm not able to setup smstools properly) to store "status report" to SM or ME storage. Then I have to use "routed status report" which are not always handled by smstools (mainly when modem is under higher load). In this case I get: "Cannot handle this routed status report. You MUST DISABLE status report routing with modem settings." I'm looking for modem that is able to operate without routed status report. That means (I believe) modem must be able to store "status report" as regular sms - to SM or ME memory. Maybe Q24plus Wavecom, M35 ? Q2406B is great except issue with status report. Thank you
mzahor: SMS between IPhones ( with disabled iMessage ) was sent correctly
mzahor: Sending device was iPhone ( XR, 8 ) and some android based device. Also tried 3 different GSM providers as senders and 2 different as recipient. Each time the same issue.
mzahor: Correction 0x1B not 0x19
mzahor: Operating system name and version: Debian 9 Version of smsd: latest Smsd installed from: debian repository Name and model of a modem / phone: Wavecom Interface: USB When I send SMS that contains characters from GSM 3.38 codepage then I'm receiving incorrect data. PDU that I have received for SMS with EUR symbol. 0791249130330300040C91249150286469000091602202417080046150390C Text in octets containing 7bit chars : 61 50 39 0C After decoding, we can see that first letter "a" is correct : 0x61 Second is EUR symbol, so first should be 0x19 ( indicating that next 7bit is pointing to extended charset of GSM 3.38 ) , instead, second 7bit char is 0x20, which is SPACE not ESC ( 0x19 ). So, now I don't know if smstools is manipulating PDU or .... Thank you for ideas.
mzahor: Version of smsd: latest Is it possible to set "try time" to X seconds, so system is not trying too long.
mzahor: Did I get whole process right with my use case. Use case: I'm writing SMS files directly to modem queue, not to outgoing folder ( I need to choose which modem exactly will send particular sms ) Situation a.If error occures, then process sleeps for "errorsleeptime" - sms waiting b.If error occures "blockafter" times, then modem is blocked for "blocktime" - sms waiting c.After "blocktime" system check, if sms sending should be retried ( from parameter send_retries) - if not, sms is marked as failed If I set sms header Retries:0, then SMS will wait in steps a., b. and then set as failed. Did I get it right? Thank you
mzahor: Thank you for answers
mzahor: Hi, I'd like special sms header parameter that will cause that system will not retry sending sms ( as defined in smsd.conf ) - in case of first error, sending will fail. For some SMS is better to not be delivered then delivered too late. ( One can retry sending with triggered failed action and decide if retry or drop sms). Thank you
mzahor: Supporting this idea
mzahor: Hi, what will happen with sms in queue if modem is blocked after X error for Y seconds ? Are they requeued to other modem if possible or are they marked as failed, or are they just waiting ? Thank you
mzahor: Version of smsd: Version 3.1.21 Hi, Smstools waiting till start script will end and then starts processing/sending sms? Thank you
mzahor: Version of smsd: Version 3.1.21 Hi, when exactly is triggered: SENT: after modem said, that sending operation was done sucessfully? Or before sms is actually sent by mode? FAILED: after modem done last sending retry without success? Thank you
mzahor: Hi guys, 1. can SMSTOOLS send multiple SMS with multi-modem configuration. That it doesn't want until one SMS on modem 1 is sent and then continue with modem 1 but start sending sms on modem 1 , modem2, .... 2. eventhandler, alarmhandler - if one of handle script stuck or the job takes 2-5 seconds, will stuck whole SMSTOOLS ? if so, only event handlers or also sms sending ? 3. if 2 events occurred, systools will call 2 times event handler script in serial or parallel ? Best regards Michal Zahor
mzahor: ok a set rtscts = yes and working ok ... thanx
mzahor: problem solved - it was my fault - thanx for prompt reply. It was named usb mapping mis-match chaoss [ with UDEV ] so ... now both modems working OK falcom is super - very reliable
mzahor: Operating system: Linux 2.6.22 Version of smsd: 3.1-2+lenny1 Smsd installed from: debian lenny package repository Name and model of a modem / phone: Falcom Twist Serial Interface: serial - connected via RS232 <-> USB [PC side] First we used this 2 modems successfuly. Then upgraded to smstools 3.1 but using USB Falcom modems. Now we need also these 2 old modem [ serial ] but they have problem: 2010-01-27 11:49:06,7, MODEM_TMOBILE: put_command expected (OK)|(ERROR), timeout occurred. 2010-01-27 11:49:06,7, MODEM_TMOBILE: <- 2010-01-27 11:49:06,7, MODEM_TMOBILE: -> AT 2010-01-27 11:49:06,7, MODEM_TMOBILE: Command is sent, waiting for the answer I've tried different baudrates, now config is: init = ATE0 device = /dev/ttyMODEM_TMOBILE incoming = yes queues = SK_TMOBILE pin = 1111 mode = new #mode = ascii smsc = 421903333000 baudrate = 19200 cs_convert = yes report = yes eventhandler = /usr/local/bin/smshandler.pl rtscts = no Thats all , thak you

Page:  1

SMSTools3 Community » Search Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.