![fonality hud 3.6 fonality hud 3.6](https://docplayer.net/docs-images/43/12808549/images/page_18.jpg)
RingCentral does not advertise or promote itself as a cell center system. What you've described is the right feature set for a call center. Connect with perhaps it's not a bug, but at minimum, it's poor product design based on how RingCentral advertises themselves. If you are not a member of a call queue and are receiving calls you can't ignore or decline to your direct number, it is a different issue and is not expected behavior. Product is aware of the ask that when all agents reject a queue call it is sent to voicemail.Īdd your voice and vote to the Ideas Portal and we'll continue to surface this with the product team. Or you can explore Ring Groups - calls will be sent to voicemail if the call has been ignored by all the agents associated with that extension.
![fonality hud 3.6 fonality hud 3.6](https://i.ytimg.com/vi/nYyzS0x2vT4/hqdefault.jpg)
You have two options - if you want to keep the call queue set up, toggle your status to unavailable and you will not receive queue calls when you are busy. If all agents are rejecting the call, the call will continue to attempt to get an available agent until someone picks up or the customer disconnects. Ignore works best when call distribution is rotating or sequential and there is at least one other available agent. The issue here is that the agent remains available but is asking to ignore the call - if they change their status to unavailable they will not get queue calls. The ignore queue call scenario you are describing is not a bug if either the queue is using simultaneous distribution or the ignoring agent is the only available member in the queue. This is how Call Queues operate and is operating as designed - we have confirmed this with the product manager for this feature. Stuart I understand your frustration, but is correct. How many times does this have to be reported? We used to have Fonality VOIP phones which is a pretty crappy system and it didn't have this same problem. Here is another ticket reporting the same thing, from 2015:Īnd again in 2016 with TWO different tickets:Īnd again in 2018, on the iOS app, but same issue: When is RC going to take this issue serious? How is this not fixed after being reported as a problem a year ago? can you guys please combine these tickets below into the same issue? This has also been a reported "problem" for 6 years now. It's not a "feature", it's a design flaw. It was super annoying to have calls repeatedly interrupt me over and over while I was on another call on my mobile phone. I had to remove myself PERMANENTLY from our Support Queue for this exact reason. If they all hit reject then send it to voicemail. If we hit Reject it should send that call to Voicemail or if it's from a Queue (Call Center Blast, or Round Robin) then it should just ring to the other folks on the Queue. !MESSAGE Exception launching the Eclipse Platform:Īt .(EclipseStarter.java:186)Īny ideas on what I can try next? I'm stumped.I think this is absurd as well. : Exception in .() of bundle system.bundle.Īt .(StartLevelManager.java:557) : Exception in .() of bundle system.bundle.Īt .(BundleContextImpl.java:1014)Īt .(BundleContextImpl.java:970)Īt .(StartLevelManager.java:549)Īt .(StartLevelManager.java:484)Īt .(StartLevelManager.java:275)Īt .(StartLevelManager.java:245)Īt .(SystemBundle.java:155)Īt .(Framework.java:503)Īt .(OSGi.java:51)Īt .(EclipseStarter.java:289)Īt .(EclipseStarter.java:173)Īt 0(Native Method)Īt (Unknown Source)Īt (Unknown Source)Īt .invoke(Unknown Source)Īt .Main.invokeFramework(Main.java:334)Īt .Main.basicRun(Main.java:278)Īt .n(Main.java:973)Īt .Main.main(Main.java:948)Ĭaused by: Īt .(BaseStorage.java:654)Īt .(BaseStorage.java:634)Īt .BaseAdaptor.getPlatformAdmin(BaseAdaptor.java:385)Īt .(EclipseAdaptorHook.java:80)Īt .ameworkStart(BaseAdaptor.java:260)Īt .(SystemBundleActivator.java:55)Īt .$2.run(BundleContextImpl.java:995)Īt (Native Method)Īt .(BundleContextImpl.java:989) I have removed Java, removed HUD, cleaned the registry, etc. I know after reviewing the log there is some kind of Java issue. The XXXXXX part changes each time I run it. The error that pops up is:Ĭ:\Users\Public\hud.workspace\program\configuration\XXXXXXXXXXXXXXXXXX.log Fonality HUD stopped working and they have been unable to fix it. Inherited a computer from a prior employee.