Overview

The issue at hand involves missing log records for messages sent from Application Originating (AO) to Mobile Originating (MO) in the Short Message Service Centre (SMSC). The problem is specific to AO to MO routing, with MO to MO messages unaffected. The customer also reported losing outband records from LGV, affecting the visibility of sent messages in their logs. The problem seems to be related to the MTOR configuration and its handling of message logging. A solution involving the AMS rule did not apply due to its absence in the MTOR configuration.

Solution

To resolve this issue, follow these steps:

1. Set the proper logging profile for the rule. You can use the default logging profile or create a new one. To do this, navigate to Logging > Messages > Profile in your SMSC settings.

Please note that the logging profile is essential for defining the parameters and conditions under which logs are captured and stored. Without specifying a logging profile, the system lacks the necessary instructions to log these transactions effectively. Therefore, setting a logging profile is the recommended approach to ensure that outbound MT logs are captured according to your requirements.

Summary

Missing log records for AO to MO messages in SMSC can be resolved by setting the proper logging profile for the rule. This can be done by navigating to Logging > Messages > Profile in your SMSC settings.

FAQ

1. What is a logging profile?
   A logging profile defines the parameters and conditions under which logs are captured and stored in the SMSC.
2. Why are my AO to MO messages not appearing in the logs?
   This could be due to the absence of a proper logging profile for the rule in your SMSC settings.
3. How can I ensure that my outbound MT logs are captured according to my requirements?
   You can ensure this by setting a logging profile that defines the parameters and conditions under which logs are captured and stored.