Solved 3CX Windows client on terminalserver settings (audio settings)

[bit101]

Hi togehter,

we use the 3CX Windows desktop client on Windows 2012R2 terminalserver. Problem is that if we change settings by audio options and click on 3cx app close,
the settings are stored only as long as the user is within the rdp session. If he logged out the rdp session und log in again, the audio settings are back again to Primary Sound Driver".

How is it possible to store that permanently?

regards, beon

 

[VasilisV_3CX]

Hi @beon,

To confirm, you're connecting to a machine via RDP, then you change the audio settings in the 3CX Windows Client and click ok. Once you close the Windows App and open it, is the setting saved?

Now you close your RDP connection to the machine, and when reconnecting, it no longer has the audio settings you previously saved in the 3CX Windows Client?

 

[bit101]

Hi @VasilisV_3CX,

yes i agress, thats how it is. What i have see is that within the 3CXPhone.xml the GUID of <SpeakerDeviceGuid></SpeakerDeviceGuid> and <RingingDeviceGuid></RingingDeviceGuid> counts up by one if i reconnect (login) into RDP session again. As you can see, now we have {3.0.1.00000004}.{......}. When i reconnect to RDP again we have {3.0.1.00000005}. Thats the reason why it change the Audio settings.
Is there a solution to take always the same GUID?

 

[bit101]

After further investigation we could see that the device GUID in Windows for remote audio counts up by one after each fresh login in RDP session. As result the last value in 3CXPhone.xml is wrong in the new session so that the values are switch back in audio options. Is this a new problem?

 

[NickD_3CX]

After further investigation we could see that the device GUID in Windows for remote audio counts up by one after each fresh login in RDP session. As result the last value in 3CXPhone.xml is wrong in the new session so that the values are switch back in audio options. Is this a new problem?

3CX expects the device ID to remain the same, so from a 3CX software perspective, no.

Also at this point I feel I should point out that using any 3CX App in Softclient mode (in CTI mode it's fine) via Terminal Server/RDS is not recommend because audio quality can become degraded.

Not saying that it doesn't work, just not recommended.

 

[bit101]

Hi @NickD_3CX ,

yes we figured out this yesterday. Problem is that Windows change (sadly) the device ID after every Login. The old ID is within the 3CXPhone.xml and thats the reason for choosing "Remoteaudio" every single login.
Quick Workaround is not to logout but to disconnect. Advanced Workaround would be a C# script:
1.) read the actual device ID
2.) set the new device ID in 3CXPhone.xml
3.) start 3CX Windows client

PS: Audio quality is very good! No problems at all

regards,
beon

 

[VasilisV_3CX]

Great to hear that you managed to solve the issue @beon! If you require any further assistance, feel free to open a new thread!