Overview

• A customer's subscriber is roaming and tries to send an MO message to another subscriber in a different country
• The message is blocked by MO spoof-checking even if both GT belong to the same network
• Adding the country and network in MGR GUI does not solve the issue.

Workflow

Instructions

Implement Whitelisting workaround

To quickly address this issue with a workaround, you can skip the MO spoofing check if you include the originator MSISDN in a Whitelist as indicated below, section 3.8.7 from ZMM_Firewall_Guide.

===============
3.8.7 Whitelist Originator MSISDNs
You can create up to 16 whitelists of MSISDNs that the FWL will compare to the originator MSISDN specified in the MoForwardSm operation. If the MSISDNs match, the FWL skips the MO spoofing check.
To whitelist originator MSISDNs -

1. In the MGR, go to Routing ➤ Lists and create lists of MSISDNs of the originators that the FWL should consider trusted. Each list can contain up to 10,000 addresses.
2. In the semi-static configuration file, set the tpconfig attribute firewallmosmtrustedoriginatorlist[1..16] to the name of the list, where [1..16] is
   a number between 1 and 16.

Note - The number at the end of the attribute name is required, even if you implement only one list.

Reduce number of spoof-checking digits

To address the root cause and resolve the issue while still spoof-checking MO messages, see this article which explains how to reduce the number of spoof-checking digits to allow a broader number range from the same network.