ISSUE WITH JABRA EVOLVE 75 / 75e since realese 1.71
since the last update, on missed calls, the headsets receive a "call notification" making them "ring" without the ringer the 75's just flash but the 75e's don't stop vibrating until a new call is answered. Really annoying.
I have several installations with these headsets and it's really disturbing.
Can I have some feedback ?
(I have too some issues with call control with headset since beginning but not so annoying)
happy to know I am not alone.
Got trouble on all my installations with evolve - engage (we only sell Jabra for the moment)
(all seems to be ok in "audio call" mode but problem is with PBX call)
Got some other trouble with hang up when calling from OCE WebRTC
May I ask for your configuration ? do u have it working with other headsets on other customers ?
Yes, it's on PBX calling only.
The customers system is an oxo Connect R3.2 with webrtc.
The problem occurs when there is an incoming call on the RB anydevice user and he has a dyn routing to another user.
After the Dyn routing T1 is activated, the first RB anydevice user desktop application stops ringing but the Jabra headsets keepon vibrating. Sometimes it helps by shutting down the RB app but then it can happen that after restart the RB app doesn't responds anymore to new incoming Webrtc calls. So only solution is to desactivate the Anydevice user in the OXO and after a few seconds reactivate it.
This is a random behaviour, for almost all users.
On other customer sites I used Plantronic wireless headsets wiithout any problems so far.
Thanks for informations, my problem is similar but occur wether or not there is an Dyn routing.
I have the problem with NDI directly on the anydevice user on no answered call .
Got the same problem on 3 installations with Oxo Connect Evolution (integrated WebRTC) and Jabra headset (evolve 75 75e - engage 75) but only since the Rainbow 1.71 release apparently.
(The only installations I have with WebRTC)
Restarting Rainbow client corrects the problem (each time so far).
Hello Patrick :
I got today some new from ALE support if it can help you (I didn't try it for now):
1) An immediate temporary fix for this particular issue is to add a property to the settings file that prevents Rainbow from attempting to manage and synchronize USB devices with Rainbow calls.
In order to do so:
* Edit the settings file in this location with any text editor (e.g., notepad):% APPDATA% \ Alcatel-Lucent Enterprise \ Rainbow \ Settings
* add a comma and this line:
2) The "real" fix is to ensure correct management on the Desktop side of the Web Client events in the case of GW WebRTC calls and in all possible cases. We are currently studying this fix and will keep you informed as soon as possible.
Yes, I just experienced it also.
But at my customer it's not a big deal, since they use the mouse or keyboard to control and not the headset buttons.
For sure it's a loss for users working fully with the control on the headset, so let's hope R&D makes a fix soon.
Seems we are the only 2 using WebRTC and rainbow as "anydevice".
Since 1.73 no more "click to call" (default key F6). Each upgrade give me a lot of trouble.
Probably my last installation of Rainbow as soft phone next week, have to explain to my customer no RCC and no click 2 call.
Seems to be a good week.
Hello Ronald, here the same. Issues with Jabra and also dynamic routing from rainbow user to general level is not working. Sometimes it does sometimes not. It seems that oxo connect together with rainbow as anydevice user(softphone) is not a stable solution when talking about large users. In my case 80 users. I got and end date of my customer to prove it's ok if not I need to take it all back!
Frustrating is also when you try to follow the upgrades of the oxo eachtime we stumble into other issues together with Rainbow.
Fix for Click to call (have to read almost all posts to find informations : https://support.openrainbow.com/hc/en-us/community/posts/360009314219-Problems-With-the-new-Interface-Rainbow)
Iniciar sesión para dejar un comentario.