General
SMPP SMS API is developed for explaining the SMSGateway with SMPP Gateway system, installation, operation and management possibilities to the software developers.
Following is the minimum system requirements list in order to use Mobildev SMPP SMS API:
Microsoft Windows 2003 Standard Server
Microsoft SQL Server 2005 Standard Edition
Before starting with sending SMS, SMS user information control must be carried out. If you don’t have a current SMS account please CLICK HERE to obtain a test account from Mobildev Customer Services.
There are two ways to install Mobildev SMSGateway with SMPP Gateway system: on a single server as Database and Application or set up Database and Application servers separately.
By setting up multi database servers, you will be able to back up your data simultaneously with the Cluster Server support. In the meantime, multiple Application Servers can be set up as they will be using the common Database. No matter which server is used for the connection, it will enable the same process to be supported.
Application logging will be carried out locally on the application server. But in the meantime, a record will be assigned in insert only mode on the database. In this way, the logs will be kept safely on both the Application Server and the Database Server.
In terms of performance, a database set up as non cluster and non transactional mode on a single server is the proposed installation. The data must be backed up on map drive within certain periods.
Notice: Having Mobildev SMS Gateway with SMPP Gateway on the same network along with SMSC will provide major performance benefits. Business partners who connect from external networks must be routed over VPN to Mobildev SMS Gateway in order to provide the most secure solution. |
Mobildev SMS Gateway makes the SMSC connection over SMPP Protocol.
It can support more than one SMSC and account.
It can carry out load balancingandrouting.
Mobildev SMPP Gateway Supported Functions
Mobildev SMPP Gateway supports SMPP 3.4.
Supported Commands
Client To Server | Server To Client |
bind_transmitter | bind_transmitter_resp |
bind_receiver | bind_receiver_resp |
bind_transceiver | bind_transceiver_resp |
submit_sM | submit_sm_resp |
deliver_sm_resp | deliver_sm |
enquire_link | enquire_link_resp |
Mobildev SMPP Gateway supports all three connections of bind_transmitter, bind_receiver and bind_transceiver. It will allow single channel connection. If there is an active transmitter connection, it will not allow a new transmitter or transceiver connection with the same system_id. Likewise, if there is an active receiver connection, it will not allow a new receiver or transceiver connection, either.
Registering to the system is carried out with system_id and password. system_type field is left blank for sub dealers for the future versions. It can be left blank for the moment.
The system will await enquire_link message in 60 seconds interval for checking whether the connection is active or not. The connection will be terminated by the server if the message does not arrive on time.
Notice: In order to keep the connection active, the recommended period for sending the enquire_link is 50 seconds. |
The most important feature to be considered during sending of the SMS is making sure that Source Address field is a defined field in the activation screen and knowing that any message sent from this address will be debited from the customer who was matched during activation.
Notice: During sending of SMS, using a Source Address related to another customer will cause this customer to be debited. The solution provider is to control this as it will be held responsible. |
In order to control Source Address and credit balance, additional error codes were created: 0x00000401 Out of credit and 0x00000402 Invalid Source Address
Get A Test AccountI Have a Project! |