Cisco SPA112 on cloud-based PBX

[David Ewer]

I am trying to setup a Cisco SPA112 on a cloud-based 3CX PBX running version 15.5.

Under Proxy and Registration I have provided the FQDN of my PBX as the Proxy. Under Subscriber Information I have provided the Extension Number for the Display Name, User ID and AuthID (Enabled AuthID) plus the password as per my extension settings.

On the SIP tab, under NAT Support Parameters I have enabled STUN and provided the STUN server stun.3cx.com.

I have created a new extension on my PBX, allowed use of extension outside of LAN.

I have update SPA112 to the latest firmware but it will not register.

Is there anything that I might have missed?

Thanks

David

 

[eddv123]

This has been covered before in a few strings if you Google search - for example:
https://www.3cx.com/community/threads/spa112-on-a-cloud-hosted-3cx-pbx.58789/

I would recommend you use a VPN connection or SBC if you are going to attempt this (as it is an un-supported setup) as STUN will leave you with no security. You can use Secure SIP or SRTP if you want to encrypt the traffic though.

If you are going to persist with STUN however look at the extension in 3CX and ensure that "Disallow use of extension outside of the LAN" is turned off.

 

[eddv123]

Also your firewall settings/ports being opened on the firewall (run firewall checker):
https://www.3cx.com/docs/ports/

 

[David Ewer]

Thanks for your reply eddv123. STUN is my preferred method, due to limitations on the customer's site. I have found a number of articles relating to setting up the SPA112 on 3CX using Google but none of them explain exactly how to configure the SPA112 to work with 3CX using STUN. In the example you gave steve.davidson had already successfully setup an SPA112.

 

[leejor]

In the 3CX Activity Log, do you see an attempted registration, but perhaps a failure? If it happens too often the IP may be blacklisted (check the list). There really should be no issue getting it to work remotely, using manual configuration, officially supported, or not.

If it is a STUN issue, then you may see a registration, but with the local IP of the device, not the public IP of the router it is behind. Are there more than one SIP device at the remote location?

 

[eddv123]

If you are using Google on hosted then also then it will likely have ACL's or security groups which will block any inbound traffic to the PBX:https://support.google.com/cloud/answer/6262505?hl=en