Solved 3CX Windows App - Auto Dialling on Resume from Hibernation

[TitleRequired]

Posting this more for observation than anything else. I expect it is a symptom of something amiss on my laptop rather than the app.

On several occasions now, when resuming from hibernation the 3CX Windows App has auto dialled a number.

So far they have been internal contacts, and interestingly were not the last number i had dialled, but i had dialled the number recently.

For clarification, lets say at 3pm I dialled 233. Then dialled some external numbers and at 5pm put my computer into hibernation. At 7am the next morning I turn on my laptop, it goes to the login screen and it dials 233.

I use a USB headset, headset integration is disabled in the App settings.

App Version is 18.3.33.0
Windows 10 Enterprise 19043.1165
Headset Microsoft Life Chat LX-6000

 

[TitleRequired]

Ok, I have a PSR of this happening now.

It also happened just a second ago when my wifi dropped and i reconnected.

 

[TiagoC]

I have also experienced this across 3 different 3CX instances. Always seem to be 1 user who repeatedly dials another internal user through out the day. Re-provisioing te windows client or resetting the credentials made no difference however, restarting the PC seems to temporarily resolve this.

This has happened to my own computer which was helpful as I was able to experience this first hand.

Only started happenig since V18 upgrades with the new Windows Client.

 

[VasilisV_3CX]

Hi Guys,

I'd like to ask you to do the following on the PC that is calling automatically.

In the Desktop App, press F12, it'll bring up the panel shown below.



Navigate to Local Storage and add the following two lines:



Next, click Console, then click the delete button (the black circle with strikethrough):



Once empty, close the interface, and restart the PC as you normally would. After reboot, the call should happen automatically. Open the interface using F12 and paste whatever you have under the "Console" section into a notepad and send it to me via PM sharing site.

Also:

Do you have any headset Integration. If yes, what is the configuration, what is the headset?

Have you tried to replicate this issue on different PC?

 

[TitleRequired]

Sorry for delay in responding - been away from work.

I have setup the logging now and restart, so will wait to see what happens.

I suppose you could say we have tried to replicate it by virtue of having the app on other machines!

 

[VasilisV_3CX]

Sure thing @TitleRequired,

Can you also enable verbose logging on your PBX and once the call completes, generate Support Info and attach it to me in a PM? I'll need the time of the call as well as who was called and from whom.

So I'll need the logs request above and the generated support info.

 

[TitleRequired]

The problem is, it isn't every time. So I'm not sure we can run in verbose logging on the off chance it catches a call.

 

[VasilisV_3CX]

Hi @TitleRequired,

If you have enough disk space it should be fine for a while, especially if you don't have the "Backup Logs" option enabled.

All logs together, because they recycle, shouldn't exceed 300MB.

 

[TitleRequired]

No further incidents of auto dialling so far, i still have logging enabled so if it does happen hopefully it will be caught.

 

[VasilisV_3CX]

Thanks for the update @TitleRequired, I'll leave this open until it automatically closes. If anything happens until then, let me know.

 

[Charles_3CX]

Can you let us also know which headset you have on the desktop app that is making these calls automatically, please?

 

[NickD_3CX]

Hi @TitleRequired @Heine @TiagoC ,

I will send you a PM soon about this.

 

[TitleRequired]

I have a Microsoft Life Chat LX6000 USB. No headset integration enabled.

 

[NickD_3CX]

Hello everyone!

We have found a way to replicate this in-house and we believe to have found the root cause.
You can remove any debugging you may have enabled and we plan on providing a fix for this along with V18 U2.

 

[TitleRequired]

Amazing! Can you share what the cause is, or how you managed to replicate it?

 

[NickD_3CX]

Amazing! Can you share what the cause is, or how you managed to replicate it?

I don't know the exact details unfortunately. If I do find out, I will let you know.

 

[ChrisC_3CX]

For anyone facing this issue, we've just release v18 U2 so I urge you to upgrade the PBX and try it out.

Let us know how it goes:

Blog Post: https://www.3cx.com/blog/releases/v18-update2/