Limitations and Behaviors in MultiSIM AO-MT Message Delivery

Overview

This section outlines specific behaviors noted in scenarios involving MultiSIM AO-MT (Application Originated-Mobile Terminated) messages when the recipient MSISDN is offline or detached from the mobile network. Understanding these limitations is crucial for setting accurate service expectations.

Key Limitations

1. Delayed Delivery of Stored MultiSIM AO-MT Messages
   Unlike MO-MT (Mobile Originated-Mobile Terminated) messages, MultiSIM AO-MT messages stored in the AMS (Active Message Store) queue do not benefit from immediate delivery upon the recipient MSISDN reattaching to the mobile network. This behavior is consistent regardless of the recipient's SIM card type (non-Ultracard).

2. No AlertSC Functionality for MultiSIM AO-MT Messages
   Stored MultiSIM AO-MT messages do not utilize the AlertSC functionality. This means that the standard mechanism for prompting immediate delivery of queued messages upon recipient MSISDN reattachment does not apply to MultiSIM AO-MT messages, leading to potential delays in message delivery.

3. Pseudo-/Sub-Queue Handling
   MultiSIM AO-MT messages are managed within a pseudo-/sub-queue system within the existing AMS queues. This unique handling might contribute to the differentiated delivery behavior observed for these messages.

4. Trigger for Delivery Attempts
   The delivery attempts for stored MultiSIM AO-MT messages are only initiated by either a new MultiSIM AO-MT message to the same recipient MSISDN or a manual alert using the tp_qcli command. Traditional triggers, such as incoming "normal" messages or the AlertSC, do not initiate delivery attempts for these stored messages.

Recommendations for Customers

• Awareness: Customers should be aware of the distinct handling and limitations associated with MultiSIM AO-MT messages, especially in scenarios where the recipient MSISDN might be offline or detached from the network for extended periods.
• Monitoring and Manual Intervention: In cases where timely delivery of MultiSIM AO-MT messages is critical, manual monitoring and the use of tp_qcli to trigger delivery attempts may be necessary.
• Feedback and Reporting: Customers encountering issues or unexpected behaviors with MultiSIM AO-MT message delivery are encouraged to report these instances for further investigation and potential system enhancements.

Conclusion

This knowledge base article aims to provide transparency regarding the known limitations and behaviors associated with the delivery of MultiSIM AO-MT messages within our messaging system. Understanding these nuances is essential for managing expectations and ensuring effective communication strategies in multi-SIM environments.