Overview

When sending SMSs in an old SMSC setup, a MO timeout is seen while routing from 2 different sites (Site 1 and Site 2) to a third site (Site 3). The routing flow is MO-MO on the Site 1 and Site 2 nodes and MO-AT on the Site 3 site. The SW and HW of the old SMSCs are EOL.

Solution

This issue can be caused by performance limitations on Site 3 when inter-site traffic (from Site 1/Site 2 to Site 3) is concerned.  Since the SW and HW of the old SMSCs are EOL, we recommend doing the following:

• Monitor MO timeout counters in Site 1 and Site 2 in parallel to MXP timeout counters in Site 3 to compare the results. If Site 3 Traffic Elements are not performing well this can result in MO timeouts. For example, the counters below indicate timeout errors in the MXP protocol used for internal communication between components, i.e. RTR <-> AMS.
  • • Site 3-RTR1: mxpCounterTxTimeout.0 = Counter32: XXXXX
    • Site 3-RTR2: mxpCounterTxTimeout.0 = Counter32: XXXX
• Offload traffic sent to the old SMSCs by moving it to the Cloud SMSC.
• Change current routing path in Site 1 and Site 2 to avoid inter-site traffic by creating SMPP applications directly connected to the Site 1 and Site 2 for MO-AT routing.