Overview
You may have an issue where some SMS expire before the validity period you have configured and you are thrown a noPagingError message.
Solution
- This is a known issue where the first delivery attempt results in a successful SRI-SM / SRI-SM-RESP , and the MT fails with noPagingError.
- When the first message is received and fails with noPagingResponse, the DeliveryScheme is changed to the "Absent Subscriber Scheme PRIO 2", which is used for such errors. At this moment, however, the SMSC will inform the HLR about the unavailability of the recipient MSISDN, and will send ReportSM-DeliveryStatus towards the HLR, so that it can update its MWD flags.
-
On the following re-attempts, the HLR will respond the SRI-SM including InformServiceCentre operation, setting the MNRF flag. However, the SMSC considers this as a TCAP-abort message.
Depending on some configuration parameters, the SMSC will launch this SRI-SM in MAP phase1. In this case, if the HLR responds with InformSC operation, the answer is considered a TCAP-abort, because the InformSC is not supported under MAP phase1, so the HLR should not have inserted this operation in the SRI-SM response.
-
A quick fix to this issue is to try to change one parameter in the SMSC configuration to avoid this SRI-SM leave as MAP phase1. To do so, execute the following:
- Inside 'common_config.txt' file (located at /usr/TextPass/etc/ in each of the MGR servers, insert the following parameter -
enablemapphaseoptimisation = "false"
- Then restart each RTR node (one at a time).
- Inside 'common_config.txt' file (located at /usr/TextPass/etc/ in each of the MGR servers, insert the following parameter -
Priyanka Bhotika
Comments