Sending SMS seems ok, in fact, pretty much everything looks ok except inbound SMS are not being delivered to any of my endpoints?
That is, an SMS goes out containing an alert, one of the recipients attends and sends back a reply to say they're on it, or they need help, or they need a crew or whatever. The outgoing SMS gets delivered, their reply doesn't get back to my server.
This isn't a single server, it's several different servers, on different IP ranges, with different APIs and keys.
I don't know how to contact anyone who even knows what this stuff is, much less able to look into it.
Anyone got any ideas please?
I'm having the exact same issue, the notifyURL is not being hit and there is no way to see why...
I'm receiving zero SMSs to my callback (notification) URL.
But I can send SMSs using the API fine.
I contacted 'telstradev@team.telstra.com' last night waiting for a response, have sighted this forum topic.
I did some troubleshooting, if you set your notifyURL to empty string, you can retrieve your messages using the '/messages/sms' endpoint, the moment you set a notifyURL using the 'messages/provisioning/subscriptions' endpoint you cannot retrieve the message, it will return with status:"EMPTY".
The only workaround I can see right now is to clear your notifyURL and modify your application to poll '/messages/sms' without the use of a callback...
I also contacted telstradev@team.telstra.com.
My biggest concern is there's no indication on the API Live Status page that there is a problem. So it's definitely a blind spot for Telstra - they don't check to see their notification service works.
I do consider it dishonest to claim their API has had no downtime today. It is obviously broken. Well, hopefully somebody from Telstra actually checks the inbox and figures out what is wrong, adds a test for it, updates the API Live Status page to give a less dishonest representation of service status, and the problem does not re-occur.
I restarted my notification listener.
I connected to my notification listener from another location.
I used tcpdump to verify no attempt was made to contact my notification listener when I sent a test SMS to my subscription.
I attempted to re-subscribe with the same API key.
I attempted to send a SMS from the subscription (which worked).
I received a SMS to my notification listener I sent to a subscription just now. So it appears service is now working. But still no response from Telstra Dev to acknowledge it was down in the first place.
Hi Everyone,
We resolved this issue yesterday at 9.12PM Melbourne time. Today, we will be investigating the failed messages to callback URLs and if feasible, we will re-send them at the earliest as well.
Also, since this has become one of the critical functions of Messaging API, I will work with the team internally and uplift the monitoring around this.
Can you please confirm that you are able to receive messages to your callback URLs?
Regards
Vinodh
Confirmed I've been able to receive messages on at least one of my applications.
Additional testing - I think this was expected by users and disappointing to find it hasn't been.
Additional reporting of status - useful if it's actually showing things we need to know, and not saying "everything's good" when we know it's not.
Some timely way to contact someone when there IS a problem would probably stop me moving all my services away, because this HAS actually become mission-critical for many.
Hi Ross,
Thanks for your candid feedback.
Since you have reported the issue, It's a routine process to check on your end after the reported issue is resolved on the API. We have tested it using handful list of callbacks after fixing the issue.
This is the first time we have witnessed that the callbacks went down and as stated above, we will uplift monitoring on this in due course. Also, the API Live status is useful for customers using the outbound features and I understand your use case could be more inbound related which will address when we uplift the monitoring.
You can always e-mail telstradev@team.telstra.com. We will respond within 24-48 hours during business days.
Regards
Vinodh
Dear All,
As of Monday 10PM Melbourne time, we have re-sent all the failed callbacks, You If you need any support on this issue, please contact us.
Regards
Vinodh