sip trunks blacklisted https://1577.3cx.cloud/

[melbourne]

Hi,
A customer on a free version 3CX SIP trunks have been blacklisted and not registering.
how can I whitelist this customer?

 

[melbourne]

I believe 3CX is blocking our ISP 203.57.203.65

 

[NikosT_3CX]

@melbourne as I can see this is the second time this happens ( same was yerstarday ).
As I can see your server 's ip with " User-Agent: AU PBX " has been blacklisted due to too many failed authentications.
This User Agent is not from the Supported Provider I believe.
Do you whitelabel Vocus and use your own Trunk infrastructure ?

 

[melbourne]

Yes

 

[melbourne]

I use Vocus trunks but I am a reseller for them "White label"

 

[bitn2]

That information would have been helpful back in the first thread...

 

[paulodagraca]

Hello,

At the moment is seems the IP is clear (again):


Paulo

 

[melbourne]

The trunk is still not registering though

 

[bitn2]

Its not the IP that is blacklisted its the user agent as @NikosT_3CX already mentioned.

 

[melbourne]

Is this fixed by 3CX or is it something I need to arrange?

 

[bitn2]

As this isnt supported i dont know 3cx will do there anything. But maybe @NikosT_3CX clarify this.

 

[NikosT_3CX]

@melbourne the ip has been removed from this machine.
Please note though that these machines are meant to be used for tested and supported providers with the
pre-setup Registrar FQDNs.
It is highly recommended to not modify these in order to avoid issues like the one you are facing.

 

[melbourne]

Hello, thank you for sorting the issue. Can you advise what exactly was done that caused this problem.
Thanks

 

[NikosT_3CX]

@melbourne this SIP Server has been blocked due to may failed authentication requests towards the PBX.
This is something that has to be checked on your side and ensure that this will not happen again.
The PBX will blacklist anything that sends invalid requests based on the settings that are set on the Anti-Hacking section.