Configure Farm Configuration Wizard for Sending SMS

The SendSMS Activity can be configured to send SMSs by making the following SMS Config settings in the Configuration Wizard:

1. Resource Fields

   This is for mapping resource fields(Users Properties) for sending SMS. There are three fields. They are Email, MobilePhoneProvider, and SMSNumber are mapped to the table.

   Email - Mail id of the user. This field will take input from Users Properties of specified field in this field.

   MobilePhoneProvider - Service Provider. This field will take input from Users Properties of specified field in this field.

   SMS Number - Number of cell in which SMS to be sent. This field will take input from Users Properties of specified field in this field.

   Example: For the List, the Email, MobilePhoneProvider, and SMSNumber will take input from Email, Mobile Phone Provider and SMS Number respectively from the User properties.

2. SMS Sending Connection Types

   Currently three Connection Types are supported:

   GSM - You can send a SMS through a direct GSM modem or GSM phone.

   EmailProvider - You can send a SMS by specifying connection types.

   SMSPatternMatch - Each service provider has their SMS pattern to identify easily.

   Example: Hutch - Hutch number starts from 9886.*

   Airtel - Airtel number starts from 9845.*, 9980.* etc.

   Provider Configuration

   This is for Connection Type specific configuration settings. If you are using a provider other than the default provider specified here, you will have to add the details here. Currently three Connection Types are supported – SMSPatternMatch, GSM, and EmailProvider. Under each Connection Type, apart from their configuration details, two compulsory nodes – SMSMessengerAssembly & SMSMessengerClass – have to be specified. This is the class which sends SMS for each provider. This class should implement ISMSSender interface.

   The following are some examples for setting ProviderConfiguration:

   

   Note: As an alternative, "Nokia 6310i Modem" can be replaced by "COM 1", provided the Nokia phone is connected on COM1.

   

   Here are some details about values in the above example:

   DeviceSettings - 8 databits, no parity, 1 stopbit

   Provider Type - Standard TAP provider

   You can specify '0' for UCP Provider, '2' for TAP provider, 'no request' for LineFeed and '3' for TAP provider, 'no request' for EOT.

   

3. Connection Sequences

   This is the sequence in which the AVEVA Work Tasks Engine will choose the provider for sending SMS.

   For Example:

   

The Engine will try to send SMS using GSM Provider. If this fails, then it will try sending the SMS using other providers in this order: SMSPatternMatch and EmailProvider.