SMPP accounts are defined in Customers > SMPP accounts. They are what a customer uses to bind to your SSG instance and send or receive SMS (SMPP, REST, or txtConsole). Each account uses a service, which supplies the pricing plan and routing profile.

A walkthrough is in the Customers tutorial.

The grid can be filtered by customer. It supports search, Excel export, and a 15-minute activity sparkline. The Dashboard also lists customer SMPP accounts with bind-status pills (click a pill to open the account).

The dialog uses on/off switches for bind and submit. An Unsaved changes badge appears if you edit; you are asked to confirm before you cancel or close.

Add an SMPP account

Quick Create SMPP

Use this when the customer already exists.

1. Go to Customers > SMPP accounts.
2. Click Quick Create SMPP.
3. Select the organisation.
4. Select the Service.
5. Optionally enter CUG Mobiles (comma-separated MSISDNs).
6. Choose whether to email the configuration to the customer contact.
7. Click Setup.

To create the customer and first account together, use Quick Create Customer+SMPP on Customers.

Create SMPP account

1. Click Create SMPP account.
2. On Main, select the customer, enter Name and Short name, and select the Service.
3. Turn on Binding enabled and Submit enabled.
4. On Parameters, set at least Submit limit (TPS) and Default source address.
5. On Security, optionally restrict Allowed IP(s).
6. Click Save. System ID and password are assigned on save.

Edit an SMPP account

Double-click the row, or click Edit. Click Save after you change fields.

Row actions

Account information to give to customers

Provide at least:

• System ID and password
• Hosts and ports from Customer endpoints
  • port 2775 for SMPP
  • port 8775 for SMPP over TLS
• The Submit limit (TPS) you configured

Configuration

Main

Bind status is a grid of TRX / TX / RX by site (US, BR, UK, DE, SG, AU). Green means a bind of that type is up at that site.

Parameters

TLVs

Security

Allowed IP(s) — if set, binds are accepted only from these addresses. Enter them in { } brackets, for example {194.247.82.100,194.247.82.105}.

If Allowed IPs are set, the Webhooks tab warns that MO / DLR HTTP callbacks may not be reached.

Enforce TLS — the customer must bind with SMPP over TLS (port 8775).

Binding allowed from — date and time before which binds are rejected.

Rules / Blocking

Rules — rules applied to each submit_sm, in the order shown. See Rules.

Blocking — content lists. A match rejects the message. Lists are defined in Configuration > Firewall > Message content. See Firewall.

Webhooks

Three nested tabs. Each JSON field shows valid / invalid, and has Format and Remove.

If Allowed IP(s) are set, a warning is shown on the MO and DLR tabs.

Message sink (JSON)

Copies each MT submit_sm to a URL.

{"url":"https://connect.signl4.com/webhook/xyz"}

MO webhook (JSON)

Sends each inbound deliver_sm as JSON.

{
  "url":"https://abc.customer.com/sms/api/v1/published/receivesms",
  "source_address":"from",
  "destination_addr":"to",
  "short_message":"body",
  "headers":[
    {
      "authorization": "Basic ABCDEF12346567890="
    }
  ]
}

Example request:

{
  "from":"447700777888",
  "to":"447700111222",
  "body":"Hello world"
}

To forward an MO to email, use the Management API notify URL. Replace the placeholders and URL-encode them. API keys are created in Configuration > Company > User access (manager role).

{
  "url":"https://ssg-portal.melroselabs.com/mgt/notify/?key=[APIKEY]&emailTo=[EMAILTO]&emailFrom=[EMAILFROM]&subject=[SUBJECT]",
  "source_address":"from",
  "destination_addr":"to",
  "short_message":"body"
}

emailFrom must be an authorised sender address for your instance.

DLR webhook (JSON)

Sends each delivery receipt as JSON.

{
  "url":"https://bigcorp123.com/smstest/api/v1/deliveryreceiptsms",
  "source_address":"to",
  "destination_addr":"from",
  "msgid":"sid",
  "status_txt":"status",
  "status_num":"statusn",
  "error_num":"errorn",
  "completion_ts":"ts",
  "headers":[
    {
      "authorization": "Basic cFhyb31lc2lzOjdIRyglOjk4N2hD",
      "apikey": "aebdadef-12321-493213210-23-2321afdab"
    }
  ]
}

Example request:

{
  "to":"447700111222",
  "from":"447700222333",
  "sid":"00000010-00000000279178de",
  "status":"delivered",
  "statusn":2,
  "errorn":0,
  "ts":"2024-08-12T13:07:49.000000+00:00"
}

Reporting

MO and MT volume for this account. Instance-wide reports are in Reports.

MO SMS

Inbound numbers and content patterns routed to this account. Manage them in Routing > Inbound SMS.

CUG

Closed user group MSISDNs. When Use CUG is on, the customer can send only to these numbers (useful for trials).

Source addresses

Permitted source addresses (TON, NPI, address). Used with Use srcaddr list and Reject srcaddr on Parameters.

Routing

Coverage and costs for the service on this account. The same view is in Status > Routing. Check a single destination in Routing > Analyser.

txtConsole

Most recent 100 records of txtConsole activity for this account: Login events, Broadcast usage, Campaign usage.

Other

Options (JSON) — advanced per-account flags. The field validates JSON and has Format. Supported keys:

Example: {"pass_thru_concats":true,"priority_queue":5,"use_dnd_list":true}

Record created is read-only.

Enabled — do not use this to turn an account off. Use Binding enabled and Submit enabled on Main. Existing binds are not dropped when Enabled is cleared.

Archive an SMPP account

Use Archive only when the account is no longer required. New binds are rejected and submission stops. The account is removed from the rest of the portal.

Archiving the customer archives all of that customer's SMPP accounts.