Sorry, you need to enable JavaScript to visit this website.

You are here

Provisioning issues, reliability of the API, and general comments

3 posts / 0 new
Last post

GOVAU's picture
by GOVAU

Provisioning issues, reliability of the API, and general comments
1. I'm still receiving "request timeout (504)" when trying to create a new app. (Update: eventually was able to get through, but I've seen the error 3 times so far). Update 2: I just tried to post a comment on an existing post and got the 504 again. 2. What is the chance of making this API easier to use with regards to provisioning? Two parts to this: a. When I send an SMS, if no number has been provisioned, provision it for me. I suspect you have business rules relating to billing that mean you cannot do this, but the reason I ask is that I'm observing odd behaviour when trying to provision a number. The behaviour is that the create subscription request succeeds (because I can see the returned number), but then when I attempt to retry the SMS send moments later fails with NOT-PROVISIONED. The result of this in my work in progress code is that it will then try to provision again. I can see that the provisioning again succeeds and returns the same number. At which point the SMS send is attempted again, but it fails again with NOT-PROVISIONED. And so on and so on (my code is recursing). Update: OK so after creating a brand new app, and using those keys, I tried this process again and replicated it. However, then about 3-5minutes later I attempted sending again, and it worked first go. So it appears that the create subscription response with a number is not actually provisioned until later. Any ideas? Also see 4. below which is related. b. If I provision a number for 365 days, I assume that after that period it will expire? Is there a way to make some of this transparent? I mean, I'd love to just be able to send an SMS and not have to provision a number at all. And if I do have to provision one, I don't really want to have to come back in 365 days to make sure my system is still working after trying to provision a new number. Thoughts? 3. I'm seeing really slow requests for doing things on this forum (posting, loading pages etc.). 10s+ requests. Any ideas on that one? 4. While trying to get this all working I checked the Analytics tab in the Telstra dev console. When I look at the message count for this brand new app, I see that it has a count of 19. However, there's only one SMS message on my phone. It looks like the Analytics are counting failed requests in there. 19 requests would probably match the number of attempts for which I let my code recurse in 2.a above. It's like the Analytics thinks that the message sent, but the actual API refuses to send it because the number is not provisioned.

GOVAU's picture
by GOVAU

Also, the forum doesn't seem
Also, the forum doesn't seem to be respecting newlines or preformatted blocks? See my post above. Each list item should be separated by a newline.

DeveloperSteve's picture
by DeveloperSteve

Hi Jonathan

Thanks for reaching out and the feedback, we are constantly looking to update and refine so always looking at how we can help make things faster and easier.

The 504s is something weve been monitoring closely and have some fixes we are getting ready to deploy. 

Log in or register to post comments