v20 STUN setup for existing one off employees (Fanvil X4/X4U)

[bmfid]

I know I'll take flak for holding on to the past, but this is a real issue we're facing and I cant believe we're alone.

Does anyone actively have v20 working with Fanvil devices using STUN?

Scenario: Existing systems for clients who have 'recently' invested in new hardware - all are using direct connect (ie vpn) or SBC within office, but they have a hybrid workers who have desk sets at home. It would be nice to be able to move forward with the upgrade to v20 for them without selling them new hardware in the name of a router phone or SBC. Obviously all new deployments we would include for supported router phone models for this type of user.

Ive created a custom profile for the phones including the following code:

<AllowedNetworkConfig>
<option value="LOCALLAN">0</option>
<option value="REMOTESTUN">1</option>
<option value="SBC">0</option>
</AllowedNetworkConfig>

Ive searched parameters and have tried STUNDISABLED set to both 0 and 1

The defaulted phone reboots and appears to provision as normal, but always says timeout waiting for STUN server and never registers.

Can anyone shed some light on what we might be doing wrong/missing?

Thanks in advance for your time.

 

[TheodorosG_3CX]

This can be related with sip ports as well.
Is the firewall checker passed?

 

[bmfid]

This can be related with sip ports as well.
Is the firewall checker passed?

It is indeed.

 

[OlegR_3CX]

Hi there.

For STUN to work on the extension, you need to have option below OFF as in the screenshot, else the server will not allow it to be registrated :

 

[bmfid]

Thank-you for your response - that was done as well.

Hi there.

For STUN to work on the extension, you need to have option below OFF as in the screenshot, else the server will not allow it to be registrated :


View attachment 40981

 

[OlegR_3CX]

So what error do you get there?

 

[OlegR_3CX]

Have you checked SIP-ALG in the remote site where the phones are and ensured that it is OFF?
You could also check the REGISTER message, and in the contact header, you have a valid full public IP and it's not a local one?