Playnet Configuration Questions (Answered!)

(Matt Mencel) #1

I’m trying to figure out how playnet works and how to set it up. I have a master running playsms UI and one slave (soon to be two) with the USB modem attached to it.

I think I have the master and slave setup correctly, but there’s not much documentation on getting it to work or testing it. Should I be able to send an outgoing SMS message on the master (with playnet gateway) and have it go out the modem on the slave? This currently does not work for me but maybe I have something setup wrong.

I think I have to configure my multiple slaves to “Forward all sandbox SMS to a URL” to the master. So that duplicates the incoming SMS message from every slave…to the master? Now instead of doing any message processing on the slaves I should be doing it on the master instead?

Sorry about the questions, I just don’t have a good understanding of how this all works yet.


(Matt Mencel) #2

I found another forum post that had the answer. I had to use Google Translate :stuck_out_tongue_winking_eye: because it wasn’t in English, but it helped me to get it figured out. For anyone else struggling with this here is what worked for me.

In my case I have a MASTER PlaySMS instance running on a virtual machine in my datacenter, and two SLAVE PlaySMS instances running on Raspberry Pi’s, each with two Huawei E353 modems in them. The slaves only need to be able to reach the master via HTTP. The master does not need to connect to the slaves.

On the MASTER: (the master URL in the example is

Go to Settings -> Manage gateway and SMSC - Add the Playnet SMSC

Fill in the fields below and save:

SMSC name: e.g. PlaynetMaster
Local playnet username: e.g. playnet-user
Local playnet password: password for the username above, e.g. pw67675H

Go to Settings -> Main configuration: Set the Default SMSC to the name of the Playnet SMSC.

On the SLAVE:

Modify the slave (there can be more than one, the example here uses one slave only):

Go to Settings -> Manage gateway and SMSC - Add the Playnet SMSC

Fill in the fields below and save:

SMSC name: e.g. PlaynetSlave1
Remote is on: 1 (don’t use “true” like I did the first time and have it not work for days…set it to the string value “1”)
Remote playSMS URL: e.g.
Remote playnet SMSC name: PlaynetMaster
Remote playnet username: Local username in the master playnet (e.g. playnet-user)
Remote playnet password: is the password in the master Local playnet (e.g. pw67675H)
Send SMS from remote using local username Local username on the slave to send with (e.g. admin)

Go to Settings -> Route incoming SMS -> Post rules -> Forward all sandbox SMS to a URL:{SANDBOX_PAYLOAD}

The above is an example when playSMS Master Remote URL is

SANDBOX_PAYLOAD payload = {} is mandatory

In this instance the MASTER SMSC (smsc) is PlaynetMaster, username (u) is playnet-user, password § is pw67675H


As long as sending is working on the slaves…

You should be able to create a new message on the MASTER and have one of the SLAVES retrieve it and send it automatically.

Incoming SMS messages on the SLAVES should get forwarded to the MASTER.

Again, hope this helps someone out. I’ll try to get all the details written up in a blog post in the next week or two and I’ll put a link here when that’s ready.


(Matt Mencel) #3

I just put up a blog post about Sensu alerting using playSMS, including info about the Ruby Gem and Sensu Handler I wrote for it.