smpp_logger Module Configuration

Last updated March 2020

The smpp_logger module determines the location of the SMPP log file, which types of records are created and the format of those records. Find below a sample smpp_logger configuration:

smpp_logger "smpp_logger1" {
  logfile = "/var/log/ecelerity/smpplog.ec"
  logmode = 0644
  log_reception_format = "%t@R@%i@%sa@%da@%d@%g@%b@%H@%B@%sg"
  log_permfail_format = "%t@P@%i@%sa@%da@%d@%g@%b@%H@%e"
  log_delivery_format = "%t@D@%i@%sa@%da@%d@%g@%b@%H@%B@%sg@%rm"
  log_tempfail = false
  log_status = false
}

smpp_logger module configuration options can be set through the web UI in exactly the same way as other options. Setting module options through the web UI is described in Changing Module Configuration Options. Options specific to this module are described below.

concurrency: If the thread_pool option is not configured, this option specifies the number of threads that will be in the pool the logger creates for itself. The default value for this option is 1.
log_conversion: Whether or not message conversion events are logged. The default value for this option is true.
log_conversion_format: This option specifies the log line format for message conversion log entries. The default value is "%t@X@%i@%sa@%da@%d@%g@%b@%H@%e". See Table 2.1, “Log format macros” for a description of how these macros are expanded. The literal value ‘X’ in the second field indicates that the log entry is a conversion.
log_delivery: Whether or not to log MT-SMS deliveries to the SMSC. The default value for this option is true.
log_delivery_format: The delivery log format. The default value for this option is "%t@D@%i@%sa@%da@%d@%g@%b@%H@%B@%sg@%rm". See Table 2.1, “Log format macros” for a description of how these macros are expanded. The literal value ‘D’ in the second field indicates that the log entry is a delivery.
log_permfail: Whether or not to log MT-SMS permanent failures to the SMSC. The default value for this option is true.
log_permfail_format: The permanent failure log format. The default value for this option is "%t@P@%i@%sa@%da@%d@%g@%b@%H@%e". See Table 2.1, “Log format macros” for a description of how these macros are expanded. The literal value ‘P’ in the second field indicates that the log entry is a permanent failure.
log_reception: Whether or not MO-SMS receptions from the SMSC are logged. The default value for this option is true.
log_reception_format: The reception log format. The default value for this option is "%t@R@%i@%sa@%da@%d@%g@%b@%H@%B@%sg". See Table 2.1, “Log format macros” for a description of how these macros are expanded. The literal value ‘R’ in the second field indicates that the log entry is a reception.
log_status: Whether or not to log delivery status messages such as SMSC Delivery receipts, SME acknowledgements and interim delivery notifications. The default value for this option is true.
log_status_format: The status log format. The default value for this option is "%t@S@%sa@%da@%d@%g@%b@%H@%rm@%drl@%T@%S@%e". See Table 2.1, “Log format macros” for a description of how these macros are expanded. The literal value ‘S’ in the second field indicates that the log entry is a status message.

The SMPP status message contains its own type indicated by the macro %T, which can be one of SMSC Status, SME Delivery, SME User Intermediate. Other values may exist, but are represented as Unknown.
log_tempfail: This option specifies the log line format for temporary failures to deliver an MT-SMS to the SMSC The default value for this option is true.
log_tempfail_format: The temporary failure log format. The default value for this option is "%t@T@%i@%sa@%da@%d@%g@%b@%H@%e". See Table 2.1, “Log format macros” for a description of how these macros are expanded. The literal value ‘T’ in the second field indicates that the log entry is a temporary failure.
logfile: The logfile option controls the path to the file where SMPP events are logged by this logger instance. The default value for this option is /var/log/ecelerity/smpplog.ec.
logmode: The log file permissions in octal notation. The default value for this option is 0644.
namespace: The log line formats are composed of static parts and Sieve-style macros. This option allows you to change the namespace used during macro substitution. The default is smpp_logger,sieve,custom_logger meaning the system will first look for an smpp_logger macro with the given name, then a sieve macro, and finally a custom_logger macro.
thread_pool: Specify a thread pool to use. There is no default value for this option. If it is not set, the logger creates a pool named smpp_logger:instance_name_io with concurrency determined by the concurrency option. If thread_pool is set, then the smpp_logger module concurrency option is not used. For more information about creating thread pools see https://support.messagesystems.com/docs/web-ref/conf.ref.threadpool.php .

Like other modules, smpp_logger options can be set or retrieved from the system console. For example, you can set the logmode in the following way: config set smpp_logger smpp_logger1 logmode 0644 . For more information see config.

Log Format Macros

The macros used to determine the content of log entries are described in the following:

Macro	Description
%t	The time in seconds since the Unix epoch when the event was logged.
%i	The Momentum message ID of the message; this will be the same in all log lines related to a message, even in different protocol logs (i.e. SMTP and SMPP).
%d	The routing domain of the SMS message.
%g	The binding group to which the message belongs. If the binding is not in a group, the group is logged as "default".
%b	The binding to which the message is assigned.
%H	The remote IP address of the connection on which the log event occurred
%dc	The SMS data coding used in the SMS message.
%sa	The source address of the SMS message. Note that for status events, this refers to the source of the original message for which we are getting status, not the status message itself.
%sn	The source numbering plan of the SMS message. Note that for status events, this refers to the source of the original message for which we are getting status, not the status message itself.
%st	The source type of number of the SMS message. Note that for status events, this refers to the source of the original message for which we are getting status, not the status message itself.
%da	The destination address.
%dn	The destination numbering plan of the SMS message. Note that for status events, this refers to the destination of the original message for which we are getting status, not the status message itself.
%dt	The destination type of number of the SMS message. Note that for status events, this refers to the destination of the original message for which we are getting status, not the status message itself.
%rm	the MessageID in the response. It is assigned by the remote server/SMSC.
%rM	The message ID returned by the SMSC in the submit_sm_response. This is the raw version, and may contain arbitrary characters!
%T	The status type in the status event, i.e. "SMSC Delivery", "SME User", etc.
%S	The status in the status event, i.e. "Enroute", "Delivered", "Accepted", etc.
%e	The error description in the SMPP response, as defined in the spec or may be vendor-specific.
%B	The message size.
%sg	When a large message gets sent through multiple SMSes, this field indicates the segment number of the log line.
%text	The SMS message payload (in the character set indicated by the %dc macro).
%drl	The delivery report latency. The interval between submission and receipt.

Was this page helpful?

smpp_logger Module Configuration

Log Format Macros#

Log Format Macros