Needed: WiFi Setup for Fanvil V65 Phones with 3CX

[llatin]

Hi everyone,


I’m in the middle of a deployment for a customer with about 25 Fanvil V65 phones installed across remote locations.

Half of the phones are wired and working perfectly, but the other half need to connect via WiFi. I’ve seen posts here about getting these phones to work over WiFi, even though it’s not the recommended setup.

The client requires WiFi for this migration to be successful, as their previous PBX supported it. Since switching to 3CX, we've encountered issues connecting the phones over WiFi. The phones are already installed at their locations, so I’m looking for workarounds as quickly as possible.

Here’s the situation:

3CX is cloud-hosted, so each phone connects directly as a router phone.

The wired phones connect and register without issues.

As soon as we switch to WiFi, we lose the IP address and receive a "SIP Register Failed" message on the phone screen.

Has anyone successfully configured Fanvil V65 phones for WiFi with 3CX? If so, could you please share your setup or any tips to resolve this issue?


Any help would be greatly appreciated!



Thanks in advance!

 

[llatin]

Also just for reference we are using the latest firmware - 2.12.20

 

[llatin]

we also see this in the phone logs - This phone was connected directly to the network before switching to wifi and works on ethernet. but with WIFI we get the below and as mentioned above sip Register failed

Nov 27 22:23:59 (none) local0.debug wpa_supplicant: 2024-11-28 08-23-59: rfkill: Cannot open RFKILL control device
Nov 27 22:23:59 (none) local0.debug wpa_supplicant: 2024-11-28 08-23-59: nl80211: RFKILL status not available

 

[llatin]

For anyone else with this issue the fix was to install an SBC on the users pc.

https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

and then point the phone to the SBC through the users pc.

 

[kokolino23]

@llatin how did you connect this, please? I'm having the same issue and I can't connect it through the WiFi even though it's configured through an SBC.
The phone has 2 MAC addresses, one for the Ethernet, the other one for WiFi. If I connect the phone on tha Ethernet port, works fine but no joy through the WiFi?!
The phone was added on 3CX using the WiFi MAC and through an SBC installed on my PC (same network as the phone).
Thanks

 

[llatin]

Hey @kokolino23

So installed the SBC on the machine the user was using as all users were remote,

Then in 3cx cloud, i added the phone MAC but instead of selecting the phone as the router i selected the SBC I provisioned on the users machine.

and off it went.. for about 10 phones each had their own SBC due to all being remote.

 

[llatin]

Hey @kokolino23

So installed the SBC on the machine the user was using as all users were remote,

Then in 3cx cloud, i added the phone MAC but instead of selecting the phone as the router i selected the SBC I provisioned on the users machine.

and off it went.. for about 10 phones each had their own SBC due to all being remote.

If you need a hand, reach out at [email protected], see if i can help as i know how frustrating it was to get working under pressure.

 

[kokolino23]

If you need a hand, reach out at [email protected], see if i can help as i know how frustrating it was to get working under pressure.

That's what I did for mine but still doesn't register while on the WiFi. The phone has 2 MAC addresses, one for the Ethernet and the other one for WiFi, which one did you use to configure the phone on 3CX? My phone works fine on the ethernet port using the SBC installed on the local PC but not on the WiFi ?! I've added 2 phones for that user, using both MAC addresses.

 

[Fanvil Technical Support]

Regarding the MAC address: Only the MAC address of the Ethernet is used as the unique identifier. It is not recommended to deploy 3CX under Wi-Fi because 3CX considers Wi-Fi to be less stable.

 

[kokolino23]

The phone doesn't connect over WiFi as PnP, only if we use a LAN cable. I've tried the MAC for both WiFi and Ethernet port but won't connect on the wireless. I've ended up configuring the phone as a STUN and connected on the WiFi.