SMS messages can be send manually to a crew member or messages can be generated automatically whenever a roster change is made or when you release the roster.
A number of settings need to be done before we can send the SMS.
Shall be OUT
You can use the company SMS provider or one of the following providers that N-OC currently have integrated support for.
SSL stands for Secured Socket Layer - basically it is a secure way of providing authentication and encryption during communication online between your computer and mail server
Send in Curfew:
By default, there is a SMS curfew in the Sleipner config file between 2200-0800, this can be modified by configuring the 'SMSCurfew' system setting.
The curfew will add the messages to a queue to be sent after the curfew passes.
Note that the curfew time span is using local time.
Different filetypes are available, check with your provider which one to use.
The SMS (Short Message Service) protocol only allows a maximum of 160 alpha-numeric characters.
This can be reduced further by using the Setup parameter "SMSMaxLength".
Default SMS sender, which is used when no sms number is provided.
The SMS sender is called the ORIGINATOR. The mobile number of the logged in user will be used.
Defines curfew for SMS Com Channels. Default is 2200-0800lt
Maximum length of SMS. Max. is 160
Defines not allowed words in SMS. Words are defined as comma separated values.
The templates are made in the Integration factory.
We will make 4 templates, two for Revision notifications (Body and Header) that is used every time we make a revision. And two for Roster Releases (Body and Header) that will send a SMS when you release the roster.
Name: Mandatory, use a descriptive name.
Data Type: Must be of type "Human Resources"
Data Element: Text
Add: This will create an empty template.
Template: Add the elements you want in the message.
Follow the same process for the Header.
The process is the same as for Revision Notification
The Events are created in the Automation factory. When an event like a roster revision happen, the Event is triggered and Sleipner will send the message to the COM and the message will go out.
In the Events section we create our two notifications
RevisionNotification and RosterRelease
The way the two events are set up is the same, except for the Event type and the template.
Event: The system has a long list of built in events. For this exercise we use Roster REV and ROSTER PUBL
Datatype: Human Resources
Filter: None, but you could use any of the HR Filters.
Station: None, but you could use Station specific messages
Bounce message: isn't used for SMS
Template Type: Own meassage
Template: RevisionNotification Body
Header Template: RevisionNotification Header
Com Channel: SMS
Com Channel Instance: Select you COM SMS instance
Write Mobile (Communication type, see Phone Types). The system will look after the Mobile communication type on the crew and send the SMS to the phone number attached to Mobile.
From the roster gantt you can send SMS direct to a crew member.
Right click on the crew and select the SMS icon
Originator: the phone number of the user logged in.
Receiver: The phone number of the crew.
Characters left: Controlled by the SMSMaxLength
You can send the message to multiple crew by mark the crew
Manual SMS to Contacts:
From the search dialog
you can send SMS to user that isn't loaded into the Gantt.
Click on the phone number in the SMS column and the SMS dialog will open.