3cx

#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.

The 3CX VoIP Desktop Application has been compromised to deliver malware via legitimate 3CX updates. Huntress has been investigating this incident and working to validate and assess the current supply chain threat to the security community.UPDATE #1 - 3/30/23 @ 2pm ET: Added a PowerShell script that can be used to check locations/versions of 3CX and run against the hashes to see if they're bad to be run in an RMM.At 11:40 AM EDT on March 29, 2023, Huntress received an inbound support request from a partner, concerned with a new advisory and discussion on Reddit shared just 30 minutes prior. CrowdStrike was first to sound the alarm on a breaking incident: 3CX VoIP software installations were compromised, delivering malware to hosts running the 3CX desktop app. Huntress immediately added increased monitoring for malicious activity related to the 3CX application, while working to validate this attack vector so that we could provide as much information as possible to the community. From 3CX’s recently released notification, the currently known affected 3CX DesktopApp versions are 18.12.407 and 18.12.416 for Windows and 18.11.1213, 18.12.402, 18.12.407 and 18.12.416 for Mac.ImpactAt the time of writing, Shodan reports there are 242,519 publicly exposed 3CX phone management systems.3CX claims to have over 600,000 customers, and it goes without saying, this has the potential to be a massive supply chain attack, likened well enough to the SolarWinds incident or the Kaseya VSA ransomware attack in years past.Within our partner base, Huntress has sent out 2,783 incident reports where