Solved What is main security embedded features in 3CX to protect "ghost calls" hack and preventive measure.

[camtec]

Dear All,
Beside what we could see in the 3CX in the security menu of Management Console. Our customer is interesting in knowing what the main feature or setting to protect such "ghost calls" hacking and preventive measure in 3CX.

Thank you for your info and explanation.

Regards,
Ney

 

[leejor]

Many ghost calls are Direct SIP calls to a set, and do not go though 3CX. To prevent these requires you configure a firewall. In some cases, certain brands of phone have has issues in the past, much of which has been fixed with updated firmware. 3CX can be set to allow Direct SIP calls to the PBX itself, the Activity Log will show if this is the case. 3CX does a decent job of blocking registration and call attempts from unauthorized sources, but, it is not a firewall. Your own separate firewall, is the best defense against any intrusion.

 

[camtec]

Dear Leejor,
Much thanks for your prompt feedback. That mean as known experience, this can be happen on phones for which firmware is not keep update to date or firmware release is not rare to have its released. My customer just have SIT Trunk integrated to 3CX (they have SiP Peering and SIP account (Telco provider provide account id as mobile number and password to configure/set in 3CX).

We have deployed 3CX on Linode by our own since in my country 3CX hosted by 3CX vendor is not in market.

 

[cobaltit]

Ghost calls and hacking are two different things. Ghost calls are typically a combination of a poor firewall and a poor configuration on the handsets. Most handsets, and certainly 3CX supported handsets provisioned with 3CX templates are set to ignore SIP traffic not coming from 3CX. As far as what base security measures 3CX has implemented and what you can do, please refer to this article:

https://www.3cx.com/docs/voip-security/

 

[camtec]

Thank so much, Cobaltit for the info/link and explanation.

 

[ChrisC_3CX]

Seeing as this has been answered I'll be closing this thread.