Twilio Setup

As part of the implementation of Twilio, Moveware will configure your system with the correct account information and settings to be able to send SMS messages through Twilio.

System Parameters

Enable SMS feature

To use SMS features, set System Parameter sysparam-spare6[13] = ‘Y’.

Use Twilio SMS

To use Twilio, set the System Parameter “Use Twilio SMS” = ‘Y’

Maximum number of characters allowed when sending Twilio SMS

The Value field of this System Parameter defines how many characters a user can be allowed to use in a single SMS message. If this number of characters exceeded 160 characters, the message will be split, then reassembled back into a single message by recipient’s device. The maximum limit length for SMS is 1600 characters.

Please note, the SMS will be billed per message, not per request. For example, if you send a message with 200 characters to a mobile number, you are charged two messages. Note that special header needs to be appended to handle concatenated messages, so each segment can only contain up to 153 characters.

Twilio SMS – Number of days to check prior from today when looking for previous sms sent message

When an inbound SMS message is received, the system subtracts this number of days from today, then looks for all the ‘SMS Sent’ diary actions with date greater than the subtracted date. For example, let’s say the number of days is set to 7. Moveware has received an SMS message from phone number 123456789. Moveware will look for any SMS Messages that were sent to 123456789 within the last 7 days. Moveware found that on Job 777777, an SMS message was sent to 123456789 5 days ago. That meets the criteria Moveware is looking for, hence it automatically applies the incoming SMS Message to Job 777777. If no match is found, the user will be able to manually choose a Job to apply it to (much like the Outlook Inbox feature in Moveware is used for Emails). Some clients may not wish to have the client auto assign the SMS to a job, in these cases -1 can be entered into the value field so every SMS has to be manually linked. This system parameter can be adjusted by Branch and Cost Centre.

Add SMSuser to Moveware webservice Access

Set up SMS User password:

Keep Message History

Ensure the parameter “KeepMessageHistory” is set to Y (Yes). This will ensure that the sms records are not deleted so that they appear in the sms received list.

Codes and System Settings

Set up Azula API for Twilio SMS

Azula is an Azure function app designed by Moveware. It directs the traffic and communication between Twilio and Moveware database. An Azula ‘SendSMS’ API URL will be set up by the Moveware Support staff during the implementation.

The Azula ‘SendSMS’ API URL needs to be set up in Code Management > XML Type > TwilioSMS.

In the ‘Comments’ field, enter this:

url,https://[azula-domain-name]/api/SendSMS?code=[SendSMS’s Function Key]

To find out [azula-domain-name] and [SendSMS’s Function Key], refer to Twilio Implementation Guide Section 5.2

Setting Up Country Codes

To send an SMS to other countries, the dialing prefix is set in Codes Management. This is already configured by Moveware, however please ensure that the codes are correct using the steps below if you encounter any issues sending international SMS messages.

1. Navigate to Administration > Moveware Setup > Codes Management.

2. Select the code type Country and click on the required country.

3. In the Shortcut field enter the Dialing Prefix.

4. Click Save then Exit.
   
   

International SMS messages may be sent from Moveware once Country Dialing Codes have been set up. International and local SMS messages both cost 1 credit.

Setting up Sender Numbers

Using MoveSMS, we were able to use one phone number under which all SMS messages were sent. Using Twilio, we can add as many numbers as needed. For instance, we can configure a different outbound number for each branch of an organization.

We can also set a default number based on one or several branches. For instance, phone number 1 can be the default for Branches 1 and 2, and a different number can be set as default for Branch 3.

To add a Sender Number, follow these steps:

1. Open Administration > Company Setup > Codes Management

2. Click Add and create as follows:

   1. Type: Employee Notify

   2. Code Value: Set as needed (For example: Phone No1). Must be unique.

   3. Description: Set as needed (For example: Phone No1). Must be unique.

   4. Comments: add the phone number with the following format: +Country code, area code, number. For instance, +15552222222, where +1 is country code, 555 is area code and 2222222 is the number

   5. Set the Status as Active

   6. Shortcut: SMS

Setting up Employee Notifications

Finally, choose the User who is responsible for messages that don’t automatically sync with a Job in Moveware. You set this within Employee Management > User Details > Notify:

When you click on the SMS button anywhere in Moveware, you will get a new dropdown field with all the available numbers, and by default it presents the number linked to the Job’s branch. In the example below Phone No. 1 is linked to Branch: NAM.

The dropdown gives to the ability to manually change to an alternative number if required.

For automated SMS messages, the number to be used will be the number assigned to the Branch of the Job.

Open edge files

There are four files, OpenEdge.BusinessLogic.pl, OpenEdge.Core.pl, OpenEdge.Net.pl, OpenEdge.ServerAdmin.pl which need to be in:

C:\Progress\OpenEdge11\gui

C:\Progress\OpenEdge11\src

C:\Progress\OpenEdge11\tty

…on every terminal and database server that Moveware uses.

An up to date copy of these files be in C:\Moveware\Live\setup\OEProcLibrary on the database server.

Take the files, and copy them into C:\Progress\OpenEdge11\gui, C:\Progress\OpenEdge11\src, and C:\Progress\OpenEdge11\tty manually on the database server, and every terminal server.