Hi all,
Anyone can assist us with this error message?
Regards
Elmarie
···
---------- Forwarded message ---------
From: Djibril Dione djibril@hisp.org
Date: Thu, 19 Jul 2018 at 17:43
Subject: Bulksms gateway Configuration in 2.27
To: Dhis2-User dhis2-users@lists.launchpad.net, DHIS 2 developers dhis2-devs@lists.launchpad.net
Cc: Elmarie Claasen elmarie@hisp.org
Dear DHIS experts,
We are trying to configure bulksms gateway in one of our 2.27 Instance(Build: 946e228) but failing to send sms.
The config seem to be fine but whenever we try to send SMS, we got ‘’authentication failure’’ as indicated by the logs below (I have change the phone Number to 0000…).
* INFO 2018-07-19 16:38:14,989 Sending SMS to [00000000, 000000000] (SmsMessageSender.java [http-nio-8080-exec-8])
* ERROR 2018-07-19 16:38:16,733 SMS failed, failure cause: authentication failure (SmsMessageSender.java [http-nio-8080-exec-8])
The BulkSMS credentials are working perfectly on https://www.bulksms.com
I have also tried a configuration using the API and got the same message using these payload.
- Gateway Config
{
“name”: “bulkSMS”,
“username”: “Username”,
“password”: “Pwd”
}
- Add the gateway to Defaul
- Send sms
{
“message”:“Sms Text”,
“recipients”: [
“47XXXXXX1”,
“47XXXXXX2”
]
}
Am I missing something in the Config?
Is here anyone who had this issue before?
Kind regards.
Djibril Dione
HISP SA
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.