V18 Desktop App does not open .3cxconfig file properly

[ITSP]

Hi,

When we were in V16 (on-prem), we saved 2 3cxconfig files on a user's desktop called ExtensionA and ExtensionB. If we open ExtensionA's .3cxconfig file using the Windows client, it logs ExtensionA in and changes the status to Available. Same when we do it for ExtensionB's .3cxconfig file, it logs ExtensionB in.

Now that we've moved to V18, when we use the Desktop App to open ExtensionA's .3cxconfig file, it logs ExtensionB in. When we open ExtensionB's .3cxconfig file, it logs ExtensionB in as expected.

What could be causing this?

 

[SweetAction]

I wasn't aware that the 3cx config file worked with the desktop app, that interesting.

Take a look at this post - understand that updating your shortcuts to call the QRCode URL will likely be the fix.

Technically you could use the same mechanism the browser uses to launch the app.
What the browser does is invoke the EXE and pass as argument the HTTP/S link that the QR code resolves to.

To be more precise, you could load a config like this:

3CXDesktopApp.exe tcx+app:<HTTP/S link of QR code>

View attachment 23773

I suppose you could get the QR codes of the users from the Management Console and via GPO, also have a CMD script run on startup doing this.

I haven't tried it and this was not the intended way of provisioning the Desktop App, but you could give it a shot.

Super unsupported as you can guess.

 

[SteveITS]

Now that we've moved to V18, when we use the Desktop App to open ExtensionA's .3cxconfig file, it logs ExtensionB in. When we open ExtensionB's .3cxconfig file, it logs ExtensionB in as expected.

The Desktop App doesn't support more than one account. (https://www.3cx.com/community/threads/3cx-v18-client-with-more-profiles.115231/post-533834) It's been brought up several times here since the release of v18. The advice I've seen from 3CX is to use different Windows profiles, or sign into the web client.

Interesting on v16 app by the way. I know if two accounts were provisioned one could pretty easily switch between them in the app. I'd guess opening the config file reprovisions it each time?

 

[ITSP]

Thank you for confirming our suspicion.

We implemented this workaround because we needed to find a way to trigger a specific message to be played when the school is on lockdown. We routed incoming calls to an extension that auto-forwards to a digital receptionist number when its status is set to Available. The digital receptionist would simply play the message and hang up. If the extension is set to not available or not registered, it then forwards to the "normal" digital receptionist.

Does anyone have any alternative for playing a lockdown message? For now, we're keeping the V16 client installed on the devices of the people who are authorized to trigger the lockdown. As far as we can tell, the V16 client still triggers the message.

 

[ITSP]

@SweetAction thank you for that. We will give it a try. No worries on being unsupported. Our existing process is the same so no loss there.

 

[ITSP]

OK, have just tried it with the Desktop App originally provisioned for me (extension 001) and then I clicked on the shortcut that launched the Desktop App with the QR code link. The Desktop App window pops up, shows ME as logged in for a split second, then shows a 401 unauthorized error.