Solved direct SIP registration - from 3rd party phone - v20

[rattler555]

Hello,

We have a security doorbell in an isolated area that was functioning properly on v18, using SIP credentials to authenticate to the PBX. However, even after enabling direct SIP calling, the phone now registers with a 403 error. The Auth ID and password are correct.

Is it possible to connect this device using a SIP account (Auth ID and password) pointing to the PBX? It's not feasible to install an SBC here as it's on a third-party managed network.

Any assistance would be appreciated.

 

[NicholasP_3CX]

Yes, it should be possible to connect it (eventhough it is recommended to come in through an SBC).

You just need to ensure that the device is allowed to register in by making sure that the option for it to connect from a non tunnel connection is unchecked. Also check if this device is not in the IP blacklist.

Do you have an entry in the IP Phone tab of the user so the credentials are available?

 

[rattler555]

Yes, it should be possible to connect it (eventhough it is recommended to come in through an SBC).

You just need to ensure that the device is allowed to register in by making sure that the option for it to connect from a non tunnel connection is unchecked. Also check if this device is not in the IP blacklist.

Do you have an entry in the IP Phone tab of the user so the credentials are available?

Worked like a charm. I was trying to use the user pwd and SIP ID. Do I still need to have the allow direct sip calling options enabled under system settings - or is this for outside calling inbound to the pbx?

 

[NicholasP_3CX]

Its for allowing outside calls via Direct SIP. You can omit that.