Installing 3cx

#1 I'm a user, not an admin. I can't tell you the version as the client won't start anymore, but the executable is called "3CXWin8Phone.exe" and it was installed recently (approx. in May).I suspect it has something to do with the old problem of Visual C++ redistributables, as it happened around the time I did an update to Visual Studio. The following redistributables are installed on my system: 2005, 2005 (x64), 2012 (x64), 2012 (x86), 2013 (x64 - 12.0.40660), 2013 (x86 - 12.0.30501), 2013 (x86 - 12.0.40660), 2015-2019 (x64 - 14.27.29016), 2015-2019 (x86 - 14.27.29016).There is no 2015. I found a 2015 at it is version 14.0.23026. When I try to install it, I get an error 0x80070666 (another version is already installed).Any advice?Thanks,Soren #2 Hi Soren,The Windows client will install its own redistributables during installation, but it's a bit difficult to know what Visual Studio may have changed.By default, when installing the latest 3CX client as of today, you will see it installing:Microsoft Visual C++ 2015-2019Redistributable (x86) - 14.24.28127Hope this helps #3 FWIW it looks as if Microsoft are pushing a newer version of the 2015-2019 redistributable and you've listed the newer one.Out of curiosity I tried installing 3CX client ther updating the VCC redistributable and it didn't break it for me so it doesn't look like "DLL hell", but it might still be worth trying uninstalling the 2015-2019 (x86 - 14.27.29016) one, reinstalling 3CX and then reinstalling the redistributable.When you say "user not admin" you mean for 3CX don't you not Windows? #4 It's working at the moment again for some reason. Thanks for your reply. #5 Glad to hear Soren, we will mark this as solved then

#1 Have 3CX client running works perfectly inside and outside of the office (using both direct-SIP and the tunnel). When users connect via VPN (split tunnel) the 3CX client has major issues:Setup:3CX server - no 3CX SBC.Here's the logical flowIn the office (No VPN): 3CX client -> pbx.domain.com -> 3CX Server Internal IPNo issues to report - everything works fine.Out of the office (No VPN):3CX client -> pbx.domain.com -> External IP -> NAT -> 3CX Server Internal IPNo issues to report - everything works fine.Out of the office via tunnel (No VPN)3CX client -> tunnel encapsulation -> pbx.domain.com -> External IP -> tunnel decapsulation -> 3CX server Internal IPNo issues to report - everything works fine.Out of the office (VPN):3CX client -> Cisco VPN encapsultation -> Internet -> Cisco VPN Concentrator -> pbx.domain.com ->3CX Server Internal IPThe PCAP shows that once encapsulated in the Cisco VPN, it resolves the internal IP correctly and registers with no issues. All calls setup, but no media passes because the contact IP is the physical LAN interface address of the computer not the tunnel virtual interface. I have verified that the interface metric is correct and windows does route split traffic correctly. It's something inside of the 3CX client that is incorrectly sending the wrong contact IP for RTP.Looking for help on this. #2 I just reproduced this using OpenVPN on my Windows 8.1 PC.I connected to my office and the 3CX Phone was using the correct interface to transfer both SIP and RDP via the OpenVPN tunnel. So here with OpenVPN it's working.Normally Cisco uses IPSec tunnels and not all of them have a local virtual IF. Can you see your IPSec IF in "Control Panel\Network and Internet\Network Connections"?If so go to advanced and move the Cisco VPN adapter to the top. Does that make a difference?If you don't have a virtual IF for your VPN I'm not sure if that will work as with VoIP it's more than normal routing since the client and the server need to be aware of their adresses as they are submitted during 5060 communication for them being able to create a working RDP stream in both directions.

GHDSK Customer Basic Certified #1 Hi,we want to change from "3CX Phone for Windows App" to the new "3CX Desktop App". So far everything is working, but our biggest problem ist, that we used the command line (C:\ProgramData\3CXPhone for Windows\PhoneApp\CallTriggerCmd.exe +parameters) in the past to dial from some specual windows programs. This always worked for us.With the new "3CX Desktop App" we were not able to find any information how to do this.Has anyone found a solution for this?Thanks,Christian. #2 It is a feature exclusive to 3CX Phone for Windows. However, it is possible to do with our REST API. MakeCall is one of the free APIs you can use without a license. #3 How to integrate your REST API? Do you have any HOW TO? #4 We have documentation built into the Relay. Just install our Relay on your 3CX server and select the "API" link in the left-hand side panel. You will see there are ... I do not know exactly... hundreds of APIs we have developed and we are adding more weekly. One of several variations on MakeCall is: "100", "number_to": "8016424655"} #5 Thank you. Unfortunately my 3CX instance is hosted by 3CX so as I understand I can't install your Relay there, correct? #6 That is correct. When hosting your 3CX server AT 3CX, they do not support CFD applications, access to CDR files, or the installation of 3rd party tools. You would need to move your 3CX server to a hosting provider that does permit 3rd party tools.