Skip to main content
Question

System won't acknowledge number press


I'm trying to figure out what is causing this problem. When various of the phone team are taking calls from the callers through the call queue and have the calls forwarded to their cell phone, a call comes in and they are prompted to "press 1" to accept. This all worked great until about 2 weeks ago and now maybe about 1 out of 4 calls the system won't acknowledge that they pressed a number. Some are iPhone's and some are Androids. Thought maybe changing the DTMF tones to long instead of short might help but can't find that setting on my Galaxy S8....

7 replies

Mary-Community_Moderator
Community Manager
Forum|alt.badge.img

Hi! Try toggling the Press 1 to accept call queue settings in the web portal.


Thanks for that but these calls are coming through the call queue and it's not possible to toggle that one off. Not just that we still need those prompts... that's how we know if it's a personal call or a call coming from the queue. Any other suggestions?


Thanks for that information. That sounds like a good idea, but I can't remove the announcement for calls from the Call Queue thus we still need to press a number to receive the call. Could you make that setting available for us? For some reason RingCentral's system isn't recognizing the DTMF tones.


  • New Participant
  • 2 replies
  • January 19, 2024

I've encountered this fairly frequently, on and off, for a while now. It's very frustrating.


  • New Participant
  • 2 replies
  • October 23, 2024

Same - any word on how to correct this?


  • Employee
  • 18 replies
  • October 28, 2024

The option to disable the “Press 1” prompt in call queue calls is currently limited by existing feature settings. However, this has been raised as a feature request, and you can track its progress or add your support here: https://ideas.ringcentral.com/forums/958493-phone-messaging/suggestions/48022379-incoming-call-announcement-press-1-disable-for.

Thank you for your feedback, as it helps us prioritize future improvements!

 


Hey Guys, I been struggling with this as well for a while, support has really not been much help but I finally got it working.   It seems like for some reason a “user with extensions” can get corrupted over time and the press one some how stops working.   The fix for me was to make a new “User with extension” basically redoing the one that does not work and relinking it on the IVR menu, that seems to do the trick.  PS: I thought it was our old phones, so we got new phones, then I figured it was an at&t problem so we switched carriers, it was the corrupted user after all 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings