Issues provisioning a Yealink T42S in local LAN to a DO hosted 3CX

[clendee]

Hi folks,

We are a very small organisation and have two sites (though I am only trying to get one site working currently).
We intend to use only one handset at each site, I have purchased a Yealink T42S for testing.
I have setup 3CX on Digital Ocean.

I have updated the firmware to the latest version on the T42S
I have added the phone to my user account as per the RPS section on this guide https://www.3cx.com/docs/manual/configuring-ip-phones/

What firewall ports do I need to open on my site network in order for the handset to be properly provisioned to the DO 3CX. Currently the phone does not appear on the 3CX console so I presume its not communicating correctly with the PBX. Im using pfSense on my site network.

I hope this makes some kind of sense,

Many thanks,

 

[TheodorosG_3CX]

Since you are using STUN provisioning the phones will not appear as new in the PBX.
You need to manually configure the phone in the extension and send the RPS to the phone.
• https://www.3cx.com/sip-phones/yealink-t4-series/
If there are multiple phones in the same remote location you need to ensure first that in the provisioning tab of each extension the Local SIP Port of Phone is different between the extensions that you have selected to register through STUN method and are behind the same Public ip address (1st 5065, 2nd 5066, 3rd 5067, etc.. ) as well the Local RTP Audio Ports Start ( 1st 14000-140019, 2nd 14020-14039, 3rd 14040-14059, etc.. ).
Then on the remote firewall you have to make a Static NAT and Static Port Forwarding to the Private ip address of each phone.

 

[clendee]

Thank you for your speedy response.
I think Im good up until the last line that you wrote above.

Is there any documentation \ example available on setting up the Static NAT and Port forwarding in pfSense?

I also presume setting up an SBC for a single handset is probably overkill?

Thanks for your time.

 

[TheodorosG_3CX]

The only case study available is the one below but still this is just a reference and not apply to all pfSense:
• https://www.3cx.com/docs/pfsense-firewall/