Since last update, Windows app crashed and do not start any more

[ThomasF]

Very last update 5 (final) has been done yesterday night on our 3CX Instance, as well as for Windows Apps. It has been working a few hours, and then, even after a re-install, 3CX process is running, but no app available.

We are in production and right now, I seem to be the only one to be impacted, but I'm afraid this is because I'm the most up to date...

Do you think I've got anything to do?

Of course I already tried reinstall, Windows 8 compatibility mode, run as an admin etc...

 

[ThomasF]

Restart computer failed solving the problem, reinstalling also.

After restart the instance through https://customer.3cx.com/prm/myinstances.aspx , windows app finally restarted. Do not know if there is a link, but anyway I share the info.

Thread can be closed then.

 

[ThomasF]

Problem appears again. No matter what action I do, cannot start the Windows app (only see the process in the process list). Am I the only one for who this situation occurs?

 

[Metalsistem]

We are experiencing a issue after the upgrade to 16.0.5.611 on a professional license. The installation does have 238 active extensions, about 60 of them are currently using the windows desktop client (Client version 16.3.0.111). Several users have reported that 3cx Windows client is crashing about 2 seconds after a call is established. If you call a voicemail, as example, a short silent message is recorded on the target mailbox. The web client app is working. The affected clients are installed on Windows 10 1909 with all the Microsoft patches installed. I tried to uninstall and reinstall the 3cx Windows client but the issue is still here. I also tried to provision a different extension on a different user profile on the same computer; the app is still crashing. The windows user event log lists a "file open error" as crash reason, but I monitored the 3cx application with sysinternals and I dont'see any error on the open file action. I plan to do further checks after disabling the webcam. This is the last fragment of the 3cx log (the user is calling the extension 770):

To: <sip:[email protected];tag3cx=bcc442e4babc44c5bc49212618c2704d>;tag=dad22118
From: "REDACTED"<sip:[email protected]>;tag=8ef906e63171478ca19e0bf740939ceb
Call-ID: dd01c76862184222b2464bbabbdc0342
CSeq: 23812 INVITE
Session-Expires: 1800;refresher=uac
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 16.0.5.611 (611)
Content-Length: 305

v=0
o=3cxPS 25616031431000064 28355795296976897 IN IP4 10.11.24.11
s=3cxPS Audio call
c=IN IP4 10.11.24.11
t=0 0
m=audio 7868 RTP/AVP 120 96
a=rtpmap:120 opus/48000/2
a=fmtp:120 useinbandfec=1
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=sendrecv
m=video 0 RTP/AVP 31
c=IN IP4 127.0.0.1

--end msg--
[28.04.2020 00:40:35.802][26] 00:40:35.802 PjsuaCallbacks .....************ ON_CALL_STATE id = 0, state = 4 (CONNECTING) *************
[28.04.2020 00:40:35.802][26] 00:40:35.802 PjsuaCallbacks .....cause = 0 (), role = 0
[28.04.2020 00:40:35.802][26] 00:40:35.802 PjsuaCallbacks .....from call_info: cause = 200 (OK)
[28.04.2020 00:40:35.802][26] 00:40:35.802 pjsua_media.c .....Call 0: updating media..
[28.04.2020 00:40:35.802][26] 00:40:35.802 pjsua_aud.c ......Audio channel update..
[28.04.2020 00:40:35.943][36] 00:40:35.943 udp0ACE88C0 !Remote RTP address switched to 10.11.24.11:7868

 

[Metalsistem]

We have solved the issue. The affected users were using the opus audio codec. I added the G729 codec to the phone provisioning page of the affected users and put it as first in the codec list. The app is not crashing anymore.