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.
Browse around for latest entries on Google for keyword playsms and found this:
The article is explaining playSMS 1.0-rc9 installation and its basic usage in a simple way but in my opinion the right way to do it, it has screenshots with markers and it is also targeting beginners. The article could also be used as playSMS 1.0 references as both playSMS 1.0-rc9 and playSMS 1.0 are only slightly different.
Example of how to use SMS custom, a feature of playSMS provided by plugin SMS custom for accessing external script on remote URL to get proper SMS response.
Visit here to view example and discuss it: Auto collect sender mobile number
Another post worth to read: Manage custom keyword help – first time.
Try it on your own playSMS server, or use playSMS demo and menu Settings -> Simulate incoming SMS to simulate incoming SMS and the result.
More and more users using playSMS, and some of them ask about whether or not playSMS provides HTTP API. Well the answer is YES. Its been there quite sometime actually, it is called playSMS Webservices API.
For those PHP developers, you can also try to use PHP class specifically implements playSMS Webservices API. Read about it here: http://antonraharja.com/2014/04/28/playsms-webservices-class/
There are in total 8 language translations available in current playSMS.
- Catalan (Spain) ca_CA
- Deutsch (Deutschland) de_DE
- English (United States) en_US
- Spanish (Venezuela) es_VE
- French (France) fr_FR
- Indonesian (Indonesia) id_ID
- Portuguese (Brazil) pt_BR
- Russian (Russia) ru_RU
- Chinese (China) zh_CN
When user or admin activate one of them, sometime they saw changes on displayed text, but on some language no changes made. I’ve seen questions like this asked by playSMS users.
Continue reading “Why Texts Are Not Translated”
Messages are not delivered, they are queued. Admin saw all messages in View SMS queue.
Usually, before 0.9.9.2, this is the case of daemon scripts issue, they are not running or running improperly such as wrong path configured in /etc/default/playsms.
But since I introduced SMS scheduler, a way to schedule delivery of submitted SMS through Send SMS page or webservices, one more issue unfortunately has emerged. It’s the timezone settings, PHP simply cannot determine exact timezone used in the script. The result is every SMS submitted NOW will end up being scheduled for next hour depend on the timezone that actually guessed by PHP.
A discussion in the group shows an example of user experiencing this issue.
So, if you experienced an issue like the first paragraph in this article, and you already make sure that all daemon scripts are running and well configured, then its time to check the timezone settings.
Continue reading “Fix Timezone Problem”