KBI 310836 Issue Addressed: Not All SMS Numbers Are Used In Auto Correction Notification


Argent Advanced Technology 3.1A-1401-E or below


Wednesday, 19 Feb 2014


If a SMS alert uses multiple phone numbers separated by comma, though the SMS alert for original event and escalation is sent successfully, the phone numbers in even location (#2, #4, etc) are skipped when the auto correction notification is fired

For example, the phone numbers are specified as ‘2127661111; 2127661112; 2127661113‘, the number 2127661112 is skipped in auto correction notification

Technical Background

The SMS library wrongly parses the multiple phone numbers, and treats the phone numbers in even location as caller Id


Upgrade to Argent Advanced Technology 3.1A-1401-T2 or later

For customer who cannot upgrade immediately, there is two workaround options:


    But it has implications on how correction notification will be sent for email, pager and network message

    Fully understand what might be affected before taking this approach

  2. Break up the SMS alert containing multiple phone numbers into separate SMS alerts, each alert contains only ONE phone number

    To make it easier to use, an Alert Macro can be defined to wrap all these individual SMS alerts

    Say customer needs to send SMS alert to phone numbers 2127661111, 2127661112 and 2127661113

    Following is a complete how-to steps:

    • Define SMS_A (2127661111), SMS_B (2127661112) and SMS_C (2127661113)
    • Define Alert Macro &AM_SMS containing SMS_A, SMS_B and SMS_C
    • Define SMS_CORRECTION (2127661111; 2127661112; 2127661113)

      The phone number does not matter if registry ‘SEND_CORRECT_NOTIFY_TO_ESCALATED_ONLY‘ is 1

    • In Relator, use &AM_SMS for normal alert and escalation; use SMS_CORRECTION for auto correction notification