Connection Details

SMSC List

Clickatell has a compliance test and production SMSC.  Initially, you’ll need to connect to the compliance test SMSC and perform compliance testing. After this, you’ll be able to connect to the production SMSC.

SMSC

Hostname

Port

Compliance Test

smpp.clickatell.com

2773

Production

smpp.clickatell.com

2775

 

Authentication

The ESME should use its API username, API password and API ID in the supported bind PDUs to authenticate its connection with the SMSC. Please see the bind PDUs below for more detailed information.

NOTE: The ESME's API username and API password can be different to the Developers’ Central account username and password.

 

Binds

The ESME is allowed to connect eight transmitter, eight receiver, and eight transceiver binds per API ID to the SMSC.  The ESME can only create one SMPP API in Developers’ Central. Contact Clickatell support if you require more SMPP APIs. 

Note that there is no throughput limitation, but also no guaranteed throughput, on a bind. However, a single SMPP API should be enough if the ESME configures its SMPP client software with the maximum number of binds and is able to use "windowing" (asynchronous sending).

 

Security

Clickatell has an SSLv3-enabled SMSC if you want to use encryption of the data sent between the ESME and the SMSC. Please contact your technical account manager or Clickatell support for more information.