Ring-Out API with Blocked number

  • 1
  • Idea
  • Updated 3 months ago
  • (Edited)
First off thank you for updating the RingOut API so we can pass a Caller ID via the API. This works great for numbers on that users account or company numbers.

However, passing "Blocked" as the Caller ID throws an error (I assume because it's not a real number and the new RingOut API doesn't accept "Blocked".

Please add the ability to RingOut and pass either a Blocked boolean or pass "Blocked" as the Caller ID so our users can RingOut instead of having to manually dial *67 and then the number.

I know this can be solved with changing the users account to set their CallerID to Blocked, Ring Out, and then update the account again back to their original CallerID BUT it does seem if you're going to allow us to pass a CallerID via the API we should be able to set it to Blocked too and would be a whole lot easier and prevents any problems with that 3 step process.

Thanks!
Photo of Lee

Lee

  • 520 Points 500 badge 2x thumb

Posted 3 months ago

  • 1
Photo of John Wang

John Wang, Official Rep

  • 4,798 Points 4k badge 2x thumb
Hi Lee, thanks for this feedback. We'll take this as a feature request.

From your post, I'm curious about what you are currently doing. Are you:
  • having your app automate the process by set the CallerID to Blocked, RingOut and set back, all via API, or
  • having the user manually dial *67 and then the number
Just wondering if your users are actually dialing *67 or if you have implemented the 3 API call process.
(Edited)
Photo of Lee

Lee

  • 520 Points 500 badge 2x thumb
Hi John,

Thanks for taking it as a feature request.

Currently we instruct our employees to use *67 when needed but would like to use the Ring-Out to prevent mistakes when dialing manually.

Obviously it would take time to develop the 3 step process on our side instead of just passing "Blocked" or a flag for blocked that would just take minutes to update on our side. As I have other priorities this is being shelved until I have time (so never! :P) or you implement.
(Edited)