Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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

Currently we have the vendor MSDG(https://services.mgov.gov.in)* integrated for our accounts and the below details are provided by them for us to be configured in our system:

User Id

Password

Sender Id

Secure key

 

 

 

 

*Please note: This vendor has been chosen by our previous clients but the clients are free to chose other vendors keeping in line with the validations. The state/client can register themselves on this and get further information.

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 definitions of the column which are used in the data table:

  1. User Id: Username for us to enter the information.

  2. Password: Password for authentication.

  3. Sendor Id: The sendor’s name for which the information has to be sent.

  4. Secure Key : Another level of encryption in order to secure the details.

Steps

Since the SMS service is a a vendor delivered service for which the below steps would have to be followed:

  1. Client has to finalize a vendor.

  2. The vendor would ask/ give certain details and code level changes would have to be made in order to achieve the functionality.

  3. 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

A reference template is attached for the reference in case the client/state agrees to go ahead with the MSDG vendor service.

  • No labels