Introduction
The SMS service is a way of communicating necessary information/updates on the customers applications for various eGov municipal services which they are availing or are applying for it.
In order to update the users there are certain notification which have been configured at various steps in the application process which can be changed/ configured based upon the requirements.
Data Table
We have the below mentioned parameters which we use for configuration:
Parameter | Value | |
1 | sms.provider.url | |
2 | sms.username.parameter | |
3 | sms.username.value | |
4 | sms.password.parameter | |
5 | sms.password.value | |
6 | sms.senderid.parameter | |
7 | sms.senderid.value | |
8 | sms.smsservicetype.parameter | |
9 | sms.smsservicetype.value | |
10 | sms.content.parameter | |
11 | sms.mobileno.parameter | |
12 | sms.securekey.parameter | |
13 | sms.securekey.value | |
14 | sms.extra.req.params |
Please note: These are the general configuration parameters for which data is required by us but some other vendors might add/delete some parameters depending upon there requirements.
Procedure
For the SMS service to be integrated there are various things for which the vendor more or less guides us for the steps to be followed but below mentioned are a few basic steps and the generic data definitions which could be followed.
Data Definition
Below mentioned are the descriptions of the parameters which are needed for configuration:
Sr.No | Parameter | Description |
1 | sms.provider.url | Service url to send request |
2 | sms.username.parameter | Username key used in request |
3 | sms.username.value | Username value to send in request |
4 | sms.password.parameter | password key used in request |
5 | sms.password.value | password value to send in request |
6 | sms.senderid.parameter | senderid key used in request |
7 | sms.senderid.value | senderid value to send in request |
8 | sms.smsservicetype.parameter | smsservicetype key used in request |
9 | sms.smsservicetype.value | smsservicetype value to send in request |
10 | sms.content.parameter | content key used in request |
11 | sms.mobileno.parameter | mobileno key used in request |
12 | sms.securekey.parameter | securekey key used in request |
13 | sms.securekey.value | securekey value to send in request |
14 | sms.extra.req.params | placeholder to add additional constant key value pairs |
Steps
Since the SMS service is a a vendor delivered service for which the below steps would have to be followed:
Client has to finalize a vendor.
The vendor would ask/ give certain details and code level changes would have to be made in order to achieve the functionality.
At last the IP has to be whitelisted in the vendor’s server.
Validations
Whenever a vendor is chosen please make sure that the vendor should support “ Multiple Language functionality ” and specially the local language of the state.
Attachment
Below is the attached reference template: