This article is about how to use Kannel for testing playSMS. Assumed you have a box of VPS, a droplet, a physical server, or a VM running and playSMS is installed and work properly. Follow manuals here to add Kannel to the playSMS server box, configure both playSMS and Kannel to make them work together.
Once you get a working playSMS connected to a well configured Kannel for testing, you can then send bulk SMS (fake non-delivered to the real cellphone of course) and see the performace of both software handling thousands of SMS.
Let’s start the manual.
Continue reading “Testing playSMS with Kannel”
When you have working playSMS with Kannel, and Mikrotik configured to do something (not related to SMS), you can integrate them to serve something to your users. In the article below the author mentioned that the goals are:
- To renew expired users via sending Username and SCRATCH CODE to playSMS (Ubuntu Server)
- To renew expired users via sending SCRATCH CODE & verify the code with the user profile [later]
Users will be asked to send SMS to playSMS, and playSMS will handle it on its SMS Command to run a script that verify the SMS and commands Mikrotik to do something.
Visit complete article here:
Device file names aren’t persistent, this problem add complexity when managing GSM modems for Kannel, smstools or Gammu.
Here is what you can do to solve problem with non-persistent device file names.
I got a good news to share with you guys: playSMS works in Windows !
My test environment was:
- Windows 7 Home Edition
- Cygwin 1.7.7
- Kannel 1.4.3
- playSMS 0.9.5.1
- WampServer 2.0i
- GSM modem Q2406B, USB (now its freakin cheap! USD 25-35 in Jakarta)
I’m happy, it really works :) All playSMS feature seems to be running properly, including the push update of delivery status (from Sent to Delivered).
Continue reading “playSMS in Windows”