by William King, originally posted on Quentus Technologies blog.
Intro to Flowroute SMS
Flowroute has added SMS functionality to their arsenal of quality communication services. For enhanced usability in the open source community, Quentus wrote native support for Flowroute SMS in FreeSWITCH through the new mod_sms_flowroute.
Mod_sms_flowroute is currently available in the FreeSWITCH source repo. Support in packages will be announced soon!
On your Debian Jessie server, first clone the h2o libraries needed for the module.
On the same server, install FreeSWITCH from source following the steps for Building from source.
After running bootstrap.sh, open /usr/src/freeswitch.git/modules.conf and uncomment or add:
Then proceed with the configure, make, and make install commands.
On your router, forward a port to your FreeSWITCH instance. The external port can be the same as the port FreeSWITCH will be listening on, such as external:8080 pointing to internal:8080, or if desired, they can be different, such as accepting 9023 on your external IP pointing to 8090 on the FreeSWITCH instance.
You can then set the SMS CallBack IP and port on your Flowroute account at https://manage.flowroute.com/accounts/preferences/api/ then click “+Enable SMS” to apply it.
On the FreeSWITCH server in the FreeSWITCH config directory (/usr/local/freeswitch/conf/ when installing from source), open autoload_configs/sms_flowroute.conf.xml and configure based on your Flowroute API credentials and SMS CallBack port:
If you want mod_sms_flowroute to automatically load whenever FreeSWITCH starts, make sure it is present and uncommented in autoload_configs/modules.conf.xml.
Start FreeSWITCH and connect with fs_cli. Since we installed from source:
If FreeSWITCH is already running and you update mod_sms_flowroute configs, apply those changes in fs_cli with:
Receiving Messages with mod_sms_flowroute
The default chatplan in the FreeSWITCH configs is where you can specify what action you want FreeSWITCH to take when a text is received on one of your Flowroute DIDs. Opening chatplan/default.xml shows a template that can be easily modified, similar to a dialplan extension. The “reply” action automatically sends a response to the sender. Let’s add an info application as well.
If left as “^(.*)$”, FreeSWITCH will perform the action(s) that follow for texts to all recipients. This can easily be changed to apply texts to a single DID, or to a particular area code, etc. The line that is commented out demonstrates how to tell FreeSWITCH to run a lua script on receiving a text to a particular recipient. The template includes an “info” application, which prints information about the message to the FreeSWITCH console, fs_cli.
Next, let’s update the chatplan to run a simple lua script that grabs a few fields from the message and prints them to the FreeSWITCH console. We will call it parse_message.lua and place it in the FreeSWITCH scripts directory (/usr/local/freeswitch/scripts since we installed from source).
NOTE: the message headers are stored under the lua global variable “message” not “event.”
Now, with a little rearranging and removal of the “reply,” the chatplan demo extension now looks like this:
To apply, open fs_cli and enter the command:
Our fs_cli output now looks like this:
Now that you have access to the header fields of the text in the lua script, you can do anything you like with that data. You can insert it into a database, pass it as a parameter to a separate API, or generate an outbound sms to deliver it to a new recipient.
Sending Messages with sms_flowroute_send
Use this API and format for sending an outbound SMS from fs_cli, remembering that the sender/source must be one of your Flowroute DIDs:
If the above format is not used, the message will not send and will print:
You can generate SMS messages from the dialplan as well, useful if a bridge is not answered or you want to send out auto-alerts via SMS.