Hi Sven,
We've had similar issues with RTC connections but not due to firmware upgrade, rather we made a significant firewall change that shut down our ability to do these connections.
It may be a bit of a long shot, but if there are any firewalls between your agents and the Edge devices, check that they handle STUN processing correctly.
Otherwise, please be sure to let us all know if the firmware backout works. It's not unheard-of for regressions to appear in Edge software updates - we've had 4 show-stoppers in the past 18 months ourselves that we caught because we manually test all upgrades in the dead of night ourselves - so whatever you do be sure to test, test, test after any upgrade (or downgrade!).
------------------------------
Christian Legg
MyBudget
------------------------------
Original Message:
Sent: 01-20-2019 11:22
From: Sven Schiller
Subject: Experiencing errors with making/receiving WebRTC calls
Thanks Eric. We use edges that have a their own direct internet IP address.
The only thing that changed from Friday is the new firmware on the edges. However, the release notes don't mention changes to the WebRTC transport (I recall a change a couple of releases back).
I think I will revert to prior firmware and see if that addresses the issue.
Original Message------
This typically shows routing issues between the PureCloud edge and the webRTC client.
From your post I understand that you have PureCloud edges at your location.
------------------------------
Eric Dauphinais
Quovim C3 (9264-2354 Quebec Inc.)
Original Message:
Sent: 01-19-2019 14:36
From: Sven Schiller
Subject: Experiencing errors with making/receiving WebRTC calls
Starting today, some of our agents are sometimes seeing an error in the Windows PureCloud app when receiving / making calls. The call goes to another agent / fails. The error reads "Call Error - error.ininedgecontrol.connection.station.webrtc.iceNegotiation".
We are using WebRTC with persistent connections. After restarting the PureCloud app, one or more calls can be handled, then the issue reappears. Restarting the edges or agent computers had no effect. Our edges updated to the latest firmware last night, so this may be related.
I already opened a support case, but has anyone seen this error before and what may be the cause?
#Telephony
------------------------------
Sven Schiller
Kognitiv
------------------------------