Fanvil X3S showing up twice in the Phones list on 3CX.

[Ruairidh]

Info:
* I only have one phone
* It's using Direct SIP (STUN - remote)
* The Phones list in 3CX shows the exactl same phone, firmware, mac address twice
* Phone firmware version: 2.14.0.7387

I'm assuming this is causing the issue where I am unable to call this phone.

Thanks for any help!

 

[VasilisV_3CX]

Hi @Ruairidh,

I think my colleague best explained it here: https://www.3cx.com/community/threa...in-list-user-cant-use-phone.69187/post-303318

 

[Ruairidh]

System Information:
3CX Version: 18.0 (Build 461)
Server OS: Debian 10
Is the 3CX Server Hosted: AWS EC2
IP Phone Make/Model/Firmware: Fanvil X3S / 2.14.0.7387
Provisioning Method: Direct SIP (STUN - remote)
Trunk Provider: OrbTalk
Has the Firewall Checker passed: YES
Are custom Phone Templates being used: NO

* Each stun phones needs a fixed ip address (manually or via dhcp)
** DONE

* Each phone requires a different sip port , block of rtp ports (normally 12 ports) e.g phone 1 - sip port 5065, rtp ports 14000-14012, phone 2 - sip port 5067, rtp ports 14013-14025’
** I only have 1 phone

* On the router protecting the phones, you need to setup port forwarding to the phones ip address with the correct ports configured for them
** DONE

* You will need to reprovision the phones by restarting them.
** DONE

* Have you tried restarting the phone
** DONE

* Rebooting the 3cx server, sometimes just restarting the services do not work so a reboot is required
** DONE

Result:
I still have two phone showing up in the Phones list, all with identical name, ip, mac

Any more insights would be great!

 

[JohnS_3CX]

Hi,

Remember that even if you setup your firewall perfectly, the ISP modem can still do things to the traffic which you may not be aware of, and in some cases not even have control over due to ISP lockout. Does the ISP modem work in bridge mode currently, allowing your firewall full access to all internet ports? If not, then the port forwards on your firewall would effectively be null and void due to the modem blocking them one hop down the line.

If you want the problems to go away, your best bet is to install an SBC on a local machine (or a Raspberry Pi if you have one available) on the same network as the phones.