Open fvlasie opened 2 years ago
Gibbon is using heavily matthewbdaly/sms-client for SMS sending. The best way to replace this, I think, is to write a Mattewbdaly's Driver implementation for Vonage API to replace it.
The example curl code can be found here or here:
curl -X "POST" "https://rest.nexmo.com/sms/json" \
-d "from=$VONAGE_BRAND_NAME" \
-d "text=A text message sent using the Vonage SMS API" \
-d "to=$TO_NUMBER" \
-d "api_key=$VONAGE_API_KEY" \
-d "api_secret=$VONAGE_API_SECRET"
A slight modification of the Nexmo driver should do the job.
@fvlasie: I roughly went over the API documentation. It seems there isn't any breaking change to the API. I don't quite understand why the current code would stop working. I tried to invoke the API directly with CURL and your API key and secret. But I got no SMS either. If their documentation is correct, perhaps the problem is elsewhere.
Could there be any issue with your Nexmo / Vonage account? Have you tried contacting their support service (https://www.vonage.com/support/) and ask about it?
Describe the Bug
Nexmo has been aqcuired by Vonage and the old code no longer works.
To Reproduce
Try to send a test SMS with Nexmo credentials.
Expected behavior
SMS should be sent.
Actual behavior
SMS is not sent.
Screenshots
No response
Gibbon version
v25
Browser
No response
Browser Version
No response
Additional Context
According to the Vonage API guide:
Where "457ef234" and "SHqUvS3ujQ21wwAAT" are the API key and API secret respectively. And "15413261278" is the receving number.