Common Mistakes Which Lead to Call Fraud

[Pierre_3CX]

Although rare, we’ve seen cases of call fraud where several misconfigurations led to the unnecessary exposure and compromise of 3CX. In this blog post we’re going to highlight some common mistakes we’ve noticed that lead to call fraud and what you can do to avoid them.

What is a Call Fraud?​

Simply put, call fraud occurs w...

Continue reading the Original Blog Post.

 

[complex1]

To lift the security to a much higher level, please check all the 3CX templates (especially Yealink) and make sure not only the admin password is set, but also the user password.

 

[cobaltit]

Some questions about the global blacklist:

• How does one denote blacklist entries inherited from the global blacklist vs ones learned locally?
• Do global entries inherit the 'Blacklist time interval' at the time they are sync'd?
• When does the sync happen?

 

[Pierre_3CX]

Hello cobaltit,
To answer your questions:
- global blacklist entries are not shown in management console, they would appear in bin log viewer only.

From the bin log you could see also events related to packet dropped due to global blacklist entry as below:
25/02/2019 11:59:58:031 | [IPBL] Packet from banned IP/range: ip = 185.53.88.2; Comment: Blacklisted by 3CX

- the blacklist duration is permanent with an expiry set in 400 years, it does not take account of the blacklist interval.

- a sync occurs daily early morning (between 0am to 7am) at a random time

 

[Pierre_3CX]

Hello complea,
As I see in all v16 yealink templates the user account gets same password as admin password so it's not left empty or default.

 

[dalton1]

Great news on the Global IP Blacklist! I was mulling that we could use a feature like this. On V15 we have to do a lot of manual housekeeping to keep our own Global list across our customers PBX's.