The following SMPP commands are supported by the Roottori SMPP interface:
h5. 3.1 BIND_TRANSMITTER, BIND_RECEIVER, BIND_TRANSCEIVER
Direction: SME \-> Gateway
Binds ESME, resulting in connection being in BOUND_TX, BOUND_RX or BOUND_TRX state. The parameters for this command are:
|| Parameter \\ || Value \\ ||
| SYSTEM_ID \\ | Account username \\ |
| PASSWORD \\ | Account password \\ |
| SYSTEM_TYPE \\ | Ignored \\ |
| INTERFACE_VERSION \\ | Use value 0x34 for version 3.4 \\ |
| TON \\ | Ignored \\ |
| NPI \\ | Ignored \\ |
| ADDRESS_RANGE \\ | Ignored \\ |
We recommend that the BIND_TRANSCEIVER command is used when connecting to the gateway.
h5. 3.2 ENQUIRE_LINK
Direction: SME \-> Gateway
Idle connections will be terminated by the gateway. The client must utilize the ENQUIRE_LINK command to keep an idle connection connected. The gateway will terminate connections that have been idle for 90 seconds.
h5. 3.3 SUBMIT_SM
Direction: SME \-> Gateway
Message are submitted using the SUBMIT_SM command (note: the DATA_SM and SUBMIT_MULTI commands are not supported). None of the optional parameters specified in the SMPP specification are supported, except for the _message_payload_ parameter (used to specify the message payload instead of the _short_message_ parameter). It is up to the implementer to construct a possible UDH for e.g. segmented messages.
For premium priced service the SUBMIT_SM command has been extended to allow for signalling of tariff and operato details. The _service_type_ parameter must be specified when the operation is related to some specific service (the _service_type_ parameter along with the _originating_addr_ parameter specify the service in question). The max. length of the _service_type_ parameter has been extended to 64 characters (please contact Roottori support if a legacy implementation requires a shorted _service_type_ value).
*Message encoding*
The message content is read depending on the value of the _data_coding_ parameter. Content is read in the following way:
|| data_coding value \\ || Used encoding (alphabet) \\ ||
| 0 \\ | IA5 (GSM 03.38) alphabet (not 7 bit compressed) \\ |
| 1 \\ | ISO-8859-1 (latin-1) with special characters encoded as in IA5 (e.g. the € \-character is not included in the ISO-8859-1 alphabet) \\ |
| 2 or 4 \\ | 8-bit binary content \\ |
| 3 \\ | UTF-8 (transformed into the default GSM alphabet) \\ |
| 5 \\ | ISO-8859-15 \\ |
| 8 \\ | UCS-2 encoding (the message will be a unicode message) \\ |
*Optional parameter*
The following optional parameters are specified for the SUBMIT_SM command:
|| Tag \\ || Max. size \\ || Type \\ || Description \\ ||
| 0x1402 \\ | 5 \\ | String \\ | A 5 character operator id. Must be present when sending premium priced messages \\ |
| 0x1403 \\ | 2 \\ | Integer \\ | Tariff for message. The allowed values depend on country, short number and service type, and are provided during service set-up. \\ |
| 0x1450 \\ | 2 \\ | Integer \\ | Mobile Country Code of the recipient. Used along with Mobile Network Code to signal recipient operator details, as required in premium priced services (0x1450 and 0x1451 are used instead of the 0x1402 parameter) \\ |
| 0x1451 \\ | 2 \\ | Integer \\ | Mobile Network Code of the recipient. \\ |
Valid only for connections in BOUND_TX and BOUND_TRX state.
h5. 3.4 DELIVER_SM
Direction: Gateway \-> SME
The DELIVER_SM command is used to deliver messages from the gateway to the ESME. The optional parameters specified above are used to signal the originating MCC and MNC values, which must be used along with the supplied _service_type_ when replying in a premium priced service. The data-coding values are also the same as in the SUBMIT_SM operation, with textual content delivered using a _data_coding_ value of 0 (IA5).
h5. 3.5 UNBIND
Direction: SME \-> Gateway
Disconnects client.
h5.
h5. 3.1 BIND_TRANSMITTER, BIND_RECEIVER, BIND_TRANSCEIVER
Direction: SME \-> Gateway
Binds ESME, resulting in connection being in BOUND_TX, BOUND_RX or BOUND_TRX state. The parameters for this command are:
|| Parameter \\ || Value \\ ||
| SYSTEM_ID \\ | Account username \\ |
| PASSWORD \\ | Account password \\ |
| SYSTEM_TYPE \\ | Ignored \\ |
| INTERFACE_VERSION \\ | Use value 0x34 for version 3.4 \\ |
| TON \\ | Ignored \\ |
| NPI \\ | Ignored \\ |
| ADDRESS_RANGE \\ | Ignored \\ |
We recommend that the BIND_TRANSCEIVER command is used when connecting to the gateway.
h5. 3.2 ENQUIRE_LINK
Direction: SME \-> Gateway
Idle connections will be terminated by the gateway. The client must utilize the ENQUIRE_LINK command to keep an idle connection connected. The gateway will terminate connections that have been idle for 90 seconds.
h5. 3.3 SUBMIT_SM
Direction: SME \-> Gateway
Message are submitted using the SUBMIT_SM command (note: the DATA_SM and SUBMIT_MULTI commands are not supported). None of the optional parameters specified in the SMPP specification are supported, except for the _message_payload_ parameter (used to specify the message payload instead of the _short_message_ parameter). It is up to the implementer to construct a possible UDH for e.g. segmented messages.
For premium priced service the SUBMIT_SM command has been extended to allow for signalling of tariff and operato details. The _service_type_ parameter must be specified when the operation is related to some specific service (the _service_type_ parameter along with the _originating_addr_ parameter specify the service in question). The max. length of the _service_type_ parameter has been extended to 64 characters (please contact Roottori support if a legacy implementation requires a shorted _service_type_ value).
*Message encoding*
The message content is read depending on the value of the _data_coding_ parameter. Content is read in the following way:
|| data_coding value \\ || Used encoding (alphabet) \\ ||
| 0 \\ | IA5 (GSM 03.38) alphabet (not 7 bit compressed) \\ |
| 1 \\ | ISO-8859-1 (latin-1) with special characters encoded as in IA5 (e.g. the € \-character is not included in the ISO-8859-1 alphabet) \\ |
| 2 or 4 \\ | 8-bit binary content \\ |
| 3 \\ | UTF-8 (transformed into the default GSM alphabet) \\ |
| 5 \\ | ISO-8859-15 \\ |
| 8 \\ | UCS-2 encoding (the message will be a unicode message) \\ |
*Optional parameter*
The following optional parameters are specified for the SUBMIT_SM command:
|| Tag \\ || Max. size \\ || Type \\ || Description \\ ||
| 0x1402 \\ | 5 \\ | String \\ | A 5 character operator id. Must be present when sending premium priced messages \\ |
| 0x1403 \\ | 2 \\ | Integer \\ | Tariff for message. The allowed values depend on country, short number and service type, and are provided during service set-up. \\ |
| 0x1450 \\ | 2 \\ | Integer \\ | Mobile Country Code of the recipient. Used along with Mobile Network Code to signal recipient operator details, as required in premium priced services (0x1450 and 0x1451 are used instead of the 0x1402 parameter) \\ |
| 0x1451 \\ | 2 \\ | Integer \\ | Mobile Network Code of the recipient. \\ |
Valid only for connections in BOUND_TX and BOUND_TRX state.
h5. 3.4 DELIVER_SM
Direction: Gateway \-> SME
The DELIVER_SM command is used to deliver messages from the gateway to the ESME. The optional parameters specified above are used to signal the originating MCC and MNC values, which must be used along with the supplied _service_type_ when replying in a premium priced service. The data-coding values are also the same as in the SUBMIT_SM operation, with textual content delivered using a _data_coding_ value of 0 (IA5).
h5. 3.5 UNBIND
Direction: SME \-> Gateway
Disconnects client.
h5.