Configuring an SMPP MNC

Short message peer-to-peer protocol (SMPP) is based on the exchange of request and response protocol data units (PDUs) between the SafeLinx Server acting as an external short message entity (ESME) and the short message service center (SMS-C). The SafeLinx Server supports all PDU operations that are defined in the SMPP Specification Version 3.4.

About this task

Configure an SMPP MNC by editing its properties from SafeLinx Administrator.

Procedure

  • To specify the method for binding to the SMC-C, click the Bind page, and then choose one of the following options:
    OptionDescription
    Transceiver The SafeLinx Server sends messages to the SMS-C and receives messages from the SMS-C over a single SMPP session. If this method is selected and the SMS-C does not support it, the SafeLinx Server attempts to bind again by using the Transmitter/Receiver method.
    Transmitter The SafeLinx Server sends short messages to the SMS-C and receives the corresponding SMPP responses from the SMS-C. Choose this option if you do not want to receive mobile-originated messages from other short message entities.
    Receiver The SafeLinx Server receives short messages from the SMS-C and returns the corresponding SMPP message responses to the SMS-C.
    Transmitter/Receiver The SafeLinx Server sends messages to the SMS-C over one SMPP session and receives messages from the SMS-C over a second session.
  • If the SafeLinx Server is configured as a Receiver, you can specify the types of PDU operations that it can accept. Click the PDU (Receive) tab, and then select any of the following options:
    OptionDescription
    Allow outbind operation The SMS-C can signal the SafeLinx Server to originate a bind_receiver request in which the SafeLinx Server can receive short messages from the SMS-C. The SafeLinx Server can then return the corresponding SMPP message responses to the SMS-C.

    To require that the connection is mutually authenticated, select Force secure mutual authentication and specify the SMPP system identifier and SMPP system password.

    Allow unbind operation The SafeLinx Server or SMS-C can send a logoff request to close the current SMPP session.
    Allow data_sm operation The SafeLinx Server can request that the SMS-C transfer a message to an SMS client. The SMS-C might also use this operation to transfer a mobile-originated message to the SafeLinx Server.
    Allow deliver_sm operation The SMS-C can route short messages to the SafeLinx Server for delivery.
    Allow alert_notification operation The SMS-C can send a message to the SafeLinx Server when it detects that a particular SMS client is available and a pending delivery flag is set for that subscriber from a previous data_sm operation.
    Allow enquire_link operation Both the SafeLinx Server and the SMS-C can send confidence-check messages to verify the communication path between them. On receipt of this request, the receiving party sends a response that verifies that the application level connection between them is functioning.
    By default, all values except Allow unbind operation are selected. If the Allow data_sm operation or Allow deliver_sm operation options are enabled, the SMS-C can transfer the following special message types to the SafeLinx Server:
    SMS-C delivery receipt
    On detecting the final state of a registered message stored in the SMS-C, the SMS-C generates a receipt message addressed to the originator of the message.
    Short message entity (SME) delivery acknowledgment
    An indication from the recipient SME that the user read the short message.
    SME manual/user acknowledgment
    An application-generated reply message sent in response to an application request message.
    Intermediate notification
    Provides an intermediate status of a message delivery attempt.
  • If the SafeLinx Server is configured as a Transmitter, you can specify how the it sends protocol data unit messages to the SMS-C. Click the PDU (Transmit) tab, and then choose one of the following options:
    OptionDescription
    None The SafeLinx Server does not submit short messages to the SMS-C.
    submit_sm The SafeLinx Server can submit short messages to the SMS-C for onward transmission to a specified short message entity (SME). The submit_sm operation does not support the transaction message mode. This is the default value.
    data_sm The SafeLinx Server can request the SMS-C to transfer a message to an SMS client. The SMS-C can use the data_sm operation to transfer a mobile-originated message to the SafeLinx Server, including messages of the following special types:
    • SMS-C delivery receipt
    • Short message entity (SME) delivery acknowledgment
    • SME manual/user acknowledgment
    • Intermediate notification
  • After you specify how the SafeLinx Server sends PDU messages, you can specify whether it supports other types of PDU operations. Click the PDU (Transmit) tab, and then select any of the following options:
    OptionDescription
    Allow unbind operation The SafeLinx Server or SMS-C can send a logoff request to close the current SMPP session.
    Allow query_sm operation The SafeLinx Server is allowed to query the status of a previously submitted short message.
    Allow replace_sm operation The SafeLinx Server replaces a previously submitted short message that is still pending delivery.