I want to implement playSMS and SMS Tools server in an attempt to create a SMS Gateway using a Raspberry PI 4 4GB and multiple 3G Modems (just for sending/receiving text messages, not a big volume).
So… I have the problem specified in the subject reason of which I can’t send/receive text messages.
My hardware/software config:
Raspberry PI4 4GB with Ubuntu server 20.4 LTS for RPI;
playSMS 1.4.3
smstools3
Thank you so much for your fast reply. Much appreciated.
I was trying to send SMSes while running Raspbian on my RPI. That playsms daemon error made me conclude the issue with not sending SMS is this. Then, after installing Ubuntu server 20.4 LTS on my RPI, having the same playsms daemon issue here as well, I didn’t try to send SMSes again.
I’ll try again and see how it works.
Now I have another problem regarding my modems. I have several Huawei and 2 ZTE. It seems that Huawei modems work just fine but ZTE modems are not creating /dev/ttyUSBx entries and the ID of them under lsusb is 19d2:2000 which is not ok.
Interesting is that same modems worked just fine on Raspbian which is a debian distro as ubuntu…
Sadly I have again that red label. Yesterday it worked after I changed those 2 paths to reflect the correct locations to daemon and conf files.
I had to restart my R PI, I opened the web app again and on Reports -> View logs section says the daemon is not running. I started the daemon manually (I have to find a way and set it up to start at startup), I refreshed Reports->View logs section and the label is still red. I checked public_html/playsms/plugin/feature/playsmslog/config.php and I have the right paths there…
I found nothing wrong in my box, so I dont know how exactly that could happen in your raspi. Check again from console if playsmsd check_json says playsmsd is running, then its running.
If json returns says playsmsd is running, and you have put correct path in config.php, then when you refresh it should shown green.
If still red maybe web cached ? or maybe somehow playSMS web cannot run shell_exec function, but I doubt it since its working once (before you restarted raspi)
I ignored this issue (red label from log section page) and went further with smstools3 installation.
Please confirm how should the cell phone number look in config, let’s take as example the UK prefix:
+44 xxxxxxxxxxxx
0044 xxxxxxxxxxxx
44 xxxxxxxxxxx
I have another question regarding “Default Sender ID” field (Settings -> Main configuration -> Default Sender ID).
What should I put here? I suppose this field doesn’t change the sender ID which is the cell phone number no matter what I add there.
Under normal user, dont run as root. Your installation should also be done by normal user or make sure file and folders permission belongs to normal user.
hmm… unfortunately, the installation was made under sudo. would that be a problem ?
If yes, is there any command under daemon to uninstall playsms in order to reinstall it under regular user or just delete the content of the folder where it was installed?
Anyways, I’m trying to identify what’s the problem on sending/receiving text messages. I even tried to simulate receiving a SMS and it’s not working. dunno why…
I’ve managed to send SMSes from your app, which is super cool. now I don’t get it why I can’t see replies in Inbox. All relies simulated or real ones are in Sandbox. Is there anything else I have to configure?
My final project will have multiple 3G Modems used for sending/receiving SMSes. This technical solution will be used by multiple users (<10).
How does the app organize SMSes sent and received by a user.
What if 2+ users use the same modem/SIM to send/receive SMSes?
That’s not an issue, its the way it is. Browse and search this forum, read them, there are ways how to handle incoming SMS, how to get them into user’s Inbox, etc.