Calls fail in Chromium (v15.5 server)

[AlecM]

Starting with Chromium Version 83.0.4103.116 (RPM Fusion Build) (64-bit), everything looks ok until you try a call (either out-bound or received), when the client page will crash with browser error "256".

Browser help link (which connects to Chrome help rather than being Chromium-specific) indicates trying to clear browser cache/history, etc, which I have tried (using the 4 weeks option).

I only have 2 extensions in this particular browser, and tried disabling both of them - same problem. I then also tried a full Settings Reset. No good still.

The client worked perfectly in the previous version of Chromium - it's only since the last update (week or so ago?) that this crashing started.

Using "regular" Chrome (Version 83.0.4103.116 (Official Build) (64-bit)) is still OK at the moment. Without this working I would be without any ability to use 3CX remotely (can't currently use Android app as this insists on v.16 and we are still on v15.5 for a while longer).

I'm concerned that the next Chrome upgrade may also break calls the same way Chromium now does - leaving me totally without 3CX regular calls ability.

I would also like to see Firefox working 100% - but that has issues with various features in the onscreen active-call panel not operating - e.g. in-call Keypad button and transfer buttons simply locked off, so can't use it, even for voicemail - so using this for any extension dialling/forwarding or similar dial-tone based menu's is out. Shame for such a widely-used/popular browser that also supports WebRTC in other areas.

Has anyone else had similar issues? Or can offer a fix other than relying on one specific browser only (or updating server to v16, if that even makes a difference)?

[We will move to v16 at some point, but timing of doing this when everyone is remote and relying on it is difficult.]

TIA,
Alec

 

[JohnS_3CX]

Hi Alec,

V15.5 has been deprecated now, there is no support for that system and the webclient was in Beta even back then..



The time to move to V16 is now https://www.3cx.com/docs/upgrading-pbx-v16/

 

[AlecM]

Hi Alec,

V15.5 has been deprecated now, there is no support for that system and the webclient was in Beta even back then..
View attachment 16937


The time to move to V16 is now https://www.3cx.com/docs/upgrading-pbx-v16/

Yes, thanks for the response (which didn't clarify if v16 would fix this issue in Chromium or not); as I noted, the server migration is something we plan to do when I can.

Thanks for the link, but we won't be doing an in-place upgrade because our's is still running on a W2008R2 server (also planned for eventual replacement) - which is blocked from getting the v.16 upgrade. So, without a newer version of Windows Server, I'm looking to migrate it both from 15.5 up to 16 and to the Debian version (we already run several Linux servers). This consideration, plus I am on reduced hours during the pandemic, and doing everything remotely with limited resources (but we want to retain on-premise deployment) is just a big ask on my time.

Simply pointing to an upgrade but not clarifying if that upgrade will actually fix the issue is not that helpful and actually quite frustrating what with everything else I have to juggle. (Even though I understand the reason behind the guidance to that path).

 

[JohnS_3CX]

Well understood, and if you need any help when the time comes we can help answer any questions you have to make the transition as smooth as possible. If Chrome works for you now, you should stick to it so you can at least work until you are able to upgrade. Without going too much into it, I'm sure you know what Chromium is and why it should not be used for production environments, however if you are really keen on using it perhaps you can go for a newer build in the V86 series