Block Wan Requests on

[jdi92]

Trying to register a phone, don't want to use an SBC, in the event logs it says Block Requests On. I turned off the Block remote non-tunnel connections for the user I'm trying to register the phone with, but it still doesn't register. The WAN ip gets blacklisted from too many failed authentications. Any suggestions?

 

[SteveITS]

Using an SBC or router phone is safest (encrypted) and by far easiest. You can create a custom template to use STUN but 3CX doesn't support this in v20. (and no I don't have instructions, sorry)

 

[Robert L.]

You can try whitelisting the phones IP on 3CX. That way the phones IP will not be blocked, and maybe it will provision.

 

[jdi92]

You can try whitelisting the phones IP on 3CX. That way the phones IP will not be blocked, and maybe it will provision.

I just whitelisted the IP and tested. It allows for me to not be blacklisted and I don't get locked out of the web console anymore, but the registers still fail and event log still points to Block WAN Requests ON.

Unchecking 'Block remote non-tunnel connections' appears to allow the phone to be put into a registered state.

Thank you for the help.

 

[BrynLoftus]

The behavior of this checkbox is a bit odd actually, its not consistent...

If its enabled, a handset can register through a standalone SBC but NOT as a router phone with an onboard SBC. The router phone SBC doesn't count as 3cx tunnel for some reason.

 

[KyriacosS_3CX]

If its enabled, a handset can register through a standalone SBC but NOT as a router phone with an onboard SBC. The router phone SBC doesn't count as 3cx tunnel for some reason.

What phone model/firmware and what PBX install/version did you get this behaviour on?

 

[paulodagraca]

Hello jdi92,

First of all, it is wrong to not want a SBC, it is the first think you should want.

There are 3 options to seup an IP Phone on the 3CX Server:
A) Use of an SBC on remote site, to register the IP Phone.
B) Using an IP with 'Router' function (inbuild SBC).
C) The IP Phone will register as a 'flat' IP service (it seems, this is want you want to use)

To use this option you need make sure of the following options:
- Do the firewall test on the 3CX servere, it must be green and should be 100% good.
- The option "Block remote non-tunnel connections (Insecure!)", should not be set on the extension.
- Manually setup the IP Phone with SIP Details to register externally via the FQDN of the 3CX server.

The registration of an IP phone is as simple as just a few 'UDP' IP packets on the SIP port (default 5060 if not changed).
So again this should work, if not please check the SIP registration details you have used in the IP phone, there should not be anything else to do or check.

That said, it normally is 90% of the cases there is something wrong with the firewall.

Paulo