Trouble with provisioning Fanvil X7-V2

[MarkOdams]

Hi

When i try to auto provision the X7-V2 the phone downloads the config however the Proxy Address is blank, all the other details are there. Without this the registration is stuck on timeout. When i add this via the web gui the phone registers OK.

Any ideas what we are doing wrong?

 

[JohnS_3CX]

Hi,

If this is a router phone, make sure you are using the correct firmware provided by 3CX.
https://www.3cx.com/docs/phone-firmwares/

If it's a normal phone over SBC, make sure the SBC is already online before you provision any phones on it.

Then, delete the phone, add it again fresh, and finally factory reset it to load the configuration.

 

[MarkOdams]

Hi,

If this is a router phone, make sure you are using the correct firmware provided by 3CX.
https://www.3cx.com/docs/phone-firmwares/

If it's a normal phone over SBC, make sure the SBC is already online before you provision any phones on it.

Then, delete the phone, add it again fresh, and finally factory reset it to load the configuration.

It is a router phone and has the latest firmware.

I have got around it by doing a custom template which includes

{IF network=SBC}
<Proxy_Addr>%%param:bxpublicip%%</Proxy_Addr>
<Proxy_Port>%%local_sbc_port%%</Proxy_Port>
{ENDIF}

This is what seems to be missing in the default template.

 

[JohnS_3CX]

Hi Mark,

Those are not the correct values you used there. The correct ones do exist and can be seen below:



My X7-V2 just provisioned and registered successfully running firmware 20.12.17 on 3CX V20 (Build1620) based on the above values that already exist in our final release.

What you have done above is essentially told the phone to bypass its own SBC and be a STUN phone. This will not be reliable in the long run even if you got it to work temporarily. The worst part is that the phone will be reporting its local IP to the PBX and you will have issues with at least some scenarios having one way audio (the other end will not be able to hear the X7-V2).

I think you need to revert your template and troubleshoot this further.