SMS Functionality
Warning:
This feature is deprecated. It is no more available in the latest versions of the 446 Plattform and won't receive any more updates nor support.
In addition to e-mails, the 446 Plattform® allows for sending SMS messages as well. The SMS messages are not sent by the system directly. Instead, an e-mail is sent to a Mail2SMS gateway that forwards the actual SMS message. Alternatively, a file folder the content of the SMS message will be written into can be defined.
As soon as the desired deliverer has been configured, SMS can be used as a preferred medium.
SmsDeliverer
The first method is the SmsDeliverer. It sends an e-mail to an SMS gateway, which then sends the actual SMS.
Configuration
For the deliverer to be usable, several adjustments have to be made in the file:
Isonet.MessagingManager.Service.exe.config
Default path:
C:\Program Files\Isonet\MessagingManager\
In the next step, the following section has to be configured:
<!– In the recipient-, subject- and bodyTemplate following placeholders can be used: –>
<!– {$RecipientMobileNumber$}, {$Subject$}, {$ShortText$} –>
<Deliverer
enabled="True"
type="Isonet.MessagingManager.Deliverers.SmsDeliverer"
recipientTemplate="{$RecipientMobileNumber$}"
subjectTemplate="{$Subject$}"
bodyTemplate="{$ShortText$}"
defaultFromName="Messaging Manager"
defaultFromAddress="development@isonet.ch"
smtpServer="smtp.isonet.ch"
smtpPort="25"
smtpAuthMethod="" smtpUsername=""
smtpPassword=""
smtpUseSSL="False"
alternatives="Isonet.MessagingManager.Deliverers.PlainTextEmailDeliverer"
debugMode="True"
debugAddress="exch2010@isonet.ch"
/>
The following entries have to be configured:
| Entry | Description |
|---|---|
| enabled | This option activates or deactivates the SmsDeliverer. Possible values: True – activated; False – deactivated. |
| recipient |
This entry defines the recipient’s e-mail address. SMS= { $ RecipientMobileNumber $ } @server.eu returns SMS=01234567@server.eu, if a user’s mobile number is 01234567, for example. Alternatively, a customer-specific attribute with the type SMS can be defined, e.g. Mobile.SMS. |
| subject |
Specifies the subject of the SMS message. The expression { $ Subject $ } refers to the subject of the respective messaging schema. |
| bodyTemplate | This is the text of the SMS message. The expression { $ ShortText $ } refers to the short text of the respective messaging schema. |
| default |
Defines the sender’s name. It is only used if the sender specified in the messaging schema does not have a first and last name. |
| default |
Defines the sender’s address It is only used if the sender specified in the messaging schema does not have an e-mail address. |
| smtpServer | Defines the outgoing mail server (SMTP). |
| smtpPort | Defines the port used for the connection to the outgoing mail server (default: 25). |
| smtp |
Authentication method for the outgoing mail server. |
| smtpUserName | Defines the user name for the outgoing mail server. |
| smtpPassword | The user’s password. |
| smtpUseSSL | Enables an encrypted connection to the outgoing mail server (True, otherwise: False). |
| alternatives | Defines the alternative deliverer, if it is not possible to send the message. |
| debugMode | Allows for activating/deactivating the debug mode (True/False). In this mode, messages are not sent to the recipient but to the specified debug e-mail address for testing. |
| debugAddress | Defines the e-mail address to receive the messages as soon as the debug mode is activated. |
Configuring the Sender
If SMS messages are to be sent, the following attributes have to be defined for the user to be the sender of the short message:
First Name, Last Name, and E-Mail-Address: The first and last name are used for displaying the sender’s name (FROM name), the e-mail address is used for displaying the sender’s address (FROM address). The default values in the config file will be used, if this information is not available.
ShortTextToFileDeliverer
Another option for sending SMS messages is the use of the ShortTextToFileDeliverer. No SMS message is sent directly here either. Instead, a file including all of the required information is written into a previously specified folder. In this folder, the message will be processed by another service.
Configuration
In order to use the deliverer, various adjustments have to me made in the file:
Isonet.MessagingManager.Service.exe.config
Default path:
C:\Program Files\Isonet\MessagingManager\
In the next step, the following section has to be configured:
<Deliverer
enabled="True"
type="Isonet.MessagingManager.Deliverers.ShortTextToFileDeliverer_Helpdesk"
targetFolder=""
filenamePattern="Helpdesk.txt"
alternatives=""
maxFileSize="160"
overwriteFiles="True"
debugMode="False"
debugTargetFolder="C:\\Program Files\\Isonet\\Messaging Manager\\DebugFolder"
/>
The following entries can be configured here:
| Entry | Description |
|---|---|
| enabled | This option activates or deactivates the SmsDeliverer. Possible values: True – activated; False – deactivated. |
| targetFolder | Specifies the directory the file is to be written into. Network directories can be used here as well. |
| filenamePattern | Defines the file name for the file to be saved. |
| alternatives | This is an alternative file name to be used if access to the respective file is not possible. |
| maxFileSize | Specifies the maximum file size in characters. |
| overwriteFiles | Defines whether files are to be overwritten in the folder (True/ False). |
| debugMode | Allows for activating/deactivating the debug mode (True/False). In this mode, messages will not be written into the actual folder, but into a debug folder instead. |
| debugTargetFolder | Defines the folder the messages will be saved in, as soon as the debug mode is activated. |