...
Below mentioned are the descriptions of the parameters which are needed for configuration:
Sr. No. | ParameterColumn Name | Data Type | Data Size | Mandatory | Description |
---|---|---|---|---|---|
1 | sms.provider.url | Yes | Service url to send request | ||
2 | sms.username.parameter | Yes | Username key used in request | ||
3 | sms.username.value | Yes | Username value to send in request | ||
4 | sms.password.parameter | Yes | password key used in request | ||
5 | sms.password.value | Yes | password value to send in request | ||
6 | sms.senderid.parameter | Yes | senderid key used in request | ||
7 | sms.senderid.value | Yes | senderid value to send in request | ||
8 | sms.smsservicetype.parameter | Yes | smsservicetype key used in request | ||
9 | sms.smsservicetype.value | Yes | smsservicetype value to send in request | ||
10 | sms.content.parameter | Yes | content key used in request | ||
11 | sms.mobileno.parameter | Yes | mobileno key used in request | ||
12 | sms.securekey.parameter | Yes | securekey key used in request | ||
13 | sms.securekey.value | Yes | securekey value to send in request | ||
14 | sms.extra.req.params | Yes | placeholder to add additional constant key value pairs |
*Please note the parameter names could differ from vendor to vendor.
Steps to fill Data
Since the SMS service is a vendor delivered service for which the below steps would have to be followed:
Download the data template attached to this page.
Get a good understanding of all the headers in the template sheet, their data type, size, and definitions by referring to the ‘Data Definition’ section of this document.
In case of any doubt, please reach out to the person who has shared this template with you to discuss and clear your doubts.
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.
...