Table of Contents

SMPP Gateway

When you resell SMPP traffic you need to implement SMPP Gateway or SMPP Proxy.

Such application should start at least one SmppServer to be able to receive SMPP commands on TCP port and several SmppClient instances to send message to another SMPP servers (SMSC, Provider).

On SubmitSm from your customer you send back a response SubmitSmResp with assigned MessageId. Later when you forward this message to another server you will receive another MessageId from SMSC . This SMSC MessageId should also be replaced in DeliverSm ( Receipt ) for the target client.

You can implement routing for incomming messages. F.i. when you are going to forward SMS message you can estimate which SmppClient connection accepts destination phone number and which costs cheaper.

When you need only forward SubmitSm messages I suggest following steps:

These four values:

  • Client's sequence number
  • Client's MessageId
  • Provider's sequence number
  • Provider's MessageId help later to find corresponding client that should receive delivery receipt from provider.

When DeliverSm comes from the provider and contains Delivery Receipt following steps should be done: