Suppliers > SMSCs

SMSC or SMS gateway connections to suppliers using SMPP (or using SMPP-to-HTTP Bridge).

Each account dialog box has the following tabs: main, parameters, control, test and logs.

Main

Supplier

Supplier of the SMSC connection.

Name

Full name that identifies this SMSC connection.

Short Name

Name to be used throughout SSG Portal for this SMSC.

System ID

SMPP system ID (or username) for the SMPP account on the SMSC.

Password

SMPP password for the SMPP account on the SMSC.

System Type

SMPP system type (if applicable) for the SMPP account on then SMSC.

Host

Hostname for the SMSC.

Port

Port number for the SMSC.

Use TLS

Setting not used. SMPP over TLS is currently provided using a TLS proxy. Contact support@melroselabs.com with the host and port provided by your supplier for connecting to their SMSC platform and we will provide you with the TLS proxy host and port to use.

Connect From

SSG location (e.g. London or Sydney) that should connect to SMSC.

The SMSC connection will automatically be allocated to an SMSCGW node at the selected location. Automatic allocation takes place when “Connect From” has a location selected, and the SMSC has “administratively down” unchecked and “enabled” checked.

Parameters

Submit limit (TPS)

The rate at which the SSG platform can submit SMS to the SMSC, in transactions per second (SMS/sec).

EnquireLink interval (s)

The maximum period of inactivity (in seconds) before the platform will send an enquire_link PDU to the SMSC.

SMPP version

SMPP version to be used when connecting to SMSC.

Use TRX

If checked, a transceiver bind will be used to connect to the SMSC, other separate transmitter and receiver binds will be established.

Control

Administratively down

Used to control the SMPP bind to an SMSC. Set to bring the bind down and disconnect from the SMSC.

Suspend submit

Used to control submissions to an SMSC. Set to stop the sending of SMS to the SMSC.

Enabled

Used to make the SSG platform aware of an SMSC. Disable only when the SMSC connection is no longer required.

SMSC API ID

Identifier of an SMSC for use when performing operations using the SSG Management API .

Monitor

Webhook (JSON)

SMSC state changes (UP/DOWN) will be notified to the webhook below. The webhook is specified using JSON. We recommend the use of SIGNL4 (http://signl4.com ) to receive and manage alerts.

For example: {"url":"http://connect.signl4.com/webhook/abcd1234"}

From ("MLSSGMonitor"), To ("Operations") and Message (e.g. "SMSC UP: EU-UK ML SMSC Simulator 1") fields contain the alert. The Message field is formatted as follows: SMSC [state]: [site] [smsc-name]

Logs

SMSC connection logs show connection attempts, SMPP binding and disconnections.