V18 to v20 problems

Hayward-i1

SOHO User
Joined
Oct 4, 2023
Messages
67
Reaction score
18
Hi

I originally posted a comment on the PBX forum but think I now know enough to say there is something wrong with the web app

In summary after what appeared to be a successful test, I upgraded our live switch board to v20 (from v18). Note I did not upgrade the desktop web clients as I was told these should work with both v18 and v20 and I wanted to minimise the change.

Quickly I started getting reports that headset users were not being heard by the other party. Fortunately all these users had handsets and these were working so I decided to wait until the end of the day to find a solution.

My first thought went to the firewall thinking maybe v20 used different ports, but no. Then I wondered if someone had changed a firewall setting. So I swapped out the whole router with a known good router configuration. But alas the problem remained.

Scratching my head I then thought, let's try the v20 desktop client. But I didn't want to tinker with a live machine, so I pulled it another desktop (test machine) with a known good configuration intending to upgrade the client to v20. But when the desktop booted, I noticed it was using the v16 windows client and I thought I wonder.... And much to my surprise it worked perfectly.... This really did surprise me.

After a little thought I went back to my desktop and thought let's just try the v20 windows client so I removed the the web client and proceeded to download and install the v20 desktop client. Nope, same problem the other end can not hear you...

Further head scratching and I thought what if I install the v16 desktop client on my desktop. Do you think I could find a copy anywhere? No.

Then I realised that the old v18 PBX was still installed on a now switched off machine awaiting decommissioning. So I thought, worth a try. Sure enough booted v18 and I could download and configure the v16 desktop client.

Switch off v18 again and rebooted the v20 server. Boom, the v16 desktop client works with v20 and is fully functional.

I know this is long winded, but can anyone tell me why the v16 desktop client is happily working with v20 but the web app and the v20 windows app is not working?

Fyi, the microphone was/is allowed for 3cx under privacy, I thought of that!
 

Forum statistics

Threads
112,327
Messages
591,904
Members
165,483
Latest member
AshleyStokes