Closed FPMedia closed 3 years ago
Hey @FPMedia - could you provide some more context please? What error was actually returned (or behaviour that made you realise that messages weren't being sent)? Anything else that might be helpful?
Thank you for the response. There wasn't an actual error / error message in the Vonage Dashboard, the SMS messages just weren't being received at the specified cell number. I wasn't sure why the message wasn't being delivered as there were no specific errors. After investigation, I realised that the issue was that I wasn't submitting to a correctly formed mobile number. So maybe, the suggestion here is to have some way of showing whether a message was successfully delivered?
Understood. The only way to guarantee being able to see delivery status is to set up a Delivery Receipt Webhook (sample PHP code). Some errors are returned automatically as Exceptions in the SDK, but some errors are not able to be determined until we try and hand it off to a carrier. In those latter cases, Delivery Receipts are the only way to know.
For straight SMS there are actually quite a few things that can happen even after we hand it off to a carrier. Some more info can be found in our troubleshooting Knowledge Base article, and how Delivery Receipts work is different for different countries. For example, in the US and Canada Delivery Receipts are only returned when a carrier receives the message, not when it actually hits the handset.
With all that in mind, I don't believe that there is anything we can add to either the Laravel or the base PHP SDK to help illuminate when things go wrong, above-and-beyond setting up a webhook for the Delivery Receipt.
Hi Chris,
No stress, this is actually the perfect solution, thank you!
Appreciate you responding Chris, and thanks for providing some more detail @FPMedia. For the sake of the Voyagers Application I'm happy with the state of this issue and will pop you an email shortly. I think based on the convo above this issue is good to be closed 👍
Great, thanks so much Kevin.
Regards,
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
On Thu, Sep 17, 2020 at 11:08 AM Kevin Lewis notifications@github.com wrote:
Appreciate you responding Chris, and thanks for providing some more detail @FPMedia https://github.com/FPMedia. For the sake of the Voyagers Application I'm happy with the state of this issue and will pop you an email shortly. I think based on the convo above this issue is good to be closed 👍
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Nexmo/nexmo-laravel/issues/48#issuecomment-694102637, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4ASAJSVUM6XZKRROBBDJLSGHGXNANCNFSM4RHPTQMA .
I have had an issue before where I've sent an SMS which hasn't been delivered and I couldn't drill into the actual API request for the SMS with a response. I figured the issue out which was that I hadn't formatted the number correctly but this was through a more manual trial / error process.