Start a conversation

Resolving "unknownSubscriber" Error in SMS Delivery

Overview

The error "unknownSubscriber" occurs when a subscriber is not receiving SMS messages due to a mismatch between the SMSC address and the GT, causing the SRI-SM to be sent to the wrong HLR. This issue typically arises when the GT and SMSC address belong to different operators, leading to a routing error. The solution involves validating MNP data and ensuring correct routing configurations.

Information

Error Message: "unknownSubscriber"

Cause: The error occurs when there is a mismatch between the SMSC address and the GT, causing the SRI-SM to be sent to the wrong HLR, which does not recognize the MSISDN and returns the error.

Resolution Steps:

  1. Validate MNP Data:
    • Confirm that the MSISDN is correctly provisioned in the MNP database.
    • Ensure that the GT used in the SRI-SM matches the operator that owns the MSISDN.
  2. Verify Routing Configuration:
    • Check the GT translation and routing rules to ensure they align with the Core's expected HLR point codes.
    • Use the command tp_walk mobNetworkNumberRange to verify that both the SMSC address and GT are mapped to the correct operators.
  3. Monitor and Adjust Configurations:
    • Enable and monitor traps for unknown or conflicting SMSC addresses.
    • Adjust the configuration to ensure that the SRI-SM is routed to the correct HLR GT for the ported-out number.
  4. Verification:
    • Test the SMS delivery to ensure that the messages are being routed correctly and the error no longer occurs.

Note: If the issue persists, further investigation into the routing and configuration settings may be required.

Frequently Asked Questions

How do I know if this error applies to my situation?
You'll see the error message "unknownSubscriber" when attempting to send SMS messages, indicating a routing issue between the SMSC address and the GT.
What should I do if the error persists after following the resolution steps?
If the error persists, verify the MNP data and routing configurations again, and ensure that the GT and SMSC address are correctly aligned. Contact support for further assistance if needed.
How can I proactively detect similar issues in the future?
Enable and monitor traps for unknown or conflicting SMSC addresses, and set up automated alerts to identify and address routing mismatches before they impact service.
Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted

Comments