-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interface with smstools #9
Comments
Did you get this resolved? |
Yes this was sorted. My lack of docker knowledge at the time. I do not use playsms anymore but for what its worth this is the last working docker compose file I used. You basically just need to give your container access to the devices. In this example I had 2 modems that mounted on the docker host as ttyUSBx and then you map them to the docker guest.
|
Thank you so much for sharing. What do you now use? |
At the time I had a use case to use SMS to automate some things remotely based on incoming sms and content it received. Since then I don't run that project anymore but if I require the use of SMS again playsms is always my goto for small scale setups with local modems. For something at scale then still playsms but integrated with a provider that can send on scale such as Clickatell or Twilio. |
Alright, thanks. |
Not a bug or issue per say. Might just be my own ignorance but how do I interface with SMS tools when running playsms from a container? Do I need to map a tty port to the container and where do I configure smstools? Or does smstools not run inside playsms do I somehow need to talk to the smstools binary outside of the playsms docker?
The text was updated successfully, but these errors were encountered: