Don't deliver alert notifications to ESME not yet bound.

We create a new ESME in smsc->esme_list on establishment
of a TCP connection, yet we do not know the system id 
or anything else, until the ESME identifies and authenticates.

So do not send alert notifications until
we know the bind status (and system_id)

Change-Id: Iec92d4c145ca050c2e212139572eeaae581b99df
This commit is contained in:
Keith Whyte 2019-01-17 01:07:53 +01:00 committed by Keith Whyte
parent 477cbc6d93
commit a3a8821167
1 changed files with 5 additions and 0 deletions

View File

@ -284,6 +284,11 @@ static void alert_all_esme(struct smsc *smsc, struct vlr_subscr *vsub,
/* we currently send an alert notification to each ESME that is
* connected, and do not require a (non-existant) delivery
* pending flag to be set before. */
if (!esme->bind_flags) {
LOGP(DSMPP, LOGL_DEBUG,
"ESME is not (yet) bound, skipping alert\n");
continue;
}
if (!esme->acl->alert_notifications) {
LOGP(DSMPP, LOGL_DEBUG,
"[%s] is not set to receive Alert Notifications\n",