Hey guys, first and foremost this is an amazing tool! Thanks for the hard work.
I have however some issues with my installation since the last reboot and not really sure how to troubleshoot it.
Prior to the reboot I ran a few sample messages back and forth for testing with complete success, now after I rebooted all messages sent stay pending (files to be found under /var/spool/sms/modem1/out.0.1.X)
Here is a sent message log:
192.168.0.114 192.168.0.7 2017-07-08 21:26:51 PID59614e1b29466 admin L2 sendsms # start uid:1 sender_id:[07473624843] smsc:
192.168.0.114 192.168.0.7 2017-07-08 21:26:51 PID59614e1b29466 admin L2 sendsms_queue_create # saving queue_code:5734802f4c824433e7b41d794d0fa209 src:1234 scheduled:2017-07-08 21:26:51
192.168.0.114 192.168.0.7 2017-07-08 21:26:51 PID59614e1b29466 admin L2 sendsms_queue_create # saved queue_code:5734802f4c824433e7b41d794d0fa209 id:5
192.168.0.114 192.168.0.7 2017-07-08 21:26:51 PID59614e1b29466 admin L2 sendsms # dst:1 sms_count:1 total_charges:0
192.168.0.114 192.168.0.7 2017-07-08 21:26:51 PID59614e1b29466 admin L2 sendsms_queue_push # saving queue_code:5734802f4c824433e7b41d794d0fa209 dst:12345
192.168.0.114 192.168.0.7 2017-07-08 21:26:51 PID59614e1b29466 admin L2 sendsms_queue_push # saved queue_code:5734802f4c824433e7b41d794d0fa209 smslog_id:5
192.168.0.114 192.168.0.7 2017-07-08 21:26:51 PID59614e1b29466 admin L2 sendsms # end queue_code:5734802f4c824433e7b41d794d0fa209 queue_count:1 sms_count:1 failed_queue:0 failed_sms:0
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 sendsmsd # start processing queue_code:5734802f4c824433e7b41d794d0fa209 queue_count:1 sms_count:1 scheduled:2017-07-08 21:26:51 uid:1 gpid:0 sender_id:1234
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 sendsmsd # sending queue_code:5734802f4c824433e7b41d794d0fa209 smslog_id:5 to:00447446713586 sms_count:1 counter:1
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 sendsms_process # start
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 simplerate__cansend # allowed user uid:1 sms_to:1234 credit:0.000 count:1 rate: charge:0 balance:0
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 sendsms # saving smslog_id:5 u:1 g:0 gw:smstools smsc:smstools s:1234 d:1234 type:text unicode:0 status:0
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 sendsms_process # saved smslog_id:5 id:5
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 smstools_hook_sendsms # saved outfile:/var/spool/sms/modem1/out.0.1.5 smsc:[smstools]
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 simplerate__deduct # enter smslog_id:5
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 credit_hook_rate_setusercredit # no changes uid:1 balance:0
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 simplerate__deduct # user uid:1 parent_uid: smslog_id:5 msglen:27 count:1 rate: charge:0 credit:0.000 balance:0
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 simplebilling__post # saving smslog_id:5 rate: credit:0.000 count:1 charge:0
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 simplebilling__post # saved smslog_id:5 id:5
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 sendsms_process # end
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 sendsmsd # result queue_code:5734802f4c824433e7b41d794d0fa209 to:1234 flag:1 smslog_id:5
- 2017-07-08 21:26:52 PID59614e1ca5555 - L2 sendsmsd # finish processing queue_code:5734802f4c824433e7b41d794d0fa209 uid:1 sender_id:1234 queue_count:1 sms_count:1
playsmsd is running as you can see
pi@workers-pi:~ $ playsmsd check PLAYSMSD_CONF = /etc/playsmsd.conf PLAYSMS_PATH = /var/www/html/playsms PLAYSMS_LIB = /var/lib/playsms PLAYSMS_BIN = /usr/local/bin PLAYSMS_LOG = /var/log/playsms DAEMON_SLEEP = 1 ERROR_REPORTING = E_ALL ^ (E_NOTICE | E_WARNING) IS_RUNNING = 1 PIDS schedule = 2078 PIDS dlrssmsd = 2080 PIDS recvsmsd = 2082 PIDS sendsmsd = 2084
My modem is showing as “Bus 001 Device 005: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem” with lsusb
Also, the incoming messages, albeit they get a received report on my mobile phone, don’t show up on the All Inbox at all.
P.S. - I masked the phone numbers for privacy
thanks in advance for any advice you can give me on how to best address this issue.