SMPP Op - Register


This operation causes the Test Instance to inform the SMPP stack that it wishes to receive and process the SMPP PDUs delivered to the IN Tester (in its role as a simulated SMSC) for the specified destination_addr Destination Address.

A Test Instance must perform a registration operation before performing any subsequent SMPP Operation - Receive Request. The Registration remains in place until the Test Instance completes.

A single Test Instance instance may Register multiple Destination Addresses. Duplicate Registrations for a given Destination Address within a single Test Instance definition will be silently ignored. Any Test Instance that attempts to Register a Destination Address that is currently registered by another Test Instance will abort with an error.

Currently the only supported inbound SMPP PDU for Registration is the submit_sm PDU.

Note: If an inbound message is subsequently received but not consumed by a subsequent SMPP Operation - Receive Request, then the Test Instance will abort and raise an error during the end-of-instance shutdown process.


The operation attributes are as follows:

Attribute Type Description
type String smpp.smsc_from_esme.Register
arguments Object [Required] Arguments for the registration, see below.


This is an example entry within the operations array:

    "type": "smpp.smsc_from_esme.Register",
    "arguments": {
        "pdu": "submit_sm",
        "destination_addr": "6421682277"


The following operation arguments are supported:

Argument Type Notes
pdu String [Required] Name of the SMPP Protocol Data Unit (PDU) we wish to receive and process.
Currently the only supported inbound PDU for registration is submit_sm.
destination_addr Hex String [Required] Destination Address for which this Test Run wishes to receive and process inbound submit_sm PDUs.