These arrows are not in the typical FrontlineSMS process, and represent an external source, which interacts with the HTTP Trigger.
To sum up this diagram, let's see this very simply:
- You configure your port and start to "listen". Here, we use "listen", as this is an active sleep. The HTTP Trigger is silent, but is paying attention on what is happening on the "website".
- Then every time something happens, the HTTP Trigger "wakes up" and deal with the request.
- Let's say you want to send an sms, and you've configured the port 8080, you can go on:
For example, if you want to use the Test Number, just reach this address:
http://localhost:8080/send/sms/000/This is a test!/
By reaching this page, you now take the place of the "Application" entity on the diagram, as you formulate an HTTP request which is going to be "heard" by the Trigger.
When checking your messages, you should see that the message has been sent.
If your host allows you to run Java programs, then you would be able to run FrontlineSMS. It won't be a simple thing to do though, as this isn't really want FrontlineSMS is designed for. Also, how will you plug a phone into your host's server?
Maybe what you want is a server running on a local machine which forwards messages to the web server?
Beyond the wiki and blog posts on the Ushahidi website, do you know if there are any more detailed instructions on how to make Frontline and Ushahidi work together?
I have followed all of the steps from here and have sent messages to my Frontline system which is using the keyword and nothing happens in the dashboard of our Ushahidi installation. In the keywords tab of Frontline, it shows that the keyword with HTTP Request action is live and it shows the number of hits (messages I've sent to test this out).
With reference to this:
"- Let's say you want to send an sms, and you've configured the port 8080, you can go on:"
Does the port here refer to the one that appears in the phones tab? In our case, out GSM modem is connected on COM11 so I have typed in "11" in the HTTP Trigger and pushed start to start listening. Is there anything else that I need to do? I am positive that the laptop is connected to the web so that shouldn't be the problem. Thanks for your help.
I'm planning to create a website that allows people to send SMS using my website. My question is how would I connect FLSMS when my server is running on the Internet while FLSMS is running on my local machine. My website is being hosted using hostGator.
I already know how to work on HTTP Trigger.
Just to understand fully what I'm planning on my site, I will show you use cases.
1. A person will use my website to text his/her SMS to someone.
2. The message will now be processed using FLSMS which is located on my local server.
First of all, you have to make a difference between the HTTP Trigger and an HTTP Request.
The trigger, like I said, is used to "listen", which means its main purpose is to "receive" an event. The request is an action you can set up when receiving a message.
The tutorial you read from Usahidi only uses HTTP requests.
It looks like you've correctly set up your request action, though. The "hits" incrementing is a good sign. If you don't see anything on the Usahidi dashboard, this means that you mistyped the address you in the "external command" dialog for some reason, or that the Usahidi server is down. Every single character is important, so I typed it for you, just in case. Paste this in the address field of the external command:
You'll just have to replace the ***** signs by your own key. (By the way, if you can reach someone at Usahidi, I'd suggest they give this address as a text that people could copy and paste, instead of copying it by themselves. I think it will avoid this kind of problems ;)
As for HTTP trigger, if you really want to use it (which I doubt for the moment), the port is "totally" up to you. There is some kind of protected ports, but you can do pretty much what you want (I often suggest the 8080). This port is absolutely not related to the "port" on which your device is connected on your machine.
it is possible to make your website reach your local machine and trigger a message via the HTTP trigger, but it won't be really convenient, as you'll have to have a fix IP address or a static dns set up.
I guess you can understand we can't cover this on this forum, as it is just a network set up you'd have to go through.
If you really want to do this, I invite you to read on Internet Protocol (IP), DNS, and visit this page, which might help you : http://www.dyndns.com/.