SMPP-HTTP Bridge
Connect to HTTP/REST SMS gateway providers using the SSG
The SSG includes an SMPP-HTTP Bridge capability that enables you to send SMS to upstream SMS providers that do not support SMPP but instead support HTTP.
Bridge locations
Bridges are located on the UK and Singapore SSG sites. Each bridge is capable of handling up to 1500 TPS.
| Location | Instance |
|---|---|
| EU-UK | # 2 |
| EU-UK | # 3 |
| AP-SG (Singapore) | # 1 |
IP addresses for each instance are provided when bridge is configured by Melrose Labs Support.
Adapters
A number of different providers and APIs are supported through adapters implemented in the SMPP-HTTP Bridge. Below is a description of one of the generic adapters that can be configured to support different providers.
Adapter: jsonPOST
The jsonPost adapter will take SMS messages contained in SMPP submit_sm PDUs and submit them to a HTTP endpoint. The short_message field containing the message is converted to UTF8 based on the data_coding field in the submit_sm PDU and the dcsMCSpecificMeaning configuration value.
Configuration
Parameter | Description | Example |
|---|---|---|
smppsystemid | SMPP system ID use in supplier SMSC configuration within SSG to connect to configured bridge | |
smpppassword | SMPP password associated with system ID | |
dcsMCSpecificMeaning | Character set when data coding scheme (DCS) of message is 0 ("MC default alphabet"). 1: IA5/ASCII, 3: Latin1/ISO 8859-1 (3), 8: UCS2 | 8 |
urlSendSMS | API endpoint URL | |
sourceAddress | Key that should be used for source address in JSON request to API | senderId |
destinationAddr | Key that should be used for destination mobile number in JSON request to API | mobileNo |
message | Key that should be used for text message in JSON request to API | content |
messageID | Key in JSON response that is used for message ID on successful submission of message to API | msgId |
sarRef | Key in JSON request that should be used for concatenated SMS reference. | 99 |
sarTotal | Key in JSON request that should be used for concatenated SMS total parts. | 3 |
sarPart | Key in JSON request that should be used for concatenated SMS part number. | 3 |
sarMetaAlways | Controls whether concatenated SMS meta data (sarRef, sarTotal, sarPart) area always incldued, even when not concatenated SMS. | false |
forceDeliveredOnSubmission | Generation of DLR indicating message delivered. Used when API does not provide delivery status. | true |
urlCallback | Key in JSON request that should be used for the callback URL where DLRs are sent by provider | callback |
dlrQueueName | Internal - Queue to where received DLRs are routed (normally system ID of bridge account) | |
httpInCallbackPath | Internal - Path in callback URL for receiving DLRs specific to a bridge configuration | abacus-uylPLNQR |
Contact [email protected] to set-up an SMPP-HTTP Bridge in your SSG instance.
Updated 15 days ago