Blacklisting and Free version limitations confirmation

[Luke_IT]

Hi,
we've recently registered from the free 10 user SMB version and using the available Android and Windows clients all works fine. When I tried however to add a 3rd party SIP client for Windows (MicroSIP) and attempted to login I was getting unauthorized and after 4 attempts I found my static IP got blacklisted (the 3CX app reported this and could no longer login to the admin portal). I logged in from another connection and verified that in the logs there was a rejection due to "Block WAN requests is ON" from the client. Is using 3rd party SIP clients not allowed in the free version or is it just becuase of the repeated attempts and Block WAN requests that is enabled (I couldn't find an exact reference)?
I believe by reading from related posts that if I wait 24 hours from the last rejected login attempt the blacklisting should expire automatically, correct? As I have the 3CX app on my phone and it is running in the background, when my phone gets reconnected to the wifi network using the static blacklisted IP thus attempting to reconnect with the PABX, will this trigger and reset the blacklisting expiration timer for another 24 hours?

Thanks for the feedback!

 

[Evolute IT]

The expiration is indeed 24h for the blacklisted IP.

No, the repeated connections don't "reset" that timer. It will unblock automatically after 24h still.

Yes, by default "Block non-tunnel connections" is enabled so using 3rd-party softphones would cause this as they do not use the 3CX Tunnel like the 3CX App does. You will need to uncheck that to use it.

 

[leejor]

I assume that for the extension you are using, you've turned off the block non-tunnel access option.
I have not used a third party SIP client with Version 20, only some older versions, but would have assumed it would be no different than manually provisioning a "non-supported" SIP device, in that it should work, but I may be wrong.

 

[Luke_IT]

Thanks for the replies and clarifications. Unfortunately I only noticed the "Block remote non tunnel connections" *after* I was blocked while investigating the error. I was not aware of the default tunnel mode the 3CX software clients use (I have setup a few on prem asterisk/Freepbx combo installs but never used tunnels on the same LAN as the PBX was never exposed to the outside network apart from the Trunks in some cases, in other I would use Patton voice gateways over E1 always internally or at max S2S VPNs for branch offices).

I'll wait and hope that by tomorrow the blocked IP is cleared!

Cheers