Configuration: ESME
ESME section
“esme
"
This section of the configuration defines the routing of messages submitted by customers connecting to the SMPP Router. ESMEs are identified by the SMPP system ID in the SMPP bind request they issue after connecting to the platform. No passwords are configured in the SMPP Router.
If the system ID is not defined in this section, the “default
" target set will be assumed.
Each entry in the esme
section identifies a system ID ("systemid
") and the associated target set ("sharedtargetsetid
").
Field | Description | Example |
---|---|---|
| Customer’s SMPP system ID mandatory |
|
| Customer’s SMPP password optional |
|
| Customer’s SMPP password hash Used instead of plaintext
esme001:$2y$05$Y6p… optional |
|
| List of IP addresses allowed to connect to the SMPP Router using this ESME’s system ID. optional |
|
| Identifier (id) of target set to where ESME’s traffic should be routed A reserved identifier mandatory |
|
| Maximum allowed number of SubmitSM per second (TPS) for each bind SMPP throttle error will be returned if attempt to exceed limit. optional Default: 65535 |
(5000 SubmitSM per second) |
| Allow binding by ESME If disables (false), ESME will not be able to bind to SMPP Router. optional Default: true |
|
| Allow SubmitSM from ESME If disabled (false), command status (error) 69 will be returned to ESME. optional Default: true |
|
| Array of destination addresses (e.g. MSISDNs, short codes) for which this ESME should receive MO SMS Will match exactly with address or pattern match with a regular expression. optional |
JSON
JSON
|
| Routing to be applied to MT SMS submitted by the ESME See Routing optional |
JSON
|